Treasury Services (Command Group: 3)

Command Codes

Note: The Treasury may manage coins in the RAIDA Token Conversion Wallet zero by using the Lock Services.

Command Code Meanings

Access Keys

Some denominations are used as Access Keys and allow their holders to have rights on the RAIDA.

There are four access key types implemented in the RAIDA Protocol.

Every packet sent to a RAIDA server is encrypted with a key of a certain type. Besides its primary encryption function the key also provides authorization.

A RAIDA server decrypts a packet and identifies the user and permissions granted to this user.

The keys implemented as coins with higher denominations.

Get Available SNs

This method is the first part of the two-step token creation process. The client sends four-byte SessionID and the RAIDA server locks serial numbers using the Session ID. After that, the next step (Create Tokens) downloads the tokens using the same Session ID.

This service returns an array of token serial numbers that are available to be used in the creation command. The returned item can be either an individual serial number or a range.

The ranges come first prepended by the number of them. The individual serial numbers come after them.

Example Request Body with four tokens:

Sample Returns for three denominations. The first has three ranges and two singles. The second has 1 range and 1 single. The third has 2 ranges and 3 singles.

Release Lock

The service deletes coins that were previously reserved by Get Available SNs call.

Example Request Body with four coins:

Get All SNs

The service returns all serial number for a denomination (or all denominations). The returned byte array is packed into a bitmap sequence where "1" stands for "minted", "0" is "available"

Example Request Body:

Response Body

Create Tokens

The service creates tokens that were previously reserved by "Get Available SNs" call. Create tokens must be called within a few seconds after the initial Get Available SNs call before the session expires. The same Session ID must be used for both services.

Example Request Body with four tokens:

Response Body Will be empty except for status.

The PAN is determined by concatenating the RAIDA ID, Serial Number and the PG. Like this

1. The Client will generate a 16 byte random seed.
2. The Client will send this seed to the RAIDA. This seed is called a "PAN Generator".
3. The Client and the RAIDA will use an algorithm to figure out what the Authenticity numbers will be for each serial number that fixes.
4. The Authenticity numbers for each serial number will be calculated by concatenating the RAIDA Number (String), the Coin's Serial Number (string) and the Seed that will be (converted into a 32 character string) together.

Then the concatenated string is:

So the AN will be:

Create Tokens In Market Locker

This is exactly like the Create Tokens command but with a different command number.

The PG is not needed and will be ignored. Random numbers should be put there instead.

The difference on the RAIDA is that these coins will be put in a system locker with a fixed Key ID. The key ID is: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 No locker service can call this special locker key and this cannot be used by the public as their locker.

Example Request Body with four tokens:

Response Body Will be empty except for status.

Delete Tokens

The sender sends authentic tokens. Those tokens are then deleted from the system and the Months From Start Byte is changed to zero.

Example Request Body with four tokens:

Response Body

Freeze Tokens

This stops the token from being able to be authenticated.

Unfreeze Tokens

Makes it so that the coins can be used again.

The mixed bit field. zeros for pass, ones for failed.

Seize Tokens

This will take the tokens specified and place them into a locker that the Treasurer can then put in his bank. This service is almost identical to the PUT locker code service except there is no authentication of tokens.

Sample Seize Request

Response Status Table

MS means Mixed Status but here we are talking about a mixed group of lockers, not coins. Each bit returned represents the status of one locker. If the bit is a zero then that locker has failed. If the bit is a 1 then that locker is authentic.

Set Fee For Swaps

Every time someone converts coins, a fee will be charged to the account of the RAIDA. This fee is set by the Treasury. In the future, the fee may be either fixed or variable and may have a complicated algorithm. Each currency may have a different fee associated with it. That is why there will be bytes reserved in the request body. For now this command just sets a percentage of the coins converted.

Suppose the conversion fee is set to 3%. If 100 RAIDA are converted to Bitcoin, the fee will be 3 RAIDA. Suppose a person wants to convert 1 Bitcoin to 100 RAIDA with the same 3% fee. The fee will be 3 RAIDA. The amount of fees is always calculated based on the value of the RAIDA tokens involved.

The request body needs to have a percentage to charge as a fee. This percentage is expressed in two bytes. The first byte is the whole part of the percentage and ranges from 0 to 99. The second byte is the fraction part of the percentage and is valued from 0.99 too. So the least percentage that can be charged is 0.0% and the most is 99.99%

Example Request:

Example Response: