How many gigabyte is need to download and route the daily blocks data

[PostQuantumBTC]

I know full nodes are consuming data but I do not know how much data they are consuming daily for receiving and sending the latest blocks data from and to other nodes. I will like node owners to let me know the exact data.

I know the data that can be needed to download the blockchain which is above 700 gigabyte or prune node that will not consume more than 10 gigabytes can be used to start.

[LoyceV]

My full node used to upload about 2 TB per month. There's no fixed number for this.

Current specs since August 23:

Code:

  "totalbytesrecv": 44973468250,
  "totalbytessent": 1827279238373

[Cookdata]

I know full nodes are consuming data but I do not know how much data they are consuming daily for receiving and sending the latest blocks data from and to other nodes. I will like node owners to let me know the exact data.

I know the data that can be needed to download the blockchain which is above 700 gigabyte or prune node that will not consume more than 10 gigabytes can be used to start.

If disk space to keep blocks is not your problem and you want to run full node, data consumption shouldn't be your problem. It's amount of internet used in running full node will be use in running prune node, the advantage of prune is that not every blocks will be kept on your space especially when you don't have enough space.

If you want to run a full node but your concern is data consumption, there ways you can run full node with limited internet and still enjoy your full node. Just know that whatever ways, you will spend data on downloading blocks that are produce everyday. The simplest way is you can validate blocks that are produce but you don't have to relay blocks to other nodes but the setback is you wouldn't be able to relay your transactions to other nodes.

I think you should run the full node and set your own policy to how you want to manage your node, that's the best way you can manage data consumption.

[nc50lc]

I know the data that can be needed to download the blockchain which is above 700 gigabyte or prune node that will not consume more than 10 gigabytes can be used to start.

Not quite, the data consumption should be similar to both since a full node in prune mode will still download and verify all of the blocks regardless of its set size.
If you're talking about a node utilizing "assumeutxo", that will still do IBD in the background to fully verify the assumed valid UTXOs despite being synced after reaching the tip from the base block hash.

I will like node owners to let me know the exact data.

I can't comment on this because I use -maxuploadtarget in my bitcoin.conf file:

Code:

maxuploadtarget=10000m

If you'll use the info to consider whether to run a full node or not with limited internet, you can do the same to soft-cap your daily data consumption.
It usually excess the set amount quite a bit (or should I say "quite a gig") but it's effective nonetheless.