Solana @mtnDAO Demo Day with 💡 Accord and Mutual Risk Pools Demo day pitch presenting Accord (), a Schelling point based adjudication system on Solana. ✅select jurors from a pool, ✅have them commit to & reveal a verdict ✅majority rules Incentives do the hard work to keep keep jurors in line with the truth. The only outcome of accord: A verdict, to be consumed by another Program. A program on top has been built called Hanse: mutual risk pool - the oldest form of pooled protection on earth. Links below 👇👇

The fund has already started positions in 4 ownership coins, and it’s just 3 hours since we launched the fund We’ve broken multiple records for decentralized fund management 💪

Update on Accord (dispute resolution on @solana): ✅ evidence server up and running (takes in your encrypted evidence for a dispute) ✅ cranker running and drawing jurors on its own. ✅ app up and running (on devnet) ✅ first dispute has been filed (with evidence, lol) Few more edge-cases on the deployment, then ready for the first public testing ..

CT, how do you call a cracked up dev that shoots out new projects like a confetti cannon on espresso? > Vaporware Vanguard Here's the thing though: I am not building products but primitives. It’s my shadow architecture for a bigger picture 🤯 Meet me @mtndao and AMA

💡A Schelling Gate could become the sole executor on a @multisig: 1️⃣Squads members approve an exact transaction. 2️⃣The Gate produces a dispute on Accord dispute. 3️⃣Jurors review build artifacts, audits, rationale, and consequences. 4️⃣Only an ACCEPT ruling lets the Gate execute that exact payload. 5️⃣Any changed payload requires a new ruling. That's just multisig with extra steps, right? Almost, but a dispute on Accord can be appealed by anyone before the final verdict. Jurors are selected by token holders. Sounds like an concept worth discussing @MetaDAOProject @realmsdaos

I'm increasingly convinced AI just raises the commitment bar for startups - you really have to care about a problem to succeed at solving it AI makes implementation easier, but this creates a sea of slop on the competitive landscape. To actually differentiate, you need taste - but taste takes an immense cognitive load to develop, implement, and maintain Which means your cognitive load building anything is on maximum, all the time. Maximum cognitive load means you're going to be exhausted no matter what - I'm more exhausted today than I have ever been. If you don't care about the problem you're working on, this is going to be very painful. Pair that with it being very easy to create AI slop and on net harder to create something good (the bar for "good" has moved further than the ease of implementation), I call this the "AI product trough" - it's a murderous slog to get to something actually good now. You really have to want it.

🎉spec'ed out the evidence operator for Accord's dispute resolution. what i wanted (and have now) is a permissionless service that allows you to push any number of files as evidence and have them anchored (hashed) into your dispute. Meanwhile, every juror has the right to read a re-encrypted version while the dispute filer has the freedom to pick which parts of the evidence should made public. The options the jury can chose from are confidential by default (not just the votes) but the filer can make those public as well.

This paper gives a fancy name to a problem you can already feel in your bones "The Tragedy of the Cognitive Commons." Checking AI output requires deep expertise. Deep expertise comes from doing grunt work for years. And grunt work is the first thing AI eats So we're building systems that need expert supervision while dismantling the only known process for making experts The paper calls the shared pool of human expertise the "cognitive commons." Every profession drinks from it. Nobody's refilling it. By eliminating junior roles, each company is acting totally rationally, and the collective result: a profession that can't catch AI's mistakes anymore because it never learned to do the work in the first place Who checks AI's homework in 15 years?

Sharing some first pics of the app for Accord app: ✅file new dispute ✅resolved dispute ✅appealed dispute ✅final dispute ☑️create/list subaccords ☑️stake/unstake for jurors devnet deployment till monday. 🎉

@SolPlay_jonas @solana @triton_one Thank you @SteveCleanBrook Triton the only devnet RPC that would deliver deployments for a weekend grind during @mtndao going live on devnet 🔜🔜🔜

@SolPlay_jonas @solana @triton_one Thank you @SteveCleanBrook Triton the only devnet RPC that would deliver deployments for a weekend grind during @mtndao going live on devnet 🔜🔜🔜

@MetaDAOProject mechanized how a DAO decides: > what should we do❓ We mechanized how it settles a dispute: > who's right? 🫵 A DAO needs both. One decides, one settles and together they run end-to-end on mechanisms. no committee no founder no human bottleneck. 🧵👇