cosmos / cosmos/evm

[Spike] Explore removing the ERC20 module

Open
#526 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
164
Forks
213
Avg merge
3d 58m
Merged PRs (30d)
12

Description

Because x/erc20 and x/vm are so highly coupled, one cannot live without the other. Look into removing as much unneeded code from x/erc20 and move the logic into x/vm *or* fully decouple the two modules such that teams can choose to include/exclude ERC20 functionality.

This should be a followup issue to [https://github.com/cosmos/evm/issues/505](https://github.com/cosmos/evm/issues/505), where we want to clean up and move from the ERC20 precompile structure that we have right now. If we choose to do that, we should fully commit to cleaning up the modules.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the x/erc20 and x/vm modules and the follow-up context in issue #505. Trace their coupling and identify which ERC20 code is unnecessary or prevents independent inclusion. Done requires an agreed direction: moving the logic into x/vm or fully decoupling the modules, with the resulting cleanup completed.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
blockchain
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.