RAM

conceiv3d-in-lib3rty

The 8 ETH minipools are the lowest amount, but also have a minimum RPL collateral requirement which is 10% of the borrowed amount. For an 8 ETH minipool, this becomes a minimum of 2.4 ETH worth of RPL (10% of the borrowed amount, which is 24 ETH). Maximum is 12 ETH of RPL per minipool. More RPL collateral means more yield, but also means more exposure to RPL. So really it’s 10.4 ETH that is required to start up a 8 ETH minipool. Maintenance is damn near nonexistent as long as you have a reliable setup. I spend MAYBE an hour a month maintaining it. I run mine on a 12th gen i7 NUC with 32gb RAM and a 4tb SSD w/ a UPS.

Harucifer

>A lot of stuff is measured in megabytes? When Bitcoin was created/launched in 2009, we still had: * Consumer grade computers running on less than 1 gigabyte RAM * Consumer grade internet running on less than 10mb/s * iPod Shuffles with 512-1024 mb size * DVD's were still used with their 3 to 4 gb sizes * Videocards were still touching 1gb vram Today we have: * Consumer grade computers running on average 16 GB of RAM * Consumer grade internet running on average over 150 mb/s * iPod Shuffles are completely gone, rendered obsolete with 4 gb disk space * DVD's are a laughing stock in face of fast internet and cloud computing * Video cards are breaking over 16 gb vram ​ So basically everything went up about 15 fold, but for some reason "bitcoin still needs to be capped at 1mb blocks" causing extremely high fees and slow transfer times. ​ >The problem is that no matter how big you make them they will be either too big or too small. How about just *not* 1mb lol

Ilovekittens345

All you need to read is point 7 in the whitepaper to realize that you have been bamboozled. Ever heard somebody say that storing the purchase of a cup of coffee forever on your hard drive is ridicilous? And they are right of course, but that's never been how Bitcoin was designed or even currently IS designed. To make Bitcoin work we don't need to store all our transactions forever, but only 4.2 MB of blockheaders a year. See for yourself. > 7. Reclaiming Disk Space > Once the latest transaction in a coin is buried under enough blocks, the spent transactions before > it can be discarded to save disk space. To facilitate this without breaking the block's hash, > transactions are hashed in a Merkle Tree [7][2][5], with only the root included in the block's hash. > Old blocks can then be compacted by stubbing off branches of the tree. The interior hashes do > not need to be stored. > A block header with no transactions would be about 80 bytes. If we suppose blocks are > generated every 10 minutes, 80 bytes * 6 * 24 * 365 = 4.2MB per year. With computer systems > typically selling with 2GB of RAM as of 2008, and Moore's Law predicting current growth of > 1.2GB per year, storage should not be a problem even if the block headers must be kept in > memory. Let me tell you a story to illustrate the weakness of the human mind and how easy it is to exploit it. During the summer of 2010 I first heard about Bitcoin and read the whitepaper. At the time I was the second in command of a small IT company, my friend was my boss. I printed out a copy of the whitepaper and gave it to him, you should read this I said. I think there is some money to be made. He did not read it. Over the years I worked there I kept asking him, did you read the Bitcoin whitepaper. He always had an excuse. I left that company to do my own think. Years and years later in 2018 after the first big bull run to 20K my ex boss changed his entire company and became a litecoin miner. We would actually trade asics once in a while and most of the time we would use BCH for payment. Sometimes I would hire him and pay him with BCH, sometimes he would hire me or buy hardware from my company and pay with BCH. I always asked him: did you read the Bitcoin whitepaper now? Do you understand it now? He would always till have an excuse. His company eventually went bankrupt, he got hacked. He still has no idea how Bitcoin works or what it is or what it's not. He has never forced himself to study it. He is a smart man, he could understand it. But it would take effort. Effort he was not willing to expand. You guys have been bamboozled, but it's to late now. All SHA256 coins will die. All of them where explicity designed with the blockreward as a bribe and a mechanism to distribute the coins to the people that cared to get them. The blockreward is a smaller starter engine to a bigger engine, some jet engines are actually started like this. This bigger engine never got started, there are no 100 million users that use crypto as currency on a daily bases. For any proof of work based crypto, the only way for them to be selfsustainable is to have a large amount of people making a lot of transactions all paying a very small fee that combined provides security for the system.

igadjeed

The post asks about making Core run with 512MB RAM. The recommended minimum at https://bitcoin.org/en/full-node#minimum-requirements is 2GB A SD card is not RAM

MaximumStudent1839

How am I bullshitting? Check Newegg’s prices: 1) About $370 for 4 sticks totaling up to 256 GB RAM. 2) A previous gen AMD Threadreaper with 12 cores + integrated GPU cost $300 3) You just need a $120 PSU to power since you don’t need a dedicated GPU. 4) You can get an Asus threadreaper board for about $300. 5) Add a noctua cpu cooler for another $100. There you got your computer. The total is about at $1190. Get a bundle discount you lower down close to $1000.

CreepyParsnip342

Yeah, you get a ledger and you think you are safe right? You are aware that you can burn that ledger and still have your money? Also the scammers can import your wallet to their computer if they have installed malware on your computer by now. The private keys to the ledger protected wallets will be passed around when you accept smart contract interactions like bridging etc, the keys will be momentarily in your RAM. There is no way being safe if your setup is already compromised.

Impressive_Quote9696

>I don't connect my wallet to anything besides a Zilswap - a dex, and the Tyron Sovereign identity DIDxWallet smart contact wallet. If you didint connect to the DEX with an hardwarewallet but with a hot wallet, we found the problem. You can read many problems like this with many coins even tho they didint type their private seed anywhere once. The problem with hot wallets is, that your private key will appear in your RAM if you use a hot wallet. Root Kit malware scans your RAM 24/7 and allocates your private key without a problem. Another possibility are cross site script attacks, which can happen as soon as you use your browser. There the hacker is able to use your session and act with your credentials as if it is approved by yourself.

shadowdax

Apple's stinginess with RAM is embarrassing. My phone has more. But to your question, the latest Solana build has heavily cut down on memory use, see: [https://twitter.com/7LayerMagik/status/1695888030291099814](https://twitter.com/7LayerMagik/status/1695888030291099814)

fllthdcrb

> an asset with no physical existence No such thing. Even your memory exists physically in your brain. "Digital" is also utterly different from "insubstantial". Every computer file is stored *somewhere* in the world, whether it be in RAM chips, a magnetic disk, flash memory, an optical disc, etc. The Bitcoin system? It's not some magical entity outside the universe. It exists physically in the form of nodes on the Internet, even if it's decentralized. If those nodes all disappeared, so would Bitcoin. That would be very difficult to make happen thanks to its decentralization, but it's still physical, and imperfect. But back to your brain. If you're relying on the only copy of your seed which is in your brain, that's quite a risk. > my social security number…I’ve had it memorized since I was 10 and could riddle those off to you black-out drunk. Of course you have. I imagine most Americans have. You know it so well and are unlikely to ever forget it **because you started at such an early age and have probably used it throughout your life**. But tell me this: since when have you had your seed memorized? Not so early on, right? An SSN is also less information to memorize. And there's another important difference: if you do somehow forget your SSN, I bet the government would be able to help you in some way, as long as you can sufficiently prove who you are. But if you forget a Bitcoin wallet seed, and no one else knows it, and there are no copies, then no one can do anything about it; you **will not** get that money back.

MaximumStudent1839

It is what you usually see from a server computer. That RAM requirement is to handle high throughput from parallel computer. It only costs you like 300 bucks max to get that RAM. When you compare to PoW ASIC gear for LTC/BTC, this setup is cheap as fuck.

MaximumStudent1839

>You need like $100,000 dollar computer to run a node. Where are you shopping for computers? Node requirements are, 1. 12 Core CPU with 2.8 GHz 2. 256 GB RAM 3. 500 GB SSD. If you are willing to pay $100,000 for this gig, I am happy to sell it to you and pocket a $99,000 profit. Talk is cheap. Show me the money or stfu.

ross_st

*Every* software wallet at some point needs an unencrypted instance of the private key in RAM to function. There's no way around that. That doesn't just apply to crypto wallets. If your PC is infected with a rootkit, any password you use on it is vulnerable, no matter how well-written the software you're using those passwords in is. Well-written software will hold secrets in RAM for only as long as is necessary, but if you have a rootkit that's constantly monitoring what's in RAM then that doesn't matter. And the thing about cryptocurrency wallet keys is they're in a standard format, so the rootkit knows exactly what to look for. So it doesn't even matter **which** software wallet you use, if your PC is infected with a rootkit that is able to monitor everything stored in RAM, then it will exfiltrate your private keys when they are used. The rootkits that exfiltrate private keys don't target Metamask or any specific software wallet. They just monitor RAM for the appearance of anything that looks like a private key, and exfiltrate it. The only real defence against the exfiltration of secrets from RAM is for the secrets to not be held in RAM at all, and instead be held in a hardware security module. That's what a hardware wallet is.

igadjeed

> memepool No such thing --- Bitcoin is a network of 60,000 nodes. Every node has its own mempool containing unconfirmed transactions. Any node might have a long or short mempool expiry policy. Most nodes have a 336-hour expiry policy. A node with enough RAM might have mempool expiry of many years Submitting your txID to an accelerator has no connection to any node's mempool

igadjeed

> How could Bitcoin be used by billions as a day to day way to transact It can not. That wasn't the purpose. That's a fake purpose painted onto Bitcoin more recently The purpose was to create a system which was not vulnerable to the interference (transaction censorship) imposed by regulators and corrupt politicians on centralized payment services. Especially on the Internet, the gateways (Visa, Mastercard, PayPal) had adopted the role of gatekeeper, blocking transactions for moral and political reasons The design for uncensorable transactions is a decentrlaized network of nodes, each node redundantly carrying the transaction history and processing each new block of transactions. From a regulator's point of view, this is a whack-a-mole problem. There is no way to shut down more than a handful of nodes. As long as there are enough, diversely located nodes, the system resists outside control or influence The node network has inherent latency. To keep it synchronized, the blocks need to be delayed. The average block delay is deliberately calibrated to 10 minutes To ensure node operators are not discouraged from remaining in the network, and new operators are not discouraged from joining, the hardware requirements are affordable. For affordability, the most important hardware resource is RAM. If you have a node on a laptop with 2GB RAM, you can't increase it to 4GB without buying another computer That describes running a node in 2017, when the block war was won. If this was a debate today, nobody would be concerned about losing a handful of 2011 2GB netbooks and 1GB Pi3 boards from the network. But now we know that a block size increase to 2vMB solves nothing

igadjeed

> I wonder why the original plan was only 1MB The original release had no limit, and that was unsustainable. The choice of 1MB was arbitrary, because at the time there were very few transactions After Satoshi retired, the developer group set about improving speed, so that a block can be verified (by every node, independently) and propagated from node to node as fast as possible The speedup method strategically uses RAM caching to avoid slow disk I/O. The amount of RAM required is limited by the block size. The current recommended minimum RAM is 2GB, which makes nodes affordable SegWit changed the 1MB limit to 1vMB (4 million weight units). By removing the witness component of a txinput (signature and pubkey) from the RAM cache, the increase to 1.7MB (approximately, and up to 3.7MB sometimes) blocks is achieved without increasing RAM usage From a different angle, there's no valid argument for increasing block size. The factors which cause blocks to fill and mempools to back up will cause 2vMB blocks to be full. Any block size increase has this characteristic, known in the 2015 blocksize debate as kicking he can down the road. It doesn't fix anything, except temporarily. The 2015 big block proponents claimed it was urgent and kicking the can down the road would give the community time to develop a better solution. Now it's 2023. It was not urgent. It was not even a problem, and still isn't

igadjeed

For whatever reason, you're clueless about the difference between RAM and storage, not enough basic knowledge to participate in this discussion

Leithm

>Nonsense. The point is that the witness data does not need to be cached, allowing an increase in block size without increasing a node's RAM foot print Even worse if it can't be easily discarded. ​ >BRC-20 ordinals are always less than 100 bytes. They are flooding Bitcoin mempools. SegWit is irrelevant to the discussion of current Bitcoin transaction fees Really! *How Did Taproot & SegWit Enable Inscriptions?* *While NFTs and other types of tokenization use-cases had existed on and around Bitcoin for years (as described in the prior section of this report), the building blocks that allowed the creation of inscriptions really formed in 2017. First, the Segregated Witness upgrade (BIP 141) that enacted in 2017 reorganized transactions by moving the signature data (witness) to the end of the transaction, replaced the concept of bytes (data size) with virtual bytes (weight), and recalculated the weight of signature data such that each byte of it counts as only ¼ of a weight unit. This change resulted in an effective block size increase, particularly when lots of data is stuffed into the witness portion of a transaction. Bitcoin’s next (and most recent) major upgrade, Taproot (BIP 341), activated in 2021 and brought several upgrades to the network. Importantly, though, Taproot allows for much more complex scripting in the witness portion of a transaction and also removes the size limit for witness data, among several other changes (for a more detailed explanation of Bitcoin’s Taproot upgrade, read this Galaxy Research report). These two upgrades, SegWit and Taproot, combined to both make significant arbitrary data storage possible while also making it cheaper than standard transaction data, thereby setting the stage for Inscriptions.* *While it was possible to inscribe data to a Bitcoin transaction before SegWit and Taproot with the opcode OP\_RETURN, the OP\_RETURN weight limit was 80 bytes. As a result, it became more practical to use another new type of script using Taproot when inputting arbitrary data, which allows for an unlimited amount of data to be stored through the 75% discount on weight units (up to the 4 MB limit of a block).* Source: [https://www.galaxy.com/insights/research/bitcoin-ordinals-inscriptions-5-billion-nft-market/](https://www.galaxy.com/insights/research/bitcoin-ordinals-inscriptions-5-billion-nft-market/)

igadjeed

> part of the point of this was to be able to delete that signature data? Nonsense. The point is that the witness data does not need to be cached, allowing an increase in block size without increasing a node's RAM foot print > Max Dogecoin ordinal size = 10kb (P2SH data) BRC-20 ordinals are always less than 100 bytes. They are flooding Bitcoin mempools. SegWit is irrelevant to the discussion of current Bitcoin transaction fees

keithkman

Whenever I see a bitcoin node syncing I always post this comment of mine: “Open your bitcoin node program. Next to Connect on the right click the three dots. Click Advanced Settings. Change Cache Size (MB) from 450 to 7000 if you have a 8gb RAM raspberry pi. Click Save And Restart Bitcoin Node. This will assign 7,000mb instead of 450mb RAM during syncing which will allow it to sync quicker. After the node fully syncs you can change it back to 450. It's ok to do this why your node is syncing, it won't restart the syncing process. My node took 7 days to sync and then another half day to be running in sync with the blockchain.”

CandidateNrOne

My first PC had a RAM of 2000 bytes! And there was some development! I don’t think, that development stopped on the one side of quantum!

Vegas_42

For a better understanding let me quote Satoshi: >Total circulation will be 21,000,000 coins. It’ll be distributed to network nodes when they make blocks, with the amount cut in half every 4 years. first 4 years: 10,500,000 coins next 4 years: 5,250,000 coins next 4 years: 2,625,000 coins next 4 years: 1,312,500 coins etc... When that runs out, the system can support transaction fees if needed. It’s based on open market competition, and there will probably always be nodes willing to process transactions for free. From the Bitcoin whitepaper: >A block header with no transactions would be about 80 bytes. If we suppose blocks are generated every 10 minutes, 80 bytes * 6 * 24 * 365 = 4.2MB per year. With computer systems typically selling with 2GB of RAM as of 2008, and Moore's Law predicting current growth of 1.2GB per year, storage should not be a problem even if the block headers must be kept in memory. With the calculation above you need to start with 50 BTC block reward.

benhammy

Well for the most part, the claims are said in such absolute terms that it’s incorrect to say that transactions are uncensorable, and that the network will always meet its capacity needs. It’s a dogmatic opinion, sure, but you can also derive scenarios where these opinions don’t live up to reality. It doesn’t make them presently wrong, just not always right. On the issue of RAM, there’s a larger umbrella issue of increasing the specs required to run a node as the solution to increasing transaction speed. A bigger issue that pops up is that larger blocks require larger storage drives for the historical blockchain. And while I don’t think RAM has actually been a concern, you could imagine the slippery slope of increasing the requirements to properly run a full node, until eventually control of the network lies in only the hands of people with the resources to run an enterprise grade node. People often compare bitcoin to Visa or PayPal, but I’d argue those are inaccurate comparisons. Visa can process 10,000x the transactions of bitcoin, but they’re neither final settlement, nor running on a decentralized network run by users. Their nodes are probably stupid expensive to run and maintain, but it’s simply an operating expense on a centralized network.

SmoothGoing

>transactions are uncensorable They are censorship resistant. >to avoid excess RAM usage That's definitely not why. >Bitcoin will never exceed its capacity, because historical demand, current demand and future demand are well within its limits. That's an unreasonable conclusion.

igadjeed

Full adoption is a delusion Bitcoin transactions are uncensorable. To be uncensorable, the system is implemented as a network of independently operated nodes. To ensure minimal disincentives to node operators, there is a RAM constraint To ensure the nodes stay in sync, there is a 10-minute block delay. To avoid excess RAM usage, the block size is limited to 4 million weight units * 144 blocks per day * 4 million weight units per block Full adoption isn't possible. This is not a problem. The only people who claim it i a problem are people who are not using Bitcoin for uncensorable transactions. The actual adoption for uncensorable transactions is significant, small, and constantly growing. Bitcoin will never exceed its capacity, because historical demand, current demand and future demand are well within its limits

LIGHTLY_SEARED_ANUS

So what? That's like saying the RAM in your computer doesn't run code. Secure elements don't need to run code, they just need to store it so it can be run by an external module. The instructions (i.e. code) stored in the secure element is still proprietary, and is in no way open-source. By the way, it's clear from the language you're using that you lifted your description directly from Trezor's marketing. I highly recommend not relying on the marketing materials of private corporations for education.

yorickdowne

[latitude.sh](https://latitude.sh) rents those out :). It's a 7443p with 1TB RAM. For RPC queries.

Subfolded

My mempool is configured for 5GB, but I'm also running on an 8GB RasPi4 and so I could see that happening. There are times I see the RAM usage relatively high, but I also have swap space that's utilized and so I would have assumed that would take over before it starts dumping TXs. Way over my understanding, however.

GaRGa77

Your mempool size depends on the amount of RAM you have installed iirc

MoneroArbo

nah that's many multiple blocks worth of transactions, not just one Maybe OPs system is memory (RAM) limited, causing the daemon to prune the pool at times? not due

1UazZNfbWi

Imagine a world where the largest consumer computer had 1k of memory and had to turn the screen off when it was computing because it needed the screen RAM. Then find out how recently that was.

FamousM1

The white paper says you don't need to keep the entire history, just the block headers > 7. Reclaiming Disk Space > > Once the latest transaction in a coin is buried under enough blocks, the spent transactions before it can be discarded to save disk space. To facilitate this without breaking the block’s hash, transactions are hashed in a Merkle Tree [7][2][5], with only the root included in the block’s hash. Old blocks can then be compacted by stubbing off branches of the tree. The interior hashes do not need to be stored. > > A block header with no transactions would be about 80 bytes. If we suppose blocks are generated every 10 minutes, 80 bytes * 6 * 24 * 365 = 4.2MB per year. With computer systems typically selling with 2GB of RAM as of 2008, and Moore’s Law predicting current growth of 1.2GB per year, storage should not be a problem even if the block headers must be kept in memory.

C01n_sh1LL

You could try to confirm the problem by compiling the kernel in a ramdisk location, or building Libreoffice or something else big. If those also cause shutdowns, then it's further evidence of a hardware problem. I've had better luck catching bad RAM with those techniques, than by using memtest86+ or similar tools.

C01n_sh1LL

Bitcoin Core doesn't do anything which should initiate a system shutdown. If your system is shutting down, then it's a problem with the system which is unrelated to Bitcoin. You'll need to troubleshoot your system until you are able to provide a stable platform to run the node. Syncing a node is somewhat resource-intensive, so this is probably exposing some system instability which isn't obvious when doing lighter computing tasks. The first culprit to check with these symptoms would be faulty RAM.

BuyRackTurk

an electronic CCD attached to a device driver on a computer is most certainly a network device. so is a sound card, so is a speaker, honestly even a variable speed CPU fan has been used as a network device. At very short ranges, you can even used RAM and CPU activity to send magnetic information. But cameras are 100% a bad idea for cold storage. They have a very long range, and either require a very insecure printer or else putting cold storage in the same physical space as non-cold devices for screen to screen scanning. Screen to screen camera is 100% a network and can exfiltrate large amount of information instantly. putting a camera on a cold air gap device is idiotic. > Were early kodaks network devices too? were early kodaks attached to computers? dont be daft.

ZeMadMan1

Happy Cake Day dear bot! May your moons bring you all the electricity, RAM and posts you could dream of.

MaximumStudent1839

>I'm strong anti-cryptocurrency :D I wrote what I wrote not because I am "anti-crypto". You will be surprised that I am actually "pro-crypto". I just follow this space closely enough to understand what is really greasing the wheel in the crypto social economics. >And not because computers cost 10 times more then NES? :D Sure The cost was another factor. But the main factor was tech. You needed to understand what RAM, GPU, CPU, etc. meant. I had friends who came from rich families. They could easily afford to assemble PCs. But they didn't, because it was too technical. It was so much easier to ask their parents to buy them consoles. >Not because that was new, but because people were illiterate, sure No, I am talking about high school/college graduates. They aren't "illiterate". They know how to read and write better than most bozos in Web 3 space. They were educated, just not in PC talk/jargon. >So to compare that to crypto world is somewhere in time when bitcoin was created and nobody know about it basically. It is nice that you mention BTC. Even in the early days of BTC, you always had a hardcore group that wasn't there for the money and slowly grew in size over time. Trust me, it is a lot harder to store BTC and trade it back than compared to buy NFTs in Web 3 today. My point is, that both BTC and PC gaming had a core community that stuck around and grew over time. It was much harder for them to access their world than it is now with accessing "Web 3". The stunted growth in Web 3 shows the problem really isn't just tech inaccessibility. It is a lack of product market fit. > English not my language, but i know that "invested" not always means something about money. I think what you were going at is, the lack of non-speculative product market fit. Yes, I agree. The bozos that run this space have no idea what to build to attract genuine demand. > why it shoud happen. There are some good reasons why. For example, trading in-game items is not a bad idea for gamers. But the focus should have been secondary. Instead, all these bozos run their projects to launch NFTs and shitcoins first for degen to speculate than a functioning game.

d3dRabbiT

Any old computer will do. Start9 software seems to have RAM issues even though it says it is not using it. If use Start9, make sure the box has at least 8gb of RAM. Also you will want to use an SSD or things will be slow, at least 1TB for the existing chain and some growth. Nothing else really needs to be 'beefy' on the machine. Any old box will do.

information-zone

\> if you’re mining, you need to keep a ledger correct? No. Mining is done on special hardware that connects to a central computer to get chunks of work. (\*Central to the mining pool. Not central in the sense of any government or single company.) \> can i run a ledger and not mine? If by 'ledger' you mean a hardware wallet made by the company named Ledger. Yes. You do not need to mine to use a hardware wallet. \> is that called a ‘node’? A node is software that keeps a copy of the full Bitcoin blockchain. (\*There are pruned nodes which technically don't have the full BTC blockchain.) \> does that make any money? from transaction fees? No. \> where do i find the software to do that? The software to run a node is named 'bitcoind' which you should be able to download from github if I recall correctly. There are also prepackaged operating systems you can install, like umbrel and raspbllitz which will run the node as well. \> that must require a ton of memory? how much? RAM requirements are around 2GB to 8GB, but disk requirements are around 500 GB + \> does lightening network work well? who uses it. i have blue wallet and don’t see it available on there. Yes. Lightning works well. Many people use it. I don't know the names of everyone who uses it. Please feel free to ask more questions here & do not respond to people who want to help you over direct messages.

KMan471

As long as you have at least 600 GB storage free, (preferably one terabyte, due to growth), and ideally 8 GB of RAM, you certainly can. Just go to bitcoin.org, download the installation version for your operating system, and follow the instructions. It’s super super easy.

KMan471

A regular PC or laptop, with at least one terabyte of space, and 8 GB of RAM It’s incredibly easy, but takes quite a while to synchronize the Blockchain, if you have a slow Internet connection.

hoanglpr

What's your budget. I tried all RPi4 models with different RAM configurations. Slow and unreliable sometimes. Better off buying a Mac Mini 2012 model which allows you to upgrade RAM. 16 GB RAM model shouldn't cost more than 100 bucks. Grab 1 TB SSD. You're gonna sync the entire Blockchain in 1 day. Much faster and more reliable than the RPi model. One limitation: if there is a power cut, you need to manually turn on the machine.

igadjeed

The initialization time is not caused by slow downloading. The bottleneck is the I/O overhead in the UTXO database. You can reduce disk I/O by allocating more RAM for caching UTXOs. This can speed up the initialization by about 60% Set this in your bitcoin.conf dbcache=14800

Crypto_Cadet

I was able to sync the entire chain (this was about 2 years ago now) on a RPi 4 8GB RAM. 1TB SSD in 72 hours.

Halo22B

Download speed is less important than RAM and processing power....every block needs to be validated. That being said a modern laptop with 16Gb of RAM should be powering through that....what else is currently running ?

igadjeed

Go back to 2011. Bitcoin is approaching its third birthday, and a perceptive coder from Google with too much spare time reviews the launch and adoption of several altcoins. The lessons learned from that review help him to plan a new altcoin with a better chance of adoption His plan ... Start with an exact copy of Bitcoin. Make two very small changes. Code these changes in a minimal way, so that future Bitcoin upgrades can be implemented in the new coin simply by reapplying these small changes, maybe twice per year The changes ... The main change is a different proof-of-work hashing algorithm. A RAM-heavy algorithm is chosen to discourage the creation of ASIC mining hardware. Also, the reason for choosing a new algorithm is to minimize the opportunity for 51% attacks on launch day (these attacks had ruined the launches of other altcoins) Make the block interval 2.5 minutes. This isn't significant, but it is a "difference", something to answer, "how is this different?", to attract adopters It was announced. A group of adopters was enthusiastic. After a few weeks it was launched. It still exists Now answer this * what is this altcoin? * has it displaced Bitcoin?

CosmicRuin

Yes, but there's no need for the additional Pi 5 performance for simply running a BTC and/or LNC node. RPi4 with either 4 or 8 gb (RAM) will do just fine.

maximovious

How can it be limited to millions? Theoretically, couldn't you set up 2 nodes to transact with each other back and forth millions of times per second? Those 2 nodes could even be on the same physical hardware, using the same RAM.

igadjeed

> Bitcoin can't become a form of exchange Bitcoin is already a form of exchange, for those people who know they need uncensorable transactions, where their merchants have chosen to accept Bitcoin. If you're not aware of this, you're stuck in a room full of people who don't use Bitcoin, but have adopted the beliefs embodied by delusions of Bitcoin as world currency --- Bitcoin is (always was) a system for uncensorable on-line payments. To make payments uncensorable, Bitcoin is a networked system of independent nodes. To ensure the node network remains synchronized, new transactions are collected into blocks and blocks are delayed 10 minutes, one after the other. Transactions are only uncensorable if the node network is actually decentralized - sufficient number of node operators, and diverse network. To ensure decentralization, the node software's RAM footprint is kept low, so that node operators are not discouraged from remaining in the network, and new node operators are not discouraged from joining. Keeping the RAM footprint low is implemented by limiting the maximum size of a block to 4 million weight units (also referred to as 1 million vbytes) The maximum daily transaction volume for Bitcoin is defined by those two parameters - the 10-minute block interval, and the size limit of a block. The transaction volume ceiling is many orders of magnitude below your world currency delusion These parameters can be changed by creating a new cryptocurrency. The new cryptocurrency might be tunable to be a world currency. It will be centralized. Several cryptocurrencies have already been created as experiments to vary block interval or block time. Some are centralized (BCash and its two offspring). Others may become centralized, or may break in other ways, if their transaction volume ever grows to fill their more frequent blocks Bitcoin's current usage for uncensorable transactions is well below its capacity. Bitcoin does this extremely well. Bitcoin will never "change the current monetary system and replace the failing fiat standard"

CointestMod

#Avalanche Pro-Arguments Below is a Avalanche pro-argument written by ExchangeEnough7821. > AVAX Pros: (similar to my previous Avax post from the January round) > > What is Avalanche? > > Avalanche is a cryptocurrency that uses smart contracts in order to host a large number of blockchain projects. It is one of the many coins that potentially could rival Ethereum. The two main priorities and focuses of the AVAX project are the speed of transactions of this coin, and the scalability of this coin and its infrastructure. Finally, the avalanche is completely open source, so all users can add to or just look at the code that makes up AVAX. > > What are the pros of Avalanche? > > Most notably, Avalanche has a very quick transaction processing speed, So far, AVAX can handle 4,500 transactions per second, a large increase compared to Ethereum’s 15 per second - seemingly tiny in comparison. Therefore, Avalanche has a greater ability to scale large amounts – it can handle large demand and interaction that comes with a popular network. > > One of the things most valued by those using the AVAX blockchain and invested in the avalanche coin is the rewards given for processing AVAX transactions. This reward structure is so attractive particularly due to its low system requirements- only 4GB RAM and a 2GHz CPU are needed, making this reward structure accessible to everyone, in turn making the user base of AVAX larger. By rewarding participation, it encourages users to get involved with the avalanche network. > > Finally, Avalanche uses 3 compatible and interoperable blockchains that, when used together, can overcome issues faced by other blockchains. The first of these is the X-Chain, which is responsible for creating and exchanging the AVAX assets and of course coins. Secondly, there is the C-Chain (the contract chain) which is for hosting the decentralised applications and smart contracts. Finally, the P-Chain keeps track of active subnets, and easily creates new ones. When all of these are combined, the AVAX blockchain is well rounded and with few flaws. > > In conclusion, the main pros of the Avalanche network is its incredibly fast processing speed, rewards scheme and the interoperable blockchains that overcome issues faced by many other ones. ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Avalanche) to find submissions for other topics.

CointestMod

#Avalanche Pro-Arguments Below is a Avalanche pro-argument written by ExchangeEnough7821. > AVAX Pros: (similar to my previous Avax post from the January round) > > What is Avalanche? > > Avalanche is a cryptocurrency that uses smart contracts in order to host a large number of blockchain projects. It is one of the many coins that potentially could rival Ethereum. The two main priorities and focuses of the AVAX project are the speed of transactions of this coin, and the scalability of this coin and its infrastructure. Finally, the avalanche is completely open source, so all users can add to or just look at the code that makes up AVAX. > > What are the pros of Avalanche? > > Most notably, Avalanche has a very quick transaction processing speed, So far, AVAX can handle 4,500 transactions per second, a large increase compared to Ethereum’s 15 per second - seemingly tiny in comparison. Therefore, Avalanche has a greater ability to scale large amounts – it can handle large demand and interaction that comes with a popular network. > > One of the things most valued by those using the AVAX blockchain and invested in the avalanche coin is the rewards given for processing AVAX transactions. This reward structure is so attractive particularly due to its low system requirements- only 4GB RAM and a 2GHz CPU are needed, making this reward structure accessible to everyone, in turn making the user base of AVAX larger. By rewarding participation, it encourages users to get involved with the avalanche network. > > Finally, Avalanche uses 3 compatible and interoperable blockchains that, when used together, can overcome issues faced by other blockchains. The first of these is the X-Chain, which is responsible for creating and exchanging the AVAX assets and of course coins. Secondly, there is the C-Chain (the contract chain) which is for hosting the decentralised applications and smart contracts. Finally, the P-Chain keeps track of active subnets, and easily creates new ones. When all of these are combined, the AVAX blockchain is well rounded and with few flaws. > > In conclusion, the main pros of the Avalanche network is its incredibly fast processing speed, rewards scheme and the interoperable blockchains that overcome issues faced by many other ones. ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Avalanche) to find submissions for other topics.

CointestMod

#Avalanche Pro-Arguments Below is a Avalanche pro-argument written by ExchangeEnough7821. > AVAX Pros: (similar to my previous Avax post from the January round) > > What is Avalanche? > > Avalanche is a cryptocurrency that uses smart contracts in order to host a large number of blockchain projects. It is one of the many coins that potentially could rival Ethereum. The two main priorities and focuses of the AVAX project are the speed of transactions of this coin, and the scalability of this coin and its infrastructure. Finally, the avalanche is completely open source, so all users can add to or just look at the code that makes up AVAX. > > What are the pros of Avalanche? > > Most notably, Avalanche has a very quick transaction processing speed, So far, AVAX can handle 4,500 transactions per second, a large increase compared to Ethereum’s 15 per second - seemingly tiny in comparison. Therefore, Avalanche has a greater ability to scale large amounts – it can handle large demand and interaction that comes with a popular network. > > One of the things most valued by those using the AVAX blockchain and invested in the avalanche coin is the rewards given for processing AVAX transactions. This reward structure is so attractive particularly due to its low system requirements- only 4GB RAM and a 2GHz CPU are needed, making this reward structure accessible to everyone, in turn making the user base of AVAX larger. By rewarding participation, it encourages users to get involved with the avalanche network. > > Finally, Avalanche uses 3 compatible and interoperable blockchains that, when used together, can overcome issues faced by other blockchains. The first of these is the X-Chain, which is responsible for creating and exchanging the AVAX assets and of course coins. Secondly, there is the C-Chain (the contract chain) which is for hosting the decentralised applications and smart contracts. Finally, the P-Chain keeps track of active subnets, and easily creates new ones. When all of these are combined, the AVAX blockchain is well rounded and with few flaws. > > In conclusion, the main pros of the Avalanche network is its incredibly fast processing speed, rewards scheme and the interoperable blockchains that overcome issues faced by many other ones. ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Avalanche) to find submissions for other topics.

crawleyfinance

Also life was much simpler (somehow!?). Nokia and BlackBerry were the rage and 512mb RAM was just about enough!

Geolinear

Desperate upgrade to the RAM on my computer lol. Otherwise I wouldn’t be selling.

KIG45

Solana has a new privacy update. You will be able to hide the amount when you make a transaction. Also, the RAM memory for the validators in the transaction itself has been significantly reduced.

mnkbstard

>Firstly, the use of Tails. I've got it booting without any network access but I'm plugging it into a PC that would normally have network access. The question is, will that be secure enough? Tails only uses RAM, and wipes it when shutting down. it's safe to use. >Second, I'll store the seed on the persistence partition and I'm assuming that's safe? If someone got hold of the physical USB then how difficult would it be to crack the encryption? persistence partition is LUKS encrypted. as an alternative, if you really need to store your seed on digital media instead of using analog support, you could use a dedicated marked "do not use online" USB drive and an encrypted keepass file for example. >Finally, just what difference will it make if I generate an Entropy using a Libre Calc RAND function as opposed to physically rolling dice? Are the dice rolls worth the effort or is the difference minimal? as another user already answered using dice rolls will ensure easily verifiable entropy for a relatively low effort.

mnkbstard

> Firstly, the use of Tails. I've got it booting without any network access but I'm plugging it into a PC that would normally have network access. The question is, will that be secure enough? Tails only uses RAM, and wipes it when shutting down. it's safe to use. >Finally, just what difference will it make if I generate an Entropy using a Libre Calc RAND function as opposed to physically rolling dice? Are the dice rolls worth the effort or is the difference minimal? as another user already answered using dice rolls will ensure easily verifiable entropy for a relatively low effort.

coinfeeds-bot

tldr; The International Monetary Fund (IMF) has released a working paper calling for greater oversight on the crypto market. The paper highlights the significant macro-financial risks associated with crypto assets and proposes a new tool called the Crypto Risk Assessment Matrix (C-RAM) to monitor and assess these risks. The IMF emphasizes the need for international cooperation and expansion of current policy frameworks to effectively manage the risks posed by the decentralized nature of the crypto market. The paper also criticizes countries that have mandated bitcoin as legal tender, warning of the potential systemic financial risks. The IMF plans to update its framework and coordinate international efforts to address the risks from the crypto sector. *This summary is auto generated by a bot and not meant to replace reading the original article. As always, DYOR.

MadManD3vi0us

Here's what it has to say: Designing a comprehensive policy for monitoring and mitigating systemic risks arising from crypto assets requires a multi-faceted approach. Here's a proposed framework for an improved policy: **Title: Framework for Crypto Asset Systemic Risk Assessment and Mitigation** **Objective:** To establish a robust framework for understanding, tracking, and mitigating systemic risks associated with crypto assets while promoting innovation and financial inclusion. **1. Risk Assessment Matrix (RAM):** - Develop a comprehensive RAM that evaluates global and country-specific risks associated with crypto assets. - Incorporate factors such as market volatility, leverage, liquidity, and market concentration. - Continuously update the RAM to reflect the evolving crypto landscape. **2. Regulatory Collaboration:** - Encourage collaboration among international regulatory bodies, governments, and industry stakeholders to harmonize crypto asset regulations. - Establish a global standard for reporting crypto-related data to ensure transparency and consistency. **3. Prudential Oversight:** - Implement prudential regulations for crypto asset service providers, including exchanges, wallets, and custodians. - Require regular financial and security audits to ensure compliance with established standards. **4. Market Surveillance:** - Develop advanced market surveillance tools to detect and prevent market manipulation, fraud, and insider trading. - Collaborate with crypto exchanges to monitor suspicious trading activities and enforce regulatory actions when necessary. **5. Investor Protection:** - Educate investors about the risks associated with crypto assets and promote responsible investing. - Establish clear guidelines for crypto asset disclosures, including risks and potential losses. **6. Cross-Border Cooperation:** - Facilitate international cooperation to address cross-border challenges related to crypto assets, such as money laundering and terrorism financing. - Establish a mechanism for sharing information and coordinating regulatory actions. **7. Technology and Innovation:** - Encourage the development of blockchain and crypto-related technologies while maintaining a strong focus on security and risk mitigation. - Support research initiatives to better understand the potential systemic impacts of emerging crypto technologies. **8. Crisis Management Plan:** - Develop a crisis management plan that outlines procedures for handling major crypto-related incidents, including exchange insolvencies or security breaches. - Ensure adequate funds are set aside to reimburse affected investors. **9. Periodic Assessments:** - Conduct regular assessments of the crypto market's systemic risk profile. - Adjust policies and regulations based on emerging risks and industry developments. **10. Legal Framework:** - Establish a legal framework that clearly defines the rights and responsibilities of all parties involved in the crypto ecosystem. - Ensure enforceability of contracts and legal recourse for disputes. **11. Public Awareness:** - Launch public awareness campaigns to inform individuals about the risks and rewards of crypto assets. - Encourage responsible use and investment in crypto assets. **12. International Best Practices:** - Continuously review and adopt international best practices in crypto asset regulation and risk management. This policy framework aims to strike a balance between fostering innovation in the crypto sector and safeguarding financial stability. It acknowledges the global nature of crypto assets and the need for coordinated efforts to address systemic risks effectively. Regular updates and collaboration with industry participants are essential to ensure the policy's relevance and effectiveness in a rapidly evolving landscape.

Probably_notabot

The IMF can C-RAM their proposals up their A-SS

coinfeeds-bot

tldr; An IMF paper has proposed a framework for assessing systemic risks associated with crypto assets. The framework, called C-RAM, aims to assist policymakers and regulatory authorities in containing potential risks from the crypto sector. It takes a three-step approach, assessing the importance of the crypto sector to a national economy, examining indicators of systemic risk, and analyzing global macro-financial risk. The paper highlights the need for thorough regulatory and policy frameworks to mitigate the risks posed by crypto assets. *This summary is auto generated by a bot and not meant to replace reading the original article. As always, DYOR.

castorfromtheva

Go with the mini PC option: Just get a used Lenovo tiny m700 or similar (an i3-6100t is sufficient, but you can also go with more powerful i5, but in terms of energy usag don't take anything lower 6th generation cpu) with at least 8Gbyte RAM and a 2Tbyte SSD. Much more powerful than a Pi, yet cheap (used, around 100 bucks plus 80 bucks for a fresh SSD) and easily upgradeable. Install Ubuntu. And then on top setup Umbrel (or Raspiblitz on a Debian system). Or do everything manually following the http://minibolt.info guide. Energy-consumption-wise you'll pay around 2 bucks per months, which would be 1 buck per month using a pi. It's really a powerful enough machine that's even easily upgradeable and cheap.

Downtown_Estimate_13

Anything, including a washing machine, with adequate RAM, is technically able to run Bitcoin.

igadjeed

This question used to be a hobby horse for me. Have a brain dump ... Many years ago I tried to get an honest answer to this question, got the same bullshit "Satoshi's word isn't sacred" responses All the technical responses I got claimed (falsely) that the entire chain is necessary for validating the current state. There was a nuance in this argument, about the depth of a potential chain tip reorg. Separately from this discussion there was once a discussion about limiting the chain tip reorg depth. The argument was resolved in favor of having no limit. You can't prune fully spent transactions if they might be in a to-be-reorged block. Obviously, your "older than 5 years" is beyond any possible tip reorg The ignorant responses here can be ignored. Those Redditors don't have a clue about the section 7 proposed mechanism, do not understand the anti-double-spend mechanism, or the Merkle tree Fact: any transaction where all the TXOs are spent no longer participates in consensus. A TXO can only be spent once. After spending, it no longer appears in the UTXO database. Therefore, it is not required to remain stored in a block for eternity There is no process in Core or any of the other node implementations which proves transaction validity from the present back to the "original mined coin". This false belief is a common consequence of the "blockchain is public" discussions The public nature of the blockchain is for proving that all txInputs are valid spends. This proof is simple * the TXO being spent must exist * the TXO being spent must not have been spent already The only trace link in the blockchain is from a txInput back one step to the TXO being spent. Validity of spending only needs to go back this one step, and then find the TXO in the UTXO db At block level, validation includes proving that the Merkle root hash stored in the block header is valid. The section 7 proposal is to replace a deleted transaction with its hash, and traverse up the tree to replace pairs of hashes with their next-level Merkle node hash. And then, as written, a block with all fully spent transactions has no requirement to re-prove its Merkle root hash, so the block remains on the chain reduced to its 80-byte header Keeping the headers forever ensures that the blocks are linked by their header hashes immutably To digress: the section 7 mechanism would not actually reduce most blocks to to their 80-byte headers, because there always remain millions of unspent TXOs. If a transaction has one unspent TXO, it can not be section 7 pruned. All its TXOs must be spent first > to keep nodes smaller and cheaper Disk space is cheap. There's no point trying to save space. Use a HDD. Spend $300 to have enough storage for 150 years of blockchain. Ignore the "SSD is essential" fools. Core runs well on a HDD, except for slow initialization (the important problem) It turns out this pruning proposal wasn't implemented because it became habit to rebuild a wallet from the full, unpruned chain, including all fully spent transactions, and the community (those few who discussed it) did not want to lose the ability to discover ancient, fully spent transactions for the sake of having complete history in a wallet. When light wallets like Schildbach and Electrum (and Armory, Multibit, etc) became popular, they were coded to search for all history, not limited to history relevant only to UTXOs Users could choose to keep old transaction history by making wallet file backups. But, how many people know how to make a backup? That ship has sailed. Some brain virus (called iCloud) made people forget that backups were ever a thing. Even so, there's a strong argument against having fully spent transactions in a wallet's history To digress: the current (clumsy) pruning method is unable to rebuild a wallet's full history. It can build it once, during node initialization. But a user with a pruned node can not add new key/address pairs if the address has history unless he rebuilds his pruned node from scratch. Also, if his wallet file becomes corrupt, or needs to be restored from it's master key backup, the node must be rebuilt from scratch. There are other functional limitations with pruned nodes. And, as mentioned already, saving disk space isn't important Why should section7 be implemented? Because the greatest deterrent to setting up a node is the long and growing initialization time. Most of this time is in the UTXO build. Blocks are processed oldest first, from block #1. As a block is processed all the TXOs from all the block's transactions are added to the UTXO database, and all the txInputs are processed to delete the linked TXOs from the UXTO database If fully spent transactions are removed from their blocks, they no longer get added and deleted to and from the UTXO database. This makes the UTXO build much faster (or does it?) That's the argument in favor of section 7. But, since it was never implemented, we don't really know if there's a saving in initialization time We do know that - given sufficient RAM, and appropriate configuration of dbcache - a huge proportion of the UTXO database can be cached in RAM during node initialization. So, while the add-then-delete UTXO db operations are inherently inefficient, their time overhead is minimized by the operations not accessing disk storage. We also know that most UTXOs are spent within 3 blocks, so the biggest benefit of this caching does not need very much RAM anyway --- I think that's a full explanation. Personally, I think there's room for an altcoin which has Satoshi pruning, if it also has coin expiry. Then the pruning effectively keeps the chain a constant size, defined by all the transactions in the expiry period But coin expiry isn't for Bitcoin. The hoarders expect their great-grandchildren to inherit their 2011 UTXOs Bitcoin is a long-term experiment in "can technology keep ahead". That is, as more and more coins become unspendable, the UTXO database grows larger and larger, but very slowly. Does it ever become too big to be unmanageable, or do CPU power and RAM cost decrease more than the UTXO set bloats? I've done rough estimates. The UTXO set can keep growing for at least 50 more years without making Bitcoin nodes expensive

UntuckedKing

Gotcha. Makes sense because I have seen others say they’ve had trouble running a node on an old laptop. A friend helped me swap my SSD and RAM cards so I always forget I even did that on that old computer

strongboy54

Yeah you're absolutely right. The server has 64 GB RAM, CPU is AMD 5700G, 5 HDDs in RAID 6, not sure about IO speeds, but last test I did transferring 2 TB from 1 VM to another(Not over LAN), it maintained full network speed (1gbps) throughout the transfer. I'd assume that means it's more than good enough. I guess I'll also have to do the same and just run it in docker and individually manage each node.

Virgine

You know running node takes a lot of network bandwith, CPU, RAM, disk space and disk bandwidth? What are the specs of your server? You Will need a very robust one to run multiple chain nodes. For your question, i use docker as well, i dont know software that manages multiple chains

DoragonMaster1893

Was preparing to throw away an old laptop, but thinking better and consider it has decent specs (i7 CPU, 16GB RAM, 1TB SSD), why not use it as playground for some stuff, including crypto. What should I run that is not that intensive in terms of resources and it's relatively easy to setup? Note that I don't plan to have this machine up 24/7. just want to play with the tech.

teh_d3ac0n

To sell those memory RAM sticks for 5 BTC and hold them till after 2024 halving

igadjeed

> world reserve currency Bitcoin is a system for uncensorable digital transactions. To be uncensorable, the processing and data store are distributed to thousands of independently operated nodes. For the node network to remain synchronized blocks are separated by 10 minutes. To avoid centralization of the node network, block size are constrained. This makes node hardware affordable, specifically in the RAM requirement These constraints - 144 blocks per day, 4 million weight units per block - make it absolutely impossible for Bitcoin to ever be a world reserve currency Take away the constraints, centralize Bitcoin, call it PayPal. Now it's censorable Bitcoin can never be a world reserve currency

igadjeed

Building the UTXO database takes 24 hours. Downloading only takes about 8-10 hours. But a node does both things at the same time. So you can't speed it up, unless you have enough RAM to increase dbcache. That might save about 6 hours

MinimalGravitas

It might work, but you probably want 16GB of RAM, which is cheap and easy to chuck into an old PC, but I'm not sure if you can add RAM in a laptop. If you only have 8GB of RAM you will be limited on what clients you can choose. Probably Nimbus would be your only option on the Consensus layer, and I'm not sure for the Execution layer. An external SSD is fine.

Aussiehash

I would suggest you run a full node (Pi4B 8GB RAM) with Raspiblitz (Fulcrum electrum server) then all of your relatives can connect their SparrowWallet to your Fulcrum Electrum Server and custody their own coins

CarelessHumor9096

My favorite is Kill Gates saying home computers would NEVER need more than 1 MEGAbyte of RAM. Now you need 16,000 times that to get a Windows machine to work good.

castorfromtheva

Go with the mini PC option: Just get a used Lenovo tiny m700 or similar (an i3-6100t is sufficient, but you can also go with more powerful i5, but in terms of energy usag don't take anything lower 6th generation cpu) with at least 8Gbyte RAM and a 2Tbyte SSD. Much more powerful than a Pi, yet cheap (used, around 100 bucks) and easily upgradeable. Install Ubuntu. And then on top setup Umbrel (or Raspiblitz on a Debian system). Or do everything manually following the http://minibolt.info guide. Energy-consumption-wise you'll pay around 2 bucks per months, which would be 1 buck per month using a pi. But it's really worth investing the 2 bucks and have a much more powerful machine that's easily upgradeable.

Equivalent-Fun-4587

I have added there top reports, and I tried htop as well. It shows bitcoind reaches 52% of physical RAM usage before it dies. Besides 8GB of physical RAM, it also has 4GB additional of swap. It makes no sense the error it shows.

igadjeed

I would make a guess at this, but you've presented the issue report as a moving target. Your conf has no dbcache, but you say you've played with dbcache In a different direction, are you running a 32-bit Linux or a 64-bit Linux? If you're running 32-bit Linux, you're limited to accessing 4GB RAM. In this case, keep dbcache below 2800 (allows 1.2GB for OS) But it would be better to use 64-bit Linux and set dbcache to 6800 The storage device you're using is irrelevant to the out of memory error. Ignore those comments in this thread

KMan471

I run a node on a 12 year old computer with 8 GB of RAM. It’s literally free to download the bitcoin QT node.

igadjeed

Pi3 has 1GB RAM, less than the 2GB recommendation, but enough, with some config tweaking. Plug in a 2TB external HDD Pi4 does not have a 16GB RAM option Lightning channels need funding. The Lightning subreddits have Lightning node operators looking for channel peers. See those threads to get an idea of the funding amounts required A Lightning node is different software, additional to installing Bitcoin Core for a Bitcoin node

fverdeja

Raspi 3B is not enough, you'll need at least 2 GB of RAM to run a Bitcoin Core node. Also, understand that a Bitcoin node and a Lightning node are not the same thing, for running Bitcoin core you don't need to open channels with anything since all you are doing is downloading a copy of the blockchain and relaying transactions and blocks, while a Lightning node needs you to add some liquidity and open channels because that's the way LN works, but not bitcoin itself. You could open many 10.000 sats channels (2,5 USD right now) and be set if you use LND which supports AMP transactions that are multiple small TXs that make up for one single payment, but realistically that's not so viable today.

castorfromtheva

Raspi3 isn't sufficient. You need at least a 4b with 4 gigs of RAM, better 8. My advice: Go with the mini PC option: Just get a used Lenovo tiny m700 or similar (an i3-6100t is sufficient, but you can also go with more powerful i5, but in terms of energy usag don't take anything lower 6th generation cpu) with at least 8Gbyte RAM and a 2Tbyte SSD. Much more powerful than a Pi, yet cheap (around 100 bucks) and easily upgradeable. Install Ubuntu. And then on top setup Umbrel (or Raspiblitz on a Debian system). Or do everything manually following the http://minibolt.info guide. Energy-consumption-wise you'll pay around 2 bucks per months, which would be 1 buck per month using a pi. But it's really worth investing the 2 bucks and have a much more powerful machine that's easily upgradeable.