alexmiller.eth

@pcaversaccio @moo9000 K determinism was introduced by RFC6979 and is standard for most software based ECDSA signers, though unfortunately less so for HSMs. I think adoption is basically 100% in the crypto industry though (including hardware wallets) #section-3.2" target="_blank" rel="nofollow noopener">datatracker.ietf.org/doc/html/rfc69…

@moo9000 But that's for eth_sign and not eth_signTransaction. Will check it later more carefully.

Any ECDSA signature is based on a random nonce value `k`. If u ever reuse the nonce for the same account (i.e. the `r` param is the same), ur private key can be easily recovered. For educational purposes, I summarised the math derivation & code in 1 repo. github.com/pcaversaccio/e…

Funny enough, I *just* learned about this unfortunate syntax being idiomatic Go like 2 days ago. There has been a lot of discussion over whether or not to hard fork the language to remove it: github.com/golang/go/disc…

Indeed, smart contracts compiled using Vyper versions 0.2.15, 0.2.16, and 0.3.0 are vulnerable, which can lead to the failure of the reentrancy guard.

@evan_van_ness No lol but the temporal pattern is obvious!

@alexmillertech Does the Arkham narcware count?

ETH has been flat over the last 7 days, gas fees have been low and yet we've still been burning ETH. Very bullish in the long run.

@gakonst Ty sir just submitted one!

Overheard someone at some event saying to some devs "don't use Forge, it's not nearly built enough for X" or some version of it. We've built all our tools with input from the community, mentoring, and tight feedback loops. We've helped competitive products grow and gave back all our learnings for free. Yes we are competitive. But we want the entire ecosystem to grow together. There is no room for zero sum thinking. If anything in Foundry doesn't work well, please open an issue with a repro or come to our chatrooms! We will happily discuss and iterate to a great solution like we have in the past. We need all the feedback we can get. More of it! Not less! What should we do?

@josephdelong Never forget the best halftime show of all time twitter.com/PardonMyTake/s…

Can you take me higher?

@LefterisJP @rotkiapp @LiquityProtocol Sorry I meant Liquity - looks like vaults can only be collateralized with native ETH. Just wanted to confirm.

@alexmillertech @rotkiapp @LiquityProtocol what's that? What do you mean? I mean I know it's a token but in which sense do you need support for it? If it's something we don't yet support could you make an issue? github.com/rotki/rotki/is…

Are you still using maker vaults anon? Use @LiquityProtocol or get rekt. You can also then use @rotkiapp to track your troves, stability pools, staking and all related events. ⬇️Try rotki: github.com/rotki/rotki/re… 📈Buy premium: rotki.com/products

PSA: all Maker vaults now charge a minimum of 3.5%/year, up from 1%/year yesterday. Yikes.

@toghrulmaharram @adamscochran @Timccopeland @banteg Yep at a certain point running N validators on a home internet connection is prohibitive. It should be noted, though, that this is being addressed to some extent already: github.com/ethereum/conse…

@adamscochran @Timccopeland @banteg Validator ≠ full node. A single consensus participating full node can have hundreds or even thousands of validators running on top of it. No, it benefits everyone. Raising the upper bound decreases the network overhead, allowing to decrease the lower bound from 32 ETH.

Benefits: - allows for fewer validators - could let rewards more easily compound good move or bad move? theblock.co/post/235386/et…

Interesting and important problem. Uniswap has done a lot of good for the industry, but I agree that this license wrapping precedent is dangerous for web3 development incentives and should be discussed more broadly.

Very fun and clever off-chain scaling mechanism. Not cursed at all IMO

@pcaversaccio Ah so like double-counting exploits etc. Interesting, thanks!

@alexmillertech github.com/OpenZeppelin/o…

It's not only important to understand what signature malleability is in theory, but also what it means in practice. Thus, I created a repo that implements a PoC that showcases how signature malleability attacks, using compact signatures, can be executed: github.com/pcaversaccio/m…

@pcaversaccio What's the attack vector you had in mind? This shows that non-identical signatures validate against the same message, which is also true if the signer chooses any non-RFC6979 `k` value -- not sure where you're going with this.

TL;DR: Signatures must not be used as unique identifiers since the `ecrecover` precompile allows for malleable (non-unique) signatures!

@econoar @DegenSpartan @DAppNode Solo staking rewards are lower in my experience. I don't see LSD market share decreasing as long as mean(reward) > median(reward).

Wrote an article on MPC cryptography stuff. Hope you like math! open.substack.com/pub/decentralf…

@mikedemarais It's more complicated, but you are not the only one who has brought this up...

can u imagine being Consensys and owning M*tam*sk AND GridPlus but never actually making it a cohesive unified experience / product

@christine_dkim Where can I find more background information on this part? "Ryan reminded developers that the revamping of Beacon Chain attestation subnets (attnets) would be rolled out today on May 4"

Yesterday, Ethereum client teams gathered for ACDC Call #108. They talking about prepping EIP 4788 and EIP 6987 for inclusion in Deneb, SSZ considerations for EIP 4844, diversifying MEV relay client dependencies through PR 317, and more. Full writeup: galaxy.com/research/insig…

@tomhschmidt @dwr Yeah Apple will never lift a finger to help public crypto and adding k1 support would fall into that bucket. @blasteasy got the door shut in his face for making the suggestion. But prob best to keep r1 keys off base layer ETH just in case the feds put a backdoor in that curve 😛

@dwr Don't know about the above, but I actually think the opposite is maybe more interesting right now (doing other signature verification e.g. secp256r1 on chain), especially w/ 4337 or custom rollups

Anyone familiar with WebAuthn and Apple Passkeys know if there are plans to: - support ECDSA signatures from arbitrary curves? - allow for encrypt / decrypt actions?