Send listing, verification, launch, or partnership requests with one named owner, public proof, and a clear review ask.
Preparing inquiry
Loading trusted submission state and inquiry form context.
Trust Center
Use it to confirm route limits before you share project materials.
Send listing, verification, launch, or partnership requests with one named owner, public proof, and a clear review ask.
Preparing inquiry
Loading trusted submission state and inquiry form context.
Trust Center
Use it to confirm route limits before you share project materials.
Inquiry path
Business inquiries are subject to the Trust Center and disclosures. Include only the public links and contact details needed to assess fit.
Send only the contact details, public project information, and specific review request needed to decide whether there is a clear next step. Do not send credentials, private keys, seed phrases, or wallet recovery data.
Use a work email and name the person who can answer follow-up questions.
Include official public links, project URLs, and technical references instead of private files.
State the listing, verification, launch, or partnership request in one clear sentence.
Expect a manual fit check first. Approval, pricing, promotion, and timelines are not guaranteed.
Review the risk disclosures before sending a request that depends on token, listing, or market outcomes.
Submitting an inquiry does not guarantee project acceptance, commercial engagement, or a fixed delivery timeline.
Evidence requirements
A complete packet makes triage faster. Missing ownership, public evidence, or scope usually stops the request before follow-up.
Service fit
Check fit before sending a request. This is not pricing, packaging, or acceptance.
Best first stepChoose one lane, then send one specific request.
Ready packetOwner, public proof, technical reference, and request are visible.
Stop conditionMissing owner, private data, or outcome promises stop review.
| Fit check | Listing readiness | Verification support | Launch or partnership review |
|---|---|---|---|
| Use when | You have a public project package and need a manual readiness pass. | You need supply, reference, or circulation claims checked for fit. | You need one reviewer to decide whether follow-up is appropriate. |
| Prepare | Destination, supply references, public links. | Contract, public references, claim language. | Owner, launch context, release materials. |
| Boundary | No listing approval or market-outcome promise. | No custody, trading advice, or claim certification. | No press placement or fixed launch timeline. |
Support lanes
Pick the lane, then send the proof that lane needs.
I review listing materials and organize exchange or directory follow-up when the public proof is complete.
I compare supply logic, public references, and circulation materials before a verification request moves forward.
Manual review
I check fit first. Unclear ownership, scope, or proof usually stops the request there.
Collect project details, links, and metadata for eligibility review.
Review submitted information and confirm required disclosures.
Coordinate approved listing workflow and communicate status updates.
Use this for partnership, launch, or announcement requests that need one accountable reviewer to check fit.