safu.

SAFE TRANSACTION COORDINATION

Safu

Onchain coordination for Safe accounts.

Pending transactions should be available beyond one service’s database. Safu aims to put complete proposals and approval records onchain, removing reliance on Safe Transaction Service.

How it works

In development. An early app prototype is available.

PROPOSAL RECORD / 001PLANNED
Studio SafeExample account
Proposed
NATIVE TRANSFER

Send 0.01 ETH

To recipient 0x7099…79C8
Operation
Call
Safe nonce
0
Transaction hash
Linked to approval records
Discoverable approvals0 / 2
Readable by independent clients

The full proposal should remain available to other clients.

COMPLETE PROPOSALSSHARED APPROVAL RECORDSINDEPENDENT CLIENTS

How it works

Publish the proposal. Share approvals. Rebuild the queue.

  1. 01

    Publish

    Make the full pending transaction available onchain. A hash alone cannot tell another client what owners are being asked to approve.

  2. 02

    Collect approvals

    Link discoverable approval records to the proposal, building on Safe’s existing approval mechanisms.

  3. 03

    Continue anywhere

    Let another client reconstruct pending work from chain records, without the original service’s database.

Keep coordination
within reach.

Safe already handles account authorization and execution. Today, pending transaction payloads and collected signatures commonly depend on Safe Transaction Service. That coordination dependency is what Safu aims to remove.

The goal is a shared record that humans, agents, and independent clients can read and reconstruct. Onchain publication and independent discovery are still being designed.

Roadmap Open app prototype ↗
app.safu.biz