# \[SEP 55\] \[Phase 2\] Fund Safenet Beta for SAFE Token Utility

**URL:** <https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967>\
**Category:** Phase 2: Voting\
**Created:** [April 2, 2026, 9:46am UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967 "2026-04-02T09:46:52Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![rimeissner](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/rimeissner/32/4_2.png) [@rimeissner](https://forum.safefoundation.org/u/rimeissner)\
**Post date:** [April 2, 2026, 9:46am UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/1 "2026-04-02T09:46:52Z")

</div>

**Authors:** Safe Ecosystem Foundation (SEF), represented by the Foundation Council  
**Created:** 2026-04-02

 ![Screenshot 2026-03-27 at 16.46.45](https://europe1.discourse-cdn.com/flex013/uploads/gnosis_safe/original/2X/6/6c54de7ad2e31e69eb4b4064a916ff9a2d4ed636.jpeg)

* * *

## Abstract

This proposal requests **5M SAFE tokens** from the SafeDAO treasury to subsidise **“Safenet Beta”** staking rewards over a 6 month period.

Safenet Beta is a permissioned validator network that attests Safe transactions onchain, in order to enforce transaction security and protect users from high-risk threats and malicious actors e.g. phishing, UI compromises.

The requested rewards are intended to:

- incentivise and bootstrap a minimum viable validator set

- activate SAFE token utility through staking & open delegation

- de-risk the consensus and incentive design before full decentralisation

* * *

## Proposal types

- [x] SEP: Governance proposals

- [] SEP: Constitutional proposals

- [] SEP: Other SEPs

* * *

## Proposal details

### Purpose and Background

Safenet was originally announced at the end of 2024 with a focus on solving cross-chain fragmentation. It has since [pivoted](https://safefoundation.org/blog/safenet-update-open-sourcing-our-work) towards a security-focused architecture in 2025, given the rising threat of sophisticated attacks and malicious organisations.

### The Problem

Since 2017, more than $20 billion in digital assets have been stolen through wallet compromises, malicious applications, and supply-chain exploits. These attack vectors increasingly affect:

- individuals managing personal assets

- DAOs and foundations managing treasuries

- protocol operators managing governance keys

- companies managing operational wallets

While wallets and security firms have improved user control over the years, transaction verification remains fragmented and manual, relying on local heuristics coming from a centralised database or UI-based trust. The EVM and non-EVM ecosystem lacks a scalable and transparent layer that can validate transaction safety in realtime, and truly prevent users from signing off on malicious transactions.

### What is Safenet?

Safenet is a validator-based network that enables wallet transaction security checks to be enforced onchain.

It replaces centralized transaction security infrastructure (single KMS servers, UI warnings) with a resilient network of independent validators who attest to transaction safety.

Safenet’s long-term goal is to provide a scalable, transparent enforcement layer that prevents high-risk or malicious transactions from being executed - even if a user signs them by mistake. See Safenet [Documentation](https://docs.safefoundation.org/safenet).

### What is Safenet Beta?

Safenet Beta is the first production iteration of Safenet. It launches with a small permissioned validator set and focuses on validating Safenet’s core assumptions under real-world load, specifically:

- whether the validator network can reliably process transaction checks at scale

- whether validator participation can be measured and incentivized

- whether SAFE staking and delegation can bootstrap economic security

The Beta itself intentionally launches with:

- A trusted permissioned validator set consisting of 6 validators run by [Gnosis](https://www.gnosis.io/), [Core Contributors](https://cc0x.eth.limo/), [Greenfield](https://greenfieldcapital.com/), [Safe Labs](https://safe.global/), [Rockaway](https://rockawayx.com/) and [Blockchain Capital](https://www.blockchaincapital.com/) with a minimum stake of 3.5M SAFE tokens

- A [UI](https://safefoundation.org/safenet#stake-safe) enabling SAFE holders to stake / unstake to Safenet validators

- Basic transaction checks implemented in the consensus protocol (see [here](https://www.notion.so/SafeDAO-proposal-vote-2e9a8a34f3b8800283c3c503bbb2fa62?pvs=21))

- [A transaction attestation explorer](https://explorer.safenet-beta.eth.limo/)

- DAO-funded rewards (if SEP-55 passes)

Advanced checks, slashing, and long-term sustainable fee-based rewards will follow in later phases.

### Who is this Network for?

- **Web3 users** wanting protection from blind-signing, phishing, and UI exploits

- **Wallet operators** looking to offer enforced onchain security rather than offchain warnings.

- **Security providers** looking to be rewarded for their transaction checking expertise

- **Validators** who want to run nodes, secure transactions, and earn fees for providing security.

### Type of Tx Checks

**Safenet Beta Checks (Static)**

- No [unexpected](https://github.com/safe-research/safenet/blob/main/validator/src/consensus/verify/safeTx/checks/multisend.ts) delegatecalls

- Upgrade only to [trusted](https://github.com/safe-research/safenet/blob/main/validator/src/consensus/verify/safeTx/checks/config/singletons.ts) singletons

- Only allow to add [trusted](https://github.com/safe-research/safenet/blob/main/validator/src/consensus/verify/safeTx/checks/config/modules.ts) modules

- Only [trusted](https://github.com/safe-research/safenet/blob/main/validator/src/consensus/verify/safeTx/checks/config/fallback.ts) fallback handlers can be set

- Only [trusted](https://github.com/safe-research/safenet/blob/main/validator/src/consensus/verify/safeTx/checks/config/guards.ts) guards can be set

**Future Checks (Context Specific)**

- Transfer/swap volumes & slippage management

- Allow/deny lists of transfer recipients/custom smart contracts

- Custom constraints around calldata and parameters that can be passed to smart contracts

- Actively exploited protocols/contracts

### Why this Proposal is needed

Safenet Beta delivers on a direction SafeDAO has been building toward since 2024. [SEP-21](https://forum.safefoundation.org/t/discussion-safe-token-utility/), which passed with 96.4% approval and 1,323 voters, introduced five foundational layers for SAFE token utility, with Security Abstraction being one of the focus areas. It explicitly described SAFE staking as “formalized staking for economic security across protocol components, governed through SafeDAO”. SEP-23 then funded a working group to research and prioritize token utility use cases, with staking as one of the stated focus areas.

More recently, community members have been pushing for concrete progress. Dennison Bertram’s June 2025 forum proposal on decentralizing Safe’s transaction service outlined a model where SAFE holders stake tokens to operate infrastructure nodes, with community members explicitly naming Safenet as the right venue to build this. Meanwhile, multiple token holders have raised concerns on the forum that token utility remains theoretical two years after SEP-21 passed. Safenet Beta answers these calls. It implements the staking and security abstraction model the community voted for in SEP-21, puts the SEP-23 research into practice, and gives SAFE a concrete utility function beyond governance for the first time.

Safenet’s long-term objective is for validator and delegator rewards to be funded by transaction fees paid by users / integrators and network usage. However, Safenet Beta’s system is not yet mature enough to rely on organic fee demand. So in order to:

- bootstrap validator participation

- ensure reliable uptime and attestation coverage

- kickstart token utility

Safenet Beta requires **temporary reward subsidies for the next 6 months.** As without subsidies, the Safenet Beta risks insufficient validator participation, low stake participation and weaker economic security signals.

 ![image (4)](https://europe1.discourse-cdn.com/flex013/uploads/gnosis_safe/original/2X/e/e0aa7816c32191609398d873a6bda033e2a781d6.jpeg)

### Relationship to SEP-54 (Resource Allocation Pause)

[SEP-54](https://www.notion.so/SafeDAO-proposal-vote-2e9a8a34f3b8800283c3c503bbb2fa62?pvs=21) paused all SafeDAO resource allocation to allow the Foundation to focus on structural changes, including the launch of Safe Labs and Safe Research. More than six months have passed since the pause took effect, meaning it can now be lifted by either the SEF Council or a SafeDAO governance vote. This proposal requests a narrow, one-time lift of the pause, scoped exclusively to the Safenet Beta allocation described herein. Approval of SEP-55 does not reopen general resource allocation. However, the experience of running this allocation, from reward design to distribution and evaluation, should feed directly into the design of whatever replaces [OBRA](https://forum.safefoundation.org/t/sep-8-outcomes-based-resource-allocation-framework-obra/4376) as SafeDAO’s resource allocation framework going forward. A successful Safenet Beta would also establish the foundation for a more targeted approach to SafeDAO resource allocation, one that is tied to concrete protocol infrastructure rather than broad ecosystem grants.

* * *

### Requested Funding

This proposal requests:

### 5,000,000 SAFE tokens

where:

- 4.5M tokens will be allocated for Safenet Beta staking rewards for a 6-month period with rewards distributed every 2 weeks.

- 0.5M tokens will be allocated to run an open RFP for Safenet staking interfaces.

* * *

### Reward Design

_Full reward details can be found [here](https://docs.safefoundation.org/safenet/staking/rewards)_

The proposed reward design follows these principles:

**Validators**

- Validators earn rewards based on:

- Validators receive a fixed commission on delegator rewards of 5%

- Validators receive rewards relative to their participation rate.

- Validators need to maintain minimum validator stake of 3.5M SAFE in order to be remain eligible for rewards.

**Delegators**

- SAFE holders may delegate SAFE to validators

- Delegators earn rewards proportional to delegated stake

- Delegators do not need to run infrastructure

**Rewards distribution**

- Rewards will be eligible for those who stake from April 7th, 2026 00:00:00 UTC onwards

- Calculated offchain every two weeks

- Distributed via a Merkle drop contract every two weeks

- Rewards distributed every 2 weeks

- Users must actively claim their rewards

- Rewards below 1,000 USD per two weeks will NOT require KYC (cf. full compliance requirements)

* * *

### Goals and Success Criteria (6 months)

The objective of the Safenet Beta rewards subsidy is to prove that:

**Technical**

- the validator network can process Safe transaction checks at scale

- validator participation is measurable and enforceable via reward eligibility

- onchain tx attestations are reliably produced and visible

**Economic**

- SAFE token staking and delegation can bootstrap significant economic security

- incentives align validators toward consistent performance

- the DAO can credibly point to SAFE token utility as a live mechanism

* * *

### Alternative Solutions?

**No rewards subsidy - Considered but not pursued**  
Without subsidies, Safenet Beta risks low validator participation and weak network learnings.

**SEF-only funding - Considered but not pursued**  
While SEF may support ecosystem initiatives, Safenet is a SafeDAO-level token utility initiative and should be validated through SafeDAO governance. [/details]

**Smaller reward allocation - Considered but not pursued**  
A smaller allocation risks being insufficient to incentivise consistent validator participation and meaningful delegation, especially given minimum stake expectations and the requirement to secure the network credibly.

* * *

### Implementation

**Timeline**

- Safenet Beta staking UI: live [today](https://staking.safenet-beta.eth.limo/)

- SAFE Rewards launch: From April 7th, 2026 (if DAO proposal is approved)

- Reward Distribution: Begins after the proposal is ratified but rewards will be calculated retroactively from April 7th, 2026 for a total of 6 months.

**Resourcing**

- [x] Own implementation possible

- [] Own implementation but with funding

- [] Request for technical support through Safe matter experts

**Additional Funding Request: UI RFP**

While a [minimal staking interface](https://staking.safenet-beta.eth.limo/), based on the code in [this repository](https://github.com/safe-fndn/safenet-staking-ui), is operated by Core Contributors, relying on a single interface introduces several risks:

- centralisation risk

- operational dependency

- single point of failure

To align with SafeDAO’s principle of resilient decentralised infrastructure, this proposal includes an additional request of **500,000 SAFE** tokens to:

1. run an open RFP for Safenet Beta staking interfaces

2. fund independent operators to provide a UI to stake/unstake SAFE and claim rewards

3. ensure Safenet Beta has multiple reliable frontends available to SAFE holders

The Safe Ecosystem Foundation (SEF) will:

- manage the RFP process

- evaluate submissions

- select suitable providers

- execute the grants and payout

* * *

### Effects & Impact Analysis

**Effects of this Proposal**

If passed, SEP-55 will have the following direct effects:

- 5M SAFE tokens will be transferred from the SafeDAO treasury to the SEF for distribution over a 6-month period

- A live, DAO-funded staking and delegation mechanism will be operational for the first time, giving SAFE a concrete utility function beyond governance

- Six permissioned validators will attest Safe transactions onchain, replacing centralised security warnings with an enforceable, transparent layer

**Pros**

- **Delivers on prior DAO mandates:** [SEP-21](https://snapshot.org/#/s:safe.eth/proposal/0x1d65ca5270b4aa1efaa7b7ca4e17976a99b802efcf678ac2909eb836b1662a29) (96.4% approval) and [SEP-23](https://forum.safefoundation.org/t/sep-23-obra-safe-token-utility-sprint-1/4891) explicitly committed SafeDAO to staking and security abstraction as token utility pillars.

- **Low trust assumptions for delegators:** SAFE holders can participate without running infrastructure, lowering the barrier to meaningful network participation.

**Cons**

- **Treasury cost with no immediate revenue offset:** The 5M SAFE subsidy is funded entirely by the DAO treasury with no fee income during Beta, before fee-based sustainability can be implemented.

- **Permissioned validator set introduces some centralisation:** The initial 6 validators are selected rather than open, which limits decentralisation during Beta. While intentional and time-bounded, it represents a trust assumption before full decentralisation.

**Risks**

- **Validator underperformance:** Validators who fall below the 75% participation threshold earn no rewards. If multiple validators underperform simultaneously, network attestation coverage could degrade, undermining the core security proposition.

- **Fee transition risk.** Safenet Beta assumes that organic fee demand will replace subsidies after 6 months. If wallet operator adoption or user transaction volume is insufficient by that point, the DAO may face pressure to extend subsidies.

* * *

### Governance Process & Compliance

This proposal is submitted on behalf of the Safe Ecosystem Foundation represented by the Foundation Council, and is intended to comply with SafeDAO governance requirements, including:

- forum discussion period

- snapshot vote

- SEF compliance requirements for treasury execution

This proposal follows the standard SEP-7 governance process as amended by [SEP-53](https://snapshot.org/#/s:safe.eth/proposal/0x140c7fb833f778d934661a969ae476eb400735b33d1a022eef828604abce6fa1), which removed sprint-type restrictions and allows any proposal to be submitted in any sprint. Given that no active governance season calendar has been in effect during the SEP-54 pause period, this proposal is submitted independently of a specific sprint cycle. It will go through the full SEP-7 process: forum discussion, maturity signaling by three delegates or Guardians holding a combined minimum of 60,000 SAFE, and a Snapshot vote including a “Make no changes” option. The Foundation Council members named in the disclaimers section will abstain from both signaling and voting.

* * *

### Disclaimers

The validators were determined based on technical expertise, pro-active outreach, as well as ability to show sufficient token holdings in order to provide the minimum stake of 3.5M tokens. It is planned that the validator set is updated and expanded in the future up until it is open and permissionless.

Safe Labs GmbH, Berlin, is a wholly owned subsidiary of SEF and the operator of Safe Wallet by Safe Labs interface, which creates a potential conflict of interest. The Foundation and its foundation council members will abstain from voting on this proposal.

Stefan George is a member of the SEF foundation council and founder of Gnosis who is running a Safenet Beta validator which creates a potential conflict of interest. GnosisDAO as largest Safe token holders is considered as legitimized to be a running one of the initial validators. Stefan will abstain from voting on this proposal.

Richard Meißner is a member of the SEF foundation council and shareholder of Core Contributors GmbH, Berlin, which creates a potential conflict of interest. Core Contributors worked on Safenet Beta based on a grant agreement and is therefore considered to be invaluable in gaining first-hand experience in operating a validator. Richard will abstain from voting on this proposal.

The minimum validator stake amount of 3.5M SAFE applies to all validators alike.

* * *

### Open Questions

None

* * *

### Copyright

Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).

---

<div class="post-metadata">

**Author:** ![LuukDAO](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/luukdao/32/159_2.png) [@LuukDAO](https://forum.safefoundation.org/u/LuukDAO)\
**Post date:** [April 2, 2026, 11:06am UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/5 "2026-04-02T11:06:13Z")

</div>

As a delegate with sufficient [voting power](https://boardroom.io/voter/0x31cd90C2788f3e390d2Bb72871f5aD3F1a4B22a1?protocol=safedao), I believe this proposal is ready to move to a vote

Excited to see Safenet move into this relevant direction. Fully in support.

---

<div class="post-metadata">

**Author:** ![corbinpage](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/corbinpage/32/3314_2.png) [@corbinpage](https://forum.safefoundation.org/u/corbinpage)\
**Post date:** [April 2, 2026, 2:15pm UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/6 "2026-04-02T14:15:00Z")

</div>

As a delegate with sufficient [voting power](https://boardroom.io/voter/0x31cd90C2788f3e390d2Bb72871f5aD3F1a4B22a1?protocol=safedao), I believe this proposal is ready to move to a vote.

Love seeing Safenet come to life!

---

<div class="post-metadata">

**Author:** ![devanon](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/devanon/32/684_2.png) [@devanon](https://forum.safefoundation.org/u/devanon)\
**Post date:** [April 2, 2026, 2:39pm UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/7 "2026-04-02T14:39:16Z")

</div>

As a Safe Guardian I believe this proposal is ready to move to a vote.

I welcome a utility for the SAFE Token aside from governance. I welcome a decentralized validator set providing transaction screening. I would like to see this validator set used for more than transaction screening in the future e.g. signature collection, decentralized gasless submission, and much more. I think the scope detailed here is a valid place to start for the network.

I especially approve of the approach regarding the UI i.e. no canonical UI. As the developer of Eternal Safe, pending this proposal passing, I would be willing to put forward a proposal to support SafeNet staking directly in the decentralized Eternal Safe UI.

---

<div class="post-metadata">

**Author:** ![gokuDAO](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/gokudao/32/3925_2.png) [@gokuDAO](https://forum.safefoundation.org/u/gokuDAO)\
**Post date:** [April 4, 2026, 3:08am UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/8 "2026-04-04T03:08:12Z")

</div>

As a delegate with sufficient [voting power](https://boardroom.io/voter/0x31cd90C2788f3e390d2Bb72871f5aD3F1a4B22a1?protocol=safedao), I think this proposal is ready to vote.

Lets make safe greate again

---

<div class="post-metadata">

**Author:** ![Ibrahim313](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/ibrahim313/32/4799_2.png) [@Ibrahim313](https://forum.safefoundation.org/u/Ibrahim313)\
**Post date:** [April 7, 2026, 1:23pm UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/9 "2026-04-07T13:23:13Z")

</div>

As a delegate with sufficient voting power, I think this proposal is ready to vote.

I want to participate in staking but have no clue where to start. @rimeissner can you please d.m about this.

---

<div class="post-metadata">

**Author:** ![tschubotz](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/tschubotz/32/4762_2.png) [@tschubotz](https://forum.safefoundation.org/u/tschubotz)\
**Post date:** [April 8, 2026, 7:41am UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/10 "2026-04-08T07:41:37Z")

</div>

> I want to participate in staking but have no clue where to start.

@Ibrahim313 Info on staking can be found on the Safenet landing page: [Safe](https://safefoundation.org/safenet#stake-safe) as well as the docs: [Overview - Safe Docs](https://docs.safefoundation.org/safenet/staking/overview)

---

<div class="post-metadata">

**Author:** ![klotzketten](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/klotzketten/32/4774_2.png) [@klotzketten](https://forum.safefoundation.org/u/klotzketten)\
**Post date:** [April 9, 2026, 8:52am UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/11 "2026-04-09T08:52:07Z")

</div>

Proposal has been moved to Phase 2 and is ready for voting! 🗳

> **[Snapshot](https://snapshot.org/#/s:safe.eth/proposal/0xb85ed0346bb07196786df5145e57f5e3e5054d35ba7d5f67594faaa6b7a98bcd)**

---

<div class="post-metadata">

**Author:** ![Malik\_ElBay](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/malik_elbay/32/178_2.png) [@Malik\_ElBay](https://forum.safefoundation.org/u/Malik_ElBay)\
**Post date:** [April 13, 2026, 6:42pm UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/12 "2026-04-13T18:42:56Z")

</div>

Thanks for putting this together. I’m supportive of SEP-55 and plan to vote in favor.

One small point I’d push back on: I don’t think the framing that a successful Safenet Beta would “establish the foundation for a more targeted approach to SafeDAO resource allocation” is quite right. The learnings from running this program (reward design, distribution, evaluation) are absolutely worth feeding into the OBRA successor framework. That part makes sense.

But the successor framework should draw on a much broader base of input: learnings from other DAOs, different allocation models, governance experiments across the space. Tying the design of that framework too closely to Safenet Beta specifically risks narrowing the conversation prematurely. The two things can happen in parallel without one defining the other.

Also just tried Safenet myself. Great experience so far, really works well.

---

<div class="post-metadata">

**Author:** ![adamhurwitz.eth](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/adamhurwitz.eth/32/167_2.png) [@adamhurwitz.eth](https://forum.safefoundation.org/u/adamhurwitz.eth)\
**Post date:** [April 15, 2026, 3:35pm UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/13 "2026-04-15T15:35:45Z")

</div>

# Safenet security

Security is the killer feature that impacts every person and organization. I’m excited to see [the reintroduction](https://x.com/safe/status/2039644935864123775) of Safenet after the move from focusing on multinetwork compatibility to security [in July 2025](https://x.com/safe/status/1940017568686956830).

Preventing frontend attacks by looking at most likely malicious actions submitted on the contract layer makes protection accessible to all types of people using Safe accounts.

@rimeissner shares a great [introduction of Safenet beta at ethCC](https://www.youtube.com/watch?v=VCfz3P2m2xM) for those who haven’t seen it yet!

# Future Safenet uses

- I agree on important future uses mentioned by @devanon like signature collection and decentralized gasless submission.
- After the Safenet launch event at Devcon Bangkok in 2024 [I looked forward to multinetwork Safe actions](https://x.com/adamshurwitz/status/1865677310885851496) like managing owners, settings, app sign ins, and permissions. These still are possible with long term success of Safenet.
- For context on multinetwork actions, there is an Ethereum wide initiative on compatibility with the [Ethereum Interop Layer EIL](https://x.com/ethinteroplayer).
  - For example in the Safe ecosystem @marc and [Candide Labs are building towards multinetwork Safes](https://x.com/heymarcopolox/status/2021246469974417853)

# SAFE token

This is a big opportunity for $SAFE token to help secure the [$1.4 trillion of USD value processed with Safe accounts](https://x.com/safe/status/2006379385226662061?s=20).

---

<div class="post-metadata">

**Author:** ![adamhurwitz.eth](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/adamhurwitz.eth/32/167_2.png) [@adamhurwitz.eth](https://forum.safefoundation.org/u/adamhurwitz.eth)\
**Post date:** [April 20, 2026, 5:50pm UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/14 "2026-04-20T17:50:51Z")

</div>

@rimeissner, Are txs submitted to Safenet from account interfaces like Safe native app and Ambire only available for specific Safe implementations?

I’m sharing Safenet updates to a crypto performance and tax tracking team who’s asking about compatibility with ERC-4337 accounts and I don’t see ERC-4337 mentioned in the [docs](https://docs.safefoundation.org/safenet/overview/introduction).

I estimate that it’s up to the Safe frontend apps to submit the tx details to Safenet. Therefore all Safe implementation types, including ERC-4337, would be compatible because it is based on the info submitted to and processed by Safenet.

---

<div class="post-metadata">

**Author:** ![rimeissner](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/rimeissner/32/4_2.png) [@rimeissner](https://forum.safefoundation.org/u/rimeissner)\
**Post date:** [April 21, 2026, 9:24am UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/15 "2026-04-21T09:24:21Z")

</div>

In the Beta Phase only Safe Multisig Transactions are supported. As the current ERC-4337 implementation relies on Module transactions they cannot be checked yet. That being said we are considering module transactions, as they play an essential role in the Safe Ecosystem, and we will have to evaluate what is most feasible to include in the next iteration.

---

<div class="post-metadata">

**Author:** ![klotzketten](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.safefoundation.org/klotzketten/32/4774_2.png) [@klotzketten](https://forum.safefoundation.org/u/klotzketten)\
**Post date:** [April 27, 2026, 8:55am UTC](https://forum.safefoundation.org/t/sep-55-phase-2-fund-safenet-beta-for-safe-token-utility/6967/16 "2026-04-27T08:55:34Z")

</div>

[Vote](https://snapshot.org/#/s:safe.eth/proposal/0xb85ed0346bb07196786df5145e57f5e3e5054d35ba7d5f67594faaa6b7a98bcd) has reached quorum, and has closed as Accepted! 🍾

Round 1 rewards for Safenet Staking have now been [distributed](https://forum.safefoundation.org/t/safenet-beta-rewards-distribution-period-1/6991).

> **[Snapshot](https://snapshot.org/#/s:safe.eth/proposal/0xb85ed0346bb07196786df5145e57f5e3e5054d35ba7d5f67594faaa6b7a98bcd)**

> [@Safenet Beta Rewards Distribution - Period 1](https://forum.safefoundation.org/t/safenet-beta-rewards-distribution-period-1/6991):
>
> Summary Following the approval of [SEP-55](https://snapshot.org/#/s:safe.eth/proposal/0xb85ed0346bb07196786df5145e57f5e3e5054d35ba7d5f67594faaa6b7a98bcd), the first Safenet Beta reward period has concluded. Rewards have now been distributed by the Safe Ecosystem Foundation. Details Reward period: April 7, 2026 – April 21, 2026 Calculation methodology: Rewards were calculated according to the rules defined in the [Safenet docs](https://docs.safefoundation.org/safenet/staking/rewards) as per [SEP-55](https://snapshot.org/#/s:safe.eth/proposal/0xb85ed0346bb07196786df5145e57f5e3e5054d35ba7d5f67594faaa6b7a98bcd) Distribution transaction: [https://app.safe.global/transactions/tx?safe=eth:0x8cf60b289f8d31f737049b590b5e4285ff0bd1d1&id=multisig\_0x8CF60B289f8d31F737049B590b5E4…](https://app.safe.global/transactions/tx?safe=eth:0x8cf60b289f8d31f737049b590b5e4285ff0bd1d1&id=multisig_0x8CF60B289f8d31F737049B590b5E4285Ff0Bd1D1_0x53de3b97560824bbe774b2290e70bfdc37c5b9c502ac5e62d652e5f24190dc2a)
