OnChain invalid timestamp block propagation fail
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- rust
- 领域
- blockchain, networking
调研方向
从 core/verification/queue/mod.rs 和 issue 中展示的 verify() 函数开始。使用 status、header response 和 body response 消息重现 block1/block2 的时间戳场景,然后跟踪 ready_signal 和目标节点的 status response。完成的标准是:无效区块被拒绝,有效前驱被处理,并且在不依赖 logging 语句的情况下发送预期的 status 消息。
由索引模型根据 Issue 内容生成。
描述
There are some issues in sending invalid timestamp onChain blocks.
Below is a test scenario.
- Make block1 and block2.
- The timestamp in Block2's header should be invalid. Simply make it smaller than block1.
- Send a
status messagewith block2's hash as the bestHash. - Send a
header response messagewhich is [genesisHeader, block1Header, block2Header]. - Send a
body response message== [[], []], which is correspond to block1's body and block2's body. - Block is accepted from the target node only for block1. So the target node should send a status message with block1's hash as bestHash.(This is normal behaviour but it didn't)
And here are problems
- The target node does not send
status messageif in the above situation. However, if I insertedinfo!("55");then thestatus messagecome properly. - In below
verify()function in/core/verification/queue/mod.rs,Ok(verified)is returned twice although the block2 is invalid.
fn verify(
verification: Arc<Verification<K>>,
engine: Arc<CodeChainEngine>,
ready_signal: Arc<QueueSignal>,
empty: Arc<SCondvar>,
more_to_verify: Arc<SCondvar>,
_id: usize,
) {
loop {
// wait for work if empty.
{
let mut more_to_verify_mutex = verification.more_to_verify_mutex.lock().unwrap();
if verification.unverified.lock().is_empty() && verification.verifying.lock().is_empty() {
empty.notify_all();
}
while verification.unverified.lock().is_empty() {
more_to_verify_mutex = more_to_verify.wait(more_to_verify_mutex).unwrap();
}
}
// do work.
let item = {
// acquire these locks before getting the item to verify.
let mut unverified = verification.unverified.lock();
let mut verifying = verification.verifying.lock();
let item = match unverified.pop_front() {
Some(item) => item,
None => continue,
};
verification.sizes.unverified.fetch_sub(item.heap_size_of_children(), AtomicOrdering::SeqCst);
verifying.push_back(Verifying {
hash: item.hash(),
output: None,
});
item
};
let hash = item.hash();
let is_ready = match K::verify(item, &*engine, verification.check_seal) {
Ok(verified) => {
let mut verifying = verification.verifying.lock();
let mut idx = None;
for (i, e) in verifying.iter_mut().enumerate() {
if e.hash == hash {
idx = Some(i);
verification
.sizes
.verifying
.fetch_add(verified.heap_size_of_children(), AtomicOrdering::SeqCst);
e.output = Some(verified);
break
}
}
if idx == Some(0) {
// we're next!
let mut verified = verification.verified.lock();
let mut bad = verification.bad.lock();
VerificationQueue::drain_verifying(
&mut verifying,
&mut verified,
&mut bad,
&verification.sizes,
);
info!("111");
true
} else {
info!("222");
false
}
}
Err(_) => {
let mut verifying = verification.verifying.lock();
let mut verified = verification.verified.lock();
let mut bad = verification.bad.lock();
bad.insert(hash.clone());
verifying.retain(|e| e.hash != hash);
if verifying.front().map_or(false, |x| x.output.is_some()) {
VerificationQueue::drain_verifying(
&mut verifying,
&mut verified,
&mut bad,
&verification.sizes,
);
info!("33");
true
} else {
info!("44");
false
}
}
};
if is_ready {
info!("55");
// Import the block immediately
ready_signal.set_sync();
}
}
}
- 主要语言
- Rust
- 星标
- 256
- 派生
- 50
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
CodeChain-io/codechain 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 25/100
CodeChain-io/codechain#2002 ·
-
难度 4/5 3-5 天 新手友好度 35/100
CodeChain-io/codechain#1993 · 2 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
CodeChain-io/codechain#1987 · 1 条评论 ·
-
performance rpc
难度 4/5 3-5 天 新手友好度 35/100
CodeChain-io/codechain#1973 ·
-
难度 3/5 1-2 天 新手友好度 35/100
CodeChain-io/codechain#1971 ·
查看 CodeChain-io/codechain 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
bug rules
难度 2/5 1-3 小时 新手友好度 72/100
-
app bug
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 88/100
IronCoreLabs/ironcore-alloy#346 ·
-
good first issue
难度 2/5 1-3 小时 新手友好度 65/100