𝐒𝐄𝐋𝐎 𝐔𝐏𝐃𝐀𝐓𝐄🛠️ Selo can now stop a release. 🛑 Until now, Selo paid your x402 endpoint like a real customer and handed you a report. Now its verdict decides whether your release ships. Here’s what’s new 🧵 1. The selo CLI: One command in your release pipeline. You pay Selo 1 USDC over x402. Once that settles, Selo pays your endpoint, runs five checks and returns a verdict. Exit 0 = PASS, ship it. Anything else (FAIL, not proven, refused) blocks the release. 2. GitHub Action: Your deploy runs only after a PASS. Live on Algorand Mainnet, against a demo shop: •broken-v1: paid, 200 OK, but the receipt is missing a field → FAIL, deploy blocked •fixed-v2, same URL: all five checks PASS → deploy promoted 3. Signed Verdicts: Every result is signed by Selo, and anyone can check it offline with selo verify against Selo’s public key. A PASS is bound to one release, URL and method, so it can’t be reused to push out a different release. 4. Never charged twice: If a run is cut off mid-payment, the CLI won’t pay again on its own. --resume fetches the same result with no second charge. If Selo’s payment to your endpoint is unclear, the funds are held, then settled or released only on proof from the chain. The proof is all on Algorand Mainnet: 🔴 Broken release, blocked: github.com/Enoch208/selo/act… 🟢 Fix, promoted: github.com/Enoch208/selo/act… Try it on your endpoint: useselo.xyz @algodevs @AlgoFoundation @AlexaJaccarino @GoPlausible @fredestante @ganainmtech

Selo made the top 20 on the leaderboard at the @Algorand Global x402 Challenge🎉🎉 . Grateful for the recognition, and thank you to everyone who supported the build, but there is still work to be done. We are heading back to the kitchen😁👨‍🍳, updates are on the way.. keep an eye out👀 @ganainmtech @AlgoFoundation @Camohe90

Selo is live on the Algorand mainnet ..the first real round trip: •Selo paid in round 65454635 •Selo then paid ORA gate in round 65454637 The order is right there on chain.Selo is listed in Bazaar and on the x402 global challenge leaderboard @ganainmtech @algodevs

It passes through five checks and one release gate •Handshake: is your 402 valid? •paid delivery: pay, then get the resource ? •Response contract: it gives the status, type and schema •Discovery: does your bazaar listing match? •Retry: does a replayed payment charge twice

It’s an x402 orchestrator: 1. you pay Selo (1 USDC) 2. only after that settles, Selo then pays your endpoint as a real x402 client 3. you get a report with both transactions Selo never spends before it’s been paid, it treats a payment interaction as a release contract.

Selo is CI for x402 on @Algorand blockchain. before you ship a paid endpoint, Selo makes a real capped mainnet payment to it as a genuine client, checks what happens and returns a 𝐏𝐀𝐒𝐒/𝐅𝐀𝐈𝐋/𝐈𝐍𝐂𝐎𝐍𝐂𝐋𝐔𝐒𝐈𝐕𝐄 verdict backed by on chain evidence #x402

Every x402 endpoint can pass a health check and still break the moment a real buyer pays: wrong asset in the 402, paid but not delivered, a retry that charges twice. We built 𝐒𝐄𝐋𝐎 to catch that before users do. Selo : useselo.xyz Repo:github.com/Enoch208/selo 🧵