Smart Contracts Overview
Last updated
Was this helpful?
Last updated
Was this helpful?
This page is missing the RequestToken, DAIbasedREQBurner, lockForREQBurn, ChainlinkConversionPath contracts
Request Network smart contracts are available here.
There are three types of contracts
Storage - These store Content Identifiers (CIDs) for Requests stored in IPFS.
Payments - These process various payment types, also known as Payment Networks, and are deployed across many Supported Chains.
REQ Token and Burn Mechanism - These lock, bridge, and burn REQ tokens each time a Request is stored.
Declares data hashes and collects the fees.
After a request has been sent to IPFS, the hash is declared to the whole request network system through the RequestHashStorage.
Anyone can submit hashes.
Manages the fees for the creation of a request.
This contract is the entry point to retrieve all the hashes of the request network system.
Performs an ERC20 token transfer with a payment reference and a transfer to a second address for the payment of a fee.
Performs an ERC20 token transfer with a payment reference and a transfer to a second address.
This contract performs an Ethereum transfer with a Fee sent to a third address and stores a reference.
This contract performs an Ethereum transfer sent to a third address and stores a reference.
This contract allows users to lock funds in an escrow and perform payments in ERC20. It contains a refund and emergency feature to unlock funds if needed.
This contract makes multiple conversion payments with a payment references, in one transaction.
This contract makes multiple payments with payment references, in one transaction.
This contract makes multiple payments with references, in one transaction, without conversion.
This contract swaps ERC20 tokens before paying a request such that the payer sends currency A, but payee receives currency B.
This contract uses a chainlink price feed to pay a request denominated in one currency (usually a fiat currency like USD) but paid in an on-chain currency. This variant supports ERC20 payments.
This contract uses a chainlink price feed to pay a request denominated in one currency (usually a fiat currency like USD) but paid in an on-chain currency. This variant supports native currency payments.
This contract combines "conversion" and "swap-to-pay". It executes an ERC20 swap before paying a request denominated in one currency (usually a fiat currency like USD) but paid in an on-chain currency. This variant supports ERC20 payments.
This contract allows minting requests as NFTs thus allowing them to be transferred. The owner of the request NFT receives the payment.
A contract that allows payment through the ERC20FeeProxy without having to make a function call.
A contract that allows payment through EthereumFeeProxy without having to make a function call.
A factory smart contract responsible for deploying ERC20SingleRequestProxy and EthereumSingleRequestProxy contracts.
Swap-to-Pay is different from Conversion. For details see
Smart Contract Addresses
Smart Contract Source