Tom Harding
139 messages and 10 threads started, 7 Apr 2014 to 4 May 2026.
First post: Why are we bleeding nodes?. Latest: Fly Client Proposal.
Messages by year
| 2014 | 23 | |
|---|---|---|
| 2015 | 89 | |
| 2016 | 7 | |
| 2017 | 12 | |
| 2019 | 1 | |
| 2022 | 1 | |
| 2023 | 3 | |
| 2025 | 1 | |
| 2026 | 2 |
Writes about
Most active in
- deterministic transaction expiration 5 of 34, 2014
- Address Expiration to Prevent Reuse 5 of 17, 2015
- Bitcoin Core and hard forks 5 of 86, 2015
- A statistical consensus rule for reducing 0-conf double-spend risk 4 of 5, 2014
- DS Deprecation Window 4 of 7, 2014
- replace-by-fee v0.10.0rc4 4 of 79, 2015
- Block Size Increase 4 of 116, 2015
- BIP 68 (Relative Locktime) bug 4 of 7, 2015
- Block size following technological growth 4 of 111, 2015
- Dynamically Controlled Bitcoin Block Size Max Cap 4 of 24, 2015
- Anti-transaction replay in a hardfork 4 of 21, 2017
- First-Seen-Safe Replace-by-Fee 3 of 12, 2015
- BIP for Proof of Payment 3 of 32, 2015
- BIP: Full Replace-by-Fee deployment schedule 3 of 20, 2015
- Mempool "Expected Byte Stay" policy 3 of 5, 2015
Threads started
Newest first.
2017 1 thread
- High fees / centralization Tom Harding8 messages
2016 1 thread
- Proposal: Hard fork opt-out bits Tom Harding1 message
2015 6 threads
- Mempool "Expected Byte Stay" policy Tom Harding5 messages
- BIP 68 (Relative Locktime) bug Tom Harding7 messages
- Block Size Experiment Underway Tom Harding22 messages
- No Bitcoin For You Tom Harding13 messages
- Address Expiration to Prevent Reuse Tom Harding17 messages
- 3 messages
2014 2 threads
- DS Deprecation Window Tom Harding7 messages
- 5 messages