Latest Request (REQ) News Update

By CMC AI
18 January 2026 07:13AM (UTC+0)

What is the latest news on REQ?

TLDR

Request navigates privacy partnerships and security challenges while upgrading its payment infrastructure. Here are the latest updates:

  1. Private Payroll Integration (5 September 2025) – Partnered with Aleo Network to enable confidential crypto payrolls, processing $3.7M in ALEO tokens post-launch.

  2. Security Breach Patch (15 September 2025) – Front-end exploit drained $3M from a user; enhanced monitoring deployed.

  3. Checkout API Upgrade (5 November 2025) – Streamlined integrations and customizable payment widgets for developers.

Deep Dive

1. Private Payroll Integration (5 September 2025)

Overview:
Request Finance integrated with Aleo Network to offer private, compliant payroll transactions. This allows businesses to automate payments while hiding sensitive details like salaries and vendor addresses on-chain. Aleo’s zero-knowledge cryptography ensures auditability without exposing data.

What this means:
This is bullish for REQ as it taps into growing demand for confidential B2B payments. The $3.7M processed in weeks signals early adoption, though broader traction depends on enterprise uptake. (Binance News)

2. Security Breach Patch (15 September 2025)

Overview:
A phishing attack exploited a spoofed contract via Request’s front-end, draining $3M from a user’s multi-sig wallet. The flaw was patched, and additional safeguards were added.

What this means:
This is bearish short-term, as breaches erode trust. However, the isolated impact (one user) and swift fixes mitigate systemic risks. Monitoring future audits and user sentiment is critical. (Binance News)

3. Checkout API Upgrade (5 November 2025)

Overview:
Request revamped its Checkout and Payment Widget using a modular UI registry, simplifying integrations for developers. The update supports cross-chain payments and recurring subscriptions.

What this means:
This is neutral-to-bullish, as improved tooling could accelerate adoption by fintech apps. However, competition in crypto payment APIs (e.g., Stripe, Circle) remains fierce. (Request Network)

Conclusion

Request balances innovation in privacy-focused payments with post-breach resilience. The Aleo partnership and API upgrades position it as a niche player in enterprise crypto transactions, but regulatory scrutiny around privacy tools and security vigilance remain key hurdles. Will Request’s compliance-first approach attract cautious institutions?

What are people saying about REQ?

TLDR

REQ holders are buzzing between governance votes and security jitters. Here’s what’s trending:

  1. Governance activation – Voting live for community contributions

  2. Breakout hopes – Traders eye $0.1650 as next target

  3. Burn mechanics – Monthly token burns hit $71k+ in October

Deep Dive

1. @RequestNetwork: Governance voting goes live 🗳️ bullish

"REQ holders can now vote for the Q3 winner in our Discord governance channel."
– @RequestNetwork (56.5K followers · 4.8K impressions · 2025-11-27 10:16 UTC)
View original post
What this means: This is bullish for REQ because active governance participation could strengthen community alignment and protocol upgrades, though voter turnout (not disclosed) will determine real impact.

2. CoinMarketCap: Trader eyes $0.1650 breakout 📈 bullish

"REQ surged to $0.1552 before retracing to $0.1520 – entry zone $0.1510-$0.1525 with TP3 at $0.1650."
– CoinMarketCap Community Post (Aug 2025)
View original post
What this means: This is bullish for REQ as the setup suggests trader confidence in continued momentum, though the 24H high of $0.1552 (now 30% above current $0.107) shows volatility risk.

3. @RequestNetwork: October burn reduces supply 🔥 neutral

"Burned 443 REQ ($71,337) – total burned now 582,846 tokens."
– @RequestNetwork (56.5K followers · 3.1K impressions · 2025-10-31 14:20 UTC)
View original post
What this means: This is neutral for REQ because the burn represents just 0.07% of circulating supply, unlikely to materially affect scarcity, but signals ongoing commitment to deflationary mechanics.

Conclusion

The consensus on REQ is mixed, balancing governance momentum and trader optimism against modest token burns and a 90-day price decline (-15.59%). Watch for Q1 2026 updates on the Aleo Network partnership – their privacy-focused payroll integration processed $3.7M in ALEO tokens during testing, potentially expanding REQ’s B2B use cases.

What is next on REQ’s roadmap?

TLDR

Request Network’s roadmap focuses on developer tools, governance, and payment integrations.

  1. New Developer Docs (Q4 2025) – Interactive guides and use-case-driven documentation.

  2. Best Pull Request Voting (November 2025) – Community-driven governance for protocol improvements.

  3. Recurring Payments Expansion (Ongoing) – Enhanced automation for payroll and subscriptions.

Deep Dive

1. New Developer Docs (Q4 2025)

Overview: Request Network is overhauling its developer documentation to include interactive demos, clearer navigation, and real-world use cases (Request Network). This aims to lower entry barriers for builders integrating crypto payments or invoicing.

What this means:
- Bullish: Streamlined onboarding could attract more developers, boosting ecosystem growth.
- Risk: Delays or unclear examples might slow adoption.

2. Best Pull Request Voting (November 2025)

Overview: REQ holders vote quarterly via Discord to reward community contributions that enhance the protocol (Request Network).

What this means:
- Bullish: Decentralized governance strengthens community alignment and innovation.
- Risk: Low voter turnout could centralize decision-making.

3. Recurring Payments Expansion (Ongoing)

Overview: Request Network is scaling its automated payout system for subscriptions, payroll, and vendor payments, emphasizing on-chain transparency (Request Network).

What this means:
- Bullish: Recurring use cases could drive sustained REQ burns (167k tokens burned in 2024).
- Risk: Competition from platforms like Utopia Labs or Sablier may pressure adoption.

Conclusion

Request Network is prioritizing developer experience, community governance, and payment automation to solidify its position in crypto invoicing. While partnerships (e.g., Aleo for private payrolls) and burns add momentum, success hinges on balancing decentralization with execution speed. How might broader crypto adoption trends amplify or challenge these efforts?

What is the latest update in REQ’s codebase?

TLDR

Request Network's codebase recently introduced cross-chain payment flexibility and enhanced encryption features.

  1. Meta Payment Network (June 2024) – Multi-network invoicing via single requests.

  2. Lit Protocol Integration (October 2024) – Encrypted Requests with selective data visibility.

  3. Wallet Compatibility Expansion (October 2024) – Broadened support for wallet connection kits.

Deep Dive

1. Meta Payment Network (June 2024)

Overview: Enabled a single payment request to accept multiple currencies across chains (e.g., USDC/USDT on Ethereum, Polygon, etc.).
This update replaced the previous single-network limitation, allowing payers to settle invoices using their preferred chain and stablecoin. Developers implemented a "sub-payment network" structure, reducing friction for businesses operating across ecosystems.

What this means: This is bullish for REQ because it simplifies cross-chain payments, potentially increasing adoption by enterprises with multi-chain treasuries. (Source)

2. Lit Protocol Integration (October 2024)

Overview: Added end-to-end encryption for sensitive payment requests using Lit Protocol’s decentralized key management.
The integration allows payers/requesters to control data visibility (e.g., hiding invoice amounts from public ledgers while maintaining auditability). This addresses privacy concerns for institutional users.

What this means: This is neutral for REQ – while enhancing enterprise appeal, encryption complexity could marginally slow transaction processing. (Source)

3. Wallet Compatibility Expansion (October 2024)

Overview: Updated Request Invoicing’s web components to support any EIP-1193 compliant wallet connection kit.
This enables compatibility with RainbowKit, Web3Modal, and others, reducing integration time for developers building on Request.

What this means: This is bullish for REQ as it lowers barriers for dApp builders, encouraging ecosystem growth. (Source)

Conclusion

Request’s codebase is prioritizing enterprise-grade flexibility (cross-chain support) and privacy (Lit encryption), while streamlining developer onboarding. With transaction volume hitting record highs in October 2024, will these updates drive sustained protocol usage growth? Monitor monthly burned REQ tokens as a proxy for network activity.

CMC AI can make mistakes. Not financial advice.