Developer Prerequisites

CROSS Ramp Console Registration

Configure necessary settings for deploying developer token contracts and user token minting/burning.

• You can configure token names, icons, etc. to be used in the developer's application (dApp).
• You can configure game currencies to be displayed in the application (dApp).

Integration API

This is the interface required between RAMP and game servers for implementing token minting/burning functionality within applications (dApps).

⚠️

Important

To integrate CROSS Ramp for token minting and burning in applications (dApps), you must implement three endpoints in your game server according to the interface specifications in order to support integration with the RAMP backend server.

Game Currency Inquiry API Integration

• API integration between the RAMP backend server and developer server is required to retrieve currency data needed during the token minting process.

Validator API Integration

• API integration between the RAMP backend server and developer server is required to process ECDSA signature requests.
• You can generate private keys required for ECDSA signatures using the provided tools.

Result API Integration (Webhook)

• Since blockchain transaction results are sent from the RAMP backend server to the developer server via webhook, a webhook receiving API is required to handle these requests.

Wallets

Wallets are required for token deployment and token minting/burning.

Owner Wallet

• Required for deploying 'RAMP Contract' and 'token contracts' using the CROSS Ramp Console.
• A company-managed wallet using MetaMask + hardware wallet (Ledger, etc.) is required.
  • If a hardware wallet cannot be used, you must install the MetaMask app on a separate company-managed mobile device for key management.
  • Approximately 1 $CROSS is required as gas fee for transaction generation during contract deployment (less than 1 $CROSS).
  • When using MetaMask, you need to add CROSS Mainnet and Testnet networks.
• CROSSx app support is planned for the future.

Fee Wallet

According to developer policy, you can charge users token minting fees at the rate set in the CROSS Ramp Console.

• When users mint tokens, the amount excluding the percentage set in the CROSS Ramp Console is sent to the user's wallet.
  (Example: If a 10% fee is set, when a user mints 1 Token, 0.9 Token excluding the fee is sent.)
• A company-managed wallet address is required.

Validator Key

A Validator key is used to verify that transactions requested by developers are correct when users request token minting/burning.
You need to register the generated Validator key in the CROSS Ramp Console.

❗️

Important

The generated private key must be stored securely to prevent external leakage.

Key Generation

• Private keys and addresses can be generated using the KeyGenerator provided by NEXUS.
• Private keys and addresses generated from MetaMask and CROSSx can be used.
• Company management is required, and care must be taken to prevent external exposure.

Firewall Whitelist Addition

Adding firewall whitelists for communication between CROSS Ramp and developer servers is required.

• Used when displaying user game currency information to be shown in RAMP F/E.
• Required for communication between RAMP B/E and developer servers.

Others

Adding CROSS Networks (Testnet, Mainnet) to MetaMask

To use MetaMask on the CROSS network, you need to add networks within MetaMask.

• MetaMask Settings

MetaMask -> Settings (bottom right) -> Networks -> Add Network

×

×

×

×

×

Select 'Settings' (bottom right)	Select 'Networks'	Select 'Add Network'	Select 'Custom' tab	Enter network information

• CROSS Chain Network Information