Getting Started
Overview
Welcome to the Keysecure platform. This document is used by the third-party technical team to add the self-developed mainchain to the Keysecure for alliance members.
Note
When third-party technical team using WAPI to access the the server and keeping private keys, Keysecure is not responsible for the security of assets. Therefore, the third-party technical team must establish a complete private key Keysecure System and API private key Keysecure System
Development Notes
The Role of Public and Private Keys
-
Party A is a third-party public chain docking party
-
Party B is the Keysecure BaaS Cloud
-
The Role of Public and Private Keys: Party A needs to generate a pair of public and private keys in advance when registering the WAPI interface. The public key (rsa_third_pub) is provided to Party B. The private key is kept by yourself, and the private key is not disclosed to anyone. When requesting WAPI services, Party A shall encrypt the request parameters with Party B’s public key and sign the original data after MD5 with Party A’s private key. Upon receiving the request, Party B shall decrypt the data with Party B’s private key and check the original data after MD5 with Party A’s public key
Account Preparation
- Developers need to prepare the following information:
-
Generate a pair of public and private keys, and provide the public key to the platform;
-
Third-party application server IP;
- Contact the relevant people of the platform and provide the above two types of information. The platform prepares WAPI docking information for you, and provides you with the following information:
-
The unique identifier for third-party docking: app_id;
-
WAPI public key:rsa_wapi_pub
- RSA public and private key:
Password length:2048
Key format:PKCS#8
Interface rules
Transmission method: | https (the test environment temporarily uses http) |
---|---|
Signature Field: | Except for the sign field, all other required fields need to be signed |
The response status code: | 0 indicating successful processing; non-zero, indicating request error or system abnormality |
Request Address: | domain name + interface address |
Encryption Algorithm: | Java Encryption and Decryption Demo |
Domain Name and API Key
Production Environment
Domain Name: | https://baas.waas.group |
---|---|
app_id: | To be assigned |
rsa_wallet_pub: | To be allocated |
Test environment
Domain Name: | http://baas.dw2nn.com |
---|---|
app_id: | 8ee3794a7e5bd188c6af4fd7dda191f3 |
rsa_third_pub:
rsa_third_prv:
rsa_baas_pub:
Type | Token Name | Accuracy |
---|---|---|
memo | SRM | 8 decimals |
non-memo | VLX | 8 decimals |
Note
rsa_third_prv
is a third-party application private key, which is mainly used to encrypt request parameters. If it is a production environment, rsa_third_prv
is generated by the developer, and then the corresponding public key is provided to the platform. In order to simplify the developer connection process in the test environment, a set of third-party public and private keys and token names are directly provided here for developers to quickly connect.