# Testnet `kaal:entity:testnet` **Status.** derived This node is assembled mechanically from the 12 claims that carry the concept tag `testnet`. It is a roster of what the corpus says under this term. It is **not** an adjudicated definition: no single statement here has been ruled canonical, and no first-appearance call has been made. Read the claims and judge for yourself. ## Every claim under this term 12 claims across 2 works, 2021 to 2025. **2021** - [3931933-008](https://wulfkaal.github.io/claims/3931933-008) [empirical/asserted] -- The final 2021 Casper testnet used perceived validator node uptime as its single rewarding requirement. > The latest incentivized testnet ended in September 2021. The last Casper tesnet in September 2021 entailed as its single rewarding requirement the perceived uptime of the participating testnet validator node. Wulf A. Kaal, Hybrid Secure Proof of Stake (2021). SSRN: https://ssrn.com/abstract=3931933 - [3931933-009](https://wulfkaal.github.io/claims/3931933-009) [empirical/asserted] -- Early Casper testnet participation was sustained by norms of unpaid mutual support, with participants actively sharing knowledge and supporting other validators without expectation of profit or return favors. > Importantly, the early testnet community entailed many participants who were actively sharing their knowledge and supporting other validators without expectation of profit or return favors. Wulf A. Kaal, Hybrid Secure Proof of Stake (2021). SSRN: https://ssrn.com/abstract=3931933 - [3931933-010](https://wulfkaal.github.io/claims/3931933-010) [empirical/asserted] -- Detailed and easy to follow operator documentation produced by the early testnet community drove participation up to roughly 950 nodes running on the network, with around 200 nodes rewarded each week. > early testnet community created detailed and very easy-to-follow instructions for the testnet node operators, which resulted in around 950 nodes running on the network and around 200 nodes were rewarded each week. Wulf A. Kaal, Hybrid Secure Proof of Stake (2021). SSRN: https://ssrn.com/abstract=3931933 - [3931933-011](https://wulfkaal.github.io/claims/3931933-011) [failure/evidenced] *(failure mode)* -- Publishing each validator's uptime and rewarding status to the community on a weekly basis coincided with active Casper testnet nodes falling below 800, in a period of already volatile validator participation. > In the early testnet days, validator participation was volatile with validators joining and others leaving regularly. At some point during 2021, the active Caser testnet nodes fell under 800 after the uptimes/rewarding-status of each validator node was reported to the community on a weekly basis. Wulf A. Kaal, Hybrid Secure Proof of Stake (2021). SSRN: https://ssrn.com/abstract=3931933 - [3931933-012](https://wulfkaal.github.io/claims/3931933-012) [failure/evidenced] *(failure mode)* -- Validators who learned they would receive no reward shut down their nodes rather than waiting for the incentivization phase to end, so a reward scheme that visibly excludes participants loses their contribution immediately. > Other validators shut down their nodes instead of waiting for the end of the incentivization phase when they realized that there was no reward for them. Wulf A. Kaal, Hybrid Secure Proof of Stake (2021). SSRN: https://ssrn.com/abstract=3931933 - [3931933-013](https://wulfkaal.github.io/claims/3931933-013) [failure/argued] *(failure mode)* -- The initial Casper testnet was subject to inevitable centralization, illustrated by a small group of core developers setting validator performance numbers and other rules without broader community input. > The initial Casper testnet was subject to inevitable forms of centralization. For example, a small group of core developers determined the testnet validator performance numbers and other rules without broader community input. Moreover, only a rather small group of developers managed Wulf A. Kaal, Hybrid Secure Proof of Stake (2021). SSRN: https://ssrn.com/abstract=3931933 - [3931933-014](https://wulfkaal.github.io/claims/3931933-014) [failure/argued] *(failure mode)* -- Opacity about reward eligibility is itself a source of dysfunction: during the first phase of the 2021 Casper testnet it was unclear which validators would be rewarded in each week, which caused friction and non-productive discussions among the validators. > During the first phase of the 2021 Casper Testnet, it was unclear which validators would get rewarded in each week, causing friction and non-productive discussions among the validators. Wulf A. Kaal, Hybrid Secure Proof of Stake (2021). SSRN: https://ssrn.com/abstract=3931933 - [3931933-015](https://wulfkaal.github.io/claims/3931933-015) [failure/evidenced] *(failure mode)* -- The initial Casper testnet group was hampered by communication shortcomings, with only around 680 validators present in the telegram group that served as the main channel for news and updates. > Yet, the initial testnet group were hampered by communication shortcomings. For example, only around 680 of the validators were present in the telegram group. Wulf A. Kaal, Hybrid Secure Proof of Stake (2021). SSRN: https://ssrn.com/abstract=3931933 - [3931933-017](https://wulfkaal.github.io/claims/3931933-017) [failure/evidenced] *(failure mode)* -- Lack of validator expertise degraded the initial Casper testnet, with only around 85 percent of testnet nodes up to date and roughly 140 active machines contributing nothing to the network. > Lack of expertise also afflicted the initial Casper testnet. Only around 85% of the testnet nodes were up-to-date, with the rest of the active machines (around 140 machines at the time) not contributing to the network at all. Judging by the discussion and questions in the telegram channel, Wulf A. Kaal, Hybrid Secure Proof of Stake (2021). SSRN: https://ssrn.com/abstract=3931933 - [3931933-018](https://wulfkaal.github.io/claims/3931933-018) [failure/argued] *(failure mode)* -- Reward focused participation crowds out technical engagement: many Casper testnet participants lacked the expertise to run nodes, and their questions concentrated on reward payments with little to no focus on technical topics. > Judging by the discussion and questions in the telegram channel, many testnet participants also did not have the required expertise to run Casper testnet nodes. Questions primarily focused on reward payments, with little to no focus on the technical topics. Wulf A. Kaal, Hybrid Secure Proof of Stake (2021). SSRN: https://ssrn.com/abstract=3931933 - [3931933-019](https://wulfkaal.github.io/claims/3931933-019) [empirical/argued] -- Despite its shortcomings the 2021 Casper testnet fulfilled its purpose, providing a test bed for dApp developers and testing node software upgrades before deployment on the Casper mainnet. > Nevertheless, the 2021 Casper testnet fulfilled its purpose. It provided a test bed for dApp developers on Casper mainnet, and tested the node software upgrades before they were deployed on the Casper mainnet. Wulf A. Kaal, Hybrid Secure Proof of Stake (2021). SSRN: https://ssrn.com/abstract=3931933 **2025** - [5225296-040](https://wulfkaal.github.io/claims/5225296-040) [normative/asserted] -- Testnet deployment must evaluate weighted voting and microsecond-scale updates against Sybil attacks, collusion, and reputation gaming across adversarial scenarios of ten, thirty-three, and fifty percent malicious participation before SPoS's theoretical strengths can be treated as practical resilience. > Testnet deployments should evaluate both weighted voting and microsecond-scale updates against Sybil attacks, collusion, and reputation gaming under adversarial scenarios (e.g., 10%, 33%, 50% malicious participation), using real-time data and high-performance testbeds Wulf A. Kaal, Cryptographic Foundations and Interdisciplinary Dimensions of the Secure Proof of Stake (SPoS) Conse (2025). SSRN: https://ssrn.com/abstract=5225296 ## Verify Every claim above resolves to a record carrying a verbatim source quote, the sha256 of the source PDF, and a preformatted citation. Nothing here asks to be taken on trust. curl -s https://wulfkaal.github.io/entities/testnet.md | sha256sum **Canonical form.** This markdown file is the canonical hashed representation of this entity node. Its sha256 is the content hash.