Running A Full Node - Bitcoin

How to run two bitcoind processes in isolation (Windows)

I have a synced node, and I would like to create a pruned copy of that node without destroying all blocks and chainstate I already have. My thought would be to run two copies of bitcoin {BitcoinA.exe, BitcoinB.exe}, while offline and bound to 127.0.0.1. Both A and B point to each other through a connect or addnode config setting. My thought would be that now the "blank" bitcoin node (BitcoinB) would download and prune all the block data from BitcoinA via localhost.
I can imagine that I'd need separate data, block and chainstate dirs. I'll need separate rpc-cookies and separate ports.
Obviously I could just do the 300 GB file copy then do a rescan, but I figured I'd get faster IO on localhost<->localhost than disk<->disk.
Surely this is a fairly common way to clone block data. Has anyone done this before? Thoughts or advice?
submitted by brianddk to Bitcoin [link] [comments]

Bitcoin core RPC very slow: "mapOrphan overflow, removed 1 tx"

I am running bitcoin core v0.18.0 and noticed that now my queries made locally through the RPC are taking very long. Here is my bitcoin.conf:
txindex=1 datadir=/media/**** maxmempool=30000 mempoolexpiry=99999 choosedatadir=1 checkblocks=3 minrelayfee=0 maxconnections=9999 debug=mempool debug=mempoolrej addnode=*** addnode=*** logips=1 rest=1 rpcuser=*** rpcpassword=*** 
And here is a sample of the log, notice the unusual mapOrphan overflow lines:
20-05-21T21:04:09Z AcceptToMemoryPool: peer=33: accepted 1755b76d790f73252c0ccf890477803aa295444953514fc5c9aad8c2fe6154e0 (poolsz 20383 txn, 105635 kB) 2020-05-21T21:04:09Z stored orphan tx 89cdced1c7c61bf59633af323fd2dbe07c5a6859c51d83247f0fb01b83eb1451 (mapsz 101 outsz 137) 2020-05-21T21:04:09Z mapOrphan overflow, removed 1 tx 2020-05-21T21:04:10Z AcceptToMemoryPool: peer=26: accepted 1122f2315279bc0378fe51733638ede97dcaa938c2fcbd930d91ac2405999fcd (poolsz 20385 txn, 105762 kB) 2020-05-21T21:04:10Z AcceptToMemoryPool: peer=33: accepted 95bd4499ffd3111dab98dbbcb565ff897f21a07c9242659cd38f452022267f78 (poolsz 20386 txn, 105763 kB) 2020-05-21T21:04:10Z stored orphan tx 8c547967ff198c286770f966256c3b09482c5390a93016e597d8a1c6c6699afa (mapsz 101 outsz 138) 2020-05-21T21:04:10Z mapOrphan overflow, removed 1 tx 2020-05-21T21:04:10Z stored orphan tx 2d5fcb835d580caa7fd32f0260cb4ce0e5edf67bf1dc134d1153d6d3118c7009 (mapsz 101 outsz 138) 2020-05-21T21:04:10Z mapOrphan overflow, removed 1 tx 2020-05-21T21:04:10Z AcceptToMemoryPool: peer=20: accepted a49508232092870d58d4f7c63127cb688897d25f8ba1fb0d1c86e4c4b09a2f00 (poolsz 20387 txn, 105764 kB) 2020-05-21T21:04:10Z stored orphan tx 854ccbbd7fd0f04b466dec92df3cbfe96fd8aa25eb0aa17a8524aa82a4bff6ff (mapsz 101 outsz 138) 2020-05-21T21:04:10Z mapOrphan overflow, removed 1 tx 2020-05-21T21:04:10Z stored orphan tx 8ee4f6de0f5d9bdeaa840749193799636b22498711401936e86fc265574430f7 (mapsz 101 outsz 138) 2020-05-21T21:04:10Z mapOrphan overflow, removed 1 tx 
The node is up-to-date and I didn't detect anything unusual (like a stale block/fork).
submitted by johnturtle to BitcoinBeginners [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 =47.114.58.108 (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 =47.114.58.108 (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 =47.114.58.108 (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]

No inbound connections on my bitcoin full node with TOR

update: it's ok now, it only required some time. Also, looking at debug.log it won't show anything about inbound connections as I thought, it must be used `bitcoin-cli getpeerinfo` in order to get all the connections info (inbound + outbound)
Can someone connect to my node? u3ob433qu3ebkmsu.onion:8333
I'm behind a CG-NAT so I thought to use TOR to overcame it but still I have outbound connections but no inbound.
$ bitcoin-cli getnetworkinfo
{ "version": 180000, "subversion": "/Satoshi:0.18.0/", "protocolversion": 70015, "localservices": "000000000000040c", "localrelay": true, "timeoffset": 0, "networkactive": true, "connections": 10, "networks": [ { "name": "ipv4", "limited": true, "reachable": false, "proxy": "127.0.0.1:9050", "proxy_randomize_credentials": true }, { "name": "ipv6", "limited": true, "reachable": false, "proxy": "127.0.0.1:9050", "proxy_randomize_credentials": true }, { "name": "onion", "limited": false, "reachable": true, "proxy": "127.0.0.1:9050", "proxy_randomize_credentials": true } ], "relayfee": 0.00001000, "incrementalfee": 0.00001000, "localaddresses": [ { "address": "u3ob433qu3ebkmsu.onion", "port": 8333, "score": 4 } ], "warnings": "" } 
bitcoin.conf
server=1 daemon=1 # RPC rpcuser=***** rpcpassword=******* # TOR onlynet=onion proxy=127.0.0.1:9050 bind=127.0.0.1 dnsseed=0 dns=0 addnode=nkf5e6b7pl4jfd4a.onion addnode=yu7sezmixhmyljn4.onion # Raspberry Pi optimizations dbcache=100 maxorphantx=10 maxmempool=50 maxconnections=40 maxuploadtarget=5000 prune=6000 
submitted by LiL0u to Bitcoin [link] [comments]

A tour of the Gridcoin wallet

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

OVERVIEW TAB

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

SEND TAB

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

RECEIVE TAB

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

TRANSACTIONS TAB

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

ADDRESS BOOK TAB

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

VOTING TAB

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

CONTEXT BAR

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

OPTIONS

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

ENCRYPTING YOUR WALLET

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

GETTING IN SYNC AND ICONS

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

WHAT IS STAKING?

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

UTXOS AND COIN CONTROL

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

FORKING

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

CONFIGURATION FILE

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

RUNNING A LISTENING NODE

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

QUICK LINKS

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

Gridcoin Leisure Update 3.7.14.0 Released

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

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

Github release link
Forum Post

Important Notes

Upgrade instructions

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

Notable Changes

libzerocoin Exploit Fix

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

zPIV Maintenance Mode Spork

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

Accumulator Code Refactor

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

Money Supply Indexing

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

More Extensive Tracking of zPIV Supply Through RPC

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

Multisig GUI

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

Credits

FAQ

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

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

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

Gridcoin Developer Update April 23rd, 2018

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

ANN - RENESIS - LTME (Long Term Mining Evolution)

ANN - RENESIS - LTME (Long Term Mining Evolution)
https://preview.redd.it/wulcw7lgbhb11.png?width=500&format=png&auto=webp&s=c3aca3a98e0b699d88e99acee4a5dc236c8b39e0
LTME ( Long Term Mining Evolution) With ASIC Resistance Promise hav0k, The Renesis Core

Renesis Specifications:

Algorithm: Renesis Ticker: RESS Whitepaper v1: https://github.com/renesisgroup/whitepapeblob/masteRENESIS-paper.pdf 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 www.renesis.io for profiles ) - 7 members Web Site: http://www.renesis.io Block Explorers: http://tx.renesis.io - https://protopool.net/exploreRESS Reddit: https://www.reddit.com/Renesis/ Connections: Discord, Telegram, Slack ( Visit www.renesis.io 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:

https://cryptopool.party 10000 RESS Reward TX : http://tx.renesis.io/address/RVMNvHD3DFH1CZ9JVijFxiZgKcPLBpteYh
https://protopool.net 10000 RESS Reward TX: http://tx.renesis.io/address/RATQNUpMH7puoByrkBBUWiBVJowno6bGPz
http://www.tera.tn/ 10000 RESS Reward TX: http://tx.renesis.io/address/RFUkDC5dyRQZhH3GkrAhnAUNNQ2tZbTt7w

Nodes:

addnode node1.renesis.io addnode node2.renesis.io addnode node3.renesis.io addnode node4.renesis.io addnode node5.renesis.io ( Node by CryptoHobo. 1K RESS every month . TXID : 1e7a332788bceb23438b783dac172c853804d51443f43a1d68b378447981059f - 22 July 2018 addnode i.crashed.online addnode he.crashed.online addnode it.crashed.online addnode she.crashed.online 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.

Mining:

At the time of announcement, you can mine solo until pools become available. Download the CPUMiner binary or source from github with a wallet https://github.com/renesisgroup/cpuminer-release. 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 https://www.virustotal.com/#/file/1c90ca293dc016f0d8663f7bab55b5def8f484c21b3dac3dae6f81d0166cc99e/detection . 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 : https://www.virustotal.com/#/file/4cc5d6977566fc7e254744626d0783b1fc2d1aab15d72a5137c99ef0e91eee46/detection .For questions related to GPUMiner releases, please ask fellow miners or their respective developers when their releases become available for download.
UPDATE: CCMINER Download : https://github.com/renesisgroup/ccminer-renesis Reward of 50000 RESS paid to user A1 on Discord : http://tx.renesis.io/address/RVmFpemzMtbjhG16bjQTGEWv3sTgRVuzWm
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.

Roadmap:

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]

Myriad 0.11.2 RC1

Code is up and available @ https://github.com/myriadteam/myriadcoin/tree/0.11.2
No windows binaries yet, will do this for a later RC. It does work, I'm just too lazy.
Lots of little issues still to be ironed out, but should be good for wider testing. But please don't blame me if it eats all of your MYR.
Blockchain:
As this is based off Bitcoin Core 0.11.2, it inherits the ability to download the blockchain faster due to header only sync before pulling down the transactions. However this goodness DOES require the daemon to re-sync the entire blockchain. From my brief testing it does appear to sync quicker than the 0.9.2 releases.
Also try adding the following line to your myriadcoin.conf file - this is my node running this newer version (please take note the port i have used here) and it may assist with a faster sync:
addnode=nz.nutty.one:10988 
Naming: I've renamed a lot of stuff to 'Myriad' - however there are a couple of exceptions for reasons of compatibility with older existing versions:
Known Issues:
For any issues you discover, please log them here -> https://github.com/myriadteam/myriadcoin/issues . Depending on the juiciness of the issue, you may receive some MYR for your efforts.
Please be as specific as possible. Having spent too many years providing tech-support, if someone logs an issue saying "x doesn't work" with no detail, expect a terse response (along the lines of travel and procreation).
submitted by nzsquirrell to myriadcoin [link] [comments]

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

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

Addnode Information of Bitvote

9 nodes of bitvote:From seed1.bitvote.one to seed9.bitvote.one
Please synchronize with official nodes,and the method to add nodes is as follows:
1. Add the following to bitcoin.conf
addnode=seed1.bitvote.one
addnode=seed2.bitvote.one
addnode=seed3.bitvote.one
addnode=seed4.bitvote.one
addnode=seed5.bitvote.one
addnode=seed6.bitvote.one
addnode=seed7.bitvote.one
addnode=seed8.bitvote.one
addnode=seed9.bitvote.one
2. Use rpc:
bitcoin-cli addnode seed1.bitvote.one onetry
bitcoin-cli addnode seed2.bitvote.one onetry
bitcoin-cli addnode seed3.bitvote.one onetry
bitcoin-cli addnode seed4.bitvote.one onetry
bitcoin-cli addnode seed5.bitvote.one onetry
bitcoin-cli addnode seed6.bitvote.one onetry
bitcoin-cli addnode seed7.bitvote.one onetry
bitcoin-cli addnode seed8.bitvote.one onetry
bitcoin-cli addnode seed9.bitvote.one onetry
bitcoin-cli addnode seed1.bitvote.one add
bitcoin-cli addnode seed2.bitvote.one add
bitcoin-cli addnode seed3.bitvote.one add
bitcoin-cli addnode seed4.bitvote.one add
bitcoin-cli addnode seed5.bitvote.one add
bitcoin-cli addnode seed6.bitvote.one add
bitcoin-cli addnode seed7.bitvote.one add
bitcoin-cli addnode seed8.bitvote.one add
bitcoin-cli addnode seed9.bitvote.one add
submitted by bitcoinvote to bitvote_one [link] [comments]

Bitcoin regtest adding and deleting the nodes

I have a hard time in deleting the peers when i used : bitcoin-cli -regtest addnode "ip address" onetry. I have tried RPC remove but it still shows up when i use "getpeerinfo". How can i delete the peers which i am connected too
submitted by snort5121 to Bitcoin [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:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Bitcoin Core version 0.14.1 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.14.1/
Or, by torrent:
magnet:?xt=urn:btih:0482be8fc8e1c0b02162871e3591efc3d1d34585&dn;=bitcoin-core-0.14.1&tr;=udp%3A%2F%2Fpublic.popcorn-tracker.org%3A6969%2Fannounce&tr;=http%3A%2F%2Fatrack.pow7.com%2Fannounce&tr;=http%3A%2F%2Fbt.henbt.com%3A2710%2Fannounce&tr;=http%3A%2F%2Fmgtracker.org%3A6969%2Fannounce&tr;=http%3A%2F%2Fopen.touki.ru%2Fannounce.php&tr;=http%3A%2F%2Fp4p.arenabg.ch%3A1337%2Fannounce&tr;=http%3A%2F%2Fpow7.com%3A80%2Fannounce&tr;=http%3A%2F%2Ftracker.dutchtracking.nl%3A80%2Fannounce
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:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoincore.org/en/list/announcements/join/
Compatibility

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.
Mining
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
blocks.
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
here:
reducing-bitcoind-memory-usage.md.
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)

GUI

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

Mining

    • #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 mempool_packages.py test (sdaftuar)

Miscellaneous

    • #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)
Credits

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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJY+1YNAAoJEHSBCwEjRsmme+YIAIkJLCjimADYBJoM8bnHK2Dc
4KznlAjpXqFWb6taoSyWi+/6DtZxJF1MZm+iaDhqmTEy+ms313N2mBEd2xrSAPPL
nYf84e3tgnwq07sQmUxVZXyhZe2R+m/kgy75TTZw+bonyXwwA3384F0L8gvV5Iu+
kNNu6WggWUTvOADEFVKecgzWeT1FCYXklbNk+Z5T/YWWrKA8ATXgv45IIEKT8uI1
pqhKQxoqLM3ga7Df3VbzwXAYAOCaFzf+0nmTRoqDM5pX+FQ2hq0UM6joLnUNk2ee
G4/nsNWAKg/6eycrA7Wvawwcozr2iYAov/YDj6pEI8UoeGcOdlSh69Seb1cngHg=
=EHlY
-----END PGP SIGNATURE-----
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/014228.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

[ANN][PSP] POSPRO - POW/POS - ICO começa 13 de maio 11 AM -www.pospro.link )

Website Oficial: www.pospro.link (http://www.pospro.link)
Moeda POSPRO [PSP] é uma moeda online p2p que permite transações instantâneas, com custos próximos de zero para qualquer lugar no mundo. POSPRO é uma fonte aberta, rede de pagamento global que é totalmente descentralizada , sem quaisquer autoridades centrais. A rede é protegida matematicamente e permite que os usuários controlem suas próprias finanças. POSPRO apresenta uma rápida confirmação de transação e melhoria da eficiência de armazenamento do que as moedas líderes baseadas em algorítimos. Com o apoio da indústria substancial, o volume de comércio e liquidez.
POS Prova de Acumulo aumenta a velocidade, segurança e eficiência energetica comparada com as demais moedas digitais. Livre de chefes e bancos, POSPRO da o poder de volta a pessoa. Ninguém é dono da POSPRO, não é uma empresa única, qualquer um pode fazer parte.
A tecnologia POSPRO’s permite qua a pessoa envie e receba rapido, facil e com segurança pagamentos com pessoas em qualquer parte do mundo. Sem precisar de chefes ou bancos. Totalmente aberta. POSPRO é uma moeda da comunidade, e o sucesso depende em parte da implementação conjunta e marketing conjunto. Veja abaixo a distribuição ECD para mais informações.
Clientes e Carteiras
Sexta 27th de Maio 2016 – 11AM (11.00 hour European time) Timezone: UMT+1 Berlin.
Vá ate o nosso site para obter o cliente. http://pospro.link/pospro/software/
BLOCK EXPLORER http://explorer.pospro.link
SPECIFICATIONS Nome Oficial: POSPRO Ticker: PSP Scrypt POW/POS Total coins: 84 000 000 Moedas POW: 10 000 000 Distribuição ECD: 30 000 000 coins Carteira de recompenças: 2 000 000 coins (translation etc.) Distribuição DCD (ICO/Prevenda): 10 000 000 coins
POS interest: 7% Número de confirmações: 3 Maturidade da moeda: 50 Idade mínima da moeda: 8 hours Último POW BLOCK: 100 000 Prêmio Block: 100 moedas por block
RPC port= 7026 P2P port= 7025 addnode= server1.pospro.link addnode= server2.pospro.link
– Segurança e controle de todo seu dinheiro – Permite pagamentos internacionais – Custo zero ou baixo – 7% de juros compostos anual – Pagamentos por smarphone feitos com facilidade – Comunidade ativa desde o início
Baixa Inflação POSPRO foi amplamente distribuída ao longo de um curto período da fase de mineração. Não há novas POSPRO, nunca vão ser feitas novas além do juro anual de 7% pago aos detentores de POSPRO . Transações rápidas POSPRO’s prova de sistema de acumulo faz rede POSPRO ser muito rápida. POSPRO é a moeda digital ideal para transações cara a cara e todas as aplicações que valorizam a velocidade.
Forte segurança Blockchain (desde o começo do POS) A rede POSPRO’s é segura contra ataques de outras moedas digitais devido à sua confiabilidade nas operações de mineração em grande escala para executar suas redes. A rede POSPRO não requer o uso de grande escala, ou operações de hardware especializado. POSPRO é muito mais eficiente em termos energéticos do que as redes de moedas digitais tradicionais.
Comunidade é inovadora desde o início POSPRO tem uma comunidade forte e dedicada composta por profissionais e usuários de criptografia talentosos que trabalham duro para levantar a POSPRO , tanto quanto for possível. Esta comunidade é composta pelo programa ECD.
Datas Importantes
• 27 de maio: Lançamento Mainnet • 29 de maio: POSPRO ECD e distribuição DCD
EXCHANGES
Empire-x.ch https://empirex.ch/Market?pair=PSP/BTC https://empirex.ch/Market?pair=PSP/LTC https://empirex.ch/Market?pair=PSP/DOGE https://empirex.ch/Market?pair=PSP/STEPS
Mining pools (POW) http://psp.smarterhash.com http://eu-pool.com:800 http://mineblocks.no-ip.org:2627/pool/PSP/ http://pool.cryptoally.net/
ROADMAP Entre o lançamento da moeda e fase POS
Distribuição inicial na comunidade (ECD)
Registro fechado, para mais informação: www.pospro.link
Essa é a moeda da comunidade, por isso nos fizemos diferente do resto. Para fazer uma moeda de grande sucesso, nós precisamos de várias pessoas / companias e a comunidade.
Para colocar juntos, desde o início precoce (de lançamento) da moeda, uma equipe forte, uma equipe composta por pessoas de diferentes países e com diferentes habilidades. Reservamos um airdrop especial para os participantes. Estes participantes vão nos ajudar a fazer esta moeda um grande sucesso. Eles vão promover POSPRO porque detêm uma parte do estoque de moeda. E aqueles 200 ECD irá segurar a rede desde o dia 1 da fase de POS .
Na verdade , começamos desde o início com uma comunidade de 200 profissionais. Vá ao nosso site para mais informações detalhadas e junte-se a nossa comunidade. www.pospro.link
Doações para distribuição na comunidade (DCD)
Doação DCD / ICO fechada. A moedaPOSPRO passou através de 100 blocos e foram transferidos 10 milhões de moedas para CryptoMaik , CryptoMaik dividiu as moedas para 188 ações, cada ação recebeu 53191 moedas de PSP.
Qualquer um que não cumpra os critérios do ( distribuição antecipada Comunidade ) ECD pode doar alguns Bitcoins durante as semanas de pré-venda. Para esta pré-venda são 10 000 000 moedas reserverdas. Em troca de sua doação, você obtém uma parte equitativa desses 10 000 000 . As moedas são distribuídas uniformemente sobre o número de ações, todo mundo pode comprar sua quota por 0,01 BTC , doação mínima de 1 ação ( 0.01BTC ). Consulte o nosso site para mais informações. ( Primeiras 48 horas 20% de desconto, uma quota de 0,08 BTC ) . Oferecemos a todos a oportunidade de ser um proprietário moeda. Normalmente você pode conseguir algumas moedas muito baratas durante a pré-venda .
Confiar ou nao confiar na POSPRO pré-venda/doação? Há muita desconfiança para ICO de moedas, e ações de pré-venda semelhantes. Infelizmente há muitos scammers que abusam esta forma de distribuição de moeda.
Pedimos ao usuário da Bitcoinalk.org " CryptoMaik " para guiar a nossa DCD ( distribuição da comunidade Doação). Ele é responsável pelas doações e distribuição de 10 milhões de moedas. Ele só vai pagar as doações recebidas , logo que a moeda na MainNet gerar pelo menos 100 blocos e ele receber as 10 000 000 de moedas para a distribuição. Se não podemos produzir uma moeda de trabalho, todas as doações serão devolvidas a você .
Normalmente, a maioria dos usuários vai gritar agora, para este ICO / ação de pré-venda. Por favor, se você não confia nesta forma de pré-venda , o nosso conselho é que não compre ou espere até que a moeda esteja disponível para em troca .
Recompenças
Blockexplorer: 3000 PSP por mês reportagem : 15000 PSP (total para os 3 primeiros relatórios ) antes do fim da ICO ( PM para aprovação antes da publicação ) reportagem : 7500 PSP (total para os 3 primeiros relatórios ) após o lançamento da moeda ( PM para aprovação antes da publicação ) Primeiro piscina extração: 1500 PSP Facebook página : PM
Notícias POSPRO Steemit message (https://steemit.com/crypto-news/@dedriss/pospro--powpos-special-airdrop-ico--community-digital-currency/) XBT.Money News report (http://www.xbt.money/pospro-community-digital-currency/) Medium POSPRO (https://medium.com/@salex91/pospro-pow-pos-special-airdrop-ico-community-digital-currency-d86889a8f2ae#.vdubx4vi5/)
submitted by pedroshooter to CryptoCurrency [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.
BOUNTIES & GIVEAWAYS To Be Announced
WEBSITE http://www.sherlockcoin.org/ (Under Maintenance)
BLOCK EXPLORER To Be Announced
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.
DOWNLOADS
Source Code https://github.com/sherlockcoin/sherlockcoin
Windows Wallet https://www.mediafire.com/?ubm65t3099ba3hs
(https://www.virustotal.com/en/file/6d6df602b8090b105b2a0ccbb3a60a9111cace9dddc8354f8ffad855edfddd2e/analysis/1391839558/)
Sample sherlockcoin.conf file:
rpcuser=username rpcpassword=password rpcallowip=127.0.0.1 rpcport=55883 port=55884 listen=1 daemon=1 server=1 addnode=76.74.178.191
POOLS To be Announced
EXCHANGES To be Announced
SERVICES / OTHER To be Announced
REDDIT http://www.reddit.com/SherlockCoin/
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]

Bitcoin Core 0.10.0 released | Wladimir | Feb 16 2015

Wladimir on Feb 16 2015:
Bitcoin Core version 0.10.0 is now available from:
https://bitcoin.org/bin/0.10.0/
This is a new major version release, bringing both new features and
bug fixes.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
The whole distribution is also available as torrent:
https://bitcoin.org/bin/0.10.0/bitcoin-0.10.0.torrent
magnet:?xt=urn:btih:170c61fe09dafecfbb97cb4dccd32173383f4e68&dn;=0.10.0&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
Upgrading and downgrading

How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrading warning
Because release 0.10.0 makes use of headers-first synchronization and parallel
block download (see further), the block files and databases are not
backwards-compatible with older versions of Bitcoin Core or other software:
  • Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.
  • The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data
directory. Without this your node will need start syncing (or importing from
bootstrap.dat) anew afterwards. It is possible that the data from a completely
synchronised 0.10 node may be usable in older versions as-is, but this is not
supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility.
Notable changes

Faster synchronization
Bitcoin Core now uses 'headers-first synchronization'. This means that we first
ask peers for block headers (a total of 27 megabytes, as of December 2014) and
validate those. In a second stage, when the headers have been discovered, we
download the blocks. However, as we already know about the whole chain in
advance, the blocks can be downloaded in parallel from all available peers.
In practice, this means a much faster and more robust synchronization. On
recent hardware with a decent network link, it can be as little as 3 hours
for an initial full synchronization. You may notice a slower progress in the
very first few minutes, when headers are still being fetched and verified, but
it should gain speed afterwards.
A few RPCs were added/updated as a result of this:
  • getblockchaininfo now returns the number of validated headers in addition to
the number of validated blocks.
  • getpeerinfo lists both the number of blocks and headers we know we have in
common with each peer. While synchronizing, the heights of the blocks that we
have requested from peers (but haven't received yet) are also listed as
'inflight'.
  • A new RPC getchaintips lists all known branches of the block chain,
including those we only have headers for.
Transaction fee changes
This release automatically estimates how high a transaction fee (or how
high a priority) transactions require to be confirmed quickly. The default
settings will create transactions that confirm quickly; see the new
'txconfirmtarget' setting to control the tradeoff between fees and
confirmation times. Fees are added by default unless the 'sendfreetransactions'
setting is enabled.
Prior releases used hard-coded fees (and priorities), and would
sometimes create transactions that took a very long time to confirm.
Statistics used to estimate fees and priorities are saved in the
data directory in the fee_estimates.dat file just before
program shutdown, and are read in at startup.
New command line options for transaction fee changes:
  • -txconfirmtarget=n : create transactions that have enough fees (or priority)
so they are likely to begin confirmation within n blocks (default: 1). This setting
is over-ridden by the -paytxfee option.
  • -sendfreetransactions : Send transactions as zero-fee transactions if possible
(default: 0)
New RPC commands for fee estimation:
  • estimatefee nblocks : Returns approximate fee-per-1,000-bytes needed for
a transaction to begin confirmation within nblocks. Returns -1 if not enough
transactions have been observed to compute a good estimate.
  • estimatepriority nblocks : Returns approximate priority needed for
a zero-fee transaction to begin confirmation within nblocks. Returns -1 if not
enough free transactions have been observed to compute a good
estimate.
RPC access control changes
Subnet matching for the purpose of access control is now done
by matching the binary network address, instead of with string wildcard matching.
For the user this means that -rpcallowip takes a subnet specification, which can be
  • a single IP address (e.g. 1.2.3.4 or fe80::0012:3456:789a:bcde)
  • a network/CIDR (e.g. 1.2.3.0/24 or fe80::0000/64)
  • a network/netmask (e.g. 1.2.3.4/255.255.255.0 or fe80::0012:3456:789a:bcde/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff)
An arbitrary number of -rpcallow arguments can be given. An incoming connection will be accepted if its origin address
matches one of them.
For example:
| 0.9.x and before | 0.10.x |
|--------------------------------------------|---------------------------------------|
| -rpcallowip=192.168.1.1 | -rpcallowip=192.168.1.1 (unchanged) |
| -rpcallowip=192.168.1.* | -rpcallowip=192.168.1.0/24 |
| -rpcallowip=192.168.* | -rpcallowip=192.168.0.0/16 |
| -rpcallowip=* (dangerous!) | -rpcallowip=::/0 (still dangerous!) |
Using wildcards will result in the rule being rejected with the following error in debug.log:
 Error: Invalid -rpcallowip subnet specification: *. Valid are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). 
REST interface
A new HTTP API is exposed when running with the -rest flag, which allows
unauthenticated access to public node data.
It is served on the same port as RPC, but does not need a password, and uses
plain HTTP instead of JSON-RPC.
Assuming a local RPC server running on port 8332, it is possible to request:
In every case, EXT can be bin (for raw binary data), hex (for hex-encoded
binary) or json.
For more details, see the doc/REST-interface.md document in the repository.
RPC Server "Warm-Up" Mode
The RPC server is started earlier now, before most of the expensive
intialisations like loading the block index. It is available now almost
immediately after starting the process. However, until all initialisations
are done, it always returns an immediate error with code -28 to all calls.
This new behaviour can be useful for clients to know that a server is already
started and will be available soon (for instance, so that they do not
have to start it themselves).
Improved signing security
For 0.10 the security of signing against unusual attacks has been
improved by making the signatures constant time and deterministic.
This change is a result of switching signing to use libsecp256k1
instead of OpenSSL. Libsecp256k1 is a cryptographic library
optimized for the curve Bitcoin uses which was created by Bitcoin
Core developer Pieter Wuille.
There exist attacks[1] against most ECC implementations where an
attacker on shared virtual machine hardware could extract a private
key if they could cause a target to sign using the same key hundreds
of times. While using shared hosts and reusing keys are inadvisable
for other reasons, it's a better practice to avoid the exposure.
OpenSSL has code in their source repository for derandomization
and reduction in timing leaks that we've eagerly wanted to use for a
long time, but this functionality has still not made its
way into a released version of OpenSSL. Libsecp256k1 achieves
significantly stronger protection: As far as we're aware this is
the only deployed implementation of constant time signing for
the curve Bitcoin uses and we have reason to believe that
libsecp256k1 is better tested and more thoroughly reviewed
than the implementation in OpenSSL.
[1] https://eprint.iacr.org/2014/161.pdf
Watch-only wallet support
The wallet can now track transactions to and from wallets for which you know
all addresses (or scripts), even without the private keys.
This can be used to track payments without needing the private keys online on a
possibly vulnerable system. In addition, it can help for (manual) construction
of multisig transactions where you are only one of the signers.
One new RPC, importaddress, is added which functions similarly to
importprivkey, but instead takes an address or script (in hexadecimal) as
argument. After using it, outputs credited to this address or script are
considered to be received, and transactions consuming these outputs will be
considered to be sent.
The following RPCs have optional support for watch-only:
getbalance, listreceivedbyaddress, listreceivedbyaccount,
listtransactions, listaccounts, listsinceblock, gettransaction. See the
RPC documentation for those methods for more information.
Compared to using getrawtransaction, this mechanism does not require
-txindex, scales better, integrates better with the wallet, and is compatible
with future block chain pruning functionality. It does mean that all relevant
addresses need to added to the wallet before the payment, though.
Consensus library
Starting from 0.10.0, the Bitcoin Core distribution includes a consensus library.
The purpose of this library is to make the verification functionality that is
critical to Bitcoin's consensus available to other applications, e.g. to language
bindings such as [python-bitcoinlib](https://pypi.python.org/pypi/python-bitcoinlib) or
alternative node implementations.
This library is called libbitcoinconsensus.so (or, .dll for Windows).
Its interface is defined in the C header [bitcoinconsensus.h](https://github.com/bitcoin/bitcoin/blob/0.10/src/script/bitcoinconsensus.h).
In its initial version the API includes two functions:
  • bitcoinconsensus_verify_script verifies a script. It returns whether the indicated input of the provided serialized transaction
correctly spends the passed scriptPubKey under additional constraints indicated by flags
  • bitcoinconsensus_version returns the API version, currently at an experimental 0
The functionality is planned to be extended to e.g. UTXO management in upcoming releases, but the interface
for existing methods should remain stable.
Standard script rules relaxed for P2SH addresses
The IsStandard() rules have been almost completely removed for P2SH
redemption scripts, allowing applications to make use of any valid
script type, such as "n-of-m OR y", hash-locked oracle addresses, etc.
While the Bitcoin protocol has always supported these types of script,
actually using them on mainnet has been previously inconvenient as
standard Bitcoin Core nodes wouldn't relay them to miners, nor would
most miners include them in blocks they mined.
bitcoin-tx
It has been observed that many of the RPC functions offered by bitcoind are
"pure functions", and operate independently of the bitcoind wallet. This
included many of the RPC "raw transaction" API functions, such as
createrawtransaction.
bitcoin-tx is a newly introduced command line utility designed to enable easy
manipulation of bitcoin transactions. A summary of its operation may be
obtained via "bitcoin-tx --help" Transactions may be created or signed in a
manner similar to the RPC raw tx API. Transactions may be updated, deleting
inputs or outputs, or appending new inputs and outputs. Custom scripts may be
easily composed using a simple text notation, borrowed from the bitcoin test
suite.
This tool may be used for experimenting with new transaction types, signing
multi-party transactions, and many other uses. Long term, the goal is to
deprecate and remove "pure function" RPC API calls, as those do not require a
server round-trip to execute.
Other utilities "bitcoin-key" and "bitcoin-script" have been proposed, making
key and script operations easily accessible via command line.
Mining and relay policy enhancements
Bitcoin Core's block templates are now for version 3 blocks only, and any mining
software relying on its getblocktemplate must be updated in parallel to use
libblkmaker either version 0.4.2 or any version from 0.5.1 onward.
If you are solo mining, this will affect you the moment you upgrade Bitcoin
Core, which must be done prior to BIP66 achieving its 951/1001 status.
If you are mining with the stratum mining protocol: this does not affect you.
If you are mining with the getblocktemplate protocol to a pool: this will affect
you at the pool operator's discretion, which must be no later than BIP66
achieving its 951/1001 status.
The prioritisetransaction RPC method has been added to enable miners to
manipulate the priority of transactions on an individual basis.
Bitcoin Core now supports BIP 22 long polling, so mining software can be
notified immediately of new templates rather than having to poll periodically.
Support for BIP 23 block proposals is now available in Bitcoin Core's
getblocktemplate method. This enables miners to check the basic validity of
their next block before expending work on it, reducing risks of accidental
hardforks or mining invalid blocks.
Two new options to control mining policy:
  • -datacarrier=0/1 : Relay and mine "data carrier" (OP_RETURN) transactions
if this is 1.
  • -datacarriersize=n : Maximum size, in bytes, we consider acceptable for
"data carrier" outputs.
The relay policy has changed to more properly implement the desired behavior of not
relaying free (or very low fee) transactions unless they have a priority above the
AllowFreeThreshold(), in which case they are relayed subject to the rate limiter.
BIP 66: strict DER encoding for signatures
Bitcoin Core 0.10 implements BIP 66, which introduces block version 3, and a new
consensus rule, which prohibits non-DER signatures. Such transactions have been
non-standard since Bitcoin v0.8.0 (released in February 2013), but were
technically still permitted inside blocks.
This change breaks the dependency on OpenSSL's signature parsing, and is
required if implementations would want to remove all of OpenSSL from the
consensus code.
The same miner-voting mechanism as in BIP 34 is used: when 751 out of a
sequence of 1001 blocks have version number 3 or higher, the new consensus
rule becomes active for those blocks. When 951 out of a sequence of 1001
blocks have version number 3 or higher, it becomes mandatory for all blocks.
Backward compatibility with current mining software is NOT provided, thus miners
should read the first paragraph of "Mining and relay policy enhancements" above.
0.10.0 Change log

Detailed release notes follow. This overview includes changes that affect external
behavior, not code moves, refactors or string updates.
RPC:
  • f923c07 Support IPv6 lookup in bitcoin-cli even when IPv6 only bound on localhost
  • b641c9c Fix addnode "onetry": Connect with OpenNetworkConnection
  • 171ca77 estimatefee / estimatepriority RPC methods
  • b750cf1 Remove cli functionality from bitcoind
  • f6984e8 Add "chain" to getmininginfo, improve help in getblockchaininfo
  • 99ddc6c Add nLocalServices info to RPC getinfo
  • cf0c47b Remove getwork() RPC call
  • 2a72d45 prioritisetransaction
  • e44fea5 Add an option -datacarrier to allow users to disable relaying/mining data carrier transactions
  • 2ec5a3d Prevent easy RPC memory exhaustion attack
  • d4640d7 Added argument to getbalance to include watchonly addresses and fixed errors in balance calculation
  • 83f3543 Added argument to listaccounts to include watchonly addresses
  • 952877e Showing 'involvesWatchonly' property for transactions returned by 'listtransactions' and 'listsinceblock'. It is only appended when the transaction involves a watchonly address
  • d7d5d23 Added argument to listtransactions and listsinceblock to include watchonly addresses
  • f87ba3d added includeWatchonly argument to 'gettransaction' because it affects balance calculation
  • 0fa2f88 added includedWatchonly argument to listreceivedbyaddress/...account
  • 6c37f7f getrawchangeaddress: fail when keypool exhausted and wallet locked
  • ff6a7af getblocktemplate: longpolling support
  • c4a321f Add peerid to getpeerinfo to allow correlation with the logs
  • 1b4568c Add vout to ListTransactions output
  • b33bd7a Implement "getchaintips" RPC command to monitor blockchain forks
  • 733177e Remove size limit in RPC client, keep it in server
  • 6b5b7cb Categorize rpc help overview
  • 6f2c26a Closely track mempool byte total. Add "getmempoolinfo" RPC
  • aa82795 Add detailed network info to getnetworkinfo RPC
  • 01094bd Don't reveal whether password is <20 or >20 characters in RPC
  • 57153d4 rpc: Compute number of confirmations of a block from block height
  • ff36cbe getnetworkinfo: export local node's client sub-version string
  • d14d7de SanitizeString: allow '(' and ')'
  • 31d6390 Fixed setaccount accepting foreign address
  • b5ec5fe update getnetworkinfo help with subversion
  • ad6e601 RPC additions after headers-first
  • 33dfbf5 rpc: Fix leveldb iterator leak, and flush before gettxoutsetinfo
  • 2aa6329 Enable customising node policy for datacarrier data size with a -datacarriersize option
  • f877aaa submitblock: Use a temporary CValidationState to determine accurately the outcome of ProcessBlock
  • e69a587 submitblock: Support for returning specific rejection reasons
  • af82884 Add "warmup mode" for RPC server
  • e2655e0 Add unauthenticated HTTP REST interface to public blockchain data
  • 683dc40 Disable SSLv3 (in favor of TLS) for the RPC client and server
  • 44b4c0d signrawtransaction: validate private key
  • 9765a50 Implement BIP 23 Block Proposal
  • f9de17e Add warning comment to getinfo
Command-line options:
  • ee21912 Use netmasks instead of wildcards for IP address matching
  • deb3572 Add -rpcbind option to allow binding RPC port on a specific interface
  • 96b733e Add -version option to get just the version
  • 1569353 Add -stopafterblockimport option
  • 77cbd46 Let -zapwallettxes recover transaction meta data
  • 1c750db remove -tor compatibility code (only allow -onion)
  • 4aaa017 rework help messages for fee-related options
  • 4278b1d Clarify error message when invalid -rpcallowip
  • 6b407e4 -datadir is now allowed in config files
  • bdd5b58 Add option -sysperms to disable 077 umask (create new files with system default umask)
  • cbe39a3 Add "bitcoin-tx" command line utility and supporting modules
  • dbca89b Trigger -alertnotify if network is upgrading without you
  • ad96e7c Make -reindex cope with out-of-order blocks
  • 16d5194 Skip reindexed blocks individually
  • ec01243 --tracerpc option for regression tests
  • f654f00 Change -genproclimit default to 1
  • 3c77714 Make -proxy set all network types, avoiding a connect leak
  • 57be955 Remove -printblock, -printblocktree, and -printblockindex
  • ad3d208 remove -maxorphanblocks config parameter since it is no longer functional
Block and transaction handling:
  • 7a0e84d ProcessGetData(): abort if a block file is missing from disk
  • 8c93bf4 LoadBlockIndexDB(): Require block db reindex if any blk*.dat files are missing
  • 77339e5 Get rid of the static chainMostWork (optimization)
  • 4e0eed8 Allow ActivateBestChain to release its lock on cs_main
  • 18e7216 Push cs_mains down in ProcessBlock
  • fa126ef Avoid undefined behavior using CFlatData in CScript serialization
  • 7f3b4e9 Relax IsStandard rules for pay-to-script-hash transactions
  • c9a0918 Add a skiplist to the CBlockIndex structure
  • bc42503 Use unordered_map for CCoinsViewCache with salted hash (optimization)
  • d4d3fbd Do not flush the cache after every block outside of IBD (optimization)
  • ad08d0b Bugfix: make CCoinsViewMemPool support pruned entries in underlying cache
  • 5734d4d Only remove actualy failed blocks from setBlockIndexValid
  • d70bc52 Rework block processing benchmark code
  • 714a3e6 Only keep setBlockIndexValid entries that are possible improvements
  • ea100c7 Reduce maximum coinscache size during verification (reduce memory usage)
  • 4fad8e6 Reject transactions with excessive numbers of sigops
  • b0875eb Allow BatchWrite to destroy its input, reducing copying (optimization)
  • 92bb6f2 Bypass reloading blocks from disk (optimization)
  • 2e28031 Perform CVerifyDB on pcoinsdbview instead of pcoinsTip (reduce memory usage)
  • ab15b2e Avoid copying undo data (optimization)
  • 341735e Headers-first synchronization
  • afc32c5 Fix rebuild-chainstate feature and improve its performance
  • e11b2ce Fix large reorgs
  • ed6d1a2 Keep information about all block files in memory
  • a48f2d6 Abstract context-dependent block checking from acceptance
  • 7e615f5 Fixed mempool sync after sending a transaction
  • 51ce901 Improve chainstate/blockindex disk writing policy
  • a206950 Introduce separate flushing modes
  • 9ec75c5 Add a locking mechanism to IsInitialBlockDownload to ensure it never goes from false to true
  • 868d041 Remove coinbase-dependant transactions during reorg
  • 723d12c Remove txn which are invalidated by coinbase maturity during reorg
  • 0cb8763 Check against MANDATORY flags prior to accepting to mempool
  • 8446262 Reject headers that build on an invalid parent
  • 008138c Bugfix: only track UTXO modification after lookup
P2P protocol and network code:
  • f80cffa Do not trigger a DoS ban if SCRIPT_VERIFY_NULLDUMMY fails
  • c30329a Add testnet DNS seed of Alex Kotenko
  • 45a4baf Add testnet DNS seed of Andreas Schildbach
  • f1920e8 Ping automatically every 2 minutes (unconditionally)
  • 806fd19 Allocate receive buffers in on the fly
  • 6ecf3ed Display unknown commands received
  • aa81564 Track peers' available blocks
  • caf6150 Use async name resolving to improve net thread responsiveness
  • 9f4da19 Use pong receive time rather than processing time
  • 0127a9b remove SOCKS4 support from core and GUI, use SOCKS5
  • 40f5cb8 Send rejects and apply DoS scoring for errors in direct block validation
  • dc942e6 Introduce whitelisted peers
  • c994d2e prevent SOCKET leak in BindListenPort()
  • a60120e Add built-in seeds for .onion
  • 60dc8e4 Allow -onlynet=onion to be used
  • 3a56de7 addrman: Do not propagate obviously poor addresses onto the network
  • 6050ab6 netbase: Make SOCKS5 negotiation interruptible
  • 604ee2a Remove tx from AlreadyAskedFor list once we receive it, not when we process it
  • efad808 Avoid reject message feedback loops
  • 71697f9 Separate protocol versioning from clientversion
  • 20a5f61 Don't relay alerts to peers before version negotiation
  • b4ee0bd Introduce preferred download peers
  • 845c86d Do not use third party services for IP detection
  • 12a49ca Limit the number of new addressses to accumulate
  • 35e408f Regard connection failures as attempt for addrman
  • a3a7317 Introduce 10 minute block download timeout
  • 3022e7d Require sufficent priority for relay of free transactions
  • 58fda4d Update seed IPs, based on bitcoin.sipa.be crawler data
  • 18021d0 Remove bitnodes.io from dnsseeds.
Validation:
  • 6fd7ef2 Also switch the (unused) verification code to low-s instead of even-s
  • 584a358 Do merkle root and txid duplicates check simultaneously
  • 217a5c9 When transaction outputs exceed inputs, show the offending amounts so as to aid debugging
  • f74fc9b Print input index when signature validation fails, to aid debugging
  • 6fd59ee script.h: set_vch() should shift a >32 bit value
  • d752ba8 Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) (test only)
  • 698c6ab Add SCRIPT_VERIFY_MINIMALDATA (BIP62 rules 3 and 4) (test only)
  • ab9edbd script: create sane error return codes for script validation and remove logging
  • 219a147 script: check ScriptError values in script tests
  • 0391423 Discourage NOPs reserved for soft-fork upgrades
  • 98b135f Make STRICTENC invalid pubkeys fail the script rather than the opcode
  • 307f7d4 Report script evaluation failures in log and reject messages
  • ace39db consensus: guard against openssl's new strict DER checks
  • 12b7c44 Improve robustness of DER recoding code
  • 76ce5c8 fail immediately on an empty signature
Build system:
  • f25e3ad Fix build in OS X 10.9
  • 65e8ba4 build: Switch to non-recursive make
  • 460b32d build: fix broken boost chrono check on some platforms
  • 9ce0774 build: Fix windows configure when using --with-qt-libdir
  • ea96475 build: Add mention of --disable-wallet to bdb48 error messages
  • 1dec09b depends: add shared dependency builder
  • c101c76 build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix
  • e432a5f build: add option for reducing exports (v2)
  • 6134b43 Fixing condition 'sabotaging' MSVC build
  • af0bd5e osx: fix signing to make Gatekeeper happy (again)
  • a7d1f03 build: fix dynamic boost check when --with-boost= is used
  • d5fd094 build: fix qt test build when libprotobuf is in a non-standard path
  • 2cf5f16 Add libbitcoinconsensus library
  • 914868a build: add a deterministic dmg signer
  • 2d375fe depends: bump openssl to 1.0.1k
  • b7a4ecc Build: Only check for boost when building code that requires it
Wallet:
  • b33d1f5 Use fee/priority estimates in wallet CreateTransaction
  • 4b7b1bb Sanity checks for estimates
  • c898846 Add support for watch-only addresses
  • d5087d1 Use script matching rather than destination matching for watch-only
  • d88af56 Fee fixes
  • a35b55b Dont run full check every time we decrypt wallet
  • 3a7c348 Fix make_change to not create half-satoshis
  • f606bb9 fix a possible memory leak in CWalletDB::Recover
  • 870da77 fix possible memory leaks in CWallet::EncryptWallet
  • ccca27a Watch-only fixes
  • 9b1627d [Wallet] Reduce minTxFee for transaction creation to 1000 satoshis
  • a53fd41 Deterministic signing
  • 15ad0b5 Apply AreSane() checks to the fees from the network
  • 11855c1 Enforce minRelayTxFee on wallet created tx and add a maxtxfee option
GUI:
  • c21c74b osx: Fix missing dock menu with qt5
  • b90711c Fix Transaction details shows wrong To:
  • 516053c Make links in 'About Bitcoin Core' clickable
  • bdc83e8 Ensure payment request network matches client network
  • 65f78a1 Add GUI view of peer information
  • 06a91d9 VerifyDB progress reporting
  • fe6bff2 Add BerkeleyDB version info to RPCConsole
  • b917555 PeerTableModel: Fix potential deadlock. #4296
  • dff0e3b Improve rpc console history behavior
  • 95a9383 Remove CENT-fee-rule from coin control completely
  • 56b07d2 Allow setting listen via GUI
  • d95ba75 Log messages with type>QtDebugMsg as non-debug
  • 8969828 New status bar Unit Display Control and related changes
  • 674c070 seed OpenSSL PNRG with Windows event data
  • 509f926 Payment request parsing on startup now only changes network if a valid network name is specified
  • acd432b Prevent balloon-spam after rescan
  • 7007402 Implement SI-style (thin space) thoudands separator
  • 91cce17 Use fixed-point arithmetic in amount spinbox
  • bdba2dd Remove an obscure option no-one cares about
  • bd0aa10 Replace the temporary file hack currently used to change Bitcoin-Qt's dock icon (OS X) with a buffer-based solution
  • 94e1b9e Re-work overviewpage UI
  • 8bfdc9a Better looking trayicon
  • b197bf3 disable tray interactions when client model set to 0
  • 1c5f0af Add column Watch-only to transactions list
  • 21f139b Fix tablet crash. closes #4854
  • e84843c Broken addresses on command line no longer trigger testnet
  • a49f11d Change splash screen to normal window
  • 1f9be98 Disable App Nap on OSX 10.9+
  • 27c3e91 Add proxy to options overridden if necessary
  • 4bd1185 Allow "emergency" shutdown during startup
  • d52f072 Don't show wallet options in the preferences menu when running with -disablewallet
  • 6093aa1 Qt: QProgressBar CPU-Issue workaround
  • 0ed9675 [Wallet] Add global boolean whether to send free transactions (default=true)
  • ed3e5e4 [Wallet] Add global boolean whether to pay at least the custom fee (default=true)
  • e7876b2 [Wallet] Prevent user from paying a non-sense fee
  • c1c9d5b Add Smartfee to GUI
  • e0a25c5 Make askpassphrase dialog behave more sanely
  • 94b362d On close of splashscreen interrupt verifyDB
  • b790d13 English translation update
  • 8543b0d Correct tooltip on address book page
Tests:
  • b41e594 Fix script test handling of empty scripts
  • d3a33fc Test CHECKMULTISIG with m == 0 and n == 0
  • 29c1749 Let tx (in)valid tests use any SCRIPT_VERIFY flag
  • 6380180 Add rejection of non-null CHECKMULTISIG dummy values
  • 21bf3d2 Add tests for BoostAsioToCNetAddr
  • b5ad5e7 Add Python test for -rpcbind and -rpcallowip
  • 9ec0306 Add CODESEPARATOFindAndDelete() tests
  • 75ebced Added many rpc wallet tests
  • 0193fb8 Allow multiple regression tests to run at once
  • 92a6220 Hook up sanity checks
  • 3820e01 Extend and move all crypto tests to crypto_tests.cpp
  • 3f9a019 added list/get received by address/ account tests
  • a90689f Remove timing-based signature cache unit test
  • 236982c Add skiplist unit tests
  • f4b00be Add CChain::GetLocator() unit test
  • b45a6e8 Add test for getblocktemplate longpolling
  • cdf305e Set -discover=0 in regtest framework
  • ed02282 additional test for OP_SIZE in script_valid.json
  • 0072d98 script tests: BOOLAND, BOOLOR decode to integer
  • 833ff16 script tests: values that overflow to 0 are true
  • 4cac5db script tests: value with trailing 0x00 is true
  • 89101c6 script test: test case for 5-byte bools
  • d2d9dc0 script tests: add tests for CHECKMULTISIG limits
  • d789386 Add "it works" test for bitcoin-tx
  • df4d61e Add bitcoin-tx tests
  • aa41ac2 Test IsPushOnly() with invalid push
  • 6022b5d Make script_{valid,invalid}.json validation flags configurable
  • 8138cbe Add automatic script test generation, and actual checksig tests
  • ed27e53 Add coins_tests with a large randomized CCoinViewCache test
  • 9df9cf5 Make SCRIPT_VERIFY_STRICTENC compatible with BIP62
  • dcb9846 Extend getchaintips RPC test
  • 554147a Ensure MINIMALDATA invalid tests can only fail one way
  • dfeec18 Test every numeric-accepting opcode for correct handling of the numeric minimal encoding rule
  • 2b62e17 Clearly separate PUSHDATA and numeric argument MINIMALDATA tests
  • 16d78bd Add valid invert of invalid every numeric opcode tests
  • f635269 tests: enable alertnotify test for Windows
  • 7a41614 tests: allow rpc-tests to get filenames for bitcoind and bitcoin-cli from the environment
  • 5122ea7 tests: fix forknotify.py on windows
  • fa7f8cd tests: remove old pull-tester scripts
  • 7667850 tests: replace the old (unused since Travis) tests with new rpc test scripts
  • f4e0aef Do signature-s negation inside the tests
  • 1837987 Optimize -regtest setgenerate block generation
  • 2db4c8a Fix node ranges in the test framework
  • a8b2ce5 regression test only setmocktime RPC call
  • daf03e7 RPC tests: create initial chain with specific timestamps
  • 8656dbb Port/fix txnmall.sh regression test
  • ca81587 Test the exact order of CHECKMULTISIG sig/pubkey evaluation
  • 7357893 Prioritize and display -testsafemode status in UI
  • f321d6b Add key generation/verification to ECC sanity check
  • 132ea9b miner_tests: Disable checkpoints so they don't fail the subsidy-change test
  • bc6cb41 QA RPC tests: Add tests block block proposals
  • f67a9ce Use deterministically generated script tests
  • 11d7a7d [RPC] add rpc-test for http keep-alive (persistent connections)
  • 34318d7 RPC-test based on invalidateblock for mempool coinbase spends
  • 76ec867 Use actually valid transactions for script tests
  • c8589bf Add actual signature tests
  • e2677d7 Fix smartfees test for change to relay policy
  • 263b65e tests: run sanity checks in tests too
Miscellaneous:
  • 122549f Fix incorrect checkpoint data for testnet3
  • 5bd02cf Log used config file to debug.log on startup
  • 68ba85f Updated Debian example bitcoin.conf with config from wiki + removed some cruft and updated comments
  • e5ee8f0 Remove -beta suffix
  • 38405ac Add comment regarding experimental-use service bits
  • be873f6 Issue warning if collecting RandSeed data failed
  • 8ae973c Allocate more space if necessary in RandSeedAddPerfMon
  • 675bcd5 Correct comment for 15-of-15 p2sh script size
  • fda3fed libsecp256k1 integration
  • 2e36866 Show nodeid instead of addresses in log (for anonymity) unless otherwise requested
  • cd01a5e Enable paranoid corruption checks in LevelDB >= 1.16
  • 9365937 Add comment about never updating nTimeOffset past 199 samples
  • 403c1bf contrib: remove getwork-based pyminer (as getwork API call has been removed)
  • 0c3e101 contrib: Added systemd .service file in order to help distributions integrate bitcoind
  • 0a0878d doc: Add new DNSseed policy
  • 2887bff Update coding style and add .clang-format
  • 5cbda4f Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope
  • b4a72a7 contrib/linearize: split output files based on new-timestamp-year or max-file-size
  • e982b57 Use explicit fflush() instead of setvbuf()
  • 234bfbf contrib: Add init scripts and docs for Upstart and OpenRC
  • 01c2807 Add warning about the merkle-tree algorithm duplicate txid flaw
  • d6712db Also create pid file in non-daemon mode
  • 772ab0e contrib: use batched JSON-RPC in linarize-hashes (optimization)
  • 7ab4358 Update bash-completion for v0.10
  • 6e6a36c contrib: show pull # in prompt for github-merge script
  • 5b9f842 Upgrade leveldb to 1.18, make chainstate databases compatible between ARM and x86 (issue #2293)
  • 4e7c219 Catch UTXO set read errors and shutdown
  • 867c600 Catch LevelDB errors during flush
  • 06ca065 Fix CScriptID(const CScript& in) in empty script case
Credits

Thanks to everyone who contributed to this release:
  • 21E14
  • Adam Weiss
  • Aitor Pazos
  • Alexander Jeng
  • Alex Morcos
  • Alon Muroch
  • Andreas Schildbach
  • Andrew Poelstra
  • Andy Alness
  • Ashley Holman
  • Benedict Chan
  • Ben Holden-Crowther
  • Bryan Bishop
  • BtcDrak
  • Christian von Roques
  • Clinton Christian
  • Cory Fields
  • Cozz Lovan
  • daniel
  • Daniel Kraft
  • David Hill
  • Derek701
  • dexX7
  • dllud
  • Dominyk Tiller
  • Doug
  • elichai
  • elkingtowa
  • ENikS
  • Eric Shaw
  • Federico Bond
  • Francis GASCHET
  • Gavin Andresen
  • Giuseppe Mazzotta
  • Glenn Willen
  • Gregory Maxwell
  • gubatron
  • HarryWu
  • himynameismartin
  • Huang Le
  • Ian Carroll
  • imharrywu
  • Jameson Lopp
  • Janusz Lenar
  • JaSK
  • Jeff Garzik
  • JL2035
  • Johnathan Corgan
  • Jonas Schnelli
  • jtimon
  • Julian Haight
  • Kamil Domanski
  • kazcw
  • kevin
  • kiwigb
  • Kosta Zertsekel
  • LongShao007
  • Luke Dashjr
  • Mark Friedenbach
  • Mathy Vanvoorden
  • Matt Corallo
  • Matthew Bogosian
  • Micha
  • Michael Ford
  • Mike Hearn
  • mrbandrews
  • mruddy
  • ntrgn
  • Otto Allmendinger
  • paveljanik
  • Pavel Vasin
  • Peter Todd
  • phantomcircuit
  • Philip Kaufmann
  • Pieter Wuille
  • pryds
  • randy-waterhouse
  • R E Broadley
  • Rose Toomey
  • Ross Nicoll
  • Roy Badami
  • Ruben Dario Ponticelli
  • Rune K. Svendsen
  • Ryan X. Charles
  • Saivann
  • sandakersmann
  • SergioDemianLerner
  • shshshsh
  • sinetek
  • Stuart Cardall
  • Suhas Daftuar
  • Tawanda Kembo
  • Teran McKinney
  • tm314159
  • Tom Harding
  • Trevin Hofmann
  • Whit J
  • Wladimir J. van der Laan
  • Yoichi Hirai
  • Zak Wilcox
As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).
Also lots of thanks to the bitcoin.org website team David A. Harding and Saivann Carignan.
Wladimir
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-February/007480.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

Marscoin specifications. 33 Million Total Coins 1 block per 2 Mars minutes. 50 coins per block. 590 Blocks per Mars Day. Difficulty retardet every 24 Hours 39 Minuter (1 Mars Day)

MARSCOIN MRS
Currently, there are two attempts underway to establish the first human base on Mars. While technologically not impossible funding such a project (estimated at 6-20 billion) is a major obstacle. If you share our dream of making that first giant step for mankind a reality, then Marscoin might be something for you.
Simply by using Marscoin, a bitcoin alternative, you will automatically participate in serious boostraping efforts to colonize Mars.
We donated 350,000 Marscoins to MarsOne, a non-profit that attempts to build the first colony on Mars. With your help - by adopting Marscoin - we will be able to help fund mankinds first colony on Mars simply by kickstarting the financial system of the future Mars colony!
In addition, once the colony is set up MarsOne or a Mars colonist could take Marscoin to Mars and install it. That means that your Marscoins would continue to be yours on Mars, forever.
Website http://marscoin.org/
Block Explorer / Crawler http://explore.marscoin.org/
Contact [email protected]
SPECIFICATIONS Scrypt Algo 1 block per 2 Mars minutes 50 coins per block 590 Blocks Per Mars Day Difficulty retarget every 24 hours 39 Minutes (Mars day) Subsidy halves every Mars Year ~33 million total coins
PREMINE 300k donation premined for non-profit MarsOne.
DOWNLOADS
Windows https://mega.co.nz/#...SEhScyfL_ZmfiZk
Virustotal https://www.virustot...sis/1390829585/
MacOS https://mega.co.nz/#...chDJZiWW1sl_hrI
Linux https://mega.co.nz/#...62qd2R5duKSFD2g
Source Code https://github.com/marscoin/marscoin.
Sample marscoin.conf rpcuser=username rpcpassword=password rpcallowip=localhost rpcport= port= gen=0 server=1 addnode= PORTS RPC Port: None Available. P2P Port: None Available.
POOLS
http://mars.pooler.cc/ http://pool.marscoin.org/ http://mars.pooler.cc/ http://p2pool.neocities.org/
EXCHANGES
None Available.
SOCIAL
Twitter https://twitter.com/marscoinorg
Facebook https://www.facebook.com/marscoin
Forum http://www.mars-project.org/
Reddit http://www.reddit.com/marscoin
SERVICES / OTHER
Faucet http://faucet.marscoin.org/
Payment Processor https://coinpayments.net/
Edited by Jimmy, 31 January 2014 - 05:48 PM. Added / Updated Information. CryptoCoinTalk.com Discussing the world of cryptocoins and cryptocurrencies
Information posted on CryptoCoinTalk.com doesn't constitute legal or financial advice. Please consult a licensed trained professional. CryptoCoinTalk.com does NOT host cryptocoin mining software nor does it create or develop any cryptocoins. Cryptocointalk.com doesn't endorse any cryptocoins or cryptocoin services. Please follow all local, state, federal, and international laws. Any views expressed are provided for informational purposes only and represent only the opinions of this CryptoCoinTalk.com website and should not be construed in any way as an offer, an endorsement, testimony, or inducement to invest. All cryptocoin launch announcements / information threads are informational threads created to provide information about a new cryptocoin. In no way do these launch announcements / informational threads denote that CryptoCoinTalk developed the launched cryptocoin. Download links come without any warranties implied. Download and use cryptocoin / cryptocurrency software, mining pools, or any listed services at YOUR OWN RISK.
submitted by MoonBaby666 to marscoin [link] [comments]

Welcome to Rainbowcoin! Information within...

Welcome to the Rainbowcoin gathering place on Reddit. This sub is volunteer run because this coin deserves our love & support.
Whether you already know about cryptocurrencies, or this is your introduction, we hope you will dive in and get yourself some Rainbowcoins of your own, especially this early, while they are quite cheap to acquire(but rising fast!).
After you learn a little about the coins, please download a wallet and start mining, or hit the exchanges and acquire some that way.
Here is a list of links related to our beloved Rainbowcoin:
RAINBOWCOIN (LGBT)
Rainbowcoin is the bitcoin-based cryptocurrency to be proud about.
Website
www.rainbowcoin.info
DOWNLOADS
Windows
https://www.mediafir...4rcdzyxtm9y8ie7 https://github.com/Rainbowcoin/Win32
Virustotal
https://www.virustot...5bb40/analysis/
MacOS
None Available.
Linux
https://mega.co.nz/#...-_yIX_YC_iXBJew
Block Explorer / Crawler
http://5.175.185.36/rainbow/explore
Source Code
(https://github.com/R...oin/Rainbowcoin)
Sample: rainbowcoin.conf
rpcuser=username rpcpassword=password rpcallowip=localhost rpcport= port= gen=0 server=1 addnode= PORTS RPC Port: None Available. P2P Port: None Available.
POOLS
(http://rainbow.hashrapid.com/) http://172.245.183.41/lgbt/public/
EXCHANGES
CRYPTORUSH
SOCIAL
Twitter
Facebook
SERVICES / OTHER
Faucets:
http://deathxchange....ainbowcoins.php rhttp://rainbowcoin.altcoinfaucet.net/eddit!
SPECIFICATIONS
SHA-256 Algo Halving at 50000 blocks Initial coins per block 10000 coins Target spacing 1 min Target timespan 960 h Coinbase maturity 2 blocks Max coinbase 1000000000 coins
submitted by RainbowCoin to Rainbowcoin [link] [comments]

How to give your bitcoin node commands using a web server Neo Nodes Part 3: RPC Nodes Bitcoin NodeJS Part 1 - Hello World bitcoin-cli and bitcoind - Breaking Down Bitcoin Ep. 2 Bitcoin RPC Remote Code Execution Exploit for BitcoinCore 0.9-0.15.1 CVE-2017-9230

addnode (0.17.99 RPC) addnode "node" "addremoveonetry". Attempts to add or remove a node from the addnode list. Or try a connection to a node once. Every Bitcoin RPC command can be added as an endpoint in this API to make fully functional Bitcoin applications. With these 12 methods we have setup a communication with our Bitcoin node that will ... addnode¶. addnode "node" "command". Attempts to add or remove a node from the addnode list. Or try a connection to a node once. Nodes added using addnode (or -connect) are protected from DoS disconnection and are not required to be full nodes/support SegWit as other outbound peers are (though such peers will not be synced from). addnode "node" "addremoveonetry" Attempts to add or remove a node from the addnode list. Or try a connection to a node once. Nodes added using addnode (or -connect) are protected from DoS disconnection and are not required to be full nodes/support SegWit as other outbound peers are (though such peers will not be synced from). Arguments: 1. "node" (string, required) The node (see getpeerinfo ... This site aims to provide the docs you need to understand Bitcoin and start building Bitcoin-based applications.

[index] [4568] [7561] [15309] [24572] [10809] [30229] [43574] [9212] [34302] [26320]

How to give your bitcoin node commands using a web server

Bitcoin JSON-RPC Tutorial 2 - VPS Setup - Duration: 6:28. m1xolyd1an 15,422 views. 6:28. Setting Up Bitcoin Fullnode on Raspberry Pi 2 - Bitcoin Core 0.12 - Duration: 36:08. ... In this video I revisit an old topic where several things have changed since 2015 in regards to using the JSON-RPC to communicate with your node with an apache server with PHP. https://www.amazon ... Bitcoin JSON-RPC Tutorial 4 - Command Line Interface - Duration: 5:14. m1xolyd1an Recommended for you. 5:14. Bitcoin Lightning Network Tutorial Part 1 - Setup Bitcoind - Duration: 15:10. ... Bitcoin JSON-RPC Tutorial 3 - bitcoin.conf - Duration: 8:10. m1xolyd1an 13,667 views. 8:10. How to build a monero full (remote) node on ubuntu linux server - Duration: 14:32. ... Bitcoin NodeJS Tutorial. Intro to NodeJS including installation, creating a basic http server, and fetching the current bitcoin price.

#