@Dusk_Foundation I kept looking at DUSK’s depth-34 Phoenix tree from the wrong number first 17.18 billion leaves sounds almost impossible to exhaust.
But tree size alone hides the real pressure. What matters is how quickly Phoenix creates notes not just how many transactions DUSK processes.
At 10 TPS with 2 outputs each, 20 notes enter the tree every second. That gives roughly 27.2 years of capacity. At 50 TPS it falls to about 5.44 years. At 100 TPS around 2.72 years.
Then the curve gets uncomfortable.
At 500 TPS × 2 outputs 17.18B leaves could be consumed in roughly 199 days. At 1,000 TPS around 99 days.
Some of this is theoretical. Networks rarely sit at maximum traffic continuously and output counts will vary.
Still TPS vs actual state growth is the comparison I care about.
What happens if private usage rises faster than expected? Can DUSK extend rotate archive or otherwise manage Phoenix state without adding painful proof or sync costs?
That is the real test for DUSK. A huge tree is useful but longevity depends on note creation behavior.
Capacity sounds static. Usage turns it into a clock.
#dusk $DUSK #dusk $DUSK @Dusk
But tree size alone hides the real pressure. What matters is how quickly Phoenix creates notes not just how many transactions DUSK processes.
At 10 TPS with 2 outputs each, 20 notes enter the tree every second. That gives roughly 27.2 years of capacity. At 50 TPS it falls to about 5.44 years. At 100 TPS around 2.72 years.
Then the curve gets uncomfortable.
At 500 TPS × 2 outputs 17.18B leaves could be consumed in roughly 199 days. At 1,000 TPS around 99 days.
Some of this is theoretical. Networks rarely sit at maximum traffic continuously and output counts will vary.
Still TPS vs actual state growth is the comparison I care about.
What happens if private usage rises faster than expected? Can DUSK extend rotate archive or otherwise manage Phoenix state without adding painful proof or sync costs?
That is the real test for DUSK. A huge tree is useful but longevity depends on note creation behavior.
Capacity sounds static. Usage turns it into a clock.
#dusk $DUSK #dusk $DUSK @Dusk