safu.

ARCHITECTURE

Architecture

Safu aims to make pending proposals and approval records discoverable onchain, so compatible clients can rebuild the queue without depending on the Safe Transaction Service database.

ONCHAIN COORDINATION GOALPLANNED
  1. 01PROPOSALS + APPROVALS

    Publish coordination

    Make complete pending proposals and their approval records available onchain for discovery and reconstruction.

  2. 02COMPATIBLE CLIENT

    Read independently

    Discover pending proposals and rebuild the queue and coordination history from onchain records.

  3. 03EXISTING SAFE

    Safe execution

    Existing Safe contracts enforce owners, threshold, signatures, and nonce. Compatible executors submit the authorized transaction.

    EXISTING AUTHORITY
COORDINATION RECORDS

Readable beyond one hosted index.
No owner or module authority.

Authorization and execution.
Provided by Safe.

Planned coordination model. Publication and reconstruction are still being researched; no coordination contract design has been selected.

THE COORDINATION LAYER

Make proposals
discoverable.

Safe already provides onchain authorization and approveHash. A hash alone does not reveal a pending transaction’s full contents or its coordination history.

Explore the security model
01 / PUBLICATION

Keep the full proposal available.

Publish the full pending transaction, so a client can inspect its contents and reconstruct its hash before execution.

02 / APPROVAL RECORDS

Find approvals with the proposal.

Make approval records and any required signature data discoverable alongside the proposal. Safe continues to decide which approvals authorize execution.

03 / RECONSTRUCTION

Rebuild the queue and history.

Let another client reconstruct pending proposals, approval records, and execution outcomes without relying on one service’s database or index.

CONTRACT COMPATIBILITY

Bring your existing Safe.

Supported account versions, with the same address, owners, and threshold.

Safe

SUPPORTED
  • 1.3.0
  • 1.4.0
  • 1.4.1
  • 1.5.0

Safe and SafeL2 variants. Current signing supports EOA owner wallets.

OpenZeppelin

UNDER EVALUATION

No OpenZeppelin contract is currently used.

TimelockController is a coordination candidate. No version has been selected for the product.

DESIGN GOAL

Reconstruct the queue.

Onchain records should support independent proposal discovery and coordination history. Indexes can help clients read them, while the data remains available beyond any one index.

WHAT COMES NEXTRoadmapView the roadmap