Passport
0xe1c37e637e…cb950f52
Checked by ChainlinkThe picture's storage is not answering right now. Try again in a minute.
The turtle greenhouse
GeneratedRegistered Sep 30, 2026, 12:00 PM UTCDownload the original
Trust mark
Chainlink's network fetched this picture itself, measured it again, and it matches its passport: 0 of 64 bits apart. Written on Monad on Oct 7, 2026.
Chainlink found no earlier look-alike among the candidates Moolam's search proposed.
Chainlink's check
Checked again, by someone else
Anyone can say a picture is theirs. This part is different: Chainlink's CRE workflow downloaded the picture itself, took its fingerprint again and wrote the result on Monad.
matched
Test run
A test run in Chainlink's simulator
Registered fingerprint Chainlink's fingerprint A Chainlink CRE workflow re-fetched this picture and recomputed its fingerprint: 0 of 64 bits apart.
A test run on one machine, in Chainlink's simulator. It stays in the record and never turns on the mark.
- What Chainlink reported
- 0 of 64 bits apart
- At
- Sep 30, 2026, 12:06 PM UTC
- Written on Monad by Moolam's Chainlink receiver
- 0x4aD66c…Aa95
The first grid is the fingerprint the registry stored when this picture was registered. The second is what the workflow computed from the file it fetched itself. Every cell that disagrees is marked.
matched
Checked by a Chainlink CRE workflow
Registered fingerprint Chainlink's fingerprint A Chainlink CRE workflow re-fetched this picture and recomputed its fingerprint: 0 of 64 bits apart.
Several independent Chainlink machines ran this check and agreed on the answer.
- What Chainlink reported
- 0 of 64 bits apart
- At
- Oct 7, 2026, 10:21 AM UTC
- Written on Monad by Moolam's Chainlink receiver
- 0x0d6905…ff04
The first grid is the fingerprint the registry stored when this picture was registered. The second is what the workflow computed from the file it fetched itself. Every cell that disagrees is marked.
Checked on Oct 7, 2026
How AI may use this picture
A file can carry a line saying its creator refuses AI training, and anyone can strip that line out on the way past. This is the same statement written to a register on Monad, where only the holder of this passport can write it and nobody can take it back out.
In force today
Not for AI training
Oct 7, 2026written Sep 30, 2026, 12:00 PM UTC
The holder refuses all four uses in the standard. This is a choice, not a fault.
No AI use
Drag the day sliderDrag the day slider, or use the arrow keys, one day a step
registered Sep 30, 2026today
The four uses
What stands today, use by use. Every summary loses something, and this is where training and inference are allowed to differ.
- AI trainingNot allowed
- Generative AI trainingNot allowed
- AI inferenceNot allowed
- Data miningNot allowed
- Stated by
- 0x80819a…3F44
- Written on
- Sep 30, 2026, 12:00 PM UTC
Dreamloom stated these terms. They stand until whoever holds the passport states new ones.
One statement
Sep 30, 2026, 12:00 PM UTCstands today
Not for AI training
The record
Checked on chain, and it matched
- Creator
- 0x80819a
894AAa89 e0346b71 5bEb897A 7c2fda3F 44 A key bound to this creator's wallet signed this picture's fingerprint on Monad.
Imagined on Dreamloom. Dreamloom holds this passport until the person who imagined it claims it.
Dreamloom's agent drew the picture and its server key registered it the moment it was made. Moolam checked that Dreamloom holds both keys, not who the company is.
- Where the claim comes from
Drawn on Dreamloom. Its agent signed the picture the moment it was made.
Registered through the platform kit. Dreamloom sent no statement of its own, and a platform's picture is not checked against the web.
- Generator agent
- Agent 10273
Listed by Moolam as Dreamloom's agent
Its own card calls it Dreamloom image generator. Moolam has not checked that name.
- About
- An image made by Dreamloom's generator, ERC-8004 agent 10273, and registered through the Moolam platform kit. The agent's owner signed this fingerprint, and the key bound to the creator wallet signed it, before the registry would write the record.
The fingerprints
Fingerprint version 1
Anyone can fetch the picture, fingerprint it again and compare it with these. Chainlink's check does exactly that. Nothing here depends on the file name or on anything the metadata claims.
- Look fingerprint (pHash)
- 0xa71c5c
67b36b6c 95 - Layout fingerprint (block hash)
- 0x0ff00f
f00ff00f f07ffe3c 7e301c10 0cff1f7f 1340801f 90fff73c f7300c08 08 - Exact file fingerprint (SHA-256)
- 0xe1c37e
637ea944 ac14e549 698e669d 7509c75e 48033f78 d446ec80 68cb950f 52 - Content Credentials fingerprint
- 0x22b06b
643e370c 60494141 c3249964 6f72c4f4 a96272ea 231640bb a0de5398 d9 - Metadata
- Open the stored record on IPFS
- Passport id
- 0xe1c37e
637ea944 ac14e549 698e669d 7509c75e 48033f78 d446ec80 68cb950f 52
This passport is also an NFT on Monad, with the same id
Edits
Registered from this one
No edit has been registered from this passport.
Only the owner can add edits. The app's Privy permission can add edits and nothing else.
Check a copy
Is your copy this picture?
Drop any copy here. It goes to the verify service, which fingerprints it and answers against this passport, not against the file name.
A resized, re-encoded, turned or mirrored copy still matches. A crop does not, yet.