BITCOIN MINING UBUNTU COMMAND LINE – sinsoelot29

(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]

How to get started on GPU mining on Pizza Pool (gpu.pizza) [Nvidia/linux/ClosedSource]

Sunday morining the 0xBitcoin Discord got a surprise from @0xPiZzA...
hi guys. i am 0x778, again! has it gone a long time and you miss me? 8^D= i wait two more weeks since last time, want to check you to see if you are ready for gpu and 0xBITCOIN. today i am ready to release Closed Source GPU Miner for everyone, works for my new Mining Pool name " PiZzA Pool " ! \o/ new pizzaminer is ALPHA software : means speed good but has bugs. Linux only OS. new pool PiZzA Pool also ALPHA but in testing now, available for your to try. credit system is counting. automatic payment, i am building it now. XD lets GO for best! i am not support Help with this software, please figure it out. i believe you can do it. PiZzA Pool going to donate 2% to 0xBITCOIN project / Infernal Toast who will make Open Source Gpu Miner in competition with pizzaminer and Prevail in Triumph. .o/\o/ when you ready, more info : http://gpu.pizza/ :heart: Have Fun, Love 0xBITCOIN 8^D= ~~ 0xPiZzA :heart: 
GPU mining!!!
PiZzA pool - http://gpu.pizza/
Before we start...
THIS SOFTWARE IS CLOSED SOURCE
I DON'T OFFER ANY WARRANTIES ON THIS MINING SOFTWARE
USE AT YOUR OWN RISK
Yet the miner works and I've been paid by the pool (71.17318134 0xBTC):
https://etherscan.io/address/0x79c5BE8f4098208006C7940cF72dAE71738b39b6#tokentxns
1. Prepare your mining rig
Download required programs:
http://gpu.pizza/#download
https://www.ubuntu.com/download/desktop
https://rufus.akeo.ie/
Using this software is risky, but you can minimize the risk by planning. Ideally you want a sanitized GPU mining rig.
This means:
  • No private key!!!
  • No saved passwords!!!
  • No files you are not comfortable with losing!!!
Use this as a basic security audit if you have an existing GPU mining rig.
2. Download and Install Ubuntu
You can Google this.
I believe in you, you will figure it out. :-D
But get an .iso and use Rufus to make a bootable USB.
3. Install Nvidia Drivers
Don't download them from the Nvidia website. Use repositories instead. This guide worked for me: http://www.linuxandubuntu.com/home/how-to-install-latest-nvidia-drivers-in-linux
Make sure you are connected to wifi at this stage. The error message will not clue you into the fact that your internet is not working.
4. Run the pizzaminer software
Details are in the README.TXT. But essentially all you need to do is run the program. Make sure in properties it has permissions to exectute. Also run each miner in their own terminal instance.
http://gpu.pizza/download/pizzaminer-v0.0.1-alpha/README.txt
CUDA_VISIBLE_DEVICES=0 ./pizzaminer 0x0123AbC... CUDA_VISIBLE_DEVICES=1 ./pizzaminer 0x0123AbC... CUDA_VISIBLE_DEVICES=2 ./pizzaminer 0x0123AbC... CUDA_VISIBLE_DEVICES=3 ./pizzaminer 0x0123AbC... 
5. Configure Autostart
Inside the directory where pizza miner is create a file (autostart) that is executable and contains your payment address:
#!/bin/sh xterm -e -hold CUDA_VISIBLE_DEVICES=0 ./pizzaminer 0x0123AbC... & xterm -e -hold CUDA_VISIBLE_DEVICES=1 ./pizzaminer 0x0123AbC... & xterm -e -hold CUDA_VISIBLE_DEVICES=2 ./pizzaminer 0x0123AbC... & xterm -e -hold CUDA_VISIBLE_DEVICES=3 ./pizzaminer 0x0123AbC... & ... 
Then from Start>Startup Applications add the following task:
Name: Autostart pizzaminer Command: autostart (browse for file created above)
7. Optimization
v0.0.3 CPU optimization
Before the CPU was bottle necking the GPU utilization in certain cases. v0.0.3 fixes this and it's stable for me. With multiple cards on a Celeron G39XX you can expect a 50%+ boost in overall hash rate.
Overclocking (EXPERIMENTAL!!!)
This command should allow basic overclocking, monitor free initialization. Honestly haven't had much success in the overclocking department. Let me know if you do!
sudo nvidia-xconfig -enable-all-gpus -cool-bits=28 --allow-empty-initial-configuration 
6. Known Hashrates
GPU MH/s MH/s MH/s
Version v0.0.1 v0.0.2 v0.0.3
GTX 970 (40 MH/s) (55 MH/s) (75 MH/s)
GTX 1050 Ti (40 MH/s) (75 MH/s) (90 MH/s)
GTX 1060 (60-70** MH/s) (100 MH/s) (150 MH/s)
GTX 1070 Ti (90** MH/s) () ()
GTX 1080 Ti (140** MH/s) () (325** MH/s)
**unconfirmed
Please tell me your hashrates to add to this table!!!
If this guide has been helpful please consider donating:
(@Parsley) 0x79c5BE8f4098208006C7940cF72dAE71738b39b6
submitted by AnarchyKitty to 0xbitcoin [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]

How To Mine Doge with Ubuntu 13.10. (Part 1, for AMD Graphics Cards)

I feel the community really needs a resource like this. Because if I had a Doge for every-time taught a newbie how to Mine on Ubuntu, I would be a very rich doge!
EDIT: Sorry if it looks funny, Reddit doesn't like the numbers I put in for some reason.
If you have Ubuntu you have likely not upgraded because you think you cant mine on 13.10, and while that has been true in the past, a few people have got it figured out. So feel free to upgrade. If you are not on Ubuntu, Seriously you should consider using it. Even if its just on an older desktop.
Alright, so lets get a few things clear, I am assuming that you just FRESHLY installed Ubuntu 13.10 x64 on your system. I am assuming that you have no drivers, and no miners. You will need at least a key board and a mouse. The guide will be done in several parts, this first part is for most AMD Graphics cards. If you have an Nvidia, or just want to mine with your CPU, please check back later for those guides!
When reading this guide, please remember that as I give you commands to type into the terminal, Anything between { and} must be included. Do not copy and paste the {}.
Lets get started, If you have not already done so, Install Ubuntu 13.10 64Bit From Here (http://www.ubuntu.com/index_asus.html)
*1. Lets start by making sure you are up to date. Open up the terminal and enter this:
{sudo apt-get update && sudo apt-get upgrade} 
Let that run for a bit.
*2. Once that has finished we are going to download some applications we will need:
{sudo apt-get install dh-make dh-modaliases execstack libxrandr2 libice6 libsm6 libfontconfig1 libxi6 libxcursor1 libgl1-mesa-glx libxinerama1 libqtgui4} 
*3. Once that has run its course we are going to install the ssh server. Remember this command is going to make your computer shut down. While it is shut down, carefully install your graphics cards. If you don't have any experience with this, I suggest you 3 minutes to watch this guide, because failure to install a graphics card the right way can destroy it.
(http://www.youtube.com/watch?v=O9x097QRXeA)
{sudo apt-get install openssh-server sudo shutdown now} 
*4.Install your Card(s) and turn the computer back on.
*5. Make a new folder called "AMD DRIVERS123" inside of your download folder. Downoad the following 3 things into that folder. (1. AMD Drivers: http://support.amd.com/en-us/download/incomplete) (2. AMD APP SDK: http://developer.amd.com/tools-and-sdks/heterogeneous-computing/amd-accelerated-parallel-processing-app-sdk/downloads/) (3. AMD ADL SDK:http://developer.amd.com/tools-and-sdks/graphics-development/display-library-adl-sdk/)
*6. Ok, now we need to unzip and compile those drivers. So, open a terminal my right clicking inside of "AMD DRIVERS123". The enter this:
{unzip amd-catalyst*.zip chmod +x amd-catalyst*.run} {sudo ./amd-catalyst*.run --buildpkg Ubuntu/saucy} 
*7. Now we need to install the drivers. Enter the code exactly as you see it, don't worry, the first command will fail, we are expecting it too.
{sudo dpkg -i fglrx*.deb} {sudo apt-get -f install} {sudo dpkg -i fglrx*.deb} {sudo reboot} 
Your computer should now reboot.
(If this failed, you probibly need to remove the old drivers. Do this
{cd /etc/default sudo pico grub} 
Change the line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" 
Now save by pressing [CTRL+x]
{sudo update-grub} this will make the change perminent. {sudo reboot -n} Reboot with new settings. Once it starts back up try installing the new drivers again.) 
*8.GREAT! You are really on a roll! Now we need to update AtiConfig
{sudo aticonfig --initial --adapter=all} 
*9.Time to install the APP ADK:
{tar xvf AMD-APP-SDK*.tgz} {sudo ./Install-AMD-APP.sh} {sudo reboot} 
*10. WOOT! You are so close to diggin that sweet Doge!! Its time to download CGMiner. IMPORTANT NOTE! You need to get CGminer 3.7, IT IS THE ONLY ONE THAT WILL WORK. Do not get any older or newer, Just this. :
{sudo apt-get install git unzip git clone -b 3.7 https://github.com/ckolivas/cgminer} 
*11. Ok, now go back to "AMD DRIVERS123", Unzip AMD SDL SDK 6.0. Once you have it unzipped, go the file called "include", open it up, copy everything inside, then go find CGminer. Copy these files into the CGminer file called ADL_SDK.
*12. To install CGminer, we are going to need a few things. Get all of these.
{sudo apt-get install build-essential autoconf libtool libcurl4-openssl-dev libncurses5-dev pkg-config libudev-dev} 
*13. Lets go ahead and compile CGminer.
{cd cgminer} {./autogen.sh} 
*14. Ok, when you did that, it told you GPU was not supported, time to fix it.
{./configure --enable-opencl --enable-scrypt} 
(if you did it right you should now get this: OpenCL...............: FOUND. GPU mining support enabled scrypt...............: Enabled ADL..................: SDK found, GPU monitoring support enabled)
*15. If everything has been good so far then
{make} 
*16. MATHEMATICAL! Now lets get it set up to run a test.
{nano test.sh} {!/bin/bash export DISPLAY=:0 export GPU_MAX_ALLOC_PERCENT=100 export GPU_USE_SYNC_OBJECTS=1} {./cgminer -n} 
*17. Now save by hitting [Control+x][y][Enter]
*18.Lastly lets CHmod test.sh
{chmod+x test.sh} 
*19. TIME TO RUN THE TEXT!!!
{./test.sh} 
(If your output looks like this your ready to go!!! CL Platform 0 vendor: Advanced Micro Devices, Inc. CL Platform 0 name: AMD Accelerated Parallel Processing CL Platform 0 version: OpenCL 1.2 AMD-APP (1214.3) Platform 0 devices: 1 0 Tahiti GPU 0 AMD Radeon HD 7900 Series hardware monitoring enabled 1 GPU devices max detected)
*20. Excellent! Now we have it installed, its time to pick 2-3 pools, and get accounts set up at each of them. I currently use These 2, and If I find another I like I'll update. If you have a really awesome pool you would like me to include on the list, feel free to message me.
Pools: http://doge.cryptovalley.com/ (great community, server not super stable, but they have a chat. I hang out here a lot under the handle 'StrongBad' feel free to stop buy and ask questions)
https://dogehouse.org/ (Super stable pool, Great contests, super friendly, and they pay your miner a bonus if you find the block!)
Choose your pools, go to their sites and sign up. VERY IMPORTANT!!! Use different usernames and passwords for every mining site. If one site gets hacked, you don't want to give them a way to steal everything!!!!! Don't worry about the worker names and passwords being unique or complex tho, the most they can do with this is mine for you.
*21. Ok, now go to the CGminer folder, and open up a Terminal Window.
{sudo ./cgminer} 
This should start ./cgminer up with some really basic settings, and not pointed at any pool. Lets fix that: First press [p] to go to pool settings Now [A] and enter the information for the 1st pool. For instance if you are signing on for dogehouse: (Input server details: stratum+tcp://stratum.dogehouse.org:3333 Username: 'yourusername.workername password: 'yourpassword') If you got no errors, you did it right! Your miner should now connect and start to mine very slowly.
Now, do the same thing for all your other pools. the reason we do this is because Doge Coin pools are constantly being DDoS attacked, and this way your worker automatically switches over to a good pool if one go's down.
*22. time to save your current settings press [Enter] to get back out to the main menu, then [s] to bring up settings. Now press [W] to write a Config file. Name it DogeCoin.conf, and make sure to save it in the location it directs you too.
*23.OK! So, now we have everything set up to its basics. What you need to do now is sit down, and fine tune your Card(s). Its really early in the morning, and I need to get some sleep, I will add more on how to tune your card tomorrow in another post, and link it HERE:
Or, I will help you find the best configuration for your card(s). However as this is quite a bit of work, I do charge a small fee. Contact me with your card(s) information and I will get back to you right away. I generally let you decide how much to pay me.
This is my first ever guide on reddit! If you enjoyed it, or if it helped you please remember to upvote! I am going to start doing an educational YouTube series about Bitcoin, and will likely be doing a side program about Doge, if I find time and funding!! You can find that here: All tips are appreciated! DPTwcQreASwzt6TeWBWFb6Kz9ZU5Sezvr9 If you have any Questions, feel free to ask, I will get back to you ASAP.
Happy Digging everybody!
submitted by Sonofchange to Dogecoinmining [link] [comments]

I can't set up a full node!! Help!!

I open the port on my router, when check with "bitcoind getnetworkinfo"
I have 8 connections, try to use the IP and port on https://getaddr.bitnodes.io/ and it says not connected.
If I type in terminal: netstat -nptl
As a result I have this:
(Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN - tcp 0 0 127.0.0.1:2628 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN - tcp 0 0 127.0.0.1:8332 0.0.0.0:* LISTEN 24081/bitcoind tcp 0 0 0.0.0.0:8333 0.0.0.0:* LISTEN 24081/bitcoind tcp 0 0 127.0.0.1:5941 0.0.0.0:* LISTEN - tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN - tcp6 0 0 ::1:631 :::* LISTEN - tcp6 0 0 :::25 :::* LISTEN - tcp6 0 0 :::445 :::* LISTEN - tcp6 0 0 :::139 :::* LISTEN - tcp6 0 0 ::1:8332 :::* LISTEN 24081/bitcoind tcp6 0 0 :::8333 :::* LISTEN 24081/bitcoind
If I try this http://www.lurkmore.com/mining/port8333/ it says that I haven't open the port, but this is untrue!
In port fowarding setup I have:
PORT FORWARDING SETUP
Server Name External Port Start External Port End Protocol Internal Port Start Internal Port End Server IP Address Schedule Rule Remote IP bitcoin 8333 8333 TCP 8333 8333 192.168.1.1 Always bitcoin1 8333 8333 TCP 8333 8333 192.168.1.2 Always bitcoin2 8333 8333 TCP 8333 8333 192.168.1.3 Always bitcoin3 8333 8333 TCP 8333 8333 192.168.1.4 Always folding_at_home 36330 36330 TCP 36330 36330 192.168.1.1 Always 0.0.0.0 
Why it doesn't works?
PS using this "sudo ufw allow 8333" nothing change...
submitted by pietrod21 to BitcoinBeginners [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]

Mining Bitcoin di Linux Menggunakan M7MHASH WORK!!! How To Install BitCoin On Ubuntu 16.04 CPU mining on Linux(Ubuntu) operating system using ... minar bitcoin con nicehash en ubuntu tutorial: Bitcoin mining with CGMiner - YouTube

As part of these changes, consensus critical Bitcoin mining ubuntu //tiny.cc/CryptoMine Another great Mining business: //tiny.cc/OmniaTechInfo Rock solid Bitcoin Investment program: //tin Which command line software tools are required to mine litecoin. you simply have to execute this command to lunch mining : Command line bitcoin cash wallet Minera is a complete web frontend to manage and ... 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 ... CGMiner is a Bitcoin mining tool written with the C programming language. It is designed to run on ASIC mining devices, works on both Windows and Linux, and is ideal for advanced cryptocurrency users. The CGMiner application is command-line based, and users interact with it via a command-line interface. It can mine for Bitcoin using multiple methods (GPU and CPUs) and does it quite efficiently ... Bitcoin mining rigs and systems have come a long way since the beginning. The first Bitcoin miners made do with the tools they had at their disposal and set up various software to control the mining hardware in their rigs. While these make-shift solutions were better than nothing, they didn’t exactly work efficiently. Not only did that slow down the mining process, but it also made it ... NOTE: Bitcoin mining is very time consuming and you need a very powerful network of server machines to obtain even a small result (less than a bitcoin in most cases). This is due to the fact that you are competing with people and organizations running highly specialized hardware ( ASIC miners , FPGA devices etc.) which does nothing but compute BTC block hashes 24h a day.

[index] [30437] [4687] [11168] [3507] [22979] [13729] [42886] [40361] [28694] [22349]

Mining Bitcoin di Linux Menggunakan M7MHASH WORK!!!

Noob's Guide To Bitcoin Mining - Super Easy & Simple - Duration: 11 ... How to build an altcoin or bitcoin on Ubuntu Linux Server Shell - Duration: 11:08. Antonie Geerts 10,735 views. 11:08. How ... Bitcoin Mining on Ubuntu 18.10 - Bitcoin Mining Software 2019 - Duration: 24:00. Bitcoin Mining Software 2019 7,950 views. 24:00. How to install Bitcoin on Ubuntu 16.04 - Duration: 2:50. 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... 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:56. In this video, I'm going to show you how to start mining Bitcoin on Linux/Debian based operating systems. https://bitcoinminingsoftware2019.com/bitcoin-minin...

#