
Cheng Wang (ℵ)
@wachmc
Followers
5K
Following
3K
Media
72
Statuses
1K
founder & core dev @Alephium / scale blockchain with sharding / proposed the first linear-time async Byzantine consensus algorithm https://t.co/1lNm8XjwIB
Alephium
Joined November 2009
Scaling PoW was just the beginning. Now we build the flywheel. Alignment begins. 🌀.
35
64
193
Code editors should show you which lines were written by AI vs. humans. Would change how we review, debug, and even trust code.
6
3
64
Now is the time to activate. As the ecosystem grows, every builder benefits. Alignment strengthens the network, the network strengthens opportunities. The next era of Alephium begins! Stay close.
0
5
89
No hype cycles. No empty promises. Value loops that sustain themselves through usage, staking, and deflationary tokenomics. Composability. Sustainability. Deflation by design.
2
3
79
Phase 2: Alignment. An economy that rewards participation, not extraction. Staking as the network’s heartbeat, powered by transaction fees from a Core dApp and ecosystem synergies.
3
7
97
Phase 1: Infrastructure. • Native sharding → real scalability.• Security → grounded in proven principles.• Dev experience → Web2-grade.
1
2
74
While others chose PoS, we scaled PoW. Scaling without sacrifice. Performance without trade-offs. A single, coherent Layer 1, secure, composable, reliable. This isn’t a promise. It’s live. Tested. Proven.
39
52
204
RT @TheVladCostea: Proof of Less Work & Scalable DeFi with @maudbannwart & @wachmc of @alephium (Bitcoin Takeover Podcast S16 E36) https://….
0
27
0
RT @TheVladCostea: Tonight’s interview with @MaudBannwart & @wachmc of @alephium will get postponed due to technical issues on my end. Don’….
0
12
0
Looking forward to it!.
Upcoming Bitcoin Takeover podcast episodes:. S16 E36 w/ @MaudBannwart & @wachmc . S16 E37 w/ Andrew Poelstra. S16 E38 w/ @MattAhlborg & @ziggamon . S16 E39 w/ @hashdag . Awaiting confirmation, may or may not happen: Perry Metzger, Blake Emerson, @ValVenisEnt . Subscribe!
6
2
48
Alephium is stable again, but the situation is still developing. An official update and full post-mortem will follow soon. Thanks for your support and patience. Onwards 🔥.
1
3
60
The incident lasted about 24 hours. Several core contributors barely slept. Big thanks to Maud, Hongchao, Muchen, and others who jumped in. And to the community: your alerts and feedback were incredibly helpful.
4
0
45
What did we learn?. ✅ The DAA (Difficulty Adjustment Algorithm) behaved as intended.⚠️ But the penalty curve was too steep in practice. We’ll be refining it in the future, keeping its core purpose but softening the edges.
1
1
31
A few hours later, we connected with the right pool. They responded quickly, updated their mining strategy, and pushed the change to production shortly. Roughly 10 hours later, difficulty levels is back to normal on their own.
1
0
31
With Maud’s help, we reached out to pools to confirm the behavior. It was a Friday night. No replies at first. So we kept going: digging into block data, identifying patterns, and preparing backup plans.
1
0
25
Then Muchen joined, freshly awake, and we quickly pinpointed the issue. A large hashrate was repeatedly mining only one chain at a time. That behavior triggered the penalty again and again, causing difficulty to spike rapidly.
1
0
25
The idea is simple: if too much hashrate ends up on one chain, a penalty kicks in and raises the global difficulty. But in hindsight, the penalty factor might’ve been too aggressive in certain edge cases. We started asking: do we need an emergency upgrade to change that?.
1
0
23
Hongchao quickly pointed to a likely culprit: our difficulty penalty mechanism. This system, part of Alephium's original design, discourages miners from concentrating hashrate on a single chain. That's essential for a secure sharded network.
1
0
31