Nexwest Docs

Launch readiness

0 of 24 complete

Jurisdiction & licensing

Target jurisdictions are documentedList every country you accept users from and the legal basis for serving derivatives there.Licensing position is reviewed by counselDetermine whether the frontend, referral program, or order routing requires a license or exemption.Geo-blocking and IP controls are enforcedBlock restricted regions at onboarding and at order submission, not only on the marketing site.Operating entity and terms are clearUsers must know who operates the interface, which entity holds the relationship, and where disputes are handled.

KYC / AML & sanctions

KYC/AML program matches the risk profileNon-custodial interfaces may still have obligations. Document thresholds, monitoring, and escalation.Sanctions and PEP screening is activeScreen at onboarding and on an ongoing basis; keep evidence of screening decisions.Wallet risk screening is definedDecide how you treat sanctioned, mixer-linked, or stolen-fund addresses before allowing order flow.

Product & risk disclosures

Leverage, liquidation, and funding risks are disclosedShow the risk before the first trade, not only in a footer. Include liquidation and auto-deleveraging scenarios.All fees are shown before signingProtocol fees, builder fees, referral discounts, and funding must be visible in the order preview.No investment advice or guaranteed returnsRemove language that promises yield, points value, or risk-free outcomes.Eligibility and restricted-person rules are enforcedDefine who cannot use the interface and how you detect and offboard them.

Marketing & conduct

Marketing claims are substantiatedEvery performance, volume, or reward claim needs a source and a date. Avoid implying a partnership that does not exist.Affiliate and influencer disclosures are in placePaid promotion must be disclosed. Referral links and builder fees must be explained.Points/token language is accurateDo not imply points are tokens, have guaranteed value, or will be listed.

Data, API & IP

Venue API terms are reviewedCheck rate limits, redistribution, commercial use, branding, and builder-code rules.Market data is licensed for your usePublic availability is not the same as a right to resell. Document your rights for any paid data product.Brand and trademark usage is compliantDo not imply that you are the venue or an official affiliate without written permission.

Operations & incident response

Incident response plan is writtenDefine who declares an incident, how users are notified, and how funds/positions are protected.Monitoring and alerting cover order flowAlert on failed feeds, stale prices, gateway disconnects, and abnormal order rejection rates.Support escalation and evidence handling are definedNever ask for seed phrases. Keep ticket evidence, timestamps, and transaction hashes.Privacy policy and data retention are publishedExplain what you collect, why, where it is stored, and how users can request deletion where applicable.

Builder & referral economics

Builder fee approval is explicitThe user approves a maximum fee. The fee is shown before signing and never exceeds the approval.Referral rewards are disclosedExplain the 10% share, the referee discount, and any caps. Do not hide the relationship.Tax treatment of builder/referral income is reviewedRevenue paid in stablecoins or tokens may create tax obligations. Confirm with an accountant.

Launch is a checklist, not a feeling.

Not legal advice

Evidence, not intentions