Capture

Proof that pays. Make reality investable.｜Powered by @numbersprotocol

[Capture @captureapp_xyz]

7/ If you’re a photojournalist, editor, or supporter who wants frontline work to live beyond a single headline, what would you want to see in a mission-as-RWA model? Reply with your thoughts and follow along as we share more from the field.

#ProofInTheField #CaptureForIP #RWA

[Capture @captureapp_xyz]

1/ Picture a high-risk frontline assignment.
Flights, fixers, insurance, weeks of prep — one photographer or reporter on the ground, burning through budget and energy for a few days of coverage.

[Capture @captureapp_xyz]

6/ This is the world we’re building toward with Capture for IP and The PROOF Challenge: real missions, captured and verified on-chain, designed from day one to reward truth-tellers over a much longer time horizon.

[Capture @captureapp_xyz]

x402 is our “pay gate” for the AI web.
We chose HTTP 402 because it’s:

1. native to bots & APIs
2. composable with existing web infra
3. ideal for streaming small payments to RWA over time

This is the charging front door of our AI business engine.

[Numbers Protocol @numbersprotocol]

The Numbers flow with x402

When something new is created, maybe a dataset, maybe a photo/video, or even a tokenized real-estate, we open a clean page for it. Think “start of the story”: what it is, when it started, who’s behind it.

As things happen, we just… keep writing on that same page. New version? Small fix? Minor addition? It’s all recorded on the exact same page, so the story’s already there.
Anyone who needs to can peek at the page and understand what this thing is, what changed, and when.

Now the part people usually miss: money and permission.
X402 make the payment easier, Numbers provide the receipt, that sticks to the same page.

Example: An apartment building is tokenized. Investors buy fractions; later, the building is leased and generates income.
- When an investor buys a fraction, an receipt notes who bought it, how much, and the timestamp tied to the building’s page.
- When rent is paid out each month, another receipt shows who got how much and for which month.
- If someone rent for 14 days, a receipt records who had access and when it ends.
- If a property manager is granted operating rights for a quarter, the receipt spells out the scope and the dates.

Same pattern works for other things too: a lab renting a dataset for 90 days, a GPU cluster getting paid for job.
All in one page: receipts show up when value was exchanged.

The best thing about this? Because x402 is involved, AI agents can do all of this autonomously.

[Capture @captureapp_xyz]

7/ In the coming weeks we’ll break down a real assignment, from brief to RWA, and show how frontline work can be financed as an asset, not a cost.

If you’re a creator, editor, or AI builder, follow along and tell us: which part of your work feels most underpriced today?

[Capture @captureapp_xyz]

1/ The real problem with AI isn’t that it “steals images.”
It’s that high-risk, high-skill work, like reporting, photography, and creative IP, that gets sold once, too cheaply, while platforms and models keep compounding the value.

[Capture @captureapp_xyz]

6/ Why does this matter?
If we want better AI, we need better inputs. That means paying fairly for verified, on-the-ground work instead of squeezing prices until only the cheapest, noisiest content survives.

[Bofu Chen @bafuchen]

@elonmusk @grok your X employee @alypetru's account hack led to our @numbersprotocol company acct breach. Traces removed from your employee acct post-recovery, but our community remains vulnerable with fraudulent posts. We've alerted support—can you expedite? #XSecurity

Here are the blockchain proofs:
1. https://t.co/P6Nx9rkuBO
2. https://t.co/iLWskLJHBY

[Bofu Chen @bafuchen]

Hi everyone – quick heads-up about today’s security incident.

Even with two-factor authentication turned on, our X account (AT numbersprotocol, @numbersprotocol) was compromised this afternoon.

What happened (UTC+8):

1. 13:20 – we attempted to sign in via Google + 2FA (our usual security setup).

2. Immediately afterwards, an email appearing to be from X Support arrived, asking for a Telegram number to “verify ownership.” (see attached photo)

3. We Did NOT share any Telegram details or codes. Conversation stopped there.

4. ~20 mins later we discovered the account had nevertheless been taken over.

We’re now working with X’s support team to regain control and to understand how 2FA was bypassed. In the meantime:

Treat any recent posts or DMs from @numbersprotocol as un-trusted until we regain control.

Do not click links or share personal info if contacted by that handle.

If you need to reach us urgently, please visit our Telegram https://t.co/sldVHTxSPr or email [email protected].

I’m sorry for the disruption. We’ll keep you updated and share what we learn so everyone can stay safer.

Stay vigilant and thanks for your support.

All future official announcements will include a Capture‑signed proof photo (see attached image). Posts without it are unauthorised.

Proof for the photo → https://t.co/n5l96Z4efB

[Capture @captureapp_xyz]

You can follow @bafuchen, founder of Numbers Protocol, or @captureapp_xyz, our product channel, to know the latest progress.

[Capture @captureapp_xyz]

Security notice: Our official @numbersprotocol X account was hacked earlier today.

Please ignore any recent posts or DMs and avoid clicking links. We’re already working with X Support to regain control.

[Capture @captureapp_xyz]

We’ll share updates from this account until everything is resolved.