Following the adoption of SEP-55, the Safe Ecosystem Foundation (SEF) received the mandate to run an open RFP process to fund independent operators enabling SAFE staking on Safenet Beta.
Background
Currently, only one staking interface is publicly available: https://staking.safenet-beta.eth.limo/, based on open-source code in this repository.
Relying on a single interface introduces centralisation risk, operational dependency, and a single point of failure.
At the same time, broader adoption of SAFE staking requires reaching users through a variety of platforms and user experiences.
To address both goals, this RFP is designed to:
- Increase resilience through multiple independent, permissionless interfaces
- Expand adoption via integrations into existing platforms and services
SEF will manage the RFP process, evaluate submissions, select suitable providers, define milestones, and execute the grants.
What we’re looking for
We are inviting teams or entities to build and operate solutions that enable SAFE holders to:
- Stake SAFE
- Unstake SAFE
- Claim rewards
Solutions may take different forms, including:
- Non-custodial, permissionless staking interfaces
- Smart contract wrappers or automation layers
- Custodial or integrated staking offerings
Our goal is to support a diverse ecosystem of staking access points serving different user segments.
RFP Structure: Two Tracks
Applicants should apply to one of the following tracks.
Track A: Permissionless Non Custodial Interfaces Resilience Focus
Goal:
Reduce reliance on a single UI and ensure robust, decentralised access to Safenet staking.
Typical examples:
- Web UIs similar to the current reference implementation
- IPFS hosted frontends with ENS domains
- Alternative UX implementations such as mobile or CLI
Requirements:
- Fully non custodial
- Open source frontend code
- Direct interaction with Safenet staking contracts with no custodial intermediary
- Support:
- Wallet connection such as injected wallets, WalletConnect, or Safe Apps
- Staking, unstaking, and reward claiming
- Target uptime of at least 95 percent
Nice to have:
- Alternative hosting such as IPFS and ENS
- UX improvements compared to the reference UI
- Additional transparency features such as validator insights or simulations
Track B: Integrated Custodial Wrapper Solutions Adoption Focus
Goal:
Expand access to SAFE staking via platforms users already trust and use.
Typical examples:
- Wallet integrations
- Staking services
- Centralised platforms
- Smart contract wrappers optimizing staking strategies
Open source:
- Not strictly required
- Applicants must provide sufficient technical documentation for evaluation
Nice to have:
- Existing user base or distribution channel
- UX that abstracts validator selection or optimizes yield
- Reporting, analytics, or automation features
Guardrails:
- Solutions must not obscure or misrepresent underlying staking mechanics
- Users must not be exposed to undisclosed risks
- SEF reserves the right to exclude solutions introducing excessive custodial or counterparty risk relative to their benefits
Shared Baseline Requirements
- Solution must:
- Enable staking, unstaking, and reward claiming
- Integrate with Safenet Beta contracts
- Must meet agreed reliability and security standards defined during evaluation
- Applicant must be an individual or legal entity able to pass SEF AML and compliance checks
Compensation
Up to 5 operators will be selected across both tracks.
Each approved operator may receive a grant of up to 100,000 SAFE, subject to achieving agreed milestones.
Grant size, duration, and milestone structure will be defined with each selected operator.
SEF may prioritise diversity across implementation approaches and user segments when selecting grantees.
Applications are accepted on a rolling basis until all slots are filled.
How to apply
Send an email to rfp+staking@safefoundation.org
Include:
- Description of you, your team, or entity
- Track you are applying for
- Description of your solution or implementation plan
- Link to your UI or integration if available
- Link to repository if applicable
- Intended hosting or distribution approach