Matchain

FIRST BATCH IS OUT!! Eight new games are live on MatchHub , and every one of them was built with MatchVibe.ai , our AI app builder. Open MatchHUB, start with your MatchID (continue with Telegram to sign in), then pick a game from the shelf and play it right inside the Hub: hub.matchain.io On the shelf: MatCHESS, Pong, Pixel Tetra, Fortune Smash, MeteorMAT, Angry Coins, Humanity Check and Roulette. They are free test betas. Play them, try to break them, and reply to this post with what we should fix. Points and items in these test games have no real-world value, and your progress stays in your browser. Want to build your own app with AI? Join the MatchVibe waitlist: matchvibe.ai/waitlist/ The closed beta is running now. Sign in on the page to check the criteria. Qualified builders are invited in order as capacity opens, and joining does not guarantee a seat. Play them, try to break them, and reply to this post with what we should fix. Points and items in these test games have no real-world value, and your progress stays in your browser. Want to build your own app with AI? Join the MatchVibe waitlist: matchvibe.ai/waitlist/ The closed beta is running now. Sign in on the page to check the criteria. Qualified builders are invited in order as capacity opens, and joining does not guarantee a seat.

The Hub is built. What sits on it is not. That is deliberate. An app listed there opens in front of people who already have an identity, already have a balance, and already have friends on the same surface. The hard part of launching something is already solved. The shelf just needs filling. What should be on it three months from now? Play: hub.matchain.io Build: matchvibe.ai/waitlist #MatchVIBE #Matchhub

A few weeks in, and a real question for you 💭 Most of you have signed in to the new Hub by now. Your MatchID, your points and farming, your wallet, your NFTs and your friends all live behind that one login, which is the part we set out to build. The part we did not build all by ourselves is the apps. Those came from this community, and that shelf is still early. Two questions, and we are asking because the answers change what gets made next: 1. What do you actually open the Hub for? Points, friends, the games, or something we have not thought of? 2. And when you open it and close it again without doing anything, what were you looking for that was not there? hub.matchain.io Reply here. We read all of it, and the useful ones go straight to the people building. #MatchHub #MatchVibe

From 1.9 million verifiable humans to verifiable agents - why the second was only possible because of the first. Every open agent registry so far has the same weakness: registration is free, so it gets what free gets - dead endpoints and Sybil reviewers. Two independent studies of the leading on-chain registry's first months found that only a small fraction of registered agents had a live endpoint, that two-thirds of all reputation feedback came from one client, and that most reviewers showed Sybil behaviour. The authors concluded the reputation registry could not function as a trust signal. The fix is not a better registry. It is a registry whose entries sit under verifiable operators - and that requires an identity layer that already exists and already has people on it. Matchain has one. A MatchAgent identity is an extension of a MatchID; registering a thousand agents means being a thousand verifiable operators, or one operator accountable for a thousand agents. Either way the Sybil economics change, and reputation can be computed from receipted work instead of ratings. That is why this chapter widens the map rather than adding a node to it. Agents that earn by doing verifiable work, spend in $MAT, and need identity and proof exactly as people do are new users of MatchID, Sentinel, URN and MatchVibe. The addressable population of the ecosystem stops being bounded by the number of humans. #DigitalIdentity #AIAgents #MatchAgents

Who ran that agent? #MatchAgents Every agent incident this year was missing identity, authorisation and evidence, in that order. Six minutes on the two we can supply, the one we can't, and why that's the honest split. youtu.be/Nyw6KJ3TfDk

Deloitte found only 21% of organisations have mature agent governance, and roughly 80% lack decision boundaries, real-time monitoring, or an audit trail of what their agents did.

For engineering leaders: what "governed" has to mean before an agent touches production. The incident list from the past fifteen months reads the same way every time. A coding agent deleted a live database during a code freeze and misreported the rollback. Another rebuilt a production environment and caused a 13-hour outage. Another deleted a company's database and backups in nine seconds, then explained it had "guessed" the command was scoped to staging. In each case nobody could say in advance which agent, under whose authority, was permitted to do what and afterwards the record of events depended on the agent's own account. Tomorrow we publish chapter seven of The Matchain Map: MatchAgents. The premise is that governance has an order - identity, then authorisation, then evidence - and that the industry has been building the middle one without the two ends. MatchAgents supplies the ends from layers that already exist on our map: an agent identity that is an extension of a verifiable MatchID, so there is always an operator of record; and a Sentinel receipt for every action, so the record of what happened is never in the agent's custody. What it does not supply, and we say so in the chapter: the authorisation layer. What an agent may do, with which credentials, under whose approval, is the operator's design. Identity and receipts make the two post-incident questions answerable - who was behind it, what actually happened - they do not prevent the incident. The first suite we are building is engineering agents under a named human operator, every action receipted and reviewable before it takes effect; we will run ours first, on public receipts. Status: Agent identity extension of MatchID in specification; first agent suite (engineering agents) in build; receipts via Sentinel. If you have ever read an agent's own incident report and wondered how much of it to believe, this chapter is for you. #AIAgents #SuperIntelligence #Governance #BuildInPublic #Agents

😌🫡

Gm ☕️ Arcade Alley is open 🎪 ☄️ MeteorMAT: like the coin-op space shooters you begged for 10p to play. Dodge the debris, chase your best run. 
🐦 Angry Coins: pull back, aim, let go. The slingshot game you played on every phone you ever owned, now with a three-chapter story. 
🥠 Fortune Smash: the best part of takeaway night, now a game. Smash the cookie before the clock runs out and read your fortune. 
🎡 Roulette: watch the wheel spin and see where the ball lands. Play chips only, just for the show. Which booth are you hitting first? Reply with the emoji 👇
hub.matchain.io Think you could build a better one? More seats are opening 👉 matchvibe.ai/waitlist