Executed

Launch of Retail dApp on Base Chain


ID 915511...0928

ID 915511...0928

Proposed on: May 22nd, 2025

Proposed on: May 22nd, 2025

Result details
Final Votes

Quorum

1.19M of 377.7K

Majority support

Yes

For

1.19M

Against

0

Abstain

0

Proposal

Summary

This proposal introduces the deployment of a Wirex Pay retail dApp on the Base chain, aiming to extend the reach of the Wirex Pay Chain’s non-custodial card infrastructure into one of the most active and scalable Layer 2 ecosystems. This strategic move is designed to increase transaction throughput, provide ultra-low gas fees for retail users, and accelerate adoption of WPAY-based DeFi and payment use cases.

Abstract

To drive broader adoption of the Wirex Pay platform and its non-custodial tools, we propose to launch a fully integrated retail dApp on Base, Coinbase’s Ethereum Layer 2 rollup. This dApp will allow users to:

  • Onboard using non-custodial wallets, email or passkey
  • Order and manage Wirex Pay virtual/physical cards
  • Spend stablecoins via Wirex Pay cards
  • Access fiat bank accounts with auto-conversion to stablecoins

The retail dApp will serve as a Web3 gateway into the Wirex ecosystem for thousands of Base-native users and developers, expanding stablecoin-based payments and enhancing real-world usability of the Wirex infrastructure.

Proposal Track

Standard Track

  • Discussion Period: 2 days
  • Voting Period: 3 days
  • Snapshot voting: Enabled

Justification: This proposal introduces strategic expansion to a new chain, involves deployment of DAO-managed assets, and requires alignment with the community’s roadmap for cross-chain presence.

Motivation

Current Situation

  • Wirex Pay currently operates on EVM-compatible networks with limited exposure on Base chain.
  • No direct deployment exists to capture retail activity from the Base ecosystem.
  • User onboarding is fragmented and lacks chain-native UX flows for new L2 communities.

Proposed Solution

  • Deploy a retail-oriented dApp natively on Base.
  • Integrate account abstraction, card ordering, and bank account features.
  • Enable stablecoin spending and fiat access through an intuitive UX.
  • Bootstrap with UI/UX focused on mobile-first retail onboarding and Web2-to-Web3 transitions.

Details

Core Features of the Base Chain Retail dApp

FeatureDescription
Non-Custodial OnboardingConnect non-custodial wallet or use email, passkey to access services
Card Ordering FlowOrder Wirex Pay virtual or physical cards via a decentralized flow
Retail SpendingUse stablecoins for real-world spending via Wirex Pay cards
Bank Accounts IntegrationAccess fiat accounts with automated conversion to supported stablecoins

Implementation Timeline

PhaseDurationDeliverables
Community discussion and vote1 weekProduct scope, Base network readiness, UI/UX wireframes
Go-Live1 weekLaunch dApp on Base mainnet with card ordering live
Marketing CampaignOngoing post-launchEcosystem push, user guides, Base-native awareness

Budget Considerations

  • No direct fund allocation is requested in this proposal.
  • Existing DAO developer resources and grant collaboration with Base Ecosystem Fund may be explored.
  • Future incentive proposals (airdrops or liquidity boosts) may be submitted separately based on adoption KPIs.

Benefits for Wirex Pay DAO

  • Cross-chain presence: Expands WPAY usage and liquidity to the Base ecosystem.
  • User growth: Taps into a fast-growing L2 retail and DeFi audience.
  • dApp visibility: Builds a high-performance UX hub powered by Wirex infrastructure.
  • Ecosystem synergy: Bridges assets and users across Wirex Pay Chain and Base.

On-chain Voting Structure

  • Duration: 72 hours
  • Quorum Required: >4% of total veWPAY supply
  • Approval Threshold: 50% of participating tokens

Voting Options

  • For: Approve the Base chain dApp deployment
  • Against: Reject the proposal
  • Abstain: No opinion
Final Votes

Quorum

1.19M of 377.7K

Majority support

Yes

For

1.19M

Against

0

Abstain

0

Final Votes
Status

Thu May 22, 04:05 pm

Draft created

Thu May 22, 04:05 pm

Published onchain

Sat May 24, 04:05 pm

Voting period started

Tue May 27, 04:05 pm

Voting period ended

Wed May 28, 06:06 pm

Proposal queued

Sat May 31, 03:47 am

Proposal executed