## <img height="351" width="624" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfTkJDeeH4qaPCgShb4I0ToGhA6HJMTI-WMWdcJ4_wwRf7nJ0aXBIiWeZxg0Wp7T37Bij5HCp_5g_gZ83TG6lQUu1WqXTeb7dl75NOq_5hqxzWop1oSk3tJ6Km3F4AznUZwYajV7w?key=FSdueCfSwPsfw-tX90v8eusb" />

## Table of Contents

* [TL;DR](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.sl6sjhxely3)
* [Brief](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.ysbubcs7olq3)
* [Scope of Delivery](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.ej6irkz3q4kx)
* [Budget](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.jn56yjeasn71)
* [Interest Received](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.fa9wbqovtovw)
* [Details](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.e7lxknx6l76w)
* [What Epico Enables](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.32yunos9qx6e)
* [Demo](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.t6hyg9lnkjm1)
* [Epico Limitations](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.cllc0sbkxd21)
* [Ecosystem Impact](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.yi8r4lyesi8r)
* [Proposed Funding Model](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.lhrubzpfwcvv)
* [Scope of Work](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.518hls24ib1q)
* [Out of Scope](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.uckb9m7ulx9a)
* [Our Past Work](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.jfrypmpujjvb)
* [Budget](https://docs.google.com/document/d/1t-uazf3ly__WgoF1W7FpOoCBrjeG-XikQMRvqCKopts/edit?tab=t.0#heading=h.h42qyvyej1t6)



## TL;DR

### Brief

We are seeking Polkadot Treasury’s support for the development and open source rollout of Epico — an Ethereum wallet compatibility layer for the Polkadot SDK. Epico will enable Polkadot SDK chains to seamlessly interface with Ethereum wallets — without the need for EVM emulation, or wallet plugins (snaps).

### Scope of Delivery

* Epico source code
* Integration guides
* Technical Support for 3 months

### Budget

$246,330 USDC



## Interest Received

We announced Epico and published a recorded demo right before EthDenver 2025 (late February), and spoke with several parachain teams during and after EthDenver for potential integration of Epico in their chains. We have received interest from 5 teams so far, 3 of which are listed below and the other two didn’t wish to be named in the proposal.

* Mythos
* Frequency
* Polimec

As and when we publish the Epico source code and integration guide, we expect more teams to adopt the solution in their Polkadot SDK based chains.

We also received the following words of support from Mythos and Frequency:

“*At Mythos, our mission is to lower the barriers to Web3 adoption starting with gaming, but extending to the broader ecosystem. A key part of that is meeting users where they already are. By enabling Ethereum RPC compatibility via Epico, on the Mythos parachain, we make it possible for millions of users to interact using wallets they already trust, while still benefiting from the throughput improvements of Substrate. This would significantly reduce friction and open up seamless access to the MYTH token, whether on Ethereum or within our parachain.*” - Cameron Thacker, VP, Mythical Games

“*The Frequency core contributors support this proposal. We believe there is a requirement for interoperability with the Ethereum community for the success and expansion of the Polkadot ecosystem. We also see this as a perfect pairing with the ongoing work on Pallet Revive. Epico has the chance to accelerate the rollout of Ethereum RPC compatibility for Frequency, a major goal for us this year. We have previously had great experiences with BlockDeep, including the code reviews they did for Frequency, and have confidence in BlockDeep’s ability to deliver the work for this proposal.*” - Harry Evans, CTO, Project Liberty



## Details

One of the largest barriers to mainstream adoption for Polkadot-based chains has been the unfamiliarity users face when interacting with Substrate-native accounts and wallets. The majority of crypto users today, especially those coming from Ethereum and EVM-compatible ecosystems, rely on MetaMask and other Ethereum-centric wallets as their default gateway into Web3.

The following graphs show absolute domination of MetaMask, sourced from [<u>Dune dashboard: Wallet War</u>](https://dune.com/hashed_official/wallet-war)

<img height="307" width="624" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfZ3dswfP9dW2cvDzR5-DB4RDFSqL20nQqlvQpY92JEn4de9o0pPJOMgvlgX5oUTsPV_Z4rpfBdn5303RIPbqiwN8VVfv4-l77CyQqqsMhbZSkM5gAmz89tXoMXXD2_GNBUYGvn8Q?key=FSdueCfSwPsfw-tX90v8eusb" />

<img height="231" width="624" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdoJSL9BRCXSh80qQag0ny8TJDwbtVCgpiP8PGgoIxOzpCfD-9X7Mka-fZeJZch03xGCj27_lgWodjUjA1ZCLzpZ9dd1ML2mP1RtI4F5VcwzgLknt9FgPPNtW27vb1SotS7YKsG?key=FSdueCfSwPsfw-tX90v8eusb" />

Epico directly addresses this challenge by enabling users to sign and send transactions using their existing Ethereum wallets like MetaMask to Polkadot SDK chains, without needing to install snaps (plugins) or understand new account formats.



## What Epico Enables

* MetaMask and Ethereum Wallet Support: With Epico, any Polkadot SDK chain that integrates the solution will allow users to connect using their Ethereum accounts and sign transactions via MetaMask and other Ethereum wallets — just as they would on any EVM chain.
* Familiar UX for New Users: Users will no longer need to manage separate Polkadot-specific accounts or learn new address formats. A single Ethereum wallet address can now interact with both Ethereum and Polkadot-based applications on chains that adopt Epico.
* Frictionless Onboarding: Whether a user is exploring DeFi, NFTs, games, or decentralized identity apps on Polkadot, Epico allows them to skip the typical onboarding hurdles like creating new wallets, backing up new seed phrases, or converting assets via bridges.



## Demo

We integrated Epico with a solo-chain node and recorded the following fully functional demo. We encourage the community to take a look at the demo before casting their vote.

[<u>https://www.youtube.com/watch?v=CS74zbi9OYI</u>](https://www.youtube.com/watch?v=CS74zbi9OYI) 



## Epico Limitations

In its current form, Epico focuses on enabling seamless interaction between MetaMask (and other Ethereum-compatible wallets) and Substrate-based chains. This is achieved by integrating chains that natively support Ethereum-style accounts (such as Mythos).

However, chains that exclusively use Substrate’s account format (AccountId32) do not yet benefit from Epico. To address this limitation, we’ve been actively exploring solutions that would allow Substrate chains to support Ethereum accounts while maintaining full backward compatibility with their existing native account systems.

One approach involves leveraging Ethereum accounts as proxies for Substrate accounts — a mechanism we have already successfully demonstrated in our [smart accounts project, Otro](https://blog.blockdeep.io/introducing-otro-substrate-smart-accounts-ff56179f2f10).



## Ecosystem Impact

Epico is built with one clear goal: to remove the invisible walls between the Polkadot and Ethereum ecosystems from the user's perspective.

By allowing users to access Polkadot-based chains and applications directly through MetaMask and other Ethereum-compatible wallets, Epico will:

* Make Polkadot-based apps immediately accessible to the largest wallet user base in the blockchain ecosystem.
* Reduce the learning curve and eliminate the need for new wallets, boosting adoption of both new and existing dApps built on Polkadot SDK.
* Encourage broader user engagement in the Polkadot ecosystem by removing the need for wallet switching.



## Proposed Funding Model

Our proposal differs slightly from most others seeking prospective or retrospective funding. Epico was built over the course of several months — from initial analysis and design to development and testing. It has been an iterative journey, during which we explored multiple approaches before arriving at a solution that truly works.

Once the technical work was complete, we began evaluating potential ways to sustain and distribute Epico. One option was to adopt a closed-source, per-integration licensing model, allowing teams building on Substrate to purchase access. The alternative was to open-source the project and rely on retrospective funding.

The first path would require significant time spent on sales cycles, which we felt would divert our focus away from what we do best — building and improving the technology. The second path risked turning the project into an unmaintained code dump if retrospective funding didn’t materialize, which would ultimately not result in a useful solution.

Instead, we’ve chosen a middle-ground approach: one that allows us to deliver polished, high-quality code while ensuring support and maintenance. We are committed to open-sourcing Epico under the Apache 2.0 license upon completion, giving the community full access to the codebase.

Upfront funding will enable us to finalize the remaining work: cleaning up the code, writing comprehensive documentation, conducting peer reviews, and ensuring alignment with ecosystem standards. This ensures the project will be released in a state that is truly useful, reliable, and maintainable from day one.

We believe open-sourcing without proper funding risks leaving behind incomplete or poorly documented code, which can create more confusion than value for the ecosystem. Our goal is to avoid that by releasing a professional, well-supported open-source project — not just publishing a code dump.



## Scope of Work

* Completion of Epico core features. Open-sourcing of the entire codebase.
* Documentation, tutorials, and integration guides to streamline adoption by parachain and solo chain teams.
* Fully functional demo with Epico integration and a demo UI for anyone to try it out.
* Technical support/advisory for the first 3 months (after open sourcing) to any team who intends to integrate Epico in their chain.
* Maintenance and update to latest Polkadot SDK quarterly releases for at least 6 months. 



## Out of Scope

* Security audits are out of scope of this proposal. However, we will approach PAL for audits, or may create another proposal for that if needed.
* Development effort for integration with specific chains is out of scope, however we commit to providing technical support for integration as mentioned in the scope section above.



## Our Past Work

In our \~1 year of operations so far, BlockDeep Labs has delivered the following to the Polkadot ecosystem:

* Development and migration of [Mythos parachain](https://blog.blockdeep.io/bringing-mythos-to-polkadot-the-mythical-games-parachain-development-story-b6450374c3a2) (funded by DF program).
* [Delivery of Ecosystem Services](https://blog.blockdeep.io/blockdeep-labs-ecosystem-services-delivered-d4e3b25de82c) as part of our last treasury proposal.
  * In-depth code reviews for 20 teams
  * Detailed [Polkadot SDK best practices book - Libro](https://libro.blockdeep.dev/)
  * [Delivery Partners Program](https://blog.blockdeep.io/launching-the-delivery-partners-directory-394a0dfad607)
  * [Release analysis reports](https://forum.polkadot.network/tag/release-analysis)
* Development of [Smart Account Abstraction](https://blog.blockdeep.io/introducing-otro-substrate-smart-accounts-ff56179f2f10) and [XCM Tracer](https://blog.blockdeep.io/introducing-xcm-tracer-a0889c1397ab).
* Currently under development - [RFC-0097: Fast Unbonding of Staking rewards](https://x.com/0xBlockDeep/status/1924910399750549562).
* Advisory to several pre-launch teams building in the ecosystem.



## Budget

We’ve spent \~185 person-days (roughly 1.5 FTE for approx. 5 months) of effort on the following tasks on Epico:

* Detailed analysis of all standard Eth RPCs
* Analysis of API calls made by MetaMask
* Analysis of Frontier project and identification of reusable components for Ethereum signatures support
* Designing Epico on-chain and off-chain (node side) components
* Designing of Epico DApp side components (JavaScript snippets)
* Solving efficient storage of transaction receipts
* Detailed analysis of Ethereum Gas and Substrate Weights, and a conversion mechanism for RPC APIs
* Development and in-depth testing
* Integration with parachain and solochain node templates
* Reorganizing and packaging rust code into easily usable crates
* Building an end to end demo (as showcased in the video)

We require another 20 person-days of effort for the following tasks:

* Code reviews (not security audits)
* Documentation and integration guides
* Polishing the demo

In the future, to provide technical support to teams integrating Epico in their chains, we estimate a total of 25 person-days of effort spread over a 3 month period.

**Total Effort:** 230 person-days

**Daily Rate:** USD 900 (\~ EUR 800 per day or EUR 100 per hour)

**Sub Total (230\*900):** $207,000

**German VAT at 19%:** $39,330

**Total:** $246,330 USDC

Thank you for considering our proposal. We're happy to answer any questions and provide further details as needed. Looking forward to engaging with the community and moving Epico forward together.

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

#1580 Epico: Ethereum Wallet Compatibility for Polkadot SDK Chains

No Active Proposals