Business Support
Send listing, verification, launch, or partnership requests with a named owner and public proof.
Pick the lane, attach public evidence, and keep private data out of the inquiry.
Support lanes
Choose the review lane before you write.
Pick the lane, then send the proof that lane needs.
- Listings
Listing readiness
I review listing materials and organize exchange or directory follow-up when the public proof is complete.
- Best for
- A prepared listing or directory packet that needs a manual fit check before outside submission.
- Bring
- Website, contract reference, supply logic, and listing destination.
- Proof
Verification support
I compare supply logic, public references, and circulation materials before a verification request moves forward.
- Best for
- A project that needs public references and supply claims checked before a verification request moves forward.
- Bring
- Public source links, contract details, and the claim you want reviewed.
- Ops
Launch and partnership support
Use this for partnership, launch, or announcement requests that need one accountable reviewer to check fit.
- Best for
- A launch, partnership, or announcement request that needs a single accountable reviewer.
- Bring
- Owner contact, project context, timing, and public release materials.
Service fit
Match the request to the review lane.
Check fit before sending a request. This is not pricing, packaging, or acceptance.
Best first stepChoose a lane, then write one request.
Ready packetOwner, public proof, and boundary 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. |
Listing readiness
- Use when
- You have a public project package and need a manual readiness pass.
- Prepare
- Destination, supply references, public links.
- Boundary
- No listing approval or market-outcome promise.
Verification support
- Use when
- You need supply, reference, or circulation claims checked for fit.
- Prepare
- Contract, public references, claim language.
- Boundary
- No custody, trading advice, or claim certification.
Launch or partnership review
- Use when
- You need one reviewer to decide whether follow-up is appropriate.
- Prepare
- Owner, launch context, release materials.
- Boundary
- No press placement or fixed launch timeline.
Evidence requirements
Bring the proof before review.
A complete packet makes triage faster. Missing ownership, public evidence, or scope usually stops the request before follow-up.
What to include
- A work email and the best person to contact.
- Project website, official social links, and public source links.
- Token contract or technical reference when a token is involved.
- The listing, verification, launch, or partnership request you want reviewed.
What I can review
- Official project ownership proof
- Accurate token metadata
- Compliance disclosure alignment
- Profile setup support
What this page does not promise
- No listing approval, pricing promise, or fixed delivery timeline.
- Never send credentials, private keys, seed phrases, or wallet recovery data.
- No custody, asset control, trading advice, or promotional guarantee.
Manual review
How review works
I check fit first. Unclear ownership, scope, or proof usually stops the request there.
Intake
Collect project details, links, and metadata for eligibility review.
Validation
Review submitted information and confirm required disclosures.
Execution
Coordinate approved listing workflow and communicate status updates.
Inquiry path
Send a Business Support inquiry
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 and public project information needed to decide whether there is a clear next review 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 public source links, project URLs, and technical references instead of private files.
State the listing, verification, launch, or partnership request in one clear sentence.
Submitting an inquiry does not guarantee project acceptance, commercial engagement, or a fixed delivery timeline.
Trust Center
Check the Trust Center before you submit.
Use it to confirm route limits before you share project materials.