jxom pfp

jxom

@jxom

43 Following
13511 Followers
jxom pfp
jxom
@jxom
Damn
0 reply
0 recast
2 reactions
jxom pfp
jxom
@jxom
@wagmi/core
1 reply
1 recast
2 reactions
jxom pfp
jxom
@jxom
EIP-7702 is now stable in Viem which is why you were seeing this. But we added these exports back into viem/experimental, and marked them as deprecated to still be backwards compatible with libraries that have Viem as a peer dep. Our bad!
1 reply
0 recast
1 reaction
jxom pfp
jxom
@jxom
where is the out-of-date viem docs?
1 reply
0 recast
0 reaction
jxom pfp
jxom
@jxom
Blog post? We need an ERC for this.
0 reply
0 recast
1 reaction
jxom pfp
jxom
@jxom
Viem doesn’t default to it right now though. Maybe we should if there are obvious benefits.
0 reply
0 recast
1 reaction
jxom pfp
jxom
@jxom
Is there really a performance benefit as everyone is on HTTP/2 now?
2 replies
0 recast
1 reaction
jxom pfp
jxom
@jxom
Simple answer: update vocs to latest
0 reply
0 recast
1 reaction
jxom pfp
jxom
@jxom
Feel free to open a PR adding it!
0 reply
0 recast
2 reactions
jxom pfp
jxom
@jxom
🫡
0 reply
0 recast
0 reaction
jxom pfp
jxom
@jxom
wow you got me
0 reply
0 recast
1 reaction
jxom pfp
jxom
@jxom
Your cast is trending!
1 reply
0 recast
4 reactions
jxom pfp
jxom
@jxom
check out https://github.com/ethereum/EIPs/blob/master/EIPS/eip-7851.md
0 reply
0 recast
0 reaction
jxom pfp
jxom
@jxom
thought we were talking about the case where we are not persisting the private key ("forgetting"). nevermind.
1 reply
0 recast
0 reaction
jxom pfp
jxom
@jxom
so for this case, you want to rotate for the case where it may take a billion years to crack the private key?
1 reply
0 recast
0 reaction
jxom pfp
jxom
@jxom
sure we can easily upgrade signers on SCA to be PQ-safe, but this wouldn't suffice because everything else would be screwed, so we need a backwards compatible way to secure the vulnerable keys.
1 reply
0 recast
0 reaction
jxom pfp
jxom
@jxom
yeah, the idea is that EOA key will be deactivated. so signature verification for that EOA won't work on execution / onchain.
0 reply
0 recast
0 reaction
jxom pfp
jxom
@jxom
there are also proposal addressing PK deactivation: https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7851.md
1 reply
0 recast
1 reaction
jxom pfp
jxom
@jxom
why is it weird? if it's a post-quantum concern, then the issue is orthogonal as majority of multisig & execution signers are not PQ safe right now.
3 replies
0 recast
1 reaction
jxom pfp
jxom
@jxom
It doesn’t need to be “stored” though :)
1 reply
0 recast
0 reaction