Started muting all the filter discourse words on X. Wake me up when there is more interesting stuff to talk about.
But the recent comcast "excessive data use" controversy got me moving a little bit.
I added this line, to limit my data usage of my node to 10GB per day, to my bitcoin.conf.
```
maxuploadtarget=10000
```
You can check your data usage like this:
```
$ bitcoin-cli getnettotals
{
"totalbytesrecv": 1584250,
"totalbytessent": 449445,
"timemillis": 1756049077506,
"uploadtarget": {
"timeframe": 86400,
"target": 10485760000,
"target_reached": false,
"serve_historical_blocks": true,
"bytes_left_in_cycle": 10485310555,
"time_left_in_cycle": 85966
}
}
```
But now to the analysis part, if you are still here!
```
$ du -h --max-depth=0 /media/blockdata/bitcoin/
828G /media/blockdata/bitcoin/
```
The bitcoin blockchain is 828GB on my machine. That means with my current limit, it will take ~83 peers like me to do a full IBD. Your copy of the bitcoin blockchain is precious! You should back it up from time to time, so that if you nodes database gets corrupted, you don't have to download it all again from the public network.
If there are 100K connectable bitcoin full nodes, all with 10GB data cap, as a network we can only onboard 1207 new full nodes, per day. Thats a lot but also not that much.
Im sure there are a lot of people out there running with no limits on a large connections who are doing the bulk of the work bootstrapping new nodes, but it is interesting to think about it in the worst case.
I think it is a smart move to enable `maxuploadtarget` setting to whatever you think is best, as a general rule. Regardless if people are toying around or not, this is an adversarial network, and you should treat it as such. Don't give people permission to do what they please with your internet connection.
@Hunter βΏeaαΉ©t @The Space
