Just a quick update and feel free to lock.
SD card is working flawlessly. No issues at all. I may suffer the slow read and write speed for a full node but may just wait when I find a larger card that will give plenty of room for growth. Thank you to everyone for the help, troubleshooting, and idea bouncing.
Topic: Suggested Bitcoin Core Pruned Node Size (Read 442 times)
I installed everything on the card, application and all. Would just be more portability, something smaller than the tablet. Then I've never used a windows phone. Still researching to see what is out there and how they work.
In all pretty happy with the node on the tablet so far. Just cant browse the web as quickly when it starts to sync in the am after being off line.
In all pretty happy with the node on the tablet so far. Just cant browse the web as quickly when it starts to sync in the am after being off line.
I don't have a windows phone but wonder if I can swap the card out between devices?
What do you have stored on your SD card ?
Just the blockchain + chainstate files or all files which are necessary to run the node ?
With blockchain and chainstate files, you should be able to simply swap the card into multiple devices to have your blockchain available.
If you however intend to run your node on multiple operating systems without core being installed there, you'd need to have all necessary binaries stored there too.
Generally it is definitely possible to swap the card between multiple devices. But what would be a windows phone for ?
The disc is practically idle now when minimized to taskbar on the winX tablet i'm using. Transactions in and out working fine, I suppose if you have a wallet that connects to a node already it maybe redundant.
Since my goal was to have a full node w/incoming traffic my shortsightedness let me down but still may suffer another ul period to at least sync the full chain.
I don't have a windows phone but wonder if I can swap the card out between devices? Maybe give it try after some research, or experience of others replying.
Since my goal was to have a full node w/incoming traffic my shortsightedness let me down but still may suffer another ul period to at least sync the full chain.
I don't have a windows phone but wonder if I can swap the card out between devices? Maybe give it try after some research, or experience of others replying.
I had forgotten about the port forwarding. So being mobile I may have to let that go as I wont be able to control other networks or hotspots, etc.
So pruned I can have incoming then? It depends on the network I suppose being mobile (to have ports forwarded). At least a couple networks i traveled to today do but still only 8 out.
Whether you are running a pruned node or not has no influence on the incoming connections.
If the network you are visiting with your full node, doesn't have port 8333 forwarded to your machine, you can not accept incoming connections.
You'll need either to contact the administrator to give you a static IP and set port forwarding for this IP, or live without incoming connections.
Note that your node is fully functional, you just don't support the network without incoming connections.
So pruned I can have incoming then? It depends on the network I suppose being mobile (to have ports forwarded). At least a couple networks i traveled to today do but still only 8 out.
I did select pruned as Core website said it needed 220gb from what I recall and would be about 10gb added monthly?
220 gb sounds a bit too much. Blockchain size is currently at ~184 GB and core shouldn't need more than a few GB.
Also 10 GB quarterly sounds more appropriate than monthly.
One thing I miss is incoming connections of a full node. Unless I'm missing something?
You need to enable incoming connections in the settings first.
Also, did you set port forwarding of port 8333 on your router ?
Everything works well. Read/write to disk is about 2 mb/s "spikes" three or four times a minute, or so. The initial strain is obviously the ul of history for two days. One thing I miss is incoming connections of a full node. Unless I'm missing something?
I'll try to load everything including application onto it and will prune at 230 gb.
Fortunately you won't need pruning. The current size of the blockchain is at about 184 GB.
You might also want to backup the chainstate folder (on the same sd card, in a different directory).
This will allow you to get to a working state if your current chainstate will get corrupted.
Will update as it goes.
Feel free to update regarding stability and convenience.
We'll also gladly assist in any occurring problems.
We'll just a couple more hours till done syncing. I did select pruned as Core website said it needed 220gb from what I recall and would be about 10gb added monthly?
I'll try and get the back up as suggested. Currently the "disk" is at 90-100% usage while UL and get's average of 7MB/s read/write. Not to bad. Might UL faster with pruning I imagine.
I'll try to load everything including application onto it and will prune at 230 gb.
Fortunately you won't need pruning. The current size of the blockchain is at about 184 GB.
You might also want to backup the chainstate folder (on the same sd card, in a different directory).
This will allow you to get to a working state if your current chainstate will get corrupted.
Will update as it goes.
Feel free to update regarding stability and convenience.
We'll also gladly assist in any occurring problems.
The mobile device I can't update the main drive with more storage but can add the microSD storage. This is a high grade microSD but still more of an experiment, yes.
Looks like 99GB is max for a pruned node. UL speed has fluctuated when using the device. 63% progress into May 2017 blocks, 15 hrs remaining as of now.
Looks like 99GB is max for a pruned node. UL speed has fluctuated when using the device. 63% progress into May 2017 blocks, 15 hrs remaining as of now.
The flash memory in microSD cards isn't designed to sustain so many write operations. It'll wear out quickly. You're better of buying an SSD and using that.
It's always interested me to know how well a mobile device handles the satoshi bitcoin client, it's obviously always been possible (and now that people are using Arm A53 class SoC machines like Raspis for full nodes + lightning, it's obviously practical).
I'd recommend supplying the -blocksonly parameter to bitcoind as well as -prune (assuming the app lets you do that easily enough). Your data plan will get crushed if you re-sync the blockchain over your cell connection too regularly, relaying transactions and all the other network messages will make that something like twice as data-hungry.
You want this in your image tags to change image size:
[img height=numberOfPixels][/img]
I'd recommend supplying the -blocksonly parameter to bitcoind as well as -prune (assuming the app lets you do that easily enough). Your data plan will get crushed if you re-sync the blockchain over your cell connection too regularly, relaying transactions and all the other network messages will make that something like twice as data-hungry.
You want this in your image tags to change image size:
[img height=numberOfPixels][/img]
Not sure how to resize but should have posted without screen capture.
Half hour in mobile mesh.
We'll I'm going to proceed with a "mobile" node with this mircoSD card I paid for myself. Not by mfb or given by PNY. I'll try to load everything including application onto it and will prune at 230 gb. Will update as it goes. Sorry for refection.
Then there shouldn't be any problem, even though i doubt microSD is durable if you plan to run node 24/7.
Yeah, i also believe this won't work out well. SD cards (or external HD's) aren't very good at guaranteeing a continuous connection.
But without pruning and some rescans, it theoretically should work somewhat good.
You should look random read/write speed and make sure at least it's as fast as HDD's random read/write speed.
SD cards use flash memory (same as USB sticks and SSD's).
So a SD card should be at least as fast as a HDD by default, even cheap ones (but their durability is way lower than from a quality SD card).
Well it would just be for the node nothing else. 100 mb/s read is the spec I'm looking at, doesn't say what the write is though.
If you have 256gb, you don't need any pruning at all. The best in this case would be to store the complete blockchain.
Also, note that this might not work out as you are expecting. Core needs a continuous connection to the memory. This might fail with a SD card.
In this case some data is going to be corrupted, requiring a resync.
But in theory.. yes, this would be a 'light wallet' (in terms of portability) using a full node.
Also, note that this might not work out as you are expecting. Core needs a continuous connection to the memory. This might fail with a SD card.
In this case some data is going to be corrupted, requiring a resync.
But in theory.. yes, this would be a 'light wallet' (in terms of portability) using a full node.
Jump to: