pull down to refresh

223 sats \ 8 replies \ @optimism 6 Sep \ parent \ on: Stacker Saloon

No.

It sounds pretty much like a recently introduced or recently fixed consensus bug, which is why mempool's node would stop processing blocks right before the tx happened. It rejected the chain from that block onward.

Also, since the source seems to be confidential txs, it sounds very much like an inflation bug a la zcash.

"Fake L2".. I wasn't aware that they called their sidechain an L2?

write
compose
147 sats \ 7 replies \ @Scoresby 6 Sep

Wouldn't wiz be running an older version than blockstream itself?

If so, I think that leans more toward recently introduced than recently fixed?

reply
1 sat \ 6 replies \ @optimism 6 Sep

I suspect that too, yes. But I am fully prepared to be not surprised if it is the other way around! I mean... stranger things have happened.

reply
147 sats \ 5 replies \ @Scoresby 6 Sep
reply
103 sats \ 4 replies \ @optimism 6 Sep

Oh crap... how'd you find that one? At a glance looks like a cache bug, yes. The commit it fixes is 6 months old though, so still more likely to be that Mempool ran the older version.

reply
126 sats \ 3 replies \ @Scoresby 6 Sep

I wish I could say I found it. Nifty said something about it and I am just speculating based off her extensive knowledge.

reply
103 sats \ 2 replies \ @optimism 6 Sep
reply
126 sats \ 1 reply \ @Scoresby 6 Sep

commit 2 hrs ago?

reply
103 sats \ 0 replies \ @optimism 6 Sep

Yes. It fixes the current bug by nuking the entire caching mechanism and just validating the range proofs (which, fwiw, is good, but it is slow)

reply on another page