Proposal discussion: Dapp Abstraction on Waves (DA wallets, registry, relayers)

WavesDAO
1

Hi everyone :waving_hand:

I’ve been working on a concept called Waves DA (dApp Abstraction), a pragmatic, Waves-native pattern that enables an “Account Abstraction-like” UX (fewer user signatures, sponsored execution) on the Waves Protocol.

The goal is simple:
:white_check_mark: users stay in control (EOA remains the authority)
:white_check_mark: apps can feel “real-time” (relayers execute actions on behalf of user)
:white_check_mark: target dApps see the user DA wallet as the on-chain caller (not the backend)

What it is (short version)

Each user creates a DA Wallet (a dApp acting as a proxy).

  • The DA wallet is owned by the user (EOA).

  • The user can authorize one or more relayers to call specific dApps/methods via the DA proxy (scoped permissions, optional expiry, spending limits).

  • A global registry maps EOA → DA so relayers never trust frontend-provided addresses.

  • DA setup is protected against init frontrun using a pendingOwner lock written before setScript.

  • After setup, relayers can execute actions via proxy() so users don’t need to sign every interaction.

Demo + article

I’m posting this as a discussion first, to collect feedback before opening a formal funding request.

Current status (PoC)

The PoC is end-to-end functional:

  • DA wallet creation + script deployment

  • secure init + registry registration

  • permission management

  • proxy calls to target dApps

  • relayer backend flow

  • refund validation guard (optional fee sponsorship)

Roadmap to production (target: early Q2 2026)

If there’s interest, I’d like to turn this PoC into a production-ready toolkit. Planned deliverables:

Core deliverables

  • Landing page: create & manage your DA wallet (clean UX for users)

  • JS library: easy integration for 3rd party projects

  • Production NodeJS relayer: proper backend script/service to run as a relayer

  • GitBook documentation: concepts + integration guides + examples

  • Hosting + domain

  • Maintenance & updates for 1 year

Improvements beyond the PoC

  • Full support for missing callable arg types in proxy:

    • binary (ByteVector) support

    • List support

  • Frontend completeness:

    • UI/UX Improvements

    • expose all missing methods (pause/unpause, etc.)

    • better Params management:

      • dropdowns for authorized relayers / dApps / methods

      • human-friendly expire presets (1h / 1d / 1w / 1m + custom)

      • limit spending/allowances more ergonomically

    • richer wallet management:

      • list WAVES & assets balances

      • improved withdraw/transfer UI

  • More signer options / login options

Funding request

I aim to submit a funding request for $10,000 in WAVES, covering the work above and 1 year of maintenance.

Why this matters for Waves

  • helps games/social apps reduce signature fatigue

  • enables “sponsored execution” patterns safely

  • keeps users in control (relayers never become owners)

  • doesn’t require protocol changes, fork, or special nodes

Thanks in advance, I would be happy to answer questions and adapt the roadmap based on feedback.

Christophe