dataforge-labs/dogecoin-network-propagation

Dogecoin network propagation

How fast the Dogecoin peer network learns things, measured from connections held to its reachable peers at once.

Dogecoin targets a block every minute. That is ten times Bitcoin's rate, and it makes this the densest propagation record of the set: one 140-second window produced 33 block announcements here against a single block on Bitcoin.

Nothing here can be reconstructed later. A block carries only the timestamp its miner claimed, an announcement carries none at all, and a peer's own relay policy is broadcast and forgotten.

Contents

name	one row is
e26_doge_block_propagation	one peer announcing one block, timestamped
e26_doge_tx_propagation	one peer announcing one transaction, timestamped
e26_doge_relay_floor	one peer's own minimum relay fee, at the moment it announced it
e26_doge_p2p_peers	one peer connected to: user agent, services, handshake state

What a one-minute block buys you

Propagation is measured against the first peer to tell us, so the useful quantity is the spread across peers for the same block. On a ten-minute chain a collection window catches a handful of blocks; here it catches dozens, which is the difference between an anecdote and a distribution.

The node population is unusually uniform: peers run Shibetoshi 1.14.x almost exclusively, against the several independent implementations seen on Bitcoin Cash. A network where nearly every node runs the same build is a useful control for anything that might be implementation-specific.

Transactions are NOT sampled here

Bitcoin's transaction announcements are sampled at roughly one in sixty-four because they arrive in the thousands per second. Dogecoin does not need that: one window carried 1,080 announcements of only about 22 distinct transactions, so everything is kept. A near-empty mempool is itself the reason the propagation curves are complete rather than sampled.

Before you build on this

• Peers come from DNS seeds rather than a crawler. Two of the four published seeds no longer resolve, so the reachable set is smaller and more concentrated than Bitcoin's.
• Timings are ours and include network distance to each peer. Differences of milliseconds are partly geography; differences of seconds are not. peer_addr is retained so this can be controlled for.
• A peer that disconnects stops announcing, which resembles slowness. e26_doge_p2p_peers carries handshake state so a gap can be told from a silence.
• Merge-mined with Litecoin, so block timing here is not independent of that chain. If you are comparing the two, that is a shared cause and not a coincidence.

Partitions are parquet, one file per collection window, under dataset/YYYY/MM/. Every dataset here carries a FIXED 7-day sample WINDOW starting at its own first day of collection, together spanning 2026-08-30 to 2026-09-05, so you can check schema, coverage and quality before asking for more. It does not advance, so there is nothing to gain by re-downloading it. The full history is held privately, available on request.

from huggingface_hub import snapshot_download
import pandas as pd, glob

path = snapshot_download("dataforge-labs/dogecoin-network-propagation", repo_type="dataset",
                         allow_patterns="e26_doge_block_propagation/**")
df = pd.concat(map(pd.read_parquet,
                   glob.glob(f"{path}/e26_doge_block_propagation/**/*.parquet", recursive=True)))

Coverage

e0_run_manifest lists every collection window with its poll counts and failure counts, and is published in full rather than windowed. Gaps between windows are real, cannot be filled in afterwards, and nothing here is interpolated.

License and contact

ODC-BY: use it freely, credit "DataForge (dataforge-labs)". Questions and requests for the full history via the discussions tab.