Numbers Protocol

This account is verified because it's an official organization on X. Learn more

@numbersprotocol

Numbers Protocol makes it impossible to lie about where content came from.

Internet numbersprotocol.io Joined February 2019

691 Following 163K Followers 5K Posts

Latest posts 5

Pinned post

Numbers Protocol @numbersprotocol 6d

A designer finds a campaign image through its Numbers Asset Profile.

That helps answer one question: which asset are we dealing with?

The next question is whether the planned reuse is actually covered by the recorded terms.

Keep these four things together:

1. The asset's Numbers ID and the version being delivered.
2. The recorded license or terms, plus when they were checked.
3. The intended use: channel, audience, duration, and any planned edits.
4. The permission evidence, including anything still unresolved.

An image approved for an internal client presentation, for example, may not automatically be cleared for a paid advertisement.

Asset Profile makes the recorded source context and license information easier to inspect. It does not decide whether every new use is permitted.

Identify the asset. Check the terms. Compare them with the actual brief. Record any gap before delivery.

Inspect an Asset Profile:
docs.numbersprotocol.io/applications/v…

Numbers Protocol @numbersprotocol 1d

An agency delivers five images with one message: "These are cleared."

The receiving side needs more than reassurance. It needs to know what "these" actually covers.

Each delivered image should stay connected to its source reference and the permission evidence that applies to it. If several assets share the same terms, they can point to the same document, but it should still be clear which files those terms cover.

Exceptions matter too. One image may be cleared for editorial use, another may still need logo approval, and a crop may require a separate check.

Those differences should be visible in the handoff, not buried in filenames or old messages.

One delivery can contain five assets with five different permission states.

Make it possible to inspect each one without guessing what "cleared" meant.

Numbers Protocol @numbersprotocol 2d

A designer crops a licensed photograph for a banner.

The source reference still points to the original. The file being delivered is now the crop.

Both need to stay visible in the handoff.

Keep the original source reference connected to the delivered version, the intended placement, and the permission evidence relevant to that edit and use.

A visual match can help recover the source. It cannot explain what changed during production or whether the new placement is covered by the original terms.

That relationship should be recorded before the exported file becomes the only thing left.

**The reviewer should be able to trace the delivery back to its source without confusing the two.**

Numbers Protocol @numbersprotocol 4d

A studio receives permission to use an image. Before the production folder fills with crops, resizes, and campaign exports, that original can be registered with the Numbers Registration API.

Registration gives the source a Numbers ID and makes its Asset Profile available, creating a clear reference point for everything that follows.

Keep that NID with the original file and the permission record. When a new version is delivered, identify that version separately rather than treating the source NID as an identifier for every export.

Registration helps establish **which source the work started from**. It does not grant a license, confirm every right held by the uploader, or automatically record what happens later in production.

The handoff should still connect the registered source, the permission evidence, the delivered version, and the intended use.

And storage is a separate decision too. The current Registration API documentation says the initial IPFS pin is available for one month, with longer-term storage handled separately.

**Register the source before the versions start multiplying.**

docs.numbersprotocol.io/developers/ini…

View quoted post on X

Numbers Protocol @numbersprotocol 3d

Sofia's Weekly Summary.

A useful handoff connects the registered source, the intended use, and the permission evidence before versions multiply.

Build a handoff others can inspect.

Read the letter:
docs.numbersprotocol.io/introduction/w…

docs.numbersprotocol.io 6 Nov 2026 - Numbers Protocol Docs 6 Nov 2026 - Documentation for Numbers Protocol - The Decentralized Provenance Standard

Numbers Protocol @numbersprotocol 4d

A studio receives permission to use an image. Before the production folder fills with crops, resizes, and campaign exports, that original can be registered with the Numbers Registration API.

Registration gives the source a Numbers ID and makes its Asset Profile available, creating a clear reference point for everything that follows.

Keep that NID with the original file and the permission record. When a new version is delivered, identify that version separately rather than treating the source NID as an identifier for every export.

Registration helps establish **which source the work started from**. It does not grant a license, confirm every right held by the uploader, or automatically record what happens later in production.

The handoff should still connect the registered source, the permission evidence, the delivered version, and the intended use.

And storage is a separate decision too. The current Registration API documentation says the initial IPFS pin is available for one month, with longer-term storage handled separately.

**Register the source before the versions start multiplying.**

docs.numbersprotocol.io/developers/ini…