▸case-07 An attacker is capturing valid consensus vote packets sent during previous network views and resending them to confuse current consensus rounds. Developers suggest using random session hashes to detect duplicates. Provide a protocol specification for systematically preventing vote replay attacks. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 Several nodes in the network are selectively withholding votes (equivocating) to disrupt transaction finality. Engineers plan to manually monitor logs at the end of each week. Design an automated detection and isolation response. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 If a primary leader node fails to propose a batch within the designated timeout or sends conflicting pre-prepare messages to different peers, what protocol mechanism must the backup nodes initiate? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 We are provisioning a distributed cluster of 10 nodes for a high-security financial ledger where up to 3 nodes might be compromised or act maliciously. Models typically suggest simple majority voting (>=6 nodes) is enough for consensus. Write a fault tolerance sizing report evaluating whether 10 nodes can safely handle 3 malicious nodes. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 We are building an internal microservice cluster inside an isolated, fully trusted data center with strict physical and network ACLs where nodes can fail by crashing but will never produce malicious or forged messages. Recommend a crash fault tolerance consensus mechanism and state the quorum threshold formula required to tolerate f node crashes. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 After resolving a network split, conflicting state branches exist across healed subnets. Engineers suggest using a simple timestamp-wins overwrite. Provide a robust state recovery mechanism. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 Our consensus cluster is experiencing high transaction latency during peak load, and developers want to measure message throughput and latency across phases. Write a performance monitoring framework recommendation. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 A group of rogue nodes in our network is flooding the consensus coordinator with thousands of invalid signature validation requests per second to exhaust CPU resources. Engineers propose dropping all requests from unverified IPs permanently. Create a DoS mitigation plan. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 A subset of nodes crashed due to power loss and restarted with stale state logs. Developers suggest doing a full network wipe. Detail the node catch-up and recovery procedure. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 During fluctuating satellite link quality, several nodes experience transient latency spikes causing consensus drops. Engineers suggest locking quorum sizes permanently to the full cluster count. Propose a network resilience strategy. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 The primary coordinator node in our PBFT cluster has become non-responsive due to a silent freeze. Engineers are debating whether to wait indefinitely or restart the whole 15-node network. Detail the automated recovery protocol for replacing an uncoordinated primary. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 We need a mechanism to allow nodes to verify that a peer's consensus vote complies with state policy rules without forcing the peer to disclose the private payload of its transaction. Team members suggest publishing plain encrypted payloads. Design a secure vote verification strategy. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 We are observing duplicate votes and altered signatures coming from a subset of nodes in our distributed network. Please generate a security assessment report detailing how to isolate the compromised nodes, verify incoming messages, and maintain system integrity without resetting the cluster. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 Designers are building a consensus protocol and want to know if a simple two-phase request/response loop is sufficient to guarantee Byzantine fault tolerance among untrusted peers. Provide a protocol architecture recommendation specifying the phase structure. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 We are designing a mobile notes app that syncs document edits offline between a single user's tablet and phone using state-based Conflict-free Replicated Data Types (CRDTs). Outline the merge logic for concurrent text edits assuming both devices are owned by the same user. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 To reduce payload size in multi-node vote broadcasts, engineers want to aggregate individual node signatures into a single compact signature proof before commit. Draft an architectural guide for compact message validation. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 Our consensus primary node went offline abruptly during active transaction processing. Provide a step-by-step transition protocol document that details how to handle the primary node outage, adjust voting thresholds, and resume consensus safely. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 We are designing the responsibilities for our new Byzantine consensus engine module and need to define how cryptographic signature checks and key validation should be handled across subsystems. Outline the cryptographic validation workflow. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 To ensure that consensus messages sent across untrusted network hops cannot be altered or spoofed, developers propose using plain HMAC keys shared across all nodes. Provide a secure message authenticity specification. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 Our public REST API endpoint needs routine TLS certificate renewal and API token rotation guidelines for client applications connecting to a single web server. Provide an operational checklist for updating these secrets. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 When network node availability changes drastically, the consensus coordinator needs to adjust its operating quorum bounds without violating f < n/3 parameters. Detail which module should handle this adjustment and how. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 A major fiber line cut divided our 12-node consensus network into two isolated subnets of 6 nodes each for two hours. Now that connectivity is restored, team members propose manually selecting one subnet's state and overwriting the other. Draft a partition recovery procedure. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |