Technology

The open network for transaction requests. View roadmap

Image

Request is an open network for transaction requests. It allows anyone to create, store and access invoices and receipts in a universal, decentralized network.

By having all transaction requests in one place, companies with services like accounting, invoicing, payment processing, and auditing can plug into the same network and communicate with each other using the same single source of truth. It is built using blockchain technology and is completely decentralized. No one owns the network and the data remains verifiably immutable. Permissioned access means that the data remains accessible to those who need it, and completely private from those who don’t grant users ultimate control over their own data.


Request – The Universal Invoicing Network

Watch video
Image

Simple to use

Request gateways reduce the complexity of interacting with the blockchain. No 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.


Visit the documentation
  1. Ethereum

    Ethereum is an open-source, public, blockchain-based, distributed computing platform and operating system featuring smart contract functionality.
  2. IPFS

    The InterPlanetary File System is a protocol and network. It is designed to create a content-addressable, peer-to-peer method of storing and sharing hypermedia in a distributed file system.
  3. Request Node

    Nodes receive transactions (such as the creation of a request or its acceptance), batch them, and save them on IPFS and Ethereum. They abstract IPFS, Ethereum and gas for the users. They also store all data.
  4. Request Gateway

    Gateways make Request even easier to use than the nodes would on their own. They offer high-level APIs to Request users. These APIs then allow anyone to interact with Request seamlessly. That way anyone can manage their blockchain keys (if needed), identity, the purchase of gas, and so on. All using a clear, developer-friendly interface.
  5. Payment processors

    Payment processors connect Request with payment networks (such as BTC, Ethereum, Monero, and fiat networks). They detect payments and update the state of requests (like whether they have been paid).
  6. Apps

    Apps connect to the Request system to help manage payments. They can enable and streamline invoicing, accounting, crowdfunding, and more. These applications are not part of the protocol or its implementation but are built on top of it.


Request a feature

In progress

  • ERC20 requests

    20%
    Currency support
  • Encryption on testnet

    60%
    Privacy

Up next

  • ETH requests

    Currency support
  • Fiat

    Currency support
  • Access tokens for Request nodes

    Protocol v2
  • Smart requests on Ethereum

    Protocol v2
  • Warnings

    Protocol v2
  • Smart requests on other smart contract platforms

    Protocol v2
  • Ethereum storage optimizations (batching)

    Storage
  • Request node optimizations (batching, parallelization, throttling)

    Protocol v2
  • Privacy improvements (compartmentalization, share a request, remove access)

    Privacy
  • Consider alternative storages

    Storage
  • Multipayee

    Protocol v2
  • Multipayer

    Protocol v2
  • Identity

    Protocol v2
  • More payment networks and currencies

    Currency support

Done

  • Declarative fiat requests

    Feature available
    Currency support