[MS] DOT #1580 - Epico: Ethereum Wallet Compatibility for Polkadot SDK Chains
active
Description

https://polkadot.subsquare.io/referenda/1580

Epico is a project that aims to make Polkadot SDK chains compatible with Ethereum wallets like MetaMask. This will allow users to interact with Polkadot-based applications using their existing Ethereum wallets without needing extra plugins or understanding new account formats. The project has received interest from several parachain teams, including Mythos and Frequency.

The main goal of Epico is to make Polkadot-based apps more accessible to the largest wallet user base in the blockchain ecosystem, which is currently dominated by Ethereum users. By reducing the learning curve and eliminating the need for new wallets, Epico can boost the adoption of both new and existing dApps built on Polkadot SDK.

The project is seeking funding to complete the development and open-source rollout of Epico. The budget requested is $246,330 USDC, which will be used for finalizing the code, writing documentation, conducting peer reviews, and providing technical support for the first three months after open-sourcing. The project plans to open-source Epico under the Apache 2.0 license upon completion, giving the community full access to the codebase.

BlockDeep Labs, the team behind Epico, has a history of contributing to the Polkadot ecosystem, including developing the Mythos parachain, providing code reviews for 20 teams, and developing smart account abstraction and XCM Tracer.

Appendants
1
#1
15h ago

🟢 5 • 🔴 0 • ⚪️ 1
Vote #1: AYE
10 available members.
CoI reported. DV delegation voted abstain.
https://polkadot.subscan.io/extrinsic/26217097-2
https://polkadot.subsquare.io/referenda/1580#2

Cast your votesingle

Votes·9

1xzc...1bX6
1xzc...1bX6
1xzcLSwo7xBFkJYZiL4EHaqFpuPTkH641E3V43W4cuk1bX6
Aye
# 1
We think this could strengthen the whole Polkadot <> Ethereum narrative.
167Y...TY9F
167Y...TY9F
167YoKNriVtP4Nxk9F9GRV7HTKu5VnxaRq1pKMANAnmmTY9F
Aye
# 1
Anything to make Ethereum players come into our community is a priority. The team is known in the ecosystem with a proven track record.
14Gn...YLEh
14Gn...YLEh
14Gn7SEmCgMX7Ukuppnw5TRjA7pao2HFpuJo39frB42tYLEh
Aye
# 1
I share the vision of the rest of the team members, about how important it is to build tools that allow us to work on the Ethereum-Polkadot connection.
1ZSP...vx6w
1ZSP...vx6w
1ZSPR3zNg5Po3obkhXTPR95DepNBzBZ3CyomHXGHK9Uvx6w
Abstain
# 3
On the one hand, this is clearly useful to Mythical and Frequency. On the other hand, it's unclear when this will go into production with a parachain, so the costs to bring this to production are unknown (e.g. technical support after the initial 3 month period, audit, integration costs etc.). I would prefer to see Blockdeep either propose the idea upfront, or issue a retroactive proposal once it goes into production with a parachain. Beyond this, it would be good to paint a picture of the potential future market of users, e.g. non-EVM chains with Ethereum addresses.
12s6...nE8h
12s6...nE8h
12s6UMSSfE2bNxtYrJc6eeuZ7UxQnRpUzaAh1gPQrGNFnE8h
Aye
# 1
Important. Necessary. Compatibility with EVM and EVM wallets is crucial. Aye.
15fT...yBzL
15fT...yBzL
15fTH34bbKGMUjF1bLmTqxPYgpg481imThwhWcQfCyktyBzL
Aye
# 1
It's a valuable contribution toward greater adoption by means of Ethereum wallet support. The source code will be open-sourced, which checks another box. Hopefully this solution will be useful for more development teams in the future.
12Kt...DCoJ
12Kt...DCoJ
12KtA8mtfsK1CyQb4utLiwG3ao22z77w2cM2GqnaL2RiDCoJ
Aye
# 1
I like that the team took initiative, kept costs in check, and came up with a workable solution before asking for funds from the treasury.
14gM...deVb
14gM...deVb
14gMJV95zwxUsFEZDSC8mtBVifS6SypKJkfBKANkMsLZdeVb
Aye
# 1
I hope projects will adopt this work.
13ED...KQbF
13ED...KQbF
13EDmaUe89xXocPppFmuoAZaCsckaJy3deAyVyiykk1zKQbF
Abstain
# 3
Don't know enough about this to make an informed voting decision. Open to changing our minds.

Discussions·0

No current comments
...
Information
Snapshot
Timestamp
Created
May 22 2025 19:03
Start date
May 22 2025 00:00
End date
Jun 21 2025 00:00
Results
Voters
9
one-person-one-vote
Aye
7 VOTE
 
Nay
0 VOTE
 
Abstain
2 VOTE
 
© 2025 OpenSquare. All Rights Reserved.