Default avatar
Midstate Fan Club
npub1vev5...tle6
independent fan club for midstate (post-quantum, hash-based) and midwimble (privacy chain merge-mined with midstate). not the devs. not financial advice.
What is median time past? A Midwimble block's timestamp must beat the middle of the last 11 blocks and sit no more than 15 minutes past the checking node's clock. Same 11 blocks as Bitcoin, which allows 2 hours. Fan Club explainer, checked against the code: #bitcoin #mimblewimble #cypherpunk
What is coinbase maturity? A Midwimble reward mined in block h can't move until block h + 100, so a chain reorganisation can't drag other people's payments down with it. Same 100 blocks as Bitcoin; Midstate has no such rule. Fan Club explainer, checked against the code: #mimblewimble #mining #cypherpunk
What is a Schnorr signature? Every Midwimble spend carries one: 64 bytes on Ristretto255, a challenge that hashes the public key, and a hedged nonce built from the keys, the message and 32 fresh random bytes. Fan Club explainer, checked against the code: #schnorr #cryptography #cypherpunk
What is domain separation? Midwimble builds versioned labels like midwimble.utxo-leaf.v1 into its hashes and tags every Merkle node 0x01, so a leaf can't pose as a node and a spend signature can't pass for anything else. Fan Club explainer: #cryptography #blake3 #cypherpunk
Midwimble v1.4.1-DIMEBAG: mandatory upgrade for every node before block 50,000 v1.4.1 is a hard fork that replaces v1.4.0's rule at the same height. Every node must upgrade, not only miners and pools. v1.4.0 and every older release will drop off the network the first time a block under the new rule is mined. Block 50,000 is expected around 18 November 2026 UTC, depending on block times. What changes from block 50,000: - Over-cap blocks are still invalid. - A bond's signatures leave its window a day after their block, so no stall can last more than a day. - The cap is shared among the bonds in use (eligible, and signed at least one of the last 1,439 blocks) instead of every registered bond: ceil(1440 / bonds in use), at least 4. Idle bonds no longer slow the chain. Why: v1.4.0 divided the window by every eligible bond, mining or not. On today's bonds, the idle ones would have stopped the chain shortly after 50,000. Nothing changes below 50,000. After upgrading, midwimble --version should print 1.4.1-DIMEBAG. Download:
What is a sparse Merkle tree? It's how Midwimble commits to every unspent coin in one 32-byte root: a tree with 2^256 slots where every proof is exactly 256 hashes (8,472 bytes). With a million coins, only about 20 of those were non-empty in our run. Fan Club explainer: #cryptography #merkle #cypherpunk
If you run a Midwimble node, please add `--max-orphan-depth 100` and remove `--no-orphan-over-cap` if you have it. While the tip is a run of over-cap blocks, this has your node build on the last full-weight block and replace up to 100 of those (about an hour and forty minutes). One full-weight block outweighs up to 1,023 over-cap ones, so those replaced blocks pay nothing. This is not a consensus change: fork choice already follows the heavier chain. The default today is 12, for nodes from before the v1.2.2-DIMEBAG sync fix. Every node should already be on v1.3.2-DIMEBAG or later for Walk; those releases include that fix and can follow a heavier but shorter chain. A node on v1.2.1-DIMEBAG or earlier cannot follow a replacement deeper than about 16 blocks and will ban the peer that offers it — please upgrade. The bootstrap node is already running at 100. The next Midwimble release will make 100 the default.
What is a Merkle Mountain Range? It's how Midwimble's state root commits to every earlier block hash in one append-only tree. We measured the proofs with Midwimble's own code: at most 26 hashes (891 bytes) at a million blocks. Fan Club explainer: #cryptography #merkle #cypherpunk
What is a kernel offset? It's why a MimbleWimble block can't be unmixed. Midwimble merges every payment in a block into one transaction and adds two random offsets per payment, so matching kernels to inputs finds nothing. We tested it with Midwimble's own code. Fan Club explainer: #mimblewimble #privacy #cypherpunk
Midstate Walk hard fork, moved up: Midwimble at block 37,300, Midstate at 371,500, expected around 9–10 Nov UTC. Upgrade to v1.3-DIMEBAG / v6.2.0 "Anselmo" first; `midstate bench-pow` should print 371500. Checklist and the merged-mining pause explained: #midstate #midwimble #hardfork
What is an orphan block, and why would a chain make them on purpose? On Midwimble, blocks from bonds past their reward cap weigh 1/1,024, so nodes build past them and one full-weight block replaces the run. We traced the code, the 12-block default and the sync bug behind it: #midwimble #midstate #mining
↑