Verified collections
A verified badge answers one question: does the account that minted this collection belong to the people who say they made it? This guide explains what it proves, and walks through getting one, step by step.
What verification means
The verification page shows every applicant the same definition, and it is the one we hold ourselves to:
Verification confirms who controls the issuing account. It is not an endorsement of the project, its team, its roadmap, or its value.
Prove it any of three ways, and one is enough to be reviewed: sign with the issuing account’s wallet, publish an xrp-ledger.toml on your domain that lists the issuing account, or post a code from the project’s X account. We check each proof automatically; a person still makes the decision. Our staff can also verify a collection directly when they have confirmed who controls it another way, and the reason is recorded with the badge.
A collection is promoted when a verifier is satisfied that: whoever controls it has proved control of the issuing account, the project’s domain, or its X account — more proofs are stronger evidence; there is no open copyright takedown; the artwork does not match an existing verified collection; and the metadata is complete enough to display.
What it tells you as a buyer
Look for it when you are worried about copies. A copy-mint can reuse a collection’s name and artwork, but it cannot come from the original’s issuing account, so it cannot carry the original’s badge.
It is not a recommendation. A verified collection can still fall in value, and no badge on this marketplace is investment advice.
No badge does not mean a collection is fake. A collection without one may simply never have applied.
What you need to apply
Applying takes a few minutes. You need:
- to be signed in — the request is yours, and only you and the verifiers can read it;
- the collection’s issuing account — the XRP Ledger address that minted it;
- at least one of the three proofs below: the issuing account, your domain, or your X account;
- and a person’s review, which is always the last step. Passing a proof sends your request to a verifier; it does not grant the badge by itself.
One proof is enough to be reviewed. Each extra one is independent evidence, so more proofs make a review quicker and more likely to succeed.
Then:
- On your collection’s page, open the About tab and choose Apply for verification.
- Enter the issuing account. If the project has a Discord, an Instagram, a Telegram channel or a website contact page, add them — a verifier checks those by hand. Choose Start the application.
- The next screen shows the three proofs. Do any of them, in any order. Each is checked automatically within a minute or so, and says why if it did not pass, so you can fix it and choose Check again.
- The first proof that passes moves your request to In review. You can keep adding proofs while it waits.
Proof one: the issuing account
This proves you hold the keys to the account that minted the collection. It is the strongest proof. The page offers the ways your wallet can use.
If you are signed in as the issuing account, choose Use my signed-in wallet. Your sign-in is the proof. It does not count if the account’s master key has since been disabled, because the key you signed in with then no longer controls the account; sign the proof transaction instead.
To sign on the page, connect the issuing account’s own wallet and choose Sign the proof. Your wallet shows a settings transaction that changes nothing on the account: its only content is a note carrying your request’s challenge.
First Ledger’s built-in wallet signs NFT transactions only, so it cannot sign this one. If it is your issuer, use its sign-in, above; otherwise connect another wallet.
This transaction is submitted, and costs the network fee
It is sent to the ledger, not just signed, and it costs the network fee — a fraction of a cent. That is deliberate. A signature on its own could only be checked by us; a submitted transaction is checked by the ledger itself, against whichever keys control the account today.
From any other wallet or tool — a cold wallet, a hardware wallet, a script — send any transaction from the issuing account carrying the memo the page shows, then choose I have submitted it — check. Paste the transaction’s hash if you have it; without one we search the account’s latest 1,000 transactions.
A challenge is accepted for 24 hours. If it runs out before your transaction is validated, choose Get a new challenge and sign again.
An account with a regular key can sign with that key. The ledger accepts it as the account’s own signature, and so do we.
A multi-signing account can collect its signers’ signatures on the same transaction in its usual tool and submit it the any-wallet way. If that is not practical, prove your domain or your X account instead, and say so in the request’s messages; a verifier will take it from there.
An issuer that can no longer sign — master key disabled and no other key, often called blackholed — cannot give this proof at all. Use the domain or X proof, and say so in the request’s messages, so the verifier knows why this one is missing.
Under the hood
The page’s transaction is an AccountSet with one memo: fl-nft-verify as its type, the challenge as its data and text/plain as its format, each hex-encoded.
Any transaction type works, if it is from the issuing account, carries the challenge exactly, and was validated before the challenge expired. A tesSUCCESS result counts, and so does any tec result: both are applied and recorded with their memo. A transaction signed by a delegate on the issuer’s behalf does not count.
Using your sign-in is refused when the account has lsfDisableMaster set.
Proof two: your domain
This proves the project’s website vouches for the issuing account, with a small file in the XRP Ledger’s own standard format.
Create a file named
xrp-ledger.tomlwith an[[ACCOUNTS]]entry for the issuing account. Put your issuing account’s address in place of the example’s; the description is optional:[[ACCOUNTS]] address = "rXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" desc = "Issuer of our NFT collection"- Publish it at exactly
https://example.com/.well-known/xrp-ledger.toml, with your domain as the host. - On the verification page, enter just the host — like
example.com— and choose Check domain.
What the check accepts:
- https only. The file is never read over plain http.
- At most 128 KB, answered within 10 seconds.
- Redirects — up to 3 — only to the same host or its
www.address, and https all the way. A redirect to another domain, such as a hosting provider’s own address, is refused: the file must be your domain’s own statement. - Any content type, though
application/tomlor plain text is best. A web page in the file’s place — what many sites serve for an address they do not know — is refused as not a TOML file. - A subdomain is its own site. A file on
nft.example.comproves that host, not the main domain, and the verifier sees exactly which host you proved. - No CORS header is needed for our check, which reads the file from our servers. Wallets and explorers read the same file from the browser, and the standard asks for
Access-Control-Allow-Origin: *for them.
A bonus signal: set the issuing account’s Domain field to the same domain, and the verifier sees that the two agree. Wallets and tools that edit account settings can set it; the field holds the domain in hexadecimal, which most of them write for you.
Under the hood
The file is XLS-26’s, and only its [[ACCOUNTS]] entries are read: a line inside a description or another table never counts. The Domain field is set by an AccountSet transaction’s Domain.
Proof three: your X account
This proves the project’s X account vouches for the request. No X login and no app is involved: we read the post the way a website embeds one.
- Copy your code from the verification page. Every request has its own, shaped like
FL-XXXXXXXXXX. From the project’s X account, publish a new post that contains it. For example:
Verifying our collection on First Ledger NFT: FL-XXXXXXXXXX- Copy the post’s link, enter it with your handle on the verification page, and choose Check post.
What makes it fail:
- The code must be in the text you wrote. A code in a post you quote, or in the post you reply to, is not read.
- The post must be by the handle you entered. We take the author from X’s answer, not from the link, so a link with another name in it changes nothing.
- It must be public. A protected account’s posts cannot be read, and neither can a deleted post.
- Keep it up until your request is decided. The verifier may open it.
Discord, Instagram, Telegram and a website contact page have no automatic check. List them on the form and the verifier checks them by hand; they may ask you, in the messages, to post something there.
What happens in review
A person reviews every request, whatever passed. The page’s status says In review while it waits.
The verifier looks at:
- which proofs passed, and how — including whether your domain matches the issuing account’s own Domain field;
- the other accounts you listed, by hand;
- open reports, copy-mint flags, copyright takedowns and the scam list, and whether the issuing account mints other collections too — then an issuer or domain proof speaks for all of them, so expect a question;
- and the criteria above: the artwork against collections already verified, and whether the metadata is complete enough to display.
There is no fixed turnaround. Requests are reviewed oldest first, and one in review never expires while it waits.
If the verifier needs something, the status becomes A verifier has a question and the question is under Messages on the request. Reply there or add a proof; either sends it back to review. A request waiting on your answer does not expire.
We send no email or Telegram message about a request. Its status is on the collection’s verification page, and on your own account page under Your verification requests, which marks a request that changed since you last looked.
An approval puts the badge on the collection. A rejection always says why.
When a request expires
- Each challenge lasts 24 hours. When it runs out, the page offers a new one.
- If no proof passes within 48 hours, the request expires. Nothing is held against the collection, and you can apply again straight away.
- Once a proof has passed, the request no longer expires.
- One request per collection can be open at a time.
How a badge is lost
What removes a badge is part of the same definition:
Verification can be reversed. Transfer of the issuing account, a confirmed copy-mint, or a sustained takedown all remove it, and each reversal is recorded with a reason.
If a request is rejected
A rejected request says why. What happens next is the same for everybody:
One appeal is allowed. Apply again and reference this request; it is reviewed against the same written criteria, and the answer may be the same one.