addnode — Bitcoin

Running a Bitcoin node on a $11.99 SBC

Running a Bitcoin node on a $11.99 SBC
Just wanted to let you guys know that I'm successfully running a (pruned) Bitcoin node + TOR on a $11.99 single board computer (Rock Pi S).
The SBC contains a Rockchip RK3308 Quad A35 64bit processor, 512MB RAM, RJ45 Ethernet and USB2 port and I'm using a 64GB SDCard. It runs a version of Armbian (410MB free). There's a new version available that even gives you 480MB RAM, but I'm waiting for Bitcoin Core 0.19 before upgrading.
To speed things up I decided to run Bitcoin Core on a more powerful device to sync the whole blockchain to an external HDD. After that I made a copy and ran it in pruned mode to end up with the last 5GB of the blockchain. I copied the data to the SD card and ran it on the Rock Pi S. After verifying all blocks it runs very smoothly. Uptime at the moment is 15 days.
I guess you could run a full node as well if you put in a 512GB SDcard.
The Rock Pi S was sold out, but if anybody is interested, they started selling a new batch of Rock Pi S v1.2 from today.
Screenshot of resources being used
Bitcoin Core info
Around 1.5 GB is being transferred every day
---
Some links and a short How to for people that want to give it a try:
  1. This is the place where I bought the Rock Pi S.
  2. Here you find more information about Armbian on the Rock Pi S. Flash it to your SDCard. Follow these instructions.
  3. Disable ZRAM swap on Armbian. If you don't do this eventually Bitcoin Core will crash. nano /etc/default/armbian-zram-config ENABLED=false
  4. Enable SWAP on Armbian sudo fallocate -l 1G /swapfile sudo chmod 600 /swapfile sudo mkswap /swapfile sudo swapon /swapfile sudo swapon --show sudo cp /etc/fstab /etc/fstab.bak echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab
  5. Set up UFW Firewall sudo ufw default deny incoming sudo ufw default allow outgoing sudo ufw allow ssh # we want to allow ssh connections or else we won’t be able to login. sudo ufw allow 8333 # port 8333 is used for bitcoin nodes sudo ufw allow 9051 # port 9051 is used for tor sudo ufw logging on sudo ufw enable sudo ufw status
  6. Add user Satoshi so you don't run the Bitcoin Core as root sudo adduser satoshi --home /home/satoshi --disabled-login sudo passwd satoshi # change passwd sudo usermod -aG sudo satoshi # add user to sudo group
  7. Download (ARM64 version) and install Bitcoin Core Daemon
  8. Download and install TOR (optional). I followed two guides. This one and this one.
  9. Create a bitcoin.conf config file in the .bitcoin directory. Mine looks like this: daemon=1 prune=5000 dbcache=300 maxmempool=250 onlynet=onion proxy=127.0.0.1:9050 bind=127.0.0.1 #Add seed nodes seednode=wxvp2d4rspn7tqyu.onion seednode=bk5ejfe56xakvtkk.onion seednode=bpdlwholl7rnkrkw.onion seednode=hhiv5pnxenvbf4am.onion seednode=4iuf2zac6aq3ndrb.onion seednode=nkf5e6b7pl4jfd4a.onion seednode=xqzfakpeuvrobvpj.onion seednode=tsyvzsqwa2kkf6b2.onion #And/or add some nodes addnode=gyn2vguc35viks2b.onion addnode=kvd44sw7skb5folw.onion addnode=nkf5e6b7pl4jfd4a.onion addnode=yu7sezmixhmyljn4.onion addnode=3ffk7iumtx3cegbi.onion addnode=3nmbbakinewlgdln.onion addnode=4j77gihpokxu2kj4.onion addnode=5at7sq5nm76xijkd.onion addnode=77mx2jsxaoyesz2p.onion addnode=7g7j54btiaxhtsiy.onion ddnode=a6obdgzn67l7exu3.onion
  10. Start Bitcoin Daemon with the command bitcoind -listenonion
Please note that I'm not a professional. So if anything above is not 100% correct, let me know and I will change it, but this is my setup at the moment.
submitted by haste18 to Bitcoin [link] [comments]

Addnode vs Connect

Addnode vs Connect
Hello everyone, i would like to share the differences between two commands (Addnode vs connect) which are used to find connections.
Addnode:
Let's you establish a connection to a particular node as well as let other nodes connected to it know you exist.
Connect:
Using this will only let you connect to that specific node and nothing else.

Recommended command if you're behind a firewall or have trouble finding connections. is addnode=xx.xx.xx.xx
x is the address of the node.Enter these node in the x42.conf file.
Popular nodes for x42
addnode=52.211.235.48:52342
addnode=18.179.72.204:52342
addnode=63.32.82.169:52342
addnode=34.255.35.42:52342
Source : https://github.com/bitcoin/bitcoin/blob/masteshare/examples/bitcoin.conf
https://preview.redd.it/t6mv6dbh7qd41.png?width=1417&format=png&auto=webp&s=8b138662a256c3515c57c9efb6c2fb78eb62560d
submitted by sirviks to x42 [link] [comments]

A tour of the Gridcoin wallet

Hey guys, I thought I would put together an in-depth tour of the Gridcoin wallet software for all of our recent newcomers. Here I'll be outlining all the features and functions the windows GUI wallet has to offer, along with some basic RPC command usage. I'll be using the windows wallet as an example, but both linux and macOS should be rather similar. I'll be including as many pictures as I can as embedded hyperlinks.
Edit: Note that since I originally made this there has been a UI update, so your client will be different colors but all the button locations are in the same place.
This is my first post like this, so please forgive me if this appears a little scatter-brained.
This will not cover the mining setup process for pool or solo miners.
When you launch the wallet software for the first time you should be greeted with this screen.

OVERVIEW TAB

After that prompt, you should be left sitting on the main overview tab with several fields on it.
From top to bottom:

SEND TAB

Now onto the other tabs on the left side. Currently we're on the Overview tab, lets move down to the Send tab. This tab it pretty self-explanatory, you use it if you want to send coins, but I'll go over the fields here:
  • Pay To: Enter a valid gridcoin address to send coins too. Gridcoin addresses always start with an S or and R.
  • Label: Enter a label here and it will put that address in your "address book" under that label for later use. You can leave it blank if you don't want it in your address book.
  • Message: Enter a message here if you want it attached to your transaction.
  • Amount: How many coins you want to send.
  • Add Attachment: Leave this alone, it is broken.
  • Track Coins: This doesn't do anything.

RECEIVE TAB

Now down to the Receive tab. Here you should have a single address listed. If you double click on the label field, you can edit it's label.
  • New: Generate a new address.
If you click on an address, the rest of the options should be clickable.
  • Copy: Copy the selected address to your clipboard.
  • Show QR Code: Show a scan-able QR code for the selected address.
  • Sign Message: Cryptographically sign a message using the selected address.

TRANSACTIONS TAB

The Transactions tab is pretty boring considering we have no transactions yet. But as you can see there are some sorting tools at the top for when you do have transactions listed.

ADDRESS BOOK TAB

The Address Book is where all the addresses you've labeled (that aren't yours) will show up.
  • Verify Message: Verifies a message was signed by the selected address.
The rest of the functions are similar to the functions on the Receive tab.

VOTING TAB

Onto the Voting tab. There wont be any polls because we aren't in sync yet.
  • Reload Polls: Pretty self-explanatory, I've never had to use this.
  • Load History: By default, the wallet will only display active polls. If you want to view past polls you can use this.
  • Create Poll: You can create a network-wide poll. You must have 100,000 coins as a requirement to make a poll. (Creating a poll does not consume the coins)
Here's what the Voting tab will look like once you're in sync

CONTEXT BAR

Now onto the context bar menus on the top.
Under File you have:
  • Backup Wallet/Config: This lets you backup your wallet configuration file just in case.
  • Export: You can export your Transactions tab or Address Book in CSV format.
  • Sign message: Does the same thing as on the Receive tab.
  • Verify message: Does the same thing as on the Address Book tab.
  • Exit: Close the wallet.
Under Settings you have:
  • Encrypt Wallet: Encrypts your wallet with a password. (we'll come back to this)
  • Change Passphrase: Allows you to change your encryption password.
  • Options: Opens the options menu. (We'll come back to this)
Under Community you have:
Under Advanced you have:
  • Advanced Configuration: Opens the Advanced Configuration menu. (Not so advanced if you ask me)
  • Neural Network: Allows you to view solo miners project statistics. It will be largely blank if you're not in sync yet.
  • FAQ: Don't touch this, It is broken.
  • Foundation: Don't touch this, It is broken.
  • Rebuild Block Chain: Starts the client syncing from 0. Don't worry, using this will not make you lose coins.
  • Download Blocks: Downloads the latest official snapshot, can help speed up syncing. The download progress tends to sit at 99.99% for a long time, don't worry, it's working.
Under Help you have:
  • Debug window: Opens the debug window. (We'll come back to this)
  • Diagnostics: Don't touch this, it is broken. This has since been fixed. You can use this to see if there is anything wrong with your setup.
  • About Gridcoin: Opens the About Dialog. This gives you your client version and other information.

OPTIONS

Now back to the options menu under Settings > Options.
Here we have the options menu main tab:
  • Pay transaction fee: The transaction fee that will be automatically paid when you make a transaction.
  • Reserve: You can reserve an amount so that it will always be available for spending.
  • Start Gridcoin on system login: Pretty self-explanatory
  • Detach databases at shutdown: Speeds up shutdown, but causes your blockchain file to no longer be portable.
On the Network tab:
  • Map port using UPnP: Attempts to connect to nodes through UPnP.
  • Connect through SOCKS proxy: Allows you to connect through a proxy.
The window tab is pretty self-explanatory.
The Display tab is also pretty self-explanatory, with the exception of:
  • Display coin control features (experts only!): This allows you to have a great deal of control over the coins in your wallet, check this for now and I'll explain how to use it further down. Don't forget to click "Apply".

ENCRYPTING YOUR WALLET

Now that all of that is out of the way. The first thing you'll want to do is encrypt your wallet. This prevents anybody with access to your computer from sending coins. This is something I would recommend everyone do.
Go to Settings > Encrypt Wallet and create a password. YOU CANNOT RECOVER YOUR COINS IF YOU FORGET YOUR PASSWORD.
Your wallet will close and you will have to start it up again. This time when it opens up, you should have a new button in the bottom left. Now if you want to stake you will have to unlock your wallet. Notice the "For staking only" box that is checked by default. If you want to send a beacon for solo mining or vote, you will need to uncheck this box.

GETTING IN SYNC AND ICONS

Before we continue, Let's wait until we're in sync. Depending on your internet speeds, this could take from several hours to over a day or 2. This can be sped up by using Advanced > Download Blocks, but this can still take several hours.
This is what an in-sync client should look like. Notice the green check to the right of the Receive tab. All of these icons give you information when you hover your mouse over them.
The lock
The arrow tells you if you're staking. If you aren't staking, it will tell you why you're not staking. If you are staking it will give you an estimated staking time. Staking is a very random process and this is only an estimate, not a countdown.
The connection bars tell you how many connections to the network you have.
The check tells you if you're in sync.

WHAT IS STAKING?

Now I've said "stake" about a million times so far and haven't explained it. Gridcoin is a Proof of Stake (PoS) coin.
Unlike bitcoins Proof of Work (PoW), PoS uses little system resources, so you can use those resources for scientific work. PoS works by users "Staking" with their balance. The higher the balance, the higher the chance to create, or "stake" a block. This means you need to have a positive balance in order to stake. Theoretically, you can stake with any amount over 0.0125 coins, but in practice it's recommended to have at least 2000 coins to reliably stake.
Staking is important for solo miners, because they get paid when they stake. Pool miners don't need to stake in order to get paid however. So if you want to solo mine, you'll need to buy some coins from an exchange or start in the pool first and move to solo when you have enough coins.
In addition to Research Rewards for miners, anyone who holds coins (solo miners, pool miners, and investors) gets 1.5% interest annually on top of your coins. So it can be beneficial for pool miners to stake as well.
Here is a snippet of what a research rewards transaction looks like from my personal wallet. I have a label on that address of "Payout address" as you can see here.

UTXOS AND COIN CONTROL

At this point you'll need some coins. You can use one of our faucets like this one or this one to test coin control out.
First let me explain what a UTXO is. UTXO stands for Unspent Transaction Output. Say you have an address with 0 coins in it, and someone sends you 10 coins like I've done here. Those 10 coins are added to that address in the form of a UTXO, so we have an address with one 10 coin UTXO in it.
Now we receive another 5 coins at the same address, like so. Now we have an address with one 10 coin UTXO and one 5 coin UTXO. But how do we view how our addresses are split up into different UTXOs?
Earlier we checked the "Display coin control features" box in Settings > Options > Display. Once that's checked you'll notice there's another section in the Send tab labeled "Coin Control Features". If you click the "Inputs" button, you'll get a new window. And look, there's our 2 UTXOs.
All UTXOs try to stake separately from each other, and remember that the chance a UTXO has to stake is proportional to it's size. So in this situation, my 10 coin UTXO has twice the chance to stake as my 5 coin UTXO. Now wallets, especially ones that make a lot of transactions, can get very fragmented over time. I've fragmented my wallet a little so I can show you what I'm talking about.
How do we clean this up? We can consolidate all this into one UTXO by checking all the boxes on the left and selecting OK.
Now pay attention to the fields on the top:
  • Quantity: The total amount of UTXOs we have selected.
  • Amount: The total amount of coins we have selected.
  • Fee: How much it would cost in fees to send all those UTXOs (more UTXOs = more transaction data = more fees)
  • After Fee: Amount - Fees.
  • Bytes: How large the transaction is in bytes.
  • Priority: How your client would prioritize making a transaction with this specific set of UTXOs selected had you not used coin control.
  • Low Output: If your transaction is less than 0.01 coins (I think).
  • Change: What you will get back in change.
  • custom change address: You can set the address you get your change back at, by default it will generate a new address.
So let's fill out our transaction so we end up with 1 UTXO at the end.
In "Pay To:" Just put any address in your wallet, and for the amount put what it has listed in the "After Fee" Field. Just like this.
Notice how we get no change back.
Now click "Send", we'll be prompted to enter our passphrase and we're asked if we want to pay the fee, go ahead and click "Yes".
Now if we go back to the Overview tab we get this funky icon. If you hover your mouse over it, it says "Payment to yourself", and the -0.0002 GRC is the network transaction fee.
(Ignore the first one, that was me fragmenting my wallet)
Now if we look at the Coin Control menu, we can see that we've slimmed our wallet down from 7 UTXOs to 1.
Now why would you want to use coin control?
2 Situations:
  1. UTXOs less than 0.0125 coins cannot stake. So you can combine a lot of tiny, useless UTXOs into 1 bigger one that can stake.
  2. After a UTXO stakes, it cannot stake for another 16 hours. So if you have 1 large UTXO that is big enough to stake more than once every 16 hours, you can split it into smaller UTXOs which can allow you to stake slightly more often.
  3. By default, the wallet will always generate a new address for change, which can make your wallet get very messy if you're sending lots of transactions. Keep in mind that more UTXOs = larger transactions = more fees.
Sidenote - When you stake, you will earn all research rewards owed reguardless of which UTXO staked. However, you'll earn the 1.5% interest for that UTXO. Not your whole wallet.

FORKING

A fork is when the network splits into multiple chains, with part of the network on each chain. A fork can happen when 2 blocks are staked by different clients at the same time or very close to the same time, or when your client rejects a block that should have been accepted due to a bug in the code or through some other unique circumstance.
How do I know if I'm on a fork?
Generally you can spot a fork by looking at the difficulty on your Overview tab. With current network conditions, if your difficulty is below 0.1, then you're probably on a fork.
You can confirm this by comparing your blockhash with someone elses, like a block explorer.
Go to [Help > Debug Window > Console]. This is the RPC console, we can use to do a lot of things. You can type help to get a list of commands, and you can type help [command you need help with] (without the brackets) to get information on a command. We'll be using the getblockhash [block number] command.
Type getblockhash [block number] in the console, but replace [block number] with the number listed next to the "Blocks:" field on the Overview tab.
This will spit out a crazy string of characters, this is the "blockhash" of that block.
Now head over to your favorite block explorer, I'll be using gridcoinstats. Find the block that you have the hash for, use the search bar or just find it in the list of blocks.
Now compare your hash with the one gridcoinstats gives you. Does it match?
If it matches, then you're probably good to go. If it matches but you still think you're on a fork, then you can try other block explorers, such as gridcoin.network or neuralminer.io.
If it doesn't match, then you need to try to get off that fork.
How do I get off a fork?
  1. Just wait for an hour or two. 95% of the time your client is able to recover itself from a fork given a little time.
  2. Restart the client, wait a few minutes to see if it fixes itself. If it doesn't restart again and wait. Repeat about 4 or 5 times.
  3. Find where the fork started. Using the getblockhash command, go back some blocks and compare hashes with that on a block explorer so you can narrow down what the last block you and the block explorer had in common. Then use reorganize [the last block hash you had in common]. Note that reorganize takes a blockhash, not a block number.
  4. Use Advanced > Download Blocks.
  5. If none of this works, you can take a look at social media (reddit/steemit) and see what other people are saying.

CONFIGURATION FILE

Your configuration file depends on your operation system:
  • On Windows: %appdata%\GridcoinResearch\
  • On Linux: ~/.GridcoinResearch/
  • On MacOS: /Users/USERNAME/Library/Application/Support/GridcoinResearch/
And it should look like this.
If you open up your gridcoinresearch.conf, you'll see the default one it generated. Note that if you entered your email earlier, the first line will have your email on it instead of "investor". If you decided you want to solo mine but didn't enter your email when you first started the wallet, go ahead and put your email on the first line in place of "investor". If you're a pool miner, just leave it as "investor".
Next, it's recommended that you use the addnodes on the gridcoin wiki. So our gridcoinresearch.conf will look like this.
A useful line for solo miners is PrimaryCPID=[YOUR CPID]. Sometimes your wallet can pick up on the wrong CPID so it's good to have that in there if you're solo mining.

RUNNING A LISTENING NODE

A listening node is a node that listens for blocks and transactions broadcasted from nodes and forwards them on to other nodes. For example, during the syncing process when you're getting your node running for the first time, you're downloading all the blocks from listening nodes. So running a listening node helps support the network.
Running a gridcoin listening node is simple. All you need to do is add listen=1 to your gridcoinresearch.conf and you need to forward port 32749 on your router.
If you don't know how to port forward, I'd suggest googling "How to port forward [your router manufacturer]".

QUICK LINKS

Gridcoin.us Official Website
Gridcoin.science Unofficial Website
Gridcoinstats.eu Block Explorer
NeuralMiner.io Block Explorer
Gridcoinstats.eu Faucet
Gridcoin.ch Faucet
Gridcoin Wiki
Gridcoin Github
GRCPool
Arikado Pool
And that's all I have for now!
I plan to keep this post up-to-date with changes in the client. So if anyone has any suggestions, have clarifications they want made, or maybe I got something wrong, then please feel free to leave a comment below or PM me!
submitted by Personthingman2 to gridcoin [link] [comments]

Gridcoin Leisure Update 3.7.14.0 Released

Today we have a new leisure update for you. This version includes a lot of "under the hood" changes, but there are some improvements for the average user as well.
 
Notably this release includes a better time to stake calculation method, thanks to @jamescowens. Also the Neural Network runs much smoother thanks to many optimizations by @ifoggz.
 
Download the update from GitHub here.
The Windows MSI can be downloaded here.
 
Full Release Notes:
Added
 
Changed
 
Fixed
 
Removed
 
Thank you to all the developers who contributed to this release. I will update this post when the Windows MSI has been uploaded to the website.
submitted by barton26 to gridcoin [link] [comments]

such beginner shibe thread wow how to get coin

 how to shibecoin v rich in minutes much instruct so simple any doge can do 

START HERE

UPDATE 1/21/14: I'm not updating this guide anymore. Most of the steps should still work though. See the wiki or check the sidebar for updated instructions.
Before you do anything else, you need to get a wallet. Until there's a secure online wallet, this means you need to download the dogecoin client.
Now open the client you just downloaded. You'll be given a default address automatically, and it should connect to peers and start downloading the dogechain (aka blockchain in formal speak). You'll know because there will be a progress bar at the bottom and at the lower right there should be a signal strength icon (TODO: add screenshots).
If you've waited 2 or 3 minutes and nothing is happening, copy this:
maxconnections=100 addnode=95.85.29.144 addnode=162.243.113.110 addnode=146.185.181.114 addnode=188.165.19.28 addnode=166.78.155.36 addnode=doge.scryptpools.com addnode=doge.netcodepool.org addnode=doge.pool.webxass.de addnode=doge.cryptopool.it addnode=pool.testserverino.de addnode=doge.luckyminers.com addnode=doge.cryptovalley.com addnode=miner.coinedup.comdoge addnode=doge.cryptoculture.net addnode=dogepool.pw addnode=doge.gentoomen.org addnode=doge.cryptominer.net addnode=67.205.20.10 addnode=162.243.113.110 addnode=78.46.57.132 
And paste it into a new text file called dogecoin.conf, which you then place into the dogecoin app directory.
Now restart your qt client and the blockchain should start downloading in about 1-2 minutes.
Once it finished downloading, you're ready to send and receive Dogecoins!

GETTING COINS

Decide how you want to get Dogecoin. Your options are:
I'll go into detail about each of these. I'm currently writing this out. I'll make edits as I add sections. Suggestions are welcome.

MINING

Mining is how new dogecoins are created. If you're new to crypto currencies, read this. To mine (also called "digging"), a computer with a decent GPU (graphics card) is recommended. You can also mine with your CPU, but it's not as efficient.

GPU MINING

These instructions cover only Windows for now. To mine, you'll need to figure out what GPU you have. It'll be either AMD/ATI or Nvidia. The setup for both is approximately the same.

Step One: Choose a pool

There's a list of pools on the wiki. For now it doesn't really matter which one you choose. You can easily switch later.
NOTE: You can mine in two ways. Solo mining is where you mine by yourself. When you find a block you get all the reward. Pool mining is when you team up with other miners to work on the same block together. This makes it more likely that you'll find a block, but you won't get all of it, you'll have to split it up with others according to your share of the work. Pool mining is recommended because it gives you frequent payouts, because you find more blocks. The larger the pool you join, the more frequent the payouts, but the smaller the reward you get.
Over a long period of time the difference between pool and solo mining goes away, but if you solo mine it might be months before you get any coins.

Step two: Set up pool account

The pool you chose should have a getting started page. Read it and follow the instructions. Instructions vary but the general idea is:
When you're done with this, you'll need to know:

Step three: Download mining software

For best performance you'll need the right mining software.
Unzip the download anywhere you want.

Step four: Set up miner

Create a text file in the same folder as your miner application. Inside, put the command you'll be running (remove brackets).
For AMD it's cgminer.exe --scrypt -o stratum+tcp://: -u -p
For Nvidia it's cudaminer.exe -o stratum+tcp://: -O :
Substitute the right stuff in for the placeholders. Then on the next line of the text file type pause. This will let you see any errors that you get. Then save the file with any name you want, as long as the file extension is .bat. For example mine_serverName.bat.

Step five: Launch your miner

Just open the .bat file and a command line window should pop up, letting you know that the miner is starting. Once it starts, it should print out your hash rate.
If you now go to the pool website, the dashboard should start showing your hashrate. At first it'll be lower than what it says in the miner, but that's because the dashboard is taking a 5 minute average. It'll catch up soon enough.
NOTE: A normal hashrate is between 50 Kh/s up to even 1 Mh/s depending on your GPU.

You're now mining Dogecoins

That's it, nothing more to it.

CPU MINING

CPU mining isn't really recommended, because you'll be spending a lot on more on power than you'd make from mining Dogecoin. You could better spend that money on buying Dogecoin by trading. But if you have free electricity and want to try it out, check out this informative forum post.

Trading

Trading has been difficult so far, but Dogecoin just got added to a few new exchanges. If you don't have a giant mining rig, this is probably the best way to get 100k or more dogecoins at the moment. I'll write up a more complete guide, but for now check out these sites:

Faucets

Faucets are sites that give out free coins. Usually a site will give out somewhere between 1 and 100 Dogecoin. Every site has its own time limits, but usually you can only receive coins once every few hours, or in some cases, days. It's a great way to get started. All you do is copy your address from the receive section of your wallet and enter it on some faucet sites. Check out /dogecoinfaucets for more. If you go to each site on there you might end up with a couple hundred Dogecoin!

Begging

This method is pretty straightforward. Post your receiving address, and ask for some coins. Such poor shibe. The only catch is, don't do it here! Please go to /dogecoinbeg.

Tips

At the moment there are two tip bots:
Other redditors can give you Dogecoin by summoning the tip bot, something like this:
+dogetipbot 5 doge
This might happen if you make a good post, or someone just wants to give out some coins. Once you receive a tip you have to accept it in a few days or else it'll get returned. Do this by following the instructions on the message you receive in your inbox. You reply to the bot with "+accept". Commands go in the message body. Once you do that, the bot will create a tipping address for you, and you can use the links in the message you receive to see your info, withdraw coins to your dogecoin-qt wallet, see your history, and a bunch of other stuff.
As a bonus, so_doge_tip has a feature where you can get some Dogecoins to start with in exchange for how much karma you have. To do this, send the message "+redeem DOGE" to so_doge_tip. You'll need to create a tipping account if you don't have one.
If you want to create a tipping account without ever being tipped first, message either of the bots with "+register" and an address will be created for you.

CHANGELOG

  • 1/21/14 - Added note about this thread no longer being updated
  • 1/21/14 - Changed wallet links to official site
  • 12/27/13 - Added 1.3 wallet-qt links
  • 12/21/13 - Added new windows 1.2 wallet link
  • 12/20/13 - Fixed +redeem text
  • 12/18/13 - Added short blurb on trading.
  • 12/18/13 - Updated cudaminer to new version (cudaminer-2013-12-18.zip).
  • 12/18/13 - Fixed +redeem link
  • 12/18/13 - Updates dogecoin.conf, from here.
  • 12/17/13 - Linked to mining explanation.
  • 12/17/13 - Added link to CPU mining tutorial, in response to this.
  • 12/16/13 - Added links to tip commands, link to dogetipbot wiki.
  • 12/16/13 - Note about tip commands going in body, in response to this.
  • 12/16/13 - Added link to cgminer mirror, thanks to scubasteve812 and thanks to Bagrisham.
  • 12/16/13 - Note about removing brackets in response to this.
  • 12/15/13 - Fixed hash rate as per this comment, thanks lleti
  • 12/15/13 - Added info for all other ways of getting money, except for trading (placeholder for now)
  • 12/15/13 - Added windows GPU mining instructions 12/15/13 - Added wallet instructions, list of how to get money
submitted by lego-banana to dogecoin [link] [comments]

PIVX Core Wallet 3.0.5 final release (November 13th, 2017) - Mandatory Upgrade

Github release link
Forum Post

Important Notes

Upgrade instructions

1- Download the appropriate release for your platform from the Github release link. For command line installs/updates this link may help.
2- Start up your client and see if you are on the wrong chain by using this link (Am I forked?) or manually comparing your latest block hash against the [block explorer](www.presstab.pw/phpexplorePIVX/index.php#)
3- If you are on the correct chain, let it fully sync (or as far as it will go) and then repeat step 2. If you are still on the right chain move on to step 4. If you're on the wrong chain, download the chainstate from this link (mirror) and follow the instructions to install it. Do NOT delete wallet.dat or your backups folder. Once this is done, restart your client and let it finish syncing
  1. stop your wallet and/or daemon
  2. locate the folder with the blockchain folders (usually ~/.pivx/)
  3. do a complete(!) backup of this folder in case something goes wrong
  4. completely remove the folders "blocks", "chainstate", "sporks" and "zerocoin"
  5. download one of the snapshot-files (preferably the newest one) above into this folder
  6. unpack the snapshot file: 'unzip '
  7. the folders deleted above are now replaced by the ones from the snapshot
  8. restart your wallet and/or daemon
4- On this step you should be fully synced and on the right chain. Using the debug screen or pivx-cli, use the command
spork show 
to output your spork status. Have a look at spork 16 and make sure the value is 1510179528 (now 1609459199). If it is, go ahead and start staking.
If you are having trouble getting the correct value for spork 16, try adding nodes to your pivx.conf file that are protocol 70912. A list of 70912 nodes can be found at http://www.presstab.pw/phpexplorePIVX/nodes.php . This can be done from the debug menu or with pivx-cli by saying
addnode 123.45.67.89 add 

Notable Changes

libzerocoin Exploit Fix

zPIV relies on a 3rd party library called libzerocoin. All currencies that utilize the zerocoin protocol use libzerocoin, and many of those currencies have been exposed to an exploit which allowed for the creation of multiple zero-knowledge spending proofs for one single zerocoin mint. The PIVX developers were able properly identify the exploit, track down any fraudulent spending proofs, link the fraudulent spending proofs with their one valid proof that they were mutated from, and remove any mints from the accumulators that were derived from the invalid spends.

zPIV Maintenance Mode Spork

Handling the above noted libzerocoin exploit required the PIVX team to immediately release a patched wallet to as many users as possible which rejected bad spends and also disabled all zPIV transactions in general. The process of releasing a patched wallet in such a small time frame is frustrating and difficult for all members of the PIVX team and especially users of PIVX. The PIVX developers have added a new spork which allows for zPIV transacting to be turned on/off without having to release a patched wallet. This will allow much smoother operation if any problems occur in the future, and should also allow exchanges and 3rd party services to continue to operate even if zPIV is in maintenance mode.

Accumulator Code Refactor

The zPIV accumulator code has undergone a major refactor. Accumulators are one of the most essential components of the zerocoin protocol, and also one of the most computationally expensive parts of the protocol. This refactoring speeds up syncing and spending of zPIV by over 5x. The new code also allows for spending of zPIV with only 2 required mints occurring on the network after your mint has been added, whereas before 3 were required. This refactor allows for lighter resource load and a smoother user experience.

Money Supply Indexing

The exploit in libzerocoin threw off some of the wallet's internal money supply calculations for both the zPIV supply and the PIV supply. User's wallet's will automatically recalculate the supply on block 908001. User's also have the ability to recalculate supply using the startup flag reindexmoneysupply.

More Extensive Tracking of zPIV Supply Through RPC

More information has been added to the getinfo and getblock RPC calls, which now display the total zPIV supply as well as the balance for each zPIV accumulator.

Multisig GUI

Provides functionality which is currently only available through raw transactions. Multisignature addresses require signatures from multiple parties before coins belonging to the address are spent. Accessed through the File dropdown menu.

Credits

FAQ

  • Will I lose piv or zpiv?
    • No. Backup your wallet.dat again for good measure and never delete a wallet.dat file.
  • My wallet is stuck on block ?
    • Check if you're forked (Am I forked?) and then check if you're really on v3.0.5. If you're on the right version and chain, just hang tight and your wallet will find a good node to sync with eventually. Contact support if it's more than a few hours and the problem persists
  • My zPIV balance is incorrect
    • Contact support in discord or via the Support Portal. Please note that during the upgrade period and zerocoin maintenance mode there may be delays.
submitted by turtleflax to pivx [link] [comments]

Non-propagating dust transaction creation by pools needs to stop!

This is an issue that has led to unnecessary clogging of the network for a long time, yet it seems to be one that has been overlooked for some time.
For those who don't know: BLOCK REWARD = 12.5BTC + (SUM OF ALL TRANSACTION FEES MINED ON THAT BLOCK)
Most of the largest pools keep the transaction fee part of the block reward for themselves (i.e. they do not pay that out to miners.)
Here's what I'm talking about:
This is done by pools that do not pay out transaction fees to miners (Antpool is by far the worst offender.) The practice is only profitable to pools which retain the transaction fee part of the block reward for themselves. The pool constantly creates a large number of minable but non-propagating transactions by creating transactions which violate the network "dust" rule. This rule prevents payments of less than 0.00001BTC from being broadcast throughout the network. As a result the transaction gets "stuck" in the pool's node and as such can only be mined by them. They will attach a large fee to the transaction, which in turn lowers the priority of transactions with lower fees attached. This ensures that only transactions with the highest fees are included in the block they mine- leaving the transactions with lower fees attached unconfirmed, driving up the necessary transaction fee, wasting mining power mining transactions that server no other purpose other than to drive up transaction fees and allowing the pool to, in essence, refuse to mine transactions with a fee below a certain amount attached. Since the pool will mine it's own transactions, they can create a virtually unlimited number of these transactions, with many unconfirmed descendants, to serve their purpose depending on the state of the mempool, and since they do not pay out transaction fees to the miners, they will get back all the transaction fees they used to attach to these transactions. Algorithms determine how much of the block-space to "waste" in order to maximize the profit- since the mempool can be analyzed at any time, it can be determined exactly how many transactions to create and what fee to attach in order to mine the transactions with the highest fee attached and drive up the necessary fee to have a transaction confirmed along with the "smart-fee," while ensuring low fee transactions are mined by the pools that do not practice this strategy. The strategy pays highest when the mempool is above 1MB (the size of a block) or has quickly filled. It also is most profitable when the fee distribution and queue-time in the mempool is highly divided/distributed- this strategy can prevent lower-fee transactions that have been waiting a long time to confirm from replacing new transactions that have a high fee attached on a block.
In Summary:
  1. Pool creates many "dust" transactions and attaches a high fee to each.
  2. Dust transactions (transactions below 0.00001BTC) do not broadcast, so the pool is guaranteed to mine its own transactions and re-collect the high fees they attached to the transaction.
  3. Pool now only mines outside transactions with the highest fees (per kB) attached, leaving the low-fee transactions to be mined by pools which do not practice this while simultaneously driving up the fee necessary to have a transaction confirmed.
Example:
https://www.blockchain.com/en/btc/tx/c57ea54104bbf160bac88b65b2edf465c5f8ac9253c42e391100fc31b028d645
If you click on the address, you can see this exact transaction is repeated exactly every hour (which sends a fixed amount back to itself and an address that cannot be decoded, due to the nature of the transaction, being sent 0BTC- which is what makes this a dust transaction.) If you go back to the block this transaction was originally confirmed (mined) on (by Antpool) you will see tons of similar transactions. In fact, Antpool has hundreds, if not thousands, of addresses used solely for this purpose. The practice is much more calculated and complex (in actual practice) than I summarized above. Eventually (or sometimes even on the same block) the divided outputs created by each transaction you see on that account would/will be concatenated into a single output over an additional series of combining, non-broadcasting, "dust" transactions.
Can it technically be considered a fair practice?
While their are plenty of valid reasons to create non-propagating transactions, such as to concatenate inputs left with dust amounts of bitcoin after valid transactions, without risking loosing the entire amount due to the minimum transaction fee being larger than the total amount, creating transactions like this with no other purpose than to increase a pools own profits is hard to argue as being a honorable one. Furthermore, since this practice is overall detrimental to the network (filling blocks with loads of unnecessary transactions, slowing confirmation times and artificially manipulating the necessary transaction fees) and in addition penalizes pools which pay the transaction fee part of the block reward to miners (since the practice cannot be performed by such pools, as it would cost the pool far too much,) as well as the fact that THE MINERS- THE ONES ACTUALLY CONTRIBUTING THE MINING POWER ARE NOT BENEFITING, I think it is safe to say that this practice is a deplorable one. Yes, one could argue that this is a loophole and exploiting it is going to be a natural occurrence, but I believe that since it encourages pools not to pay the transaction fee part of the block reward to miners, it is a practice that should not continue.
What to do about it?
There are a few options:
You can try if you run a full-node, but...: I for instance run a full node on a high bandwidth, fixed IP and allow incoming connections. I allow more connections in the command line options and maintain a few hundred connections at once. I noticed a few pools started automatically connecting to my node (I had to do some nmap scanning and some other testing to confirm they were indeed pool nodes, and who they belonged to, but was able to determine that- my first clue was multiple connections from bitcoinj nodes in the same subnet.) I was also able to find the addresses of other pool nodes and manually add them with the `addnode' command. So, with multiple pools connected (or the ability to connect to multiple pools upon restart,) I tweaked my node to allow for the broadcast of both zero-fee and dust transactions. My thinking was that I could serve as an unknowing "bridge" between pools- broadcasting one pools "dust" transactions to another, thereby removing the pool's ability to ensure that the transaction was not mined by another pool and making the practice unprofitable.
BUT... While this sounds good in theory, in practice it doesn't work for a few reasons. First of all, the pool nodes would not connect to me once I started broadcasting dust transactions. Second, I noticed my overall connection count way down, leading me to believe that broadcasting dust transactions was causing me to be labeled as a misbehaving node and finally, while this could work for some less advanced pools, Antpool, at least, designs its dust transactions in such a way that they violate more than just the "dust" rule- further tweaking would be required and this would need to be an action taken by a majority of nodes to work.
The only other option, I suppose, would be to appeal to the bitcoin dev team. Perhaps they could implement a way to prevent this practice, although I do not likely see it happening. The "dust" rule is in place to prevent clogging of the network with tiny transactions- to prevent anyone wishing to back-up the network from being able to do so without spending a large sum of money. The dust rule and the minimum transaction fee go hand in hand to prevent such occurrence- so anyone wishing to do harm to the network would soon find themselves spending very large amounts of BTC in an attempt to back it up- pools which retain the transaction fee however are not bound by these limitations.
The only real option to fight this, as a miner, is to mine on a pool that pays the transaction fee part of the block reward to the miners- you'll make more anyway, even if the overall fee may be slightly higher. An example of one of these pools is KANO, there are many others. I would just avoid antpool in general- but that's just me.
tl;dr
Pools which retain the transaction fee part of the block reward use a loophole is a network rule that allows them to only mine high fee transactions, which in turn hurts pools that pay the transaction fee part of the block reward to miners, clogs up the network- slowing confirmation times, and drives up transaction fees.
submitted by Mypassispass123 to Bitcoin [link] [comments]

How to Mine BiblePay on Windows

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/
Windows Guide: 1. Download 32 or 64 bit .exe from https://www.biblepay.org/wallet/ 2. Double Click / Run .exe file and step through Install process 3. Run BiblePay 4. Click Tools >> One Click Mining, (Or set up mining manually with steps a through d below)
     a. Open File Explorer, in address bar type: %appdata%      b. Press Enter      c. Go to BiblepayEvolution folder      d. Open biblepay.conf file for editing, add lines and Save
addnode=node.biblepay.org gen=1 genproclimit=1 
NOTE: addnode is used to give the wallet a starting node to connect to and sync with gen=1 turns on mining by default when the wallet is opened genproclimit=1 sets number of mining threads to 1 by default

5. Close BiblePay and Run it again 6. In BiblePay, go to Tools menu, Click Debug Console 7. Type these commands into the debug console:
getinfo getmininginfo help 
NOTE: getinfo will show you what block number your wallet is currently on and the version number getmininginfo will show you how many threads are running and how much mining hash you have help will show you all the other commands you can use

Threads: 8. To change number of threads to use up for mining
a. Edit %appdata%/BiblepayEvolution/biblepay.conf file: Find with File Explorer or inside the wallet go to Menu >> Tools >> Open Wallet Configuration File
genproclimit=X 
and restart BiblePay -or- b. Menu >> Tools >> Debug Console >> Type command:
setgenerate true X 
(Replace X with the number of threads you want to use Open Task Manager to view CPU usage)

Using the 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 (NOTE: Your Worker Username needs to be unique)
  3. Enable pool and add Worker Username in %appdata%/BiblepayEvolution/biblepay.conf file, add these lines:
    pool=https://pool.biblepay.org workerid=insertWorkerUsernameHere
4. Restart BiblePay
How to Withdraw Coins From Pool? The pool holds onto your coins, go to "Account" >> "Withdraw" to withdraw your coins In your BiblePay Wallet go to "File" >> "Receiving Address" and you can right click and copy the address and paste it into the Pool's Withdraw screen as the "Destination Address", then click the "Withdraw" button and the coins will be sent from the Pool to your Wallet
Setup Auto-Withdraw Navigate to Account >>> Account Settings >>> Verify your BBP Receiving Address >>> Click Authorize-Auto-Withdraws
Why use a Pool? As the network hash rises (as more miners are mining), it can take longer and longer to solve a block, by using the pool, everyone works together with all of their hash power to solve blocks, and the reward gets split between everyone who contributed based on how much they contributed in hash.
With solo mining (not using the pool) it may take 1 month to finally solve a block and get large BBP reward, with pool you can get small frequent BBP rewards every ~30 minutes. (BBP meaning BiblePay coins)

How to Update: Download exe from biblepay.org and install again, your wallet will stay intact

Backup:
Your wallet.dat stores your private keys that contain the access to your coins, this file is backed up every 24 hours in the backups folder, We also recommend that you save a copy of this file in other places, like a flash drive
Learn More about Backing Up your Wallet.dat https://www.reddit.com/BiblePay/comments/7lksp4/backup_walletdat/

FAQ
QUESTION: How long does it take for coins to mature? If you're solo mining, the coins become mature after ~100 blocks. If you're using the pool, they become mature after 24 hours
QUESTION: How do I know if I am currently mining? In your wallet >> In Top left Menu select "Tools" >> Click "Debug Console" Type in the command: getgenerate If it returns true, mining is turned on command: getmininginfo Will show how much "hashps" (hashing) your pc is doing, "genproclimit" will show how many mining threads you are using "poolmining" will be show value of true if you are successfully mining on the pool

How to Buy or Sell BBP coins?
You can buy and sell BBP coins for Bitcoin on the Exchanges we are listed on: SouthXChange: https://www.southxchange.com/Market/Book/BBP/BTC CoinExchange.io: https://www.coinexchange.io/market/BBP/BTC

Misc: Building headless Bitcoin and Bitcoin-qt on Windows https://bitcointalk.org/index.php?topic=149479.0 https://msdn.microsoft.com/en-us/commandline/wsl/install_guide https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux https://bitcointalk.org/index.php?topic=2388064.msg27133702#msg27133702 https://github.com/OleEichhorn/bitcoin-msvc

OUTDATED
Windows Mining Video Tutorial by copper101great https://www.youtube.com/watch?v=K1yKx8KsH60
submitted by togoshige to BiblePay [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]

Bitcoin ABC 0.18.8 released!

Bitcoin ABC version 0.18.8 is now available from:
https://download.bitcoinabc.org/0.18.8/
This release includes the following features and fixes: - dumpwallet now includes hex-encoded scripts from the wallet in the dumpfile - importwallet now imports these scripts, but corresponding addresses may not be added correctly or a manual rescan may be required to find relevant· transactions - getblock 2 (verbosity = 2) now returns hex values in transaction JSON blobs - Remove miner policy estimator in favor of minimum fees, also remove fee_estimates.dat. Old copies will be left in place. - The log timestamp format is now ISO 8601 (e.g. "2019-01-28T15:41:17Z") - Behavior change: in case of multiple values for an argument, the following rules apply: - From the command line, the last value takes precedence - From the config file, the first value takes precedence - From the config file, if an argument is negated it takes precedent over all the previous occurences of this argument (e.g. "foo=2 \n nofoo=1" will set foo=0) - The configuration files now support assigning options to a specific network. To do so, sections or prefix can be used: main.uacomment=bch-mainnet test.uacomment=bch-testnet regtest.uacomment=bch-regtest [main] mempoolsize=300 [test] mempoolsize=200 [regtest] mempoolsize=50 The addnode=, connect=, port=, bind=, rpcport=, rpcbind= and wallet= options will only apply to mainnet when specified in the configuration file, unless a network is specified.
submitted by jasonbcox to BitcoinABC [link] [comments]

Trying to salvage some coins from 2013. Core (bitcoin-qt.exe v0.8.1-beta on Windows 8.1) is taking weeks to DL the blockchain as expected but keeps crashing now. Can I upgrade to a newer version without losing what I've gotten already (about 75% complete)?

Currently there are 134305 blocks remaining. When I start it up it works pretty smoothly for a while but then slows down. I leave it running while I'm gone but the last several days when I've come back it has crashed and gives me an I/O error, and I have to hit OK then start it back up. It does appear to be further along when I start it back up but not by a whole lot. So this has really slowed my progress. It's reindexed about 75% though, and so I don't want to start over from the beginning.
The drive it is on has ~400gb of free space so that's not the issue. I have 8gb of memory, and the task manager says bitcoin is taking up about 500mb, but it's using 60-85% of my cpu at a time.
If I download a newer version of core, I can just copy/paste the old wallet.dat file, right? But wouldn't it have to start downloading the entire blockchain again from the beginning? If so, is there any quicker method?
While typing this, it crashed twice. It only runs for about 10 minutes.
The version I have doesn't have any settings I can change. I read that there's a db size limit you can change in later versions that could help. This one does have a "debug window" with a command line console but I don't really know what to do with it. Here is a list of available commands: 
addmultisigaddress <'["key","key"]'> [account]
addnode
backupwallet
createmultisig <'["key","key"]'>
createrawtransaction [{"txid":txid,"vout":n},...] {address:amount,...}
decoderawtransaction
dumpprivkey
encryptwallet
getaccount
getaccountaddress
getaddednodeinfo [node]
getaddressesbyaccount
getbalance [account] [minconf=1]
getblock
getblockcount
getblockhash
getblocktemplate [params]
getconnectioncount
getdifficulty
getgenerate
gethashespersec
getinfo
getmininginfo
getnewaddress [account]
getpeerinfo
getrawmempool
getrawtransaction [verbose=0]
getreceivedbyaccount [minconf=1]
getreceivedbyaddress [minconf=1]
gettransaction
gettxout [includemempool=true]
gettxoutsetinfo
getwork [data]
help [command]
importprivkey [label] [rescan=true]
keypoolrefill
listaccounts [minconf=1]
listaddressgroupings
listlockunspent
listreceivedbyaccount [minconf=1] [includeempty=false]
listreceivedbyaddress [minconf=1] [includeempty=false]
listsinceblock [blockhash] [target-confirmations]
listtransactions [account] [count=10] [from=0]
listunspent [minconf=1] [maxconf=9999999] ["address",...]
lockunspent unlock? [array-of-Objects]
move [minconf=1] [comment]
sendfrom [minconf=1] [comment] [comment-to]
sendmany {address:amount,...} [minconf=1] [comment]
sendrawtransaction
sendtoaddress [comment] [comment-to]
setaccount
setgenerate [genproclimit]
settxfee
signmessage
signrawtransaction [{"txid":txid,"vout":n,"scriptPubKey":hex,"redeemScript":hex},...] [,...] [sighashtype="ALL"]
stop
submitblock [optional-params-obj]
validateaddress
verifymessage

submitted by closer_to_the_flame to Bitcoin [link] [comments]

Having Connection Errors?

Those facing difficulty connecting to the network during initial the sync:
  1. Visit this link.
  2. Pick one of the IP addresses listed.
  3. Execute the following command using the MicroBitcoin CLI, or in the QT wallet's debug window:
addnode SELECTED_IP_HERE add
The application should find and connect with peers on the network. See wiki post here.
submitted by microbitcoinorg to MicroBitcoinOrg [link] [comments]

Please keep your nodes up to date ahead of the fork.

Taking the opportunity of the 0.14.4 release to remind everyone that it's important that you keep your ABC installations up to date before the fork on August 1.
A fork is a special event, we need to bring along as many nodes as possible.
So, you must make sure your node has other ABC peers.
For now, we are only a small part of the overall Bitcoin network, but we need to be as strong and well-connected to each other as possible.
Familiarize yourself with the addnode RPC command , or RPC commands in general, if you have not yet. You can execute these through the Debug console if you are using the GUI , or directly on the command line using the bitcoin-cli utility .
You can find a list of other up-to-date ABC nodes by querying bitnodes.21.co , e.g.
https://bitnodes.21.co/nodes/?q=Bitcoin%20ABC:0.14.4
Adapt the version number in that string to whatever the latest release of ABC is, to get a listing of network nodes that are upgraded to that version.
If you want to list all ABC nodes detected by bitnodes, omit the final version number:
https://bitnodes.21.co/nodes/?q=Bitcoin%20ABC
Add some ABC nodes which are fully synched to your active peer list if you have none .
Thanks!
submitted by ftrader to BitcoinABC [link] [comments]

Gridcoin Developer Update April 23rd, 2018

Hello folks and welcome to another Developer Update from the Gridcoin team. I'd like to remind everyone that these posts will be created every two weeks unless a wallet update is pending that week.
 
These last two weeks, developers have been preparing for an upcoming leisure update and finalizing fixes currently in staging branch. Testnet has been busy as well testing various new features and verifying fixes. Some of the pull requests these last two weeks have included:
 
In addition to the PRs listed above, @ifoggz has been working with the testing team to improve performance and better handle errors in the current Windows neural network implementation. So far these tests have been positive and show greatly improved consensus among neural nodes. In particular an issue was found when the downloaded gz files from project sites were incorrectly formatted. In the past, the NN would simply accept the bad data and try to use it for calculations resulting in wildly inaccurate magnitudes and hashes. The new improved NN code will recognize badly formatted project data files and prevent their bad data from being included in NN calculations. The new NN code will also try to redownload the excluded bad data on the next sync.
I would like to thank personthingman2 for all his help assisting in this testing.
 
I would like to add a quick update on testnet. I gave a "Introduction to Testnet" talk on the last Fireside podcast. Thanks to @jringo for having me and I look forward to hearing the edited audio once it is finalized. The goal of this talk was to educate people about testnet and bring new testers on board.
 
Thanks for reading this edition of the Developer Update. Expect to see another update two weeks from today (5/7), barring a wallet update around that time. If you have any comments or questions for the Gridcoin development team feel free to ask in the comments below. If I am not able to answer your question directly, I can certainly forward it to someone who can! Thanks everyone!
submitted by barton26 to gridcoin [link] [comments]

Bitcoin cash blockchain craziness (missing BCC)

Before doing anything with BCC, I transferred my BTC from one bitcoin address (old address) to another (new address), a total of 2.05 BTC. I only had one address in my wallet (old address) when I started.
So, I installed the Bitcoin ABC client and completely synched with the Bitcoin Cash blockchain, after copying my blockchain data from the core data directory, addnode'ng the Bitcoin Cash nodes to the .conf file, starting with a brand spanking new fresh wallet, and issuing the following command to pick up the correct blocks after the fork:
invalidateblock 00000000000000000019f112ec0a9982926f1258cdcc558dd7c3b7e5dc7fa148 
I then proceeded to import my (old address) private key:
importprivkey ... 
..., into Bitcoin ABC and waited (patiently) for the rescan to complete.
The crazy part: I was 1 BCC short - it showed 1.05 BCC instead of 2.05 BCC. So, I went back into my core wallet, copied the entire list of transactions to a spreadsheet and compared them to the list of transactions in the ABC client to see what the heck happened.
The ABC client transaction list shows two 0.5 BTC withdrawals (from the old address) circa 2016, that never happened and this is the reason that I am 1 BCC short in the end.
I don't know how this is possible. The withdrawals were all from around mid to late 2016, way before this fork happened, and that part of the blockchain is common to both. Since I was able to transfer the entire 2.05 BTC from my old BTC address to a new BTC address before I started, with >10 confirmations, I definitely know that I had 2.05 BTC at the old address, the only address I used until after the fork.
If anybody has any ideas on how this is possible, or what steps I should take next to reconcile my BCC amount with my BTC amount pre-fork, I am all ears.
submitted by mikegold10 to BitcoinABC [link] [comments]

replace-by-fee v0.10.0rc4 | Peter Todd | Feb 12 2015

Peter Todd on Feb 12 2015:
My replace-by-fee patch is now available for the v0.10.0rc4 release:
[https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.10.0rc4](https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.10.0rc4) 
Along with demo scripts of the functionality:
[https://github.com/petertodd/replace-by-fee-tools](https://github.com/petertodd/replace-by-fee-tools) 
New to this version is a comprehensive set of unittests under
qa/replace-by-fee
Additionally the preferential peering support now preferentially peers
with Bitcoin XT¹ nodes that support Andresen/Harding's double-spend
relaying² patch. While Bitcoin XT nodes don't accept double-spends into
their mempool, they do relay them perfectly well and thus are an asset
to those doing replace-by-fee mining.³
I've had a number of requests from miners for a version of
replace-by-fee against Luke-Jr's Eligius patches⁴; I'll be also
releasing that shortly once this release has undergone some more
testing.
What's replace-by-fee?
Currently most Bitcoin nodes accept the first transaction they see
spending an output to the mempool; all later transactions are rejected.
Replace-by-fee changes this behavior to accept the transaction paying
the highest fee, both absolutely, and in terms of fee-per-KB. Replaced
children are also considered - a chain of transactions is only replaced
if the replacement has a higher fee than the sum of all replaced
transactions.
Doing this aligns standard node behavior with miner incentives: earn the
most amount of money per block. It also makes for a more efficient
transaction fee marketplace, as transactions that are "stuck" due to bad
fee estimates can be "unstuck" by double-spending them with higher
paying versions of themselves. With scorched-earth techniques⁵ it gives
a path to making zeroconf transactions economically secure by relying on
economic incentives, rather than "honesty" and alturism, in the same way
Bitcoin mining itself relies on incentives rather than "honesty" and
alturism.
Finally for miners adopting replace-by-fee avoids the development of an
ecosystem that relies heavily on large miners punishing smaller ones for
misbehavior, as seen in Harding's proposal⁶ that miners collectively 51%
attack miners who include doublespends in their blocks - an unavoidable
consequence of imperfect p2p networking in a decentralized system - or
even Hearn's proposal⁷ that a majority of miners be able to vote to
confiscate the earnings of the minority and redistribute them at will.
Installation
Once you've compiled the replace-by-fee-v0.10.0rc4 branch just run your
node normally. With -debug logging enabled, you'll see messages like the
following in your ~/.bitcoin/debug.log indicating your node is replacing
transactions with higher-fee paying double-spends:
2015-02-12 05:45:20 replacing tx ca07cc2a5eaf55ab13be7ed7d7526cb9d303086f116127608e455122263f93ea with c23973c08d71cdadf3a47bae45566053d364e77d21747ae7a1b66bf1dffe80ea for 0.00798 BTC additional fees, -1033 delta bytes 
Additionally you can tell if you are connected to other replace-by-fee
nodes, or Bitcoin XT nodes, by examining the service bits advertised by
your peers:
$ bitcoin-cli getpeerinfo | grep services | egrep '((0000000000000003)|(0000000004000001))' "services" : "0000000000000003", "services" : "0000000004000001", "services" : "0000000004000001", "services" : "0000000000000003", "services" : "0000000004000001", "services" : "0000000004000001", "services" : "0000000000000003", "services" : "0000000000000003", 
Replace-by-fee nodes advertise service bit 26 from the experimental use
range; Bitcoin XT nodes advertise service bit 1 for their getutxos
support. The code sets aside a certain number of outgoing and incoming
slots just for double-spend relaying nodes, so as long as everything is
working you're node should be connected to like-minded nodes a within 30
minutes or so of starting up.
If you don't want to advertise the fact that you are running a
replace-by-fee node, just checkout a slightly earlier commit in git; the
actual mempool changes are separate from the preferential peering
commits. You can then connect directly to a replace-by-fee node using
the -addnode command line flag.
1) https://github.com/bitcoinxt/bitcoinxt
2) https://github.com/bitcoin/bitcoin/pull/3883
3) https://github.com/bitcoin/bitcoin/pull/3883#issuecomment-45543370
4) https://github.com/luke-jbitcoin/tree/0.10.x-ljrP
5) http://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg05211.html
6) http://www.mail-archive.com/[email protected]/msg06970.html
7) http://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg04972.html

'peter'[:-1]@petertodd.org
000000000000000013c290b77d45d2ea7f9220aedfadfd556ad41b6bd39822f3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 650 bytes
Desc: Digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150212/a1703e85/attachment.sig>
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-February/007404.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

Experimenting with BU bitcoin-qt and Core bitcoin-qt.

I have an existing ubuntu box that has an up to date block chain running core bitcoin-qt. I've connected another ubuntu box with BU bitcoin-qt that has no blocks. They are connected through a router with DNS. I've run the BU with the command line "bitcoin-qt -addnode=192.168.1.100", where 192.168.1.100 is the core box.
Core and BU qt clients connect, but no blocks are sent from the Core box to the BU box. Any suggestions on how to trouble shoot this, or is core now refusing to talk to BU?
submitted by PastaArt to bitcoin_unlimited [link] [comments]

BIP150/151 concerns and some comments | Jonas Schnelli | Feb 14 2017

Jonas Schnelli on Feb 14 2017:
Hi
Recently I read some concerns about BIP150/151 and its „identity system“.
I think we should take those concerns seriously and I wrote some
comments for some of the concerns I'm aware of. In my opinion, most of
these worries are unfounded.
Concern 1: BIP150 introduces a identity system that could partition the
network
command, peer banning in app-layer. Fast block relay is a good example
(example: FIBRE).
obviously not ideal) to a secure form of authentication with pre-shared
keys (ECDH).
valid reasons to do that
Concern 2: But BIP150 makes it simpler and increase the risk of network
partitioning
Signal) and store in on both peers or calling a „addnode “, or
„iptables-DROP “?
Concern 3: Identity is not something we want in Bitcoin
EC pubkey can be changed. It’s different per network interface. You only
reveal it to peers that already have proven the know your identity.
different to hide.
Concern 4: But peers can fingerprint my node and ban me after BIP150 has
been deployed
your identity unless the responding peer has proven he knows your identity.
Concern 5: BIP150/151 is not necessary, we have already Tor and STunnel,
etc.
technologies? Using tor for a single secure channel seems like using
a sledgehammer to crack a nut.
it accessible for the novice user?
what security do they have today (IP address, really?)?
security enhancement (encrypt twice). IMO the focus of Tor is not on
securing single channels (it's rather onion routing / anonymity).
Concern 6: BIP151 gives a false sense of security and has no MITM detection
what’s going on. With BIP151, an attacker needs to actively substitute
ephemeral keys in both direction. This attack is A) more complex to
achieve and B) it’s an active attack (no excuse of „I just made some
statistics“), C) it requires the attacker to accept the risk of being
detected.
different) would reveal the attack.
Concern 7: But Bitcoin traffic is trustless, why the hell you want to
encrypt it?
your complete wallet content („~all your addresses") to every network
observer between you and the node you have connected to. This means, if
you pay for a coffee (while being on the owners WIFI), the coffee owner
and all the involved ISPs can correlate your wallet with your other
internet behavior. Same is true for your cellphone provider if you use
cellular.
attack that involves the risk mentioned in Concern 6.
Concern 8: If you want to have a light client, you should use a
different channel to communicate with your full node then the p2p layer
port, lack of a (RPC / ZMQ, etc.) standard, no fallback option if the
trusted node is down, hard to setup)
me. Keep the users on the p2p layer! If we don’t want the users on that
channel, we automatically form a different layer, the wallet-com wild-west.
they can help the network in some ways.
anytime to non-trusted nodes (if your trusted node is no longer
reachable). If your SPV peer needs to catch up a couple of hours while
your trusted peer was done, fine, download full blocks or change your
bloom filters FP rate significant (or sacrifices your privacy in this case).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170214/8559c0c1/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170214/8559c0c1/attachment-0001.sig
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-February/013580.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

My full node starts to get stuck on pruned nodes, is bitcoin network starts to get congested?

My full node got stuck on bloom nodes that does not let download new blocks. I am using addnode x.x.x.x onetry commands more than ever to connect back to full nodes. Is bitcoin network slowly dying?
submitted by johnjacksonbtc to Bitcoin [link] [comments]

Bitcoin Debug Console Issues

Hello Everyone
I have the latest version of BitcoinQt downloaded from bitcoin.org when i try to run the command addnode to whatever the ip of the node is i get this error message Method not found error code (-32601)
Is there any way to fix this?
submitted by Xercanion to Bitcoin [link] [comments]

Old bitcoin version.. no news in iceland... Convince me this isn't a scam?

0.6.3 is the bitcoin client, missing quiet a few commands (such as addnode)...
Iceland you would expect to have lots of PR by now with the drop not far away... but nothing.
What is there about this coin that makes you believe in it?
submitted by darrenturn90 to auroracoin [link] [comments]

[P2pool] How to make your own personal p2pool Node!

Tired of getting no block rewards and sending many dead shares? Need a p2pool node close to your miner? MAKE YOUR OWN! :D
And, Yep, P2pools give 0.5% Rewards to block finders!
Here's some info about p2ools: http://whatisp2pool.com/
The stronger the P2Pool network becomes the more resistant the digibyte network is to 51% attacks!
Oh and, P2pools are DDOS proof! Now that's News! So if your node gets DDOS'd .. you dont lose your shares as the shares have been saved in the p2pool, its called the sharechain. So you get paid anyhow! Thanks to the p2pool network. and you ccan set your workers to another pool using the "--failover only" command in cgminer (if im not wrong) and get it back to work on the p2pool network!
TL;DR; P2POOL = 1 Big fat network Decentrazlized pool!
STEPS TO MAKE A P2POOL:
Install Ubuntu server or Desktop if you want http://www.ubuntu.com/download/ or u can use a VPS (VirtualPrivateServer -- Link Below with coupon code)
So Let's start off in the command line (Open Terminal.. and all you have to do is Cut, Copy Paste! ;) )
Start by updating and upgrading Ubuntu, you know you want the best ;)
sudo apt-get update sudo apt-get upgrade sudo apt-get install python-software-properties sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update 
Time for the DigiByteProject dependencies!
sudo apt-get install build-essential libboost-all-dev libcurl4-openssl-dev libdb5.1-dev libdb5.1++-dev git qt-sdk libminiupnpc-dev sudo apt-get install qrencode libqrencode-dev 
And, Now to compile DigiByte on your system!
git clone git://github.com/digibyte/DigiByteProject.git digibyte #renaming makes it easier ;) cd ~/digibyte/src mkdir obj make -f makefile.unix USE_UPNP=- sudo cp digibyted /usbin cd ~ 
After it has compiled try running 'digibyted'
./digibyte/src/digibyted 
If you get an error saying you need to make the digibyte.conf file, good! :) If it doesnt give you that error, make sure you followed the compiling steps appropriately.
So, Lets create the conf file here...
cd .digibyte #edited from 'digibyted' .. fixed!! nano digibyte.conf 
Paste the following, CHANGING THE USERNAME AND PASS!! make sure to take note of both, you'll need these later!
rpcuser=CHANGEusername rpcpassword=ChangePassword daemon=1 server=1 rpcport=14022 port=12024 gen=1 rpcallowip=127.0.0.1 addnode=74.208.230.160 addnode=31.220.25.91 addnode=184.155.218.183 addnode=24.119.23.61 addnode=70.196.193.231 addnode=198.98.118.241 addnode=142.4.204.115 addnode=23.90.191.58 addnode=216.250.125.121 addnode=115.28.31.25 addnode=83.172.105.46 
Press 'CTRL' + ' X', and then 'Y' to save when prompted
cd ~ ./digibyte/src/digibyted ./digibyte/src/digibyted getinfo 
Make sure you check the latest block in the block chain or on your local DigiByte Wallets. This is to see how far your p2pool node has gotten! This is gonna take quite a while so lets CONTINUE!
Let's get the p2pool software and frontend in! Install the p2pool dependencies!
sudo apt-get install python-zope.interface python-twisted python-twisted-web git clone https://github.com/Rav3nPL/p2pool-rav p2pool #renaming it! cd ~/p2pool/digibyte_subsidy #Thanks to Chaeplin sudo python setup.py install 
Time to edit and customise the html code to personalise your p2pool's frontend. Feel free to change the p2pool name and if you're an advanced user, feel free to add your own frontend from git hub after removing the web-static folder. (OPTIONAL: by using rm -f -r web-static #in that directory. And then you can choose whichever frontend you want! by cloning it in the web-static folder)
Editing the current frontend html!
cd .. cd web-static nano index.html 
After personalising the page, i.e. changing the p2pool name and adding some info! Lets go back and check how far the block downloading has gotten! You can check this by typing this in the command line after going back to the root directory:
cd ~ ./digibyte/src/digibyted getinfo 
This is gonna take a while so might as well check for updates again :P
sudo apt-get update sudo apt-get upgrade 
After making sure that all the blocks have been synced locally! We're ready to run the p2pool node! Simply enter the string below in the command line, entering your USERNAME and PASS that you saved earlier!
screen -d -m -S myp2pool ~/p2pool/run_p2pool.py --give-author 0 --net digibyte NEWUSER NEWPASS --outgoing-conns 4 
If you want to charge a fee for your node add this to your string, adding your fee address!:
--fee 1.0 --address NEWDGBADDRESS 
To see if the node is up and running enter this in the command line:
screen -x myp2pool 
'CTRL' + 'A' + 'D' to close the terminal if you press 'CTRL' + 'C', it will terminate the p2pool program and you'll have to restart the pool by using the string above!
Once, Everything is setup as planned! Check your p2pool node's ip Address by entering this into the command line:
ifconfig 
inet addr: 192.168.1.1 #You'll see a line like this.
So, Your cgminer string should look something like this:
cgminer --scrypt -o 192.168.1.1:9022 -u DGBADDRESS -p x
And your p2pool WEB ADDRESS should look like this:
192.168.1.1:9022
example: http://192.168.1.1:9022/
You can monitor your p2pool using that web address! Enjoy, your personal p2pool node!! :D
If for whatever reason the server shuts off and you need to restart the p2pool node, you should run digibyted again and after it has synced successfully, just type in your p2pool string:
./digibyte/src/digibyted
screen -d -m -S myp2pool ~/p2pool/run_p2pool.py --give-author 0 --net digibyte NEWUSER NEWPASS --outgoing-conns 4 --fee 1.0 --address NEWADDRESS
PRESS CTRL + A + D to Detach from screen
UPDATE Follow Guide below if you used this guide before DigibByte v2.0 was released (28th Feb 2014)
You must check whether you're on the right ShareChain. Make Sure the block Value says 7960!
https://bitcointalk.org/index.php?topic=408268.msg5440858#msg5440858
This Tutorial was made with the help of an existing Guide: http://doges.org/index.php?topic=5586.0 Kudos to crypto49er!
If you want to do this on a VPS:
Here's a link to a VPS hosting site:
https://www.digitalocean.com/
Feel free to use my $10 ref. code -- it doesnt really make a difference, though.
https://www.digitalocean.com/?refcode=dc909c442664
Let me know if this guide helped!
submitted by StormMiner to Digibyte [link] [comments]

9. bitcoind 15. Bitcoin over Tor 1337 Installing wallet and add nodes tutorial (details in description) How to Install Latest PIECOIN Wallet - add Active Nodes, Setup Security and Backup How To: add a node to the iop core wallet

To interact with Bitcoin Core daemon, you will use the command bitcoin-cli (Bitcoin command line interface). If you installed Bitcoin Core into the default location, type the following at the command prompt to see whether it works: C:\Program Files\Bitcoin\daemon\bitcoin-cli getblockchaininfo Note: it may take up to several minutes for Bitcoin Core to start, during which it will display the ... ./bitcoin-qt Command-line arguments . These commands are accurate as of Bitcoin Core version v0.14 .0. ... ## ##### # Use as many addnode= settings as you like to connect to specific peers #addnode=69.164.218.197 #addnode=10.0.0.2:8333 # Alternatively use as many connect= settings as you like to connect ONLY to specific peers #connect=69.164.218.197 #connect=10.0.0.1:8333 # Listening mode ... here is the node list from my account go into the console and use the command Addnode <IP> ex Addnode 193.70.47.2:4200 193.70.47.2:420 … bitcoin-qt command line arguments. GitHub Gist: instantly share code, notes, and snippets. Skip to content. All gists Back to GitHub Sign in Sign up Sign in Sign up {{ message }} Instantly share code, notes, and snippets. donpdonp / gist:4997294. Created Feb 20, 2013. Star 3 Fork 2 Star Code Revisions 1 Stars 3 Forks 2. Embed. What would you like to do? Embed Embed this gist in your website ... addnode=134.265.252.133 addnode=135.255.282.101 addnode=149.202.47.155 addnode=445.773.194.266 Method 1: Adding nodes from wallet debug console. You need to check this guide on QT core wallet where we’ve explained about debug console window. There are so many command line options available for a wallet and one among them is addnode command ...

[index] [51504] [46374] [5070] [23184] [22255] [18381] [39877] [11673] [21112] [47987]

9. bitcoind

You'll have to open the console and add each active node one at a time with the command "addnode 82.165.162.27 add" (Minus quotes, just change the IP address with the active node lists on the site. this video shows how to add a node to the iop core wallet, if you have problems with the blockchain synchronization special thanks to @klewer _____... addnode=139.59.72.56:7118 addnode=159.89.152.81:7118 addnode=104.131.124.189:7118 addnode=73.24.58.144:7118 addnode=198.13.62.166:7118 addnode=128.199.201.17... Bitcoin from the Command Line - Sending Bitcoin Transactions Programmatically with Javascript - Duration: 17:07. Decypher Media 12,116 views. 17:07. Language: English ... Auf YouTube findest du großartige Videos und erstklassige Musik. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder mit der ganzen Welt teilen.

#