safu.

ROADMAP

Roadmap

The goal is a shared onchain record of pending proposals and approvals, readable without Safe’s hosted transaction service or Safu’s database.

Proposal foundationWorking
Onchain coordinationDesign
Clients & devicesPlanned

CURRENT

A portable
proposal format.

The local prototype packages proposals and owner signatures for exchange. Onchain publication comes next.

  • Complete proposals

    Keep all transaction fields in one portable format.

    ✓

  • Proposal exchange

    Export proposals and owner signatures.

    ✓

  • Proposal integrity

    Check a proposal against its transaction hash.

    ✓

Local prototype. No onchain proposal store yet.

IN PROGRESS

Rebuild the
pending queue.

Publish complete pending proposals and readable approval records onchain. Let clients discover and reconstruct the queue without Safu’s database.

ONCHAIN RECORD / RESEARCH

Full pending proposalsTransaction + approval records
DiscoverReconstruct the queue

Safe already supports onchain hash approvals. This work makes the complete pending proposal and its approval record discoverable.

Design and research. The onchain format and publication model remain open.

FUTURE

Use the queue
from any client.

A browser interface and agent tools can share the same public record. New signing methods are a separate track.

app.safu.bizPlanned application. Not live yet.

  • Multiple clients

    Read one proposal record from different applications.

  • Agent tools

    Discover pending work through the shared public record.

  • Optional device approvals

    Explore passkeys alongside existing signing methods.

  • Independent recovery

    Test access without Safu’s domain or the original devices.

Planned capabilities. No release dates yet.

BEFORE THE NEXT STEP

Before
release.

Verify independent discovery and reconstruction before releasing the coordination layer. Test new signing methods on their own track.

Our security approach

  1. Rebuild without Safu

    Find pending proposals and approval records with a fresh client.

  2. Test missing services

    Keep coordination usable when a hosted index is unavailable.

  3. Review new signers

    Test device approvals and recovery separately as those features arrive.