HARBORVIEW TECHNOLOGY · FREESTYLE LEGENDS WALLET
VIX Connect
Developer foundation · External connections not yet releasedA Web3-oriented integration architecture connecting FLT identities, VIX-native capabilities and future authorized applications. ROCx Exchange is the planned separate exchange and asset transfer execution rail.
1. Architecture
FLT World authenticates the person and resolves approved FLT roles. FLT Wallet manages wallet identity, tickets and the request to activate VIX on-chain access. VIX is the proof/blockchain layer. ROCx Exchange is a future separately governed trade, transfer and settlement integration. External applications must request explicit scopes and consent; they never inherit administrator or athlete privileges.
2. API discovery
| Resource | Route | Availability |
|---|---|---|
| Capability manifest | /.well-known/vix-connect.json | Published, read-only |
| Own-wallet status | GET /api/wallet/v1/me/ | Authenticated |
| Activation request | GET/POST /api/wallet/v1/onchain/ | Authenticated, explicit consent |
| Registered app grants | GET /api/wallet/v1/connect/ | Authenticated, read-only |
| Third-party authorization | OAuth2/OIDC authorize/token | Not released |
| WalletConnect / VIX provider | Native signed session | Not released |
| ROCx exchange transfers | Exchange/settlement API | Not released |
3. Future app onboarding
Register an application, validate its HTTPS redirect allowlist and ownership, undergo scope and risk approval, authorize with OAuth 2.1 Authorization Code + PKCE S256, show precise consent to the account holder, issue audience-limited tokens only after release acceptance, support short expirations and revocation, and use VIX-native signed challenges for asset operations. No general third-party token issuance is live.
4. Protocol requirements
Implement CAIP-style chain/account identification where applicable, replay-safe challenge signing with origin and nonce binding, EIP-1193 only if chain compatibility is independently confirmed, and WalletConnect only after VIX signing and session controls pass tests. No claim is made that VIX is EVM-compatible. No private keys or raw device biometrics may be exposed to applications.
5. FLT user on-chain activation
A verified member selects Request VIX On-Chain Activation in the wallet and consents to review. The request appears in Control Tower. An authorized reviewer can reject it or approve it for future VIX provisioning. Approval does not create a wallet address, custody account or NFT. Those features remain disabled until chain ownership, signing and legal/reconciliation controls are ready.
6. ROCx Exchange integration plan
ROCx will be an independently permissioned adapter for future supported asset discovery, deposit addresses, order placement, withdrawals, transfer execution, fees and settlement. It must use separate account linkage, sanctions/KYC/AML where required, product eligibility, balances and settlement proof verification, travel-rule controls where applicable, and jurisdiction-specific licensing reviews. FLT Wallet must never equate an exchange deposit address with a VIX-native self-custody address. All ROCx trading and transfers are currently off.