Wormhole hack was caused by a bug in solana itself (patched very recently - but requiring existing contracts to...

Wormhole hack was caused by a bug in solana itself (patched very recently - but requiring existing contracts to upgrade), not wormhole.
twitter.com/kelvinfichter/status/1489048862824226816
this explains why SBF decided to silently provide a 120k eth bailout. This would kill Solana.

Attached: 1643678489060.png (585x577, 136.95K)

Other urls found in this thread:

github.com/solana-labs/solana/blob/7ba57e7a7c87fca96917a773ed944270178368c9/sdk/program/src/sysvar/instructions.rs#L180-L188
twitter.com/NSFWRedditImage

how does a bug in solana require contracts to update separately?
you mean it was a bug in their compiler not the blockchain itself?

Sam deserves all of this and more.
>WJG0D

Attached: 4517988D-CE84-4B71-8D22-6C2725BF71B8.jpg (1125x746, 241.39K)

They made an instruction that was supposed to execute system contracts (the equivalent of precompiles on ethereum), but actually was executing any address it received.
Why they just 'deprecated' it instead of fixing is a mystery to me.

"load_instruction_at" sounds like something that'd be compiled to byte code for launch on chain, so yeah. In any case it's pretty much synonymous when smart contracts are being written with code that gets compiled by this dumpster fire

>SBF decided to silently provide a 120k eth bailout.
This happen already?

github.com/solana-labs/solana/blob/7ba57e7a7c87fca96917a773ed944270178368c9/sdk/program/src/sysvar/instructions.rs#L180-L188

Attached: 1625664400665.png (922x188, 18.52K)

it's possible it's just code that was being compiled into vm opcodes, and not part of vm itself, which would explain why it couldn't be fixed
never coded for solana before

imagine depreciating insecure instructions instead of just disabling. that's a move only a blockchain with few active developers would make.

insanity

hopefully not, my assumption is that they kept the opcode for contract data that was deployed prior to a certain block for "backwards compatibility".