Last updated
Last updated
Open both a subscription and pay-as-you-go contract (not at the same time, as only one contract is allowed open at a time between a provider and client/delegate) with the sole data provider.
After a contract is open, there are some attributes that are configurable by the contract owner. Attributes such as IP white listing, cross-origin resource sharing (CORS), and per user rate limiting.
In order to read or write a contract configuration, the contract owner (with their private key) needs to authenticate with the data provider. This is done by making a GET
or POST
request with a signature. That request will look something like
When making a GET
request, you will get back some JSON structured like so.
Once you have the current state of the contract configuration. You can alter/change any aspect to the json and POST
it back to the data provider
If the contract is a subscription, it can be cancelled. Pay-as-you-go isn’t available to cancel as you can stop making requests as a form of cancelling (providers can cancel though). Closing a contract should also trigger a payout to the provider.
The <id>
is the contract id, <nonce>
is an integer that is larger than the last one. While this number is somewhat arbitrary, the recommendation is to use the current . If you need more granularity than per second, use milliseconds. And the <sig>
is the signature of <id>:<nonce>
. The signature produce should be hex encoded into a string for transmission (]. There is also a command line tool to creating this signature in the arkeo codebase, called