Partner Integration
Asset configuration, partner identity and operational coordination.
Asset integration inputs
Agree the token contract, network, decimal precision and technical behaviour with the team. Check market reserve responsibilities and the intended prediction-market use before activation. Do not infer deployed contract addresses from architecture diagrams.
Wallet identity
Partner login connects the chosen wallet and requests an identity signature containing a one-time nonce and expiry. Verification is performed server-side. The login signature is not a transfer or token approval; access depends on the wallet being bound to a partner.
Partner-scoped information
The dashboard serves the bound partner’s projects and tokens. Data availability varies by connected sources; unknown metrics are unavailable, and demo data is explicitly labelled. Wallet switching ends the old session rather than granting access to another partner’s information.