We study a lightweight ledger protocol for intermittent and noisy networks, motivated by IoT and mobile settings in which partitions are common and full-history verification is impractical. Our design centers on an \emph{operational} notion of \textbf{contextual authentication}: each node decides whether a chain extension is acceptable in its current local context, using checkpoint-first fork choice, a local branch score derived from recent proposer behavior, and an inconsistency-driven \emph{quarantine} signal. To improve recovery after partitions, we combine this acceptance rule with \textbf{adaptive synchronization}, which increases gossip effort only when inconsistency becomes prevalent. We evaluate the protocol with a discrete-event simulator under controlled partitions and two network regimes (clean and noisy). Across 500 seeds at $N=20$, the main result is that quarantine alone does not materially improve agreement or recovery under noisy conditions, whereas increased synchronization (\texttt{Gossip\_only} and \texttt{Both}) substantially improves both final agreement probability and recovery-time tails after partition rejoin. Longer-horizon experiments show that low-synchronization failures are not removed simply by waiting longer, and scaling experiments at $N=50$ and $N=100$ show that parameters that work at small scale do not automatically generalize. These results indicate that, under noisy partition/rejoin dynamics, recovery in the current design is limited primarily by information availability, making synchronization policy a first-class design problem.

翻译：我们研究一种适用于间歇性和噪声网络环境的轻量级账本协议，其动机来自分区常见且完整历史验证不可行的物联网与移动场景。该设计的核心围绕**上下文认证**的操作性概念：每个节点基于检查点优先的分叉选择规则、源自近期提议者行为的本地分支评分以及不一致驱动的**隔离**信号，判定链扩展在当前局部上下文中是否可接受。为提升分区后的恢复能力，我们将该接受规则与**自适应同步**相结合——仅当不一致现象普遍时增加八卦传播开销。通过离散事件模拟器，我们在受控分区和两种网络模式（清洁与噪声）下评估该协议。在$N=20$的500组随机种子实验中，主要结果表明：噪声条件下单独使用隔离机制对提升一致性与恢复效果不显著，而增加同步机制（`Gossip_only`和`Both`）则显著提升了最终一致性概率及分区重连后的恢复时延尾部分布。长时域实验显示，低同步失效无法通过简单延长等待时间消除；$N=50$和$N=100$的规模扩展实验表明，小规模下有效的参数无法自动泛化。这些结果表明：在噪声分区/重连动态下，当前设计的恢复能力主要受限于信息可用性，因此同步策略应作为首要设计问题。