Architecture

Through the CROSS-RAMP console, you can intuitively check the request-response flow between applications (Dapps) and servers, as well as the token issuance process linked to the blockchain network.

Developers can easily understand how applications (Dapps) interact with the RAMP platform and how token issuance requests are transmitted to the blockchain to create actual tokens step by step.

Components

Component	Role / Description
RAMP F/E	Provides the user interface (UI) and displays transaction status in real-time.
RAMP B/E	Performs core logic such as transaction request processing, validation, and Validator signature requests.
Game Client	Calls RAMP F/E and displays transaction progress status.
Game Server	Responsible for game internal logic such as game asset verification, deduction, restoration, and signature processing.
Blockchain Network	Handles the minting and burning transactions of actual tokens.

Token Minting

Token minting process sequence.

When a user requests token minting, the game assets must be deducted first before token minting proceeds.
If the token minting fails in the transaction, game assets need to be restored.
In sequence 10, it is necessary to verify whether the game assets and token amounts used for user token minting match the game assets and token amounts requested by the CROSS platform.

No.	Description	Note
1	User requests NFT minting
2	Request JWT token	Used in flows 9 and 14, needs verification on the game server
3	Request UUID
4	Query game assets required for NFT minting
5	Call RAMP API to obtain UUID	Request must include information necessary for NFT minting (Intent, etc.)
6	Open RAMP F/E web view	Includes UUID, JWT, sessionID
7	User selects minting on RAMP F/E	Proceed with signing through the wallet
8	Deliver user signature value
9	Request Validator signature to game server
10	Verify NFT minting request information and deduct necessary game assets	Restoration needed if transaction fails
11	Validator signature	Signed with the Validator private key registered in the RAMP console
12	Verify Validator signature	Verified with the Validator address registered in the RAMP console
13	Request transaction occurrence to blockchain network
14	Send transaction result to game server
15	Process transaction result	Restoration of game assets needed if transaction fails
16	Process minting result UI in-game

Token Burning

Token burning process sequence.

When a user requests token burning, the token burning transaction must be performed first before game assets are granted.
If the transaction fails, game assets should not be granted.
In sequence 10, it is necessary to verify whether the game assets and token amounts used for user token burning match the game assets and token amounts requested by the CROSS platform.

No.	Description	Note
1	User requests NFT burning
2	Request JWT token	Used in flows 9 and 14, needs verification on the game server
3	Request UUID
4	Query game assets required for NFT burning
5	Call RAMP API to obtain UUID	Request must include information necessary for NFT burning (Intent, etc.)
6	Open RAMP F/E web view	Includes UUID, JWT, sessionID
7	User selects burning on RAMP F/E	Proceed with signing through the wallet
8	Deliver user signature value
9	Request Validator signature to game server	Needs verification on the game server with JWT
10	Verify NFT burning request
11	Validator signature	Signed with the Validator private key registered in the RAMP console
12	Verify Validator signature	Verified with the Validator address registered in the RAMP console
13	Request transaction occurrence to blockchain network
14	Send transaction result to game server	Needs verification on the game server with JWT
15	Process transaction result	Game assets need to be granted if the transaction is successful
16	Process burning result UI in-game