Crypto guy @flycrypt

China Times photographers do not upload first and register later. They register at origin. Before any image enters the editorial pipeline, it carries a NID, a C2PA manifest, and an immutable record on Numbers Mainnet. This is done for the sake of professional standard not as compliance checkbox. The EU AI Act changes what "professional standard" means for AI-generated content. Enforcement begins in August. Traceability is no longer optional and will be a liability question. Most AI content pipelines produce no chain of custody at all. That gap does not appear on a balance sheet. It appears in a compliance audit or a legal proceeding where there is nothing to present. The Capture SDK closes that gap behind one API call. The record exists before the content leaves the source. Build it in now, or retrofit it later under pressure.

Numbers Protocol @numbersprotocol

5 days ago

A newsroom publishes a photo. A reader questions it. The editor has no verifiable record of when or where it was taken. That gap has a price. Retracted stories. Lost credibility. Legal exposure. The cost is not the forgery. It is the missing original. Numbers Protocol closes

1 1 14 892 0

The numbers in this post are real. In early 2024, a finance worker joined a video call where every participant, including the CFO, was a deepfake. US$25.6M transferred across 15 transactions. The tool that created these deepfake cost nothing in comparison to the loss. The infrastructure that would have caught the incident also costs nothing, yet it still happens. So cost was never the variable. The fake is automatic. The proof is a choice. This is the only thing that needs to change.

Numbers Protocol @numbersprotocol

3 days ago

a fake earnings report costs $120M in 11 minutes. a deepfake voice call could costs $25M in one phone call. a generated image costs a reputation permanently. the cost of creating all three: $0. the cost of verifying all three at creation: also $0. the only expensive thing is

1 0 18 1K 0

Dear Numbers Community, Happy Friday! It's Sofia here with our first June update. Last month we d multiple campaigns that leave receipts, expanding access to NUM, and more exciting updates! Read the full letter: docs.numbersprotocol.io/introduction/w…

@Eren791000 @Mekselinamek How there is enough distance to stop He got in something element of surprise. But it seems u have no idea Of course father is mistaken instead of hitting the motorcycle driver he should hit him self as a reckless father the kid should be trained by his father how to act in street

Nearly 200 policymakers, platforms, and media leaders gathered in Singapore for the first APAC content authenticity summit of its size. Everyone agreed provenance matters. The open question was how fast it scales. Numbers Protocol showed up with a live implementation, demoed beside Canon, Adobe, and Digimarc, Bofu on the lightning talk stage. While the room maps how to scale provenance, some of the tools already run. Trust is scarce. Receipts help. contentauthenticity.org/blog/reflectin…

Numbers Protocol @numbersprotocol

3 weeks ago

Bofu at OTS Content Authenticity Summit. one slide compared food labels to digital provenance. in 1970 a can showed brand and price. today you expect calories, ingredients, origin. nobody calls that a feature anymore. it is just how trust works. digital content is getting the

4 6 21 1K 0

@AlexMasonCrypto Yes, you are the best chart reader, no one on earth can read chart, BTC created for you just to read, yo should be called a witch, or even future reader. Man plz it’s ur first prediction u did it right from millions of ur wrong predictions. Well done

Content without provenance is a liability. A press photo published without proof of origin. A contract referenced in a dispute with no timestamp. An AI-generated report submitted as evidence with no authorship chain. A social media clip used in litigation that cannot be verified as unaltered. Every one of these is predictable. It is what a system produces when verification is an afterthought. The stack to fix it already exists. NID for identity. C2PA for credentials. Numbers Mainnet for the record. PyroImage and others already build on it. The Capture SDK puts the whole thing behind one integration. So when something goes wrong, you already have the receipt.

Numbers Protocol @numbersprotocol

a week ago

The accountability layer had a week. 1,328,237 total transactions. 75,090 addresses. And yesterday alone: 18,385. Seven-day average is 7,955 a day. The 5,000 daily target has been quietly in the rearview all week. Here's the part that matters: none of these numbers live in a

4 4 19 1K 0

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

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

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

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…

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

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

Every major AI company published a content policy this year. None of them published a content receipt. Policies describe intentions. Receipts prove actions. The distance between those two is where every content scandal starts and where accountability quietly disappears. Numbers Protocol does not write content policies. It writes content receipts. NID records origin. C2PA makes it portable. x402 makes it licensable. ProofSnap handles it in one tap. PyroImage photojournalists already use it. The entire stack is open, verifiable, and does not require anyone's permission to check. The AI industry has tried the policy approach for three years. Content trust has only gone down. Maybe try receipts.

Agents are making decisions your team will be asked to explain. Who authorized that trade? Which model generated that content? When did the agent access that data? If the answer is "we don't know", that is a liability. A paper trail is not optional when agents act autonomously on behalf of organizations. It is the minimum standard for accountability. What a verifiable agent trail gives you: - Proof of action (what the agent did and when) - Proof of identity (which agent, tied to an NID) - Proof of non-tampering (on-chain, immutable) This month is about making that trail standard practice. This week we opened Agent Arena and the Agent Prove It campaign. Both generate on-chain records by default. Verification as public infrastructure starts here. docs.numbersprotocol.io

Bofu at OTS Content Authenticity Summit. one slide compared food labels to digital provenance. in 1970 a can showed brand and price. today you expect calories, ingredients, origin. nobody calls that a feature anymore. it is just how trust works. digital content is getting the same treatment. 90% of online content projected synthetic by 2026. AI models collapse when trained on AI output. human-made content is becoming scarce. scarcity creates value. C2PA writes the provenance label. Numbers Protocol anchors it to an immutable ledger. even after screenshots, re-uploads, metadata stripping. Reuters and Starling Lab use this to keep news traceable. PyroImage and China Times use it to make archives licensable by AI. registered once. verified everywhere.

Verification is not a feature. It is infrastructure. The same way DNS resolves names and TCP/IP moves packets, provenance infrastructure resolves the question: did this agent actually do that? Right now that question has no answer. There is no shared layer. No default record. No agreed-upon trail. Numbers Protocol is that layer. Every agent action registered on NP mainnet is: timestamped cryptographically linked to an identity (NID) permanently retrievable publicly verifiable by anyone This is what public infrastructure looks like. Not owned by one platform. Not locked behind an API. Not deletable. Your agent will act. The question is whether there is a record. mainnet.num.network

Lin Tsong Yi photographs a breaking story. He uploads to Capture Dashboard. From that point, infrastructure takes over. NID assigned. Timestamp locked. Origin registered on-chain. Verifiable by anyone. Nobody at PyroImage had to configure anything for that to happen. One upload, and the photo has a provenance record that outlasts the news cycle. NID is a public endpoint. Any editor, AI agent, or licensing platform can verify the photo's origin without calling Lin Tsong Yi, his agency, or Numbers Protocol. One API call returns creator identity, device signature, and chain of custody. x402 makes the photo licensable: AI crawlers that want to use it hit a payment request, not a wall. The newsroom gets attribution and revenue without negotiating anything. The photographer uploads. The infrastructure runs. Neither notices the other. x402-pyro.numbersprotocol.io

deepfake detectors: 99% accuracy in the lab. in real-world conditions, accuracy drops by up to 50%. detection is trained on what already exists. provenance doesn't need training.