1. Getting Started

This guide covers integrating ONE RAMP into your game or service.

1.1 What ONE RAMP Does

It converts in-game assets into blockchain tokens, and converts those tokens back into in-game assets.

What you get from integrating

Deploy an ERC-20 game token contract without complex setup or deep blockchain knowledge
Complete deployment and configuration in the console, without writing smart contract code
Fixed API specifications for asset lookup, order validation, and result handling, which reduces trial and error

Term	Description
Studio	Workspace for a team or organization. Manages members, contracts, and API Keys together
Project	A service (dApp) unit inside a Studio. A Project ID is issued on creation
Token Contract	The game token contract (ERC-20)
RAMP Contract	Handles internal Mint/Burn logic. Deployed per project; only works once a token contract is linked
Validator Key	Key used to verify that a request is a legitimate transaction created by your backend
HMAC Key	Key for verifying request integrity between RAMP and your server. Issued when the RAMP Contract is deployed
RAMP F/E	The screen where users perform Mint/Burn (provided by NEXUS)
RAMP B/E	The RAMP backend that processes requests, validates them, and requests signatures (provided by NEXUS)
Intent	The request specification describing which in-game asset is exchanged for which token, and how much

Endpoint	Purpose	Console field
Game asset lookup	Returns the user's asset balances for display in RAMP F/E	`Get Assets`
Signature validation	Validates request integrity, then returns the Validator signature	`Validate Order`
Result handling	Processes the blockchain transaction result	`Handle Order Result`

#	Document	Contents
1	Getting Started	Overview · glossary · scope of your implementation · links
2	2. Architecture	Components · Mint/Burn sequences · absolute rules
3	3. Prerequisites	Wallet · Validator Key · network info · firewall · asset IDs
4-1	4-1. Account and Project	Sign-up · 2FA · Studio · Project · operational checks · Blacklist
4-2	4-2. Contracts	Token and RAMP contract deployment · project linking · known limitations
4-3	4-3. Ramp Settings	Endpoints · fees · display labels · authentication
5	5. Endpoint Specification	HMAC · API spec · Validator signature · constants · errors · testing · Mainnet switchover

Scope

This guide is written for ERC-20 game token (FT) integration.
Other token types require additional API integration and will be documented separately. Contact NEXUS if you need them.

Item	URL
RAMP Console	https://cross-ramp-console.crosstoken.io
RAMP F/E	https://ramp.crosstoken.io
RAMP API	https://cross-ramp-api.crosstoken.io
Terms of Service	https://terms.crosstoken.io/docs/ramp-terms-june-29-2026
ONEx Guide	https://docs.onechain.nexus/docs/introduce
TESTNET Faucet	https://docs.onechain.nexus/v1.4/docs/dev_testnet-faucet
ONEexplorer	https://explorer.onechain.nexus
Key Generator	https://github.com/to-nexus/key-generator/releases/tag/v1.0.2
Contact	[email protected]

This document is based on the ONE RAMP console and API specification as of 2026-08-07. Screens and specifications may change with service updates.