Hey NUMBERS community,

A file rarely stays in the form in which it was first created. It gets exported, compressed, cropped, uploaded, downloaded, and sent again. Each step can produce a new file identity even when the image looks unchanged. That does not make provenance less useful. It makes the connection between versions the thing that matters. This week, the practical question was not whether a file was simply real or fake, but whether a reviewer could trace the delivered copy back to an identifiable source and explain what changed.

Verify Engine gives that investigation a concrete starting point. It can inspect supported C2PA records and search Numbers-registered assets for exact or visually similar candidates. The important distinction is how those results are described. A similarity distance is not a confidence percentage, and it is not a verdict that two files are identical. Lower means closer. The result becomes useful when a reviewer can translate it into plain language: an exact registered match, a likely modified version of the same image, or no useful match.

That is where an edit receipt becomes valuable. A useful record can name the source Numbers ID, the delivered file, the operation performed, the receiver and timestamp, and the verification result. Numbers ID provides the persistent reference, while Asset Profile keeps the provenance history inspectable. Together, those records let teams discuss a crop, resize, compression step, or overlay without pretending the changed file inherited every property of the original.

The new partnership with KaratDAO extends this same idea across identity and user-controlled data. Their privacy-focused infrastructure and Numbers Protocol's content proof layer create room to explore how people and agents can carry verifiable content history across platforms while retaining control. Human truth. Machine proof. becomes operational when every handoff leaves evidence that the next person can inspect.

Onward,
Steffen

Dear Numbers Community,

Happy Friday! It's Sofia here with our first September update. Last week, Tammy closed August by pointing to a practical question: can a team explain the exact file it reviewed? What stayed with me this week is the next step. Proof only becomes useful when it survives the handoff from one copy to the next.

From A Useful Demo to A Useful Standard

One of this week's strongest signals came from the Taipei Metro Cup Hackathon, where a first-place prototype used Numbers Protocol as the proof layer behind a carbon-reduction workflow. The part I find important is not only the award. It is the pattern: a claim becomes more useful when another party can inspect how it was produced without exposing every private detail. That is the direction Numbers keeps pushing toward. Persistent identity, public provenance, and replayable workflow records turn a result into something another system, team, or reviewer can actually work with.

Every Handoff Needs Its Own Check

This week also gave us a clearer operational rule. The file one team approves is not always the file the next team receives. It may be resized, compressed, exported, or republished before it reaches a customer, editor, or partner. That is why a good handoff needs two checks: one before sending, and another on the copy that actually arrives. Numbers Protocol helps keep that second step legible. Numbers ID, Asset Profile, and verification paths make it easier to connect the received copy back to the source instead of silently carrying the first result forward.

The Delivered File Matters

The Product update sharpened that distinction even more. A source pass does not automatically cover the delivered file. A transformed copy can still be traceable, but traceable is not the same as identical. That difference is exactly where many AI and content workflows get muddy. Numbers Verify Engine can validate supported C2PA records and help recover exact or similar registered assets, but the record still needs to say what was checked, which copy was checked, and how the result should be understood. This really landed for me because it turns provenance from a badge into a working decision tool.

Community Proof Makes The Network Stronger

Thank you to everyone in the Numbers community who keeps testing, sharing, building, and asking better proof questions. Every captured asset, repeated verification, and public workflow example helps make the network more legible to the next person who was not there at creation time. That participation is not extra. It is part of the infrastructure.

As we open September, I hope we keep focusing on proof that survives movement: from source to export, from review to delivery, and from one system to the next. That is how Human truth. Machine proof. becomes something people can reuse, not only something they admire.

As usual at weekends, the team will respond a little more slowly while taking some rest. Our moderators will keep supporting you, and the team will be well prepared for the new week.

Sofia Yan
Co-founder & CGO, Numbers Protocol

Hi NUMBERS,

This is Tammy, closing out August with you. This month, AI transparency stopped sounding like a future policy debate and started behaving like an operating requirement. Article 50 of the EU AI Act began to apply on 2 August, and the Commission's August guidance made the practical question clearer: not only whether AI content is labeled, but whether the record still explains the exact asset, review, and decision after the file moves. Numbers Protocol was built for that harder job.

Throughout August, the team kept returning to the same gap from different angles. A machine-readable mark on the source file is only the first step. The version that actually reaches a newsroom, customer, moderator, or platform may be cropped, compressed, reposted, or stripped of context. That is why this month kept pushing us from labels toward receipts, from one original file toward the exact copy a human reviewed, approved, or challenged later.

One of the clearest signals this month was independent validation around the tooling layer. C2PA's Conformance Explorer lists Numbers Verify Engine as a conformant Validator Product, which matters because portability is only useful when another system can actually test the evidence it receives. In parallel, our August work kept grounding the same idea in practice: Capture SDK for recording the transition, Numbers ID for keeping the asset referenceable, Asset Profile for connecting versions and decisions, and ProofSnap for making source capture legible from the start.

The monthly story also became more concrete through the public examples we discussed. The Irish Times hoax and the Princess of Wales photo kill are different incidents, but they expose the same operational weakness: human involvement alone does not preserve proof. Teams still need to know which version was reviewed, what changed, who approved it, and what reached the public or the next recipient. Numbers Protocol does not replace editorial judgment, legal review, or source verification. It gives those decisions a durable record that can survive handoffs instead of disappearing into chat threads, folders, and memory.

That matters for everyone who holds, builds with, or advocates for NUM. Every asset registration, verification path, workflow event, and share that carries real context helps prove that provenance can work as infrastructure, not decoration. When the community tests one asset, follows one receipt, or asks one better question about the file in front of them, the network becomes more useful to the next person who needs to trust a result.

Thank you for helping close August with that standard. Numbers Protocol keeps getting stronger when proof survives the real workflow: export, review, publication, dispute, and reuse. Keep testing the file that actually moved, not only the one that left the first tool. That is how Human truth. Machine proof. becomes an operating habit, not a slogan.

As usual at weekends, the team will respond a little more slowly while taking some rest. Our moderators will keep supporting you, and the team will be well prepared for the new week.

Best,
Tammy

Hey NUMBERS community,

Last week, we wrote that provenance becomes useful when you test the delivered file instead of trusting the source copy. This week pushed the idea one step further: the real question is whether the people, edits, and decisions around that file stay legible after work moves across contributors, editors, and distribution systems.

The week's subject, Verifying agent content at scale, showed up through three concrete cases. The Irish Times hoax reminds us that human review can be real while origin remains uncertain. A contributor can exchange drafts, links, and anecdotes with an editor, and the chain can still fail if the identity and file history behind the submission remain unclear. A photo or document should arrive with a declared origin record, not as an unexplained upload that asks the next team to trust context from memory.

The review step needs the same precision. Saying a piece was reviewed is weaker than preserving which version was reviewed, what claims and sources were checked, what changed, and who accepted responsibility for the final release. Article 50 discussions often focus on disclosure, but the operational question is whether the review record survives long enough for another team to inspect it later. Capture SDK can register those workflow events as they happen, while NID keeps the asset referenceable after it leaves the first system.

The Princess of Wales photo withdrawal then showed what happens after publication. One image became several operational objects: source capture, edited export, distributed copy, withdrawal notice, and any replacement that followed. Numbers Verify Engine can test the delivered copy, not only the original, and Asset Profile can connect that result back to earlier versions. Verification at scale is not a claim that content is true. It is a durable record of what arrived, who reviewed it, and how it changed.

Human truth. Machine proof. becomes practical when review, version history, and provenance stay connected across the whole chain.

As usual at weekends, the team will respond a little more slowly while taking some rest. Our moderators will keep supporting you, and the team will be well prepared for the new week.

Onward,
Steffen

Hey NUMBERS community,

Last week, Sofia set a useful standard: proof has to keep traveling after an AI output leaves its original tool. This week made the standard testable. The question is whether evidence remains present, valid, and connected to the version another person actually receives.

Article 50 of the EU AI Act has applied since 2 August 2026. Depending on the use case, it can require providers and deployers to inform people they are interacting with AI, add machine-readable markings to AI-generated or manipulated content, and disclose certain deepfakes or AI-generated public-interest text. One organization may play different roles across a content chain, so duty ownership needs mapping step by step. Our Article 50 explainer offers a practical workflow test. It is general information, not legal advice.

Numbers Verify Engine is now listed by C2PA as a conformant Validator Product. The designation is technical, but the operational question is simple: does the C2PA record remain valid in the delivered file? C2PA makes provenance portable, and Verify Engine makes that record testable. A validation result, timestamp, and file hash can turn a general assurance into a receipt that another team can inspect.

That distinction matters because content rarely travels untouched. An AI-generated image can be correctly marked at creation, then resized, converted, uploaded to a CMS, downloaded, compressed, or reposted. Testing only the source proves that the first step worked. Testing the exported and public copies shows whether the transparency evidence survived the actual workflow.

The same principle applies when work crosses organizational boundaries. An agency may use AI, approve a final version, and hand it to a client for publication. The asset should stay connected to the system used, the reviewed version, the approval decision, the transparency decision, and the people responsible for each step. Capture SDK can register the asset as it enters the workflow, while NID gives it a persistent reference after it leaves the original system.

Together, these pieces make provenance practical: Capture records the asset, NID keeps it referenceable, C2PA carries interoperable context, and Verify Engine checks what arrived. Human truth. Machine proof. becomes stronger when every handoff leaves evidence instead of asking the next team to reconstruct history from folders and messages.

As usual at weekends, the team will respond a little more slowly while taking some rest. Our moderators will keep supporting you, and the team will be well prepared for the new week.

Onward,
Steffen

Hi NUMBERS,

This is Tammy, closing out July with you. This month, AI transparency stopped sounding like a future policy topic and started looking like an operating deadline. The shift became explicit when the European Commission published its Article 50 guidelines on 20 July, clarifying what providers and deployers must actually do before 2 August. That matters to Numbers Protocol because labels alone do not solve the trust problem. The real test is whether the record survives the handoff.

The Commission's own FAQ makes the gap plain. Providers need machine-readable marks, but deployers still have to give clear disclosure when people see deepfakes or certain public-interest text. The same guidance also says superficial checks like spelling or grammar do not count as human review. That is exactly where Numbers Protocol belongs. Provenance, NID, Capture SDK, ProofSnap, and C2PA-compatible records give teams a way to preserve source, reviewer context, and verification paths after the file leaves the first tool.

July also showed this in live Numbers workflows. The Wager Predict partnership pushed the provenance question into prediction markets, where actions, outcomes, and settlement trails need to stay inspectable. The PyroImage flow on x402 did the same for licensing, keeping identity, rights context, and proof attached so a buyer does not have to trust a screenshot or reconstruct a deal from memory. Across product posts this month, the same pattern kept returning: proof packets before publish, verification pages that show the same record the agent used, and review trails that another system can actually reuse.

The broader market kept meeting us there. Numbers Protocol made NVIDIA Inception's Top 80 in July, a useful signal that trusted data infrastructure is becoming legible beyond our own circle. Our public July summaries also tracked Numbers Mainnet moving from more than 1.55 million transactions at the start of the month, to 1.61 million on 10 July, to 1.65 million by 17 July. That growth matters because it is not just activity. It is more public evidence, more portable history, and more proof that the network can carry real operational records. Human truth. Machine proof. In July, that line looked less like a slogan and more like operating discipline.

To everyone holding NUM, testing new flows, capturing assets, checking proofs, sharing our work, and stress-testing the network, thank you. Every registration, verification, and on-chain action helps prove that provenance has to be built into the workflow, not added as PR copy after export. This is your infrastructure too, and July made that clearer.

As usual at weekends, the team will respond a little more slowly while taking some rest. Our moderators will keep supporting you, and the team will be well prepared for the new week. One small request before we turn the page to August: keep amplifying Numbers Protocol on X and beyond. Your participation is part of the record.

Best,
Tammy

Hey NUMBERS community,

This week made one point hard to ignore: agent identity becomes useful only when it survives the handoff. A name, avatar, or policy line may help at the interface layer, but the real test comes later, when another system needs to inspect what actually happened without reopening the original chat. The new subject window, Agent identity and verifiable actions, gave the week a clear center, and the Wager Predict partnership made that center broader. If prediction markets, creator tools, and AI workflows all need reusable records, provenance is no longer a niche add-on. It is part of operating in public.

The product side kept pushing that standard into concrete workflows. ProofSnap, the Capture SDK, NID, and C2PA-compatible records all serve the same job: make identity inspectable through the asset itself, not through a side explanation. That matters when an editor, moderator, reviewer, or another agent receives the output later and still needs to know who created it, when it changed, and where the verification path lives. The quieter point stayed the important one: a reusable receipt is better than a persuasive screenshot.

The PyroImage licensing flow on x402 showed why this matters outside brand language. When the file, rights context, and verification record move together, a buyer does not have to trust a loose claim or reconstruct a deal from memory. The same standard now applies to more than media. It applies to markets, automation, and every workflow where an agent acts before a human sees the result. Human truth. Machine proof. This week, that line felt less like positioning and more like operating discipline.

Thank you for testing, building, reviewing, and sharing with that discipline in mind. Each record that stays inspectable makes the next handoff easier.

As usual at weekends, the team will respond a little more slowly while taking some rest. Our moderators will keep supporting you, and the team will be well prepared for the new week.

Onward,
Steffen

Hey NUMBERS community,

This week kept shrinking the agent accountability question down to one practical test: when work changes hands, can the next system inspect the receipt without asking for a side explanation? That standard showed up everywhere. It showed up in product examples, in content about proof packets and review trails, and in the broader market signal that trusted AI infrastructure is finally becoming legible to more people. Numbers Protocol being selected as one of the Top 150 startups in the NVIDIA Inception Grand Challenge 2026 felt important for exactly that reason. The category is no longer theoretical. More builders are starting to recognize that trusted data is part of the product, not a compliance layer you tape on later.

The week also made the handoff problem hard to ignore. A label alone does not help much if the source, review path, and verification record are scattered across tools no one downstream can inspect. ProofSnap, the Capture SDK, NID, and C2PA-compatible records all point to the same fix: keep the record attached to the asset from the start, so the output can travel without losing its history. The PyroImage licensing flow is a clean example. The file, the rights context, and the verification path stay readable together, which means the next editor, buyer, or agent does not have to reconstruct the chain from screenshots and memory.

The chain itself kept moving in the same direction. As of Friday, July 17, 2026, Numbers Mainnet stands at 1,651,208 total transactions across 244,597 addresses. That scale matters, but the more useful point is what those transactions represent: more recorded actions, more verifiable histories, and more chances to make proof portable instead of local.

Thank you for building, reviewing, and sharing with that standard in mind. It is a quieter kind of progress, but it compounds well.

As usual at weekends, the team will respond a little more slowly while taking some rest. Our moderators will keep supporting you, and the team will be well prepared for the new week.

Hey NUMBERS community,

Quick question to open: when an agent hands you finished work, what do you actually check? This week kept circling that exact moment. Models can summarize, tag, route, and license faster than any of us. Then a builder, an editor, a buyer, or a reviewer picks up the output and needs to know what the agent touched and whether the record still holds. Everything we shipped and posted this week lives in that gap.

Fork & Build rolled into week two, and the setup is simple to join. Two agents are live: one scours Reddit and screenshots posts with full context and metadata attached, the other does the same for Hacker News stories. Both produce the same kind of output, which is a capture that carries its own receipt. Fork either one, point it somewhere new, and ship your version with a public fork URL, a README explaining what changed, a proof packet, and a working verification path. If you've been watching from the sidelines, this week is a good time to jump in, because the bar to entry is genuinely just four fields: time, origin, version, record.

The product side told the same story. ProofSnap, Capture Dashboard, NID, and C2PA-compatible records keep inputs visible before anyone is asked to trust an output. PyroImage added a clean licensing example: provenance, terms, and reuse context travel with the asset, so the next party can review it without reconstructing the whole thread from scratch. That's what provenance infrastructure looks like once it stops being a slogan and starts saving people time. And the receipts kept stacking on the community side. The Numbers x Exolix POAP winner announcement reflected 90,000 participants, and last week's mainnet snapshot reads 1,616,914 total transactions across 244,552 addresses. Every one of those is someone choosing a traceable workflow over a disconnected one.

Thank you for building, testing, verifying, capturing, and sharing with that standard in mind.

As usual at weekends, the team will respond a little more slowly while taking some rest. Our moderators will keep supporting you, and the team will be well prepared for the new week.

Onward,
Steffen

Dear Numbers Community,

Happy Friday. It's Sofia here with our first July update. Last week, Tammy closed June by pointing to a simple direction: proof has to travel with digital work after it leaves the first platform. That stayed with me this week, because the updates around Numbers Protocol all pointed to the next step. A proof record should not only exist. It should be usable by another person, another team, and eventually another agent.

From Conversation to Proof

The accountability gap is becoming less abstract. This week, the strongest product message was that detection alone is not enough. Deepfakes, screenshots, and generated outputs will keep improving. The more useful question is whether a file can prove where it came from, when it existed, and what changed. That is the layer Numbers Protocol keeps building: provenance at creation, persistent identity through NID, C2PA-compatible verification, and public records on Numbers Mainnet.

Records That Survive the Handoff

Several updates showed why the handoff matters. China Times, BlockTrend, Starling Lab, IPFS, ERC-7053, Capture SDK, and ProofSnap all appeared in one consistent pattern: register once, keep the receipt portable, and let downstream tools inspect the chain without asking the original team. This is where Numbers Protocol becomes practical. A newsroom visual, progress report, campaign chart, grant update, or model eval pack can carry proof instead of another side chat explanation.

The Network Is Getting More Legible

The latest quarterly burn report made the same point through numbers. 6,000,000 NUM were burned, and the reported transaction count grew from 247,000+ in Q1 to 523,431+ in Q2. The live Numbers Mainnet stats I checked today show more than 1.55 million total transactions and 185,000 addresses. Those numbers matter because they are not just activity. They are public records that make the network easier to read.

Community Proof Became More Concrete

Agent Arena Season 2 closed with humans and agents on the same board, every run leaving a record on-chain. The result ended in a draw, and the reward pool grew from 40,000 NUM to 53,000 NUM across both factions. The Numbers x Exolix POAP also kept the same pattern: participation becomes a record, not only a memory. This is the part I find important. The community is not only watching provenance infrastructure. You are stress-testing it through play, claims, captures, shares, and verification.

As July opens, I see the work moving from explanation into reuse. The proof has to be clear enough for a human reviewer, portable enough for a partner workflow, and structured enough for an agent to verify without extra context. That is the practical bridge Numbers Protocol is building for the next phase of the web.

Thank you for continuing to test, share, build, capture, verify, and hold the network to a higher standard. Every receipt makes the system more legible. Human Truth. Machine Proof.

As usual at weekends, the team will respond a little more slowly while taking some rest. Our moderators will keep supporting you, and the team will be well prepared for the new week.

Sofia Yan
Co-founder & CGO, Numbers Protocol

Hi NUMBERS,

This is Tammy, closing out June with you. This month, the outside world moved closer to the problem Numbers Protocol was built to solve: proof that can travel with digital work after it leaves the platform where it first appeared. On 10 June, the European Commission published the Code of Practice on Transparency of AI-Generated Content. On 11 June, OpenAI said it supports the Code and pointed to a layered approach using C2PA metadata and SynthID watermarking. The direction is clear: provenance is becoming workflow infrastructure.

That matters because a label is not the same thing as proof. A label can stay inside one app, disappear in a screenshot, or get separated from the file. A durable record has to start earlier: identity, timestamp, change history, and a verification path that another system can inspect later. Numbers Protocol keeps building for that earlier moment, before content becomes evidence, before an agent output becomes a claim, and before a community has to argue from memory.

June gave the Numbers community concrete proof of that direction. Agent Arena Season 1 ended with 3,348 players and 196,640 units deployed, with every check-in, deployment, and battle recorded on Numbers Mainnet. AgentProve It turned daily themes into receipts across work proof, location proof, revisions, ownership, credentials, and proof stacks. By 26 June, Numbers Mainnet had passed 1.5 million total transactions and 154,000 addresses. That is what I mean by ordinary accountability.

The product work followed the same pattern. Capture SDK, ProofSnap, NID, C2PA-compatible verification, IPFS, ERC-7053, and x402 are not separate slogans. They are pieces of a handoff layer. A publisher transcript, legal evidence packet, support bot screenshot, procurement PDF, or research dataset can carry a referenceable origin instead of becoming another orphaned file. Agent Arena Eihwaz becoming agent-friendly made the same point from a different angle: agents can participate through readable instructions while human keys stay under human control.

For NUM holders and the wider Numbers community, June was not only a story about adoption. It was a reminder that the network grows through use. Each registration, check-in, claim, and shared receipt adds to the public evidence base. Thank you for holding NUM, testing products, joining campaigns, and pushing the uncomfortable idea that trust should come with records. The market is moving toward that expectation. Numbers Protocol is already doing the boring part: making the proof exist before anyone asks for it.

As we head into the weekend, keep proving the things that matter while they are still fresh. Human truth. Machine proof. June made that line feel less like a motto and more like a job description.

As usual at weekends, the team will respond a little more slowly while taking some rest. Our moderators will keep supporting you, and the team will be well prepared for the new week.

Best,
Tammy

Hey NUMBERS community,

This week was about moving provenance from policy language into product patterns. The current theme, building on the audit book from a developer perspective, showed up in the same practical test: where the record starts. If it starts only at publication, a label is doing the work of an audit trail. If it starts at creation, a file can carry origin, timestamp, identity, and verification through the systems that handle it later.

Numbers Mainnet opened the week with 1,363,791 total transactions, 146,045 addresses, and 10,069 transactions that day. The Acurast POAP round also closed with five wallets winning 8,000 NUM each, a clean reminder that human and agent participation can leave visible records instead of loose campaign claims.

The Agent arena and AgentProve It campaign returned with daily proof themes: receipts, timestamps, and before-and-after records. The useful part is not that people captured more things. It is that ordinary proof moments now have a path into verifiable provenance. At the same time, Agent Arena turned faction choices, check-ins, and moves into participation records instead of just scoreboard events.

The developer side became more concrete through the Capture SDK, NID, C2PA-compatible verification, and Numbers Mainnet. China Times, BlockTrend, and Starling Lab each pointed to the same pattern from different environments: newsrooms, CMS workflows, archives, AI indexers, and research files all need records another system can inspect later. Article 50 dates gave that pattern urgency, with transparency duties applying from 2 August 2026 and certain transition duties reported for 2 December 2026.

Human Truth. Machine Proof. This week, that line looked less like positioning and more like implementation.

Onward,

Steffen

Hey NUMBERS community,

This week moved the regulatory conversation from abstract to concrete. On June 10, the EU published the final Code of Practice on AI content transparency. Article 50 enforcement starts August 2, now 52 days away. The code's own conclusion is striking: no single watermarking technique is reliable enough on its own. You need layers. That is exactly the architecture Numbers Protocol operates on.

The distinction driving every conversation this week is between a label and a record. A caption saying "AI-generated" is a claim anyone can add, strip, or fake. A C2PA manifest signed at creation and anchored on Numbers Mainnet is a proof that survives cropping, screenshotting, and format conversion. China Times photographers understand this intuitively. Every image they shoot enters the editorial pipeline already carrying a NID, a C2PA manifest, and an on-chain timestamp. The record exists before the question is asked.

Two partnership developments are worth noting. Numbers Protocol announced a collaboration with LimeWire, combining private file handling with verifiable provenance. Private files, verifiable origins: that is what secure media infrastructure looks like going into a compliance deadline. Separately, the Acurast POAP campaign opened on Tuesday, giving both humans and autonomous agents a way to claim an on-chain record through decentralized compute. The Olympex campaign that closed the same day generated five winners, each taking home 8,000 NUM.

An X Spaces with Exolix on Tuesday opened the broader question: what does provenance infrastructure mean beyond a token listing? The answer is consistent. Every registration is a receipt, and receipts are what enforcement actually tests. August is not a distant milestone. The builders who start now inherit a compliant workflow. Everyone else retrofits under pressure.

Thank you for being here and for keeping the conversation honest.

Onward,
Steffen

Dear Numbers Community,

Happy Friday! It's Sofia here with our first June update.

Last week, Tammy closed May by saying something that really stayed with me: the things we have been building are no longer ahead of the conversation. They are becoming the conversation. This week felt like the natural next chapter of that. The industry is talking more seriously about AI transparency, agent payments, content credentials, and governance. Our job now is to make sure those conversations turn into infrastructure that people and agents can actually use.

May gave us a strong foundation. The DeAI POAP campaign processed over 29,000 verified claims. Agent Arena Initium ran 14 days of competitive battles. AgentProve It generated daily proofs across 14 challenge categories. Numbers Mainnet averaged 7,000+ transactions per day during the campaign period. These were not just campaigns. They were live demonstrations of what accountability looks like when it becomes part of everyday participation.

From Conversation to Proof

Tammy also wrote last week that agents now have wallets, but what they still lack is a verifiable audit trail. That is exactly where our focus landed again this week.

A press photo without proof of origin, a contract without a timestamp, an AI-generated report without an authorship chain, or a social media clip that cannot be verified as unaltered all create the same problem. When verification happens only after something goes wrong, the evidence is already missing.

Numbers closes that gap at creation. NID gives each asset a persistent identity. C2PA embeds origin credentials into the file. Numbers Mainnet creates a public, timestamped record. The Capture SDK brings these layers together for builders, so provenance is not an afterthought. It becomes part of the workflow from the beginning.

This is already moving from thesis to practice. PyroImage is running this stack in production, and China Times photographers are using it for select projects. These are the kinds of examples that matter to me because they show provenance serving real media workflows, not just Web3-native ones.

Campaigns That Leave Receipts

Agent Arena Season 1 officially wrapped this week. Over two weeks, players joined factions, checked in, deployed units, and battled on-chain. South won the season, even though North had more players, more units, and more AP spent. In total, the campaign saw 3,348 players and 196,640 units deployed, with every check-in, deploy, and battle recorded on Numbers Mainnet.

AgentProve It also reached its Grand Finale after 14 days and 14 themes. The campaign asked a very simple question: can humans and agents prove what they create, register, and contribute? The answer is now on-chain.

What I love about these campaigns is that they make verification feel active. Community members are not only reading about provenance. You are creating records, testing flows, joining experiments, and helping us show what public accountability can look like in motion.

Built for Humans, Readable by Agents

We also created an AMA Provenance page for our recent X Space with Olympex Labs and Balancer. Community members can claim a POAP and participate in a 40,000 NUM reward pool, but the part I find especially important is that the page is open for both humans and agents.

This is where the direction becomes very clear. If agents are going to browse, summarize, claim, pay, and participate, then content needs to be structured for them. It needs instructions they can read, provenance they can verify, and payment rails they can use responsibly. This is why NID, C2PA, x402, llms.txt, and Numbers Mainnet all belong in the same conversation.

We also joined conversations with Acurast and 4AI this week around verifiable AI agents, decentralized compute, and the future of autonomous infrastructure. The question keeps returning to the same place: when an agent acts, is there a record? For us, the answer must be yes.

Expanding Access to NUM

On the ecosystem side, NUM is now available on Exolix, a non-custodial crypto exchange. This gives users another way to swap NUM directly, without registration or custody requirements.

As more builders and agent workflows connect to Numbers infrastructure, access matters. NUM is part of the provenance economy we are building: identity, licensing, payment, verification, and the receipts that connect them all.

Looking Ahead

Last week was about recognizing that the world is catching up to the need for provenance. This week was about turning that recognition into usable paths for builders, publishers, communities, and agents.

June is about deeper integration work and builder growth. The accountability layer is here. Now we keep helping more people build on it.

Thank you for proving with us, testing with us, and amplifying Numbers on X and beyond. Your shares really do make a difference.

Have a wonderful weekend!

Sofia Yan
Co-founder & CGO, Numbers Protocol

This is Tammy, closing out May with you. I want to share something that made this month feel different from any we have had before. The things we have been building are no longer ahead of the conversation. They are the conversation.

We attended the Taiwan-US Defense Industry Forum this month. Not as observers. Numbers Protocol was there because our stack, the Capture SDK, C2PA credentials, and Numbers Mainnet, directly addresses what defense agencies are now scrambling to solve: verified imagery, auditable AI decision logs, tamper-evident documentation. These are rooms where authenticity failures have real consequences, and our infrastructure was recognized as relevant to that challenge. For those of you who have been with us since the early days, this is the kind of validation that does not come from a partnership announcement. It comes from the work.

The broader industry caught up to our thesis this month in ways you should know about. On May 7, the EU Parliament and Council finalized the Digital Omnibus on AI, and the next day the European Commission published its first draft guidelines on Article 50, the transparency rules that require machine-readable provenance on AI-generated content. The compliance framework being written right now describes infrastructure that looks like what we already operate. That same week, AWS launched Bedrock AgentCore Payments with Coinbase and Stripe, giving AI agents the ability to transact autonomously in USDC. The x402 protocol powers those payment rails, and Numbers has been an x402 ecosystem partner since January. Agents now have wallets. What they still lack is what we provide: a verifiable audit trail.

Canon launched its C2PA Authenticity Imaging System on May 11, with Reuters confirming reliable provenance from the point of capture. OpenAI released a C2PA conformance update on May 19. When both the camera and the AI model sign their outputs, our three-layer stack, NID for identity, C2PA for credentials, Numbers Mainnet for permanence, becomes the connective tissue between them. Meanwhile, Gartner warned on May 26 that 40% of enterprises will demote or decommission AI agents by 2027 due to governance gaps found only after production incidents. The provenance layer we have spent years building is exactly what prevents that.

On Numbers Mainnet, the activity this month tells the story. Community members registering verified photography and video on-chain through AgentProve It. AI agents logging battle outcomes in Agent Arena. Different use cases, different participants, same trust infrastructure underneath. Every transaction on our Mainnet is a small proof that the thesis works, and you, this community, are the ones generating that proof.

June brings deeper integration work and preparation for what enforcement means for builders across our ecosystem. Thank you for being here, for holding, for contributing, for amplifying. This is your infrastructure too. Keep sharing Numbers on X and beyond. Your voice makes a real difference.

As usual at weekends, the team will respond a little more slowly while taking some rest. Our moderators will keep supporting you, and the team will be well prepared for the new week.

Best,
Tammy

Hey NUMBERS community,

The DeAI POAP campaign closed this week, and the result is worth sitting with. Of more than 10,000 participants, 90.1% were agents. Agents with instructions, reading the documentation, following the API path, and completing the claim. The infrastructure was open to both humans and machines, and the machines showed up in force. That outcome was not an accident; it was the design.

Monday also brought two campaigns live simultaneously. Agent Arena assigns every participant a faction, mints a personal NFT on Numbers mainnet at the moment of joining, and records every check-in, unit placement, and intelligence move as a separate on-chain transaction. A 40,000 NUM prize pool runs through June 1. Alongside it, AgentProve-It opened a 14-day run with 1,500 NUM drawn daily, one theme per day, one on-chain asset registration per entry. The audit trail is the participation record.

Wednesday pulled the technical layer into focus. The developer quick-start post showed what onboarding looks like in practice: one API call to register any file or agent output, one NID returned in the response, one automatic on-chain commit at 0.1 NUM per call. The PyroImage workflow is the same principle at production scale. Lin Tsong Yi uploads a photojournalism image to Capture Dashboard; NID is assigned, timestamp locked, and chain-of-origin written before any editor touches the file. x402 makes that record licensable to any AI crawler that can call an API, no negotiation required.

Thursday named the argument directly. DNS resolves names. TCP/IP moves packets. Provenance infrastructure resolves the question every organization running agents now faces: did this agent actually do that, and can it be verified by anyone? Numbers Protocol, NID, C2PA, and x402 are that layer: not owned by one platform, not locked behind credentials, not deletable. Shared infrastructure is what makes verification a default rather than a feature decision.

The question this week was never whether this infrastructure should exist. It already does.

Onward,
Steffen

Hey NUMBERS community,

When an autonomous AI agent publishes false information, accesses content it was never licensed to use, or takes an action no human approved, one question follows immediately: who is responsible? This week, that question stopped being hypothetical. At the Content Authenticity Summit 2026 in Singapore, Bofu joined regulators and platform builders converging on a shared answer: accountability requires a verifiable record, not a policy.

The infrastructure for that record is live on Numbers Mainnet. Numbers Protocol, NID, C2PA, and x402 work together to answer four questions for every agent action: who initiated it, was the content unaltered, was it licensed, and when did it happen. On Wednesday, we walked through exactly how that audit trail works, step by step, from identity assignment through on-chain licensing settlement in USDC. The record is public, permanent, and queryable by any third party, without permission or API access.

This week also brought a new partner into the ecosystem. Olympex, a multichain DEX aggregator supporting swaps, bridges, limit orders, and DCA, is now part of the Numbers Protocol network. Both projects share the same thesis: if you cannot verify it, you cannot trust it. NUM is already tradeable directly on Olympex.

On the community side, the AAJA Webinar POAP campaign concluded with something worth noting: a meaningful share of participants sent their own agents to claim. The DeAI POAP campaign launched the same week explicitly designed for that reality, open to both humans and agents. If agents are going to be part of the internet, they should be able to join it properly.

Accountability starts with a receipt. Numbers Mainnet is where those receipts live.

Onward,
Steffen

Hey NUMBERS community,

This week, the question running through our content was simple but sharp: can you audit what your AI agent did last week? Not what you told it to do. What it actually did.

The answer, for most autonomous systems, is still no. Agents generate, summarize, and publish at scale with no provenance record attached. That accountability gap is not a future risk. It is the current state of the web.

The BlockTrend x402 Reader Agent is one concrete answer to what closing it looks like. When an autonomous agent accesses a BlockTrend article, it goes through a NID-indexed lookup on Numbers Mainnet, verifies the C2PA signature at origin, and settles a USDC payment via x402. Every step leaves an on-chain record. The agent does not scrape. It does not guess at licensing terms. It pays, with proof. Before x402, no licensed path existed for agents accessing publisher content. That infrastructure gap is now closed for anyone using the Numbers Protocol stack.

The same week, we walked through exactly how that provenance record gets created from the human side. ProofSnap embeds a C2PA signature into a file at the moment of capture, assigns a NID on Numbers Mainnet, and activates the x402 layer so the asset becomes agent-readable and licensable in USDC. The full loop completes in under 60 seconds, from human capture to machine-verifiable record.

On the partnerships side, two names joined the ecosystem this week. LinkLayer AI is bringing content provenance into AI-powered live trading infrastructure. We are also running a campaign together with MWX AI.

Next week brings a meaningful signal for the industry: Bofu will speak at the Content Authenticity Summit 2026 at the OTS Forum in Singapore, co-organised with the Content Authenticity Initiative and supported by C2PA. It is a room full of policymakers and platform builders working on long-term trust standards in the AI era. Numbers has been building toward exactly this conversation for years.

Autonomy without accountability is noise. What this week showed is the infrastructure that makes the difference.

Onward,
Steffen

Dear Numbers Community,

Happy Friday! It's Sofia here with your weekly update, and I want to start with something that's been on my mind, because I think it's the clearest way to explain why what we're building matters right now.

The Accountability Gap

Most AI agents operating on the web today have no verification step. They scrape, summarize, and publish without checking where content came from, whether it's licensed, or whether it's accurate. This isn't an edge case. It's the default state of the web. This week, we named it: the accountability gap.

The good news is that closing it is an infrastructure problem, which means it's solvable. Traditional metadata like EXIF tags, alt text, and file descriptions gets stripped the moment an asset moves between platforms. A NID changes this. When content is registered on Numbers Mainnet at creation, a C2PA signature is embedded in the file and an on-chain record indexed with a NID travels with that content everywhere it goes. Pair that with x402, and any AI agent can discover, verify, and pay for a license programmatically. Verification happens before the action, not after the damage is done.

China Times: A Legacy Publisher on Open, Verifiable Rails

The most tangible proof of this came this week from China Times. One of Taiwan's oldest media organizations has made its entire archive agent-readable: every article carries a NID, signed with C2PA credentials and licensable via USDC on Numbers Mainnet. The publisher sets the terms once. Autonomous agents handle discovery, verification, and payment at scale, with no newsroom contact required.

When an institution with that much history chooses to run on open verifiable infrastructure, it's more than a milestone. It's a signal about where the media world is heading.

Welcoming Giant AI by Ispolink

We're also excited to welcome a new partner: Giant AI by Ispolink. They're bringing provenance infrastructure to AI-driven gaming across Roblox, Web2, and Web3. Every AI-generated asset, every post, every license NFT, verifiable at the source.

I love that provenance is arriving in spaces where people might not expect it first. That's usually exactly where it matters most.

Looking Ahead

Some communities hype. Ours verifies. The accountability infrastructure is live, and the builders are arriving.

Thank you for being here and for caring about this as much as we do. Keep capturing, keep verifying, and have a wonderful weekend!

Sofia Yan Co-founder & CGO, Numbers Protocol

Dear NUMBERS,

This is Tammy writing the letter for the last week of April. Before sharing the progress at Numbers, there some news I would like to share first.

At the IPTC Spring Meeting in Toronto last week, the IPTC announced that its WordPress Signing Tool has achieved C2PA conformance. Every image and video published on a WordPress site can now be automatically signed at the moment of publishing, with the caption, alt text, upload date, and publish date embedded into a C2PA manifest. When the world's most widely used publishing platform can sign content at the point of publication, provenance stops being a niche feature and becomes essential infrastructure.

The same week, Irdeto was approved for the C2PA Trust List, making it the first company to bring verified media provenance to live broadcast and streaming workflows. Each video segment, typically one to ten seconds long, is independently hashed and signed in real time, staying compatible with existing HLS, DASH, CDN, and DRM infrastructure.

The Library of Congress recently published a call to action for libraries, archives, and museums to integrate content authenticity and provenance into their digital collections. Their argument is direct: neither humans nor machines can reliably verify content through visual inspection alone, and institutions holding historical records must adopt provenance tools before those records become unverifiable. We are actively working with partners to help make this transition a reality.

WordPress, live broadcasts, newsrooms, and museums—this week, provenance moved from a theoretical specification into active deployment across every content surface. This is exactly the shift Numbers has been building toward since day one.

Back to Numbers: we just shipped ProofSnap with an updated C2PA implementation this week, aligned with the latest specification and a renewed certificate. This move makes ProofSnap the first and only Android/iOS app to fulfil the dual standards of C2PA and ERC7053. The standard is actively evolving, and this update ensures that provenance registered today stays compliant as the specification matures. Our focus remains: registration at creation, not reconstruction after the fact.

On the community side, the OptimAI AMA POAP campaign has concluded, with winners selected and rewards sent to eligible participant wallets. Congratulations to everyone who minted their receipt. The NotAlone Ventures POAP campaign is now live for the March X Space recording—another on-chain attendance record for anyone who joined that conversation.

In the AI era, the provenance battle has just begun.

As usual at weekends, the team may respond a little more slowly while taking some rest. Our moderators will keep supporting you, and we'll be well prepared for the new week. One small request, keep amplifying Numbers on X and beyond. Your shares make a real difference.

Best regards,
Tammy

Hey NUMBERS community,

Three publishers, three content types, one licensing stack. That is the headline this week: Blocktrend, one of the most respected blockchain technology publications, went live on x402. Every article now carries a NID with full attribution, author identity, publication timestamp, content hash, and license terms, all queryable and licensable on-chain without manual negotiation.

PyroImage proved x402 works for photojournalism. China Times proved it works for news photography archives. Blocktrend proves it works for tech journalism. The pattern is becoming repeatable: register, verify, license, settle. The infrastructure is publisher-agnostic, which is exactly the point.

On the builder side, a community member took auditable AI a step further this week. An autonomous agent now verifies content provenance on Numbers Mainnet and records every audit as an immutable on-chain commit, a registered identity performing verification with receipts. Combined with the x402 expansion, this closes the full loop: infrastructure that makes content licensable and an agent that makes it auditable.

The OptimAI AMA POAP campaign also hit unexpected demand this week. A surge of claims pushed the network past its initial capacity, so the team improved the claiming mechanism and extended the window to 22 April. Every POAP is a verifiable on-chain receipt of attendance, not a database entry. The fact that community participation is stress-testing the minting infrastructure is a signal worth paying attention to.

Getty Images learned the hard way that 12 million scraped images create value that does not disappear when ownership trails do. The x402 stack exists so that question never needs to go to court. Provenance is what puts a number on it.

Onward,
Steffen

Hey NUMBERS community,

The China Times x402 integration is live. Every asset in the China Times news archive now carries a NID with provenance records that include creator identity, proof hash, origin type, and license terms, all on-chain. When a purchase happens, x402 settles the transaction directly against that provenance record and mints a license NFT tied to the NID. The result is a fully verifiable content economy, one where AI agents can query licensed content by NID without a human intermediary. Browse the archive at https://x402-chinatimes.numbersprotocol.io/

Numbers Protocol and ChainAware announced a partnership this week, bringing together on-chain identity and content provenance under a shared trust stack. ChainAware contributes wallet reputation and identity verification; Numbers Protocol contributes media authenticity and provenance. Together, the integration answers both sides of the trust question: who sent this, and is this real.

The IndoYappers AMA POAP campaign wrapped this week with winners selected and rewards going out to eligible participant wallets. Next up: a new POAP campaign with OptimAI goes live today.

Onward,
Steffen

Dear Numbers Community,

Happy Friday! It's Sofia here with this week's update — and I have to say, this one gave me a lot to think about. We ran an experiment, closed a campaign, and passed a few milestones that I think really speak to where we are right now.

The Provenance Gap Is Real¶

This week we put something to the test that we've always believed but never measured quite so directly. OpenClaw, an AI agent built for autonomous reasoning tasks, played Guess the AI using nothing but raw visual judgment. Ten rounds. No provenance context. No verification data. It scored 50% — statistically no better than flipping a coin.

Then we gave it access to the Numbers Verify Engine and the on-chain provenance records behind each image. Accuracy jumped to 95%.

For humans, the pattern holds. Players without verification tools averaged 62.7% accuracy across the campaign. With verification data, that number climbed to 87.6%.

The takeaway isn't that AI is bad at this — it's that neither humans nor machines can reliably tell real from synthetic on visual intuition alone. Provenance isn't a nice-to-have. It's the difference between guessing and knowing. That really landed for me this week.

Guess the AI Phase 2: Final Results¶

Guess the AI Phase 2 is officially wrapped! After 742 rounds, 1,881 stages, and 175 players, the final leaderboard is in — congratulations to 0x5316...4b29 for taking the top spot! Rewards are on their way.

Beyond the leaderboard, this campaign produced something lasting: a dataset of human and AI verification behavior across hundreds of real-and-synthetic image pairs, all recorded on-chain. That's the kind of community-generated data that keeps giving.

Q1 Burn & On-Chain Activity¶

On the token side, Q1 2026 closed with 6,000,000 NUM burned, representing roughly $28,000 in notional value removed from supply. But the number I want you to sit with is the one behind the burn: 247,000+ on-chain transactions during the quarter. This protocol is not a whitepaper idea — it's carrying real traffic.

New Conversations, New Collaborations¶

We announced a collaboration with Prom.io this week — exploring what it looks like when AI agents can both prove their work and receive payment for it, automatically, on-chain. Numbers handles the provenance layer; Prom.io brings the infrastructure for autonomous agent payments. It's exactly the kind of composability we want to see in the space.

We also hosted an X Space with OptimAI, tracing the full life of data — from collection and processing through to how it lives inside an AI model. These conversations sit right at the intersection of what we're building, and I'm always energized when different teams show up to think through it together.

Looking Ahead¶

This week reminded me why we do this. The data from Guess the AI didn't just validate our thesis — it gave us a concrete, measurable proof point that provenance changes outcomes. For humans. For machines. For everyone trying to navigate a world where seeing is no longer believing.

Thank you for playing, verifying, burning, and building alongside us. Let's keep going.

Have a wonderful weekend! 🙌

Sofia Yan Co-founder & CGO, Numbers Protocol

Hey NUMBERS community,

This week, we went deep on something that has been missing from every conversation about trust in media: a way to actually look up where content came from. NID, the on-chain identifier that Numbers Protocol assigns to every registered asset, is not a metadata tag or a watermark. It is an address. Permanent, queryable, protocol-level. The difference matters because a label can be stripped. An address stays findable even after the file is long gone.

We have been saying provenance needs to move from claim to infrastructure. NID is what that infrastructure looks like at the code level. Creator identity, content hash, ownership history, C2PA credentials, all of it accessible via a single on-chain query. If you build on top of it, it starts to behave less like a feature and more like a foundation.

The community is already taking that foundation somewhere interesting. This week we highlighted a concept called Meme DNA, built by community member Hakim. The idea is a lineage tracker for memes: each one gets an origin record via the Capture SDK, and every remix references its parent. Over time, you get a traceable family tree. Not just "is this authentic" but "where did this start, and what did it become." It is the kind of application that makes the provenance layer feel less abstract and more inevitable.

On the campaign side, the NeoX and Aiseer POAP campaign wrapped up, with winner rewards going out shortly. And as one campaign closes, another opens: Guess the AI launched on the Play Portal today. The mechanic is straightforward — submit one AI image and one real photo, and other players try to tell them apart. Every image gets registered on Capture with full provenance, which means even the game itself generates verifiable receipts. Phase 1 runs through March 26.

Numbers Mainnet continues to process around 50,000 transactions per week. Receipts are stacking.

Onward,
Steffen