Correspondence topic guide · Edition 1.0.0
Scaling & fees
A source-led map of capacity, bandwidth, storage and fee discussion across the launch-era mailing lists and public forums.
What this guide includes.
This guide groups records tagged scalability or fees. The categories overlap but are not equivalent: some fee records concern spam or relay policy, while some scaling records concern bandwidth, storage or throughput.
Limit: Historical remarks are not a current capacity forecast or a complete policy prescription. Network conditions, implementations and terminology have changed since these records were written.
Coverage / 2008–2010
The shape of this source set.
Counts describe indexed records, not distinct claims or unique ideas. Cross-posts, reply threads and multi-tag records can overlap.
Records by year
- 6
- 8
- 52
Records by venue
| Venue | Records | Share |
|---|---|---|
| BitcoinTalk | 53 | 80.3% |
| Cryptography list | 7 | 10.6% |
| bitcoin-list | 3 | 4.5% |
| P2P Foundation | 2 | 3.0% |
| P2P Research list | 1 | 1.5% |
Matching tag counts
- scalability2233.3% of this guide
- fees4974.2% of this guide
Tag counts can sum above the 66 unique records in this guide.
Reading lenses
Three questions to carry into the sources.
These prompts organize close reading. They are not quotations or claims attributed to Satoshi.
- 01
Resource constraints
Distinguish bandwidth and storage discussion from transaction-count claims and later debates that use different system assumptions.
- 02
Fee functions
Read fee-tagged records in context to separate anti-spam, relay, priority and long-run incentive questions.
- 03
Changing conditions
Use dates and release context before comparing a historical statement with present-day Bitcoin behavior.
Deterministic reading path
Ten coordinates across the record.
The generator removes repeated normalized subjects, then selects an even chronological spread. It is a reproducible orientation set—not a ranking of importance or a random sample.
-
01
· Cryptography list
Bitcoin P2P e-cash paper
-
02
· BitcoinTalk
Re: A few suggestions
-
03
· BitcoinTalk
Re: Command Line and JSON-RPC
-
04
· BitcoinTalk
Re: Odd amount of generated coins
-
05
· BitcoinTalk
Re: Scalability
-
06
· BitcoinTalk
Re: Transaction Overload Solution
-
07
· BitcoinTalk
Re: Development of alert system
-
08
· BitcoinTalk
Re: Version 0.3.13, please upgrade
-
09
· BitcoinTalk
Version 0.3.17
-
10
· BitcoinTalk
Re: BitDNS and Generalizing Bitcoin
Need every match? Open the searchable archive with the primary tag applied. For combined-tag coverage, use the exact selection rule recorded above.
Limited source previews
Three pointers into the full record.
Each preview is an existing archive excerpt of no more than 18 words from a separate source record. Complete wording stays at the linked archive.
· bitcoin-list
I would be surprised if 10 years from now we're not using electronic currency in some way, now…
Read the complete record in context ↗· BitcoinTalk
It would be nice to keep the blk*.dat files small as long as we can. The eventual solution…
Read the complete record in context ↗· BitcoinTalk
I agree. All transactions, IP changes, renewals, etc. should have some fee that goes to the miners. You…
Read the complete record in context ↗
Exact tags, documented era, pinned bytes.
The network-free builder verifies correspondence dataset v1.0.0 by SHA-256, includes only records marked documented-project-era, and matches exact labels in each record’s topics array. The disputed 2014 account message is excluded. Topic labels were created for discovery from subjects, normalized source text and linked quotation categories; they are not human-authored abstracts.
When citing a statement, cite the linked original or archival record—not this guide’s count alone. Source rights remain with their respective holders; this page adds original organization, statistics and limited excerpts.