Two trust checks, one review file
Audit and KYC coordination brings two separate checks into one organized file. An independent auditor reviews the agreed smart contract code. A KYC provider handles the identity check. We coordinate the work and arrange the resulting evidence. Neither assessment is performed by us.
Start with the destination's written request. A data site may ask for different proof than a launchpad. Note the recipient and requested format. Also record any instructions about the report or badge. Our wider listings and verification support can help you plan this alongside other listing materials.
| Track | Who carries it out | What we help organize |
|---|---|---|
| Contract audit | Independent auditor | Contract references, agreed review plan, report handoff |
| Identity check | KYC provider | Provider requirements, secure submission route, completion evidence |
| Destination file | Your project contact, with our coordination | Request, supporting links, consistent names, submission record |
For example, a project preparing for a directory review can keep audit evidence separate from identity documents. The team can still track both against the same request. That simple distinction helps your team find the right file. It also avoids treating one check as a substitute for the other. If CoinMarketCap or CoinGecko is the destination, coordinate this work with the relevant CoinMarketCap listing support or CoinGecko listing support.
Keep the record together when plans change
A clear evidence record helps your team answer questions without guessing which file is current. We track what was requested and which provider received each item. We also record what came back. At Brand Community, one coordinator maintains that evidence index. They keep open questions visible to your project contact.
Picture a validator team after a campaign ends. Nobody wrote down what happened. Now they need to prepare an audit and KYC file, but links and versions are scattered. We would collect the destination's request and available records first. Then we would mark what still needs an owner.
The team stays in control of its own documents. We can route technical questions to the auditor. Questions about the provider's process go to the KYC provider. Your authorized contact answers project questions and approves anything submitted on the team's behalf. This keeps handoffs clear. It also avoids asking the auditor to speak for the project.
For another project, say the contract address changes during review. We would flag the changed reference. Then we would compare it with the agreed audit work and ask the auditor whether the change matters. We also keep project names and supporting links aligned across the evidence file. If token data needs its own check, circulating supply verification is a separate track with its own supporting materials.
How do we prepare providers and project materials?
We begin with the actual recipient request. Then we match the provider's proposed work and your available materials to it. That gives everyone a shared reference before any handoff. It also helps us spot missing contract details or unclear KYC instructions early.
For the contract review
Share the chain, contract addresses, and source-code or repository references. Add a short explanation of the system. Note which version or deployed contracts the review should cover. Ask the auditor what its report will describe. Check how it handles questions and code changes during review. We help record those answers. Your team can then see what the report is expected to cover.
For the identity check
Ask the KYC provider which representatives must complete its process. Check what confirmation it issues. Find out who receives personal documents and how they should be submitted. Ask where to direct questions about access or retention. We coordinate the handoff through the provider's confirmed channel. Do not send identity documents to a general project contact.
For the destination
Keep the exact request, recipient name, and format instructions beside the evidence list. Say a launchpad asks for an audit report and proof of a completed identity check. We can map those requests to the right provider outputs. Then we can identify anything the project still needs to supply. Our launchpad listing support can sit alongside this preparation when that is your next step.
Five handoffs carry the work to submission
The coordination moves through five visible steps. It starts with the destination's request and ends with a record of what your team sends. You keep approval over project information and each agreed handoff.
- Share the request. Send the data site or launchpad name and its audit or KYC instructions. We use the wording provided to identify the requested evidence.
- Map the materials. We review contract references, existing reports, project details, and missing items. You confirm the intended review and what may be shared.
- Set provider handoffs. We help arrange introductions and clarify open questions about provider plans, expected materials, and communication. The auditor and KYC provider remain responsible for their own processes.
- Organize the evidence. We collect the agreed reports or completion evidence. Then we check names, versions, and contract references for consistency. The index records each item's owner and status.
- Prepare the destination file. We arrange the agreed materials for the named recipient and record what was sent. If a follow-up arrives, we route it to the project contact or provider best placed to respond.
Your team can see which items are ready and which still need attention. The evidence index gives your contact a practical check-in point throughout the work. Questions do not need to stay buried in separate messages. If the destination asks for a profile correction as well, see our listing profile update support for that separate task.
The recipient reviews the evidence on its own terms
A well-organized submission makes the requested evidence easier to follow. Keep a copy of the recipient's instructions beside the provider report or KYC confirmation. Check that contract references, project names, and file versions agree. If anything has changed, flag it before submission instead of relying on an old description.
A data site or launchpad decides whether the audit report or KYC evidence meets its request. Each provider controls its own assessment and output. We cannot promise acceptance, a particular audit finding, or issuance or display of a badge. We can complete the agreed coordination, track the handoffs, and provide a clear record of the evidence prepared and sent.
To begin, send us the destination's exact request and relevant contract references. Include any existing reports and the name of your authorized project contact. We will review those materials with you. Then we will identify missing handoffs and confirm what coordination comes next. You do not need to send identity documents to start that conversation.
How it works
- Share the destination requestSend the data site or launchpad name and its audit or KYC instructions. We map the evidence to the request you received.
- Confirm materials and accessWe review contract references, existing documents, and missing items. You approve the review plan and decide what information may be shared.
- Coordinate the providersWe arrange the agreed auditor and KYC provider handoffs, track questions, and keep your project contact informed.
- Organize the evidenceWe gather the agreed reports or completion evidence and check names, contract references, and versions for consistency.
- Prepare the destination fileWe arrange the agreed materials for the recipient and record what was sent. Follow-up questions go to the project contact or provider best placed to answer.
Frequently asked questions
Who actually reviews our smart contract code?
An independent third-party auditor carries out the technical review and prepares its own findings. We help define the agreed contract work, organize materials, and coordinate communication. Before work begins, share the relevant addresses and code references. This lets us compare the proposed review with the contracts you plan to use.
Can one audit report serve more than one destination?
It may be useful to share the same report, but first compare it with each recipient's request. Check that the report identifies the relevant contracts and version. Ask whether the destination requests a particular format or additional evidence. We can keep a separate record of what was sent to each recipient.
Should I send identity documents to your team?
No, not as a routine first step. We help confirm the KYC provider's requested materials and its designated submission route, then coordinate that handoff. Start by sharing the destination's request and the provider instructions you already have. Keep personal documents within the provider's confirmed channel.
Can the audit and KYC checks run at the same time?
They can be coordinated as two tracks when the chosen providers and your project materials are ready. We record each track's requests and handoffs in one evidence index. Your contact can see what is waiting on the auditor, KYC provider, or project team. We confirm the sequence once provider requirements are clear.
Which details help us get the review started?
Send the recipient's exact request, the chain and contract references, any existing audit or KYC evidence, and your authorized project contact's details. A short system outline is useful for the auditor. You can start without sending identity documents. We will help identify the correct provider route first.
Will a report or KYC confirmation secure acceptance?
No. The data site or launchpad makes its own decision about whether the submitted evidence meets its request. Providers control their assessments and outputs. We can coordinate the agreed work, check the evidence file, and record the submission. Acceptance and badge display are not ours to decide.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…