211669
jtriley.eth
@jtriley #211669
926 Follower 1 Following
i'm running for op's security council, mostly incident response and signing off on protocol changes
will use hardware wallet for signing key w 3/6 shamir backup from a python script on an airgapped raspberry pi. might blow torch the sd card or smth idk
https://gov.optimism.io/t/security-council-member-nomination-riley-jtriley-eth/8705
will use hardware wallet for signing key w 3/6 shamir backup from a python script on an airgapped raspberry pi. might blow torch the sd card or smth idk
https://gov.optimism.io/t/security-council-member-nomination-riley-jtriley-eth/8705
venezuela is the bear case for zk voting bc you can have all the votes in clear text and the loser can just say "i won" and people just.. believe them. crazy
anyway here's anonymized votes for the venezuelan election on arweave (static html, no js):
https://akrd.net/zV0t6C8am6ISHVO93RyK9Xwe1sgfqk2-Idm40hhBFvo
anyway here's anonymized votes for the venezuelan election on arweave (static html, no js):
https://akrd.net/zV0t6C8am6ISHVO93RyK9Xwe1sgfqk2-Idm40hhBFvo
cinematic flying on the lake :3
essentials team built out two pieces recently, declarative execution environment (essentialvm) & constraint driven language (pint)
pint contracts are composed of a persistent storage block & a series of predicates which constrain how state transitions happen. state access is made explicit in predicates, identifier (counter) may constrain existing state, identifier w single-quote suffix (counter') may constrain next state.
vm itself is a 64 bit stack machine w two execution stages, one for loading storage variables into a tx buffer, the other for constraining values in the tx buffer. isa is minimal, w a handful of logical, arithmetic, elliptic curve, sha, storage, and control flow ops
note that state is not explicitly assigned to a single value, state is arbitrarily provided by solvers, predicates only constrain the bounds of what solvers submit
obligatory counter attached:
pint contracts are composed of a persistent storage block & a series of predicates which constrain how state transitions happen. state access is made explicit in predicates, identifier (counter) may constrain existing state, identifier w single-quote suffix (counter') may constrain next state.
vm itself is a 64 bit stack machine w two execution stages, one for loading storage variables into a tx buffer, the other for constraining values in the tx buffer. isa is minimal, w a handful of logical, arithmetic, elliptic curve, sha, storage, and control flow ops
note that state is not explicitly assigned to a single value, state is arbitrarily provided by solvers, predicates only constrain the bounds of what solvers submit
obligatory counter attached:
HOLD UP WARP HAS VIDEO NOW??
moving the abstract nonsense to warp
the obj of these started as general study of abstract algebra, but has evolved into foundations of zk
first up is set theory
https://substack.com/home/post/p-145043277?r=1qyfrf&utm_campaign=post&utm_medium=web
the obj of these started as general study of abstract algebra, but has evolved into foundations of zk
first up is set theory
https://substack.com/home/post/p-145043277?r=1qyfrf&utm_campaign=post&utm_medium=web
crypto devs are due for a cultural revolution
venture slopfest grows older by the day, memecoins offer nihilistic alternative, but neither are satisfying for those of us sold on agent codification where rules are smart contract source files and enforcement is beautiful composition of cryptography and social consensus over code execution
the crypto we were born into no longer exists. but it's all too easy to forget where the industry comes from, where the technology comes from. cryptographers and game theoreticists lay foundations, but implementations don't exist without implementors
what we do doesn't have to be big, it doesn't have to be the next ethereum, we just have to open the editor
venture slopfest grows older by the day, memecoins offer nihilistic alternative, but neither are satisfying for those of us sold on agent codification where rules are smart contract source files and enforcement is beautiful composition of cryptography and social consensus over code execution
the crypto we were born into no longer exists. but it's all too easy to forget where the industry comes from, where the technology comes from. cryptographers and game theoreticists lay foundations, but implementations don't exist without implementors
what we do doesn't have to be big, it doesn't have to be the next ethereum, we just have to open the editor
incredibly refreshing to see notable voices point out the speculation and speculation accessories meta. venture capital was a premature abstraction, rocket fuel showed up looking to take off and the rocket isn't assembled
decline of hilarious defi summer yields and subsequent nft frenzy leaves an increasing pool of capital looking for increasingly scarce yield. as capital moves to other industries, it will be generally considered a "death of crypto" but is exactly the opposite. cultural maturation happens when there is no bag for which dishonesty can benefit
the revolution will be underfunded
decline of hilarious defi summer yields and subsequent nft frenzy leaves an increasing pool of capital looking for increasingly scarce yield. as capital moves to other industries, it will be generally considered a "death of crypto" but is exactly the opposite. cultural maturation happens when there is no bag for which dishonesty can benefit
the revolution will be underfunded
are there papers with formal specifications of dao's?
dao topology is composable from the m-of-n to the connectedness of of all dao's across all chains
multisigs are the most restricted, delegating alignment to external social and legal contracts on a one-member one-vote basis
daoโข๏ธ plutocracy is the most open, minimizing social and legal contract assumptions, opening membership to any buyers of the coin, trusting only the self-interest objective function
former exhibits high agency, explicit alignment, and clear direction. latter necessarily exhibits low agency to buffer capture cost from capture benefit
dao of dao's opens chain-wide and ecosystem-wide opportunities for human collaboration between ideologies, ethnicities, incentives, but a pure plutocratic supermajority leads only to the same failures of dao's as they are now
non-financialized dao structures, exotic selection mechanisms, and novel alignments are great starting points, no dao is too small, no assumption set is too large
multisigs are the most restricted, delegating alignment to external social and legal contracts on a one-member one-vote basis
daoโข๏ธ plutocracy is the most open, minimizing social and legal contract assumptions, opening membership to any buyers of the coin, trusting only the self-interest objective function
former exhibits high agency, explicit alignment, and clear direction. latter necessarily exhibits low agency to buffer capture cost from capture benefit
dao of dao's opens chain-wide and ecosystem-wide opportunities for human collaboration between ideologies, ethnicities, incentives, but a pure plutocratic supermajority leads only to the same failures of dao's as they are now
non-financialized dao structures, exotic selection mechanisms, and novel alignments are great starting points, no dao is too small, no assumption set is too large
finally getting some good flight time, gonna start uploading footage soon :3
rwandan espresso & mรผesli
gm :3
gm :3
cooked my esc on my last flight, time for a swap ._.
what gets logged if you send:
1. no calldata, no wei?
2. no calldata, one wei?
3. calldata, no wei?
4. calldata, wei?
1. no calldata, no wei?
2. no calldata, one wei?
3. calldata, no wei?
4. calldata, wei?
announcing the rippler, a fast as fuck multicaller.
the rippler uses a custom encoding scheme, packing calls in reverse order and prefixing the calldata with a 2 byte jump target indicating the number of calls to make.
0/3
https://github.com/jtriley-eth/the-rippler
the rippler uses a custom encoding scheme, packing calls in reverse order and prefixing the calldata with a 2 byte jump target indicating the number of calls to make.
0/3
https://github.com/jtriley-eth/the-rippler
b4ufly is a great app for planning an fpv session
you need to be in unrestricted airspace with no NOTAMs to fly. special events like airshows may affect where you can fly
dji by default will not let you fly in restricted airspace but this is not always the case, better to be safu
you need to be in unrestricted airspace with no NOTAMs to fly. special events like airshows may affect where you can fly
dji by default will not let you fly in restricted airspace but this is not always the case, better to be safu
don't forget to submit your tcr
spot the bug
if you're as tired of IERC____Receiver implementations as i am
here's how you never have to deal with it again
here's how you never have to deal with it again
playing with the simulator while the drone is under repair ๐ซ
https://youtube.com/shorts/v_8eL3dToZ4?si=MK0cqeaNQ6RVSENR
https://youtube.com/shorts/v_8eL3dToZ4?si=MK0cqeaNQ6RVSENR
cleared the terminal after a failed fuzz run and now i canโt reproduce
this is fine
this is fine
fuzzing is wild bc sometimes you find useful edge cases you wouldn't have thought of but then other times it's like "what if you are the zero address and transfer zero tokens to the zero address on behalf of the zero address with zero approval and also the token is the zero address"
can we please rewrite erc4337 from the ground up?
i dont wanna change the std it's just poorly organized and more monologue than specification
i dont wanna change the std it's just poorly organized and more monologue than specification