Paralism Node RESTAPI

  1. Home
  2. Docs
  3. Paralism Node RESTAPI
  4. 1. SubmitRegistration Submit an on-chain request

1. SubmitRegistration Submit an on-chain request

Get method (upper limit of uplink data load is 16KB)

*Parameter: The content of the data chain

*Example: http://127.0.0.1:8080/SubmitRegistration?data=123456789

*Return example:

{
  "queuenum": "4",
  "requestid": "4wLGmMkJqxhaDxWK23TnTH8YVEy",
  "state": "queueing"
}

Post mode (on-chain data load limit is 2MB)

*Example: http://127.0.0.1:8080?SubmitRegistration

*Return example:

{
  "queuenum": "4",
  "requestid": "4wLGmMkJqxhaDxWK23TnTH8YVEy",
  "state": "queueing"
}

Return value:

queue, the sequence number of on-chain requests cached locally on the node. Returned when state is queuing

requestid, on-chain request id, base58 encoded string

state, on-chain status:

  • queue, the sequence number of on-chain requests cached locally on the node. Returns when the state is queuing.
  • onChainState, on-chain state:
  • queuing, the on-chain request is cached locally on the node and queued in the uplink.
  • onchaining1, the on-chain data has been added to the local consensus for constructing the sub chain.
  • onchaining2, the on-chain data has been added to the local consensus along with the business sub chain.
  • onchained, the on-chain data has been recognized by the global consensus and corresponding hyperblocks have been obtained in the business local chain, in mapSearchOnChain
  • matured, mature, after 4 global consensus cycles (which can be set by MATURATY_TIME), the obtained hyperblock is not discarded by the network, indicating that the hyperblock and related local chains have successfully solidified consensus across the entire network, and the possibility of being forked and discarded again is extremely low.
  • nonexistent, the submitted on-chain request was not found
  • failed, the on-chain request submission failed
  • unknown, an unknown problem has occurred.
Was this article helpful to you? Yes No