Base API
API Signatures
The authorization signature uses 'Ethereum message signing', assuming the ChainID of the relevant chain (e.g., ETH: 1, Silicon Mainnet: 2355).
For signatures used in snapshot submissions, verification is conducted using the ETH ChainID of 1 (the ChainID is included in the message).
Basic Response
Success
Fail
Error Message List
The following are basic error messages. Additional error messages may be present depending on the handling within each method.
Basic Validation
invalid_target
When managerName
does not match the name of the requested Manager.
request_timeout
Request timed out.
used_signature
When the signature value has already been processed within the allotted time (to prevent double usage).
invalid_cohort
When the CohortId
in the request does not match the CohortId
in the requestPath, or if the CohortId
is invalid or the cohort does not exist.
invalid_owner
When the owner in the request is missing or does not match the Owner of the CohortId
.
invalid_method
When the method is incorrect.
fail_to_authorization
When the authorization signature verified with the hash in the body does not match the Cohort Owner.
Basic Method Validation
invalid_members
When the members field is missing or not in a dictionary format.
exceed_limit
When the number of members being added exceeds the limit per request.
too_many_members
When the total number of members, after attempted additions, exceeds the overall limit.
invalid_address
When one or more addresses in the members field have an incorrect format.
invalid_weight
When the format of the weight in the members field is incorrect (must be an integer between 0 and uint32.max
).
pending_snapshot
When an add
request is sent during the snapshot prepare
status, but a submit
is expected.
Signature Generation Example
Example 1
Example 2
Last updated