CH

engineering @base

[CH @_chunter]

@apoorveth Awesome 👏 love this

[CH @_chunter]

@theprivacycash Just deposited 🤫

[CH @_chunter]

@Nick_Prince12 lfg

[CH @_chunter]

@ryanberckmans Feels like another good reason for 8130

[CH @_chunter]

@danielvf What’s your take on 8130? Easy rules to follow for accounts + easy upgrade path for protocol. No EVM changes, can build native performance for authentication mechanisms while maintaining same useful flexibility as 8141

[CH @_chunter]

I do think that 8130 has the right middle ground.

Easy validation for nodes that want to cover the 90% of use cases today. 8141 requires nodes to simulate to tell if its breaking their rules, where as 8130 can tell the rules explicitly in the tx by verifier address.

Permissionless extension of validation code without fork. FOCIL, permissionless paymasters, privacy pool gas, etc.

https://t.co/nTPJZCy1jm

[CH @_chunter]

@_jxom @lightclients @gakonst https://t.co/5nrL0Q8JXQ

Curious on your take on 8130 then?

Tries to provide a lot of the details/defaults for most accounts but also the extensibility for accounts to define their own features when needed.

[CH @_chunter]

@gakonst 8130 doesn't require 7562 for the average case (k1, p256, webauth, ...).

Nodes only need validation rules if they want to accept any tx validation method.

Validation method is explicit in the tx, so nodes can easily gate on that.

https://t.co/5nrL0Q8JXQ

[CH @_chunter]

8130 enables all the same BUT provides the ability for nodes to cleanly filter tx prior to executing anything for validation. With 8130 you can tell, explicit in the transaction, what the computation will be.

8141 requires nodes to execute, trace and run 7562 to know if it even conforms to the rules.

With 8130 nodes can just run an allowlist of verifiers that cover the 99.99% of wallets without the need for tracing. This set defines the mempool rules. New PQ algo? - just deploy the contract and get nodes to allow it.

8130 also means you only need a small bit of state to validate most transactions.

https://t.co/nTPJZCy1jm

[CH @_chunter]

Updated EIP - 8130 for native account abstraction!

Now has fully permissionless expression of authentication types for wallet signature verification! Fully extensible without hard fork and can optimize at protocol level when needed.

No tracing, no reputation or staking mechanisms. No new opcodes, no new frame system.

Performant, deterministic validation, ready for the PQ + ZK future.

Key rotation, gas abstraction, programable accounts, batching, … it’s all there.

Check it out https://t.co/P3OtOsrJAP

[CH @_chunter]

Check out EIP-8130 — account abstraction by account configuration

The idea: enshrine auth types in a system contract. Protocol reads known storage slots to validate.

Built for all the standard AA use cases (programmable accounts/gas sponsorship/key rotation/...). Backwards compatible with all account types. Made to be extensible and support future quantum migration.

Would love any feedback! https://t.co/47b9SpxkpE

[CH @_chunter]

@nazimahmed @ripsapp @baseapp @farcaster_xyz Let er rip!

[CH @_chunter]

Can’t they:
- lock the satoshi era vulnerable coins
- have some way of adding a proof today that shows you know the private key prior to QC and are transferring ownership of the to a new QC safe key.
- this proof would hide what addresses you are claiming, so even Satoshi could migrate without anyone knowing that it occurred.

[CH @_chunter]

@0xspoder @base @clankeronbase Haha good analysis @0xspoder - $LGSF was created as a food acquisition initiation system! Can send it to people to let them know that you believe it is time to get some food together

[CH @_chunter]

@zksecurityXYZ excited to try!

[CH @_chunter]

@mykcryptodev @Evan_Mann @DylanAbruscato @kellykim_xyz @mindofmiller @jessepollak @eth_call @lindaxie 🌭

[CH @_chunter]

@dcinvestor Mikes way

[CH @_chunter]

@base Also Cat Town music is amazing!

[CH @_chunter]

@base XL

[CH @_chunter]

@jessepollak @ChipotleTweets I too love @ChipotleTweets