Tick simulator
Every node tries, packets wait in time buckets, then tips reconcile. A controlled lens for comparing difficulty, population and attack rate.
open experiment / deterministic by design
The Tick model advances every node on one synchronized clock; the Routine model lets goroutines mine concurrently, with a 500 μs sleep after a failed attempt.
01 / the setup
The project keeps the chain model intentionally simple, then changes the clock and network around it. That makes the effect of latency visible instead of burying it in infrastructure.
Every node tries, packets wait in time buckets, then tips reconcile. A controlled lens for comparing difficulty, population and attack rate.
Independent goroutines mine and gossip over real TCP connections. Bootnode observes the DAG while peers discover their own rhythm.
02 / experiment families
Tick advances in synchronized rounds; Routine mines continuously and sleeps 500 μs after a failed attempt.
A miner withholds work, then releases it when the private lead is valuable.
The attacker mines privately while honest miners extend the public branch.
03 / under the hood
No real hashing, no transaction layer, no magic. Just enough machinery to make propagation delay, private chains and miner strategy legible.
Difficulty × HashPowerBoth branches share the same probability rule. Only the clock, transport and observability layer change.