Difference between revisions of "Request Network (REQ)"
m (1 revision imported) |
|||
Line 1: | Line 1: | ||
{{Crypto_info_template|launch = 20-10-2017|total_supply = 999.999.999|type = Token}} | An open network for [[transaction]] requests. It allows anyone to create, store and access invoices and receipts in a universal, [[decentralized]] network.{{Crypto_info_template|launch = 20-10-2017|total_supply = 999.999.999|type = Token}} | ||
== Basics == | == Basics == | ||
* Launched on: | * Launched on: | ||
* [[DeFi]] | * [[DeFi]] | ||
* "''[https://fynestuff.com/chainlink-story-analysis/ Aims] (to) become the de facto standard for exchanging [[fiat]] with cryptos."'' | * "''[https://fynestuff.com/chainlink-story-analysis/ Aims] (to) become the de facto standard for exchanging [[fiat]] with cryptos."'' | ||
* From their [https://request.network/en/technology/ website] (21-4-2020): | * From their [https://request.network/en/technology/ website] (21-4-2020): | ||
Line 10: | Line 9: | ||
== History == | == History == | ||
== Audits & Exploits == | |||
* [https://request.network/en/technology/ It says] (21-4-2020) it is on 30% of an 'Encryption security audit'. | |||
=== Bugs/Exploits === | |||
== Governance == | |||
=== Admin Keys === | |||
=== DAO === | |||
=== Treasury === | |||
* [https://blog.bancor.network/nexus-mutual-joins-30-daos-adopting-bancors-dao-treasury-management-solution-2eb60b762259 Plans] to [[stake]] their treasury (or parts of it) in [[Bancor Token (BNT)|Bancor]] V3 (9-3-2022). | |||
== Token == | == Token == | ||
=== | |||
=== Launch === | |||
=== Token allocation === | === Token allocation === | ||
== Tech == | == Tech == | ||
* [[Whitepaper]] can be found [insert link here]. | * [[Whitepaper]] can be found [insert link here]. | ||
* Consensus Algorithm: | * [[Consensus]] Algorithm: | ||
* Capacity (TPS): | * Capacity (TPS): | ||
* [https://request.network/en/technology/ Uses] (21-4-2020) [[Ethereum]], [[IPFS]] plus Request [[nodes]] and Request Gateways: | * [https://request.network/en/technology/ Uses] (21-4-2020) [[Ethereum]], [[IPFS]] plus Request [[nodes]] and Request Gateways: | ||
''"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. '' | ''"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. '' | ||
''Gateways make Request even easier to use than the nodes would on their own. They offer high-level [[API]]s 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."'' | ''Gateways make Request even easier to use than the nodes would on their own. They offer high-level [[API]]s 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."'' | ||
== Oracle Method | == Oracle Method == | ||
== Privacy Method | == Privacy Method == | ||
Their [[roadmap]] states they want to [https://request.network/en/technology/ work towards] (21-4-2020): ''"Privacy improvements (compartmentalization, share a request, remove access)"'' | Their [[roadmap]] states they want to [https://request.network/en/technology/ work towards] (21-4-2020): ''"Privacy improvements (compartmentalization, share a request, remove access)"'' | ||
== Roadmap == | == Roadmap == | ||
* Can be [https://request.network/en/technology/ found here] (21-4-2020). | * Can be [https://request.network/en/technology/ found here] (21-4-2020). | ||
* It says it is on 20% of V2, 60% of their explorer, 50% of Multis integration. | * It says it is on 20% of V2, 60% of their [[explorer]], 50% of Multis integration. | ||
* Up next, with no timeline are: [[FIAT]] support, 'smart requests on Ethereum and other platforms', privacy options. | * Up next, with no timeline are: [[FIAT]] support, 'smart requests on Ethereum and other platforms', privacy [[options]]. | ||
== Usage == | == Usage == | ||
Line 49: | Line 59: | ||
=== Cons === | === Cons === | ||
== Competition == | == Competition == | ||
== Team, investors, Partners == | |||
== Team, investors, | |||
=== Team === | === Team === | ||
=== Investors === | === Investors === |
Latest revision as of 04:56, 21 March 2022
An open network for transaction requests. It allows anyone to create, store and access invoices and receipts in a universal, decentralized network.
Type | Token |
---|---|
Total supply | 999.999.999 |
Basics
- Launched on:
- DeFi
- "Aims (to) become the de facto standard for exchanging fiat with cryptos."
- From their website (21-4-2020):
"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."
History
Audits & Exploits
- It says (21-4-2020) it is on 30% of an 'Encryption security audit'.
Bugs/Exploits
Governance
Admin Keys
DAO
Treasury
Token
Launch
Token allocation
Tech
- Whitepaper can be found [insert link here].
- Consensus Algorithm:
- Capacity (TPS):
- Uses (21-4-2020) Ethereum, IPFS plus Request nodes and Request Gateways:
"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.
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."
Oracle Method
Privacy Method
Their roadmap states they want to work towards (21-4-2020): "Privacy improvements (compartmentalization, share a request, remove access)"
Roadmap
- Can be found here (21-4-2020).
- It says it is on 20% of V2, 60% of their explorer, 50% of Multis integration.
- Up next, with no timeline are: FIAT support, 'smart requests on Ethereum and other platforms', privacy options.
Usage
Projects that use or built on it
- From their website (21-4-2020):
Gilded (bookkeeping), Reqify (Shopify plugin), REQLoot (Online game) an WooReq (WooCommerce puglin).
Pros and Cons
Pros
Cons
Competition
Team, investors, Partners
Team
Investors
Partnerships
- Has partnerships with Digi Global
- Partners (22-1-2018) with Chainlink
- According to the website (21-4-2020): Gilded (which is build with Request), Maker and Multis. Kyber, Y Combinator, WSBA, ABC and PwC France.