Request (REQ)

Overview

Request (REQ) market snapshot: Price $0.054983, market capitalization $43.80M, and reported 24-hour volume $3.85M.

Trading activity: Reported 24-hour volume equals 8.79% of market capitalization. The local markets snapshot lists Bithumb, Binance and LATOKEN among venues with observed trading activity.

YearBull indicators: YearBull Rank #403. Bull Score 57/100. YB Market Risk Low. This relative market-volatility label is not an investment-safety assessment. Cycle Early. Observed price change: 24h 0.36% · 7d 2.80% · 30d 2.92%.

Values are descriptive and should be read together rather than as a price forecast. Read the YearBull methodology. Snapshot date: 2026-09-20. Data history: 89 daily observations available in the latest 90-day window.

Methodology responsibility: YearBull’s analytical methodology and presentation rules are developed and maintained by Alan Zelvin, Founder & Lead Crypto Researcher. This note identifies responsibility for the methodology; it does not attribute authorship of this data snapshot.

What is Request (REQ)?

YearBull Project Summary: Request (REQ) is tracked by YearBull under the source identifier request-network. Source categories place the asset in the Ethereum Ecosystem Coins universe, with additional labels including Business Services, Polygon Ecosystem, Ethereum Ecosystem. Category labels describe market context; they do not prove project activity, adoption, or investment quality.

Source description

“What Is Request (REQ)? The Request (REQ) utility token, launched in 2017, ensures the performance and stability of the Request Network. The Request Network itself is an Ethereum-based decentralized payment system where anyone can request a payment and receive money through secure means. It removes the requirement for third parties in order to provide a cheaper, more secure payment solution that works with all global currencies. When a user creates a request for payment, they define to which address the payment needs to be allocated and what the amount is. The user can also define the terms and conditions of the payment, upgrading a simple request into an invoice. Once this is completed, the user can share their request to be paid by their counterparty. Every step is documented and stored on the Request network, allowing everyone involved to easily keep track of all the invoices and payments for accounting purposes. Request is also integrated with legislation across the world to remain compliant with the trade laws of each individual country. Who Are the Founders of Request? The founders of Request are Christophe Lassuyt and Etienne Tatur. Christophe Lassuyt is currently the chief financial officer at Request. Before this position, he co-founded MONEYTIS. Etienne Tatur is the chief technical officer of Request. Prior to this, he also co-founded MONEYTIS and worked as a lead developer at QOBUZ, a music streaming service. What Makes Request Unique? The payments on Request are performed by simply sending an invoice through the blockchain; the counterparty can then detect the request and pay it with one click in a peer-to-peer manner. The fact that the payments are push-generated instead of pull-generated is one of Request’s key advantages.”

This source-supplied description may contain old, promotional, or unverified claims and is not YearBull editorial analysis.

Request (REQ) project facts

  • Source tags: Business Services, Polygon Ecosystem, Ethereum Ecosystem
  • Recorded networks: Ethereum, Polygon Pos
  • Recorded launch or genesis date: 2017-10-07

Official links and contract records appear in Key Facts. Project details can change, so verify current information with the project.

Request (REQ) FAQ

How does Request turn a payment request into an invoice?

The project describes a workflow in which the sender specifies the recipient’s address, payment amount, and any applicable terms or conditions. These details can transform a basic payment request into an invoice. The completed request can then be shared with the counterparty, who can detect it and make a peer-to-peer payment.

How are invoices and payments recorded on the Request Network?

The project states that each step involved in creating, sharing, and settling a request is documented on the Request Network. This record is intended to let participants track invoices and payments for accounting purposes. It also describes requests as being stored on an immutable digital ledger that can serve as evidence for auditing activities.

Why does Request use Ethereum and IPFS in its payment system?

Request describes itself as an Ethereum-based decentralized payment system and says it leverages decentralized blockchains such as Ethereum and IPFS. According to the project, this architecture is intended to support security, privacy, and user data ownership while reducing reliance on third-party payment processors. Blockchain transactions still require fees to broadcast changes to the network.

What role does REQ play within the Request Network?

REQ is presented as the Request Network’s ERC-20 utility token and can be spent to use the network. The project also states that a portion of the REQ fee is burned, with the burn rate determined by factors including current supply and exchange rates with other currencies. REQ is based on the Ethereum platform.

Request metric comparison

255 daily observations are available from 2025-12-30 through 2026-09-16. Percentiles compare the latest value with the same-day analytical universe; a higher percentile means a larger observed value, not necessarily a better investment characteristic.

MetricCurrent30d ago90d agoChange vs 30dUniverse percentile
Price$0.0503$0.0504$0.0567-0.2%n/a
Market cap$40.04M$40.14M$42.18M-0.3%P94.1
YearBull Rank#1,501#2,606#1,098Improved 1,105P83.8
Bull Score45/10052/10058/100-7.0 ptsP52.1
Turnover1.14%3.31%3.84%-2.2 ptsP57.2
YB RiskLowLowLowUnchangedn/a
CycleEarlyMidEarlyMid → Earlyn/a

Median absolute daily movement 1.61%; distance from the highest local daily price -54.0%; circulating supply change +7.0%. These measurements are descriptive and do not predict future direction.

Editorial research. Identity, project facts, sources, and risks below belong to the dated editorial review. The live analytical snapshot above may be newer and is generated separately from stored market data.

Request (REQ) research overview

Request (REQ) is tracked by YearBull under the source identifier request-network. Source categories place the asset in the Ethereum Ecosystem Coins universe, with additional labels including Business Services, Polygon Ecosystem, Ethereum Ecosystem. Category labels describe market context; they do not prove project activity, adoption, or investment quality.

Market structure and supply

Observed market capitalization is about $41.81 million and reported 24 hour volume is about $226.3 thousand. That volume equals 0.54% of market capitalization in the dated snapshot. Current circulating supply is 796,694,831. The recorded maximum supply is 1,000,000,000. Circulating supply changed +7.0% across the available historical window. Reported volume and supply fields can change through source revisions, issuance, burns, migrations, or venue coverage.

Key risks and limits

Liquidity depth, holder concentration, contract or network controls, token issuance, venue availability, governance, and operational dependencies remain material. High YearBull Risk appeared on 0.4% of stored observations. Historical metrics describe the available YearBull record; they do not predict future returns. Contract addresses, network support, custody, and venue availability should be verified before use.

Primary sources and review scope

YearBull methodology | Official project website | Technical documentation or whitepaper | Source repository. Identity, categories, supply, and historical market fields were reviewed from locally stored source records on 2026-09-12. The live analytical snapshot may be newer than this editorial review.

Request (REQ): An Ethereum-Based Payment and Invoicing Network

Request Network is designed to let users create, share, and settle blockchain-based payment requests without relying on conventional payment processors. REQ is the network’s ERC-20 utility token, while the project’s payment records and fee model depend on underlying blockchain infrastructure.

Request Network turns payment requests into blockchain records

Request Network is described as a decentralized payment system built on Ethereum. Its core process begins when a user creates a payment request, identifies the destination address, and specifies an amount. Additional conditions can be added so that the request functions as an invoice rather than a simple transfer instruction.

The resulting request can be shared with the intended counterparty, who can detect it and pay it in a peer-to-peer transaction. project materials says that the steps involved in creating, tracking, and settling invoices are recorded on the Request network. This is intended to give the participants a persistent record for accounting and payment-history purposes, although the practical experience depends on the wallets, blockchains, and applications used by both sides.

Push-based invoicing limits the information a payer must disclose

Request presents its payment flow as push-generated rather than pull-generated. In this model, the recipient creates the request and the payer authorizes a payment to a specified address, rather than granting a third party continuing access to an account or payment method. The project identifies this structure as a way to avoid sharing account information with an intermediary.

The claimed benefit is a simpler peer-to-peer payment process with fewer processor-dependent steps. That does not remove every operational dependency: a transaction still has to be broadcast to an underlying blockchain, and the payer must use a compatible wallet or service. Network fees, wallet support, and the counterparty’s willingness to use the request format remain practical conditions for settlement.

REQ supplies the utility-token layer and fee mechanism

REQ is an ERC-20 token launched in 2017 and described as the utility token supporting the performance and stability of Request Network. project materials states that REQ can be spent to use the network. It also describes a fee model in which part of the REQ fee is burned, with the burn rate determined by the token’s supply and its exchange rate against other currencies.

The payment process also involves blockchain transaction fees. These are presented as costs required to broadcast changes to the relevant blockchain and, in project materials, as compensation for the parties that help reach consensus. The token-burn design therefore should not be confused with the underlying transaction fee: one relates to the project’s stated REQ fee mechanism, while the other is a network-level cost associated with blockchain activity.

Ethereum and Polygon are the recorded network relationships

project materials centers Request Network on Ethereum and states that requests using REQ are stored on an immutable digital ledger. Ethereum is also the stated base for the ERC-20 token. YearBull’s recorded project categories include both the Ethereum Ecosystem and Polygon Ecosystem, and the recorded networks are Ethereum and Polygon PoS.

Those records indicate that both ecosystems are relevant to the project page, but project materials does not explain how each network is used, which payment flows are available on Polygon, or whether all Request features operate identically across the two networks. Those implementation details matter because settlement costs, supported assets, confirmation behavior, and wallet compatibility can differ between chains.

Accounting, privacy, and compliance are stated design objectives

Request describes blockchain storage, including Ethereum and IPFS, as a way to support security, privacy, and user data ownership. Its ledger is also presented as evidence for auditing. These are design objectives and project descriptions rather than independent findings about every deployment or user workflow.

The source further claims that Request is integrated with legislation across countries so that it can remain compliant with local trade laws. public materials does not specify the jurisdictions covered, the responsible legal entities, the scope of that integration, or how compliance obligations are handled by users and counterparties. Those questions are material for businesses considering the system for invoicing or cross-border payments.

Founding history and historical market context

Request was launched on October 7, 2017, according to the recorded genesis date. project materials names Christophe Lassuyt and Etienne Tatur as founders, identifying Lassuyt as chief financial officer and Tatur as chief technical officer at the time described. It also associates both with the founding of MONEYTIS and identifies prior roles for Tatur at QOBUZ. These are supplied biographical claims, not independently assessed employment findings.

YearBull’s historical observations show that REQ’s recorded market behavior has varied substantially across the observation window. The strongest sequential rank was 19 and the weakest was 4,477, while the dominant cycle label was Early. The recorded median absolute daily move was 1.6%, and the window’s drawdown from its high was 51.67%. This context describes historical variability; it does not establish how Request Network is used or predict future token behavior.

Key takeaways

  • Request Network is designed around blockchain-based payment requests that can be expanded into invoices with amounts, destination addresses, and conditions.
  • The project presents push-based payments as a way to avoid sharing account information with third-party processors.
  • REQ is an ERC-20 utility token associated with network use and a stated fee-burning mechanism.
  • Ethereum is central to project materials, while YearBull also records Polygon PoS as a related network.
  • Ledger-based records are intended to support payment tracking and auditing, but actual workflows depend on wallets, supported chains, and counterparties.
  • The project makes broad privacy, data-ownership, and cross-border compliance claims whose scope requires further verification.

Risks and unresolved questions

  • public materials does not establish which Request features, assets, or payment flows are currently available on Ethereum versus Polygon PoS.
  • The scope and operation of the stated REQ fee and burn mechanism are not detailed, including how fees are calculated in specific transactions.
  • Blockchain transaction costs, wallet compatibility, and counterparty adoption may affect whether the invoicing workflow is practical for users.
  • The project’s claims about privacy, data ownership, auditing, and security are not accompanied here by independent testing or a detailed threat model.
  • The stated integration with laws across countries lacks jurisdiction-by-jurisdiction detail and does not clarify user or business compliance responsibilities.
  • The relationship between invoice data, IPFS storage, and on-chain records is not fully explained, including what information is public or difficult to remove.

YearBull Rank overview

Most recent YearBull Rank reading for request-network is #403.

Rank timeline (last 365 days)

Rank movement (nearest daily data).

Reading rule: lower numbers mean higher placement.

  • 7d window (2026-09-13): #1200 → #403 (up by 797).
  • 30d window (2026-08-21): #2215 → #403 (up by 1812).

YearBull Rank is an internal ordering on YearBull that positions a coin relative to the rest of the tracked universe. It is a context signal for relative placement, not an outcome forecast.

Cycle view: If the line is range-bound, treat changes as relative, not absolute.

Market access: If rank moves sharply, it may reflect venue mix changes rather than fundamentals.

Risk view: If the last month is chaotic, widen the lookback before concluding.

Liquidity framing: If the curve jumps, check whether the cohort moved too (relative effects).

Practical note: direction and persistence matter more than the last tick.

Editorial note: This analysis was prepared by the YearBull research team under the direction of Alan Zelvin, Founder and Lead Crypto Researcher. The assessment follows YearBull’s internal research methodology and editorial standards. Methodology · Editorial Policy
Research context

Related research and comparable assets

All hubs →

Similar coins

Popular by YearBull Rank

Request (REQ) Markets

Venue refresh pending. Markets last checked: 2026-07-26. The next refresh is queued in the hourly updater. Venue listings and volumes are stored snapshots, not live quotes.
Exchange Top Pair Stored 24h volume (snapshot) Source Trust Rank
Bithumb REQ/KRW $6.88M #71
Binance REQ/USDT $2.65M #2
LATOKEN REQ/USDT $979.24K #135
Coinbase Exchange REQ/USD $750.73K #1
Uniswap V3 (Ethereum) REQ/WETH $400.94K #174
Pionex REQ/USDT $385.31K #49
Bitvavo REQ/EUR $364.08K #26
DigiFinex REQ/USDT $343.80K #30
Gate REQ/USDT $291.30K #5
BloFin REQ/USDT $251.50K #79

Listings are ordered by reported snapshot volume. Source Trust Rank is an external venue-quality signal; it is not an endorsement or a solvency guarantee.