vitalik.eth (@VitalikButerin)

The final verdict from @trueo_’s most contentious market has been delivered. The Jury voted for an outcome Reset. In other words, they ruled that it was too early to resolve the market. But there were some very interesting things about this dispute… For starters, both TRUE holders and Attesters voted against the Oracle Council’s initial decision. The Oracle Council voted 3-2 in favor of a YES outcome (I was among the YES voters). But TRUE holders and Attesters voted in supermajority support of the dispute. They deemed that the proposal came too early, and that Polymarket had not really released a “token” yet. Or did they? I personally voted YES as an oracle council member because I felt like the rules, though ambiguous, were satisfied as written when Polymarket released pUSD. I wasn’t happy about it, obviously it didn’t capture the essence of the market which was clearly meant to be about a potential network or governance token, but I voted YES nonetheless because I felt like the criteria in a literal sense was met when pUSD dropped. But TRUE holders and Attesters felt otherwise. They must have felt like the purpose of the market wasn’t satisfied even if the rules in a very rigid and literal sense were. I know the outcome might not be to everyone’s liking, and I know that some users would have preferred a YES outcome, but I do hope that they at least found some consolation in the process it self. Namely that the various arguments were aired, and that multiple desperate judgements came to pass on the dispute. In the future these contentious markets can be avoided with more precise resolution rules, but there is always some room for interpretation or some hidden ambiguity in the spectrum of possibilities. Getting these things right is very difficult, and ultimately, what I believe is more important than the outcome itself, is the process through which an outcome is derived. All this being said, there’s nothing stopping someone from proposing the same outcome again in hopes that TRUE holders have changed their minds, or that a different batch of Attesters gets selected who are more sympathetic to the resolution. Prediction markets are vey tricky specifically because of their subjective nature. But that’s also what makes them interesting! We still have much to improve on, and we learned a lot from this dispute, but hopefully we were able to prove that we take the concept of due process very seriously. Because at the end of the day, a prediction market is only as good as its oracle!

🔐 New EIP-8250: Keyed Nonces for Frame Transactions 🔐 by @soispoke, @nero_eth, @lightclients and @VitalikButerin This replaces the single sender nonce with (nonce_key, nonce_seq), giving frame transactions independent replay domains. For privacy protocols, the key can be derived from a nullifier: concurrent withdrawals from a shared sender become possible, with inclusion atomically marking the nullifier spent. Target fork: Hegota Links below 👇

Excitining News! Signal Shot is a public moonshot to verify the Signal protocol and its Rust implementation using Lean. It is a joint effort of Signal (Rolfe Schmidt), the Beneficial AI Foundation (Max Tegmark), and the Lean FRO. #leanprover# #leanlang#

The kind people at @eth_limo have warned me that there has been an attack on their DNS registrar. So please do not visit or other pages until they confirm that things are back to normal. You can check my blog via IPFS directly here: