17 ms·
A Bitcoin full node only takes 5GB of disk space to run, and 256MB of memory. [0]: https://github.com/bitcoin-dot-org/Bitcoin.org/pull/3624/files https://githu
by crazypython 5y ago
A Bitcoin full node only takes 5GB of disk space to run, and 256MB of memory.
[0]: https://github.com/bitcoin-dot-org/Bitcoin.org/pull/3624/files https://github.com/bitcoin-dot-org/Bitcoin.org/pull/3624/fil...
[1]: https://bitcoin.org/en/full-node https://bitcoin.org/en/full-node
- rawtxapp 5y agoIn hindsight, I think most would agree it was a good idea to force the smarter scaling solutions rather than brute-force blocksize scaling (which sooner or later would have hit a ceiling anyways).
- wmf 5y agoThe "smarter" scaling solutions still aren't here after years of waiting, fees are hitting all-time highs, and other chains can do >4,000 TPS on layer 1. So no, small blocks weren't and aren't a good idea.
- rawtxapp 5y agoThey are here, the publicly known nodes alone on lightning have 1.2+k BTC locked in [1], that's ignoring all the private channels which form the majority of the channels (private channels are the end-user channels which don't route transactions themselves and are not broadcast publicly). We have easy to use wallets [2], easy ways to run lightning nodes [3]. And if you look at the average transaction value, you can see that the blockchain itself is acting more of a settlement layer rather than "coffee transactions" as it should [4]. 1: https://1ml.com/ https://1ml.com/ 2: https://phoenix.acinq.co/ https://phoenix.acinq.co/ 3: https://getumbrel.com/ https://getumbrel.com/ 4: https://bitinfocharts.com/comparison/transactionvalue-btc-xrp.html https://bitinfocharts.com/comparison/transactionvalue-btc-xr...
- wmf 5y agothe blockchain itself is acting more of a settlement layer That is a sign of failure.
- sennight 5y agoWhat is a sign of success, multicasting every transaction in the world and storing it on a public ledger? I don't remember that being in the white paper.
- rawtxapp 5y agoBecoming the most trusted decentralized worldwide settlement layer is considered a failure now? Many of the cryptos that claim to scale to thousands of tps on layer 1 are all sacrificing decentralization to achieve it, at which point, I might as well use Paypal/Visa. There's no point in being able to scale to those levels in theory if in practice no one uses them.
- riffraff 5y ago> Becoming the most trusted decentralized worldwide settlement layer is considered a failure now? it is, if the original goal was to be something else. If you start a marathon and stop to eat the greatest hot dog ever made, it wouldn't be considered a successful run, although you can say "but it was the best!" and be happy about it.
- hungryforcodes 5y agoHuh, so every startup thats ever pivoted -- including for example Instagram, AirBnB, and Twitter -- are failures huh? Interesting.
- xorcist 5y agoNot sure if it can be called a pivot when it was in the original release of the software. Payment channels aren't in the white paper but they were in the first public release and had dedicated opcodes. That first implementation wasn't very practical nor was it secure. The fact that modern payment channels are implemented with other opcodes may be a pivot in implementation but not in concept.
- alwillis 5y agofees are hitting all-time highs I just checked https://mempool.space https://mempool.space A low-priority transaction cost $2.36; medium is $4.39 and high is $7.48. To put this into context: you can send $10,000 worth of BTC anywhere in the world in an hour for $2.36 right now. A bank wire transfer for $10,000 is going to be at least $35; often it's more, depending on which country you're sending to and if you have to use an intermediate bank to get to the bank you're ultimately are attempting to reach. Bank holidays, weekends, etc. don't apply to bitcoin.
- garmaine 5y agoMy bank does those wires for free…
- csomar 5y agoInternational SWIFT wires? What's your bank?
- lhl 5y agoMy Schwab account does international wires settled in USD or in a number of foreign currencies for free. (The official fee is $15 but it’s always been refunded for me.)
- argvargc 5y ago"Free". In the case of any currency conversion - you'll likely be silently stung a single digit percentage during conversion. Check rates quoted on the final statement versus those prevailing at that time. For a few limited cases of going USD -> USD (in foreign jurisdiction), and the USD is not converted to anything else ever, there may be a net win. In all other cases (the majority), you, or the receiver will at some point be paying far more than the wire fee for any transfer over a grand or so.
- csomar 5y ago
- delaaxe 5y ago50,000 TPS for Solana
- keymone 5y ago> other chains can do >4,000 TPS on layer 1 read: other chains are centralized databases that have no business being blockchains in the first place and can be replaced by single mysql instance. the trick is not to have high TPS, bitcoin could have unlimited TPS too, it's just a single line of code change. the trick is to have a decentralized system that functions at saturation on commodity hardware. the conservative minds prevailed during scaling debate in 2015-2017, creating selection pressure for scaling solutions that optimize limited resource - chain space, rather than populist simplistic "solutions" pushed by cheap propaganda slogans like "we can do this much TPS!".
- anonymouse008 5y ago> read: other chains are centralized databases that have no business being blockchains in the first place and can be replaced by single mysql instance. This, too, has been a thought of mine, but I'm not exactly sure how I would block diagram the 'locking' mechanism for the MySQL instance. I've come to believe the locking mechanism is the nonce produced to sufficient solution parameters that appears to use the difficulty of finding said solution as its defensibility. So how do you get the 'strength' of the miners throwing ExaHashes at a solution with a single instance? We could easily snapshot the DB and sign them, however, the point of failure is no longer in a 50% attack, but in losing said key... which intuitively feels far less secure? Curious to hear your thoughts
- keymone 5y agolocking is needed to order transactions, mysql already has acid transactions. i use mysql metaphorically to describe a single centralized database protected by single entity that controls all the writes. we already have such payment systems: visa, mastercard, paypal, venmo, etc. blockchain and miners only make sense if you need and actually maintain decentralization. if you don't and/or can't - miners (and validators in PoS systems) are useless overhead.
- anonymouse008 5y agoThank you, I had never heard of ACID -- yeah, centralized vs. decentralized becomes fairly philosophical (eco vs. democratized arguments, etc). To build on the discussion, I'm more amazed at blockchain's capabilities as a cooperation engine outside of the normal channels. To that end, I'm really surprised we haven't seen significant attrition in the current legal system to smart contract systems. I guess the lack of adoption more highlights just how 'customized' a 'standard' contract or dispute is in the real world.
- dannyw 5y agoIt's not black and white. Would 2MB blocks (and hence 10GB of disk space) be a worthy trade off? The problem I see is bitcoin devs refusing to be pragmatic. Segwit is just an accounting trick.
- rocqua 5y agoI believe the point of segwit is more than accounting. Essentially these signatures /spend-scripts are pruneable once the blocks they are in are old enough. After all, if a transaction had an invalid spend script, it would not have gotten 100 blocks worth of confirmations.
- csomar 5y agoBitcoin has checkpoints: https://bitcoin.stackexchange.com/questions/1797/what-are-checkpoints https://bitcoin.stackexchange.com/questions/1797/what-are-ch... even for normal P2PK transactions.
- nullc 5y agoCheckpoints don't do what you think they do. They only exist today as a mechanism to prevent nodes from being flooded by low difficulty fork blocks, forking off back before height 230k, because the initial difficulty of Bitcoin (2^32 hash operations per block) is too low relative to multiple TH/s asic mining devices.
- keymone 5y agois there any ongoing work to have utxo set commitments? if not - why?
- nullc 5y agoI'm not sure, I haven't been actively involved in development for a couple years. There were a couple distinct activities. One is the rolling utxo hashes, which has no major engineering hurdles, and can allow a compromised security "bootstrap from a utxo set". The other are schemes that allow nodes to not have the utxo set but still validate-- these have historically had unfavorable IO costs, and the bandwidth storage tradeoff hasn't seemed that appealing-- e.g. would you find reducing storage from 10 GB to 1MB but at a cost for increasing bandwidth 10x to be appealing? In some applications it would be, not others. I believe work related to both has been ongoing, however.
- lawn 5y agoIn hindsight it should be obvious that these "smarter" scaling solutions have utterly failed to keep Bitcoin functioning as peer-to-peer electronic cash, like the original intention was.
- JohnJamesRambo 5y agoWere we getting low on disk space? https://commons.m.wikimedia.org/wiki/File:Hard_drive_capacity_over_time.png https://commons.m.wikimedia.org/wiki/File:Hard_drive_capacit... It’s perverse you are proud of that and chose a tiny hard drive size over becoming actually useful and doing more than seven transactions per second. Time marches on, technology improves, but Bitcoin is proud they can run a node on a computer from 1995.
- rawtxapp 5y agoDecentralization/trustless aspect of Bitcoin is the utmost important thing, without those, there's no need for it, we can just use fiat. Once you've accepted that premise, the next question is how do you achieve the most decentralization? The answer is by having the most nodes. How do you get people to run nodes? Make it super cheap to run. It's simple really, people are not paid to run nodes (miners != nodes). It's not about storage space, you also have to consider network latency and propagating those blocks across a large adversarial network.
- WanderPanda 5y agoThat! I would never consider running an Ethereum node but btc is well within range and is something that I’m looking at
- rawtxapp 5y agoI bought a second 10TB harddrive just to be able to run a full eth node, right now even fast sync of eth requires like 400GB+, full archives sits at 6TB+ [1]. When infura went down, the whole network had issues [2]. I'm really hoping the eth2 will somewhat improve the situation, but we'll see. 1: https://ethereum.org/en/developers/docs/nodes-and-clients/ https://ethereum.org/en/developers/docs/nodes-and-clients/ 2: https://cryptobriefing.com/infura-outage-sparks-debate-over-ethereums-decentralization/ https://cryptobriefing.com/infura-outage-sparks-debate-over-...
- wmf 5y agoNodes that neither mine nor have economic weight (e.g. exchanges) just slow down the network; they don't contribute anything.
- wereHamster 5y agoWait what? I thought a full node needed 200GB+… Since when are the requirements so low?
- Proven 5y agofull node with pruning. and gp post is wrong, it's 7 and not 5 gb. those are nice new features, except bitcoin is no longer relevant except for trading and speculation.
- msgilligan 5y ago“ It is possible to configure your node to to run in pruned mode in order to reduce storage requirements. This can reduce the disk usage from over 350GB to around 7GB.” From [1] in the parent.
- wereHamster 5y agoAh, so it's 5 (7) GB for a pruned node! That makes sense. But then the comment is inaccurate: A Bitcoin full node only takes 5GB of disk space to run, and 256MB of memory. Should instead read A Bitcoin pruned node only takes 5GB of disk space to run, and 256MB of memory. A full node may still be required for certain use setups (such as when used by lnd – a Lightning Network daemon).
- sennight 5y agoIt is definitely possible to run a lightning node using a pruned backend. The official implementation doesn't "support" it, but that is only because some additional thinking is required on the end user's part. It is really just a matter of implementing the code to instruct the backend to get the pruned, but still needed by lnd, transactions - and the work is happening: https://github.com/lightningnetwork/lnd/pull/5154 https://github.com/lightningnetwork/lnd/pull/5154
- garmaine 5y agoThe pruned/archival distinction is orthogonal from the full/simplified categorization. A full node that pruned spent transactions is not a contradiction of terms. Edit: a “full” node is one which fully validates blocks, meaning it checks that blocks meet all of bitcoin’s consensus rules. All data in bitcoin is either validated once the first time it is seen (like witness data), or at most twice (an output and its later spend). Pruned nodes garbage collect this data once it can provably never be referenced again. This does not diminish the nodes ability to check bitcoin’s consensus rules, so it is still a full node.
- weasel_words 5y agoThis is factually incorrect. And, this sort of misinformation is one of the reasons people don't like the crypto-hype. Perhaps a pruned node can get somewhere in the area of sub-10G, but a "full node" is actually at around 328G: https://www.statista.com/statistics/647523/worldwide-bitcoin-blockchain-size/ https://www.statista.com/statistics/647523/worldwide-bitcoin...
- crazypython 5y agoA pruned node is a full node. A full node is any node that is fully validating. A pruned node is fully validating; "Full nodes download every block and transaction and check them against Bitcoin's consensus rules." (https://en.bitcoin.it/wiki/Full_node#Archival_Nodes https://en.bitcoin.it/wiki/Full_node#Archival_Nodes) Pruned nodes do just that. The blockchain data structure means that once verified, you don't need to store old blocks. You only need the most recent blocks to verify new ones. The nodes you're talking about, that store the entire blockchain, is called an archival node. Anyway, encouraging people to install full nodes, pruned or not– which enforces the rules– improves Bitcoin's decentralization.[0] [0]: https://bitcoin.org/en/bitcoin-core/features/validation https://bitcoin.org/en/bitcoin-core/features/validation
- anonporridge 5y agoIt should be clarified that running a node isn't worthwhile as a "set it and forget it" contribution. If you're not actively using it for something, it will just silently break if the network does something against the rules and does nothing to improve decentralization. It doesn't even really matter from a software signalling perspective, because Sybil attacks are easy from someone with enough money to run lots of nodes. At best it's a gateway drug to get people more involved. Interestingly, running a lightning routing node actually is a way an individual can run a full node to not only generate some fees to cover the cost, but actively and consistently participate in the cyber economy and have a marginal voice in enforcing the rules. The nodes you have channels with are incentivized to care about your vote if they want to stay connected to you.
- JohnTHaller 5y agoThe current Bitcoin Core on Windows stores 366GB of data on your local drive excluding the app files. Source: Looking at the folders on my PC right now.