Overview of wallet authentication & Orderly keys
chainId
will be the id of the chain connected, which must be supported by Orderly.
Registration
and AddOrderlyKey
types are entirely processed off-chain, which is why the verifyingContract
is set to 0xCcCCccccCCCCcCCCCCCcCcCccCcCCCcCcccccccC
.
ed25519
elliptic curve standard for Orderly keys. Users can generate Orderly keys using any public ed25519
libraries and then be added to any account through the REST API.
An Orderly key is necessary to perform API authentication.
Orderly keys can have different scopes. A read
scope API can access all private read-only APIs, and a trading
scope can, in addition, access all order APIs (create order, batch create order, edit order, cancel order, cancel order by client_order-Id, cancel orders in bulk, batch cancel orders, batch cancel orders by client_order_id).
Orderly keys also have expirations for security reasons. The maximum allowed expiration of an Orderly key is 365 days.
Follow the following steps to add a new Orderly key on Orderly:
Generate an ed25519 key-pair
Obtain signature from EIP-712
Name | Type | Required | Description |
---|---|---|---|
brokerId | string | Y | Builder ID, the valid list can be found [here] |
chainId | int | Y | Chain ID of registering chain (within those that are supported by the Network) |
orderlyKey | string | Y | ed25519 public key |
scope | string | Y | valid scopes are read , trading and asset . Multiple scopes can be sent, comma separated |
timestamp | timestamp | Y | timestamp in UNIX milliseconds |
expiration | timestamp | Y | Expiration time of the key in UNIX millisecondsMaximum allowed expiration is 365 days from add |
Add Orderly key