-
Notifications
You must be signed in to change notification settings - Fork 1
L1 反滥用共识内核:消息防刷底线 + 质押式匿名身份 #69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
27 commits
Select commit
Hold shift + click to select a range
0a8b632
feat(core): L1 反滥用共识内核——消息防刷底线(随长度递增)+ 质押式匿名身份(纯锁仓无罚没)
v0id-byte 092665e
feat(node,cli,web): 质押式匿名身份下游接线——API/CLI/Web 面板
v0id-byte b637cc3
test: 两个新 selftest——message-burn-floor-selftest.ts / identity-selftes…
v0id-byte 9665dec
fix(smoke): 加密私信场景补足挖矿本金 + 检查 addTransaction 返回值;ci: 纳入两个新 selftest
v0id-byte fc6e292
fix(core): isProtocolMemo 收紧为精确校验,堵住套壳绕过消息防刷底线的漏洞
v0id-byte 4f019dc
fix(core): 补 IDENTITY_ESCROW_ADDRESS 进 SYSTEM_ADDRESSES
v0id-byte 3ebcc54
fix(node,cli,web): 消息默认烧币值真正按长度计算,而非在更早的调用点就被扁平默认值锁死
v0id-byte deeec7a
fix(core): isProtocolMemo 补 from/to/amount 语境校验,堵住第二层套壳绕过
v0id-byte af2321f
fix(node): claimIdentity() 补节点内部激活高度守卫,防止提前认领永久锁死押金
v0id-byte 5bc702e
fix(core): addBlock 后清理 mempool 里被判负的排他性交易,防止身份认领竞态卡死钱包
v0id-byte f01071b
fix(core): isProtocolMemo 补 from/to/amount 语境校验,堵住第二层套壳绕过
v0id-byte 84ebb92
perf(core): revalidateMempool 复用单份 computeState,避免每次出块全量重放 mempool×链
v0id-byte ed7d487
fix(core): isMemoSpamCandidate 扩大消息防刷候选范围,堵住「自转夹带」绕过(关键修复)
v0id-byte 37bb6f1
fix(node): revalidateMempool 补 onMempoolDropped 回调,同步清理 seenTx 去重缓存
v0id-byte 1ff7fe5
fix(core): computeIdentityState 跳过 coinbase,防止恶意矿工伪造身份认领的只读展示
v0id-byte 5760699
fix(core): isProtocolMemo 补 DEL 撤单豁免 + IDRELEASE 的 amount 依赖条件
v0id-byte f00f5d6
fix(core): browser.ts 补 identity.js 导出,补全浏览器端身份质押能力
v0id-byte 80a713b
fix(core): isProtocolMemo 补 ROOM| 房间发布豁免,堵住消息防刷底线漏判
v0id-byte 4539273
fix(core): isProtocolMemo 堵住数字/字符串字段填充套壳绕开消息防刷底线
v0id-byte 71c284c
fix(core): isProtocolMemo 补 PET/FISH/LAND 缺失的 burn>0 校验
v0id-byte 12d9798
fix(core): IDRELEASE 未激活守卫补 burn=0 条件,防历史消息被 retroactive 判非法
v0id-byte b7d3154
fix(core): isProtocolMemo 保留字符串入参兼容,不静默破坏公共出口签名
v0id-byte ebef92a
fix(core): 消息门槛补免费备注额度,封堵双钱包接力绕过(#1,维护者选定方案)
v0id-byte 15546e4
fix(core): isProtocolMemo 补集市 BUY 豁免 + 字符串入参恢复历史纯前缀语义
v0id-byte 8d2b0fd
feat(node): 送币路径支持 burn——长备注付款可补足消息门槛所需销毁额(#4)
v0id-byte d93edf7
fix(core): parsePets 送崽须 amount>0,与 isProtocolMemo 分类对齐(#2)
v0id-byte 13fbe1e
perf(test): identity-selftest 锁定期等待改用 forgeTo + forge 时间戳钳到 now(#5)
v0id-byte File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both added selftests forge to very high activation heights (
40000and45000) by repeatedly calling the real PoWmineBlock; I checked the workflow context and a local 70s run of the same forge helper only reached height 5000, so these two new steps alone are likely to exceed the check job's 15-minute timeout and make PR CI fail before tests complete. Use a cheaper deterministic block builder for these activation-height tests or lower the heights under test.Useful? React with 👍 / 👎.