Repository navigation
End-to-end demo: peering relay + policy-vs-consensus mining #5
Replies: 1 comment
3. Tried it on real testnet tooLocal regtest proves the mechanism works deterministically, but doesn't touch real network conditions. Went and tried that too — mixed, honestly-reported result: testnet-exploration.md Short version: real peer discovery and faucet funding worked cleanly. One genuine finding worth knowing about the PR's current scope — |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
End-to-end demo: peering relay + policy-vs-consensus mining
Two local regtest demos of PR #3 actually working end-to-end, beyond the unit/functional/sanitizer/fuzz testing already covered in the PR thread. Both are deterministic, zero real money, no public network — proving the mechanics before anyone touches mainnet.
1. A large, dusty transaction relays over a real dog connection
Full writeup with the actual evidence and the recovered image: Mehdalon/dogmode-relay-demo
Short version: forced an actual
dog-type connection between two nodes (same RPC the PR's ownp2p_dogmode_peering.pyuses), broadcast a 3,877,833 WU transaction — 99.4% of the actual 3,900,000 WU ceiling, 9.7x the old 400,000 WU standardness cap — carrying a 1-satoshi dust output and an image embedded inOP_RETURN, and confirmed it relayed to the second node solely over that connection — then extracted the image back out of the second node's own mempool copy and verified it byte-for-byte (SHA256 match, still opens as a valid photo).2. Standardness is a relay courtesy, not a consensus rule
Second demo, aimed at a different question: if a transaction can't relay under default policy, can a cooperating miner get it confirmed anyway?
Two nodes: one running PR #3, one built from genuinely unmodified stock v31.1 (verified zero diff on the relevant files). Connected normally (no dog-peering involved this time).
testmempoolaccepton the PR#3 node:allowed: true. Same call, same transaction, on the stock node:allowed: false, reject-reason: "tx-size". After broadcast, the stock node's mempool stayed empty — confirmed the relay wall directly rather than assuming it.confirmations:1, and the 1-satoshi output is live in its own UTXO set — permanently, on a node that would never have accepted this transaction pre-confirmation.That's the actual mechanism: relay policy only ever controlled propagation, never validity. A miner willing to include these transactions doesn't need the rest of the network's policy to change at all.
Scope note on both: local, deterministic, no real money, no public network. These demonstrate the mechanism works — they're not a mainnet or signet claim, and adoption/hashrate is a separate, much bigger question from whether the mechanism itself is sound.
All reactions