
Backup account of @numbersprotocol Open & decentralized network. Ensure provenance for all digital media created by humans & AI. Powered by $NUM
Web3
Joined January 2024
- Tweets70
- Following162
- Followers116
- Likes374
Numbers - Build in Public retweeted
The Q2 NUM burn is done.
6,000,000 NUM were burned in quarter 2. That’s around $15,000 in notional value removed from supply.
But aside from that, one thing you need to note of:
In Q1, there were 247,000+ transaction
In Q2, we reached 523,431+ transaction
The network doubled in size. More receipts are being printed, shared, and utilized.
medium.com/numbers-protocol/…
Numbers - Build in Public retweeted
DeAI POAP is now closed.
Over 10,000 participated, and you know what? At least 90.1% of it were agents!
Appreciate everyone's participation, the reward will be sent shortly.
Another campaign, the Agent Arena opens tonight. The audit trail continues.
Numbers - Build in Public retweeted
the average AI agent lives for 6 days before someone notices it exists.
in those 6 days it has already published, transacted, and made decisions on behalf of someone.
nobody checked. nobody was notified. nobody signed off.
the word for this in any other industry is liability.
When your agent acts without authorization, who's accountable? That question moved from philosophy to policy at the Content Authenticity Summit this week.
NID, C2PA, x402 = the verifiable answer.
docs.numbersprotocol.io/intr…
Numbers - Build in Public retweeted
Who is responsible when an AI agent acts?
This week, that question moved from philosophy to infrastructure at the Content Authenticity Summit 2026 in Singapore, where regulators, platform builders, and provenance architects gathered to agree on what accountability requires at the technical layer.
The answer they are converging on: a verifiable record. An audit trail that links every agent action to its origin, its authorization, and its data source.
That infrastructure exists on Numbers Mainnet today. NID gives every asset a permanent identity. C2PA signatures confirm integrity at creation. x402 records every licensed access transaction on-chain in USDC. PyroImage, China Times, and BlockTrend have already built on it.
The question is not whether this infrastructure should exist. The question is who deploys it, and when.
The organizations that treat accountability as an afterthought are about to discover it is also a liability.
What would your team need to put in place today to answer the responsibility question with evidence, not explanation?
Numbers - Build in Public retweeted
Guess the AI Phase 2 closes tomorrow, which means this is your last chance to stare directly at synthetic nonsense and call it out for what it is.
Some of you are one good run away from the leaderboard.
Some of you are one bad run away from embarrassment.
Ps: The leaderboard is getting competitive, some of you are taking this too personally and intern loves that!
Guess the AI is live.
Registration is over. 392 image pairs submitted. now it's your turn to spot the fakes.
Here's how it works:
- Spend 1 NUM to play a round.
- You will see 2 images, pick which one is AI-generated.
- Get it right, and you may double the reward by proceeding to the next stage.
- 3 stages per round, 3 rounds per day. Every correct pick counts toward the leaderboard.
- The player with the most correct AI picks at the end wins 10,000 NUM.
- If there's multiple top player at the end of the campaign, winner will be picked randomly.
Sounds easy until you're staring at all the images and none of them look fake, or all of them do. Intern went 4 for 6 on the first round and is choosing to call that a win.
play.numbersprotocol.io/game…
Numbers - Build in Public retweeted
Everyone can FEEL it. AI slop is REAL.
When the web is drowning in generated noise, authenticity becomes a premium. We powers the backbone of the Auditable Web, providing the Proof of Origin for every human creation.
Our service enables partners like China Times to reclaim values. Through the x402 protocol, we prove who made what, and enable the payment and licensing that keeps creativity sustainable.
In a world of noise, certainty is the rarest signal.
Numbers was recently listed in the x402 ecosystem, but what does that mean?
Let's briefly talk about x402: The protocol reviving the long forgotten HTTP 402 "Payment Required" status.
We believe content is more than just data, contents are asset. By integrating x402 we're enabling:
- Machine-Native Payments: AI agents can now license verified media instantly.
- Zero-Friction: No accounts or credit cards. Just a wallet handshake.
- Verified Provenance: Every x402 transaction on Numbers is backed by an on-chain Certificate of Authenticity.
The "Agent Economy" is here, and it’s powered by verifiable data that pays for itself.
Numbers - Build in Public retweeted
No middleman. No 'Trust Me.'
This isn't a pipe dream. This is how PROVENANCE actually works.
Numbers Protocol creates the receipts. Every asset is cryptographically signed at the moment of creation: origin, creator, timestamp.
NOT a label. NOT a text field. A PROOF that cannot be faked.
x402 creates the contract. It tells any AI agent not just where content came from but how it can be used, licensed and paid for. Automatically. Autonomously.
This is the engine behind the Auditable Web.
Numbers - Build in Public retweeted
A sneaker. A rare card. A signed vinyl.
Most people just see “stuff” on a shelf. But the moment you capture and register them on-chain, they become verified real world assets.
Your physical collection has a story, but does it have proof? Unless you capture it, its history relies on trust, not truth.
Numbers bridges the gap by attaching digital provenance to your photos, you create a verifiable digital twin for your physical items.
Ownership: Verified
History: Immutable
Don't let your collection stay offline:
- Snap a photo of your favorite item. (Pro tip: Use ProofSnap or Capture Cam to secure provenance from the very start!)
- Mint it via Capture Dashboard or Capture API to lock in its history.
Share your proof with us!
Start Minting: teapaw.org/numbersprotocol/status…
Want to dig deeper? We'll share a product deep dive tomorrow.
But if you're already a pro, show us what you can do right now! 💪
What’s the most valuable thing in your room right now?
Sneakers? A rare card? A collectible you’d never sell?
These valuables are assets, and when you register the proof, the photo becomes a digital receipt that can travel.
New mini campaign: Turn your valuables into Licensed NFT
How to join:
- Show us a physical good you think counts as RWA (sneakers / cards / collectibles / anything).
- Register it via any Numbers tool (ProofSnap / Extension / Capture / Dashboard / API)
- Mint as a Licensed NFT and list it for 5,000 NUM
- Comment under this post with your asset link.
If you win, we’ll buy your Licensed NFT → you get 5,000 NUM.
Don’t want to mint? You can still join, but if you win, it’s 2,500 NUM (half reward).
Winner selection:
- In your comment, tag Grok and convince Grok why your item is the most “RWA-worthy” entry.
- After the campaign ends, we’ll ask Grok to pick 3 winners based on entries + arguments.
3 winners. 5,000 NUM if you mint. 2,500 NUM if you don’t.
Duration: 24 Feb – 28 Feb 2026 13:00 UTC
Drop your link & comment in this thread!
Numbers - Build in Public retweeted
The Gateway Managing digital assets on-chain shouldn't require a computer science degree.
Capture Dashboard is your command center.
Unlike standard cloud storage, every file you drop here is analyzed, hashed, and prepped for Web3 registration. It’s the bridge between "just a JPG" and a verifiable real world asset.
No code. No friction.
Just drag, drop, and secure your work.
Try it now: dashboard.captureapp.xyz/
Numbers - Build in Public retweeted
The Engine What actually happens when you click "Register"?
On top of "uploading" the file, we inject identity to it.
Our system generates a unique ID (Nid) for your content and anchors its metadata directly onto the blockchain.
This creates an immutable "Integrity Record", the digital DNA that proves who created it, when, and exactly what it is.
Whether you use our Dashboard or build with our tools, the result is the same: Tamper-proof history.
📚 Read the Docs: docs.captureapp.xyz/capture-…
The Gateway Managing digital assets on-chain shouldn't require a computer science degree.
Capture Dashboard is your command center.
Unlike standard cloud storage, every file you drop here is analyzed, hashed, and prepped for Web3 registration. It’s the bridge between "just a JPG" and a verifiable real world asset.
No code. No friction.
Just drag, drop, and secure your work.
Try it now: dashboard.captureapp.xyz/
Numbers - Build in Public retweeted
The Value, the final piece of the puzzle: The Asset Profile.
Once registered, your file is verified and best of all? It's also ready for business.
You can instantly mint a license that carries your copyright terms on-chain. This turns your digital footprint into a tradeable, legally recognized real world asset.
From raw file -> to Integrity Record -> to Monetizable Asset.
Experience the full flow here: dashboard.captureapp.xyz/
The Gateway Managing digital assets on-chain shouldn't require a computer science degree.
Capture Dashboard is your command center.
Unlike standard cloud storage, every file you drop here is analyzed, hashed, and prepped for Web3 registration. It’s the bridge between "just a JPG" and a verifiable real world asset.
No code. No friction.
Just drag, drop, and secure your work.
Try it now: dashboard.captureapp.xyz/
Numbers - Build in Public retweeted
Resharing this because intern genuinely believe this deserves more love!
Hinoki built x402 on Numbers Mainnet and made NUM micropayments look… effortless.
Watch the payment flow in the demo, this is what “pay-per-use” is supposed to feel like.
That was quick!
In response to our X402 announcement, community member hinokitheshibainu0301 built an X402 implementation on Numbers Mainnet using NUM!
X402-Numbers shows how to:
- Accept micropayments in NUM (on Numbers Protocol, not Base)
- Verify payments on Numbers blockchain
- Create immutable commit records
- Prevent transaction reuse
Open source reference for builders: github.com/hinokitheshibainu…
Numbers - Build in Public retweeted
Payment is cool, but what does it have to do with Numbers if we don't include verification as the "trust layer"?
This implementation shows how to verify NUM payments on-chain, write immutable commit records, and prevent replay/reuse.
Open source ref for builders
Numbers - Build in Public retweeted
x402 makes web-native payments practical: request, pay, get access.
But payment alone isn’t the full story. After someone pays, you still need a clean answer to: "What was licensed? Under what terms? For how long? Who paid?"
Numbers plugs into the step that’s usually missing: persistent proof.
After payment, Numbers can issue a License NFT / receipt that records the licensing outcome in a way that’s:
- machine-readable (AI/agents can parse it)
- portable (not trapped in one platform)
- verifiable (anyone can check the receipt)
So the flow becomes:
request → pay via x402 → get access → mint a receipt (License NFT) → verify anytime.
x402 = payment rail
Numbers = receipt + verification rail
Numbers was recently listed in the x402 ecosystem, but what does that mean?
Let's briefly talk about x402: The protocol reviving the long forgotten HTTP 402 "Payment Required" status.
We believe content is more than just data, contents are asset. By integrating x402 we're enabling:
- Machine-Native Payments: AI agents can now license verified media instantly.
- Zero-Friction: No accounts or credit cards. Just a wallet handshake.
- Verified Provenance: Every x402 transaction on Numbers is backed by an on-chain Certificate of Authenticity.
The "Agent Economy" is here, and it’s powered by verifiable data that pays for itself.
Numbers - Build in Public retweeted
Everyone knows Error 404: Not Found. It means a broken link.
But do you know Error 402: Payment Required?
It was reserved in the 90s for native digital payments but sat unused. We fixed it to turn static media into productive assets.
With the x402 protocol, we enable the "Rent/Buy" mechanism for the AI web:
- Search (Find the verified asset)
- Pay (Instant settlement via x402)
- License (Receive on-chain rights)
See this flow in action with PyroImage: x402-pyro.numbersprotocol.io…
P.S. Our team is showcasing this live at @consensus_hk.
If you're there, come say hi.
Numbers - Build in Public retweeted
That was quick!
In response to our X402 announcement, community member hinokitheshibainu0301 built an X402 implementation on Numbers Mainnet using NUM!
X402-Numbers shows how to:
- Accept micropayments in NUM (on Numbers Protocol, not Base)
- Verify payments on Numbers blockchain
- Create immutable commit records
- Prevent transaction reuse
Open source reference for builders: github.com/hinokitheshibainu…
Numbers was recently listed in the x402 ecosystem, but what does that mean?
Let's briefly talk about x402: The protocol reviving the long forgotten HTTP 402 "Payment Required" status.
We believe content is more than just data, contents are asset. By integrating x402 we're enabling:
- Machine-Native Payments: AI agents can now license verified media instantly.
- Zero-Friction: No accounts or credit cards. Just a wallet handshake.
- Verified Provenance: Every x402 transaction on Numbers is backed by an on-chain Certificate of Authenticity.
The "Agent Economy" is here, and it’s powered by verifiable data that pays for itself.
Numbers - Build in Public retweeted
The License NFT: Minting the Deed to the Asset
x402 by itself is a payment protocol. Pay for access, get the content, simple
But Numbers Protocol integrates something more: the License NFT, a digital deed that encodes actual usage rights on-chain.
You're paying for access, permission : specific, verifiable rights to use, display, or monetize the asset.
Here's the difference:
- Traditional payment: You get a file
- License NFT: You get the deed - immutable proof of what you're allowed to do with it
This is how the web should work. Permissioned usage, verified on-chain, no ambiguity about rights.
When you license an asset on Numbers, you're minting the deed itself. Not a link. Not a copy. The actual rights.
Numbers - Build in Public retweeted
When you license an asset through Numbers x402, you don't get a file.
You get a License NFT - the digital deed to the asset.
Here's what's inside:
Your licensed asset (high-quality, verified)
On-chain deed (ERC-721)
Encoded usage rights (what you're permitted to do)
Full metadata & provenance (verifiable by anyone)
Payment for access vs. payment for rights. That's the Numbers difference!
Try it acquiring a license NFT now x402-pyro.numbersprotocol.io
Numbers - Build in Public retweeted
For PyroImage’s photographers and BlockTrend's researchers, the problem is clear: high-quality images and technical analysis are being scraped by AI without attribution or revenue.
The solution isn't a watermark only; but also a License NFT.
By integrating Numbers Protocol x402 solution, these partners are actively "Minting the Deed" to their work. They are embedding licensing terms directly into their files on the Numbers Protocol network. This transforms a static photo or blog post into a smart asset that can negotiate its own usage rights with AI agents.
This is the difference between a file that gets stolen and an asset that gets paid.
PyroImage and BlockTrend are proving that content can remain open while still being protected. For B2B decision-makers, this is the blueprint for monetization in the AI era.
When you license an asset through Numbers x402, you don't get a file.
You get a License NFT - the digital deed to the asset.
Here's what's inside:
Your licensed asset (high-quality, verified)
On-chain deed (ERC-721)
Encoded usage rights (what you're permitted to do)
Full metadata & provenance (verifiable by anyone)
Payment for access vs. payment for rights. That's the Numbers difference!
Try it acquiring a license NFT now x402-pyro.numbersprotocol.io















