Bitcoin Technical Stack

[bob_rushford]

Hi there,

Can anyone please let me know that
what will be the Software/Hardware requirements will be better for Bitcoin.

Please mention in Stack.

Thanks in advance.

[1714006235]

1714006235

[1714006235]

1714006235

[aleksej996]

Could you be more clear?

And what is Stack?

[cellard]

Could you be more clear?

And what is Stack?

I don't know, I think he means like a list of computer parts of the recommended settings to fun a full node..

Minimum:

Disk space
145 GB

Download
500 MB/day (15 GB/month)*

Upload
5 GB/day (150 GB/month)

Memory (RAM)
1 GB

System
Desktop
Laptop
Some ARM chipsets >1 GHz

Operating system
Windows 7/8.x/10
Mac OS X
Linux

You can even lower it further if your computer is older:


https://bitcoin.org/en/bitcoin-core/features/requirements

[Xynerise]

You don't need up to 145GB space if you prune.
You can go as low as 550MB.

[cellard]

You don't need up to 145GB space if you prune.
You can go as low as 550MB.

I think these claims about pruning are misleading... you do need 145 GB at the time of the first sync. After that you are good to go with 550MB or whatever other setting you have configured, but remember that in order to enable prune mode you need to download the entire blockchain at least once... so you must be sure that you have the required free space.

Some people thought that you only need the pruned setting amount, then they realized they didn't had enough free space for the initial sync.

Also remember that if your pruned node files become corrupt, you will need to download the entire thing again.

[Xynerise]

You don't need up to 145GB space if you prune.
You can go as low as 550MB.

I think these claims about pruning are misleading... you do need 145 GB at the time of the first sync. After that you are good to go with 550MB or whatever other setting you have configured, but remember that in order to enable prune mode you need to download the entire blockchain at least once... so you must be sure that you have the required free space.

Not true.
Pruning deletes old blocks data after they've been validated, only a keeping the last few hundred blocks or so depending on the size specified.
So you do need to download the whole blockchain and verify it obviously, but you do not need to store them before you can prune; pruning happens on the fly.

Some people thought that you only need the pruned setting amount, then they realized they didn't had enough free space for the initial sync.

People run full pruned nodes on raspberry Pi's with 64GB memory just fine.

Also remember that if your pruned node files become corrupt, you will need to download the entire thing again.

This applies for unpruned nodes too.

[harbs23]

Hi there,

Can anyone please let me know that
what will be the Software/Hardware requirements will be better for Bitcoin.

Please mention in Stack.

Thanks in advance.

Bro what gadgets you are planning to use ?
and what purpose! it is for mining or for trading or for posting? be clear bro?
Because even cellphones are required to use for bitcoin for earning such as trading, posting this forum, claiming faucets sites!

[cellard]

Pruning deletes old blocks data after they've been validated, only a keeping the last few hundred blocks or so depending on the size specified.
So you do need to download the whole blockchain and verify it obviously, but you do not need to

Oh really, well that's cool, I thought that you needed the entire space at first.

It would be cool to be able to run a pruned node by only downloading the last 550 MB of blocks or whatever setting you've selected, but I guess that is nonsense and would lead to endless possible exploits and problems.

What is the ideal setting to use in terms of decent security levels? if the setting is too low, it wouldn't be safe, if it's too high, it defeats the purpose of prunning... what is a good balance? 10GB maybe?

[HeRetiK]

Oh really, well that's cool, I thought that you needed the entire space at first.

It would be cool to be able to run a pruned node by only downloading the last 550 MB of blocks or whatever setting you've selected, but I guess that is nonsense and would lead to endless possible exploits and problems.

What is the ideal setting to use in terms of decent security levels? if the setting is too low, it wouldn't be safe, if it's too high, it defeats the purpose of prunning... what is a good balance? 10GB maybe?

Actually I think for most use cases 550 MB should be plenty.

I'm not sure if I'm missing any metadata, but that's about 140 - 550 blocks worth of confirmations, depending on whether you assume full SegWit-transactions-only or full legacy-transactions-only blocks. Coinbase maturity seems like an adequate baseline and requires 100 confirmations, so these 140 - 550 blocks that a fully pruned node stores look good enough to me for the average user.

[Xynerise]

What is the ideal setting to use in terms of decent security levels? if the setting is too low, it wouldn't be safe, if it's too high, it defeats the purpose of prunning... what is a good balance? 10GB maybe?

There are no security implications-- as far as I know -- of running a pruned node.
Pruned nodes are still as secure as archival nodes because they download and verify the whole blockchain first but they don't just keep it on disk. For pruned nodes to be affected there should be a blockchain reorg longer than ~3 days worth of blocks.

Pruned nodes still validate consensus rules too.

The only downsides are not related to security: not being able to serve historical blocks, not able to rescan the blockchain, etc.

[cellard]

What is the ideal setting to use in terms of decent security levels? if the setting is too low, it wouldn't be safe, if it's too high, it defeats the purpose of prunning... what is a good balance? 10GB maybe?

There are no security implications-- as far as I know -- of running a pruned node.
Pruned nodes are still as secure as archival nodes because they download and verify the whole blockchain first but they don't just keep it on disk. For pruned nodes to be affected there should be a blockchain reorg longer than ~3 days worth of blocks.

Pruned nodes still validate consensus rules too.

The only downsides are not related to security: not being able to serve historical blocks, not able to rescan the blockchain, etc.

Well they may not be a security downgrade for individuals in practice, but they lower the overall security of the network... an user that wants to run a pruned node ultimately depends on other people running full nodes in order to download the network, so ideally, we want more full nodes, not just more pruned modes, otherwise like I say, you are damaging the overall network. If you can afford to run a full node, do so, pruned mode should only be enabled in extreme cases where you are living in circumstances that cannot afford you the required space etc.

[bob_rushford]

Thanks everyone I understood the requirement.
I will ask more here if needed.

Thanks again guys.

[bob123]

Even though this post is 1 month old, i'd still like to comment this because it contains wrong information.

Well they may not be a security downgrade for individuals in practice, but they lower the overall security of the network...

The overall security does NOT get lowered by running a pruned node.
The 'security' depends on the amount of miner/hashrate. Not on the amount of nodes.

an user that wants to run a pruned node ultimately depends on other people running full nodes in order to download the network,

This applies to anyone who wants to run a node. Doesn't matter whether pruned or not.
EACH node needs to download the blockchain from other peers when setting up.

so ideally, we want more full nodes, not just more pruned modes, otherwise like I say, you are damaging the overall network.

They are NOT damaging the network. They do NOT contribute to the overall health of the network, but definitely do NOT damage the network.
By the way, non-pruned nodes which do not allow incoming connections do also NOT contribute to the overall health of the network since they do not distribute old blocks to new peers.