Content
@
0 reply
0 recast
2 reactions
Aditya Kulkarni
@adityapk
Bad news: To make EIP 712 signatures work in Go, you have to manually increment the 65th byte of the signature by 27 to make it work (!!) Good news: Github Co-pilot knows this, and auto completed `sig[64] += 27` at the end of my function without me prompting (or even knowing about this)
4 replies
1 recast
15 reactions
Shane da Silva
@sds
Yeah, it turns out this hack appears in more places than you would expect (it's not just Go). https://github.com/safe-global/safe-core-sdk/blob/4d1c0e14630f951c2498e1d4dd521403af91d6e1/packages/protocol-kit/src/utils/signatures/utils.ts#L91
2 replies
0 recast
1 reaction
Mikko
@moo
It's because many Ethereum APIs and such are badly designed and badly standardised. Now it's too late to fix things and hacks and problems will live around forever.
1 reply
0 recast
2 reactions
Aditya Kulkarni
@adityapk
Our only hope is that the AIs learn all these hacks and workarounds and fix our code for us.
1 reply
0 recast
1 reaction
Mikko
@moo
That's an unreasonable expection. In this phase, as progress on innovation is slowing down, a good alternative is to write down "lessons learnt" and then work on a new blockchain that is still in much earlier phase and ensure the mistakes in 2.0, 3.0 or 4.0 blockchains will be fixed.
2 replies
0 recast
1 reaction
Mikko
@moo
Like with the Mastercoin failure that led to the creation of Ethereum. However, the problem with this process is that the cycle is really really long ~5-7 years.
0 reply
0 recast
0 reaction
Cassie Heart
@cassie
That is exactly what I'm doing 🫡
1 reply
0 recast
1 reaction
