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 12, 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 FT, 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 FT, NFT minting
5	Call RAMP API to obtain UUID	Request must include information necessary for FT, NFT minting (Intent, etc.) The interface required for UUID requests can be found at the following link .
6	Open RAMP F/E web view	Includes UUID, JWT, sessionID
7	Retrieves the user asset information required for calculations in the Ramp F/E.
8	Retrieves the user asset information	The interface for retrieving a user’s in-game assets can be found at the link .
9	User selects minting on RAMP F/E	Proceed with signing through the wallet
10	Deliver user signature value
11	Request Validator signature to game server	The interface for signatures required for server verification can be found at the link .
12	Verify FT, NFT minting request information and deduct necessary game assets	Restoration needed if transaction fails
13	Validator signature	Signed with the Validator private key registered in the RAMP console
14	Verify Validator signature	Verified with the Validator address registered in the RAMP console
15	Request transaction occurrence to blockchain network
16	Send transaction result to game server	The interface for checking token minting and burning transaction results can be found at the link .
17	Process transaction result	Restoration of game assets needed if transaction fails
18	Retrieves the user asset information required for calculations in the Ramp F/E.
19	Retrieves the user asset information	The interface for retrieving a user’s in-game assets can be found at the link .
20	Process burning 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 12, 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 FT, 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 FT, NFT burning
5	Call RAMP API to obtain UUID	Request must include information necessary for FT, NFT burning (Intent, etc.) The interface required for UUID requests can be found at the following link .
6	Open RAMP F/E web view	Includes UUID, JWT, sessionID
7	Retrieves the user asset information required for calculations in the Ramp F/E.
8	Retrieves the user asset information	The interface for retrieving a user’s in-game assets can be found at the link .
9	User selects burning on RAMP F/E	Proceed with signing through the wallet
10	Deliver user signature value
11	Request Validator signature to game server	The interface for signatures required for server verification can be found at the link .
12	Verify FT, NFT burning request
13	Validator signature	Signed with the Validator private key registered in the RAMP console
14	Verify Validator signature	Verified with the Validator address registered in the RAMP console
15	Request transaction occurrence to blockchain network
16	Send transaction result to game server	The interface for checking token minting and burning transaction results can be found at the link .
17	Process transaction result	Game assets need to be granted if the transaction is successful
18	Retrieves the user asset information required for calculations in the Ramp F/E.
19	Retrieves the user asset information	The interface for retrieving a user’s in-game assets can be found at the link .
20	Process burning result UI in-game