RAM

PeerNameCom

Start it with `--dbcache=10000` to allocate a 10 GB cache. The optimal value depends on how much RAM you have. A larger cache can significantly improve download speed—but only after the cache has been filled.

EndTheFed90210

I recommend buying your own rig. Much cheaper. I went on eBay and bought an HP Elitedesk 800 G3 Mini with an i5 6th gen quad core 3.2Ghz. Came with 8GB ram and no disk or power supply for $55. I added 8GB of RAM ($12), bought a power supply ($13), new cooling fan ($13), and used a 2TB sata ssd I already had. It runs fantastic. I do Bitcoin Node, Electrs, mempool, and Pi-Hole for DNS level add filtering. I generated my own SSL cert, opened some port forwards, use nginx reverse proxy and UFW firewall, and got a free DNS name from changeip and attached it to my ISP router. I'm able to connect apps like BlueWallet on iPhone and Sparrow Wallet on Windows PC to my own node for broadcasting transactions, and it's all secured with SSL certs and TLS 1.2/1.3. It's a bit complicated to setup, but RaspiBlitz has good guides on how to set this part up. Since Umbrel runs in a docker container, anytime I get an update, it wipes out the reverse proxy, firewall, and ssl cert. But it only takes me 10 minutes to set it up again after an update. Since I generate my own SSL certs, I consider this a safe method, because I generate a new cert key each time Umbrel is updated. If what I just typed has your head spinning, you may want to buy the premade node from Umbrel. I'm able to do this method because I'm an IT and network admin. Most people would struggle to do this on their own, and reinstalling all proxies, firewalls, and certs after an update may be a headache you don't want to deal with.

valoov

There are 10 000 000 000 possible passwords. In Atomic Wallet your password is run through a password‑hashing KDF (e.g. scrypt, PBKDF2 or similar) that uses a random salt and intentionally high work‑factor (many iterations and/or memory‑hard operations). That means each guess takes on the order of hundreds of milliseconds (or more) of CPU+RAM work, drastically slowing down any brute‑force attack. Below is an estimate of how long it would take to exhaustively try every all‑digit password of length 4–10, given two attack rates: * **Normal CPU**: \~10 password‑guesses per second (a typical 4‑core desktop). * **Fast server**: \~150 guesses per second (e.g. a 48‑thread machine with \~150 H/s). |Length|Combinations|Time @ 10 H/s|Time @ 150 H/s| |:-|:-|:-|:-| |4|10 000|16 minutes 40 seconds|1 minute 6 seconds| |5|100 000|2 hours 46 minutes|11 minutes 6 seconds| |6|1 000 000|1 day 3 hours|1 hour 51 minutes| |7|10 000 000|11 days 13 hours|18 hours 31 minutes| |8|100 000 000|115 days 17 hours|7 days 17 hours| |9|1 000 000 000|3 years 62 days|77 days 3 hours| |10|10 000 000 000|31 years 259 days|2 years 41 days| If your password was up to 7 digits long, then it would take up to 2 weeks to crack it on your computer. In worst case scenario that your password was 10 digits long you would need to rent a fast server for about 2 years to get it solved. Easy! 

pop-1988

The answer is different for ETH, because its blockchain is many terabytes. A comparison ... https://blog.lopp.net/2021-altcoin-node-sync-tests/ > mass adoption Bitcoin constrains resource usage (mainly RAM requirements, ask if you want this explained) by limiting the size of a block, and the block interval. This incidentally flows to other resources. It's very light on CPU and network, and a single affordable HDD will store almost 200 years of blockchain This constraint triggers the scaling debate. But is there a scaling issue? No. Would there be a scaling issue with mass adoption? Who cares? There has been no sign of mass adoption. The expectation of mass adoption is unrealistic. It's probably a happy coincidence. By carefully constraining resource usage, the node network is cheap to run forever. And the level of actual adoption is well within the constraints for at least 50 more years As you can see in Lopp's other articles about initialization times for Bitcoin nodes, the main unbounded constraint is the linear time increase for initializing a new node. How long is too long? Already, Lopp's 10-hour time is too long for many, and is currently increasing by about 8% per year. For an operator with an HDD, the time is about 60 hours Nothing else has adoption anywhere close to Bitcoin. The "Bitcoin equivalent" blockchains (LTC, DOGE, Monero) have so little usage that they don't even function as spillover options for when Bitcoin is occasionally congested. ETH is bloated from its not-Bitcoin design, an indicator of the folly of arbitrarily discarding Bitcoin constraints. ETH has the remarkable twin features of almost no usage, and a bloated chain making it too expensive to operate a node

Numerous_Ruin_4947

Base is now 2x faster than Solana. Solana also chokes under volume, as seen with the Trump meme release. [https://www.youtube.com/watch?v=12G2nD821YE](https://www.youtube.com/watch?v=12G2nD821YE) Did you think this through? Solana's chain is over 300 TB in size. It becomes a nightmare to manage, and they will probably archive out older transactions to trim it down. Solana validators required 10G connections and 256 GB RAM. That by design makes in centralized. How many home validators can match these specs? [https://www.helius.dev/blog/how-to-set-up-a-solana-validator](https://www.helius.dev/blog/how-to-set-up-a-solana-validator) >Currently, the minimum recommendation *is* 12 cores/24 threads, 256GB RAM, 2x 1TB SSD disks (ideally w/ RAID0), and a *10GB* internet *connection*.

BstardSun

I was thinking a # SER8 Mini PC, AMD Ryzen 7 8745HS(4nm, 8C/16T) up to 4.9GHz, Mini Computer 24GB DDR5 RAM 8TB M.2 NVME & # WiFi6/BT5.2/2.5Gbps NORMAL Ryzen with upgraded storage, do you think this would be straight for3 to 4 years? Thank you.

bitusher

This has been discussed many times before , but I'll explain it again >Why isn't Bitcoin's block size increased? The limit was already increased in 2017 from 1 MB to 4 million units of weight or up to 3.7 MB blocks limit . Anyone who tells you otherwise is lying or ignorant . Some context for beginners to understand scaling capacity in Bitcoin: Satoshi Nakamoto originally set a 1MB blocksize limit on Bitcoin to prevent certain resource attacks and keep Bitcoin decentralized. He suggested some ways we can scale Bitcoin by introducing us to the idea of payment channels and ways to replace unconfirmed transactions (RBF) for a fee market before he disappeared. The first version of Bitcoin released had a version of replacing transactions as well https://github.com/trottier/original-bitcoin/blob/master/src/main.cpp#L434 https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2013-April/002417.html Over the years there has been many opinions and disputes as to how to scale Bitcoin from keeping the limit as is , to scaling mostly onchain with large blocks, to a multi-layered approach and every variation in between. In 2017 the Bitcoin community finally removed the 1MB after coming to consensus over a path forward. https://github.com/bitcoin/bitcoin/blob/master/src/consensus/consensus.h 1MB limit was removed and replaced with a larger limit of 4 million units of weight- https://www.reddit.com/r/BitcoinBeginners/comments/ghqcqn/bitcoin_bubble_or_revolution/fqa72j1/ Bitcoin is taking the approach of scaling with many solutions at once. With larger blocks, hard drive capacity is the least of our concerns due to – Archival full nodes contain the full blockchain and allow new nodes to bootstrap from them . Pruned nodes can get down to around ~5GB , and have all the same security and privacy benefits of archival nodes but need to initially download the whole blockchain for full validation before deleting it (It actually prunes as it validates) The primary resource concerns in order largest to smallest are: 1) UTXO bloat (increases CPU and more RAM costs) 2) Block propagation latency (causing centralization of mining) 3) Bandwidth costs 4) IBD (Initial Block Download ) Boostrapping new node costs 5) Blockchain storage (largely mitigated by pruning but some full archival nodes still need to exist in a decentralized manner) This means we need to scale conservatively and intelligently. We must scale with every means necessary. Onchain, decentralized payment channels , offchain private channels , optimizations like MAST and schnorr sig aggregation, and possibly sidechains/drivechains/statechains/ fedimint, cashu must be used. Raising the blockweight limits in the future is not completely opposed - https://bitcoin.org/en/bitcoin-core/capacity-increases https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html >"Further out, there are several proposals related to flex caps or incentive-aligned dynamic block size controls based on allowing miners to produce larger blocks at some cost." But raising the blocksize further than 4 million units also might not be needed as well depending how all the other solutions come to fruition.

pakovm

I have a MinisForum GK41 with 8GB RAM, an Celeron J4125 and I gave it an extra 1TB SSD, works great as a pruned node. If you don't want to spend too much money, that's a good place to start, but I would recommend something a little more beefy if you want to future proof, maybe the same model with but more RAM and SSD as you don't need a powerful processor to run Bitcoin, Lightning or anything Bitcoin related, just memory.

Quirky-Reveal-1669

If an old laptop already works, and you like tinkering yourself, and fiat money is no issue, you might even consider building the ultimate future-proof node. With at least 8TB dual SSDs, 128GB DDR5 RAM and a >2GHz base frequency processor. How fast would that finish the initial blockchain sync?

Halo22B

You didn't list your RAM or CPU and which is more pertinent than your connection capability

KryptoSC

My node is running on an older desktop that has 24GB of RAM with an i7 processor. I think that should be sufficient.

Charming-Designer944

How much RAM do your node have? The UTXO set has to fit in memory or the download will crawl. 32MB RAM shound work well. 16MB is not quite sufficient. It is not sch a big problem once it has catched up with the blockchain. If you want to run the nose on a smaller computer then maybe consider using a bigger computer for the initial download and then sync over the blockchain and chain state to the smaller computer. There is no trust issue in you syncronising the chain state between two computers you trust.

Helper_kev

Increase database cache – In bitcoin.conf, set dbcache=4000 (or higher if you have RAM to spare). Its more the 500gb now lol

izdigohkz

There are lots of RWAs worthy of attention in my opinion, with RAM particularly being one of my major watch at the moment, as the decentralised and low latency storage it provides gains even more on-chain recognition, warranting further demand, value, as well as indicating its long-term viability

Ok-Western-5799

RAM is one of my faves. Serves as a RWA on the EOS ecosystem.

izdigohkz

That's the best approach if you ask me. I'd rather opt for high-potential holds for the long term tbh, with the likes of RAM occupying top spots on my watch list, with on-chain utilities that'll guarantee their stay in the long run Do make your findings

izdigohkz

Overhype doesn't necessarily equate to utility, though eventually, assets with good enough use cases gain the recognition they deserve. It's more reason RWAs like RAM have stayed atop my watch list, especially considering RAM's importance to on-chain efficiency and consistency, owing to its low latency storage. Such innovations are bound to attract increased adoption, as well as recognition over time

gigabyteIO

You need a system with at least 16GB of RAM, 8 vCPU, a fast SSD (100 GB NVMe or equivalent).

Bits2LiveBy

Nice, downloading more RAM and inserting private keys now. Money here i come *rubs hads together*

Big-Finding2976

I don't understand why anyone would pick Kaspa over Radix XRD. With the Hyperscale upgrade it will be able to handle 1M+ TPS of actual swaps with atomic composability, running on sharded nodes with very low hardware requirements, like 4 cores 12GB RAM, 300GB storage, thus enabling true decentralisation, and the mobile wallet shows transactions manifests in plain English that guarantee you will receive what it says.

Charming-Designer944

The download will slow down progressively. The main performance issue in my experience is the UTXO set. It together with the block index cache and other RAM requirements eventually outgrows the RAM you have available on such small computers, limiting the speed of block transaction validation. 16GB is on the border today. Once the blockchain have synced up you can survive with much less RAM, down to a couple GB even, at the cost of a little more disk I/O and slightly slower block validation. Sure, you will not be top speed in accepting new blocks but for most uses some additional seconds for the validation of each new block every 10 minutes is not a problem. One simple option if you do not want to wait for days is to quickly sync up with the network is to prime the download by running the block download on a bigger computer of yours with plenty of RAM (more CPU also helps), then when synced up copy the downloaded blockchain + chainstate over to the smaller computer. But be warned that if you ever need to reindex the blockchain then you get back into the same performance issues from RAM shortage, but you can do the same trick then if needed. As long as you only use computers you trust there is no issue in moving or copying the downloaded & verified blockchain + chainstate to multiple nodes of yours.

ovr_the_cuckoos_nest

I've got a i3 Dell 3070 for my jellyfin/media server. It's got 20gb of RAM. So maybe just a 2tb SSD added via USB?

LuptinPitman

Blockchain is 724gb as of this moment. You will want to run an Electrum server and maybe a mempool instance but the space requirements are negligible to add those. I recently spun up a 2 vCPU 4GB RAM VM on my NAS and assigned 2TB of space. Installed umbrelOS via ISO (free) and it was ridiculously easy to get set up and running. Took me like 5 days to sync the entire blockchain but I think that had more to do with the virtualization. I've pulled the trigger on an actual Umbrel Home since it is just turnkey and now I'm comfortable with how to connect Sparrow wallet from my desktop and even Nunchuk and Bluewallet from my phone (while on my local wifi network). I plan to configure TOR connectivity so I can always use my node when interacting with air-gapped cold wallets on my phone and desktop though. Umbrel has the ability to run Plex and all sorts of other stuff non-bitcoin related but at 2TB that's gonna be tough. Worth it for me to just use it as a dedicated Bitcoin Node and Electrum server etc.

Pasukaru0

You are missing quite a few things: Backups are just data. Renting the storage for that is cheap. A couple of bucks per month. Renting an equivalent amount of compute and RAM is hundreds of bucks per month. The single core performance of this machine doesn't even compare to the vCPUs that you rent. Which is huge for the game servers. I also would not have a 10gbit connection to all the services I run. Latency is also a factor. Everything is basically instantaneous. Privacy. The memory and disk space of the running services is also not encrypted, so that basically invalidates all the privacy gains too as the VPS provider does have physical access to all of it. I don't want random employees of the VPS company to get access to the camera footage in my living room. Even if they promise to not do that. It's just a promise. I cannot validate that. The NAS is also a data and backup solution for my other devices. Copying a file there at 10gbit is amazing. The second level backup is then the scheduled tasks when it uploads it to b2 in the background, which doesn't matter how slow it is since, well, it's in the background. Home assistant is replacing Alexa/Google/Siri which is a lot more easily to handle when the devices are all in the same network. All of it continues should my internet connection die. Previously I couldn't turn on my lights because alexa just doesn't respond at all without internet. Granted, internet was only gone once, but still. Will probably happen again for a day or two when I switch providers in the future. And probably a few other factors that I did not think of myself off the top of my head right now.

Fun-Technology-1371

You can do this on a closed network, no internet. Stored in RAM only as well. I do this at work all the time. Still wouldn’t recommend this though. What can be laser engraved can be lost in a fire or also even scratched away. A 40W CO2 laser isnt removing material to physically “stamp” the seed phrase, just marking it. 40W Fiber lasers do physically remove metal though, that would definitely be permanent. Idk what OP is using though, or what metal for that matter.

Big-Finding2976

If you like good tech, you should check out Radix XRD too. It uses an asset-orientated programming language, Scrypto, which is more secure and saves developers a lot of time, it has linear scalability and composability without fragmentation, and they'll be running a public test soon, which will be verified by an independent third-party, proving that their Hyperscale upgrade will be able to process 1M+ TPS of true swaps, on a network which shards execution, consensus and state (SUI and Aptos only shard execution), with nodes running on modest hardware, i.e. 4 core, 8GB RAM. The wallet is also a breath of fresh air, with plain English transaction manifests which guarantee that you'll receive what it says, and MFA is coming with the next upgrade, which will provide extra security without the expense of buying hardware wallets, although it supports the Ledger Nano and Arculus wallets if you prefer to use one.

riscten

I'm with you and operate under the same assumptions. Technically, any hardware wallet will need to be updated at some point, and pretty much all of them require a USB connection or some sort of storage being connected in. So you have to balance risk between opening the door to an attack via USB, or operating knowing that some critical fixes are not applied to the firmware running on your device. One nice thing about Jade and Coldcard is that they can be operated in stateless mode, meaning that your private keys and mnemonics are never stored on the device and only ever live in RAM. The moment you turn the device off, it's all gone. You have to literally type in your seed again (or scan a [SeedQR](https://github.com/SeedSigner/seedsigner/blob/dev/docs/seed_qr/README.md)) to be able to sign transactions every time you start the device. Impractical if you spend frequently, but no big deal for long term cold storage. Stateless means that even if you lose the wallet, nobody can extract keys, because they only place they're stored is on your metal plates, recovery backup or brainwallet. There's the possibility that someone might extract the keys from RAM after shutdown due to data remanence, but that's an extremely sophisticated attack that's very unlikely. Stratospheric levels of paranoia at that point, but someone truly worried about this could easily modify Jade's code to implement some sort of RAM zero-fill they'd run before shutdown that would essentially eliminate that risk (honestly I'm not even sure that's not already being done when closing a session).

birl_ds

Bill Gates is said to have said, "640K ought to be enough for anybody" at a computer trade show in 1981. This quote was made in defense of the IBM PC's 640KB RAM limit. However, there is little evidence that Gates actually said this. 

bitsignal

Bismuth, because 1. **Lightweight Design**: Bismuth is designed to be resource-efficient, requiring neither powerful CPUs nor large amounts of RAM. This makes it accessible to a broader range of users, including those with limited hardware resources. 2. **Flexibility**: The platform offers a modular, Lego-like building block system, allowing developers to easily customize and assemble components to suit their specific needs. This flexibility fosters innovation and experimentation. 3. **Extensibility**: Bismuth supports private decentralized applications (dApps), enabling developers to create specialized, privacy-focused applications. This feature is particularly appealing for projects requiring confidentiality. 4. **Scalability**: Unlike many blockchain platforms, Bismuth’s dApps run only on nodes that have a vested interest in the application. This targeted approach reduces unnecessary network load and enhances scalability. 5. **Fair Distribution**: Bismuth was launched without an Initial Coin Offering (ICO) or premining, ensuring a fair and equitable distribution of tokens. This approach aligns with the decentralized ethos of blockchain technology. 6. **Original Codebase**: Bismuth was coded entirely from scratch, avoiding the pitfalls of being a Bitcoin or Ethereum clone. This originality allows for unique features and innovations that set it apart from other cryptocurrencies. 7. **Python Codebase**: The use of Python as the programming language makes Bismuth particularly appealing to developers, scholars, and academics. Python’s simplicity and widespread adoption lower the barrier to entry for those looking to contribute to or study the platform. 8. **Efficient Block Time**: With a main-chain block time of just 60 seconds, Bismuth ensures relatively fast transaction confirmations, balancing speed and security. 9. **Dynamic Proof-of-Work Difficulty**: Bismuth’s Proof-of-Work difficulty retargets every block, ensuring consistent block times and maintaining network stability even as mining power fluctuates.

castorfromtheva

I have different node setups running. One of them is Umbrel. Running it for around three years. It's pretty stable even when running software like Electrum Server, Lightning Node an own mempool.space instance, Thunderhub and other things on top of Bitcoin core. It's very easy to setup and really stable, but in terms of configurability not as open as for example RaspiBlitz or manually setting everything oneself. But it's really easy to use and also very good as a fallback option in case other fullnode servers have issues. One thing I'd recommend though is not going with a Raspi4. Either go with a Raspi5 with 8 gigs of RAM.... Or still better decide for a normal x86 architecture. For example Lenovo tiny or Dell optiplex with at least a Gen. 6 CPU like I3-6100T or above. These miniPCs will be around 100 bucks if you get a used one and another 100 bucks for a 2Tbyte which is a great, futureproof setup especially when you decide for 16 gigs of RAM (while depending on how much additional bitcoin related sofware you're gonna run on top, 8 gigs would likely do the trick as well and you can upgrade later). Energy-wise you'll probably pay around 1 to 2 bucks per month when having it run 24/7/365. You can connect a lot of different wallets to your node, even mobile software wallets which in case of transactions on the go will then use your own fullnodes dataset run @yourhome. It's a great feeling to have and in the first place actually *use* an own fullnode as it's honestly the only true way to be sovereign participant within the bitcoin network. If you have further questions, also during setup or running it, feel free to head back. Maybe I can help.

coinfeeds-bot

tldr; Jambo is a $99 smartphone and mobile network built on the Solana blockchain, featuring 12GB RAM, 128GB storage, and an inbuilt AI chatbot. It includes a Solana wallet, app explorer, and Web3 features, but only supports 4G networks. Jambo is marketed as the largest on-chain mobile network, active in 128 countries with nearly 1 million wallet addresses. Despite its innovative features, users are advised to proceed with caution due to its new status and potential security risks. The Jambo Token, issued on Solana, is also part of the ecosystem. *This summary is auto generated by a bot and not meant to replace reading the original article. As always, DYOR.

transatoshi_mw

An idiot? Yeah I guess. You need 16 vCPUs 32GB RAM and 3TB SSD space. It's not like you can run one with the spare resources one might have usually. Like shit dude, take off your blinders.

--mrperx--

"Well, does gold actually?" The contacts on the RAM chip in my PCs is made of gold. Gold, silver etc has the most intrinsic value out of all assets, criticizing that is pretty dumb. It's used in manufacturing. Commodities are the most useful, but having them the most expensive would be problematic. So commodities are most intrinsic value but best if price stays low fiat cash has low intrinsic value per unit and should stay like that so people spend crypto and stocks have no physical use-case but can absorb value. their intrinsic value is that they store value

Berganzio

Give more RAM.

Ok-Western-5799

RAM comes first in my portfolio when it comes to DePINS. It acts as the decentralized physical storage for projects building on EOS.

izdigohkz

RAM combines both the DePIN and RWA narrative and I consider it a solid coin to hodl.

CoolWorldliness4664

Indeed. I remember spending $200 for 4 MB of RAM, $300 for a CD ROM drive, $2000 for a 486 Desktop. Inflation is good for bankers, not so good for everyone else.

Full_Possibility7983

nah, no effect. It's just slow because of the CPU and limited RAM. It can take anywhere between 2 to 4 weeks, don't worry about the number of peers, your node connects to no more than those that can feed its processing, the bottleneck is definitely on your hardware.

Intrepid-Phrase-2660

dont talk to this scammer, he's just pumping for info [r/django](https://www.reddit.com/r/django/)•  # [Hey guys I wanted to know what would be an operational cost to maintain a full website](https://www.reddit.com/r/django/comments/1h8ikkr/hey_guys_i_wanted_to_know_what_would_be_an/) [SocialKritik](https://www.reddit.com/user/SocialKritik/) commented 3 days ago  I'll share from my experience. A few months ago I managed a CRM for a client with 70 Employees and managing over 1500 clients. The backend was Django, Postgres, Redis and Celery with some agents running locally on-prem servers. Django, Celery and Redis were running as docker containers on ServerC12 (just a random name to help with explaining), PostgreSQL qas running on the docker host, ServerC12. ServerC12 had 4GB or RAM, 2vCPUS, 80GB disk. The frontend was/is a mobile app, so no server there, but they all share a CI server, ServerC15 to automate the build, test and deploy. So there I have two servers, each costing me $24 a month. I decided to go with AWS lightsail because they don't have hidden costs and relatively cheaper to DO Droplets, EC2,...I didn't compare with Google Cloud or Azure, but I have a feeling those would cost more. Upvote11Downvote[Replyreply](https://www.reddit.com/r/django/comments/1h8ikkr/comment/m0tasqa/)ShareShare

jetylee

I use a ledger for what I consider warm and “mostly very secure storage” My real cold storage is core wallets created in RAM Drive VMs then printed out with public addresses added as “watch only” in software like “trust wallet” That way I can send what I want to them without ever touching them. The VM and the RAM drive is then destroyed. At no point in time did the VM ever go online.

Adept_Swimming_3116

Yes, I am talking about the order of magnitude ! If each instance of this program uses 5MB (5*10^6B), it would require 5*10^6*3000^12 Bytes ... Which is a lot ! As for storage capacity, that is not relevant as it should be using memory (RAM) with higher access speed (what costs a lot is access to storage as it cannot be used concurrently)

Ok-Western-5799

Check out RAM on EOS. It’s already seen over 50x gains this year, and the upside is still massive. The token’s utility within the EOS ecosystem is strong, and it could easily keep pushing higher.

Delicious-Use-8789

**ChatGPT:** Running a Bitcoin node is a great way to help secure the Bitcoin network and verify your own transactions. Here's a simple, beginner-friendly guide: 1. Understand What a Bitcoin Node Is A Bitcoin node is a computer that runs the Bitcoin software (called Bitcoin Core) and stores a full copy of the blockchain. This allows the node to independently verify all Bitcoin transactions and blocks. 2. What You Need You mentioned you want to run your node on a 2 TB device, which is a good size because the blockchain is over 500 GB as of 2024 and growing. Below are the hardware options: Laptop: This is a good option if your laptop has sufficient storage (2 TB) and can be kept running 24/7. Bitcoin Core does require a stable internet connection and reasonable CPU power, but not too much. External Hard Drive (HDD/SSD): You can also use an external drive (2 TB or more) to store the blockchain, especially if your laptop doesn’t have enough internal space. An SSD is faster but more expensive than an HDD. For a Bitcoin node, speed isn’t critical, so an HDD should work fine. Raspberry Pi 4 (with 4 GB or 8 GB RAM): A Raspberry Pi is a low-cost, energy-efficient option, but it requires a bit more setup. If you go this route, you'll need an external 2 TB hard drive or SSD connected to the Pi to store the blockchain. For simplicity, starting with a laptop + external HDD would be the easiest route for someone new to tech. 3. Hardware You’ll Need Here’s a list of hardware pieces you’ll need if using a laptop: Laptop (with at least 4 GB of RAM and a good processor like an Intel i5 or higher) External hard drive (HDD or SSD) with at least 2 TB of storage. Internet connection (a broadband connection with no data caps is ideal). Power supply for your laptop or Raspberry Pi if using one. If you go with a Raspberry Pi: Raspberry Pi 4 (4 GB or 8 GB RAM) MicroSD card (16 GB or more) to load the operating system (use a high-quality card). Case and power supply for the Raspberry Pi. External 2 TB hard drive (USB 3.0 connection is best for fast data transfer). 4. Software Setup Once you have your hardware, follow these steps: Option 1: Using Your Laptop 1. Download Bitcoin Core: Visit the official Bitcoin Core website: https://bitcoincore.org and download the software for your operating system (Windows, macOS, or Linux). 2. Install Bitcoin Core: Install it like any regular program. During setup, you’ll be asked where you want to store the blockchain. Choose your external 2 TB drive (or internal storage if it has enough space). 3. Configure Your Node: After installation, Bitcoin Core will begin syncing the blockchain. This can take several days (sometimes even a week) to fully download the blockchain. Just leave it running in the background. Your laptop must be powered on and connected to the internet during this process. 4. Connection Setup: Make sure you have a stable internet connection (preferably without data caps) because syncing the blockchain will use significant bandwidth. To optimize your node, allow incoming connections by opening port 8333 on your router. This will help your node communicate with others more effectively (you can Google "open port 8333 on [your router's model]" for instructions). Option 2: Using a Raspberry Pi 1. Install Operating System: Download Raspberry Pi OS and use a program like Balena Etcher to flash the OS onto the MicroSD card. 2. Download and Install Bitcoin Core: Once the Raspberry Pi is set up, connect it to your external hard drive. Then, follow the instructions to install Bitcoin Core on your Raspberry Pi: sudo apt update sudo apt install bitcoind After installation, point Bitcoin Core to store the blockchain on your external 2 TB drive. 3. Configure the Node: You’ll also need to configure Bitcoin Core on the Raspberry Pi to allow incoming connections. Edit the configuration file (bitcoin.conf) to enable port 8333. Leave the Raspberry Pi running 24/7 to sync the blockchain and process transactions. 5. Running the Node Once Bitcoin Core is installed and synced: You’ll have a fully functioning Bitcoin node. You can use your node to verify your own Bitcoin transactions, improve privacy, and contribute to the network's security. 6. Keeping It Running After initial setup, make sure your node stays connected to the internet and powered on. It will automatically stay in sync

castorfromtheva

Get a used Lenovo Tyny or Dell Optiplex, Ultra Small Form Factor, with at least a 6100t or higher, doesn't matter if it's just a i3 or even an i5. i7 or i9 is unnecessary. The higher the generation the more energy-efficient your machine will be. Don't choose anything below generation cpu 6! Go with a 2Tbyte SSD and at least 8 GByte of RAM. Go with 16 if you plan to run further software (like Lightning node, Electrum Server, BTCPayServer, an own mempool.space server, LNbits, etc) on top. The machine will be less than 200 bucks and around 1 to 2 bucks of energy per month. It will run smooth and stable like a charm.

izdigohkz

RWA are good. ONDO, OM, and RAM. RAM is quite undervalued unlike the big guys ONDO. This can run 40x more.

user_name_checks_out

> If all electricity disappears for a year, and then a year later civilization starts to bring the power grid back online, would the bitcoin blockchain still be intact? Sadly, no. Bitcoin is only stored in RAM, it is never, ever written to disk. (This was one of Satoshi Nakamoto's dying wishes). Therefore, at least one bitcoin computer must be kept running at all times - kind of like the Olympic torch. We have a contingency plan in case, as you say, "all electricity disappears for a year". We are going to take turns running on a treadmill to power a generator to keep the last bitcoin computer running. You are asking great questions, you are clearly very smart.

JuHustle

I do know what a RAM drive is lol I been working on computers my whole life. Everything you both said I understood perfectly. Just wanted peoples opinions.

jetylee

So your friend effed up? I did explain to him that he would only import when he was ready to move it. I don’t believe there’s anything wrong with “exposing your stack” via one public address. I have some from 2011. They’re untouchable. I invite you to figure out which ones are mine and if you do, best of luck obtaining them. But sure. Firmware and a microchip is far better than steel and firearms. You kids are so short minded. Ever make a Bluetooth light bulb explode remotely? Just cuz the guy is new to crypto doesn’t mean he doesn’t know what a RAM drive is. Your method is more risky. Period. I sincerely hope for your own sake you and I have different quantities of coins at risk.

jetylee

if it has a micro chip in it, its not secure. create a wallet offline in a VM that resides in a RAM drive on a machine NOT connected to the internet. Write down your seed words, laminate the paper, put it in a safe. Go to Walmart and buy the old Vietnam War Dog Tags that we put on Dogs collars. Stampe ONE seed word on each tag, put on a key ring in an order you'll remember. (not even consecutive if you want to go full paranoia). Place steel tags in another safe. This is the way.

TemporaryCitron9271

Hi, I'm not a team member so if you need real and verified answer you can ask this question on Mina official discord channel then some devs or core member will provide you good answer. I can provide you with a link to some sources - [22kB-Sized Blockchain -- A Technical Reference | Mina Protocol](https://minaprotocol.com/blog/22kb-sized-blockchain-a-technical-reference) and also answer like that: You don't need an archive node to check your assets. A regular Mina node only requires about 11kB to verify the current state, which includes: * Protocol state (822 bytes) * Account data (181 bytes) * Merkle path to account (741 bytes) * Verification key (2039 bytes) The system works by having archive nodes store the complete historical data, while regular nodes remain lightweight by only maintaining the current state proof. When you need to check your assets, your node can verify the current state without needing the entire blockchain history. This unique architecture allows Mina to maintain its succinct nature while ensuring all historical data is still preserved and accessible when needed. And also docks source for archive node - [Archive Nodes Getting Started | Mina Documentation](https://docs.minaprotocol.com/node-operators/archive-node/getting-started) # Archive Node Requirements * 8-core processor * 32 GB RAM * Minimum 64 GB of free storage space * PostgreSQL database for storing historical blockchain data

izdigohkz

There are coins I will hold till May next year The likes of EOS, RAM, METIS and ONDO.

castorfromtheva

Well, then all you need is a bitcoin core fullnode and potentially an Electrum server. Both, Umbrel and start9 are really easy to install and setup. All you need is a x86 mini pc, for example lenovo tiny or Dell optiplex mini (can easily be used/refurbished but don't go with any processer older than an Intel 6. generation), go with 8 gigs of RAM and a 2 Tbyte SSD to be futureproof. Get a network cable (I wouldn't go with wifi, cable is more stable). And last not least you need an usb drive where you burn either Umbrel or Start9 onto via Balena Etcher. With this stick you install the OS on the machine. After that any of them is reachable via WEB UI and you can install Bitcoin Core and Electrum server before connecting you desired coordinator app to it. The exact installation process is described on either of where websites. Both setups are quite similar and easy to do.

Efficient_Culture569

If you define your basket as being CPUs, RAM and Mobile phones, we'll have a negative 10% CPI. The basket of goods for CPI can change. Everyone's CPI is different depending on what you purchase on a monthly basis.

hutulci

If you use another bootable linux OS, you will need to put Electrum on it, unless it comes preinstalled. Even if your chosen OS does come with Electrum, you will likely want to have your wallet information readily available, to avoid typing it in every single time, so either you put it in an encrypted partition on the same or in another USB, or you have to make your OS persistent. You will also need persistence to prevent your OS from wanting to connect to the internet using WiFi every single time you start it (and if you forget about this, it might connect on a public network nearby). But then, this persistence comes at the cost of your OS being no longer immutable and, thus, susceptible to infection. Tails comes with all this out of the box, done right. You need to enable the internet connection at the start if you want to use it, so it's impossible to connect accidentally to networks. It is amnesic by design, and thus it is also resistant to (most) malware, and comes with its own nice GUI to manage its encrypted storage, meaning that you can have the Electrum AppImage and your wallet file readily at hand. In addition to this Tails doesn't detect and thus write to any disk, but it operates fully in RAM and bleaches it once unplugged. It comes with some bare minimum vetted software, which reduces the surface of attack. In short, if you want to use this setup and do it right, it's way more convoluted to use any other Linux OSes than Tails, which, as unfamiliar as it might look, is pretty much just Debian. But I do second the suggestion to use a (fully open-source and well reputed) hardware wallet, especially for beginners.

neo69654

2048 is very low, bump it up based on the RAM you have dude. You can also try to block incoming connections while syncing.

ancihu

Thanks for the suggestions! Totally beginner here. I'm using a 64G RAM but not idea why cannot fully utilize it. Things changed after I set dbcache=2048. It's been speeding up and should be done within a week, which is acceptable for me. Will surely make a backup once done. Thanks!

nou_spiro

Do you run bitcoin core and have 8GB RAM? Then add this line to bitcoin.conf dbcache=6000

Ok_Passage_4185

Not crazy. But you might be a bit crazy to try to run a full node on such limited hardware. The slowdown over the days might be related to various system caches filling up. Extra RAM might help there (check the utilization, but I would recommend no less than 4GiB on an otherwise idle system). There are also a couple tweaks you might want to lookup related to buffer sizes that can help quite a bit. I would definitely recommend something a bit beefier. Doesn't have to be crazy, but SSD over a decent bus (like not an external over USB 2.0) is critical for good operation. And RAM definitely helps. Your real problem is if anything goes down, your catch up can get you in a position where you can't use your node for some time. Definitely make a backup of the full chain once synced in case you need to recover from disaster.

bigbarryb

A node is pre-initialised with all of the historical transactions ever confirmed into the blockchain. When a new transaction arrives, a node will validate it the same way whether it is a payment to you or not. Bitcoin nodes may never be privy to which transactions are payments to you or not, they only serve to be an independent auditor of the blockchain. That said, using a Bitcoin node that isn't your own to validate a transaction gives a third party useful information, namely that a user using your IP address is interested in the particular transaction you are querying about. This can lead to compromise of your own personal security which is why we recommend you run your own node... this way you can rest assured that your node isn't collecting information about you and not using it against you. The way it validates a transaction is this: 1. Check all "inputs" aka coins that are being spent and validate that they are all marked as "unspent" which means it has not been spent in another transaction already in the blockchain. 2. Validate the sums, make sure the sum of outputs do not exceed the sum of the inputs. 3. Validate signatures, make sure that there are no missing signatures and that all signatures match up. 4. Once validated, a node may still choose to discard the transaction if it has limited resources such as RAM, it may decide to rank the transactions it is monitoring based on fees and keep the higher paying ones. The reason for this is that nodes need to optimise themselves for speed, and when a bitcoin block is mined, if there are transactions that they are not tracking in the block, they have to spend time validating it at the time of receipt, whereas if they had all or most of the transactions pre-validated, then they can just accept the block and wait for the next one. Therefore, nodes will take actions to improve the chances of the second outcome over the first, especially when there are limited resources to work with on the machine it is running on. Regarding "how does the node learn their public key beloning to the wallet address", every transaction has to have valid "witness data" (which we often refer to as signatures, but technically can include more information than just signatures). In that witness data is the public key of the address, and the signature. With this combined information, we can verify that the public key was indeed the key used to generate the address, and we can confirm that the signature is indeed valid and was created by whoever owns the private key of the address in question. There is no need to know WHO owns which address, only that there is a valid signature and that the signature was made from the appropriate private key. Cryptography allows us to validate all of this without ever seeing the private key which is why Bitcoin can work the way it does so securely.

crimson974

I have 16Gb of RAM. It’s an Asus Rog G751J. A bit old but still a decent machine

pwuille

My guess is that you're seeing the effect of the UTXO set growing. Bitcoin Core heavily caches UTXO data in RAM, but only up to the dbcache setting size (by default 450 MiB; I recommend you increase it to a few gigabytes if your system has enough memory). Over time, the size of the UTXO set has grown, so at some point during validation, the size will exceed what comfortably fits in ram, and at that point, blocks will start requiring thousands of database reads from disk, which are significantly slower.

castorfromtheva

Oh, interesting. Then indeed this doesn't seem to be the bottleneck. How much RAM is installed in your machine?

MinimalGravitas

You seem like a decent person, and I appreciate that you aren't being too shilly, but you've got some pretty big misunderstandings, presumably from being fed a certain narrative by the Hedera bubble. The biggest point is about adoption by enterprise and institutions, but lets look at some other things first. > the node part is easy and public nodes are on the road map. I'm not sure that's correct, in order to keep up with the network, full nodes have to be able to receive, check and send out all the transactions that are happening. It is very easy to do this if you only need a few data centres with ultra-high speed connections and hundreds of gigs of RAM, but very difficult to do so on regular consumer hardware and domestic internet. > Let’s face it, most other network’s ‘nodes’ are just hosted on AWS or another cloud service so they’re no more decentralised. Bitcoin may be the exception As well as Bitcoin, you can run full nodes for Ethereum, Monero, Litecoin, Polkadot, Cosmos, Cardano, Polygon, Gnosis... and many other chains, on hardware as cheap as a Raspberry Pi. https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html Personally I run nodes for Ethereum and Optimism (the L2 that I use the most) in my living room. I'm planning to spin up a Gnosis node too now that my main Visa card is a Gnosis Pay onchain wallet. > The consensus and transactions on Hedera is public record the same as any DLT. Not really, no. If I want to check my balance on Ethereum I can use my node to look onchain directly. If you want to check your balance you need to either trust a block explorer or a proxy that your wallet connects to. An example of why this matters was shown in March last year, when Hedera stopped accepting transactions from users and no one knew if the network was still running. In fact it was, but the governing council had shut down the proxies for regular users, meaning they couldn't connect to do anything as the token price dropped, while insiders were still able to use the network themselves. That situation can't occur on a chain where users have their own nodes. https://www.coindesk.com/business/2023/03/09/hedera-turns-off-services-after-network-irregularities/ > Just look at the sheer volume of development commits, much more than any other network… it’s all software after all and I’m looking to projects with the most development. Number of commits is a bad way to measure development because a commit can be anything, from a whole new piece of software, to the correction of a spelling mistake in a readme file. Electric Capital publish an annual report on developer activity in crypto that is widely regarded as the most robust analysis available, the last one looked at 485 million code commits across 818k open-source repositories and worked out which were meaningful contributions. Their report is free to read and very thorough, one section I think is very telling looks at the first place code is found, so lets you see where novel is being written, rather than just copy-pasted from elsewhere: https://www.developerreport.com/developer-report?s=71-of-contract-code-is They also publish updated data roughly every 6 months, showing where the most developers are. You have to scroll quite far down to find Hedera... https://www.developerreport.com/ > As I say I think it’s running ahead of what enterprise can currently drag its lumbering ass to leverage but when it happens I can’t see them building anything on anything else. Do you remember the hype in the Hedera community about Blackrock maybe deploying there? Well where did they actually end up deploying? https://etherscan.io/token/0x7712c34205737192402172409a8f7ccef8aa2aec And they are just one example, since then we've also seen loads more huge companies onboard to Ethereum, not through some sweetheart deals or subsidized partnerships, they just build and deploy stuff without needing to be bribed or incentivized to do so... **Wisdom Tree** ($100 billion asset management company): https://www.cryptopolitan.com/wisdomtree-launches-platform-tokenize-rwas/ **Visa** (You know who they are): https://investor.visa.com/news/news-details/2024/Visa-Introduces-the-Visa-Tokenized-Asset-Platform/default.aspx Visa have also been working on an Ethereum upgrade for account abstraction: https://usa.visa.com/solutions/crypto/rethink-digital-transactions-with-account-abstraction.html **Paypal**: https://www.coindesk.com/business/2023/08/07/paypal-to-issue-dollar-pegged-crypto-stablecoin-bloomberg/ Paypal and Venmo have also recently integrated with Ethereum Name Service: https://decrypt.co/248739/paypal-and-venmo-users-can-now-send-crypto-payment-with-ens-names **Sony**: https://dailycoin.com/sonys-ethereum-l2-testnet-goes-live-builders-enticed-with-incubator/ We could go on, but you get the idea. I'm really not trying to be unkind, I just think that your sources of information regarding the crypto ecosystem seem a bit biased, which isn't a great start for investing.

izdigohkz

You can put that money into some alts to like EOS and RAM. They have better chances of giving you over 50x in the long run. BTC might not 2x from here in the full bull.

Similar_Scar7089

The OS runs in RAM and nothing is saved when powered off. I suppose if there is an option to keep the phrase on the device there could be an issue

TaGoItFr

I think rpi zero... Yeah it have numerous attack vectors, but if u use the software seedsigner (it runs on RAM), and if you know what you are doing (if you check the transaction outputs etc.) you are as safe as trezor, keystone pro or ellipal titan... Maxbe not as safe as ngrave zero (but they arent open source so its maybe not as safe as they say)

izdigohkz

That's so much money flowing into RWA. Now what's the best crypto to hold in the RWA category? RAM and ONDO are on the top of my list. RAM is used for storage by exSat and other projects.

izdigohkz

We are in the bull run. Lot of memes flying and now it's time for alts. My best bet is staking some high utility memes like RAM. exSat and other projects are accumulating it for storage purpose. It's going to fly high.

pakovm

I have 1TB, 8GB RAM and a Pentium N400 for my Bitcoin node, it can run Bitcoin Core, Electrs, [Mempoool.space](http://Mempoool.space) (I think this explorer is a lot better than Blockstream's), an LND node and more, so yeah, that should be enough.

Ok-Employ-1029

Yes, I was going to say the same. I don't know what size Eth's full chain history is, but the 2tb is for validating current blocks, the technicalities of which I don't understand. So it appears that Solana needs 256GB RAM (or perhaps more now?) to hold the entire global state in RAM, is that correct? The thing which I don't understand is the extent to which historic data is relevant and important for security. For instance, a bitcoin node will replay and verify every transaction. If Solana can really reach something like a millions tps, the chain will grow so fast... what practical consequences will follow?

CrazyAppel

It's not centralized and the whole reason Solana is scam-ridden is because it's not centralized lmao. The argument for it being centralized is that it's expensive to run a validator node (you need 256gigs of RAM and at least a Cooperlake Xeon CPU), but a lot of people understand things backwards. Solana uses PoH, mainly built by Anatoly, his whole idea was to have the lowest block times and the fastest transaction speeds, resulting in high node costs. By abusing these metrics, you can build stuff like bundlers that can buy your own coin from a bunch of different wallets at the same time when your coin is created. It tricks newbies into thinking your coin is active, you can easily sell all supply after with a single press of a button. Creating a rugpull coin costs you like 100 bucks max and a few hours of your time, THAT is why this chain is so scam ridden. The product is actually good though, PoH is a handcrafted and masterfully coded piece of artwork by mostly one person. All good things end up being abused hardcore

---Q_Q---

Only way they'd do this is if the device still had the seed stored in RAM for some reason or if the seedphrase itself was stored in a file/password manager they managed to gain access to.

Aussiehash

Well if you are happy to pay for the "best" take a look at Start9 https://store.start9.com/ On the other hand I am perfectly happy with my Pi4b 8GB (or you could use Pi5 with 8GB RAM) and USB 3.2 SSD/NVME. 1TB is barely enough now for a full node with additional Electrs/Fulcrum database, so I would suggest either 1.5TB or 2TB SSD/NVME storage

Trilzerobyte

Do you just want to run Bitcoin Core, or also Lightning, Electrum server, a web UI, block explorer?  If just Bitcoin Core then you may get away with 2GB RAM. But what CPU do you have? Do you want to verify all the blocks from the genesis? Many NASes are low powered ARM servers. If it's equivalent to a RPi 3, it'll take nearly a month to sync the blockchain. If you don't need to verify old blocks, then you can copy the block data from another machine you trust. Once caught up to latest block, you only need to verify one block per 10 minutes on average so it's easier to stay caught up than to initially sync.

na3than

There are two sides to "safety" when it comes to storing Bitcoin seeds/keys: 1. The likelihood that someone you don't want to have access to your seed/key will gain access to your seed/key 2. The likelihood that someone you want to have access to your seed/key--e.g. YOU--will lose access to your seed/key Storing your seed/key in a Minecraft world MIGHT have low likelihood that someone else, including malware scanning your computer or your network, will discover it. But you'd be making a lot of assumptions about how the world is physically stored on disk, how it's stored in RAM, etc. Don't equate "I don't know how objects in Minecraft worlds are stored / most people don't know how they're stored" with "objects in Minecraft worlds are undiscoverable outside the world". Storing your seed/key in a Minecraft world has a moderate to high likelihood that YOU will lose access to it. Minecraft software changes frequently, and there's no guarantee that, ten years from now, you'll be able to find software that can render the world you made in 2023 exactly as you left it.

coinfeeds-bot

tldr; Solana Mobile is launching a new crypto smartphone, the Seeker, following the Saga's initial struggles. Unveiled at Token2049 in Singapore, the Seeker is set for a mid-2025 release with 140,000 pre-orders. It features a lower price point, starting at $450, and includes 128GB storage, 8GB RAM, and upgraded cameras. The Seeker aims to attract crypto users with proprietary custody solutions and dapp incentives. It also offers exclusive benefits like a Helium Mobile subscription and game assets, positioning itself as a rewards magnet for the crypto community. *This summary is auto generated by a bot and not meant to replace reading the original article. As always, DYOR.

jetylee

I create VMs on a RAM Drive with a host machine offline and no network on the VM. Generate the wallets and power off the VM, remove the RAM drive and "none of this ever happened."

Archophob

a system-on-chip does have RAM, it's just not on DIMMs.

SmoothGoing

Wallets will have RAM to store things while in use. Makes no difference. Faraday cage doesn't matter. No wallet will be "pulling seeds wirelessly."

Ctrl_Fr34k

So if they are a standalone device with an OS that doesn't need to be connected to a main computer to work it doesn't need RAM?

Zensiert_Gamer

Its a small Computer basically all will use some RAM

Ok-Western-5799

RAM is definitely one to keep an eye on. With the EOS spring fork dropping soon, the demand for RAM is about to pop off, and a 100x surge could be just around the corner as more projects start building on EOS.

izdigohkz

RWA still a good category with lot of money flowing in there. ONDO, RAM and OM are a good bet. A lot of projects like exSat are utilizing RAM for storage which eventually creates demand.

MangaKhan

Google DBCACHE setting for Bitcoin core. It uses more RAM and relieves HDD access. Can be set in UI as well as via config file or at startup time.

Temporary_Pen_1692

But both of my CPU and RAM are at low position..... I think software doesn't really maximally utilize the resources

ta_pi

One variable I found important in downloading the full blockchain was RAM. Not CPU. Not bandwidth. If you don't have enough RAM you'll be swapping to disk so much it will seem like the bandwidth is the bottleneck. Check what your machine is doing, mine with 4Gb initially was working the HDD _hard_.

jpowsecretstack

I'm glad you mention that. Tails OS runs entirely in the computer's RAM and does not rely on the hard drive, meaning it operates independently of the underlying hardware. This means that any tampering or malware present on the computer, such as on the hard drive or firmware, is bypassed when using Tails! Since no part of the OS interacts with the potentially compromised hardware, it's considered ultra secure for tasks like manipulating Bitcoin seeds, protecting against pre-existing hardware-level threats. Electrum comes pre-installed with Tails so that you do not need to connect to the internet when creating your seed. It's basically more secure than an offline signing device or seed generator like Ledger, Trezor, etc as you remove the hardware tampering risk. I hope that helps.

Schmiegefp

In the RWA narrative, I'm replacing RIO with RAM, a RWA on EOS.

TaGoItFr

Yeah, because seed signer doent need a secure element. Seedsigner doent save data to the device. Its operations work on RAM memory. So you just need to generate a xpub and store just this save. The seedsigner dont save your seedpgrase so its the savest method...

Ok-Western-5799

DePINs are slowly but surely taking center stage. One standout project is RAM, the physical memory of EOS. With rising adoption and more projects building on EOS, RAM is becoming a highly sought-after token in the ecosystem

SmoothGoing

Did you try to download more RAM to your phone? Coldcard is a hardware wallet.

fudelnotze

Which model you buyed at a cryptoexchange? RAM? SRT?

rdevaux

Check Nano/Banano. Feeless and nearly instant transactions. Node is set up within a few minutes, needs a few GB storage (depends on the size of the Blockchain) and 2-4GB RAM. Best served as a docker container.

FunWithSkooma

keep it in RAM memory? Wat?

Thin_Caramel_3483

Indeed, the best way is to download the spreadsheet and use it in an always-offline computer. And there is no need to save the file with your seeds typed, keep it just in RAM memory.

ske66

This is a version of JIT memory management. RAM is volatile and more expensive than near line or cold storage, so if you can process data from cold storage without needing to load it into RAM, that means you have made a major leap in JIT processing

Tasty_Action5073

Swapfiles…damn this is so old I hope I remember correctly what I’m about to say… is what we used to do as virtual RAM. Your computer will dedicate an area that is quicker to access than fetching files from the hard drive to use as RAM. So it’s just extended RAM really. Now how you found it and why you think it has Bitcoin I don’t know. But I reaaaally doubt your Bitcoin wallet was stored in RAM, and in this situation in the Swapfile.

MiguelLancaster

no idea what that is, old bitcoin files are usually wallet.dat a swap file is usually temporary storage between RAM and your disk drive

CoolCatforCrypto

Didn't gates say in the late 90s no one could possibly need more than 64k of RAM?

LegendaryJohnny

He is tech illiterate. He is mastermind in dictatorship, public speech, hive mind manipulation, decent in politics, great in making people disappear, but I believe he knows shit about what is 16 GB RAM and stuff like that.