Berkeleydb Sasecurity Wiki FANDOM powered by Wikia
Berkeleydb Sasecurity Wiki FANDOM powered by Wikia
Compilation on Debian Wheezy fails - need to use libdb 4.8 ...
Berkeley DB 4.8 installer - GitHub
build: Add options to override BDB cflags/libs · bitcoin ...
Install berkeley 4.8 db libs on Ubuntu 16.04 - 88plug
Make your own stakebox. Ultimate beginners guide how to compile any wallet on AARCH64 (Raspbery pi and other SBC)
I contemplated to wrote this for a long time, so it's finally time. As you know a lot of altcoins uses PoS (Proof-of-stake) way of "mining" coins. Which basically means, that you hold coins on your unlocked wallet and you are receiving stakes as a reward. This requires very little power and it can bring you a lot of rewards, at just 10W from the wall. So first I am using latest Raspbian on RPI4B 4GB in this example.Setting up Raspbian is not part of this process since it's very well documented. I recommend to change user from pi to something else due to security concerns and you can also do other stuff just search "security Raspberry PI" and you find a lot of articles, but this is not the focus of this guide. I know there are a lot of guides on the internet, but I am using like 5 sources, so it's compiled what other people wrote and some of my research. I am using AnyDesk insted of SSH or VNC server, because it works it's ligthweit and it just works. So after you see the gui of Raspbian, just launch terminal (CTRL + ALT + T) and do basic thing: sudo apt-get update && sudo apt-get upgrade Than press Y and let it run, after is finished, we need to prepare so dependency packages. Since most of the wallets using Berkeley DB 4.8 we need to obtain it. So in terminal wrote:
cd cd Downloads wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz tar -xzvf db-4.8.30.NC.tar.gz cd db-4.8.30.NC/build_unix ../dist/configure --enable-cxx make sudo make install
So wait unti it's finished and than you can delete files in Downloads folder in gui or use:
Watch the output folder which it creates, it's stated in the first two lines and copy then by highliting the text and CTRL+SHIFT+C copy it to your clipboard.
cd Streamies (this is that git created folder) ./autogen.sh ./configure CPPFLAGS="-I/uslocal/BerkeleyDB.4.8/include -O2" LDFLAGS="-L/uslocal/BerkeleyDB.4.8/lib" sudo make (this could take hours) sudo make install
And you are done, files is going to be in folder /uslocal/bin (DO NOT delete git created folder, because you are going to need it for faster compiling, when wallet get's and update.)
Now you can list files by:
And then you can copy/move them where ever you want by using:
sudo mv * [destination full path]
Let it run and go back to folder where you move those files.
sudo chmod +x streamies-qt (since we want to run wallet)
In most cases compiled files are going to in format of "shared library" so we need to create script to run it. Open up a text editor from gui or through nano. And paste this to that file:
And save it as a sh file, for example run.sh. Then we need to make it runnable so:
sudo chmod +x run.sh
Now to run it, it's just:
And here we are glorious GUI wallet appears and you are done, you can paste blockchain, wallet.dat from other sources, so this migration is pretty easy and you, if you have it on for exaple flash disk. So this is basic how to compile QT wallets on AARCH64. I am running 7 wallets, 2 of those are Masternodes and RPI 4B 4GB would handle way more, I am at best on half of my RAM. Some wallets need more package, but it's not much of and issue, since compiling stops and you just copy paste nape which is missing put it in the google and add "apt-get" after the name of package and you are going to see, what is the name of the packages so it can be retreived from package assinstant aka apt-get. So basically:
sudo apt-get install [package name]
Then press y and again wrote:
This process is going to continue where it was left off, so nothing is going to run from beginning. Updating wallets is basically exactly same, just repeat steps from "git clone" and after that proceed as it was written above. So I hope this helps some of you, to use this at home and not on some VPS, if you are anxious as me, to host my wallets on remote server.
Is it normal for a new Full Node server to repeatedly show Potential Sale Tip detected messages? What does this even mean. I surprisingly can't find anything with a solution on the internet. Please look at my log dump and give me an idea what to do. Im trying to run a full node in service to the net
Here is my log messages: 2019-11-14T03:05:38Z Bitcoin Core version v0.18.1 (release build) 2019-11-14T03:05:38Z Assuming ancestors of block 0000000000000000000f1c54590ee18d15ec70e68c8cd4cfbadb1b4f11697eee have valid signatures. 2019-11-14T03:05:38Z Setting nMinimumChainWork=0000000000000000000000000000000000000000051dc8b82f450202ecb3d471 2019-11-14T03:05:38Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation 2019-11-14T03:05:38Z Default data directory /home/norman/.bitcoin 2019-11-14T03:05:38Z Using data directory /media/norman/Seagate Expansion Drive/.bitcoin/ 2019-11-14T03:05:38Z Config file: /media/norman/Seagate Expansion Drive/.bitcoin/bitcoin.conf (not found, skipping) 2019-11-14T03:05:38Z Using at most 125 automatic connections (1024 file descriptors available) 2019-11-14T03:05:38Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-11-14T03:05:38Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-11-14T03:05:38Z Using 8 threads for script verification 2019-11-14T03:05:38Z scheduler thread start 2019-11-14T03:05:38Z HTTP: creating work queue of depth 16 2019-11-14T03:05:38Z No rpcpassword set - using random cookie authentication. 2019-11-14T03:05:38Z Generated RPC authentication cookie /media/norman/Seagate Expansion Drive/.bitcoin/.cookie 2019-11-14T03:05:38Z HTTP: starting 4 worker threads 2019-11-14T03:05:38Z Using wallet directory /media/norman/Seagate Expansion Drive/.bitcoin/ 2019-11-14T03:05:38Z init message: Verifying wallet(s)... 2019-11-14T03:05:38Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-11-14T03:05:38Z Using wallet /media/norman/Seagate Expansion Drive/.bitcoin/ 2019-11-14T03:05:38Z BerkeleyEnvironment::Open: LogDir=/media/norman/Seagate Expansion Drive/.bitcoin/database ErrorFile=/media/norman/Seagate Expansion Drive/.bitcoin/db.log 2019-11-14T03:05:39Z init message: Loading banlist... 2019-11-14T03:05:39Z Cache configuration: 2019-11-14T03:05:39Z * Using 2.0 MiB for block index database 2019-11-14T03:05:39Z * Using 8.0 MiB for chain state database 2019-11-14T03:05:39Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space) 2019-11-14T03:05:39Z init message: Loading block index... 2019-11-14T03:05:39Z Opening LevelDB in /media/norman/Seagate Expansion Drive/.bitcoin/blocks/index 2019-11-14T03:05:39Z Opened LevelDB successfully 2019-11-14T03:05:39Z Using obfuscation key for /media/norman/Seagate Expansion Drive/.bitcoin/blocks/index: 0000000000000000 2019-11-14T03:05:39Z LoadBlockIndexDB: last block file = 0 2019-11-14T03:05:39Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03) 2019-11-14T03:05:39Z Checking all blk files are present... 2019-11-14T03:05:39Z Opening LevelDB in /media/norman/Seagate Expansion Drive/.bitcoin/chainstate 2019-11-14T03:05:40Z Opened LevelDB successfully 2019-11-14T03:05:40Z Using obfuscation key for /media/norman/Seagate Expansion Drive/.bitcoin/chainstate: fb03fb54abfe4745 2019-11-14T03:05:40Z Loaded best chain: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03T18:15:05Z progress=0.000000 2019-11-14T03:05:40Z init message: Rewinding blocks... 2019-11-14T03:05:40Z init message: Verifying blocks... 2019-11-14T03:05:40Z block index 1516ms 2019-11-14T03:05:40Z init message: Loading wallet... 2019-11-14T03:05:40Z BerkeleyEnvironment::Open: LogDir=/media/norman/Seagate Expansion Drive/.bitcoin/database ErrorFile=/media/norman/Seagate Expansion Drive/.bitcoin/db.log 2019-11-14T03:05:40Z [default wallet] nFileVersion = 180100 2019-11-14T03:05:40Z [default wallet] Keys: 2001 plaintext, 0 encrypted, 2001 w/ metadata, 2001 total. Unknown wallet records: 0 2019-11-14T03:05:41Z [default wallet] Wallet completed loading in 449ms 2019-11-14T03:05:41Z [default wallet] setKeyPool.size() = 2000 2019-11-14T03:05:41Z [default wallet] mapWallet.size() = 0 2019-11-14T03:05:41Z [default wallet] mapAddressBook.size() = 0 2019-11-14T03:05:41Z mapBlockIndex.size() = 1 2019-11-14T03:05:41Z nBestHeight = 0 2019-11-14T03:05:41Z torcontrol thread start 2019-11-14T03:05:41Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there 2019-11-14T03:05:41Z Bound to [::]:8333 2019-11-14T03:05:41Z Bound to 0.0.0.0:8333 2019-11-14T03:05:41Z init message: Loading P2P addresses... 2019-11-14T03:05:41Z Loaded 253 addresses from peers.dat 16ms 2019-11-14T03:05:41Z init message: Starting network threads... 2019-11-14T03:05:41Z net thread start 2019-11-14T03:05:41Z dnsseed thread start 2019-11-14T03:05:41Z opencon thread start 2019-11-14T03:05:41Z init message: Done loading 2019-11-14T03:05:41Z addcon thread start 2019-11-14T03:05:41Z msghand thread start 2019-11-14T03:05:52Z Loading addresses from DNS seeds (could take a while) 2019-11-14T03:05:54Z 187 addresses found from DNS seeds 2019-11-14T03:05:54Z dnsseed thread exit 2019-11-14T03:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1890 seconds ago) 2019-11-14T03:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2520 seconds ago) 2019-11-14T03:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3150 seconds ago) 2019-11-14T04:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3780 seconds ago) 2019-11-14T04:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 4410 seconds ago) 2019-11-14T04:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5040 seconds ago) 2019-11-14T04:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5670 seconds ago) 2019-11-14T04:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6300 seconds ago) 2019-11-14T05:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6930 seconds ago) 2019-11-14T05:12:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 7560 seconds ago) 2019-11-14T05:22:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8190 seconds ago) 2019-11-14T05:33:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8820 seconds ago) 2019-11-14T05:43:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 9450 seconds ago) 2019-11-14T05:54:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10080 seconds ago) 2019-11-14T06:04:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10710 seconds ago) 2019-11-14T06:15:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11340 seconds ago) 2019-11-14T06:25:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11970 seconds ago) 2019-11-14T06:36:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 12600 seconds ago) 2019-11-14T06:46:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13230 seconds ago) 2019-11-14T06:57:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13860 seconds ago) 2019-11-14T07:07:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 14490 seconds ago) 2019-11-14T07:18:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15120 seconds ago) 2019-11-14T07:28:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15750 seconds ago) 2019-11-14T07:39:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 16380 seconds ago) 2019-11-14T07:49:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17010 seconds ago) 2019-11-14T08:00:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17640 seconds ago) 2019-11-14T08:10:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18270 seconds ago) 2019-11-14T08:21:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18900 seconds ago) 2019-11-14T08:31:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 19530 seconds ago) 2019-11-14T08:42:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20160 seconds ago) 2019-11-14T08:52:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20790 seconds ago) 2019-11-14T09:03:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 21420 seconds ago) 2019-11-14T09:13:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22050 seconds ago) 2019-11-14T09:24:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22680 seconds ago) 2019-11-14T09:34:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23310 seconds ago) 2019-11-14T09:45:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23940 seconds ago) 2019-11-14T09:55:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 24570 seconds ago) 2019-11-14T10:06:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25200 seconds ago) 2019-11-14T10:16:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25830 seconds ago) 2019-11-14T10:27:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 26460 seconds ago) 2019-11-14T10:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27090 seconds ago) 2019-11-14T10:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27720 seconds ago) 2019-11-14T10:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28350 seconds ago) 2019-11-14T11:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28980 seconds ago) 2019-11-14T11:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 29610 seconds ago) 2019-11-14T11:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30240 seconds ago) 2019-11-14T11:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30870 seconds ago) 2019-11-14T11:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 31500 seconds ago) 2019-11-14T12:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32130 seconds ago) 2019-11-14T12:12:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32760 seconds ago) 2019-11-14T12:22:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 33390 seconds ago) 2019-11-14T12:33:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34020 seconds ago) 2019-11-14T12:43:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34650 seconds ago) 2019-11-14T12:54:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35280 seconds ago) 2019-11-14T13:04:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35910 seconds ago) 2019-11-14T13:15:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 36540 seconds ago) 2019-11-14T13:25:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37170 seconds ago) 2019-11-14T13:36:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37800 seconds ago) 2019-11-14T13:46:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 38430 seconds ago) 2019-11-14T13:57:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 39060 seconds ago) 2019-11-14T14:07:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 39690 seconds ago) 2019-11-14T14:18:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 40320 seconds ago) 2019-11-14T14:28:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 40950 seconds ago) 2019-11-14T14:39:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 41580 seconds ago) 2019-11-14T14:49:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 42210 seconds ago) 2019-11-14T15:00:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 42840 seconds ago) 2019-11-14T15:10:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 43470 seconds ago) 2019-11-14T15:21:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 44100 seconds ago) 2019-11-14T15:31:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 44730 seconds ago) 2019-11-14T15:42:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 45360 seconds ago) 2019-11-14T15:52:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 45990 seconds ago) 2019-11-14T16:03:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 46620 seconds ago) 2019-11-14T16:13:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 47250 seconds ago) 2019-11-14T16:24:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 47880 seconds ago) 2019-11-14T16:34:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 48510 seconds ago) 2019-11-14T16:45:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 49140 seconds ago) 2019-11-14T16:55:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 49770 seconds ago) 2019-11-14T17:06:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 50400 seconds ago) 2019-11-14T17:16:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 51030 seconds ago) 2019-11-14T17:27:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 51660 seconds ago) 2019-11-14T17:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 52290 seconds ago) 2019-11-14T17:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 52920 seconds ago) 2019-11-14T17:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 53550 seconds ago) 2019-11-14T18:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 54180 seconds ago) 2019-11-14T18:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 54810 seconds ago) 2019-11-14T18:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 55440 seconds ago) 2019-11-14T18:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 56070 seconds ago) 2019-11-14T18:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 56700 seconds ago) 2019-11-14T19:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 57330 seconds ago) this goes on until I decided just to shut down server after 24 hours and the .dat blockchain file was stuck at 16MB in size. Seemed like going nowhere.
Hi, I have had bitcoin core running on a raspberry pi for about 4 month now (followed the raspibolt instructions from stadicus) and it worked fine until 3 days ago it suddenly stopped working. With bitcoin-cli blockchaininfo i got
error code: -28 Loading block index...
or something similar. When a looked in the debug log file i saw this:
2019-08-29T16:48:08Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin/.bitcoin/database ErrorFile=/home/bitcoin/.bitcoin/db.log 2019-08-29T16:48:11Z init message: Loading banlist... 2019-08-29T16:48:11Z Cache configuration: 2019-08-29T16:48:11Z * Using 2.0 MiB for block index database 2019-08-29T16:48:11Z * Using 8.0 MiB for chain state database 2019-08-29T16:48:11Z * Using 90.0 MiB for in-memory UTXO set (plus up to 47.7 MiB of unused mempool space) 2019-08-29T16:48:11Z init message: Loading block index... 2019-08-29T16:48:11Z Opening LevelDB in /home/bitcoin/.bitcoin/blocks/index 2019-08-29T16:48:11Z Opened LevelDB successfully 2019-08-29T16:48:11Z Using obfuscation key for /home/bitcoin/.bitcoin/blocks/index: 0000000000000000 2019-08-29T16:54:14Z 2019-08-29T16:54:14Z Bitcoin Core version v0.18.1 (release build) 2019-08-29T16:54:14Z Assuming ancestors of block 0000000000000000000f1c54590ee18d15ec70e68c8cd4cfbadb1b4f11697eee have valid signatures. 2019-08-29T16:54:14Z Setting nMinimumChainWork=0000000000000000000000000000000000000000051dc8b82f450202ecb3d471 2019-08-29T16:54:14Z Using the 'standard' SHA256 implementation 2019-08-29T16:54:15Z Default data directory /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z Using data directory /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z Config file: /home/bitcoin/.bitcoin/bitcoin.conf 2019-08-29T16:54:15Z Using at most 20 automatic connections (1024 file descriptors available) 2019-08-29T16:54:15Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-08-29T16:54:15Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-08-29T16:54:15Z Using 4 threads for script verification 2019-08-29T16:54:15Z scheduler thread start 2019-08-29T16:54:15Z HTTP: creating work queue of depth 16 2019-08-29T16:54:15Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-08-29T16:54:15Z HTTP: starting 4 worker threads 2019-08-29T16:54:15Z Using wallet directory /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z init message: Verifying wallet(s)... 2019-08-29T16:54:15Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-08-29T16:54:15Z Using wallet /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin/.bitcoin/database ErrorFile=/home/bitcoin/.bitcoin/db.log 2019-08-29T16:54:16Z init message: Loading banlist... 2019-08-29T16:54:16Z Cache configuration: 2019-08-29T16:54:16Z * Using 2.0 MiB for block index database 2019-08-29T16:54:16Z * Using 8.0 MiB for chain state database 2019-08-29T16:54:16Z * Using 90.0 MiB for in-memory UTXO set (plus up to 47.7 MiB of unused mempool space) 2019-08-29T16:54:16Z init message: Loading block index... 2019-08-29T16:54:16Z Opening LevelDB in /home/bitcoin/.bitcoin/blocks/index 2019-08-29T16:54:16Z Opened LevelDB successfully 2019-08-29T16:54:16Z Using obfuscation key for /home/bitcoin/.bitcoin/blocks/index: 0000000000000000
After that there should follow a line about Loading the block index but it never appears. It seems to be restarting without shutting down correctly, maybe it cannot find the block index? I tried reinstalling core, recreating the symlink to the hdd and resetting the service but nothing happened. Everytime it starts it gets stuck at the same point. It also takes an awful long time to stop bitcoind but i don't know if that is normal. I found several people with similar problems online but noting helped so far. Has anyone had a similar problem in the past and found a solution to this?
Storage space: I am using an 8 GB microSD card for the OS, and a 128 GB USB drive for data. Minimums I would recommend: 8GB SD card and 32 GB USB drive.
Reddcoin Core client version: v184.108.40.206-a8767ba-beta (most recent version at this moment). ↳ Screenshot
You need the OS; Lubuntu. Download Lubuntu (707 MB) for the Raspberry Pi: https://ubuntu-pi-flavour-maker.org/download/. It's a .torrent download, so you will need a BitTorrent client. Message me or post in this thread if you need help with this.
You need software to write the OS to the SD card. I use Etcher. Download Etcher: https://etcher.io/.
Select image: select the lubuntu-16.04.2-desktop-armhf-raspberry-pi.img.xz file.
Select drive: select your microSD card.
Plug the SD card into your Raspberry Pi and power it up.
Lubuntu should boot up.
Set up Lubuntu, connect to the internet (wired or wireless). ↳ As username, I chose "rpi3b". You will see this username throughout this whole tutorial.
Make sure date and time are correct ([Menu] > System Tools > Time and Date). ↳ Click on Unlock to make changes. I personally change Configuration to "Keep synchronized with Internet servers". ↳ Screenshot
Reboot ([Menu] > Logout > Reboot). I am connected to wifi, but have issues getting wifi to work on initial boot. A reboot solves this issue.
Make sure system is up-to-date, install never versions.
Open LXTerminal ([Menu] > System Tools > LXTerminal). ↳ Screenshot
Enter the following in LXTerminal: sudo apt update && sudo apt upgrade ↳ Screenshot
You will be asked if you really want to continue. Enter Y (yes).
Updates are being installed! Wait until it's finished.
Install programs that will be used in this tutorial.
GParted: to partition the USB drive.
Htop: to see the amount of memory (RAM) and swap that is in use.
Enter the following in LXTerminal to install these 2 programs. sudo apt install gparted && sudo apt install htop ↳ Screenshot
Create 2 partitions on the USB drive: 1) Swap partition 2) data partition (for the Reddcoin blockchain) The swap partition is necessary: The Reddcoin wallet can be memory intensive. To prevent any crashes or freezes, add 2 GB of 'virtual' memory by creating a swap partition.
Important: Backup your USB drive if needed. The USB drive will be formatted, so the data on the USB drive will be wiped.
Please use the USB drive solely for this purpose, do not combine it with other stuff.
Keep your USB drive plugged in, do not (randomly) plug it out.
Plug your USB drive in.
GParted will be used to create the partititons. Start GParted via LXTerminal: sudo gparted ↳ Screenshot
Apply the changes. Click on the check mark or select Edit > Apply All Operations. ↳ Screenshot ↳ Screenshot
Important: The name of the swap partition is needed later, so please write it down. Mine is /dev/sda1 (first partition on first drive (drive 'a')). ↳ Screenshot
Reboot. After the reboot, the data partition you just created should be visible on your desktop. ↳ Screenshot
The swap partition is created, so now we can enable and use it.
The swap in use can be monitored with the program Htop. Open Htop ([Menu] > System Tools > Htop) to see the 'Swp' (swap) in use. ↳ Screenshot By default, swap is not used, so 0K. ↳ Screenshot You can leave Htop open.
To enable the swap partition, open LXTerminal and enter the following commands: (Assuming /dev/sda1 is your swap partition.)
Unpack the file (large file, takes around 15 minutes to unpack): sudo xz -d bootstrap.dat.xz ↳ Screenshot
After a successful unpack, your will find the file bootstrap.dat in your USB root folder. ↳ Screenshot
On the first run of the Reddcoin Core client, it will ask for a data directory to store the blockchain and wallet data.
Start the Reddcoin Core client: sudo /media/rpi3b/usb/reddcoin/src/qt/reddcoin-qt ↳ Screenshot
The welcome screen will appear and ask you about the data directory. I suggest a new folder on your USB drive, I picked blockchain. The directory will be created with all the necessary files. ↳ Screenshot
Click on the three dots (...) on the right. ↳ Screenshot
Click on Create Folder at the upper right corner. Type and enter in the folder name. (In my case: blockchain.) Click on Open. ↳ Screenshot ↳ Screenshot ↳ Screenshot
After selecting the directory, the Reddcoin Core client will start. Wait till it's fully loaded and close it.
Move the bootstrap.dat file to your data directory you selected in the previous step. By doing this, Reddcoin Core will use the bootstrap.dat file to import the blockchain, which speeds up syncing. sudo mv bootstrap.dat /media/rpi3b/usb/blockchain/ (Assuming blockchain as data directory.) ↳ Screenshot
The Reddcoin Core client set up is completed, but you still have to sync fully with the blockchain before you can send, receive and stake.
Keep the client running until it's fully synchronized. It will use the bootstrap file first, and download the rest of the blockchain to complete the sync. This can take some time (it took 2 days for me). Syncing the blockchain uses a lot of resources, so the software may react slow.
You can see the progress in the debug window (Help > Debug window). ↳ Screenshot
When the synchronization is completed, the red (out of sync) will disappear on the Overview screen! ↳ Screenshot
When synchronization is complete, you can start staking your Reddcoins.
You can write down your private key or copy and save it in a document. Make sure you save it somewhere only you can access it.
To import later: Debug window -> Console -> importprivkey [label] [label] is optional. ↳ Screenshot (without a label) ↳ Screenshot (with a label)
Boot with only 1 USB drive plugged in: Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly. If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
Start Reddcoin Core easier Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
Right Click on your Desktop and select Create New -> Empty File. ↳ Screenshot
Enter a file name, make sure it ends with .sh, and click on OK. I've chosen for Reddcoin.sh. ↳ Screenshot The file will be created on your Desktop. ↳ Screenshot
Add the command to start Reddcoin to the file.
Right click on the file, select Leafpad (to open the file in a text editor). ↳ Screenshot
Add the following to the file and save the file: sudo /media/rpi3b/usb/reddcoin/src/qt/reddcoin-qt ↳ Screenshot
To be able to execute the shell script (.sh), it has to have 'execute permissions'.
Right click on the file, and select Properties. ↳ Screenshot
Click on the Permissions tab.
For Execute, select Anyone, and click on OK. ↳ Screenshot
To start Reddcoin Core, double click on the file. A new window will pop-up, asking you what you want. Execute in Terminal is what we want, so you can click on enter. ↳ Screenshot Reddcoin Core will now start. Do not close the Terminal window, you can minimize it if needed.
Minimization options Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
Activate 'Minimize on close'. Settings -> Options... -> Window (tab) -> Minimize on close. ↳ Screenshot Reddcoin will still run when you click on the X button. To close/exit Reddcoin, right click on the Reddcoin icon in the system tray (bottom right corner). ↳ Screenshot
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
After your download is finished, open the file and click Install Package. ↳ Screenshot
To run the VNC Connect once:
Open [Menu] > Run, and enter: vncserver-x11 ↳ Screenshot
To auto run on startup:
Open Default applications for LXSession ([Menu] > Preferences > Default applications for LXSession). ↳ Screenshot
In LXSessions configuration, select Autostart in the menu left.
Under Manual autostarted applications, enter vncserver-x11 and click on + Add. ↳ Screenshot ↳ Screenshot
Reboot your Raspberry Pi and check if VNC Connect is started automatically after the reboot.
When VNC Connect is running, you'll see a VNC icon on the right bottom corner. Double click the icon to open VNC Connect and to see the IP address you need to enter to connect to your Raspberry Pi. ↳ Screenshot
[DEVELOPMENT] Bitcoind IPV4 testnet port (18332) is failing to bind
[SOLVED] Thanks for everyone that have helped!
Hello everyone, this is a development problem that I'm currently having. Since the BTC Development sub is kind of inactive and I couldn't find any rule contraty to posting about BTC Development, I'll try my luck in here as I'm hopeless already. I've posted on BTC Stack Exchange but no answers also. Please, don't get me wrong, I'm trying to solve this problem for many days now, I've looked up everywhere for this. I'm new to Bitcoin development and I'm currently having difficulties trying to make RPC calls from a Docker Container to a Bitcoin-Core daemon running in a SSH server. I suppose that the problem may be with Firewall or closed ports, but I also do not know much about Network settings. I'm using nbobtc/bitcoind-php package to make the RPC calls with HTTP requests, and it is running in a Docker container. I'm sure the container is functional and is not the problem. So here's what happening: when I run bitcoind in root user (but normal also won't work) in my SSH server, the IPV4 testnet port seems to be not opened. This message goes up when I run bitcoind:
Here's what my bitcoin.conf looks like (I want to use testnet in here). I'm using Bitcoin-Core "subversion": "Satoshi:0.17.1".
server=1 debug=net txindex=1 testnet=1 rpcuser=userb rpcpassword=test test.rpcport=18332 # I've already tried allowing the IP these 3 ways: # rpcallowip=192.168.xx.xx # My machine's IP # rpcallowip=172.19.x.x/xx # Docker's NBOBTC container IP # rpcallowip=0.0.0.0/0 # Allowing all IP datadir=/home/bitcoin-dev/.bitcoin debuglogfile=/home/bitcoin-dev/.bitcoin/debug.log
Here's what appears in debug.log right after I run Bitcoind:
2019-05-06T14:43:10Z Bitcoin Core version v0.17.1 (release build) 2019-05-06T14:43:10Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2019-05-06T14:43:10Z Assuming ancestors of block 0000000000000037a8cd3e06cd5edbfe9dd1dbcc5dacab279376ef7cfc2b4c75 have valid signatures. 2019-05-06T14:43:10Z Setting nMinimumChainWork=00000000000000000000000000000000000000000000007dbe94253893cbd463 2019-05-06T14:43:10Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation 2019-05-06T14:43:10Z Default data directory /root/.bitcoin 2019-05-06T14:43:10Z Using data directory /home/bitcoin-dev/.bitcoin/testnet3 2019-05-06T14:43:10Z Using config file /home/bitcoin-dev/.bitcoin/bitcoin.conf 2019-05-06T14:43:10Z Using at most 125 automatic connections (1024 file descriptors available) 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 4 threads for script verification 2019-05-06T14:43:10Z scheduler thread start 2019-05-06T14:43:10Z Binding RPC on address 0.0.0.0 port 18332 failed. 2019-05-06T14:43:10Z HTTP: creating work queue of depth 16 2019-05-06T14:43:10Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-05-06T14:43:10Z HTTP: starting 4 worker threads 2019-05-06T14:43:10Z Using wallet directory /home/bitcoin-dev/.bitcoin/testnet3/wallets 2019-05-06T14:43:10Z init message: Verifying wallet(s)... 2019-05-06T14:43:10Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-05-06T14:43:10Z Using wallet wallet.dat 2019-05-06T14:43:10Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin-dev/.bitcoin/testnet3/wallets/database ErrorFile=/home/bitcoin-dev/.bitcoin/testnet3/wallets/db.log 2019-05-06T14:43:10Z net: setting try another outbound peer=false 2019-05-06T14:43:10Z Cache configuration: 2019-05-06T14:43:10Z * Using 2.0MiB for block index database 2019-05-06T14:43:10Z * Using 56.0MiB for transaction index database 2019-05-06T14:43:10Z * Using 8.0MiB for chain state database 2019-05-06T14:43:10Z * Using 384.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2019-05-06T14:43:10Z init message: Loading block index... 2019-05-06T14:43:10Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/blocks/index 2019-05-06T14:43:10Z Opened LevelDB successfully 2019-05-06T14:43:10Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/blocks/index: 0000000000000000 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file = 161 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=755, size=30875345, heights=1513309...1514061, time=2019-04-29...2019-05-03) 2019-05-06T14:43:19Z Checking all blk files are present... 2019-05-06T14:43:20Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/chainstate 2019-05-06T14:43:20Z Opened LevelDB successfully 2019-05-06T14:43:20Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/chainstate: 2686d59caeb1917c 2019-05-06T14:43:20Z Loaded best chain: hashBestChain=00000000b3b6a5db140b6058b7abe5cb00d8af61afd2a237ae3468cd36e387fa height=927391 date=2016-09-08T15:04:00Z progress=0.311180 2019-05-06T14:43:20Z init message: Rewinding blocks... 2019-05-06T14:43:29Z init message: Verifying blocks... 2019-05-06T14:43:29Z Verifying last 6 blocks at level 3 2019-05-06T14:43:29Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE]. 2019-05-06T14:43:29Z No coin database inconsistencies in last 6 blocks (500 transactions) 2019-05-06T14:43:29Z block index 19450ms 2019-05-06T14:43:29Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex 2019-05-06T14:43:30Z Opened LevelDB successfully 2019-05-06T14:43:30Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex: 0000000000000000 2019-05-06T14:43:30Z init message: Loading wallet... 2019-05-06T14:43:30Z txindex thread start 2019-05-06T14:43:30Z [default wallet] nFileVersion = 170100 2019-05-06T14:43:30Z [default wallet] Keys: 2005 plaintext, 0 encrypted, 2005 w/ metadata, 2005 total. Unknown wallet records: 1 2019-05-06T14:43:30Z Syncing txindex with block chain from height 694205 2019-05-06T14:43:30Z [default wallet] Wallet completed loading in 123ms 2019-05-06T14:43:30Z [default wallet] setKeyPool.size() = 2000 2019-05-06T14:43:30Z [default wallet] mapWallet.size() = 7 2019-05-06T14:43:30Z [default wallet] mapAddressBook.size() = 4 2019-05-06T14:43:30Z mapBlockIndex.size() = 1515581 2019-05-06T14:43:30Z nBestHeight = 927391 2019-05-06T14:43:30Z torcontrol thread start 2019-05-06T14:43:30Z Bound to [::]:18333 2019-05-06T14:43:30Z Bound to 0.0.0.0:18333 2019-05-06T14:43:30Z init message: Loading P2P addresses... 2019-05-06T14:43:30Z Loaded 10420 addresses from peers.dat 36ms 2019-05-06T14:43:30Z init message: Loading banlist... 2019-05-06T14:43:30Z Loaded 0 banned node ips/subnets from banlist.dat 29ms 2019-05-06T14:43:30Z init message: Starting network threads... 2019-05-06T14:43:30Z net thread start 2019-05-06T14:43:30Z dnsseed thread start 2019-05-06T14:43:30Z addcon thread start 2019-05-06T14:43:30Z msghand thread start 2019-05-06T14:43:30Z init message: Done loading 2019-05-06T14:43:30Z opencon thread start
After all that appears above, there are just "UpdateTip", "Requesting block", "received block" and "getdata" messages. (so the P2P port, 18333, works). And here is when I netstat: sudo netstat -nap|grep bitcoin|grep LISTEN
Could we get some compiling instructions for Bitcoin SV? I'm having a hard time compiling it to run on my server alongside a bitcoin node. When I try to start it up after compiling, it says unable to start HTTP server. Also, the wallet functions are limited because for whatever reason I can't get it to use the Berkeleys DB. Please post some terminal commands for Ubuntu/Debian based installation :) thanks
PSA: Monero 0.10.2 is out, and is a STRONGLY recommended update:)
this details the 0.10.2.1 point release, which includes a minor fix for RPC issues on 0.10.2
This is a necessary point release of Monero v0.10 "Wolfram Warptangent", and is a strongly, strongly recommended update as it includes massive efficiency improvements to the RingCT validation code and various other necessary bug fixes. Some highlights of this release are:
the 0.10.2.1 point release fixes two sets of RPC issues that affected the 0.10.2 point release
massive speed improvements to RingCT validation
cache tx hashes for failed txs with bad semantics
added an update notification / download / verification system (to be expanded to include opt-in auto-updating for unattended daemons)
initial smart mining implementation (Linux only)
improvements to IBD (initial block download) and sync speed
switched to a portable serialiser so that wallet files can be used on any operating system
added uptime to daemon status
added support for separated mempool / peer datasets for multiple nodes on the same machine (with different p2p ports)
added a change_password command to monero-wallet-cli
addes support for restoring wallets from a certain date
added mempool prioritisation of older txs
added fixes to fluffy blocks (not enabled by default on mainnet yet)
add HTTP digest authentication support to all RPC interfaces
added a connection limit for incoming connections from the same IP
switched to EasyLogging++ for logs
added a gray peerlist house keeping system
added support for multiple daemons using the same LMDB database
added additional password prompting for monero-wallet-cli actions
added additional output detail for ring output selection in monero-wallet-cli
fixed issues with wallets dealing with large reorgs
massive additions to libwallet_api for additional functions used by the GUI
removed support for BerkeleyDB, as it is now deprecated
added support for Android
added support for DragonFlyBSD
fixed armv8 build issues
Contributors for this Release
This release was the direct result of 24 people who worked, largely unpaid and altruistically, to put out 527 commits containing 21 090 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
A GPG-signed list of the hashes is at https://getmonero.org/downloads/hashes.txt and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys)
I want to stake Reddcoins on my Raspberry Pi, but there is no easy to install package for the Reddcoin Core client. I found some tutorials (mentioned at the bottom, under 'credits'), but I still struggled to get the result I wanted. It took some small adjustments, but I got the GUI Wallet of Reddcoin Core working on my Raspberry Pi Model 3B. See the steps below. :).
If you have any questions or comments, please post a comment in this thread, so others can also benefit from it.
If you would like to tip me: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
Even though Raspbian is the primary OS for the Raspberry Pi, it seems that it's not possible to build and compile the Reddcoin wallet software for Raspbian Stretch. However, I got the wallet compiled using Ubuntu MATE.
RPi: Raspberry Pi 3 Model B
OS: Ubuntu MATE 16.04.2 (Xenial)
Space needed: I would recommend at least 32 GB. I am using an 8 GB SD card for the OS, and a 128 GB USB drive for data.
The Reddcoin wallet can be memory intensive. To prevent any crashes or freezes, add 1 GB of 'virtual' memory by creating a swap file. After your Raspberry Pi has rebooted, open MATE Terminal again and enter the following commands:
sudo fallocate -l 1G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
To make sure the swap file persistent (so it survives a reboot), you have to add a line to the /etc/fstab file.
In MATE Terminal, enter the following command to open the file in Pluma (text editor): sudo pluma /etc/fstab
In Pluma, create a new line, add this text: /swapfile none swap sw 0 0 ↳ Screenshot (You should add spaces to vertically align the lines.)
Save and close the file.
Back to MATE Terminal; reboot your Pi: sudo reboot
To see if the swap file is used after a reboot, run: sudo cat /proc/swaps ↳ Screenshot
After the reboot, open MATE Terminal again. Download, unpack, configure, build and install Berkeley DB:
Add this line in Pluma: /uslocal/BerkeleyDB.4.8/lib/ ↳ Screenshot
Save and close the file.
Back in MATE Terminal: sudo ldconfig
Download the source of the Reddcoin wallet and build it:
git clone https://github.com/joroob/reddcoin
sudo ./configure --disable-tests
sudo make ↳ Screenshot (this will take some time; with me it took just over 1 hour)
sudo make install
Speed up synchronizing with the Reddcoin blockchain by bootstrapping.
cd (to make sure your working directory is your home directory)
Download the bootstrap file (1.45 GB): sudo wget https://github.com/reddcoin-project/reddcoin/releases/download/v220.127.116.11/bootstrap.dat.xz
Unpack the file: xz -d bootstrap.dat.xz
After a successful unpack, your will find the file ''bootstrap.dat'' in your home folder. ↳ Screenshot
On the first run of the Reddcoin Core client, it will ask for a data directory to store the blockchain and wallet data.
Start the Reddcoin Core client: sudo $HOME/reddcoin/src/qt/reddcoin-qt
The welcome screen will appear and ask you about the data directory. I suggest a new directory in your home directory, I picked 'blockchain'. The directory will be created with all the necessary files. ↳ Screenshot
After selecting the directory, the Reddcoin Core client will start. Wait till it's fully loaded and close it.
Use the file manager (Caja) to browse to your home directory and move the ''bootstrap.dat'' file to your data directory you selected in the previous step. Your home directory is the first item in the File Manager in the left menu.
The Reddit Core client set up is completed, but you still have to sync fully with the blockchain before you can send, receive and stake.
Launch the Reddcoin Core client again: sudo $HOME/reddcoin/src/qt/reddcoin-qt
Keep the client running until it's fully synchronized. This can take some time (it took 2 days for me).
You can see the progress in the debug window (Help > Debug window). ↳ Screenshot
When the synchronization is completed, the red (out of sync) will disappear on the Overview screen!
Your wallet will be encrypted, and the Reddcoin Core client will be closed. Launch the Reddcore Client again. ↳ Screenshot 4
To stake, you need to unlock your wallet (by entering your password): Settings > Unlock Wallet...
Make sure "For staking only" is checked before clicking OK. ↳ Screenshot
You can only stake with Reddcoins that have matured: coins have to be at least 8 hours in your wallet to mature.
The grey arrow at the bottom should be green when staking. Hover over that icon to see the progress of staking. ↳ Screenshot
Backup your wallet! File > Backup wallet... ↳ Screenshot
Start Reddit on system login. Settings > Options ↳ Screenshot > This works when using only an SD card. > I can't get this to work when using SD card (for OS) and a USB (for data/blockchain).
Adjust minimization options, so you can safely press on the red X (close/exit button). ↳ Screenshot
The default browser, Firefox, stops working and crashes after updating Ubuntu MATE. My solution is installing another browser: Chromium. To install Chromium, enter the following in MATE Terminal: sudo apt-get install chromium-browser ↳ Screenshot You can then access Chromium via [Menu] Applications > Internet. ↳ Screenshot
To remote connect to the Raspberry Pi, I use VNC Connect from RealVNC.
Run a 0.14 Full-Node on RaspberryPi3 Pruned(less than 16GB SD needed)
Hi! Happy if this guide helps you. Tip if you want: 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v UPDATE 04/06/17 Add 'uacomment=UASF-SegWit-BIP148' into your bitcoin.conf if you want to signal UASF. UPDATE 03/13/17 ADDED a tl;dr; Version at the end of this Post. UPDATE 03/12/17: Just to test it - I reinstalled all on 8GB SD and it works as well. But maybe you should use at least 16GB for the beginning. Using a 128GB card for the first version was a little bit stupid - so I reinstalled everything on a 8GB SD card. Including Linux and a pruned blockchain - and it works. I used prune=550 and Jessie Lite (headless / command line) - without wallet and gui. The SD is almost full, but it works so far I also updated the whole manual a bit to make things more clear. Thank you for all your feedback! Just started my Bitcoin Node today and wanted to share the way I did it with people who are interested in running their own full node. It took some time to write everything down - hopefully correct so far. I am sure, many people around bitcoin are way more informed and educated as I am - I am the noob. So I wrote this manual to help users like me - noobs, to get started with a cheap, simple bitcoin node on raspberry pi. Have fun! I wanted to get my Raspberry Pi 3 working as a node to support the network. Actually the process of installing and running the node was more or less easy - but for Noobs (like I am) it might be a bit tricky to start the whole thing, because there are different ways. Did you - like me - think you would need +120GB on the raspi, external USB HDD to be a full node? You won't! If you have a Raspberry and you know what Bitcoin is, I guess, you are a little bit aware of linux, networks and of course bitcoin - so I won't go into detail too much. This guide is just a little helper to get a full node running on your raspberry pi. Thanks to the help of the nice people in this sub and of course the documentation by the developers, I got it working - and of course also special thanks to raspnode.com - as I followed their tutorial to start - I went some other ways here and there - so please read carefully. For the Part 2 I would suggest to have http://raspnode.com/diyBitcoin.html open and read through my manual. I split the tutorial in 2 Parts - PART ONE is about installing the client on your PC and downloading the Blockchain. PART TWO is about the setup of the raspberryPi and transferring the pruned blockchain to the pi and run it as a full node! The first thing to be aware of is: You actually need to download the whole blockchain to get this working - if you already have your bitcoin client synced on the PC / MAC great you can reuse it! Now you might think "but you said less than 16GB in the title!" Yes, but the good thing is you won't need to download it on your Raspberry, neither you need to sync it completely on your raspberry which took ages (weeks!) before. When you finished this Guide, you will just have a max. 4GB Blockchain on your Raspberry Pi - but it still is a full node! The magic word is Pruning. Maybe even a 8GB SD Card works just fine including Linux (jessie lite)! So, if you already have a full node on your PC - Great you can almost skip PART ONE - BUT have at how to Prune in PART ONE if you don't know about it. For PART TWO you'll need a Raspberry Pi 2 or 3 (I used 3) min. 8GB (works also) or better 16GB SD Card. (I used a 128GB for the first version of this manual - which is way too big)
This is the manual how to get started on you PC / MAC / Linux (I did it on Win7) Go to: https://bitcoin.org/en/download and download the core Client for your Machine (I used win64). Install it and configure it to save the Blockchaindata to the directory of your choice - so instead getting 120GB on your C drive, I would suggest to download it to another place like a USB drive. You can set this up during the install. Standard folder for the blockchain folder is "%APPDATA%\Bitcoin" on Windows. or you can do it after the install by creating a bitcoin.conf file inside your installation folder / or %APPDATA%\Bitcoin and add
to the file. Line by line. By the way here you could also just add dbcache - to use more memory to speed up the process a bit:
if you don't want to use the settings inside the program. (you can also set this inside the program under settings! If you have this inside the bitcoin.conf you will see the amount you set there from inside the program - it overrides the values) You can check inside the windows client under settings, if you can see a manual dbcache is set by having a look at the left footer area. When your dbcache value shows up, everything is fine. So the Blockchain download process will take time - maybe a few days! Depending on your machine, internet connection and HDD. The Blockchain is huge as it contains every single transaction of the past until today. You won't need to keep your PC running all the time, you can turn it off and on and it will resync automatically when you start bitcoin-qt.exe! Make sure to close the client always via "quit" - ctrl+q. After you have your bitcoin core installed, the blockchain downloaded and synced - you are ready to PRUNE! First - close the Client and let it close smoothly. After it is really closed you can follow these steps:
By pruning, your blockchain will dramatically shrink. From 120GB to just a few GB.
Be aware, that you will lose your Downloaded Blockchain as pruning will erase a big chunk of it! If you have enough space, you could of course keep the full blockchain saved somewhere on another HDD. You can prune by editing your bitcoin.conf file by adding:
I used prune=1024 - not sure where the differences are right now (min. prune=550). (for my 8GB version I used 550! I suggest to use this.) Save the bitcoind.conf file and restart your windows client. It will now clean up the Blockchain. So just the latest blocks are saved. The client should start without any problems. Maybe it takes some time to prune the blockchain data. Check if everything works normally (the client opens as usual, you can see an empty wallet) than close the client. Inside the Bitcoin Folder, you'll find two folders called:
those are the interesting folders containing the important data (now pruned) - and we will transfer those two to the raspberry later! Now you are good to start the raspi transfer explained in the next part.
Here is what I did: 1) I installed Raspian Pixel (https://www.raspberrypi.org/downloads/raspbian/) using a 128 GB SD - which is not needed because of "Pruning" - I think a 16GB card might work, too! (You can also install Raspian Jessie Lite - which saves you even more space, as it runs headless - only command line) (Updated: It is better to use Jessie Lite to save a lot of space - when you are fine with only command line) 2) I followed partly this tutorial to get everything running and setup:
Please have a look at it - I have copied the Headlines in capitals to let you know what I did, and what I skipped. On Tutorial Page: Start with RASPBIAN (OPTIONAL) CONFIG OPTIONS. Set You RasPi up including "EDITING FILES" to save your Layout at the tutorial page and come back here. I skipped the CONFIGURE USB AND SET AUTOMOUNT process, as we are going to use PRUNING to reduce the 120GB to a tiny filesize - so USB Devices are not needed here! It was necessary to ENLARGE SWAP FILE to install bitcoin core - otherwise it didn't went through which ended in a frozen raspi. So have a close look by following the raspnode tutorial at: ENLARGE SWAP FILE. I have my raspi running via cable to router - but you can also WiFi setup everything described under NETWORKING ON THE RASPBERRY PI. Now comes the interesting part: Follow the steps at DOWNLOADING BITCOIN CORE DEPENDENCIES - they work fine for 0.14.0 too. Git should be on Board already when you installed Pixel - otherwise you would need to install it.
sudo apt-get install git -y (only jessy lite)
I skipped the next command lines - as I don't use bitcoin-qt wallet. If you want to use it as wallet - do the step.
as I don't need the wallet functionality. I didn't need to use "MAKE" which saves you maybe up to 2.5 hours. instead you can just go ahead with:
sudo make install
(If I am wrong in doing so - please let me know) The install takes some time - and just a heads up: when it gets stuck somewhere - just redo the installation process - it took three times to went through - stuck at some processing. After the installation took place you can finally get your Raspberry Pi Node running in no time! To test if the the installation went through - you can just start bitcoind using:
than check if everything is working so far:
after a few seconds you should see version: etc... if not, something went wrong. Try to redo the steps in the raspnode tutorial. (don't give up if it failed - retry! Ask your questions here) IMPORTANT: you need to stop bitcoin on your raspberry now!
If you don't need an external USB Drive - what I hope - as we are going to use pruning just go ahead and skip the USB part and create a file inside (or follow the raspnode tutorial on how to setup the USB drive):
cd .bitcoin sudo nano bitcoin.conf
and enter the exact same pruning size you have used on your Desktop Machine to prune. I used 1024 but the minimum is 550. (used 550 for the 8GB SD card on PC and Raspberry)
That's it for the raspi. update: To signal UASF enter in a new line:
Now you have to transfer the two folders CHAINSTATE and BLOCKS from your PC bitcoind directory to your raspberry. I am using a program called "WINSCP" - it is free and easy to use: https://winscp.net/eng/download.php We need this to transfer the files to the Raspberry pi. Pretty sure you can also do it via SSH - but I am the noob. So let's keep it simple. Open Winscp and put in the IP Address of your Raspberry Pi, User and Password (same as in SSH) You should now see the directories on your Raspberry Pi. There is a folder called
enter it and you will see the two folders
blocks & chainstate
you can delete them on the raspberry as they have some data from your previous test inside. Make sure you can also see the bitcoin.conf file in that directory, which needs to contain the exact same prune line, like the one on your desktop machine. If not, make sure to edit it via SSH. The line "datadir=l:\yourfolder" is obviously not needed in the Raspberry bitcoin.conf file. Now grab the two folders CHAINSTATE and BLOCKS from your PC and copy them to your .bitcoind folder. I also copied banlist.dat, fee_estimation.dat, mempool.dat and peers.dat to the folder - not really knowing if needed! Not needed. The whole copy process might take some minutes (against some weeks in the old way). After copying is finished, you can now start bitcoind on the Raspberry.
the & symbol let you still use the command line while the process is running btw. The process - if succesfull - will take some time to finish.
Will give you some informations what is going on right now. When you can see, that it is checking the blocks, this is good! If you get an error - double check - if you have the correct prune size (same as on desktop machine) - in bitcoin.conf and that this file is inside .bitcoin on RaspberryPi. It took me some time, to find my mistakes. Congrats! You are almost a part of the network! To make your node now a fullnode, you will need to go to your router (often 192.168.1.1) and enable portforwarding for your raspberry pi - and open ports 8333 - that's it! You can now go to: https://bitnodes.21.co/nodes/ scroll down to "JOIN THE NETWORK" and check check if your node IP is connected! It will show up as soon as the blocks are checked and the raspi is running. Well done! Now you are running a full node, with a small Blockchain and got it working in Minutes, not weeks! I really hope, my little tutorial worked for you and your are part of the Node network now. If you have problems or I made a mistake in this helper tut, just let me know and I will try to make it better. Have fun and NODL! the noob tl;dr; (if you are a real noob start with the non-tl;dr version!) tl;dr; PART ONE 1) Download & install / setup bitcoincore @ https://bitcoin.org/de/download 2) change dbcache to something smaller than your memory and download the whole Blockchain (120GB). 3) create a file called bitcoin.conf put the line prune=550 (or higher) in to activate pruning on win inside %appData%/bitcoin 4) Open ports 8333 on your Router to make this a full node with a smaller Blockchain. You are running a full node on your PC. tl;dr; PART TWO 1) Install jessie lite and the needed dependencies on your SDCard - Raspberry ( >git clone -b 0.14 https://github.com/bitcoin/bitcoin.git )
see tutorial for more info.
2) create a file called bitcoin.conf inside .bitcoin and add the same prune=Number you had on your PC. 3) transfer the pruned folders BLOCKS and CHAINSTATE to the Raspberry Folder .bitcoin 4)Start "bitcoind &" 5) let everything sync 6) Make sure you have port 8333 opened on your router. You are running a full node on your Raspberry with a super small Blockchain (I put all on a 8GB SDcard) Tip if you want : 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v updated 03/12 - will update more, soon. updated 03/12.2 - I updated the whole process a bit and also added some improvements. updated 03/14/ Added a tl;dr version at the end.
step 12: Build Reddcoin Wallet ---download source code ---- only source from joroob/reddcoin will work because some stweak was needed for ARM CPU
cd ~ git clone https://github.com/joroob/reddcoin.git
---build reddcoin ----
cd reddcoin ./autogen.sh ./configure --with-gui=no --disable-tests cd src make sudo make install
If you finish this, you are in a great position!!! step 13: Create reddcoin configuration file
cd ~ mkdir .reddcoin && cd .reddcoin nano reddcoin.conf rpcuser=YOUR OWN USERNAME, YOU DONT NEED TO REMEMBER THIS, MAKE IT AS LONG AS YOU WANT rpcpassword=YOUR OWN PASS WORD, YOU DONT NEED TO REMEMBER THIS, MAKE IT AS LONG AS YOU WANT
step 14: Use bootstrap (At this point, you had a running reddcoin daemon, now you can start staking. But syncing the full chain takes long time.)
cd ~/.reddcoin wget https://github.com/reddcoin-project/reddcoin/releases/download/v18.104.22.168/bootstrap.dat.xz xz -d bootstrap.dat.xz
step 15: start the reddcoin daemon service cd ~/reddcoin/src ./reddcoind -daemon After this, you can test if the daemon is working, by perform this command: ./reddcoin-cli getblockcount step 16: if your app is not able to sync, it is probably the firewall issue with OS, run this to allow port 45444 (used by Reddcoin) and redo step 15
ADDITIONAL REMARKS: From my PC: I am using putty to execute the command, winSCP to monitor the file location on raspberry. Moving Red Coins out of exchange really a big move, start with normal wallet, don't start with this tutorial :) Ever since I move my coins out of exchange, I am free from all of the ups and downs! Really! So guys and gals, Redd On! UPDATE 18 Mar: my first stake has arrived after 6 days staking :) In case you want to tip me: RaF3TeWqgTzAdnaZQffnsxS74dag13zsAY Edit 1: Format stuff Edit 2: Add step 18 to execute staking command. Edit 3: In case you don't want to compile the source code, you can download my compile version here: https://github.com/hieplenet/reddcoin/releases/tag/v22.214.171.124 (but doing this, you should be aware of the risk of me changing source code for my benefit - I don't change any thing, but you should be cautious, this is the internet :) )
Discord Log from Ravencoin Open Developer Meeting - Oct 5, 2018
joey at 1:57 PM
What kind of transaction types are possible with RVN assets? Is it possible to create an asset that has a set lifetime or self-destruct time?
Tron at 2:00 PM
Not for assets/sub-assets/unique. We might be able to do that with voting tokens.
RavencoinDev at 2:01 PM
SpyderDev at 2:01 PM
[Dev] Blondfrogs at 2:01 PM
Chatturga at 2:01 PM
BruceFenton at 2:01 PM
Probably lots of ways to do a self destruct on second layer as well if desired
russ at 2:01 PM
suuuuuupso what is todays topic?
RavencoinDev at 2:02 PM
Thanks for joining us today. We would like to discuss the current status of the 2.1 release.As well as doing an open Q&A at the end.First though I want to thank everybody that helped get the word out on upgrading to the 126.96.36.199 release!Without that fix being in place and exchanges and pools upgrading we would be having a different conversation today.This community is amazing.
russ at 2:04 PM
we would have ended up like pigeoncoinnot a good look📷2
watsure at 2:05 PM
Hello Mr. God
RavencoinDev at 2:05 PM
russ at 2:05 PM
i gave pigeoncoin the pullrequest but they ignored meglad we have competent devs
[Dev] Blondfrogs at 2:05 PM
Everyone, So we are planning on getting out build 2.1 as soon as possible. We are still doing bug fixes, and getting the code hardened for release. There is currently one bug is the asset layer that we are fixing right now, and once that is done we should have a couple days of testing. It would be lovely if the community helped with testing, and we appreciate all of the testing that the community has already done. Once, we have a basic build that is tested, we are going to make a public release and notify the miners and pools.
RavencoinDev at 2:06 PM
Once that bug is addressed a release branch will be created.
russ at 2:06 PM
that duplicate ownership asset bug is nasty
RavencoinDev at 2:06 PM
You should all be able to build that and jump on testnet.
[Dev] Blondfrogs at 2:07 PM
@russ Yeah, didn't see that one. BUt I have a fix right now that seems to be working on my local machine
RavencoinDev at 2:07 PM
We need as much testing help from our devs as possible.
[Dev] Blondfrogs at 2:07 PM
so, I will have that pushed up with the day.
russ at 2:07 PM
[Dev] Blondfrogs at 2:08 PM
Just a reminder, that when the new wallet is published, if you don't update your wallet by the time assets are voting in by the blocks you will fork. So, we are going to try and get the wallet out there as soon as we can so users have weeks to upgrade.
Skan at 2:09 PM
RavencoinDev at 2:10 PM
Any questions comments about the 2.1 release?
Skan at 2:10 PM
SpyderDev at 2:10 PM
Yes and no
RavencoinDev at 2:10 PM
Good question SkanRight now that's also an issue with Bitcoin.
SpyderDev at 2:12 PM
The short version for Mojave is that the released binaries will work fine.
Skan at 2:12 PM
Interesting, so is it likely going to be a future upgrade that brings stability?
SpyderDev at 2:12 PM
However, developers should hold off.
RavencoinDev at 2:12 PM
We are currently building on High Sierra
Skan at 2:12 PM
Ok good to know for those who ask
SpyderDev at 2:13 PM
There is an incompatibility with Berkeley db version 4 that causes a segfault on init.
RavencoinDev at 2:13 PM
Or using the build scripts that Under created to build on Linux. Thjanks @Under
[Master] Roshii at 2:13 PM
Looks I'm late to the event
[Dev] Blondfrogs at 2:13 PM
RavencoinDev at 2:13 PM
Sorry it's late for you @[Master] Roshii
Skan at 2:14 PM
master roshi is never late, he is simply the turtle hermit
SpyderDev at 2:14 PM
One can upgrade Berkeley-db to the latest version and compile with the --incompatible-bdb and things will run, but there are some unknowns as far as wallet compatibility is concerned.
RavencoinDev at 2:15 PM
Raven will likely follow Bitcoin on Mojave support.
SpyderDev at 2:15 PM
The release binaries are compiled on Linux which we have tested on Mojave, so as long as you aren't compiling binaries go ahead and update to Mojave
RavencoinDev at 2:15 PM
It's a problem they have to solve as well, so...
SpyderDev at 2:15 PM
There is supposed to be a patch to bdb, but so far it isn't working
[Master] Roshii at 2:15 PM
@RavencoinDev it's never late for me.
Skan at 2:15 PM
Ok, and for the devs interested just point them to the berkeley upgrade with some warnings or to Under's scripts?
RavencoinDev at 2:16 PM
Right, the wallet runs just fine on Mojave. It's just a developer issue.
[Master] Roshii at 2:16 PM
If I can say anything it will be : don't update to Mojave
SpyderDev at 2:16 PM
There is a warning note in the docs section for OSX building
RavencoinDev at 2:16 PM
Mojave slowed down @[Master] Roshii and the iOS wallet.
Skan at 2:16 PM
YikesOk good to know, just want to be able to help / point people in the right direction
RavencoinDev at 2:17 PM
SpyderDev at 2:17 PM
There is also an issue with Mojave dark mode and the QT wallet that makes things difficult to read (white on white text). We have a workaround which is to disable dark mode for QT in the plist file.
Skan at 2:17 PM
Ok so this is going to be pretty soon then, right ? Next week, likely?
RavencoinDev at 2:18 PM
Any further Mojave questions?Which @Skan ?
Skan at 2:18 PM
I think that covers it for me2.1 releaseIn order to have weeks to upgrade before main net
RavencoinDev at 2:18 PM
Yes, it is looking like we can work through this last issue with asset re-org very soon.Likely early next week.
Skan at 2:20 PM
Is 2.1 going to have any UI updates ?
RavencoinDev at 2:20 PM
Yes, frogs has more details.
[Dev] Blondfrogs at 2:20 PM
The UI is done. It is currently in the develop2. So if you have built the develop2 branch, you would be looking at the new UI for now.
RavencoinDev at 2:21 PM
There have been other QT designs kicked around and we would love to see more from the community.
[Dev] Blondfrogs at 2:21 PM
Future upgrades to come though. but those won't be mandatory upgrades. Just visual upgrades.
SpyderDev at 2:21 PM
The UI tweaks are subtle, but they make a big difference.
Skan at 2:22 PM
Very cool, I will check out dev2 branch
russ at 2:22 PM
new asset creation UI is awesome
Skan at 2:22 PM
I saw that, I like it. And the longer asset holdings list
RavencoinDev at 2:22 PM
@russ Don't make @[Dev] Blondfrogs head any larger...
russ at 2:23 PM
RavencoinDev at 2:23 PM
Other 2.1 release questions/comments?
Skan at 2:23 PM
Cant think of anything else at the momentThanks!
Hans_Schmidt at 2:23 PM
Is dividend support officially part of 2.1 release? It wasn't intuitive to me how that works.
RavencoinDev at 2:24 PM
No it will be in the next release. However, you could write a script that would provide the same functionality with what will be released in 2.1.
Skan at 2:25 PM
I heard something about Phase 4 being complete already, is that true, and is that in 2.1?
RavencoinDev at 2:25 PM
List all addresses with an asset, loop through sending X raven to each.
Skan at 2:25 PM
RavencoinDev at 2:25 PM
Yes, Unique assets are complete.(edited)
Tron at 2:25 PM
Dividend support can be done without modifying the protocol. We can add it to a version of the software that can be used by the payer, without requiring others to upgrade.So we did phase 1, 2, 4
Skan at 2:26 PM
Oh wowGreat job everyone!
RavencoinDev at 2:26 PM
Yeah, we're super excited about the use cases that assets and unique assets provide to our develoepers(edited)
Skan at 2:27 PM
Can you tell us anything else about this separate software client? Will it be geared more towards enterprise use in general or will it just be that feature?
RavencoinDev at 2:27 PM
Speaking of, do any of you have a dev project in the works with assets?
russ at 2:27 PM
well its not a separate software client, its a backwards compatible release @Skan(edited)kind of like a softfork if you know what that is
Skan at 2:28 PM
Yeah unique assets will be awesome, actually there's a korean community member planning on issuing them along with silver ravencoinsIf im not mistaken
How to install any QT-Wallet on the Raspberry Pi / Pi3B+
Hello and welcome to my first tutorial. Today I will show you how to install almost any QT-wallet on the RaspberryPi. I hope this tutorial will help you. I use the BankSocietyCoin in this tutorial, you can change it also to your fav. Coin. Install Raspbian , *Buster produced a lot of failures on my system while compiling Wallets* (my version: https://downloads.raspberrypi.org/raspbian/images/raspbian-2018-03-14/ ) Run the following commands: Change Swap Size of the Rasp: sudo nano /etc/dphys-swapfile change to CONF_SWAPSIZE=2048 press: ctrl o Enter and ctrl x enable the swap file with its new size: sudo dphys-swapfile setup sudo dphys-swapfile swapon ---------- Install Required Dependencies: apt-get update sudo apt-get install git build-essential libtool autotools-dev autoconf pkg-config libssl-dev libcrypto++-dev libevent-dev libminiupnpc-dev libgmp-dev libboost-all-dev devscripts libdb++-dev libsodium-dev and sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libcrypto++-dev libminiupnpc-dev qt5-default ---------- Install bitcoin PPA files for the compiling process: cd /etc/apt/sources.list.d/ sudo nano bitcoin.list paste to following line: deb-src http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu artful main press: ctrl o Enter and ctrl x sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv C70EF1F0305A1ADB9986DBD8D46F45428842CE5E sudo apt-get update ---------- Install working libssl: cd && sudo apt-get remove libssl-dev sudo nano /etc/apt/sources.list change stretch to jessie press: ctrl o Enter and ctrl x sudo apt-get update sudo apt-get install libssl-dev sudo apt-mark hold libssl-dev sudo apt-mark hold libssl1.0.0 sudo nano /etc/apt/sources.list Change jessie" back to stretch press: ctrl o Enter and ctrl x sudo apt-get update ---------- Compile and Install BerkeleyDB 4.8.30 : wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz sudo tar -xzvf db-4.8.30.NC.tar.gz cd db-4.8.30.NC/build_unix sudo ../dist/configure --enable-cxx sudo make sudo make install export CPATH="/uslocal/BerkeleyDB.4.8/include" export LIBRARY_PATH="/uslocal/BerkeleyDB.4.8/lib" ---------- The wallet: (my way) mkdir wallets , cd wallets git clone https://github.com/RGPickles/BankSocietyCoin cd BankSocietyCoin chmod 755 src/leveldb/build_detect_platform chmod 755 src/secp256k1/autogen.sh cd src/ make -f makefile.unix ./societyd * for qt wallet* cd .. qmake make edit society.conf in .society (rpcuser=SomeCoolRandomUsername rpcpassword=SOMETHINawesomeYOUdontHaveToRemember rpcconnect=127.0.0.1 save. ./society-qt ---------- Have fun! for a Beer - Donations ;) SOCI - Si6V7EwnJqzmFiNGHSbXrtWUXKH6F4EFm3 BTC - 1HpGF4wMzztpJ4KT4o2ySFvnLJ4gCoYaV5 LTC - LS22MgY9G4KbaKhkR5dFi995MbcQhuyDXW ETH - 0x6b5EdC3e58Fd84a40aa942964690adA91C398075 TRX - TKBpktt5QQ9WV57QjonQrGr1vmKLCVQBL6 13.07.2019 DennisHilk ********** if error (makefile.unix:200: obj/rpcclient.o] appears) [This first step is necessary because you will get linking errors if you don't remove the old Boost library] sudo apt remove --purge --auto-remove libboost-dev libboost-thread-dev libboost-system-dev libboost-atomic-dev libboost-regex-dev libboost-chrono-dev mkdir boost cd boost wget https://dl.bintray.com/boostorg/release/1.64.0/source/boost_1_64_0.tar.gz tar xfz boost_1_64_0.tar.gz (can take rly long, dont worry) cd boost_1_64_0/ ./bootstrap.sh ./b2 stage threading=multi link=static --with-thread --with-system sudo ./b2 install threading=multi link=static --with-thread --with-system cd ../../ nano .bash_profile export LIBS="-L/home/YOURS/boost/boost_1_64_0/stage/lib" export CPPFLAGS="-I/home/YOURS/boost/boost_1_64_0" cd society root make clean cd src sudo make -f makefile.unix (if bignum error) sudo apt-get install libgmp-dev or delete opensll and reinstall as above.
What benefits does Nexus bring to the blockchain space?
How does Nexus secure the network and reach consensus?
What is quantum resistance and how does Nexus implement this?
What is Nexus’ Unified Time protocol?
Why does Nexus need its own satellite network?
The Nexus Currency:
How can I get Nexus?
How much does a transaction cost?
How fast does Nexus transfer?
Did Nexus hold an ICO? How is Nexus funded?
Is there a cap on the number of Nexus in existence?
What is the difference between the Oracle wallet and the LLD wallet?
How do I change from Oracle to the LLD wallet?
How do I install the Nexus Wallet?
Types of Mining or Minting:
Can I mine Nexus?
How do I mine Nexus?
How do I stake Nexus?
I am staking with my Nexus balance. What are trust weight, block weight and stake weight?
1. What is Nexus (NXS)? Nexus is a digital currency, distributed framework, and peer-to-peer network. Nexus further improves upon the blockchain protocol by focusing on the following core technological principles:
Nexus will combine our in-development quantum-resistant 3D blockchain software with cutting edge communication satellites to deliver a free, distributed, financial and data solution. Through our planned satellite and ground-based mesh networks, Nexus will provide uncensored internet access whilst bringing the benefits of distributed database systems to the world. For a short video introduction to Nexus Earth, please visit this link
2. What benefits does Nexus bring to the blockchain space? As Nexus has been developed, an incredible amount of time has been put into identifying and solving several key limitations:
Quantum computing vulnerability
Centralized network access
Slow difficulty adjustment
Slow block times
Block reward halving
Nexus is also developing a framework called the Lower Level Library. This LLL will incorporate the following improvements:
LLC (Lower Level Cryptography): This is a suite of cutting edge cryptographic methods including hashing, asymmetric encryption, digital signatures, and symmetric encryption algorithms
LLP (Lower Level Protocol): This is a template protocol to allow any protocol to be created with ease without the need for repeated network programming.
LLD (Lower Level Database): This is a set of templates for creating high efficiency database systems. This high efficiency can be used to power large websites, which are currently built with database software that is not designed to scale.
For information about more additions to the Lower Level Library, please visit here
3. How does Nexus secure the network and reach consensus? Nexus is unique amongst blockchain technology in that Nexus uses 3 channels to secure the network against attack. Whereas Bitcoin uses only Proof-of-Work to secure the network, Nexus combines a prime number channel, a hashing channel and a Proof-of-Stake channel. Where Bitcoin has a difficulty adjustment interval measured in weeks, Nexus can respond to increased hashrate in the space of 1 block and each channel scales independently of the other two channels. This stabilizes the block times at ~50 seconds and ensures no single channel can monopolize block production. This means that a 51% attack is much more difficult to launch because an attacker would need to control all 3 channels. Every 60 minutes, the Nexus protocol automatically creates a checkpoint. This prevents blocks from being created or modified dated prior to this checkpoint, thus protecting the chain from malicious attempts to introduce an alternate blockchain.
4. What is quantum resistance and how does Nexus implement it? To understand what quantum resistance is and why it is important, you need to understand how quantum computing works and why it’s a threat to blockchain technology. Classical computing uses an array of transistors. These transistors form the heart of your computer (the CPU). Each transistor is capable of being either on or off, and these states are used to represent the numerical values 1 and 0. Binary digits’ (bits) number of states depends on the number of transistors available, according to the formula 2n, where n is the number of transistors. Classical computers can only be in one of these states at any one time, so the speed of your computer is limited to how fast it can change states. Quantum computers utilize quantum bits, “qubits,” which are represented by the quantum state of electrons or photons. These particles are placed into a state called superposition, which allows the qubit to assume a value of 1 or 0 simultaneously. Superposition permits a quantum computer to process a higher number of data possibilities than a classical computer. Qubits can also become entangled. Entanglement makes a qubit dependant on the state of another, enabling quantum computing to calculate complex problems, extremely quickly. One such problem is the Discrete Logarithm Problem which elliptic curve cryptography relies on for security. Quantum computers can use Shor’s algorithm to reverse a key in polynomial time (which is really really really fast). This means that public keys become vulnerable to quantum attack, since quantum computers are capable of being billions of times faster at certain calculations. One way to increase quantum resistance is to require more qubits (and more time) by using larger private keys: Bitcoin Private Key (256 bit) 5Kb8kLf9zgWQnogidDA76MzPL6TsZZY36hWXMssSzNydYXYB9KF Nexus Private Key (571 bit) 6Wuiv513R18o5cRpwNSCfT7xs9tniHHN5Lb3AMs58vkVxsQdL4atHTF Vt5TNT9himnCMmnbjbCPxgxhSTDE5iAzCZ3LhJFm7L9rCFroYoqz Bitcoin addresses are created by hashing the public key, so it is not possible to decrypt the public key from the address; however, once you send funds from that address, the public key is published on the blockchain rendering that address vulnerable to attack. This means that your money has higher chances of being stolen. Nexus eliminates these vulnerabilities through an innovation called signature chains. Signature chains will enable access to an account using a username, password and PIN. When you create a transaction on the network, you claim ownership of your signature chain by revealing the public key of the NextHash (the hash of your public key) and producing a signature from the one time use private key. Your wallet then creates a new private/public keypair, generates a new NextHash, including the corresponding contract. This contract can be a receive address, a debit, a vote, or any other type of rule that is written in the contract code. This keeps the public key obscured until the next transaction, and by divorcing the address from the public key, it is unnecessary to change addresses in order to change public keys. Changing your password or PIN code becomes a case of proving ownership of your signature chain and broadcasting a new transaction with a new NextHash for your new password and/or PIN. This provides the ability to login to your account via the signature chain, which becomes your personal chain within the 3D chain, enabling the network to prove and disprove trust, and improving ease of use without sacrificing security. The next challenge with quantum computers is that Grover’s algorithm reduces the security of one-way hash function by a factor of two. Because of this, Nexus incorporates two new hash functions, Skein and Keccak, which were designed in 2008 as part of a contest to create a new SHA3 standard. Keccak narrowly defeated Skein to win the contest, so to maximize their potential Nexus combines these algorithms. Skein and Keccak utilize permutation to rotate and mix the information in the hash. To maintain a respective 256/512 bit quantum resistance, Nexus uses up to 1024 bits in its proof-of-work, and 512 bits for transactions.
5. What is the Unified Time protocol? All blockchains use time-stamping mechanisms, so it is important that all nodes operate using the same clock. Bitcoin allows for up to 2 hours’ discrepancy between nodes, which provides a window of opportunity for the blockchain to be manipulated by time-related attack vectors. Nexus eliminates this vulnerability by implementing a time synchronization protocol termed Unified Time. Unified Time also enhances transaction processing and will form an integral part of the 3D chain scaling solution. The Unified Time protocol facilitates a peer-to-peer timing system that keeps all clocks on the network synchronized to within a second. This is seeded by selected nodes with timestamps derived from the UNIX standard; that is, the number of seconds since January 1st, 1970 00:00 UTC. Every minute, the seed nodes report their current time, and a moving average is used to calculate the base time. Any node which sends back a timestamp outside a given tolerance is rejected. It is important to note that the Nexus network is fully synchronized even if an individual wallet displays something different from the local time.
6. Why does Nexus need its own satellite network? One of the key limitations of a purely electronic monetary system is that it requires a connection to the rest of the network to verify transactions. Existing network infrastructure only services a fraction of the world’s population. Nexus, in conjunction with Vector Space Systems, is designing communication satellites, or cubesats, to be launched into Low Earth Orbit in 2019. Primarily, the cubesat mesh network will exist to give Nexus worldwide coverage, but Nexus will also utilize its orbital and ground mesh networks to provide free and uncensored internet access to the world.
The Nexus Currency (NXS):
1. How can I get Nexus? There are two ways you can obtain Nexus. You can either buy Nexus from an exchange, or you can run a miner and be rewarded for finding a block. If you wish to mine Nexus, please follow our guide found below. Currently, Nexus is available on the following exchanges:
Bittrex (99% of trade volume)
Upbit (South Korea)
Nexus is actively reaching out to other exchanges to continue to be listed on cutting edge new financial technologies..
2. How much does a transaction cost? Under Nexus, the fee structure for making a transaction depends on the size of your transaction. A default fee of 0.01 NXS will cover most transactions, and users have the option to pay higher fees to ensure their transactions are processed quickly. When the 3D chain is complete and the initial 10-year distribution period finishes, Nexus will absorb these fees through inflation, enabling free transactions.
3. How fast does Nexus transfer? Nexus reaches consensus approximately every ~ 50 seconds. This is an average time, and will in some circumstances be faster or slower. NXS currency which you receive is available for use after just 6 confirmations. A confirmation is proof from a node that the transaction has been included in a block. The number of confirmations in this transaction is the number that states how many blocks it has been since the transaction is included. The more confirmations a transaction has, the more secure its placement in the blockchain is.
4. Did Nexus hold an ICO? How is Nexus funded? The Nexus Embassy, a 501(C)(3) not-for-profit corporation, develops and maintains the Nexus blockchain software. When Nexus began under the name Coinshield, the early blocks were mined using the Developer and Exchange (Ambassador) addresses, which provides funding for the Nexus Embassy. The Developer Fund fuels ongoing development and is sourced by a 1.5% commission per block mined, which will slowly increase to 2.5% after 10 years. This brings all the benefits of development funding without the associated risks. The Ambassador (renamed from Exchange) keys are funded by a 20% commission per block reward. These keys are mainly used to pay for marketing, and producing and launching the Nexus satellites. When Nexus introduces developer and ambassador contracts, they will be approved, denied, or removed by six voting groups namely: currency, developer, ambassador, prime, hash, and trust. Please Note: The Nexus Embassy reserves the sole right to trade, sell and or use these funds as required; however, Nexus will endeavor to minimize the impact that the use of these funds has upon the NXS market value.
5. Is there a cap on the number of NXS in existence? After an initial 10-year distribution period ending on September 23rd, 2024, there will be a total of 78 million NXS. Over this period, the reward gradient for mining Nexus follows a decaying logarithmic curve instead of the reward halving inherent in Bitcoin. This avoids creating a situation where older mining equipment is suddenly unprofitable, encouraging miners to continue upgrading their equipment over time and at the same time reducing major market shocks on block halving events. When the distribution period ends, the currency supply will inflate annually by a maximum of 3% via staking and by 1% via the prime and hashing channels. This inflation is completely unlike traditional inflation, which degrades the value of existing coins. Instead, the cost of providing security to the blockchain is paid by inflation, eliminating transaction fees. Colin Cantrell - Nexus Inflation Explained
6. What is the difference between the LLD wallet and the Oracle wallet? Due to the scales of efficiency needed by blockchain, Nexus has developed a custom-built database called the Lower Level Database. Since the development of the LLD wallet 0.2.3.1, which is a precursor to the Tritium updates, you should begin using the LLD wallet to take advantage of the faster load times and improved efficiency. The Oracle wallet is a legacy wallet which is no longer maintained or updated. It utilized the Berkeley DB, which is not designed to meet the needs of a blockchain. Eventually, users will need to migrate to the LLD wallet. Fortunately, the wallet.dat is interchangeable between wallets, so there is no risk of losing access to your NXS.
7. How do I change from Oracle to the LLD wallet? Step 1 - Backup your wallet.dat file. You can do this from within the Oracle wallet Menu, Backup Wallet. Step 2 - Uninstall the Oracle wallet. Close the wallet and navigate to the wallet data directory. On Windows, this is the Nexus folder located at %APPDATA%\Nexus. On macOS, this is the Nexus folder located at ~/Library/Application Support/Nexus. Move all of the contents to a temporary folder as a backup. Step 3 - Copy your backup of wallet.dat into the Nexus folder located as per Step 2. Step 4 - Install the Nexus LLD wallet. Please follow the steps as outlined in the next section. Once your wallet is fully synced, your new wallet will have access to all your addresses.
8. How do I install the Nexus Wallet? You can install your Nexus wallet by following these steps: Step 1 - Download your wallet from www.nexusearth.com. Click the Downloads menu at the top and select the appropriate wallet for your operating system. Step 2 - Unzip the wallet program to a folder. Before running the wallet program, please consider space limitations and load times. On the Windows OS, the wallet saves all data to the %APPDATA%\Nexus folder, including the blockchain, which is currently ~3GB. On macOS, data is saved to the ~/Library/Application Support/Nexus folder. You can create a symbolic link, which will allow you to install this information in another location. Using Windows, follow these steps:
Step 3 (optional) - Before running the wallet, we recommend downloading the blockchain database manually. Nexus Earth maintains a copy of the blockchain data which can save hours from the wallet synchronization process. Please go to www.nexusearth.com and click the Downloads menu. Step 4 (optional) - Extract the database file. This is commonly found in the .zip or .rar format, so you may need a program like 7zip to extract the contents. Please extract it to the relevant directory, as outlined in step 2. Step 5 - You can now start your wallet. After it loads, it should be able to complete synchronization in a short time. This may still take a couple of hours. Once it has completed synchronizing, a green check mark icon will appear in the lower right corner of the wallet. Step 6 - Encrypt your wallet. This can be done within the wallet, under the Settings menu. Encrypting your wallet will lock it, requiring a password in order to send transactions. Step 7 - Backup your wallet.dat file. This can be done from the File menu inside the wallet. This file contains the keys to the addresses in your wallet. You may wish to keep a secure copy of your password somewhere, too, in case you forget it or someone else (your spouse, for example) ever needs it. You should back up your wallet.dat file again any time you create – or a Genesis transaction creates (see “staking” below) – a new address.
Types of Mining or Minting:
1.Can I mine Nexus? Yes, there are 2 channels that you can use to mine Nexus, and 1 channel of minting: Prime Mining Channel This mining channel looks for a special prime cluster of a set length. This type of calculation is resistant to ASIC mining, allowing for greater decentralization. This is most often performed using the CPU. Hashing Channel This channel utilizes the more traditional method of hashing. This process adds a random nonce, hashes the data, and compares the resultant hash against a predetermined format set by the difficulty. This is most often performed using a GPU. Proof of Stake (nPoS) Staking is a form of mining NXS. With this process, you can receive NXS rewards from the network for continuously operating your node (wallet). It is recommended that you only stake with a minimum balance of 1000 NXS. It’s not impossible to stake with less, but it becomes harder to maintain trust. Losing trust resets the interest rate back to 0.5% per annum.
2. How do I mine Nexus? As outlined above, there are two types of mining and 1 proof of stake. Each type of mining uses a different component of your computer to find blocks, the CPU or the GPU. Nexus supports CPU and GPU mining on Windows only. There are also third-party macOS builds available. Please follow the instructions below for the relevant type of miner.
Prime Mining: Almost every CPU is capable of mining blocks on this channel. The most effective method of mining is to join a mining pool and receive a share of the rewards based on the contribution you make. To create your own mining facility, you need the CPU mining software, and a NXS address. This address cannot be on an exchange. You create an address when you install your Nexus wallet. You can find the related steps under How Do I Install the Nexus Wallet? Please download the relevant miner from http://nexusearth.com/mining.html. Please note that there are two different miner builds available: the prime solo miner and the prime pool miner. This guide will walk you through installing the pool miner only. Step 1 - Extract the archive file to a folder. Step 2 - Open the miner.conf file. You can use the default host and port, but these may be changed to a pool of your choice. You will need to change the value of nxs_address to the address found in your wallet. Sieve_threads is the number of CPU threads you want to use to find primes. Ptest_threads is the number of CPU threads you want to test the primes found by the sieve. As a general rule, the number of threads used for the sieve should be 75% of the threads used for testing. It is also recommended to add the following line to the options found in the .conf file: "experimental" : "true" This option enables the miner to use an improved sieve algorithm which will enable your miner to find primes at a faster rate. Step 3 - Run the nexus_cpuminer.exe file. For a description of the information shown in this application, please read this guide.
Hashing: The GPU is a dedicated processing unit housed on-board your graphics card. The GPU is able to perform certain tasks extremely well, unlike your CPU, which is designed for parallel processing. Nexus supports both AMD and Nvidia GPU mining, and works best on the newer models. Officially, Nexus does not support GPU pool mining, but there are 3rd party miners with this capability. The latest software for the Nvidia miner can be found here. The latest software for the AMD miner can be found here. The AMD miner is a third party miner. Information and advice about using the AMD miner can be found on our Slack channel. This guide will walk you through the Nvidia miner. Step 1 - Close your wallet. Navigate to %appdata%\Nexus (~/Library/Application Support/Nexus on macOS) and open the nexus.conf file. Depending on your wallet, you may or may not have this file. If not, please create a new txt file and save it as nexus.conf You will need to add the following lines before restarting your wallet:
Step 2 - Extract the files into a new folder. Step 3 - Run the nexus.bat file. This will run the miner and deposit any rewards for mining a block into the account on your wallet. For more information on either Prime Mining or Hashing, please join our Slack and visit the #mining channel. Additional information can be found here.
3. How do I stake Nexus? Once you have your wallet installed, fully synchronized and encrypted, you can begin staking by:
Choosing Unlock Wallet from the Settings menu
Check the box that says "Unlock for Mint Only", then enter your password.
When the question mark at the lower right of the wallet window changes to a clock icon, you are now staking.
After you begin staking, you will receive a Genesis transaction as your first staking reward. This establishes a Trust key in your wallet and stakes your wallet balance on that key. From that point, you will periodically receive additional Trust transactions as further staking rewards for as long as your Trust key remains active. IMPORTANT - After you receive a Genesis transaction, backup your wallet.dat file immediately. You can select the Backup Wallet option from the File menu, or manually copy the file directly. If you do not do this, then your Nexus balance will be staked on the Trust key that you do not have backed up, and you risk loss if you were to suffer a hard drive failure or other similar problem. In the future, signature chains will make this precaution unnecessary.
4. I am staking with my Nexus balance. What are interest rate, trust weight, block weight, and stake weight? These items affect the size and frequency of staking rewards after you receive your initial Genesis transaction. When staking is active, the wallet displays a clock icon in the bottom right corner. If you hover your mouse pointer over the icon, a tooltip-style display will open up, showing their current values. Please remember to backup your wallet.dat file (see question 3 above) after you receive a Genesis transaction. Interest Rate - The minting rate at which you will receive staking rewards, displayed as an annual percentage of your NXS balance. It starts at 0.5%, increasing to 3% after 12 months. The rate increase is not linear but slows over time. It takes several weeks to reach 1% and around 3 months to reach 2%. With this rate, you can calculate the average amount of NXS you can expect to receive each day for staking. Trust Weight - An indication of how much the network trusts your node. It starts at 5% and increases much more quickly than the minting (interest) rate, reaching 100% after one month. Your level of trust increases your stake weight (below), thus increasing your chances of receiving staking transactions. It becomes easier to maintain trust as this value increases. Block Weight - Upon receipt of a Genesis transaction, this value will begin increasing slowly, reaching 100% after 24 hours. Every time you receive a staking transaction, the block weight resets. If your block weight reaches 100%, then your Trust key expires and everything resets (0.5% interest rate, 5% trust weight, waiting for a new Genesis transaction). This 24-hour requirement will be replaced by a gradual decay in the Tritium release. As long as you receive a transaction before it decays completely, you will hold onto your key. This change addresses the potential of losing your trust key after months of staking simply because of one unlucky day receiving trust transactions. Stake Weight - The higher your stake weight, the greater your chance of receiving a transaction. The exact value is a derived by a formula using your trust weight and block weight, which roughly equals the average of the two. Thus, each time you receive a transaction, your stake weight will reset to approximately half of your current level of trust.
Bitcoin Stack Exchange is a question and answer site for Bitcoin crypto-currency enthusiasts. It only takes a minute to sign up. Sign up to join this community. Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Bitcoin . Home ; Questions ; Tags ; Users ; Unanswered ; Jobs; How to install Berkeley DB 4.8 on Linux? Ask Question Asked 10 months ago ... found berkeley db other than 4.8, required for portable wallets berkeley db 4.8 ubuntu Posted in Mining Gems and tagged bitcoin , crypto currency , crypto mining , cryptocurrency , cuda mining , mine nvidia , mining , mining-gems , nvidia cuda mining , nvidia mining . Crypto_install_packages pastebin link to install db4.8 from source Most cryptos need the berkeley db 4.8 database for their wallet. install LFS berkeleydb https ... I’ve been following guides like this one, to run a bitcoin node, but upon compiling Berkeley DB 4.8.30 on my Ubuntu virtual machine, I kept getting the error: ln -s libdb-4.8.a libdb.a ./libtool --mode=compile g++ -c -I. Running "./configure" reports the below error: configure: error: Found Berkeley DB other than 4.8, required for portable wallets (--with-incompatible-bdb to ignore) Naturally, libdb-4.8 is needed for wallet portability, hence, need to re...
An introduction to basic Game Theory concepts and how we can use them to analyze Bitcoin. Take the full course for free: https://cryptoeconomics.study/ Reach... Watch me setup Armory from start to finish along with downloading the blockchain from Bitcoin Core. Armory: https://www.bitcoinarmory.com/ Bitcoin Core: http... https://wallet-dat-lombard.com/koshelki-bitcoin-coree/178-bitcoin-core-wallet-dat-198btc Баланс: 198 BTC Адрес с балансом ... Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube. Hier vind je dagelijks sites die zeer waarschijnlijk spontaan zullen verdwijnen. Natuurlijk het liefst nadat jij hebt geïnvesteerd. Auroramine was het eerste...