🚧 Protocol v2.0 Coming Soon 🚧
We noticed you want to visit the protocol documentation page. While we’re happy to see you want to build with Request, we want to make you aware of the following.
We are currently upgrading the Request protocol version from v1 towards v2.0. The first version of this upgrade is available on test-net before the end of Q1 2019.
While you are free to develop your product or service using the documentation for v1, we highly encourage you to wait for v2.0. By waiting, your product/service will directly enjoy the features v2.0 adds to the network.
What does v2.0 bring?
Simple to use
Request gateways reduce the complexity of interacting with the blockchain. You don't need to manage different contracts, specific libraries, and gas (the calculable fee for every operation carried out on the Ethereum network). Gateways enable blockchain interactions as easily as any other SaaS, through HTTP APIs.
We ensure privacy and GDPR compliance. Data regarding your requests is encrypted and safeguarded using elliptic-curve encryption. And while all data is saved in a public blockchain to prevent interference, it can only be read by the parties involved in the request.
With every new version, Request can handle more and more transactions per second. That's because the bulk of the data is saved on IPFS (see below) instead of on the blockchain. What is stored on the blockchain is the hash (the proof of the data). That way, it can't be modified or manipulated. Transactions are batched and added to IPFS in bulk, which enables high throughput. And it leads to low costs as well.
Request is built on top of Ethereum, safeguarding security. Ethereum has been around the block for years, has seen intense usage, and remains secure. It ensures that data can't be changed or deleted by governments, third parties, or even by us. In addition, data exists on each node, so it can't just disappear. It's safe from the passage of time and tampering alike.