Integration Grants Application '26: Protofire, Safe Multisig for Conflux eSpace

#1

Proposal Submitter: Protofire
Target Ecosystem: Conflux eSpace (mainnet 1030 and testnet 71)
Total Grant Applied: US$15,600 for 12 months

Key Links:

1. Application Introduction

Project: Protofire: Safe Multisig for Conflux eSpace

Who we are: Protofire is a blockchain infrastructure company working since 2016. We run Protofire Multisig (app.safe.protofire.io), the largest Safe-based multisig in EVM, live on 80+ networks including Ethereum, Base and Tron.

Problem (checked 23 Oct 2026):

  • Safe contracts v1.3.0 and v1.4.1 are deployed on eSpace. The Safe web app (app.safe.global) does not support eSpace, as the Conflux docs state.
  • The only frontend, safe.conflux123.xyz, is single-chain, runs 2025 builds (client gateway v1.74.6, Tx Service 5.18.4; current: v1.129.0 and 6.12.0), indexes only Safe 1.3.0 L2, so Safes created with 1.4.1 are not supported there, and it has no testnet interface.
  • Usage is low: 78 factory transactions in 4.5 years. Teams on eSpace have no actively maintained multisig.

Solution: list eSpace mainnet and testnet in Protofire Multisig, keep it current and extend it with new functionality for 12 months. If Conflux prefers to keep the existing frontend, we can upgrade it, extend it with functionality and run it (costed separately).

1.1 Value for Conflux: what ships, what users get, what it brings

Feature What users can do Outcome for eSpace
Multisig on mainnet and testnet, Safe 1.3.0, 1.4.1 and 1.5.0 Builders, users, DAOs and other teams get a maintained multisig on both networks, including a testnet interface that does not exist today More Safes and transactions on-chain
Safe Apps (in-UI dApp browser) Use eSpace dApps, for example Swappi and Unitus, straight from the Safe. Every action still needs the Safe’s usual signatures. We help dApps become Safe-compatible Treasury funds flow into eSpace DeFi: swaps, lending, staking
Transaction simulation Before signing, the interface shows what a transaction will do: which tokens move, which approvals are granted and which contracts are called Fewer losses, more trust to hold funds on eSpace
Multichain: 80+ networks in one UI, same address creation and management Manage Conflux next to Ethereum, Base and Robinhood and create a Safe on several networks at once Projects expanding from other chains find Conflux ready
Tron: Safe on Tron is available in our UI, and only in ours Manage non-EVM funds, for example USDT on Tron, from the same interface as eSpace Safes Conflux teams reach non-EVM treasury funds
Fees in stablecoins (extended support) The Safe pays network fees in a stablecoin, so signers do not need CFX More USDC/USDT0 activity and easier onboarding of non-crypto signers
Safe modules (extended support, on request) Add-ons that extend a Safe without changing its core, for example passkey signing (sign with device biometrics) and ERC-4337 account abstraction. See also the modules overview. Easier onboarding and safer day-to-day use

Native integrations such as transaction simulation and address validation are enabled where the provider supports eSpace.

1.2 Measurable outcomes

6 months after launch. Baseline: 78 factory transactions, chain TVL $6.4M.

  1. 100+ new Safes and 1,000+ Safe transactions on eSpace.
  2. 5+ ecosystem teams onboarded (Foundation, DeFi, staking, custody) and 3+ dApps integrated as Safe Apps.
  3. 99.9% uptime, indexing lag under 1 minute.

1.3 How we drive adoption

  • Onboarding: the Foundation and ecosystem teams (DEX, lending, staking, custody) get a setup call per team, a “Safe on Conflux” guide and a path for existing Safes from the current frontend.
  • Safe Apps: integrations for at least 3 eSpace dApps, for example Swappi and Unitus.
  • Co-marketing with Conflux: announcement, docs page, social posts, included in the price.
  • Public quarterly report: Safes created, transactions, assets held, teams onboarded, uptime.

1.4 Competitive edge: what Conflux gains on the market

  • Visibility: eSpace joins the largest Safe-based multisig, next to Ethereum, Base and Tron. Multichain treasuries see it in the network list.
  • Non-EVM reach: Safe on Tron is available only in our UI, so Conflux teams and partners manage non-EVM funds next to their eSpace Safes.
  • Current, always: weekly releases, versus 2025 builds today.
  • Open source, extended by us: we deploy open-source versions of Safe components, which we further develop, enhance and extend (github.com/protofire).
  • Reliability: 99.9% uptime target, security patches, support (9 hours a day guaranteed, first response within 4 working hours on critical issues), an alternative Safe UI kept alive during the Bybit incident.
  • No lock-in and no extra bills: infrastructure can be handed over on request; infra costs, staging, QA and co-marketing are included.

1.5 Applicant details

eSpace grant wallet: 0xA119E648900d9be01B52282536EEE021F9B370A0

Incorporated startup: Altoros LLC, 1607 Ponce de Leon Avenue, GM-06, San Juan, PR, 00909.

2. Technical Introduction

  • Existing solution: safe.conflux123.xyz (described above).
  • Is it feasible? Yes. We ran our public EVM checker against eSpace mainnet and testnet: the Safe contracts are there, the Safe Singleton Factory (the contract used to deploy Safe at the same addresses on every chain) is there, and the RPC supports every method the Safe interface and backend need. What is left is running the services (backend, indexer, interface) and configuring them for Conflux.
  • Scope: eSpace mainnet (1030) and testnet (71). Not covered: Core Space.
  • Success criteria: the measurable outcomes above.
  • Terms: Safe = a smart-account multisig wallet. Tx Service = the backend that stores and indexes Safe transactions.
  • References: Conflux docs “Gnosis Safe Wallet”, github.com/safe-global releases, ConfluxScan, DefiLlama.

3. Technical Proposal

3.1 Functional

  • Deployment and verification on ConfluxScan of Safe 1.3.0, 1.4.1 and 1.5.0 on mainnet and testnet (unmodified, audited contracts). Existing Safes are indexed.
  • Backend (tx-service, gateway, config, listener, decoder) and frontend on Protofire infrastructure, with staging and production environments.
  • Mainnet and testnet interfaces branded with the Conflux logo and links. Testnet has no interface today.
  • Safe Apps and dApp onboarding. Extended support on request: fees in stablecoins (relayer), native integrations, Safe modules.
  • Licensing: we deploy open-source versions of Safe components and further develop, enhance and extend them ourselves.

3.2 Non-functional

  • Reliability: 99.9% uptime (with stable RPC), indexing lag under 1 minute, signature and history data preserved through upgrades, security patches.
  • Usability and UI: the standard Safe workflow with CFX and USDT0 preconfigured.
  • Implementation: testnet and mainnet in parallel, public reports.

3.3 Risks

Archive RPC access (we ask for a dedicated endpoint); low adoption today (see “How we drive adoption” above); the existing frontend operator is not named (our main option does not depend on them).

4. Total Budget: US$15,600 for 12 months

Paid in four quarterly milestones in USDT0 (or CFX if required; we will honor the No-Sale Rule).

Item Monthly 12 months Description
Basic support $1,000 $12,000 Hosting, updates and support for mainnet and testnet (Protofire Multisig)
Extended support $300 $3,600 Advanced integrations and extra functionality, for example fees in stablecoins via relayer, Safe Apps integrations with Swappi and Unitus, native integrations, modules on request
Total $1,300 $15,600

Launch itself (deployment, infrastructure, configuration, testing) is included in the monthly fee.

5. Development Roadmap

5.1 Stages

  • Stage 1, deployment (up to 7 days from kickoff): deploy and verify Safe 1.4.1 and 1.5.0 on mainnet and testnet, bring up backend and interface on staging and production, index existing Safes, publish the docs.
  • Stage 2, basic support (12 months): hosting, updates, monitoring and support, with the SLA below.
  • Stage 3, extended support (from month 2): Safe Apps integrations, fees in stablecoins pilot (subject to RPC feasibility), native integrations and modules on request.

5.2 Payment milestones

$3,900 each (= $1,300 x 3 months).

Milestone Timing Funding Deliverables
M1 End of quarter 1 $3,900 Stage 1 delivered, first quarter of support, onboarding of the Foundation and first teams
M2 End of quarter 2 $3,900 At least 5 teams onboarded, Safe Apps live with at least 3 dApps, first extended integrations
M3-M4 End of quarter 3/4 $3,900 Operations, public quarterly report with the KPIs above, upstream updates within 30 days

5.3 Support scope (every quarter)

  • Support and SLA: general support for the Foundation and ecosystem teams, 9 hours a day guaranteed (15 best effort), first response within 4 working hours on critical issues; emergency line outside hours.
  • Security and upgrades: patches for frontend, contracts and backend; upstream releases applied within 30 days; unrestricted Tx Service, history preserved.
  • Infrastructure: monitoring, 99.9% uptime target, indexing lag under 1 minute.
  • Reporting: public quarterly report with Safes created, transactions, assets held, teams onboarded and uptime.

6. Team

7. Terms of Use

I agree to all of the following terms of use in applying to a Conflux Ecosystem Grant:

  1. I have read and understood the Conflux Grants Ecosystem Overview.
  2. I have read about and understood that the Conflux Technical Grants are subject to a No-Sale rule.
  3. I agree to provide KYC information to the Conflux Foundation for the sake of overall ecosystem security.
  4. I understand that I will be required to follow public grant reporting requirements.