Topic: Official [ROKOS Core] Bitcoin Full node Raspberry Pi P64 IoT Feedback/Discussion - page 5. (Read 19378 times)

ok when i boot my pi (no monitor) and then i vnc into it, i get a terrible resolution how do i get it to something better

Great work on this!
Running it atm on my  raspberry 2b+

About Bitcoin Pruning and How to  (Bitcoin 0.12)

Block file pruning
This release supports running a fully validating node without maintaining a copy of the raw block and undo data on disk. To recap, there are four types of data related to the blockchain in the bitcoin system: the raw blocks as received over the network (blk???.dat), the undo data (rev???.dat), the block index and the UTXO set (both LevelDB databases). The databases are built from the raw data.

Block pruning allows Bitcoin Core to delete the raw block and undo data once it’s been validated and used to build the databases. At that point, the raw data is used only to relay blocks to other nodes, to handle reorganizations, to look up old transactions (if -txindex is enabled or via the RPC/REST interfaces), or for rescanning the wallet. The block index continues to hold the metadata about all blocks in the blockchain.

The user specifies how much space to allot for block & undo files. The minimum allowed is 550MB. Note that this is in addition to whatever is required for the block index and UTXO databases. The minimum was chosen so that Bitcoin Core will be able to maintain at least 288 blocks on disk (two days worth of blocks at 10 minutes per block). In rare instances it is possible that the amount of space used will exceed the pruning target in order to keep the required last 288 blocks on disk.

Block pruning works during initial sync in the same way as during steady state, by deleting block files “as you go” whenever disk space is allocated. Thus, if the user specifies 550MB, once that level is reached the program will begin deleting the oldest block and undo files, while continuing to download the blockchain.

For now, block pruning disables block relay. In the future, nodes with block pruning will at a minimum relay “new” blocks, meaning blocks that extend their active chain.

Block pruning is currently incompatible with running a wallet due to the fact that block data is used for rescanning the wallet and importing keys or addresses (which require a rescan.) However, running the wallet with block pruning will be supported in the near future, subject to those limitations.

Block pruning is also incompatible with -txindex and will automatically disable it.

Once you have pruned blocks, going back to unpruned state requires re-downloading the entire blockchain. To do this, re-start the node with -reindex. Note also that any problem that would cause a user to reindex (e.g., disk corruption) will cause a pruned node to redownload the entire blockchain. Finally, note that when a pruned node reindexes, it will delete any blk???.dat and rev???.dat files in the data directory prior to restarting the download.

To enable block pruning on the command line:

    -prune=N: where N is the number of MB to allot for raw block & undo data.

Modified RPC calls:

    getblockchaininfo now includes whether we are in pruned mode or not.
    getblock will check if the block’s data has been pruned and if so, return an error.
    getrawtransaction will no longer be able to locate a transaction that has a UTXO but where its block file has been pruned.

Pruning is disabled by default.

Thanks for your support to Bitcoin and the community! very nice setup, will use the image at twitter.

New Bitcoin client is awesome, you can prune the blockchain to a 2Gb size, here is the update procedure.


Enjoy your new and updated Bitcoin Fullnode 0.12

You can store the blockchain on an USB device like USB memory stick or better an USB hard drive.

I plugged a 750GB USB 2.5" external harddisk in my Pi 2, the blockchain is there so no worries regarding size of the blockchain the next year(s). Bitcoind runs on the pi, only a simple edit (datadir= ) of the bitcoin.conf is needed. ROKOS recognized the USB HDD at once, no problem mounting it and stuff.

I am wondering what will happen when the size of the blockchain goes above limit! For example think of the blockchain size crossing 100 GB!
How will the memory card inside the pi be able to hold such a long chain?

Will there be an option to store it in cloud in future to deal with the storage issue?

Btw I like the whole concept though and I might try it soon on my spare pi.

Hi how would I update to 0.12 ? I hear it has a pruned function so it will actually fit on my zero

ROKOS Bitcoin Fullnode is now an official partner for the upcoming and
most expected cryptocurrency event yet, CoinFestUK.

http://coinfestuk.org/

https://twitter.com/BitcoinFullnode/status/693156316664221696

Smooth install. Downloading the blockchain right now. Sooooo slow!!

ahh.. yeah, that is what the issue was!!

It says it's corrupt if you try and open the image up rather than mount it to a sd card

Hi, there's more than 980+ downloads so far, might of got it because of the network and other downloads at same time,
You can try to download it again with a good internet connection, can help to get it right (first report of getting a corrupted download so far).

Hope it helps, Feel free to let us know your results.

Can't copy the blockchain from your windows to a usb? what seems to be the issue?

downloaded the file
it tells me the file is corrupt..

My blockchain wouldn't copy from my Windows machine :/ scp why do you hate me?

-dbcache=50 can be used when starting the daemon,

dbcache=50 for adding it to the bitcoin.conf

cheers

I now entered -dbcache at the bitcoind command line. If I put it in the bitcoin.conf do I also use the - in front of the command or without?

which one is right?

1) -dbcache=50
or
2) dbcache=50

Remember you can also add:

-dbcache=50

to the bitcoin.conf file if you use the system for something else to improve stability.


Thanks for your feedback and support!

I installed Rokos v4 last night on my Pi2 with a Verbatim USB Harddisk and it is very easy to install. Just amazing how easy it is, download img, burn image on SD, insert SD in Pi2, start it up, run raspi-config for some small setting country+keyboard and you are good to go! Previous to the install I copied full blockchain from my linux server on to the USB HDD, then set datadir for bitcoind to the path on the USB HDD, edited bitcoin.conf and you have a full node running. It runs now for about 13 hours and it's very stable.



Thanks Rokos for making this awesome image, I will donate some BTC soon