Bitcoind – Commands, RPC Protocol, Install Server ...

Fun with low fee TXNs on Mainnet

Here's a 0.493 sat/vB TXN I put on mainnet today. You'll have to use the SoChain block explorer to see it though. I give it a 3% chance of getting confirmed, but we'll wait and see. The TXN is a donation to [email protected] since I use their seeder for my network herder.
So last month, I voiced the unpopular opinion that node operators should lower the minrelaytxfee setting to allow low-fee TXNs to propagate more freely throughout the network. Then I asked why miners weren't mining 0.999 sat/vB TXNs during idle periods since it should be more profitable than mining no TXNs at all. Finally I wrote a node herder to walk the network looking for node operators that were running minrelaytxfee below the default (1000 sat). After walking about 26% of the network, turns out about 5% of nodes are allowing low fee TXNs.
So in that vein of discussion, I decided to just sign some low-fee TXNs and send them to the 5% of nodes I found and see what happens. To my surprise it showed up on one of the 23 block explorers I tried after broadcasting it. Surprisingly, that comes out to about 5% of explorers accepting low fee TXNs as well. So hopefully 5% or so of the miners will confirm low fee TXNs. We'll see.
BTW, to do this, this is what I did.
  1. Pair my HW wallet to Electrum
  2. Use the paytomany Electrum API to craft a TXN below 1 sat/vB
  3. Import the TXN to sign in Electrum
  4. Ran a full node with minrelaytxfee set to 1 sat (0.001 sat/vB)
  5. Walked the network to find a good number of low-fee peers
  6. Use bitcoin addnode API to herd my node to the low-fee peers I discovered.
  7. Use bitcoin sendrawtransaction API to broadcast TXN
Wait and see if it can propagate to a miner and if a miner will accept it.
BTW, there is a PR to lower the minrelaytxfee in core, but it's dragged on for years. The setting was lowered about every year or so in the early days, but hasn't been touched for many years now.
submitted by brianddk to Bitcoin [link] [comments]

[ANN][ANDROID MINING][AIRDROP] NewEnglandcoin: Scrypt RandomSpike

New England
New England 6 States Songs:
Symbol: NENG
NewEnglandcoin is a clone of Bitcoin using scrypt as a proof-of-work algorithm with enhanced features to protect against 51% attack and decentralize on mining to allow diversified mining rigs across CPUs, GPUs, ASICs and Android phones.
Mining Algorithm: Scrypt with RandomSpike. RandomSpike is 3rd generation of Dynamic Difficulty (DynDiff) algorithm on top of scrypt.
1 minute block targets base difficulty reset: every 1440 blocks subsidy halves in 2.1m blocks (~ 2 to 4 years) 84,000,000,000 total maximum NENG 20000 NENG per block Pre-mine: 1% - reserved for dev fund ICO: None RPCPort: 6376 Port: 6377
NewEnglandcoin has dogecoin like supply at 84 billion maximum NENG. This huge supply insures that NENG is suitable for retail transactions and daily use. The inflation schedule of NengEnglandcoin is actually identical to that of Litecoin. Bitcoin and Litecoin are already proven to be great long term store of value. The Litecoin-like NENG inflation schedule will make NewEnglandcoin ideal for long term investment appreciation as the supply is limited and capped at a fixed number
Bitcoin Fork - Suitable for Home Hobbyists
NewEnglandcoin core wallet continues to maintain version tag of "Satoshi v0.8.7.5" because NewEnglandcoin is very much an exact clone of bitcoin plus some mining feature changes with DynDiff algorithm. NewEnglandcoin is very suitable as lite version of bitcoin for educational purpose on desktop mining, full node running and bitcoin programming using bitcoin-json APIs.
The NewEnglandcoin (NENG) mining algorithm original upgrade ideas were mainly designed for decentralization of mining rigs on scrypt, which is same algo as litecoin/dogecoin. The way it is going now is that NENG is very suitable for bitcoin/litecoin/dogecoin hobbyists who can not , will not spend huge money to run noisy ASIC/GPU mining equipments, but still want to mine NENG at home with quiet simple CPU/GPU or with a cheap ASIC like FutureBit Moonlander 2 USB or Apollo pod on solo mining setup to obtain very decent profitable results. NENG allows bitcoin litecoin hobbyists to experience full node running, solo mining, CPU/GPU/ASIC for a fun experience at home at cheap cost without breaking bank on equipment or electricity.
MIT Free Course - 23 lectures about Bitcoin, Blockchain and Finance (Fall,2018)
CPU Minable Coin Because of dynamic difficulty algorithm on top of scrypt, NewEnglandcoin is CPU Minable. Users can easily set up full node for mining at Home PC or Mac using our dedicated cheetah software.
Research on the first forked 50 blocks on v1.2.0 core confirmed that ASIC/GPU miners mined 66% of 50 blocks, CPU miners mined the remaining 34%.
NENG v1.4.0 release enabled CPU mining inside android phones.
Youtube Video Tutorial
How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 1 How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 2
How to CPU Mine NewEnglandcoin (NENG) in macOS
Decentralization and Community Driven NewEnglandcoin is a decentralized coin just like bitcoin. There is no boss on NewEnglandcoin. Nobody nor the dev owns NENG.
We know a coin is worth nothing if there is no backing from community. Therefore, we as dev do not intend to make decision on this coin solely by ourselves. It is our expectation that NewEnglandcoin community will make majority of decisions on direction of this coin from now on. We as dev merely view our-self as coin creater and technical support of this coin while providing NENG a permanent home at ShorelineCrypto Exchange.
Twitter Airdrop
Follow NENG twitter and receive 100,000 NENG on Twitter Airdrop to up to 1000 winners
Graphic Redesign Bounty
Top one award: 90.9 million NENG Top 10 Winners: 500,000 NENG / person Event Timing: March 25, 2019 - Present Event Address: NewEnglandcoin DISCORD at:
Please complete above Twitter Bounty requirement first. Then follow Below Steps to qualify for the Bounty: (1) Required: submit your own designed NENG logo picture in gif, png jpg or any other common graphic file format into DISCORD "bounty-submission" board (2) Optional: submit a second graphic for logo or any other marketing purposes into "bounty-submission" board. (3) Complete below form.
Please limit your submission to no more than two total. Delete any wrongly submitted or undesired graphics in the board. Contact DISCORD u/honglu69#5911 or u/krypton#6139 if you have any issues.
Twitter Airdrop/Graphic Redesign bounty sign up:
NENG v1.4.0 Android Mining, randomSpike Evaluation
RandomSpike - NENG core v1.3.0 Hardfork Upgrade Proposal
NENG Security, Decentralization & Valuation
Whitepaper v1.0
Step by step guide on how to setup an explorer:
Android with UserLand App (arm64/armhf), Chromebook (x64/arm64/armhf):
Linux Wallet (Ubuntu/Linux Mint, Debian/MX Linux, Arch/Manjaro, Fedora, openSUSE):
MacOS Wallet (10.11 El Capitan or higher):
Android with GNUroot on 32 bits old Phones (alpha release) wallet:
Windows wallet:
addnode ip address for the wallet to sync faster, frequently updated conf file:
How to Sync Full Node Desktop Wallet
Cheetah CPU Miner Software
Solo Mining with GPU or ASIC
How to Run Two Full Node in Same Desktop PC
ASIC/GPU Mining Pools Warning to Big ASIC Miners Due to DynDiff Algo on top of Scrypt, solo mining is recommended for ASIC/GPU miners. Further more, even for mining pools, small mining pool will generate better performance than big NENG mining pool because of new algo v1.2.x post hard fork.
The set up configuration of NENG for scrypt pool mining is same as a typical normal scrypt coin. In other word, DynDiff on Scrypt algo is backward compatible with Scrypt algo. Because ASIC/GPU miners rely on CPU miners for smooth blockchain movement, checkout bottom of "Latest News" section for A WARNING to All ASIC miners before you decide to dump big ASIC hash rate into NENG mining.
(1) Original DynDiff Warning: (2) New Warning on RandomSpike Spike difficulty (244k) introduced in RandomSpike served as roadblocks to instant mining and provide security against 51% attack risk. However, this spike difficulty like a roadblock that makes big ASIC mining less profitable. In case of spike block to be mined, the spike difficulty immediately serve as base difficulty, which will block GPU/ASIC miners effectively and leave CPU cheetah solo miners dominating mining almost 100% until next base difficulty reset.
Cminors' Pool
Features: anonymous sign up and trading. No restriction or limit on deposit or withdraw.
The trading pairs available: NewEnglandcoin (NENG) / Dogecoin (DOGE)
Trading commission: A round trip trading will incur 0.10% trading fees in average. Fees are paid only on buyer side. buy fee: 0.2% / sell fee: 0% Deposit fees: free for all coins Withdraw fees: ZERO per withdraw. Mining fees are appointed by each coin blockchain. To cover the blockchain mining fees, there is minimum balance per coin per account: * Dogecoin 2 DOGE * NewEnglandcoin 1 NENG
Latest News Aug 30, 2020 - NENG v1.4.0.5 Released for Android/Chromebook Upgrade with armhf, better hardware support
Aug 11, 2020 - NENG v1.4.0.4 Released for Android arm64 Upgrade / Chromebook Support
Jul 30, 2020 - NENG v1.4.0.3 Released for Linux Wallet Upgrade with 8 Distros
Jul 21, 2020 - NENG v1.4.0.2 Released for MacOS Upgrade with Catalina
Jul 19, 2020 - NENG v1.4.0.1 Released for MacOS Wallet Upgrade
Jul 15, 2020 - NENG v1.4.0 Released for Android Mining, Ubuntu 20.04 support
Jul 11, 2020 - NENG v1.4.0 Android Mining, randomSpike Evaluation
Jun 27, 2020 - Pre-Announce: NENG v1.4.0 Proposal for Mobile Miner Upgrade, Android Mining Start in July 2020
Jun 19, 2020 - Best Practice for Futurebit Moonlander2 USB ASIC on solo mining mode
Mar 15, 2020 - Scrypt RandomSpike - NENG v1.3.0.1 Released for better wallet syncing
Feb 23, 2020 - Scrypt RandomSpike - NENG Core v1.3.0 Relased, Hardfork on Mar 1
Feb 1, 2020 - Scrypt RandomSpike Proposal Published- NENG 1.3.0 Hardfork
Jan 15, 2020 - NewEnglandcoin Dev Team Expanded with New Kickoff
Jan 12, 2020 - Explanation of Base Diff Reset and Effect of Supply
Dec 19, 2019 - Shoreline_tradingbot version 1.0 is released
Sept 1, 2019 - NewEnglandcoin (NENG) is Selected as Shoreline Tradingbot First Supported Coin
Aug 15, 2019 - Mining Update on Effect of Base Difficulty Reset, GPU vs ASIC
Jul 7, 2019 - CPU Mining on macOS Mojave is supported under latest Cheetah_Cpuminer Release
Jun 1, 2019 - NENG Fiat project is stopped by Square, Inc
Apr 21, 2019 - NENG Fiat Project is Launched by ShorelineCrypto
Apr 7, 2019 - Announcement of Fiat Project for all U.S. Residents & Mobile Miner Project Initiation
Apr 1, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange
Mar 27, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange
Mar 17, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange
Feb 26, 2019 - Community Project - NewEnglandcoin Graphic Redesign Bounty Initiated
Feb 22, 2019 - Dev Policy on Checkpoints on NewEnglandcoin
Feb 20, 2019 - NewEnglandCoin v1.2.1 Released to Secure the Hard Kork
Feb 11, 2019 - NewEnglandCoin v1.2.0 Released, Anti-51% Attack, Anti-instant Mining after Hard Fork
Jan 13, 2019 - Cheetah_CpuMiner added support for CPU Mining on Mac
Jan 12, 2019 - NENG Core v1.1.2 Released to support MacOS OSX Wallet
Jan 2, 2019 - Cheetah_Cpuminer v1.1.0 is released for both Linux and Windows
Dec 31, 2018 - Technical Whitepaper is Released
Dec 28, 2018 - Cheetah_Cpuminer v1.0.0 is released for Linux
Update on Dec 14, 2018 - NENG Blockchain Stuck Issue
Nov 27, 2018 - Exclusive for PC CPU Miners - How to Steal a Block from ASIC Miners
Nov 28, 2018 - How to CPU Mine a NENG block with window/linux PC
Nov 29, 2018 - A Warning to ASIC Miners
Disclosure: Dev Team Came from ShorelineCrypto, a US based Informatics Service Business offering Fee for service for Coin Creation, Coin Exchange Listing, Blockchain Consulting, etc.
submitted by honglu69 to NewEnglandCoin [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year(only pc-miner)

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode = (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to BitcoinMining [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode = (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to BitcoinSerious [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode = (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to altcoin_news [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.


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


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.


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.


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.


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.


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


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.


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".


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.


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.


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.


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.


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 or
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.


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.


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 Official Website Unofficial Website Block Explorer Block Explorer Faucet Faucet
Gridcoin Wiki
Gridcoin Github
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]

such beginner shibe thread wow how to get coin

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


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= addnode= addnode= addnode= addnode= addnode=miner.coinedup.comdoge addnode= addnode= addnode= 
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!


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 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.


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 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 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 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!


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.


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.


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

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.
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.
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.
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:
IMPORTANT - Evolution Upgrade:
Quick Start
Evolution Upgrade Information
Getting Started with Evolution
Generic Smart Contracts
What is BiblePay Evolution?
Windows Guide: 1. Download 32 or 64 bit .exe from 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 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
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
  1. Set up an account on pool website:
  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= 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 and install again, your wallet will stay intact

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

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:

Misc: Building headless Bitcoin and Bitcoin-qt on Windows

Windows Mining Video Tutorial by copper101great
submitted by togoshige to BiblePay [link] [comments]

How to Mine BiblePay on Linux

This guide is outdated, please refer to:
IMPORTANT - Evolution Upgrade:
Quick Start
Evolution Upgrade Information
Getting Started with Evolution
Generic Smart Contracts
What is BiblePay Evolution?
Recommend 2GB RAM or can get stuck compiling (if 1GB RAM can use Swap File) Use Ubuntu 16.04
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 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 .. ./ #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: # 

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 

cd src ./biblepayd -daemon 
Your GUI program will be located in: /biblepay-evolution/src/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!

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

./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:
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)

NOTE: To use the pool you must now use the external miner, not the wallet miner
  1. Set up an account on pool website:
  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= 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


### 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 

./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

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 

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/
people make cron jobs and rsync automatically


Unofficial Bash Script

Official Ubuntu Package

Unofficial Ubuntu Package

Unofficial Mine in One Line


DOCKER IMAGES (NOTE: I havent tested these, use at your own risk)
submitted by togoshige to BiblePay [link] [comments]

Bitcoin ABC 0.18.8 released!

Bitcoin ABC version 0.18.8 is now available from:
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]

F.Y.I. Syncing to UnitedBitcoin UBTC main net and performing desposits on exchange...

I'm sure some of you guys noticed that the compiled github sources wont be able to connect and sync to the mainnet at all. I do think this is/was intentional, but we can do it nevertheless.
We know their mainnet is alive since they have a block explorer showing miners, blocks and transactions already. ( Also they hav an electrum client out.
I was able to compile and sync node to main net by adding their electrum indexing nodes as core nodes, turns out they have a core daemon running on the same machines. The IPs are hardcoded from their electrum client wallet ( ... 
You can add them via cli:
./ubc-cli addnode IP_HERE:8333 "add" 
or by .conf file directives:
addnode= addnode= addnode= addnode= addnode= addnode= addnode= 
But here's the hitch: After that you are fully able to sync and import your private keys BUT you will only see dust like outputs of yours spendable on the main net. I already did a test transaction to an exchange that supports this shitcoin: (WARNINIG: as berepere pointed out this exchange wants KyC not on registration but after the fact at withdrawal)
The bigger UTXO of yours have been transferred to a 'foundation address' 31rZdrTpN57Wbfhg7xTPxeFGjEQaMBjxoo (check this thread )
This means, you wont be able to access your 'currently stolen' funds. They say they will release the Phase2 airdrop funds back again at 24th Jan but who knows.
So anyway, I just wanted you to know how to sync and run your node to be prepared for whenever this thing becomes tradable and accessible. Since there is already one exchange that supports this with deposits, its good to be prepared for when this goes 'live'.
submitted by willsteel to BitcoinAirdrops [link] [comments]

ANN - RENESIS - LTME (Long Term Mining Evolution)

ANN - RENESIS - LTME (Long Term Mining Evolution)
LTME ( Long Term Mining Evolution) With ASIC Resistance Promise hav0k, The Renesis Core

Renesis Specifications:

Algorithm: Renesis Ticker: RESS Whitepaper v1: Block Time: 2 minutes Block Reward: Variable. Refer to whitepaper for reward structure. Halving: Yes Doubling: Yes Mined Confirmations PoW/PoS : 60 TX Confirmations: 10 Minimum RX confirmations to forward: 1 Total Coin Supply: 350M for Proof of Work PoS Cap: No PoS Stake Reward: 10% per year Pre-mine: Yes ( First 100 Blocks mined on low difficulty with CPUMiner) Bounties Available: Yes - From Premine Rewards Available for Community Developers: Yes, from Premine CPUMiner Available: Yes - Windows binary & source. NVIDIA GPUMiner Available: Yes ( Reward for fair release of GPUMiner is paid! 50,000 RESS ) AMD GPUMiner Available: No ( Reward for fair release of GPUMiner is > 12,000 RESS ) Renesis New Logo Design Competition: Yes ( Reward of 2000 RESS ) Renesis QT Wallet Theming Competition: Yes ( Reward of 5000 RESS ) Renesis V2 Static Website Design Competition: Yes ( Reward of 7000 RESS ) Renesis public Pool addition reward: Yes (10000 RESS) - First 3 Pools. Renesis Node Hosting: Yes ( Reward of 1000 RESS offered for 1 month of hosting ) Translation Bounties: Yes ( Reward of 500 RESS per translation posted ) Social Media Bounties: Yes ( Connect with us on our channels for information ) ICO: No - Bitcoin Talk ANN for everyone to mine starting 101 block Masternodes: Planned MainNet P2P port: 9775 MainNet RPC port: 9774 TestNet P2P port: 19775 TestNet RPC port: 19774
Renesis Development Team : hav0k - 2 developers Group : The Renesis Group ( Visit for profiles ) - 7 members Web Site: Block Explorers: - Reddit: Connections: Discord, Telegram, Slack ( Visit to connect ) Will have web wallet: No - We believe coins should be safe in your wallets not online. Pools: To be announced after announcement. Exchanges: To be announced.

Pools: 10000 RESS Reward TX : 10000 RESS Reward TX: 10000 RESS Reward TX:


addnode addnode addnode addnode addnode ( Node by CryptoHobo. 1K RESS every month . TXID : 1e7a332788bceb23438b783dac172c853804d51443f43a1d68b378447981059f - 22 July 2018 addnode addnode addnode addnode addnode renesisckko455xx.onion add ( Tor Node )
Terms & Conditions for GPUMiner Releases : Developers must release the mining software + source after brief testing to Renesis Group to claim their reward. The group will immediately upload the GPUMiner with sources on github after mining 2 test blocks and will provide proof to community. If GPUMiner software is released directly to the community then it would fair but there will be no reward for software developers.


At the time of announcement, you can mine solo until pools become available. Download the CPUMiner binary or source from github with a wallet Place the renesis.conf in your wallet data directory and (re) start wallet. Run start.bat file inside CPUMiner bin folder to mine Renesis. You can edit the start.bat file to edit the number of threads for mining. If you wish to mine on a pool then use the poolmine.bat file.
Note: Please be advised that the cpuminer.exe can show up as a virus on Windows just like almost all mining software. You can be assured it is not and is labelled as coin miner, CpuMiner (PUA) or malware. Refer to virustotal report here . You can safely verify your Claymore and EWBF CUDA miners at virustotal and they will give similar results. If you feel that it has a virus then please do not mine. Virustotal scan for Windows wallet is : .For questions related to GPUMiner releases, please ask fellow miners or their respective developers when their releases become available for download.
UPDATE: CCMINER Download : Reward of 50000 RESS paid to user A1 on Discord :
Special thanks to mrM4D for his guidelines on CPUMiner build. Cheers to ocminer, mrM4D and Epsylon3 Greets to: SCRIV, RavenCoin for their game changing innovations and ASIC resistance commitments.


Phase 1
Renesis Release Development - done CPUMiner Development - done Generate the premine - done Announcement - Underway Community Developers - 3 required and backed by funding from premine. Update: 1st Dev joined the dev team GPUMiners for AMD - Awaited and backed by rewards for fair release by developers. Masternodes Solution - TBA by developers and community consensus and backed by rewards from premine. ASIC Survey - Planned Rensis Hash Enhancement - Planned. TBA under phase 2 or after ASIC Survey Renesis Holdings Fund - Planned
Phase 2 - Next
Good things coming here =) Real use case 1 - Planned Real use case 2 - Planned To be announced after completion of Phase 1
Phase 3 - Planned
Online Gaming - Planned
Phase 4 - Planned
To be announced after completion of Phase 3
submitted by dev_hav0k to Renesis [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:
Along with demo scripts of the functionality:
New to this version is a comprehensive set of unittests under
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
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
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
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.
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.
6)[email protected]/msg06970.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 650 bytes
Desc: Digital signature
URL: <>
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

Why you should mine with replace-by-fee, a decentralized Bitundo

tl;dr: If you mine solo, run a pool, or mine on p2pool, you should get my replace-by-fee code from and install it. As for why, read on:
Out of the the rather heated discussion about the Bitundo service one comment really stuck out for me:
I think there's an interesting legal liability question here - if someone buys a product and then uses your service to Finney attack the merchant, are you part of a conspiracy to defraud the seller?
-Mike Hearn
What Mike is saying is that even though the Bitcoin protocol allows miners total freedom to put any valid transaction they want to in their blocks, the legal system may be used to try to restrict that freedom and punish miners to don't the de facto practice of only mining the first valid transactions broadcast to the network. It's easy to see the legal case playing out: suppose insecure hacks like Mycelium's transaction radar catch on. We'll have a lot of people doing transactions that depend on miners all following the same mining rules, and eventually someone is going to get hurt. They're going to want to find someone to sue, and what better than the mining pool who mined the double-spend transaction?
What's wrong with that? Of course, first and foremost by encouraging people to use Bitcoin insecurely we invite heavy handed regulation when things go wrong. We're already seeing regulators cite the hundreds of millions of dollars lost by MtGox as evidence of the need for legal regulation, rather than technological measures like multisig. Why make the exact same mistake all over again with unconfirmed transactions?
There's a deeper reason too: relying on unconfirmed transactions is only possible by making Bitcoin more centralized at the mining level, at the network level, and at the development team level. Every Bitcoin release accepts a slightly different set of transactions as valid - do you want to be worried about legal liability if your mining operation allows an attacker to rip off someone because you upgraded sooner or later than the rest of the network? Or just were using a different client all together? Like it or not, if one miner accepts a different set of transaction types than another, that's an opportunity to double-spend.
At the network level transactions simply do not and never will propagate through the network instantly. At the same time until a transaction is confirmed there isn't any proof that the transaction propagated to any hashing power at all - the proof that a transaction was succesfully published is in the form of PoW only. Again, the only way to make unconfirmed transactions even close to safe is to make the network of miners smaller - do you want to be exposed to legal liability just because your small mining pool had a worse network connection than the biggest pool? You could even be in a situation where you've been sybil attacked, preventing you from seeing some transactions at all. You won't have any proof of that fact - instead it'll look like you participated in an attempt to rip someone off.
Finally it's been proposed multiple times that merchants pay for security directly with insurance contracts with major minering pools. The miners agree not to double-spend, and the merchants pay extra for that. Of course, if you're a small miner you're not going to get these contracts - you're much too small to bother talking to. The major mining pools wind up earning more BTC/hash than you, and on top of that, if you ever do end up including a double-spend in one of your blocks it's quite likely those contracts will have those pools just kill off your blocks in a re-organization.
The fact is Bitcoin by itself just isn't suited to instant confirmations: if you want decentralization, you have to give everyone time to come to consensus securely. Fortunately we have lots of technologies that can be used in conjunction with Bitcoin for the times when 10 minutes isn't good enough, but if we don't use them we'll end up with a less secure and less decentralized Bitcoin.
What you should do if you're a pool operator, solo miner, or mine on p2pool
Replace-by-fee simply means that rather than only accepting the first transaction you see to your mempool, you accept whatever one pays the most fees. It's a simple rule that results in the most profit per block, lets users re-issue transactions with higher fees if needed, and most importantly, makes it clear to everyone that relying on unconfirmed transactions by themselves is insecure.
I've written a simple replace-by-fee patch based directly on the v0.9.1 codebase. Installation is just a matter of getting my replace-by-fee-v0.9.1 branch from and compiling it; you run the code just like you would normally.
Unlike BitUndo it's an entirely decentralized system where the 100% of the profits for replacing one unconfirmed transaction with another goes directly to miners. The patch implements preferential peering, which means it seeks out other nodes supporting replace-by-fee to ensure you'll always be connected to like-minded peers; you don't need to -addnode a central server.
While I wouldn't recommend a pool like to install it right off the bat, if you're a miner on, say, p2pool, installing the patch carries no risk to you, and will help keep Bitcoin decentralized in the future.
submitted by petertodd to Bitcoin [link] [comments]

How to fast sync the Bitcoin Gold wallet

  1. Download wallet:
  2. Check your address: File -> Receiving address
Now you can start mining to this address
How to set up miner:
  1. Make backup in case of: File -> Backup wallet
  2. Find your private key: Help -> Debug window -> Console
  3. dumpprivkey your_Receiving_address
  4. Save it somewhere
  1. Create a shotcut to bitcoin-qt.exe with -bootstrap option
  2. Add Bitcoin Core nodes (Not Bitcoin Gold as they are OVERLOADED).
Take nodes from here:
Add port 8333 at the end of each node.
For example
Help -> Debug window -> Console
addnode add
etc. If you have Bitcoin Core wallet:
Start it. Check you IP (which was specified by your router for example
Add it through Help -> Debug window -> Console
addnode add
  1. Sync till block 491407.
  2. Close Bitcoin Gold wallet.
Start it without the -bootstrap option.
  1. Add Bitcoin Gold nodes.
Or just save bitcoin.conf to the installation folder of your Bitcoin Gold.
P.S. Welcome to Bitcoin Mining Pool.
It is on the correct chain. Blocks have already been found. Everything works perfect for the whole day.
submitted by 2miners to gpumining [link] [comments]

[ANN] [BTV] Bitvote -- A Hard Fork of Bitcoin (Keep Updating)

1. Update
2018/1/20 update:The main chain is released. Please use the code in GitHub ( to compile and synchronize data.
2018/1/21 update: COINEX ( Launched BTV/BCH trading pair, deposit and withdraw.
2018/1/22 update: The solution of the mining pool is released in GitHub ( for your reference.
2018/1/26 update: Miner for Windows x64 is released in on our website. For Linux users, please use codes ( to compile, and use your CPU to mine and vote.
2018/1/27 update: The QT Wallet for Windows x64 is released.
2018/1/29 update: Hypex ( ) opened BTV/BTC and BTV/ETH trading pair, and users can deposit and withdraw BTV on Hypex.
2018/2/02 update: Block explorer is released:
2018/2/05 update: BTV integrated into BeeChat (, you can send and receive BTV in BeeChat
2018/2/07 update: Now you can put your BTV in Bitpie. Dowload Bitpie wallet at
2018/2/26 update: Bit-Z will open BTV/BTC and BTV/ETH transaction pairs at 15:00 on March 2, 2018 (GMT+8). BTV withdrawal and deposit will also be opened at the same time.
2. Introduction
Bitvote has forked successfully at Bitcoin block height 505050. Bitvote is a fork of Bitcoin, and its abbreviation is BTV. There will be no pre-mining and additional issuance. Bitvote uses the CryptoNight algorithm.
3. Exchanges
4. Mining Pool
5. Addnode Information
6.Bitvote Technical Features
Bitvote uses CryptoNight algorithm, which responds to Satoshi Nakamoto's vision of one-CPU-one-vote, to balance hashrate distribution, making decentralization a real thing.
Replay Protection
Improved wallet safety and eliminated double hashing problem make complete replay protection come true, which protects users and their tokens from various accidents as well as malicious threats.
Block Size Expansion
The block size is expanded to 8M, and the block also supports SegWit. Transaction speed can be improved greatly, so bitcoin network congestion will be completely solved and its practical values will be added.
Lightning Network
There is no need to trust the other party or the third party to achieve real-time and huge amounts of transactions, and payment channels are introduced to enhance the extensibility.
Smart Contract
With the system that has infinite possibilities and the ability to issue assets and establish applications, Bitvote is a token which integrates values and practicability together.
Block Vote
Bitvote employs the scheme of block mark bidding and voting independently. The development direction of the community will be decided by the voting result; thus an autonomous community can be established and divergences can be solved democratically.
7. Communities
Official Website
WeChat Subscription Account:bitvote
E-mail:([email protected])
8. Whitepaper
For more information about Bitvote, please refer to the whitepaper English version; Chinese version
submitted by bitcoinvote to bitvote_one [link] [comments]

Proof of Nodework (PoNW) - a method to trustlessly reward nodes for storing and verifying the blockchain | John Hardy | Feb 07 2017

John Hardy on Feb 07 2017:
Proof of Nodework (PoNW) is a way to reward individual nodes for keeping a full copy of and verifying the blockchain.
Hopefully they also do useful ‘traditional’ node activities too like relay transactions and blocks, but there isn’t really any way I can think of to trustlessly verify this also.
PoNW would require a new separate area of block space, a nodeblock, purely concerned with administering the system. A nodeblock is committed to a block as with SegWit. A recent history of nodeblocks needs to be stored by nodes, however the data eventually becomes obsolete and so does not need to be retained forever.
In order to prevent Sybil, a node must register an Bitcoin address by submitting an addNode transaction - along with a security deposit to prevent cheating.
This transaction will be stored in the nodeblock. Once a node can see that its addNode transaction has been added it can begin the PoNW process. The node’s registered address will be hashed with the block header of the block it wants to work on. This will determine exactly where within the blockchain to begin the PoNW.
The PoNW method could be as simple as creating a Merkle tree from the randomly generated point on the blockchain, though a method that is CPU/Memory heavy and less likely to be replaced by dedicated hardware like ASICs would be better. This process could not begin until the most recent block has been fully verified, and while being carried out should still enable normal relay activities to proceed as normal, since it shouldn’t tie up network at all. The data processed should also be mixed with data from the latest block so that it cannot be computed in advance.
A node can do as much PoNW for a block as it likes. Once finished it will then create a nodeWorkComplete transaction for that block with its final proof value, add how much ‘work’ it did - and create a couple of assertions about what it processed (such as there were x number of pieces of data matching a particular value during calculating). These assertions can be accurate or inaccurate.
The system will run in epochs. During each epoch of say 2016 blocks, there will be an extended window for PoNW transactions to be added to nodeblocks to limit minor censorship.
The random hash generated from a node’s address and blockhash will also be used to determine nodeWorkComplete transactions from a previous block that the node must also verify, and correctly calculate whether the assertions it made were true or false. The average PoNW that a node performed in its previous x nodeblocks will be used to determine the target PoNW for the node to verify - and this will randomly be a large number of smaller PoNW transactions, or a smaller number of large PoNW. This process will be deterministic based on that block and address hash. All the data will be put together in a transaction and then signed by the node addresses private key.
If a nodeWorkComplete transaction contains any incorrect information in an attempt to cheat the validation process a challenge transaction can be created. This begins a refereeing process where other nodes check the challenge and vote whether it is to be upheld or not. The losing node is punished by losing their accrued PoNW for that epoch and a percentage of their security deposit.
Nodes will also be punished if they broadcast more than one signed transaction per block.
In order to prevent nodes from having multiple keys registered - which would enable them choose to perform PoNW on a subset of the data that they hold - the share of reward that the node gets will be multiplied based on the number of blocks within an epoch that the node performs PoNW on. The share of reward is limited based on how much security deposit has been staked. The higher the PoNW the higher the deposit needed in order to claim their full allocation of any reward.
At the end of an epoch, with a wait period for any delayed or censored transactions or challenges to be included and settled up, the process of calculating the reward each node is due can begin. This will then be then paid in a regular block, and means for all the data involved in PoNW, the only permanent mark it makes on the main blockchain is for a transaction that pays all addresses their share of the reward at the end of epoch. Any miner who creates a block without correctly calculating and paying the due reward will have mined an invalid block and be orphaned.
The question of where and how much the reward comes from is a different one. It could come from the existing miner reward, or a special new tx donation fee for nodes. If there was some way for users to ‘donate’ to the reward pool for nodes this would increase the incentive for additional nodes to participate on the network in the event of centralisation.
This is a relatively effective way to create a reward for all nodes participating on a network. I’d be keen to field any questions or critiques.
John Hardy
john at
-------------- next part --------------
An HTML attachment was scrubbed...
submitted by dev_list_bot to bitcoin_devlist [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:
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!
Install Ubuntu server or Desktop if you want 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:// 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'
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= addnode= addnode= addnode= addnode= addnode= addnode= addnode= addnode= addnode= addnode= addnode= 
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 p2pool #renaming it! cd ~/p2pool/digibyte_subsidy #Thanks to Chaeplin sudo python 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/ --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:
inet addr: #You'll see a line like this.
So, Your cgminer string should look something like this:
cgminer --scrypt -o -u DGBADDRESS -p x
And your p2pool WEB ADDRESS should look like this:
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:
screen -d -m -S myp2pool ~/p2pool/ --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!
This Tutorial was made with the help of an existing Guide: Kudos to crypto49er!
If you want to do this on a VPS:
Here's a link to a VPS hosting site:
Feel free to use my $10 ref. code -- it doesnt really make a difference, though.
Let me know if this guide helped!
submitted by StormMiner to Digibyte [link] [comments]

Bitcoin Core 0.14.1 released | Wladimir J. van der Laan | Apr 22 2017

Wladimir J. van der Laan on Apr 22 2017:
Hash: SHA512
Bitcoin Core version 0.14.1 is now available from:
Or, by torrent:
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
To receive security and update notifications, please subscribe to:

Bitcoin Core is extensively tested on multiple operating systems using
the Linux kernel, macOS 10.8+, and Windows Vista and later.
Microsoft ended support for Windows XP on April 8th, 2014,
No attempt is made to prevent installing or running the software on Windows XP, you
can still do so at your own risk but be aware that there are known instabilities and issues.
Please do not report issues about Windows XP to the issue tracker.
Bitcoin Core should also work on most other Unix-like systems but is not
frequently tested on them.
Notable changes

RPC changes
These interface changes break compatibility with 0.14.0, when the named
arguments functionality, introduced in 0.14.0, is used. Client software
using these calls with named arguments needs to be updated.
In previous versions, getblocktemplate required segwit support from downstream
clients/miners once the feature activated on the network. In this version, it
now supports non-segwit clients even after activation, by removing all segwit
transactions from the returned block template. This allows non-segwit miners to
continue functioning correctly even after segwit has activated.
Due to the limitations in previous versions, getblocktemplate also recommended
non-segwit clients to not signal for the segwit version-bit. Since this is no
longer an issue, getblocktemplate now always recommends signalling segwit for
all miners. This is safe because ability to enforce the rule is the only
required criteria for safe activation, not actually producing segwit-enabled
UTXO memory accounting
Memory usage for the UTXO cache is being calculated more accurately, so that
the configured limit (-dbcache) will be respected when memory usage peaks
during cache flushes. The memory accounting in prior releases is estimated to
only account for half the actual peak utilization.
The default -dbcache has also been changed in this release to 450MiB. Users
who currently set -dbcache to a high value (e.g. to keep the UTXO more fully
cached in memory) should consider increasing this setting in order to achieve
the same cache performance as prior releases. Users on low-memory systems
(such as systems with 1GB or less) should consider specifying a lower value for
this parameter.
Additional information relating to running on low-memory systems can be found
0.14.1 Change log

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

RPC and other APIs

    • #10084 142fbb2 Rename first named arg of createrawtransaction (MarcoFalke)
    • #10139 f15268d Remove auth cookie on shutdown (practicalswift)
    • #10146 2fea10a Better error handling for submitblock (rawodb, gmaxwell)
    • #10144 d947afc Prioritisetransaction wasn't always updating ancestor fee (sdaftuar)
    • #10204 3c79602 Rename disconnectnode argument (jnewbery)

Block and transaction handling

    • #10126 0b5e162 Compensate for memory peak at flush time (sipa)
    • #9912 fc3d7db Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
    • #10133 ab864d3 Clean up calculations of pcoinsTip memory usage (morcos)

P2P protocol and network code

    • #9953/#10013 d2548a4 Fix shutdown hang with >= 8 -addnodes set (TheBlueMatt)
    • #10176 30fa231 net: gracefully handle NodeId wrapping (theuni)

Build system

  • - #9973 e9611d1 depends: fix zlib build on osx (theuni)


  • - #10060 ddc2dd1 Ensure an item exists on the rpcconsole stack before adding (achow101)


    • #9955/#10006 569596c Don't require segwit in getblocktemplate for segwit signalling or mining (sdaftuar)
    • #9959/#10127 b5c3440 Prevent slowdown in CreateNewBlock on large mempools (sdaftuar)

Tests and QA

  • - #10157 55f641c Fix the test (sdaftuar)


    • #10037 4d8e660 Trivial: Fix typo in help getrawtransaction RPC (keystrike)
    • #10120 e4c9a90 util: Work around (virtual) memory exhaustion on 32-bit w/ glibc (laanwj)
    • #10130 ecc5232 bitcoin-tx input verification (awemany, jnewbery)

Thanks to everyone who directly contributed to this release:
    • Alex Morcos
    • Andrew Chow
    • Awemany
    • Cory Fields
    • Gregory Maxwell
    • James Evans
    • John Newbery
    • MarcoFalke
    • Matt Corallo
    • Pieter Wuille
    • practicalswift
    • rawodb
    • Suhas Daftuar
    • Wladimir J. van der Laan
As well as everyone that helped translating on Transifex.
Version: GnuPG v1
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

[ANN]SHERLOCK COIN (SHC)| + | + 221 Baker St + | + |only 221 coins to be mined +

SHERLOCK COIN (SHC) - The Game is on to the Crypto World!
Overview As of Sherlock Holmes and as you may know is best detective and genius of all time , while being grateful for the dedication and works of Sir Arthur Canon Doyle , this coin is solely based on character of Sherlock Holmes and ingenuity of the same while solving mysteries the same can be seen on the coin. Wink , while dedicating this coin to all the enthusiasts of Sherlock Holmes , I believe and have faith that this coin will make it through and will be a success , something to hold on to and cherish.
As you probably know by now that the board get's spammed uncontrollably by ALT-Coins releases everyday , some might survive some might not I want SHC to be treasured not at all a pump and dump coin but a coin to cherish the name of Sherlock Holmes and for the enthusiasts to treasure it and if you want to spread it around.
Launch This is a fork of Litecoin and developed using foundations and guidance documented by beloved members here who have committed and pledged their support for cryptocurrencies mainly Bitcoin as well as Alt-coins , my salute is to all who strive to make Cryptocurrencies the future and the dedication of developers who work night and day to make that dream a success , this coin is not a competitor to Bitcoin nor other ALT coins but a strength to the world of Cryptocurrencies and my contribution thus stands and will always with the community , we should never forget the past , thus as they say if done will be void of a future , therefore my salute goes to Bitcoin , it's founders and developers and the community that stands by it and everyone on this forum , thereby paying my respect as we all know we should be thankful of Bitcoin without it we would never would have imagined or known about a world of Cryptocurrencies. Salute!
Please Note: This is NOT a paid up over the countewebsite coin , that just popped out of a script on a website after making a Bitcoin Payment , I had to put my sweat , tears , dedication , sacrifice and time (lot's of it) , had to put 200% of my effort, trial and error , learning , failures to make this workout , this coin opened up a new chapter in my life , learning , as I've learned alot while making this , I kindly ask you to respect that while criticizing if you may require.
WEBSITE (Under Maintenance)
FORUM To Be Announced
SPECIFICATIONS Scrypt 221 coins Max 221 second block time Difficulty re-target every 10 minutes 0.00000010 Block reward for the first 221 blocks (Conveniently set to allow you to get your miners running) Blocks 222+ are 0.00004200 block reward Random Block Rewards/Super Blocks! Smiley Block 212 is a Special Block with More Rewards than the normal block value Tx fees are 0.00000001 RPC port 55883 p2p port 55884 0.01% (0.221 coins) Premine for Testing/Bounty and Giveaway Purposes.
Source Code
Windows Wallet
Sample sherlockcoin.conf file:
rpcuser=username rpcpassword=password rpcallowip= rpcport=55883 port=55884 listen=1 daemon=1 server=1 addnode=
POOLS To be Announced
EXCHANGES To be Announced
SERVICES / OTHER To be Announced
IRC FreeNode To be Announced
For more services it's best to check out the website links at the top of this information thread.
Elementary my dear alt-coiner! Wink These coins will be rare! Smiley
submitted by soopy452000 to SherlockCoin [link] [comments]

NODE vs FULL NODE vs MINER  WHAT IS DIFFERENCE AND WORK BETWEEN THEM  IN HINDI Best Bitcoin Miner for Linux OS HomeTech Bitcoin Miner ... Virtualizing Bitcoin Full Nodes Bitcoins Smallest Full Node Miner by 21 Bitcoin BitconnectX addnode (BCCX node)

Click the large blue Download Bitcoin Core button to download the Bitcoin Core installer to your Downloads folder. Optional: Verify the release signatures. If you know how to use PGP, you should also click the Verify Release Signatures link on the download page to download a signed list of SHA256 file hashes. The 0.11 and later releases are signed by Wladimir J. van der Laan’s releases key w Bitcoind – a daemon program that implements the Bitcoin protocol, is controlled through the command line. It is one of the main components of the Bitcoin network node software. Bitcoin software exists in two forms: a GUI application and a background application (daemon on Unix, service on Windows). Doch zur Unterhaltung des ganzen Bitcoin-Netzwerkes sind nicht Miner und Wallet-Besitzer mit aktiven Wallets nötig, sondern auch seógenannte Full Nodes. Das sind Knotenpunkte, die eine volle Bitcoin-Installation dauerhaft betreiben, und so die Blockchain kopieren, bereitsstellen und validieren, sowie neue Blöcke weiterereichen und verbreiten. Dieser Service wird von relativ wenigen ... addnode= addnode= addnode= 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 ... Bitnodes uses Bitcoin protocol version 70001 (i.e. >= /Satoshi:0.8.x/), so nodes running an older protocol version will be skipped. The crawler implementation in Python is available from GitHub (ayeowch/bitnodes) and the crawler deployment is documented in Provisioning Bitcoin Network Crawler. The crawler maintained by Bitnodes connects from these IP addresses:, ...

[index] [12736] [28215] [26132] [4430] [7330] [11821] [13051] [21998] [12469] [40125]


21 Bitcoin Computer first computer with native hardware and software support for the bitcoin protocol. AKA RUN YOUR OWN NODE. This computer is awesome way learn about the bitcoin mining process. I ... HomeTech Bitcoin Miner URL -- Bitcoin Giveaway URL -- About HomeTech Bitcoin Miner -----... bitcoin cloud mining, bitcoin core, bitcoin chart, bitcoin cryptocurrency, le bitcoin c'est quoi, bitcoin doubler, bitcoin debate, bitcoin diamond, bitcoin debit card, bitcoin dead, bitcoin daily ... create file bitconnectx.conf in C:\Users\your_compuer_name\AppData\Roaming\bitconnectx and add nodes: addnode= addnode= HomeTech Bitcoin Miner URL -- Bitcoin Giveaway URL -- About HomeTech Bitcoin Miner -----...