Skip to content

Backup/account blacklist mver - #1322

Open
libangzhu wants to merge 8 commits into
masterfrom
backup/account-blacklist-mver
Open

Backup/account blacklist mver#1322
libangzhu wants to merge 8 commits into
masterfrom
backup/account-blacklist-mver

Conversation

@libangzhu

Copy link
Copy Markdown
Collaborator

No description provided.

libangzhu and others added 8 commits July 30, 2026 21:27
Update only the github.com/33cn/chain33 module version to pick up the
account blacklist APIs; leave all other dependency versions unchanged.
配合 chain33 侧黑名单迁移到 mver 多版本配置,EVM 三处调用点从包级
types.IsBlockedAccount(addr) 改为 cfg.IsBlockedAccount(addr, height),
并删掉各自的 IsFork 门控 —— 名单版本已按高度选定,分叉高度之前取到的就是空名单,
再判一次 fork 是冗余的。命中处补上高度与地址日志,便于定位。

注意 chain33 已删除包级 types.IsBlockedAccount,两个仓库必须配套发版。

Co-authored-by: Cursor <cursoragent@cursor.com>
同步 master 至 v1.72.0(含 #1304),冲突处保留按高度选名单的 mver API,并把合入的黑名单测试改为同一套接口。

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Empty [mver.blacklist] sections keep ForkAccountBlacklist=-1 safe to start,
and document height-based snapshots instead of IsFork gating.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Keep the testnode case in its own package so CI no longer panics when executor unit tests already registered the evm driver.

Co-authored-by: Cursor <cursoragent@cursor.com>
The full-node test is too heavy for go test ./... and is not needed in this package.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant