
Philip
339 posts

Philip
@phipsae
Teaching agents how to use and build on Ethereum @ethereumfndn | @buidlguidl



Security starts with developers. We are participating in the @thedaofund x @Giveth Ethereum Security QF round! Through Speedrun Ethereum, Scaffold-ETH 2, CTF games and tools like ABI Ninja and HackedWalletRecovery, BuidlGuidl is producing security-aware builders and protecting users when things go wrong. It is a quadratic funding round, meaning every single dollar counts and amplifies our impact.

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!


Last week, Ethereum core contributors gathered in Svalbard for the Soldøgn interop: a week long event focused on hardening Glamsterdam implementations to scale Ethereum securely ☀️ Read the full recap, including their candidate post-fork gas limit, below:

Last week, Ethereum core contributors gathered in Svalbard for the Soldøgn interop: a week long event focused on hardening Glamsterdam implementations to scale Ethereum securely ☀️ Read the full recap, including their candidate post-fork gas limit, below:

Funding Ethereum education through the power of @buidlguidl 🦄 BuidlGuidl's Speedrun Ethereum enables people to easily learn how to build on ethereum🏰 We're glad that today's donation will go towards helping the future builders of our ecosystem- All in line with the Ethereum's vision from 2016💻







AGENT HOURS BY @bankrbot streaming live on X - FRIDAY 4/10 1PM EST @igoryuzo and I will be speaking agentic business with the GOAT @austingriffith — @clawdbotatg / $CLAWD, ethereum foundation & hottest new infra builder around @kevincodex — @gitlawb / $GITLAWB

A must read if you want to start tinkering with RAG, great job @ShivBhonde !




