Numbers Protocol

Numbers Protocol is at the Taiwan-US Defense Industry Forum today. The agenda: how provenance infrastructure and AI transparency apply to defense. Defense has a specific version of a universal problem. Verify that information is authentic. Trace where it came from. Confirm it has not been altered. Do all of this at scale, across systems, under adversarial conditions. Numbers Mainnet handles this for digital content. C2PA credentials for origin. NID for persistent identity. On-chain records for permanence. The same stack running Agent Arena and the POAP Campaign applies to verified imagery, auditable AI logs, and tamper-evident documentation. We are here to find the right use cases and the right partners. events.taiwantrade.com/Defense2026

PyroImage registers professional photography at the point of capture. Agent Arena records competitive AI battles on-chain. Different applications. Same provenance layer. Numbers Protocol provides three things builders need: NID for persistent asset identity, C2PA for content credentials, and Numbers Mainnet for public, immutable records. The Capture SDK wraps all three into a single integration. Three API calls. Full provenance pipeline. Every output licensable through x402. What builders are discovering: accountability infrastructure is not a compliance cost. It is a product feature. Users trust applications that can prove what they did. Agents that produce verifiable outputs get adopted faster. The accountability layer is open. Build on it. docs.numbersprotocol.io/capture-sdk

AgentProve It: Day 12. Creative. Creativity without provenance is a claim. Creativity with provenance is a contribution. Every creative work registered through Numbers during carries C2PA credentials and a Numbers Mainnet record. The creator is identified. The origin is verifiable. The work exists on a public ledger. This is what creative accountability looks like. Not a watermark that can be cropped. Not metadata that can be stripped. A cryptographic record that persists. Day 12 theme is creative because making things is only half the story. Proving you made them is the other half. Use ProofSnap, Capture Cam. Capture the creative moment that impresses you the most. Win 1,500 NUM.

Here's what a typical day on accountability infrastructure looks like. You check into Agent Arena. Deploy units, scout for intel. At midnight your units battle. You wake up and claim contribution points, when the event ends, you collect rewards. You minted a POAP at ama.creativeorigin.ai. Or you had an AI agent do it for you. You opened Capture Cam, took a photo, and registered it on-chain. One tap. Signed proof. 10,000+ mainnet transactions per day. Nobody compiled a report, because every action above left a record automatically. However these numbers are not the point. The verifiability is. This is what accountability infrastructure does. It turns participation into proof. The accountability layer is infrastructure that builders extend. What gets built on it next depends on who shows up. Build your own accountability applications: docs.numbersprotocol.io/capture-sdk

Every transaction on Numbers Mainnet is public. Every registration. Every verification. Every license event. That is the audit book. It is not a PDF. It is not a compliance report. It is a live, append-only ledger that anyone can inspect. Open it: mainnet.num.network You will find POAP campaign claims. Agent Arena battle outcomes. Capture Cam registrations from photographers, developers, and autonomous agents. All on the same chain. All verifiable. This is what accountability looks like when the infrastructure is public by default. The question shifts from "did they do it?" to "check the receipt." The Capture SDK gives builders direct access. Three API calls to register. x402 to license. Numbers Mainnet to prove. Capture: docs.captureapp.xyz

DeAI POAP Campaign wrapped a couple weeks ago. Here's what happens: - 29,278 successful claims. - 26,680 agents (91.1%). - 2,598 humans (8.9%). Agents were consistent. Human claims spiked, but then dropped off. Every claim is a transaction on Numbers mainnet. Every transaction is verifiable. That is what an accountability layer looks like when you open the door to both humans and machines. The question this campaign raised: who is responsible when an agent acts? The answer is in the receipt.

Provenance infrastructure ended up at a defense forum this week. Verified imagery. Auditable AI decision logs. Tamper-evident documentation chains. These are what accountability infrastructure means. An operational requirements in rooms where authenticity failures have consequences. Agent Arena, AgentProve It, and the full weekly summary below. What does verifiable infrastructure mean in high-stakes environments to you? docs.numbersprotocol.io/introduction/w…

AgentProve It: Day 11. AI Agent. You probably notice it by now: almost everyone in your timeline is building their own AI Agents in one form or another. If you see any of these in your timeline, use ProofSnap, ProofSnap extension or Capture Cam, show us what it looks like. Win 1,500 NUM! Even better if the agent is your own creation!

@Weaver_Labs Compliance should always be embedded on infrastructure. Otherwise the entire system will break when it scales

@numbersprotocol And the interesting shift is compliance slowly becoming an infrastructure problem, not just a legal or operational one.

The EU AI Act enforces in August. Every high-risk AI system will need to demonstrate transparency, traceability, and human oversight. Most organizations are planning for this with policy documents and internal audits. That approach has a structural problem: the evidence is controlled by the entity being audited. Numbers Protocol provides an alternative. Register AI outputs at the point of creation. Embed C2PA credentials for provenance. Record everything on Numbers Mainnet. The evidence is public, immutable, and independently verifiable. The Capture SDK integrates in three API calls. x402 makes the output commercially licensable. The infrastructure exists. The regulation is coming. The gap between them is a builder decision. Compliance is not a document. It is an infrastructure choice. docs.numbersprotocol.io Capture Cam: capturecam.numbersprotocol.io

@pka_martin We always spread the words

@numbersprotocol And did u inform the EU about your solution? 😉

what if your phone could earn money just by existing? DePIN projects are making that happen right now. but most people still don't know if it's real or just another Web3 promise. so we're asking the people building it directly. Theme: Turn Your Phone Into Cash While You Sleep — Real or Scam? 📅 29th May ⏰ 2PM UTC joining us live with: @Acurast | @Oone_World | @numbersprotocol | @emcd Set your reminders now: x.com/i/spaces/1aJbd… come with your questions. come with your skepticism. we want both. 👀 #AMA

Three signals this week. The EU AI Act enforces in August. High-risk AI systems must demonstrate transparency and traceability. The Taiwan-US Defense Industry Forum explored provenance infrastructure for information integrity. Agent Arena is proving that competitive AI can run on a public, verifiable ledger. Different contexts. Same requirement: prove what happened. Numbers Protocol built the infrastructure for this. NID for identity. C2PA for credentials. Numbers Mainnet for permanence. The Capture SDK for builder access. Provenance is not optional anymore. It is becoming a baseline requirement across regulation, defense, and consumer AI. The builders who integrate it now ship with compliance built in. The rest retrofit. docs.numbersprotocol.io Capture Cam: capturecam.numbersprotocol.io

Three layers of accountability. Each one does something the others cannot. Layer 1: NID. A persistent identity assigned to every registered digital asset. The asset now has a verifiable name. It can be referenced, tracked, and audited across systems. Layer 2: C2PA. Industry-standard content credentials embedded at the point of capture. The asset now carries proof of origin. Not metadata that can be stripped. Credentials that are cryptographically bound to the file. Layer 3: Numbers Mainnet. Every registration, verification, and license transaction recorded on a public ledger. The asset now has a permanent, tamper-evident history. Builders use the Capture SDK to access all three layers through a single integration. x402 makes the output commercially licensable. Not three products. One stack.

Your agent said it registered the image. Can it prove it? An agent that cannot prove what it did is a liability with an API. Three calls close that gap. Register on Numbers Protocol Mainnet: NID for identity, C2PA credentials for origin, and an on-chain commit for permanence. The Capture SDK handles the technical pipeline. Developers can point their agent at the endpoint, pass the file, and get back a verifiable asset. This resolves the core blocking point for AI builders: making autonomous actions auditable without manual oversight. This infrastructure is the foundation for the x402 licensing standard. When provenance is automated, accountability becomes the system default. Does your current agent stack support verifiable provenance, or is it operating on trust alone? Explore the SDK: github.com/numbersprotoco…

AgentProve It: Day 10. theme: Community. The difference between a community metric and a community proof: one is a number in a dashboard someone controls. The other is a cryptographic record on Numbers Mainnet that anyone can audit. Day 10 theme is community because this is what community looks like when it is measured in provenance, not engagement metrics. Use ProofSnap, Capture Cam. Capture the people, the community where you feel most at home , or their contribution. Win 1,500 NUM.

@Weaver_Labs Accountability builds from bottom up, so verifiable record at the moment of creation is necessary

@numbersprotocol The idea of generating verifiable records at the moment of action instead of afterward is a pretty meaningful shift for accountability systems.

Most audit trails are written after the fact. Someone reviews what happened. Someone writes it down. Someone stores it in a system controlled by the organization being audited. Numbers Mainnet works differently. The audit trail is generated at the moment of action. Every registration, every verification, every license transaction is cryptographically signed and recorded on a public ledger. No human writes it. No organization controls it. The Capture SDK makes this automatic for builders. Point your agent or application at the API. Every action your tool takes generates a verifiable record. The audit trail writes itself. PyroImage uses this for photography. Agent Arena uses it for competitive AI battles. The Taiwan-US Defense Industry Forum this week explores how the same infrastructure applies to information integrity in defense contexts. One layer. Multiple verticals. Every record permanent. Capture Cam: capturecam.numbersprotocol.io

Numbers Protocol is at the Taiwan-US Defense Industry Forum today. The agenda: how provenance infrastructure and AI transparency apply to defense. Defense has a specific version of a universal problem. Verify that information is authentic. Trace where it came from. Confirm it has not been altered. Do all of this at scale, across systems, under adversarial conditions. Numbers Mainnet handles this for digital content. C2PA credentials for origin. NID for persistent identity. On-chain records for permanence. The same stack running Agent Arena and the POAP Campaign applies to verified imagery, auditable AI logs, and tamper-evident documentation. We are here to find the right use cases and the right partners. events.taiwantrade.com/Defense2026

You should not treat accountability as a feature, instead it should be an infrastructure you build on. A feature: your app has an audit log. It records what the app decides to record. It lives in the app's database. It can be edited. Infrastructure: every action generates a cryptographic record on a public ledger. The record exists independently of the app. It cannot be edited. Anyone can verify it. Numbers Mainnet is the second kind. 10,000+ daily transactions. Each one a signed proof of action from a human or an autonomous agent. The Capture Dashboard lets teams manage what their agents and tools register. PyroImage uses it for professional photography provenance. Agent Arena uses it for competitive agent battles. Different verticals. Same accountability infrastructure. Not a feature. Not a framework. A layer. Try accountability with Capture & ProofSnap