# <font>Protocol Conventions</font>

## Business Rules

- Each integrated operator will be assigned a unique agent account within the **Luckybet777** platform. All player accounts developed by the agent will be attributed to that agent account.
- Both operators and agents are subject to credit limits. If the credit limit is exceeded, please contact customer service promptly to top up the quota.
- To ensure data accuracy and improve program performance during communication, data types and conversions between strings must comply with the following specification:

| Data Type | Definition           | Value Range                                                   |
| :-------: | :------------------: | :-----------------------------------------------------------: |
| boolean   | Boolean              | true / false                                                  |
| byte      | 8-bit signed integer | -128 ~ 127                                                    |
| short     | 16-bit signed integer| -32,768 ~ 32,767                                              |
| int       | 32-bit signed integer| -2³¹ ~ 2³¹-1                                                  |
| long      | 64-bit signed integer| -2⁶³ ~ 2⁶³-1                                                  |
| float     | 32-bit floating point| 1.4E-45 ~ 3.4028235E38                                        |
| double    | 64-bit floating point| 4.9E-324 ~ 1.7976931348623157E308                             |
| char      | 16-bit Unicode char  | Not applicable                                                |

## Communication Standards

- **API Protocol**  
  > Complies with **JSON-RPC Protocol 2.0**  
  > The API endpoint is provided separately. Please contact the business representative to obtain the API address and related configuration.

- **Interface Specification**  
  > Data protocol: **JSON-RPC 2.0**  
  > Encoding: **UTF-8**  
  > Supported HTTP Header: `application/json`  
  > (*Note: POST data structure may vary. See code examples for reference.*)

- **Security Key**  
  > Agent key: `AuthCode`, also known as the API key. It is provided in the **Mega API Agent Information Form**.

- **Digest Algorithm**  
  > This document involves a signature digest, referred to as `digest`.  
  > The digest is generated using the **MD5 algorithm**, in the following format:  
  > `md5(random + transaction-specific plain fields + agent key)`  
  > `random` is a randomly generated string, UUID is recommended.  
  > The specific transaction fields used in the digest (which may be a combination of multiple fields) are described in each API interface's digest section.