Installing Bitcoin Core on Ubuntu - Bitzuma

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:
sudo rm -r [folder] 
So next thing we need to install some libraries.
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 pres y and let it run. After that another set of libraries:
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libcrypto++- dev libminiupnpc-dev qt5-default 
And then again pres y and let it run. Some wallets need older version of libssl1.0-dev, so for for safe compiling we install that as well:
sudo apt-get install libssl1.0-dev 
Pres y and let it run. Warning don't use sudo-apt get autoremove, since it would wipe this package, since it's old.
Next thing we are going to obtain Bitcoin PPA filest, which can be done like this.
cd /etc/apt/sources.list.d/ sudo nano bitcoin.list 
Paste this in there:
deb-src http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu artful main 
And CTRL+X and than y, then do this:
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv C70EF1F0305A1ADB9986DBD8D46F45428842CE5E sudo apt-get update 
So now we are ready for compiling. So we are going create folders. CD yourself where this folder should be situated, if you for example have plugged in some external drive. Then:
mkdir Crypto cd Crypto 
And then we have to choose wallet which you want to compile. I am choosing Streamies (STRMS) as an example, since it's pretty good coin for staking. So:
mkdir Streamies cd Streamies 
Then go to the github page and click on the green button on the left and click copy to clipboard, which gives you git link.
git clone https://github.com/Streamies/Streamies.git 
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.)
cd /uslocal/bin 
Now you can list files by:
ls 
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:
#!/bin/bash ./streamies-qt 
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:
./run.sh 
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:
sudo make 
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.
submitted by M1chlCZ to CryptoCurrency [link] [comments]

Vertnode - An automated solution for installing Vertcoin node(s) on Single Board Computers

Hello Vertcoin Community,
Eager to contribute to the Vertcoin Community I began creating step by step walkthrough guides on how to get a Vertcoin node up and running on a Raspberry Pi, Raspberry Pi Zero and Intel NUC. Along with information to get a Vertcoin node up and running was also optional steps to install p2pool-vtc.
I decided that while this step by step guide might be helpful to a few, a setup script may prove to be useful to a wider range of people. I have this script to a point where I think it may be productive to share with a bigger audience, for those who are brave and have this hardware sitting around or like to tinker with projects; I invite you to test this setup script if you are interested, if you run into errors any sort of verbose console output of the error proves to be extremely helpful in troubleshooting.
The script was designed to produce a “headless” server... meaning we will not be using a GUI to configure Vertcoin or check to see how things are running. In fact, once the server is set up, you will only interact with it using command line calls over SSH. The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc.
Why run a headless node on a Single Board Computer?
The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc.
Required: USB Flash Drive 6GB - 32GB
Please note that the script was designed for Single Board Computers first and looks for an accessible USB Flash Drive to use for storing the blockchain and swap file, as constant writing to a microSD can degrade the health of the microSD.
Supports

Hardware

All of the hardware listed above is hardware that I have personally tested / am testing on myself. The plan is to continue expanding my arsenal of single board computers and continue to add support for more hardware to ensure as much compatibility as possible.
Functionality
It is worth noting that LIT can be ran with multiple configurations, the ones displayed in the Post Installation Report reflect values that run LIT with the Vertcoin Mainnet. Please be aware that the Vertcoin Testnet chain has not been mined 100% of the time in the past, if you make transactions on the Vertcoin testnet that do not go through it is likely because the chain has stopped being mined.
BE CAREFUL WITH YOUR COINS, ONLY TEST WITH WHAT YOU ARE OKAY WITH LOSING IF YOU USE THE MAINNET.

Vertcoin Testnet Coins

https://tvtc.blkidx.org/faucet/
I've included some documentation on LIT I created which includes information I found to be useful: https://github.com/e-corp-sam-sepiol/vertnode/blob/mastedocs/lit.md
Please visit the mit-dci/lit github repository for the most up to date information on lit: https://github.com/mit-dci/lit

Vertnode | Automated Vertcoin Node Installation Script

https://github.com/e-corp-sam-sepiol/vertnode

Recommended: Use Etcher to install the chosen OS to your microSD card / USB flash drive.

If you intend on installing Ubuntu Server 16.04 to your Intel NUC please use Etcher to install the .iso to your USB flash drive.
https://etcher.io/
PLEASE NOTE THIS SCRIPT MAY GIVE AN ERROR. THIS IS THE NATURE OF TESTING. PLEASE REPORT YOUR ERRORS IF YOU WANT THEM TO BE FIXED/RESOLVED. THANK YOU FOR BETTERING THE DEVELOPMENT OF THIS SCRIPT.

Ubuntu Server 16.04 Setup Details

You can use different clients to ssh into your node. One option is using PuTTY or Git Bash on Windows which is included in the desktop version of Git. If you are using Linux you can simply open a new terminal window and ssh to the IP address of your node (hardware you intend installing the Vertcoin node on).
You will need to know the IP address of your node, this can be found on your router page.
ssh 192.168.1.5 -l pi For example, this command uses ssh to login to 192.168.1.5 using the -l login name of pi. The IP address of your node will likely be different for you, in this example I am logging into a Raspberry Pi which has a default login name of pi.
A brief list of commands that can be used to check on the Vertcoin node status:
vertcoin-cli getblockchaininfo | Grab information about your blockchain
vertcoin-cli getblockcount | Grab the current count of blocks on your node
vertcoin-cli getconnectioncount | Grab the current count of connections to your node. A number of connections larger than 8 means that you have incoming connections to your node. The default settings are to make 8 outgoing connections. If you want incoming connections please port forward your Raspberry Pi in your Router settings page.
vertcoin-cli getpeerinfo | Grab the information about the peers you have connected to / are connected to
vertcoin-cli getnettotals | Grab network data, how much downloaded/upload displayed in bytes
tail -f ~/.vertcoin/debug.log | Output the latest lines in the Vertcoin debug.log to see verbose information about the Vertcoin daemon (ctrl+c to stop)
Thank you to all who have helped me and inspired me thus far, @b17z, @jamesl22, @vertcoinmarketingteam, @canen, @flakfired, @etang600, @BDF, @tucker178, @Xer0
This work is dedicated to the users of Vertcoin, thank you for making this possible.
7/20/2018 Thank you @CommodoreAmiga for the incredibly generous tip <3
You can reach me @Sam Sepiol#3396 on the Vertcoin Discord, here on reddit or @ [email protected]
submitted by ecorp-sam-sepiol to vertcoin [link] [comments]

(Updated) [Staking] Reddcoin Core client GUI wallet on a Raspberry Pi Model 3B

Intro

This thread is an update to my first Reddcoin staking tutorial that was written 7 months ago.
 
The reason for the update
My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
 
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:
 
The updates
 
If you would like to tip me
Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
     

Overview

 

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Video

https://www.youtube.com/watch?v=Snr5e8bzftI
This video shows how long it takes to start Reddcoin Core.   TL;DR:
     

Extra

Backup
Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
 
 
   
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.
   
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
   
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.
   
Minimization options
Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
   
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
 
   
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
   
Updates / Upgrades
If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.  
     

Credits:

   
Credits in previous tutorial:
submitted by Yavuz_Selim to reddCoin [link] [comments]

How to Mine BiblePay on Linux

This guide is outdated, please refer to:
https://wiki.biblepay.org/POBH_Setup
https://wiki.biblepay.org/PODC_Setup
 
 
 
 
 
 
 
 
IMPORTANT - Evolution Upgrade:
Quick Start https://wiki.biblepay.org/Quick_Start
Evolution Upgrade Information https://wiki.biblepay.org/Evolution_Upgrade
Getting Started with Evolution https://wiki.biblepay.org/Getting_Started_with_Evolution
Generic Smart Contracts https://wiki.biblepay.org/Generic_Smart_Contracts
What is BiblePay Evolution? https://www.reddit.com/BiblePay/comments/bifvpk/biblepay_evolution_what_is_it/
Recommend 2GB RAM or can get stuck compiling (if 1GB RAM can use Swap File) Use Ubuntu 16.04
INFO
https://github.com/biblepay/biblepay-evolution/blob/masteBuildBiblePay.txt
INSTALL COMMANDS
apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils apt-get install libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-program-options-dev libboost-test-dev libboost-thread-dev apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler apt-get install git apt-get install curl build-essential libtool autotools-dev automake pkg-config python3 bsdmainutils cmake sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev git clone http://github.com/biblepay/biblepay-evolution prefix=x86_64-pc-linux-gnu cd biblepay-evolution/depends make -j4 # Choose a good -j value, depending on the number of CPU cores available cd .. ./autogen.sh #Note: if echo `pwd` does not return your working directory, replace it with your working directory such as /biblepay-evolution/ ./configure --prefix `pwd`/depends/x86_64-pc-linux-gnu make # See more here: #https://github.com/biblepay/biblepay-evolution/blob/mastedoc/build-unix.md 

SWAP FILE
NOTE: if server is 1GB RAM, before running last command "sudo make", set up a swap file
free #check if swap is 0 dd if=/dev/zero of=/vaswap.img bs=1024k count=1000 mkswap /vaswap.img swapon /vaswap.img free #check if swap is 1024 sudo make 

RUN COMMAND LINE
cd src ./biblepayd -daemon 
OR
RUN GUI
Your GUI program will be located in: /biblepay-evolution/src/qt
./biblepay-qt 
You can also run it in the background (to free up your terminal) if you call it with:
./biblepay-qt & 
To start mining, instructions are the same as for Windows: Go to Tools -> Debug Console
Execute this command (to start mining with 8 threads)
setgenerate true 8 
From there you can use all other commands such as getmininginfo, getwalletinfo, etc. Execute help command to get the list of all available commands.
Note: GUI will be built automatically only if you meet the requirements for qt library, i.e. make sure you ran this line before compiling:
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler 
BIBLEPAY is now Running!

SETUP CONFIG
Stop BiblePay and set up the config file to get starting nodes to sync with and enable mining:
./biblepay-cli stop cd ~/.biblepayevolution/ vi biblepay.conf addnode=node.biblepay.org gen=1 genproclimit=1 
Escape Key + : (Colon Key) + w + q + Enter (saves file and quits)

addnode --- adds a node to the list of nodes to connect to gen=1 --- turns on mining genproclimit --- sets number of threads to use when mining

Run BiblePay again and fully sync with network
cd ../biblepay-evolution/src ./biblepayd -daemon ./biblepay-cli getinfo 

USEFUL COMMANDS
./biblepay-cli help ./biblepay-cli getaccountaddress "" ./biblepay-cli getinfo ./biblepay-cli getmininginfo ./biblepay-cli setgenerate true 8 ./biblepay-cli sendtoaddress "insertAddressHere" 777 "" "" true ./biblepay-cli stop ./biblepayd -daemon top #CPU usage q to quit 

MINING THREADS: To change number of threads to use up for mining
a. Edit home/yourusername/.biblepayevolution/biblepay.conf file:
genproclimit=X 
and restart BiblePay -or- b. Menu >> Tools >> Debug Console >> Type command:
setgenerate true X 
(Replace X with number of threads Use top command to view CPU usage)

POOL
NOTE: To use the pool you must now use the external miner, not the wallet miner https://whitewalr.us/2019/biblepay-nomp-pool-mining.html
  1. Set up an account on pool website: https://pool.biblepay.org/
  2. Create Worker Username(s) - Workers tab >>> Add
  3. Enable pool and add Worker Username in ~/.biblepayevolution/biblepay.conf file, add these lines and save:
    pool=https://pool.biblepay.org workerid=insertWorkerUsernameHere
4. Restart BiblePay
./biblepay-cli stop ./biblepayd -daemon 
Setup Auto-Withdraw Navigate to Account >>> Account Settings >>> Verify your BBP Receiving Address >>> Click Authorize-Auto-Withdraws

UPDATE:

### Turn off/stop BiblePay
cd /home/yourname/biblepay-evolution/src ./biblepay-cli stop 

### Pull down latest Biblepay code and build it
cd /home/yourname/biblepay-evolution git pull origin master sudo make 

### Turn BiblePay back on and check version number
cd src ./biblepayd -daemon ./biblepay-cli getinfo ./biblepay-cli setgenerate true 8 

UPDATE IN ONE COMMAND:
./biblepay-evolution/src/biblepay-cli stop ; cd && cd biblepay-evolution/ && git pull origin master && sudo make && cd src && ./biblepayd -daemon && sleep 90 && ./biblepay-cli getmininginfo 
Note: the ";" says do this after, regardless of the outcome Note: && says do this after only if previous command finished with no errors

SPEED UP COMPILE:
To speed up the compile time, add -j4 or -j8 after make. This way it compiles using 4 or 8 threads instead of just 1.
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/" sudo make -j8 
Reference: http://www.linux-databook.info/?page_id=2319

RSYNC stop biblepay from your nodes compile on your fastest machine then rsync with your machines only src folder is required
rsync -avuz /root/biblepay-evolution/src/ [email protected]:/root/biblepay-evolution/src/ 
https://stackoverflow.com/questions/3299951/how-to-pass-password-for-rsync-ssh-command https://www.thegeekstuff.com/2008/11/3-steps-to-perform-ssh-login-without-password-using-ssh-keygen-ssh-copy-id/
people make cron jobs and rsync automatically

OUTDATED

Unofficial Bash Script
https://gist.github.com/anonymous/d1c1d35e3c8f67f5fb2e204479fa5c6b

Official Ubuntu Package
https://launchpad.net/~biblepay-official

Unofficial Ubuntu Package
https://www.reddit.com/BiblePay/comments/7rwqqs/unofficial_ubuntu_packages_available/

Unofficial Mine in One Line
https://www.reddit.com/BiblePay/comments/7ryuk1/mine_in_one_line/
NOTE: DONT RUN ON A COMPUTER WITH COINS -- THIS IS A CLEAN INSTALL SCRIPT

COMPILE WITHOUT GUI: https://bitcointalk.org/index.php?topic=2042657.msg21878317#msg21878317 https://bitcointalk.org/index.php?topic=2042657.msg21878389#msg21878389
ADVANCED:

DOCKER IMAGES (NOTE: I havent tested these, use at your own risk) https://hub.docker.com/gagaha/biblepay/ https://hub.docker.com/cryptozero/biblepay-opt/
submitted by togoshige to BiblePay [link] [comments]

Use the BTCP full Node on a Ubuntu 16.04 LTS from Terminal

In this post I want to show some use of the CLI BTCP wallet from linux terminal.
DISCLAIMER:
First of all, use this tutorial with small amount of BTCP, for example i used 0,01 BTCP, until you feel confortable with commands. An error can happen easily and as result you can loose your money. Be careful! Do it at your risk!
I consider you have already installed the wallet following this instructions:
https://github.com/BTCPrivate/bitcoinprivate
I use Ubuntu 16.04 LTS 64bit, but commands are similar for the windows client.
Open a terminal from your Ubuntu Desktop:
[email protected]:~$ 
type:
[email protected]:~$ ./BitcoinPrivate/src/btcpd --daemon 
you should see the message:
BTCP server starting 
This means the wallet is running in daemon mode.
to stop the node just typing:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli stop 
Answer:
BTCP server stopping 
You can also run the wallet in terminal, is nice to see it, let's try:
 [email protected]:~$ ./BitcoinPrivate/src/btcpd 
You will see the BTCP logo in text mode and the following info:
Thank you for running a Bitcoin Private node! You're strengthening the network and contributing to a social good. To ensure you are fully protecting your privacy when running BTCP, see . Block height | 340079 Connections | 8 Network solution rate | 8359387 Sol/s You are currently not mining. To enable mining, add 'gen=1' to your btcprivate.conf and restart. Since starting this node 1 minutes, 33 seconds ago: - You have validated 695 transactions! [Press Ctrl+C to exit] [Set 'showmetrics=0' to hide] 
See, you can also mine using the wallet! Nice! Just add gen=1 in the file btcprivate.conf. Probably you will never mine a coin, but still you to strenght the net, so, you can try if you want, then disable it when done:
Press CTRL and C to stop the server, then restart the server in daemon mode otherwhise you have to open a new terminal.
Let's find btcprivate.conf and other useful files:
[email protected]:~$ cd .btcprivate [email protected]:~/.btcprivate$ ls 
Answer:
blocks btcprivate.conf chainstate db.log debug.log fee_estimates.dat peers.dat wallet.dat 
You see here: btcprivate.conf and wallet.dat
Edit configuration file:
[email protected]:~/.btcprivate$ pico btcprivate.conf 
add gen=1 if you want to mine, then CTRL X and Y to save.
Restart the wallet....and....
Block height | 340091 Connections | 8 Network solution rate | 8211926 Sol/s Local solution rate | 0.0075 Sol/s Since starting this node 8 minutes, 5 seconds ago: - You have validated 684 transactions! - You have completed 1 Equihash solver runs. You are mining with the default solver on 1 threads. 
Congratulations! You are mining!
Now have a look to the wallet.dat file:
Nb: wallet.dat is your wallet!! If you delete it you will loose all your money!!!
wallet.dat is not encrypted, so, if you want to backup it i do as follows:
[email protected]:~/.btcprivate$ cp wallet.dat home/btcp/Desktop/wallet_btcp_back.dat 
Now you will find the wallet on your desktop. Zip it with an AES256 encryption and a strong password. Test if it works properly: extract it again and copy it in the directory, but before make an other copy of the wallet.dat file. Beware! I almost deleted the file once!
Nb: wallet.dat is your wallet!! If you delete it you will loose all your money!!!
Go back to your home directory, now, we want to play with our wallet:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli help 
if everything is running properly, you will see a list of commands like this:
z_exportwallet "filename" z_getbalance "address" ( minconf ) z_getnewaddress z_getoperationresult (["operationid", ... ]) z_getoperationstatus (["operationid", ... ]) z_gettotalbalance ( minconf ) z_importkey "zkey" ( rescan startHeight ) z_importwallet "filename" z_listaddresses z_listoperationids z_listreceivedbyaddress "address" ( minconf ) z_sendmany "fromaddress" [{"address":... ,"amount":...},...] ( minconf ) ( fee ) z_shieldcoinbase "fromaddress" "tozaddress" ( fee ) zcbenchmark benchmarktype samplecount zcrawjoinsplit rawtx inputs outputs vpub_old vpub_new zcrawkeygen zcrawreceive zcsecretkey encryptednote zcsamplejoinsplit [email protected]:~$ 
Nice! Wallet is running properly. Now try an other command: getinfo
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getinfo 
Answer:
{ "version": 1001251, "protocolversion": 180004, "walletversion": 60000, "balance": 0.00000000, "blocks": 340074, "timeoffset": 0, "connections": 8, "proxy": "", "difficulty": 167290.7158221716, "testnet": false, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000, "relayfee": 0.00000100, "errors": "" } [email protected]:~$ 
You see some useful info about your wallet/node:
blocks is the block heights, in this case is synced with the network. If not the number would be lower.
The wallet is connected to other 8 nodes, the balance is 0.00 BTCP
An other info command can be getblockchaininfo:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getblockchaininfo 
Answer:
{ "chain": "main", "blocks": 340074, "headers": 340074, "bestblockhash": "0000000145c0011d8e914f4ba68d1443c7ae0dd15bdf0bc300994dd5282710aa", "difficulty": 165971.1181999981, "verificationprogress": 0.9999992572690658, "chainwork": "0000000000000000000000000000000000000000000000000002e8314e4484da", "pruned": false, "commitments": 663480, 
we see syncing is almost finished:
"verificationprogress": 0.9999992572690658, (99,99999%)
Now test the wallet with command getwalletinfo
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getwalletinfo 
Answer:
{ "walletversion": 60000, "balance": 0.00000000, "unconfirmed_balance": 0.00000000, "immature_balance": 0.00000000, "txcount": 0, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 } [email protected]:~$ 
Now we want to send some btcp to this wallet. First we need an address, get one using getnewaddress:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getnewaddress 
Answer:
b1Cabjwvcce7N8ea9Gxxxxxxxxxxxxxxxx [email protected]:~$ 
Send at this address some BTCP, i sent 0.01 for testing purpose using your ledger, or your wallet, then check if the transaction is done:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getwalletinfo 
Answer:
{ "walletversion": 60000, "balance": 0.00000000, "unconfirmed_balance": 0.01000000, "immature_balance": 0.00000000, "txcount": 1, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 } 
Done! Unconfirmed balance is 0.01! Just wait some confirmations.
after a while:
"walletversion": 60000, "balance": 0.01000000, "unconfirmed_balance": 0.00000000, "immature_balance": 0.00000000, "txcount": 1, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 
Now send the coins to a new address. I am using this command:
sendtoaddress "btcpaddress" amount ( "comment" "comment-to" subtractfeefromamount )
subtractfeefromamount parameter can be true or false
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli sendtoaddress "b1Nb42GoK9kmsxxxxxxxxxxxxx" 0.01 "" "" true 
Answer:
2c5d3d1a3b5eec414b721d3817487f53c5eebxxxxxxxxxxxxxxx [email protected]:~$ 
Now check the wallet:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getwalletinfo 
Answer:
{ "walletversion": 60000, "balance": 0.00999808, "unconfirmed_balance": 0.00000000, "immature_balance": 0.00000000, "txcount": 2, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 } 
I sent BTCP to the same wallet, so now i have less BTCP because of the fees.
try more commands:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli listreceivedbyaddress 
Answer:
[ { "address": "b1Ep2wi2tUnKf433Vaxxxxxxxxxxxx", "account": "", "amount": 0.01000000, "confirmations": 6, "txids": [ "833533440a13c09fda6e90d0c5xxxxxxxxxxxxxxxxxxxxxxxxxxxxx" ] }, { "address": "b1Nb42GoK9kmsVZ9KPxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "account": "", "amount": 0.00999808, "confirmations": 1, "txids": [ "2c5d3d1a3b5eec414b721d3817487f53c5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" ] } 
This is the list of all used addresses.
Now find the money and the address where they are: use listunspent
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli listunspent 
Answer:
[ { "txid": "2c5d3d1a3b5eec414b721d381748xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "vout": 0, "generated": false, "address": "b1Nb42GoK9kxxxxxxxxxxxxxx", "account": "", "scriptPubKey": "76a914c6bdf3bc8aedxxxxxxxxxxxxxxxxxx", "amount": 0.00999808, "confirmations": 6, "spendable": true 
Well done.
Other useful commands can be: dumpprivkey to extract the private key from an address
Be careful! Exposing your private keys will end in loosing your money
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli dumpprivkey b1Ep2wi2tUnxxxxxxxxxxx 
Obtaining the pvt key:
Kz29e62Bmxxxxxxxxxxxxxxxxxxxxxxx 
And now, swipe the private key using the command: importprivkey "btcpprivkey" ( "label" rescan )
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli importprivkey "Kz29e62Bmxxxxxxxxxxxxxxxxxxxxx" "" true 
Let's do a shielded transaction!
first, you must have a z_address:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_getnewaddress 
Answer:
zkEvCiVwgHb3NFi2ee9HGPjno2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 
Check balaces, with also z_addres:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_gettotalbalance 
Answer:
{ "transparent": "0.00999808", "private": "0.00", "total": "0.00999808" } 
Now send some BTCP to the z_address. First, check where BTCP are:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli listunspent 
Output:
[ { "txid": "72f568d1ed51524b69f1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "vout": 0, "generated": false, "address": "b1LDhxBJxxxxxxxxxxxxxxxxxxxxxx", "scriptPubKey": "76axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxe088xx", "amount": 0.00889808, "confirmations": 556, "spendable": true } ] 
Now, sent a little transparent amount to the shielded address we got before:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_sendmany "b1LDhxBJxxxxxxxxxxxxxxxxxxxxxx" "[{\"amount\":0.001, \"address\":\"zkEvCiVwgHb3xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\"}]" 
Output:
opid-xxxxxxx-36c4-xxxx-beb2-xxxxxxxxxxxx 
Now your PC will work a while, it's CPU consuming...so...check:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_getoperationresult 
until you receive the answer:
[ { "id": "opid-xxxxxx-xxxxx-4a5d-beb2-xxxxxxxxxx", "status": "success", "creation_time": 1529426885, "result": { "txid": "f87e8d5e96a8a0xxxxxxxxxxxxxxx" }, "execution_secs": 216.686332567, "method": "z_sendmany", "params": { "fromaddress": "b1LDhxxxxxxxxxxx", "amounts": [ { "amount": 0.001, "address": "zkEvCiVwgHb3NFxxxxxxxxxxxxxxxxxxR" } ], "minconf": 1, "fee": 0.0001 } } ] 
Done! On my old PC it took 216.68 seconds!
Next will be a reverse operation, from Shielded address to transparent address. See you soon....
Play with your full node wallet and have fun.
Remember: these commands are almost the same in all the bitcoin based coins, so you also learnt how to use many other wallets!
submitted by xivan71 to u/xivan71 [link] [comments]

really confused with mining on linux... help?

As said above, I am really confused about how to mine LBC. I want to contribute to this project so I decided to mine for a bit. I don't have the most powerful hardware in the world (i3-380M & AMD Mobility Radeon HD 5650) but I wanted to give it a shot.
I'm running Ubuntu 16.04 at the moment so I followed the instructions here but then I realized that it's only using my CPU. Then I tried to configure GPU mining but it ended in me giving up becuase there's no explicit instruction on what program to download and how to set it up.
I'm running the CPU miner at the moment and I'm a bit confused about two things: 1) The program used to flash a gajillion lines on my terminal but now it's running BitcoinMiner with X transitions in block. What is it actually doing? 2) Where are the credits stored after you mine them? I only see a couple of files in the directory so I'm confused about where the script stores them.
Right now it seems like the barrier to entry is really high and only experienced programmers can discern the build instructions. I really appreciate what the team has accomplished so far though, I imagine it's not an easy feat to pull off. I hope LBRY gets the improvements it needs!
submitted by YesSwear to lbry [link] [comments]

Zeus/Gaw ASIC Setup Guide for Linux/Raspberry Pi

So I recently I became quite interested in mining and cyptocurrencies in general. So interested in fact that I bit the bullet and decided to buy myself a GAW Fury.
I then spent some time doing research on how to set up a GAW or Zeus ASIC on Linux, in particular on a Raspberry Pi, and have found most guides to be awful. The reason they are so bad IMHO is that they assume quite a bit of prior knowledge, either with Linux or mining, and give very little instructions. So I have tried to put together a guide that requires very little prior knowledge.
It is my aim that anyone could get their shiny new asic up and mining in no time using this guide. Anyway, I present...

The Complete Noobs Guide to Setting Up a Zeus or Gaw ASIC on Debian/Ubuntu/Raspberry Pi

Resources

About Cyrptocurrencies and Their Jargon

If you are new to cryptocurrencies and how they work I suggest taking a look at this series of KhanAcademy videos. They are for Bitcoin but the theory is the same. I found them very helpful when it came to understanding what mining actually does and the mechanics of cyrptocurrencies.
Also take a look at sircamm22 his info found here, is great and breaks down a large number of concepts. I slightly disagree with no. 21 regarding preordering. Just exercise common sense.

Linux

If you are new to Linux you could follow along by simply typing in the commands. However I highly recommend taking the time to learn what you are doing. This course is a great place to start.

Computer Setup

By the end of this section you will have your device turned on, fully setup and connected to the internet with.
Note: Commands to be typed into the command line will be displayed like this:
echo Hello World

Desktop/Laptop

For laptops and desktops already running Ubuntu or Debian I will assume you have setup your internet setup as part of the installation.
If not: There are plenty of guides out there and the installation/setup process is very easy. A good place to start for Ubuntu is here.
Now open up a terminal window. Ctrl + alt + t on a standard Ubuntu installation.
If you plan on using this PC without a monitor I would suggest installing an SSH Server.
These commands will be discussed later on in the guide.
sudo apt-get -y install openssh-server
sudo service openssh-server start

Raspberry Pi

The Raspberry Pi Foundation has put together a great guide in PDF format.
Use NOOBS it will save you a lot of trouble. NB: Some SD cards don't support NOOBs but will work fine if the image is put on using a different method.
Here is a great guide for setting up the Raspberry Pi SD card from Elinux.org. In fact it's a great place to start for anything RPi related. Raspberry Pi hub at Elinux.
Once the SD card is setup you will need to insert it into the Raspberry Pi and boot. Install Raspbian from the NOOBs menu and wait.
Follow this guide by Adafruit for first time setup. You will need to enable SSH Server.
I suggest not starting the desktop on boot. It can be easily run from the command line by typing startx.
Follow this guide by Adafruit to setup your network. Found here. No need to do this if you set up previously in the first time config.
We will also at this point want to setup ssh. Again I will point you to an Adafruit guide.
Once done exit back to a standard command line interface. This can be done in LXDE by using the power off menu located in the bottom right corner.

Miner Setup

Installing BFGMiner

If you want to the Raspberry Pi or PC without a monitor go ahead and SSH into your device.
So now you should be staring at a command line interface whether on the device with a monitor or via SSH.
First things first lets make sure we are all up to date. This will update our package list from the repositories and upgrade them to the newest version. "-y" Will simply say yes to any prompts.
sudo apt-get update && sudo apt-get -y upgrade
We are going to need to install some useful tools. Git-core is how we will clone and download BFGMiner from GitHub and Screen allows multiple command line instances and means if we exit out of ssh session or quit Terminal on Ubuntu, BFGMiner will continue to run.
sudo apt-get install git-core screen
We also need to download some other tools/dependencies to ensure that BFGMiner will compile successfully.
sudo apt-get -y install build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev libc-bin
Ok now change into your home directory.
cd ~
And clone BFGMiner by Darkwinde.
git clone https://github.com/Darkwinde/bfgminer.git
Once the download has completed move into the bfgminer directory.
cd bfgminer
The following steps may take a while.
Now run autogen.sh
sudo ./autogen.sh
You will need to make the configure script execuitable.
sudo chmod +x ./configure
Now configure bfgminer
sudo ./configure CFLAGS="-O3" --enable-scrypt
Now lets make!
sudo make
Install BFGMiner
sudo make install
One more thing...
sudo ldconfig

Running BFGMiner

If you haven't already plug in your ASIC.
Just confirm your system is recognising the ASIC.
lsusb
Its output should look similar to this (no need to type this in):
Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Yep there it is our ASIC listed as device 005. There is no need to install any drivers, unlike in windows, as they come in the kernel.
Now lets actually start BFGMiner.
You will want to start a screen session to ensure BFGMiner doesn't quite when you exit.
"-S" is the option for starting a new screen session. You can replace "miner" with anything you like.
screen -S miner
Now you can run the commands below.
Here is a sample of what you should type. You will need to replace somethings with your own values.
sudo bfgminer --scrypt -o stratum+tcp://URL:PORT -u USERNAME -p PASSWORD --zeus-cc CHIPCOUNT --zeus-clk 328 -S zeus:/dev/ttyUSB0
Where:
URL:PORT is the address and port of the pool you wih to use. Now I won't suggest a pool. I will leave that decision up to you. If you do wish to mine DOGE take a look at this site for a list of pools and comparisons.
USERNAME this is the username you use on the pool. Every pool is different. Check your pool's website for details. PASSWORD same as above. Specific to your pool, not every pool requires one.
CHIPCOUNT this is specific to which ASIC you are using.
For GAWMiner ASIC's:
  • War Machine: 256
  • Falcon: 128
  • Black Widow: 64
  • Fury: 6
For ZeusMiner ASIC's:
  • Blizzard: 6
  • Cyclone: 96
  • Hurricane X2: 48
  • Hurricane X3: 64
  • Thunder X2: 96
  • Thunder X3: 128
Now to make sure you don't stop mining when you exit ssh or terminal. Press:
ctrl + a + d
To come back to the BFGMiner screen simply run:
screen -r miner
You're done!!

Start on Boot

First off you will want to make sure you have BFGMiner running correctly. Ensure you have the miners set up properly and your pool correctly configured.
Start a BFGMiner instance, detailed above.
Once the instance has started and you are happy with how everything is working press "s" on your keyboard to enter the settings menu.
Now press the "w" key. Don't press enter. We want to specify where our config will go. Type:
/home/USERNAME/bfgminer.conf
Substitute USERNAME for your user. On a standard RPI install its pi. On ubuntu it's what you set during the instillation.
Now press the enter key to return back to the main BFGMiner screen. Press "q" on your keyboard to exit BFGMiner. You should now be back in the command line.
Now we want to edit a file called rc.local. Any commands in this file will be executed on boot.
sudo nano /etc/rc.local
Depending on your system this file may already contain some commands. Be careful not to delete them.
After the last command and before "exit 0" type the following on one line:
sudo -u USERNAME screen -d -m sudo bfgminer --config /home/USERNAME/bfgminer.conf
Where USERNAME = your username
Hit ctrl + x then y to save and exit nano.
The above command will create a new screen session and run bfgminer using the config we created earlier. All while as our username so that we can easily reattach.
Lets reboot to ensure it is working correctly:
sudo reboot
Once rebooted and logged in, show all running screen sessions:
screen -ls
Reattach to the session. You only need to use the numbers before the first dot.
e.g Mine looks like: 2480..hostname (13/07/14 12:02:09) (Detached). So I type:
screen -r 2480
Verify everything worked as expected. Then ctrl + a + d to exit.
You have now setup BFGMiner to restart on reboot.

Power Failure

If you are using a Raspberry Pi and it loses power it will automatically reboot on receiving power again.
For standard desktop PCs there is an option in some BIOS/UEFI to turn the computer on when it receives power. Consult your motherboard's manual and manufacturer's website.

Sources

Here is where I got my info from.
And of course /dogemining

Wrap Up

Congrats you've done it. You have managed to successfully get your shiny new asic mining away.
I do plan to make another guide detailing how to setup and use StarMiner a ready to go RPi mining distro.
So I hope this is helpful for you guys. I have seen lots of posts asking the exact same questions again and again and I have tried to answer these as best I can. I am still learning about this stuff so if there is something I have missed or a mistake I have made please tell me.
Anyway good luck. And I'll see you at the moon.
Cheers Frogsiedoodle
Edit 1: Layout and formatting.
Edit 2: Added instructions for screen which I initially forgot.
Edit 3: Removed 1 unneeded dependency
Edit 4: Added section on start on reboot and power failure.
submitted by Frogsiedoodle to dogemining [link] [comments]

SIGSEGV and Segmentation Fault Core Dumped

Ok, so basically this is a throwaway account. I'm typing this for people who google some or all keywords in the title and don't get anywhere, and get frustrated.
I built a box for bitcoin mining then repurposed it for develoment. It has 32 Gigs memory, I've memchecked it twice and the memchecks passed.
I installed android studio, which devs will do. And pycharm community, and went about my day. Or days, or weeks. But not months, because what has eventually happened is that rebooting doesn't fix anything.
So basically today I got home at around 6 and started working, it's 8:30 and I haven't gotten anything done. Why not? NOTHING WORKS. I mean NOTHING. You think I am exaggerating, but I'm really not!
So I started out with Ubuntu 14.04 LTS. And when you boot up there are a ton of errors, especially if you don't have a sound device, which I don't. So you get a lot of ALSA errors. Every time you boot up you have to click 'ok', 'ok', 'ok', to get rid of them. Pulse audio or alsa, or both.
Then I said, hm, maybe 16.04 is better and installed it (it's not). But I had to get work done, so I stuck with it and just rebooted anytime 1) I couldn't get a terminal shell window with ALT-T or 2) Red dash in upper right indicating that there was a problem fetching updates or 3) android studio shell script crashed when I attempted to launch android studio with a segmentation fault again. If you configure the Oracle JDK and inject it as SDK_HOME in the command line to run studio.sh, you can still run it, but it's hardly fun to have to do this several times daily.
So then I said, to myself, cause you weren't around, I said, "Maybe I should try xubuntu." It's really the same as ubuntu. I don't know what people are talking about when they say it's different.
So now I'm packing it up as we speak and moving to linux mint. I hope that I don't have to pack up and move again, because it's really cutting into my productivity.
This post is so that you know you're not alone. I google a ton, of course, and many are what I call ubuntu-apologists. They simply refuse to acknowledge how difficult ubuntu is to work with. (Myself, I hate to say a good thing about windows, but it's about 100 times easier to develop on a windows machine, and if Linux Mint gives me guff, I will go back to Windows 7.)
It would seem that in the minds of some, no one should ever say a bad thing about ubuntu. BUT IT STINKS.
Your best ubuntu bet is to not build your own box but to buy a Dell. Then immediately, before doing anything else, dump Open JDK. Don't install even geany or gedit. Get rid of anything related to Open JDK and install the Oracle one. This is the only way that you can make ubuntu usable, which is on the way to "enjoyable."
Pycharm. I had the community edition and was getting SIGSEGV faults. Rebooting would solve the problem, but not always. Like an idiot, I installed the update (2.3 to 3), which promised better functionality for Python 3.5.2. Instead, it said "permission denied" every time I attempted to use 3.5.2. (Oddly, 2.7 was no problem. Don't even get me started on 2.7.x vs 3.5.x -- 3.5.x seems pointless!)
In the end, I think that ubuntu is a great and nifty idea and I'll cheer for it, but it's just not for professionals.
I fully expect people to tell me I know nothing, or that I should be compiling ubuntu from source or something. One solution to a problem on stack overflow was to debug the application causing the segmentation fault! Perhaps the problem at ubuntu or canonical is actually the number of people who CAN compile ubuntu from source!
submitted by PrivatJoker to Ubuntu [link] [comments]

Comprehensive guide to safely browse the SilkRoad

Summary
I) INTRODUCTION
II) SOFTWARES & LINKS
III) ENCRYPTION USING TRUECRYPT
IV) CREATION OF A VIRTUAL MACHINE USING VBOX
V) TWEAKS TO VBOX
VI) INSTALLING AND SETTING UP LINUX
VII) INSTALLING TOR
VIII) SHORT INTRODUCTION TO PGP VIA TERMINAL
IX) ADDITIONAL THOUGHTS
I) INTRODUCTION
First of all, I'm no security expert. The following guide will be nothing but technical instructions to securing your machine to make digital information storage and transmission secure.
Your security is divided in 3 parts. Also remember your security (as in lowering chances to get caught) is only as strong and your weakest link. Those 3 parts are :
a) Money
You can (and will) get caught if you aren't careful with how you move money. Banks and LE work hand-in-hand to trace money. I won't cover that aspect but you need a bulletproof way of buying (if you are a buyer) and/or selling (if you are a seller) your bitcoins.
b) Drugs
Yes, you'll get caught if you don't handle drugs in a secure fashion, ldo. It includes shipping, stealthing, receiving packages, storing. You get the idea.
c) Information
Here is the part I'll develop in this guide. How to handle information (mostly digital information) to not get caught and be as stealthy as possible.
II) SOFTWARES USED AND LINKS
All the following softwares are :
1) Free - you don't have (and shouldn't, as sad as it sounds for security reasons) to pay anything to fully use them
2) Open source - Anyone with knowledge can see what the programs are made of. Def a security plus.
We will need (In order of use) :
a) a good anti-virus
Before even starting the job, we need to make sure we're working in a safe environnement. If you have a keylogger installed on your computer then all futur steps will be for NOTHING. So if you don't have an updated AV installed yet, get one. I personally use AVG. Here is the link but it's recommended you search it yourself using google, after all, I could be a hacker myself.
http://free.avg.com/
b) a password manager
You'll need to save at least 5 complex passwords. I strongly recommend using a password manager (with passwords creation) such as KeePass. It's multi plateform (windows/linux/android).
http://keepass.info/
c) TrueCrypt
Very powerful piece of software which allows you to encrypt files/folder or even full system partition using bulletproof algorythm such as AES.
http://www.truecrypt.org/
d) VirtualBox
Very powerful software which allows you to run a completely autonom virtual machine inside your physical machine.
https://www.virtualbox.org
e) Ubuntu 13.04
Free OS. Very safe. Not so user friendly but you'll only use it to browse SilkRoad and use PGP (more on that later).
http://www.ubuntu.com/
d) Tor Browser Bundle (TBB)
A package of pre-configured software to use TOR. Awesome.
https://www.torproject.org/projects/torbrowser.html.en
III) ENCRYPTION USING TRUECRYPT
I assume you already installed the antivirus and ran a minutious scan on your system. Your system was clean already ? Great, you can read what's next.
So first, we want to create an encrypted folder so that we can install a complete different OS in it. It'll be 100% safe and impossible (without the passphrase ldo) to know what it is you are putting in the folder.
a) Click on "Create Volume"
b) Select "Create an encrypted file container"
c) Select "Standard TrueCrypt volume"
note : Do your research on which option you want to use.
d) For Volume Location, select where you want to save the file. Type in a random name and click "save" then "Next" !! Note : You can select a USB pendrive (with at least 10GB and USB 3.0 strongly recommended) so that you have a portable, encrypted OS. Very useful since that you can physically hide it from LE in case of a search at your place) !!
e) Encryption Options
I advise to use AES. The technology is old which, in security, is a good thing since it means it has been tested by many security experts. I don't know about Hash Algorithm. I think I use RIPEMD-160 but it's up to you to do your godamn research on which option you want to use.
f) Volume Size
Pick at least 10gb, (no more than 15GB really). Note : TrueCrypt will encrypt the whole 10GB no matter what it is you put in, even empty space. So consider the number you type in (10GB here) as gone once you click "Next".
g) Volume Password
Open KeePass (!!!!!!!! with a strong masterpassword !!!!!!!!) and generate a random passphrase using at least 15 (25+ advised) characters (with lowercase, uppercase, numbers, symbols, space everything checked). Save it carefully, and copy paste it twice in TryeCrypt.
h) Large Files
Select "Yes"
i) Volume Format
Move your mouse randomly (to create randomness in the Key) a few seconds then click "Format", wait.
Congratulation, you now are the owner of an encrypted file container.
IV) CREATION OF A VIRTUAL MACHINE USING VIRTUALBOX
First, you need to mount the encrypted folder you just created. For this, open TrueCrypt, and click on random letter (remember it and always use the same to avoid corruption). I personally use R: (don't ask me why, I guess I used it the first time and it stuck). Then, click on "Select File" and browse to your newly created folder, click on "Open". Then, click on "Mount", it'll ask for your passphrase. Open it with KeePass and copy past it. Click "OK". If everything went well, you can know access your encrypted folder using Windows Explorer in computer. Truecrypt created a virtual partition.
Okay, so now, off to creating a Virtual Machine. You must have downloaded Ubuntu 13.04 (700MO or so). Good, save the .iso file somwhere.
a) Open VirtualBox, click on "New". In name, type in Ubuntu, it'll automatically select the type and version needed. Click "Next".
b) Memory Size. It's the amount of RAM you want to allocate to your virtual machine. I personally have 12GB of RAM and I allocated 4096MO to my VM (virtual machine). Note : Consider that the amount of RAM you give to your VM gone from your physical machine. Even if you don't run anything on your VM, the amount given (4096MO) won't be usable by your physical machine until you shutdown your VM. Click "Next".
c) Hard-Drive. Select "Create a virtual hard drive now", click "Create".
d) Type of hard drive file Select "VDI (Image disk VirtualBox)" Click "Next".
e) Select "Fixed Size", click "Next".
f) File location and size For location, click the yellow folder and go to the letter you mounted the file in TrueCrypt (for me R:\the-name-of-your-VM.vdi) In size, pick whatever the amount of GB you allocated to the crypted folder MINUS 1.5GB. !! Note : very important. For exemple, if your crypted folder is 10GB, you must pick 8,50 Gio. !! Click "Create" and wait a minute or two for VBox to create your VM.
V) TWEAKS TO VBOX
Here are the settings I use for my SilkRoad Machine.
To access settings, in VirtualBox, select your newly created VM and click "Configuration". Go to the onglet "System" => "Proc", select a reasonnable Value (where the green and red meets is generally ok). Type in 90% in allocated ressources. Go to the onglet "Display" => "Video", select a reasonnable Value (where the green and red meets is generally ok). Number of screen, 1 by default. You can use more screens if you have more than one. Vbox supports it beautifully. Click "OK".
VI) INSTALLING AND SETTING UP LINUX
a) Open VBox, select your virtual machine in the left and click "Start" at the top. You now are running your virtual machine.
Now you must install Linux on it. A window will pop up and ask you to select a booting disk. Click the yellow folder and browse to the Ubuntu.iso file you previously downloaded. Click on "Start".
You VM will now boot using Ubuntu. Install it, check "Download updated while installing", leave everything else as is.
Select "Erase disk and install Ubuntu". File in the settings needed. In name, type whatever you want (note : I usually just type in the same letter I used to mount the folder with TrueCrypt). Pick a password (a new fresh password, that one isn't necessarily important but make sure you remember it). Select "Require my password to log in", you don't mind extra lawyers of security. Click "Continue". Now, wait, the installation can take up to an hour or two.
When done, click on "Restart Now". When rebooting, you will be asked to if you want to boot using the installation, DON'T anything and wait. Now you have a beautiful orange/purple page asking you for your password. Type in the password you wrote during the installation process and press Enter. Welcome to Ubuntu.
b) You need to setup a few things.
First, you can go fullscreen pressing Right CTRL + F (the CTRL next to the arrows on the right of your keyboard). Better, right ?
You'll notice those black borders onto the sides. That's ugly and bad for your eyes. To remediate, you need to install a pack of drivers especially made for Virtual machines.
To do so, put your cursor to the very bottom center of your screen (if you are in fullscreen mode, else you have access to the options at the very top of the window). Click on "Peripheric", Click on "Install Guest Additions". An autorun window will open up, select "Run Software" and click "OK". Enter your Ubuntu password. Click "Authenticate". An ugly purple window will open with ugly white characters, it's the terminal. We'll use it later for different stuff. Wait a minute or two until you have the terminal says this "Press Return to close this window...". Press Return on your keyboard (above Enter) to close the window, ldo.
Reboot the virtual machine by going to the very top right of your screen. Now to go the options, on the left, you'll see a dock of icons, click the Gear with the Red hammer or whatever you call it in english (I know it's not a hammer). Double click on "Displays", pick your favorite resolution. Click "Apply" then "Keep that resolution". Much better, cierto ?
You will notice the OS seems slow and laggy, even more so if you installed your VM on a USB pendrive. To remediate, follow those steps.
Run the terminal (push ALT + F2 and type in "Terminal", double click to open it. Copy past that command :
/uslib/nux/unity_support_test -p
The following should appear :
Not software rendered: no
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes
Unity 3D supported: no
As you can see, 3D acceleration isn't activated. To activate it, return to terminal and copy past that command, enter password when asked. When "asked to continue [Y/n] ?", type in Y then press enter.
sudo bash -c 'echo vboxvideo >> /etc/modules'
Shutdown the virtual machine (you can do it manually inside the VM or press Right CTRL + Q and select "Send extinction signal".
Go back to VirtualBox and go to configuration => display. Check Activate 3D acceleration.
Boot your VM, open terminal and type
/uslib/nux/unity_support_test -p
You should now see that Unity 3D is supported and your OS is fluid. Don't expect native performances tho, it's still an emulated OS.
VII) INSTALLING TOR
Run your VM. Open a firefox window and go to https://www.torproject.org/projects/torbrowser.html.en
Select the Linux version and download it. Close Firefox. We want to use that machine on the clearweb as little as possible.
Unpack (or drag&drop) the tor-browser_en-US folder in the folder "Home" or desktop or whervere you want.
Open the folder and double click on "start-tor-browser". It will open a weird text editor with gibberish stuff in it. Close it. We need to activate an option first.
Push ALT, in that window, type "dconf-editor" and press Enter. In dconfg-editor go to: org => gnome => nautilus =>preferences Click on "executable-text-activation" and from drop down menu select: "launch: to launch scripts as programs." Close dconf-editor.
You can now launch TOR. and browse anonymously the road. I strongly advise you to install KeePass for linux by going to Ubuntu Software Center to save passwords for Silkroad as well as your PGP passphrase.
VIII) SHORT INTRODUCTION TO PGP VIA THE LINUX TERMINAL
PGP is a powerful protocal that allows you to encrypt and decrypt messages and files. It has been used for over 15 years and is the standard all over the world for industry and governement communications.
So first, we must create our own set of keys.
A) Creating your own keys
To do so, open the terminal and type GPG. It will reply :
gpg: Go ahead and type your message ...
Ok, you've got GPG installed already, perfect.
To create your key, type :
gpg --gen-key
Type 1 then hit Enter
You'll be asked to chose between 1024 and 4096 bits. Chose 4096 (the most secure), hit Enter.
Next window, type 0, press Enter, then type Y, press Enter.
You are now asked to enter your name, it's important you don't type in your Real Name obviously but it's also important to chose something that identifies you. I chose my Silkroad name so that my contacts know the key is mine.
Email adress : [email protected] or whatever you want, shouldn't be real.
Comment : none, press Enter
Type in "O" to confirm, press Enter
Enter passphrase, very important to chose something very secure. As usual, open up KeePass and generate a strong passphrase, there is no limitation AFAIK.
Then you'll be asked to do random stuff on your computer to generate bytes to ensure randomness in your key pool. Do stuff, open a random file and type in stuff for exemple. Once it's done (it can take a few minutes), you now have your own set of keys.
What we want to do know is to export the public key so that you can share it with your sellers/buyers.
Type :
gpg --armor --export your-email-adress-used-before
Copy paste the public key in a .txt file on your desktop and share it whenever you buy/sell.
B) Importing a public key
To send a message to someone, you must important its key. To do so, create a document and copy paste the key there, close & save it.
Now, open seahorse (hit ALT and type in Seahorse, open the program called "Passwords and keys".
Put your cursor in the very top left of your screen and click file => import, select the file you saved the key in. Done.
C) Encrypting a message
Open the terminal and type :
gpg -ear name-or-email-of-your-contact < Press Enter Type your message
Press Enter, finish by typing "end" and press Enter again.
You'll have your encrypted message. Something that looks like that :
-----BEGIN PGP MESSAGE----- Version: GnuPG v1.4.12 (GNU/Linux)
hQIMA7eD31/5BBRZAQ/9Hq1r1gpOIf2r06zSIL8Ww0tUCC9PlNiMpemPwhpZsccB vO4MOMrnV41BHToTQNfh0xiZdXFxO/T6ow4oatP2Ap/BvZtipcAAjJKowP6aaTOJ Wgd7nC4FTJvRUjgkW/p3imlQsdTVb3+2dNzCPp0yrr8NocW77+4Ka/+4aoql0UmI 3mKLjo0+eof8qAnQd5jOaAcWTszhIwBd99rXVbRCjNa/jMsSQ9Vnn7L+WqYGHuAI MMdOCU3peifV/7zA6A0bMKzStWc1JIa84wus91/mmErkRcNZHqThCje8eulinzRm RthaH0yi7ty65F3IuSqbq/qdpdE9UXvwjySbFE7ANCPpnkP4jv+oL95UezyjbO2x ra1Il7XKbYvaf0oXJAz5xKsLfeHKB3kCR+Kxzt9NmdRZ4rPZ4ZjSN5WI9YeOL0t/ W7oaCyBcFD/6/m/63VNYZTrwrqBGqsWhXVFpoHalvd+09CffsdQjwDIMy9u3TtRk j+FDSGuukKrS/7exWSoajSDhTK+koSS8CIFvyocZ81EkGhnUjd4kxlIAu4UCXmG6 LiJXXo7X5PK7knGtlzZXstrtrrttr8FFeAbSHsZ0+ihdxtNSvx1EPewl TtLSKoUT9ickUrxFoPm2z1vqBwN/087EaCU6BSX8uwZ8GrxMwSKgVmQKfVyfgMDS RAGGtmuRwgfyhthrertwF0KV8nTajDnSqoGiMAgK7y+e320OEFnYXOKIXlue l7FvOHwi9jZbBAR4HHAfhgJIj78P =OT60 -----END PGP MESSAGE-----
You can now send the encrypted message to your contact.
D) Decrypting messages
Open the terminal and type :
gpg -da < Press enter, then copy paste the message you received. Press Enter, finish by tiping end then press Enter again.
You will be asked to enter the passphrase to decrypt it. Open KeePass and copy paste it. The result will be like this :
You need a passphrase to unlock the secret key for user: "abcd [email protected]" 4096-bit RSA key, ID xx, created 2013-05-08 (main key ID xxx)
gpg: encrypted with 4096-bit RSA key, ID xxx, created 2013-05-08 "abcd [email protected]" ENCRYPTED MESSAGE TO THE SILK ROAD HERE
You can now safely converse with your vendors.
IX) ADDITIONAL THOUGHTS
I hope everything worked well. Finally, the most important security advice someone can give is to use your brain. Don't do anything stupid and you should be fine.
Feel free to discuss issues you may have encontered here or by PM, I'll gladly help you getting setup.
Remember also that your security is only as good as your contacts security. For exemple, if your seller is stupid and keeps detailed informations of his buyers on file, then there isn't much you can do in case he gets caught.
I could have sold this tutorial but I chose not to because my personnal security is guaranteed only if yours is aswell. You get my point.
MUST BE ANONYMOUS
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.12 (GNU/Linux)
mQENBFGIAIUBCAC75V2SJ50dU6+gUY7jdrHxJKmdjXjlOxWjE+CTuti+Pq8NveTK aPXWHmFZpsEtW+v7tHmPPT/cjEKlmo/B9Wxl9daFis+6gFQHnaKNRCFVmOSt9GL8 7qBxrxC/HZTeBgdE8dWf4RPSc911PRb2+iCCrdgj+5ILwp3fcM5EHoRqKiFDpb3A fybrw3prvpPx8dyt1H/p73S6Gfk+Iuwcq2+iIAMJUJQUc+CwMFFCplQ1BUeiD+nn 5o24FXF9Krcbw8w5lZCfPVPSh0GYTvNMaj1VWjEQFU4j0rCOiJ+UVckpgJ4MRrxI MbKJ8srGLSJRnCHM2syQC0Zq/2iwRuZY7zWXABEBAAG0EVdoYXRzdXA1NiA8YUBi LmM+iQE4BBMBAgAiBQJRiACFAhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAK CRBioWhoc3JRsCrhB/9M2AptCTjyitpQR1ZnqwFop/NDdOIY1DtERkyQKfbHftzK 5I/LI3wxP5rhts2NY/EMVl8ziJVZ7h0J9japkoia8uOYX9Un6aMasHM0PH7Mln2K 936BeoZDQbPQV8NOCyNT4lMNt7Ajd+6GJcmAIduPmUi6xjgge716MhQlTBg5HG 94ZJT3Xm7W9tuIiJh8H9Dkr60F9UuwtIPfKPEeXyxUI25fZAQ+nyVz39ap2fjyeW EYMB6y90zxWjFPiFfpx+BfcWOmzHaXkps/bG6kSbOcVn9UJS32C0JyIFmfa96N6H +tSmk+WW98u5dSBzhIoYYiXxWPihJDOjTCUYkFC9uQENBFGIAIUBCADrkKs31LOL 4MQ6fdzhw2MvTI8zDad2bJZCd/+Gf8yGTNKhagJIHo8KEuCDINydQXHCt+aNKZZ7 d/QG09nABaybZJfqf1ffOiD5L1PivcKJMdJNozNuIhWxc4E35A7c/wCPJdDOBV0v eqf57illUo+yz7CKfyO088BYMGTrBRi/ifqmPyMuYzzC4SZcx1MJFU1mzONYU1r0 ZYj0eeKdRrbHPfJUAWQUr6MteMvJp5g8JfyYC+Th+zASEYRRfs3I52rsLb1hpxoi 87xUK89xoXdg4uLysz1Iy/PhGjmtbi61sZCv1oh+o9biNsy9zIjqwhCW7oMPwmJ6 Szh2nNTMCuNFABEBAAGJAR8EGAECAAkFAlGIAIUCGwwACgkQYqFoaHNyUbBKWAf5 AbYVbQVRNYVw5pR6+NDLw1qxlafGz/7j6YnApif0vuVzBEE9aFOUdxfKyIy+Ka8l NYjoAItym2mDTsRZqJwEm1FPbmVFu7WPAnnmn1ECyHBSV0vnJjCL5qkoMx9d/EHs WBW7htnRVtbuJEzVZzzSfddjWEYXGqYcqocebBwQpNgdfuQrHadAbkSmDwLfz+KD r17m1i9sUej8hiFLr64XGau7nl2l+iRMR2vTcVpNZDTJa/t4JlrwMINR95ORo3ze bRVKbedZIn3ifeSzyWDTsScvkNVAe4dovATaHWU/+tkNgL4ECI1UNS8XYsGqWe+r pbfj19eRRPAc4lbNfLlUKQ== =aq6t -----END PGP PUBLIC KEY BLOCK-----
edit : Fixed a few typos.Reorganized chapters using roman letters.
submitted by MUST-BE-ANONYMOUS to SilkRoad [link] [comments]

Uso del Full Node Wallet BTCP Bitcoin Private da Terminale Linux

In questo post voglio dimostrare alcuni utilizzi del Full Node Wallet Bitcoin Private da terminale Linux
AVVERTENZA:
Usate questo tutorial con un piccolo quantitativo di BTCP, nell'esempio utilizzo 0,01 BTCP, almeno fino a quando non vi sentite sicuri nell'uso dei comandi. Fate attenzione! I comandi vengono eseguiti senza possibilità di annullarli, salvo in casi eccezionali, quindi fate tutto a vostro rischio.
PREMESSA:
Il wallet è già stato installato sul vostro PC o in un server Cloud usando le seguenti istruzioni:https://github.com/BTCPrivate/bitcoinprivate
Io uso una Ubuntu 16.04 LTS 64bit, ma i comandi sono simili anche per la distribuzione Windows.
Andrebbe anche aperta la porta TCP 7932 per avere un wallet perfettamente funzionante, ma ho fatto le prove senza aprirla.
Come attivare il firewall:
sudo ufw status
Please note: Make sure you enter the code in this order! If you do not, the program will not work! (If need be you can disable your firewall by entering: sudo ufw disable)
sudo ufw default allow outgoing sudo ufw default deny incoming sudo ufw allow ssh/tcp sudo ufw limit ssh/tcp sudo ufw allow http/tcp sudo ufw allow https/tcp sudo ufw allow 7932/tcp sudo ufw logging on sudo ufw enable
Apri un nuovo terminale troverai il prompt dei comandi, il mio è così, ma potrebbe essere differente:
[email protected]:~$ 
Scrivi quello che segue e premi invio:
[email protected]:~$ ./BitcoinPrivate/src/btcpd --daemon 
dovrebbe apparire il seguente messaggio:
BTCP Server Starting 
Questo significa che hai avviato il server (full node wallet) in modalità daemon, silenziosa. Per fermarlo scrivi:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli stop 
Otterrai la risposta:
BTCP server stopping 
Puoi anche avviare il wallet in una finestra del terminale e vederlo lavorare, anzichè usare il comando --daemon
[email protected]:~$ ./BitcoinPrivate/src/btcpd 
Vedreai apparire un logo del BTCP formato da tanti caratteri e la seguente scritta:
Thank you for running a Bitcoin Private node! You're strengthening the network and contributing to a social good. To ensure you are fully protecting your privacy when running BTCP, see . Block height | 340079 Connections | 8 Network solution rate | 8359387 Sol/s You are currently not mining. To enable mining, add 'gen=1' to your btcprivate.conf and restart. Since starting this node 1 minutes, 33 seconds ago: - You have validated 695 transactions! [Press Ctrl+C to exit] [Set 'showmetrics=0' to hide] 
Block height è l'allineamento del wallet con la blockchain, richiede tempo perchè si allinei e scarichi tutta la blockchain, dipende dalla velocità del tuo collegamento e del tuo pc.Connections: 8 sono i nodi a cui è collegato il nostro wallet, che è un vero e proprio nodo.
Network solution rate è la "potenza" di tutta la rete di elaborare i blocchi in Sol/s
Con un full node puoi partecipare anche tu a rafforzare la rete, abilitando il mining. Si tratta di un solo mining, quindi le probabilità di risolvere un blocco sono veramente minime.
Per farlo basta aggiungere la voce gen=1 nel file btcprivate.conf
Proviamo a farlo. Blocchiamo il nodo con il comando CTRL + C e aspettiamo che appaia il prompt di comando.
Appena appare, inseriamo i seguenti comandi:
[email protected]:~$ cd .btcprivate [email protected]:~/.btcprivate$ ls 
ci siamo spostati nella directory nascosta (inizia per .) contenente i file di configurazione di BTCP, ls mostra i file contenuti:
blocks btcprivate.conf chainstate db.log debug.log fee_estimates.dat peers.dat wallet.dat 
puoi vedere il file btcprivate.conf e wallet.dat che è il file del wallet del nodo. Editiamo ora il file di configurazione, io uso PICO, un text editor per linux, ma potete usare anche vi se preferite:
[email protected]:~/.btcprivate$ pico btcprivate.conf 
inserite gen=1 in una riga vuota del file di configurazione e poi chiudete l'editor salvando con i comandi CTRL+X e Y
gen=1 
tornate nella directory home:
[email protected]:~/.btcprivate$ cd 
Fate riavviare il wallet con il comando:
[email protected]:~$ ./BitcoinPrivate/src/btcpd 
Otterrete il seguente output:
Block height | 340091 Connections | 8 Network solution rate | 8211926 Sol/s Local solution rate | 0.0075 Sol/s Since starting this node 8 minutes, 5 seconds ago: - You have validated 684 transactions! - You have completed 1 Equihash solver runs. You are mining with the default solver on 1 threads. 
Congratulazioni! State minando!
Ora diamo un occhiata al file wallet.dat
ATTENZIONE:
wallet.dat è il vostro wallet, se lo cancellate o lo riscrivete perderete tutti i BTCP che contiene. Consiglio di farne una copia ma attenzione: wallet.dat non è crittografato, quindi vi consiglio di crittografarlo prima di spostarlo dal PC: primo faccio una copia.
Bloccate nuovamente il wallet con CTRL+C
Al prompt scrivete:
[email protected]:~$ cd .btcprivate 
Poi copiate il file sul Desktop (scrivania) Sostituite la parola Desktop con Scrivania se avete installato Linux in Italiano
[email protected]:~/.btcprivate$ cp wallet.dat home/btcp/Desktop/wallet_btcp_back.dat 
Ora troverete il file wallet_btcp_back.dat sulla scrivania, crittografatelo AES256 usando il gestore degli archivi GUI e impostando una password resistente. Per verificare che tutto funzioni, vi consiglio di fare una altra copia di wallet.dat, estrarre il file dall'archivio crittato e sostituirlo al wallet.dat. se tutto funziona siete a posto. Se non siete sicuri non fate nulla e non usate questo wallet per mettere i vostri BTCP, ma nolo per scopi didattici con pochi spiccioli. E' facile fare errori e perdere tutto.
Tornate alla directory home e riavviate il server in daemon mode.
proviamo alcuni comandi usando il client: btcp-cli
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli help 
Se tutto funziona correttamente vi risponderà con la lista di tutti i comandi disponibili:
z_exportwallet "filename" z_getbalance "address" ( minconf ) z_getnewaddress z_getoperationresult (["operationid", ... ]) z_getoperationstatus (["operationid", ... ]) z_gettotalbalance ( minconf ) z_importkey "zkey" ( rescan startHeight ) z_importwallet "filename" z_listaddresses z_listoperationids z_listreceivedbyaddress "address" ( minconf ) z_sendmany "fromaddress" [{"address":... ,"amount":...},...] ( minconf ) ( fee ) z_shieldcoinbase "fromaddress" "tozaddress" ( fee ) zcbenchmark benchmarktype samplecount zcrawjoinsplit rawtx inputs outputs vpub_old vpub_new zcrawkeygen zcrawreceive zcsecretkey encryptednote zcsamplejoinsplit [email protected]:~$ 
Benissimo! Ora proviamo ad usare qualche comando, comunciamo con getinfo
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getinfo 
Risposta:
{ "version": 1001251, "protocolversion": 180004, "walletversion": 60000, "balance": 0.00000000, "blocks": 340074, "timeoffset": 0, "connections": 8, "proxy": "", "difficulty": 167290.7158221716, "testnet": false, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000, "relayfee": 0.00000100, "errors": "" } [email protected]:~$ 
Nella risposta troverete alcune informazioni sul wallet, versione, block height, connections, balance = 0 ecc ecc
Proviamo ora getblockchaininfo:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getblockchaininfo 
Risposta:
{ "chain": "main", "blocks": 340074, "headers": 340074, "bestblockhash": "0000000145c0011d8e914f4ba68d1443c7ae0dd15bdf0bc300994dd5282710aa", "difficulty": 165971.1181999981, "verificationprogress": 0.9999992572690658, "chainwork": "0000000000000000000000000000000000000000000000000002e8314e4484da", "pruned": false, "commitments": 663480, 
La sincronizzazione in questo caso è terminata:"verificationprogress": 0.9999992572690658, (99,99999%)
Ora proviamo getwalletinfo
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getwalletinfo 
Risposta:
{ "walletversion": 60000, "balance": 0.00000000, "unconfirmed_balance": 0.00000000, "immature_balance": 0.00000000, "txcount": 0, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 } [email protected]:~$ 
Proviamo a ricevere dei BTCP da un wallet esterno, per prima cosa abbiamo bisogno di un transparent address da comunicare a chi ci invia i BTCP. Lo otteniamo con il comando getnewaddress:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getnewaddress 
Risposta: otteniamo un indirizzo (le xxx le ho aggiunte per mascherarlo)
b1Cabjwvcce7N8ea9Gxxxxxxxxxxxxxxxx [email protected]:~$ 
Inviate con un vostro wallet grafico o con electrum pochi BTCP, io ne ho mandati 0.01 per prova, dopo che li avete inviati, verificate se sono arrivati:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getwalletinfo 
Risposta:
{ "walletversion": 60000, "balance": 0.00000000, "unconfirmed_balance": 0.01000000, "immature_balance": 0.00000000, "txcount": 1, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 } 
Arrivati ! "Unconfirmed balance" 0.01! non sono ancora confermati, quindi aspettate un po' e ripetete il comando:
"walletversion": 60000, "balance": 0.01000000, "unconfirmed_balance": 0.00000000, "immature_balance": 0.00000000, "txcount": 1, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 
Adesso balance è 0.01 perfetto!
Proviamo adesso ad inviare questi BTCP ad un nuovo T-Address, per semplicità li invierò ad un indirizzo di questo wallet
Generiamo un nuovo indirizzo per riceverli:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getnewaddress 
Otteniamo:
b1Nb42GoK9kmsxxxxxxxxxxxxx 
copiamo l'indirizzo e usiamo il comando sendtoaddress "btcpaddress" amount ( "comment" "comment-to" subtractfeefromamount )
il parametro subtractfeefromamount puo' essere true or false a seconda se vogliamo che le fee vengano detratte dall'ammontare inviato o meno. Io invio tutto quanto al nuovo indirizzo e quindi le fee vanno dedotte da questo:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli sendtoaddress "b1Nb42GoK9kmsxxxxxxxxxxxxx" 0.01 "" "" true 
Risposta:
2c5d3d1a3b5eec414b721d3817487f53c5eebxxxxxxxxxxxxxxx [email protected]:~$ 
Controlliamo cosa è successo:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getwalletinfo 
Risposta:
{ "walletversion": 60000, "balance": 0.00999808, "unconfirmed_balance": 0.00000000, "immature_balance": 0.00000000, "txcount": 2, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 } 
Come vedete i BTCP sono diminuiti, perchè sono stati spostati su un nuovo indirizzo dello stesso wallet, pagando le fee. Ora vediamo esattamente dove sono e dove erano:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli listreceivedbyaddress 
Risposta:
[ { "address": "b1Ep2wi2tUnKf433Vaxxxxxxxxxxxx", "account": "", "amount": 0.01000000, "confirmations": 6, "txids": [ "833533440a13c09fda6e90d0c5xxxxxxxxxxxxxxxxxxxxxxxxxxxxx" ] }, { "address": "b1Nb42GoK9kmsVZ9KPxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "account": "", "amount": 0.00999808, "confirmations": 1, "txids": [ "2c5d3d1a3b5eec414b721d3817487f53c5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" ] } 
Questo comando vi da informazione di tutti gli indirizzi usati, vediamo solo gli indirizzi non spesi: listunspent
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli listunspent 
Risposta:
[ { "txid": "2c5d3d1a3b5eec414b721d381748xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "vout": 0, "generated": false, "address": "b1Nb42GoK9kxxxxxxxxxxxxxx", "account": "", "scriptPubKey": "76a914c6bdf3bc8aedxxxxxxxxxxxxxxxxxx", "amount": 0.00999808, "confirmations": 6, "spendable": true 
Ottimo!
Ora possiamo provare un comando che ci permette di estrarre la chiave provata da un indirizzo pubblico. Questo puo' essete utile in occasione di Fork o Airdrop per estrarre le monete.
ATTENZIONE: esporre a terzi le chiavi private è rischioso. Potrebbero rubare tutto il contenuto. Fate molta attenzione. Estraete le private keys solo se necessario o per fare delle prove su indirizzi che contengono pochi spicci. In ogni caso, dopo aver usato la private key meglio non riutilizzare quell'indirizzo.
Il comando da utilizzare è dumpprivkey T-ADDRESS
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli dumpprivkey b1Ep2wi2tUnxxxxxxxxxxx 
L'output sarà tipo il seguente, al solito la chiave è mascherata con delle xxxxxx
Kz29e62Bmxxxxxxxxxxxxxxxxxxxxxxx 
Ora proviamo lo swipe della chiave, cioè il wallet andrà a cercare nella blockchain tutti gli importi collegati a quella pvt key, : importprivkey "btcpprivkey" ( "label" rescan )
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli importprivkey "Kz29e62Bmxxxxxxxxxxxxxxxxxxxxx" "" true 
Ora proviamo a fare delle Shielded Transaction, queste transazioni utilizzano la tecnologia zk-Snark per mascherare importi e indirizzi. Per prima cosa dobbiamo ottenere un indirizzo Shielded dal nostro wallet.
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_getnewaddress 
Eccolo generato:
zkEvCiVwgHb3NFi2ee9HGPjno2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 
Vediamo dove sono i nostri BTCP, al momento sono solo su indirizzi Transparent:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_gettotalbalance 
Answer:
{ "transparent": "0.00999808", "private": "0.00", "total": "0.00999808" } 
ora mandiamo qualche BTCP all'indirizzo z_address. Per prima cosa dobbiamo recuperare l'indirizzo t-address dove si trovano:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli listunspent 
Eccoli:
[ { "txid": "72f568d1ed51524b69f1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "vout": 0, "generated": false, "address": "b1LDhxBJxxxxxxxxxxxxxxxxxxxxxx", "scriptPubKey": "76axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxe088xx", "amount": 0.00889808, "confirmations": 556, "spendable": true } ] 
Adesso mandiamo un po' di BTCP all'indirizzo Shielded che abbiamo ottenuto sopra. Il comando è abbastanza complicato ma funziona cosi':
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_sendmany "b1LDhxBJxxxxxxxxxxxxxxxxxxxxxx" "[{\"amount\":0.001, \"address\":\"zkEvCiVwgHb3xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\"}]" 
Risultato:
opid-xxxxxxx-36c4-xxxx-beb2-xxxxxxxxxxxx 
Una transazione zk-Snark è piuttosto pesante da elaborare, il mio vecchio PC ci mette un po'. Meglio disattivare processi inutili. Si puo' controllare se l'operazione è andata a buon fine:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_getoperationresult 
al termine dovreste ricevere il seguente output:
[ { "id": "opid-xxxxxx-xxxxx-4a5d-beb2-xxxxxxxxxx", "status": "success", "creation_time": 1529426885, "result": { "txid": "f87e8d5e96a8a0xxxxxxxxxxxxxxx" }, "execution_secs": 216.686332567, "method": "z_sendmany", "params": { "fromaddress": "b1LDhxxxxxxxxxxx", "amounts": [ { "amount": 0.001, "address": "zkEvCiVwgHb3NFxxxxxxxxxxxxxxxxxxR" } ], "minconf": 1, "fee": 0.0001 } } ] 
Fatto! Sul mio vecchio PC ci sono voluti 216,68 secondi!
La prossima prova sarà un invio da indirizzo Shielded a Transparent.
Play with your full node wallet and have fun.Remember: these commands are almost the same in all the bitcoin based coins, so you also learnt how to use many other wallets!
submitted by xivan71 to u/xivan71 [link] [comments]

Bitcoin Hack 30 BTC Free Bitcoin Mining Blockchain Script ... Injecting crypto-mining script on local network - YouTube CPU mining on Linux(Ubuntu) operating system using ... free vps mining bitcoin termux or putty Bitcoin Fasting Mining Script 20182019

Crypto mining scripts can usually be dealt with by closing any browser windows that you suspect are housing a mining script. However, with pop-ups, closing the browser will not stop the mining script. In this case, you will have to bring up the Task Manager (if it’s a Windows PC) and the Activity Monitor (if it’s a Mac) to completely end the browser and the mining script. If there is a ... How to download bitcoin wallet hack. How to download bitcoin hacks and scripts from our website? Everything is very simple, downloading our launcher, you get a free key, for trial testing, which comes to your e-mail, after registering in the system, select the desired script and upload it to your PC, each script contains instructions with detailed launch and solution of possible problems. Ubuntu also comes with its firewall disabled by default, but if you have enabled it, see the Ubuntu wiki page for information about adding port forwarding rules. Once you have allowed inbound connections to port 8333, start Bitcoin Core (if you haven’t already) and follow the Testing Connections instructions to test your connection. Bitcoin Mining with Ubuntu 12.04 LTS and CGMiner. a guest . Oct 9th, 2014 . 699 ... Type sudo reboot in the terminal window. After you reboot your system make sure to install synaptic package package manager and check for updates manually with that application too, just to make you have the latest kernel image. Don't install your graphics drivers until there are no more updates available to ... This article focuses on Ubuntu only, but the configuration and mining process are almost the same in other operating systems as well. To get optimum performance out of the miner, it’s recommended to upgrade Ubuntu to the latest stable release before continuing. The special thing about BFG Miner is it’s completely written in C language, and thus it’s quite efficient at mining bitcoins, at ...

[index] [1472] [24732] [7080] [9292] [26156] [17541] [39121] [50857] [37309] [163]

Bitcoin Hack 30 BTC Free Bitcoin Mining Blockchain Script ...

link:- https://tinyurl.com/ybut8p75 bitcoin, bitcoin news, bitcoin song, bitcoin mining, bitcoin etf, bitcoin wallet, #bitcoinatm, #bitcoinTrading, #bitcoinA... How to mining Bitcoin with your Ubuntu VPS? Earn 0.0001 BTC per VPS, if you have 10 VPS, you will earn 0.001 BTC per day (~2.5 USD), if you have a lot of VPS, you will earn more BTC per day. Educational content! Aimed at learning methods used by others against you, so you can get an idea of how to protect yourself. Free Hacker Course: https://g... Bitcoin Mining on Ubuntu 18.10 - Bitcoin Mining Software 2019 - Duration: 24:00. Bitcoin Mining Software 2019 4,900 views. 24:00. How to Brute Force a Bitcoin Wallet with Hashcat - Duration: 16 ... Binance - https://www.binance.com/?ref=12803159 Hashflare with 63 days to break even, 1-year contract - https://hashflare.io/r/AB31B34E Bitclub Network 5% re...

#