How to create a .conf file for your wallet? - Wallet ...

Newb Questions on running nodes...

Sort of a newbie at all this running a node and Bitcoin mining stuff.
Got a couple questions…
I’m running windows 10 pro 64 bit computer on GUI version of Bitcoin Core 0.17.0.1. Just stock settings. Got a Samsung SSD 970 PRO 1 terabyte drive as well as a standard 3 terabyte drive in my computer. Got a 150 meg connection up and down that has no monthly bandwidth cap.
  1. I’m curious about performance tuning the node; assuming you were tuning it to only run a node and nothing else. . How do you choose what settings in the gui to modify? What computer hardware has the biggest bang for the buck? How do you choose max connections, etc? Are there any sample config file settings to use for various computer profiles and internet connection speeds and monthly bandwidth caps available somewhere? How bad will running a node on my SSD be? Should I just throw the node on the HDD?
I read this about ssd drives; any truth to it still:
“Your node gets so much faster (especially if you use txindex=1) and the chainstate directory is only about 3GB, you won't regret it. Just make a symbolic link to the new directory path.
To be honest I'm not an hardware expert but if you have one lying around give it a try. Just copying the directory and creating the symbolic link took me a few minutes. My node started so much faster (30x) in checking 144 blocks.
bitcoin.conf: checklevel=3 checkblocks=144 checkblocksverify=144”
I saw this page, but it’s broken now:
https://jlopp.github.io/bitcoin-core-config-generato
https://web.archive.org/web/20180831020017/https://jlopp.github.io/bitcoin-core-config-generato
  1. Can I run multiple Bitcoin nodes on the same computer? How to install?
  2. Can I run multiple Bitcoin nodes on the same IP address? Do we need to change port settings or anything?
  3. How well does the new raspberry pi 3+ that came out this year run Bitcoin nodes? Install instructions? Are their other low cost tiny computers like that that would be preferred over the Pi?
  4. Do we have any ways of making significant money running a node yet? Any in the future planned?
  5. If block chain is downloaded on one computer & running a node, and you want to copy the block chain data & put that data on another computer to save download time can you do that? What files do you need to port over and where are they located?
  6. Are all the nodes the same for the different Bitcoin coin forks? For example Bitcoin, Bitcoin cash, Bitcoin gold, Bitcoin diamond, Bitcoin private. Would one node support all these, or does each coin require one node with different software? ? Can you run multiple nodes from same IP if they are needed? Heard something about issues running different nodes on the same computer.. Key’s getting overwritten, etc.
  7. How much upsteam & downstream data per day/month does each connection use? I know the initial chain is just under 200 gigs. With a stock setup of what 50 connections that’s what 200 gigs monthly? How much more for each extra connection you allow?
  8. What can we do with a regular node? What can we do with a lightning node? Instructions on getting the lightning part setup? What are the different types of nodes? Heard all these different terms; secure, trusted, honest, pruned, archival, SPV, validating, etc.
  9. SPV vs Validating
  10. And finally dumb question number 10. J The bitmain antminer S9… It can mine any iteration of the various bitcoins? How do you change it form Bitcoin to Bitcoin cash?
submitted by ravetildon to Bitcoin [link] [comments]

I can help you claim and sell your BTC or MONERO forked coins. Done forks of 62000 BTC+, more than 1.5 Million USD in BTC sent back to clients after the sales.

If you have Bitcoin, then you have a lot of other coins that came from the forks. I can help you claim and sell those.
Legacy addresses, Segwit addresses, multiple addresses from same seed, Ledger Nano, Trezor, Coinomi, Mycelium, whatever your wallet setup is, I can help you. If you are not tech savvy or just don't want the trouble, I can help you. If you are a whale, I can help you too: my biggest client had about 40k BTC to sell the forks.
A rough estimate is that you can get about 9% from the Bitcoin Cash fork, and about 0.8% from all the other forks. This is % of the BTC you had at the date of the fork.
Selling forked coins is a time-sensitive thing. Forked coins ALWAYS go down in price, sometimes the price drops 10 times in less than a week.
I have done it for a lot of people, check my references (comments) on these posts:
https://np.reddit.com/BitcoinAirdrops/comments/81fky0/you_are_not_tech_savvy_or_you_dont_want_to_do_it/
https://np.reddit.com/BitcoinAirdrops/comments/7rndu6/i_can_sell_your_bcx_btw_btf_or_fbtc_now_sold_fo
https://np.reddit.com/BitcoinAirdrops/comments/7ra6hx/i_can_sell_your_btw_btf_or_fbtc_now_sold_for_30/
https://np.reddit.com/CryptoCurrency/comments/7qkaio/i_can_sell_your_bitcoin_forks_btw_btf_or_fbtc_now/
https://np.reddit.com/BitcoinAirdrops/comments/7qjyiu/i_can_sell_your_btw_btf_or_fbtc_now_sold_for_30/
https://np.reddit.com/BitcoinAirdrops/comments/7qcf7z/i_can_sell_your_btw_bitcoin_world_btf_bitcoin/
https://np.reddit.com/BitcoinAirdrops/comments/7q2698/i_can_sell_your_btf_now_5_commission/
https://np.reddit.com/BitcoinMarkets/comments/7q1jyx/i_can_sell_your_btw_now_5_commission/
https://np.reddit.com/BitcoinAirdrops/comments/7pxdlm/i_can_sell_your_btw_now_5_commission/
I have created a blockchain-based feedback system for this service, check this link for details:
https://np.reddit.com/BitcoinAirdrops/comments/8f489a/cryptosnake_fork_claim_and_sell_service/
Some coins now are worth a really small amount, specially if you only had little btc before the fork. Talk to me (PM) and we will see if it's worth selling (sometimes it's not enough to sell and withdraw from the exchange, but I can sometimes consolidate a few sales and do individual withdrawals from my wallet, with lower fees).
The fee for sale at exchanges I'm KYC'd and verified is 5%, and the fee for claiming the fork coins and selling is 10%.
Sample report sent during and on completion: https://imgur.com/a/e53ObT3
If it's worth the work, I'll claim/sell them for you, and if not, I'll point you in the right direction.
There's an absurd amount of forks now (forkdrop.io is a good site to check forks), but it seems that I can help you with these:
CLAM - CLAMS
BCH - Bitcoin Cash
BTG - Bitcoin Gold
BTX - BitCore
UBTC - United Bitcoin (Developers stole the users coins. If you have it, I can sell. Check ub.com/explorer)
BCD - Bitcoin Diamond
SBTC - Super Bitcoin
BCX - BitcoinX
BICC - BitClassic Coin (deposits not working anymore on the exchange)
BTP - Bitcoin Pay
BTW - Bitcoin World (Dead, network hashrate has come down to less than 1 block per day, and only exchange needs 120 confs)
LBTC - Lightning Bitcoin
BTF - Bitcoin Faith (Dead, network down, no more wallet on github)
BITE - BitEthereum
BTN - Bitcoin New (Dead. after coin hardforked, can only be sold at a korean exchange for 0.0000476 BTC each. As it is a 1:1 coin, I will not claim and sell it anymore)
FBTC - FastBitcoin
BCP - Bitcoin Cash Plus
B2X - Segwit2X
BPA - Bitcoin Pizza (dead, no more nodes running)
BTV - BitVote
BCI - Bitcoin Interest
BCA - Bitcoin Atom
BTCH - Bitcoin Hush
BTCP - Bitcoin Private
BCL - Bitcoin Clean
BBC - Big Bitcoin
GOD - Bitcoin God (not sellable yet)
BIFI - Bitcoin File
SEM - SEMUX (It was a registered airdrop, whoever got it, got it. I can sell it if you have it.)
XMC - Monero Classic
XMV - Monero V
Just PM me and we will talk. Cheers.
P.S: Please check my references (cryptosnake). This is a matter that involves trust, and you need to trust whoever you do business with. About my name, CryptoSnake, the "Snake" part is not an analogy or whatever. It was just a school nickname. :)
submitted by cryptosnake to BitcoinAirdrops [link] [comments]

[BUILD] COSMiC: Community Open-Source Miner including CUDA v2.10.0-pre5 + HashBurner V1 (ongoing)

Hello 0xBitcoin Community! I'm excited to share my work with you today.
NOTE: THESE VERSIONS ARE OUTDATED! Get the latest here: https://bitbucket.org/LieutenantTofu/cosmic-v3/downloads/
v3.4 is the thoroughly tested Stable Version. v3.5 is experimental at the time of this writing. Thanks!
COSMiC v3.4 for Windows thread: https://www.reddit.com/0xbitcoin/comments/8ewvo9/miner_cosmic_v34t_cuda_miner_for_windows_64_linux
And for Linux: https://www.reddit.com/0xbitcoin/comments/8g92v4/build_cosmic_v34t_for_linux_with_autostart/
(Post remains for archival purposes: )
This is the first in a series of builds I will be posting here and on the Discord server that incorporate the latest updates to the various forks of the community open-source CUDA miner, plus my own optimizations and improvements (nickname: Hashburner builds). In addition to being as fast as possible, I'm trying to make these as reliable and user-friendly as possible, with quality documentation.
I am posting two archives of V1 today. The first is just the binaries(executables) for Windows X64, Mac OS X and Linux. I have only tested the Windows version- so please let me know your results! The second has the binaries, source code, a handy batch file and all the node modules you (should) need to make any changes you'd like and recompile. Both versions also have a 0xBTC.conf sample file I set up for my GTX1060-3GB as Device #0. Feel free to edit it or remove for the hardcoded intensity of 27. Same format as in Azlehria's builds, see Readme.txt.
Binaries Only (open with 7zip or similar): https://drive.google.com/open?id=1zL-hpiyxP2kwU3wIuQz6SDCPWFar-V76
Development Version (with binaries, source, node-modules, etc): https://drive.google.com/open?id=1R0A3hqIjDUp9J1JQLpetIgdtMHDd_Hmd (See the Readme.txt for details on how to build from source.)

Partial Changelog (See Readme.txt):

Please let me know your results along with your hardware configuration so that I can customize the next builds for as wide a range of hardware as possible! On my Pascal card (GTX1060-3GB w/ +122 MHz Core, -150 MHz VRAM), I am getting ~515 MH/s with this build.
Enjoy and Happy Hashing! - Lt. Tofu a.k.a. Mag517
p.s. How do you like the nickname for our community miner? Also, expect HB V1.1 in the next day or two.
submitted by LieutenantTofu to 0xbitcoin [link] [comments]

I can help you claim and sell your BTC forked coins. Done forks of 62000 BTC+, more than 1.5 Million USD in BTC sent back to clients after the sales. PRICES GOING DOWN, DO NOT WAIT.

If you have Bitcoin, then you have a lot of other coins that came from the forks. I can help you claim and sell those.
Legacy addresses, Segwit addresses, multiple addresses from same seed, Ledger Nano, Trezor, Coinomi, Mycelium, whatever your wallet setup is, I can help you. If you are not tech savvy or just don't want the trouble, I can help you. If you are a whale, I can help you too: my biggest client had about 40k BTC to sell the forks.
A rough estimate is that you can get about 9% from the Bitcoin Cash fork, and about 0.5% from all the other forks. This is % of the BTC you had at the date of the fork.
DO NOT WAIT. Check below the list of dead coins. Everyday one of these dies, and some of these dead coins gave a LOT of money back to my clients.
Selling forked coins is a time-sensitive thing. Forked coins ALWAYS go down in price, sometimes the price drops 10 times in less than a week.
I have done it for a lot of people, check my references (comments) on these posts:
https://np.reddit.com/BitcoinAirdrops/comments/81fky0/you_are_not_tech_savvy_or_you_dont_want_to_do_it/
https://np.reddit.com/BitcoinAirdrops/comments/7rndu6/i_can_sell_your_bcx_btw_btf_or_fbtc_now_sold_fo
https://np.reddit.com/BitcoinAirdrops/comments/7ra6hx/i_can_sell_your_btw_btf_or_fbtc_now_sold_for_30/
https://np.reddit.com/CryptoCurrency/comments/7qkaio/i_can_sell_your_bitcoin_forks_btw_btf_or_fbtc_now/
https://np.reddit.com/BitcoinAirdrops/comments/7qjyiu/i_can_sell_your_btw_btf_or_fbtc_now_sold_for_30/
https://np.reddit.com/BitcoinAirdrops/comments/7qcf7z/i_can_sell_your_btw_bitcoin_world_btf_bitcoin/
https://np.reddit.com/BitcoinAirdrops/comments/7q2698/i_can_sell_your_btf_now_5_commission/
https://np.reddit.com/BitcoinMarkets/comments/7q1jyx/i_can_sell_your_btw_now_5_commission/
https://np.reddit.com/BitcoinAirdrops/comments/7pxdlm/i_can_sell_your_btw_now_5_commission/
I have created a blockchain-based feedback system for this service, check this link for details:
https://np.reddit.com/BitcoinAirdrops/comments/8f489a/cryptosnake_fork_claim_and_sell_service/
Some coins now are worth a really small amount, specially if you only had little btc before the fork. Talk to me (PM) and we will see if it's worth selling (sometimes it's not enough to sell and withdraw from the exchange, but I can sometimes consolidate a few sales and do individual withdrawals from my wallet, with lower fees).
It's good to say that its becoming harder and harder to sell and withdraw "small" amounts of BTC (like 200, 300), because of the price drops and withdrawal fees on the exchanges. Sometime I can get together groups of people and do a group claim, but these are becoming scarce as well. I'll try though.
The fee for sale at exchanges I'm KYC'd and verified is 5%, and the fee for claiming the fork coins and selling is 10%.
Sample report sent during and on completion: https://imgur.com/a/e53ObT3
If it's worth the work, I'll claim/sell them for you, and if not, I'll point you in the right direction.
There's an absurd amount of forks now (forkdrop.io is a good site to check forks), but it seems that I can help you with these:
CLAM - CLAMS
BCH - Bitcoin Cash
BTG - Bitcoin Gold
BTX - BitCore
BCD - Bitcoin Diamond
BCX - BitcoinX
B2X - Segwit2X (its been difficult to sell small batches, now needs hundreds to be sellable)
BCI - Bitcoin Interest
BCA - Bitcoin Atom
BTCP - Bitcoin Private (Unclaimed coins were burnt)
GOD - Bitcoin God (No exchanges/buy orders yet... oh god, when will this happen? haha)
BIFI - Bitcoin File (No more deposits)
SEM - SEMUX (It was a registered airdrop, whoever got it, got it. I can sell it if you have it.)
XMC - Monero Classic
XMV - Monero V
UBTC - United Bitcoin (Developers stole the users coins. If you have it, I can sell. Check ub.com/explorer)
SBTC - Super Bitcoin (Deposits offline on all exchanges, pending something on the network. May come back)
BICC - BitClassic Coin (deposits not working anymore on the exchange)
BTP - Bitcoin Pay (Deposits offline on all exchanges)
BTW - Bitcoin World (Dead, network hashrate has come down to less than 1 block per day, and only exchange needs 120 confs)
LBTC - Lightning Bitcoin (Coins not claimable anymore as per network consensus of the new coin)
BTF - Bitcoin Faith (Dead, network down, no more wallet on github)
BITE - BitEthereum (blah)
BTN - Bitcoin New (Dead. after coin hardforked, can only be sold at a korean exchange for 0.0000476 BTC each. As it is a 1:1 coin, I will not claim and sell it anymore)
FBTC - FastBitcoin (not worth doing anymore, too much trouble for only a little cash)
BCP - Bitcoin Cash Plus (never sold this, dunno if its dead)
BPA - Bitcoin Pizza (dead, no more nodes running)
BTV - BitVote (its been difficult to sell small batches, now needs hundreds to be sellable)
BTCH - Bitcoin Hush (never sold this, dunno if its dead)
BCL - Bitcoin Clean (seems dead as deposits are halted, reason "hacker" on yobit)
BBC - Big Bitcoin (Only shady exchange, worth 0.30 USD for each bitcoin (0.03/BBC)
Just PM me and we will talk. Cheers.
P.S: Please check my references (cryptosnake). This is a matter that involves trust, and you need to trust whoever you do business with. About my name, CryptoSnake, the "Snake" part is not an analogy or whatever. It was just a school nickname. :)
submitted by cryptosnake to BitcoinAirdrops [link] [comments]

I can help you claim and sell your BTC or MONERO forked coins. Done forks of 62000 BTC+, more than 1.5 Million USD in BTC sent back to clients after the sales.

If you have Bitcoin, then you have a lot of other coins that came from the forks. I can help you claim and sell those.
Legacy addresses, Segwit addresses, multiple addresses from same seed, Ledger Nano, Trezor, Coinomi, Mycelium, whatever your wallet setup is, I can help you. If you are not tech savvy or just don't want the trouble, I can help you. If you are a whale, I can help you too: my biggest client had about 40k BTC to sell the forks.
A rough estimate is that you can get about 9% to 14% from the Bitcoin Cash fork, and about 1.4% from all the other forks. This is % of the BTC you had at the date of the fork.
I have done it for a lot of people, check my references (comments) on these posts:
https://np.reddit.com/BitcoinAirdrops/comments/81fky0/you_are_not_tech_savvy_or_you_dont_want_to_do_it/
https://np.reddit.com/BitcoinAirdrops/comments/7rndu6/i_can_sell_your_bcx_btw_btf_or_fbtc_now_sold_fo
https://np.reddit.com/BitcoinAirdrops/comments/7ra6hx/i_can_sell_your_btw_btf_or_fbtc_now_sold_for_30/
https://np.reddit.com/CryptoCurrency/comments/7qkaio/i_can_sell_your_bitcoin_forks_btw_btf_or_fbtc_now/
https://np.reddit.com/BitcoinAirdrops/comments/7qjyiu/i_can_sell_your_btw_btf_or_fbtc_now_sold_for_30/
https://np.reddit.com/BitcoinAirdrops/comments/7qcf7z/i_can_sell_your_btw_bitcoin_world_btf_bitcoin/
https://np.reddit.com/BitcoinAirdrops/comments/7q2698/i_can_sell_your_btf_now_5_commission/
https://np.reddit.com/BitcoinMarkets/comments/7q1jyx/i_can_sell_your_btw_now_5_commission/
https://np.reddit.com/BitcoinAirdrops/comments/7pxdlm/i_can_sell_your_btw_now_5_commission/
I have created a blockchain-based feedback system for this service, check this link for details:
https://np.reddit.com/BitcoinAirdrops/comments/8f489a/cryptosnake_fork_claim_and_sell_service/
Some coins now are worth a really small amount, specially if you only had little btc before the fork. Talk to me (PM) and we will see if it's worth selling (sometimes it's not enough to sell and withdraw from the exchange, but I can sometimes consolidate a few sales and do individual withdrawals from my wallet, with lower fees). We will agree on a fee/commission, usually between 5 and 10%.
Sample report sent during and on completion: https://imgur.com/a/e53ObT3
If it's worth the work, I'll claim/sell them for you, and if not, I'll point you in the right direction.
There's an absurd amount of forks now (forkdrop.io is a good site to check forks), but it seems that I can help you with these:
CLAM - CLAMS
BCH - Bitcoin Cash
BTG - Bitcoin Gold
BTX - BitCore
UBTC - United Bitcoin (Developers stole the users coins. If you have it, I can sell. Check ub.com/explorer)
BCD - Bitcoin Diamond
SBTC - Super Bitcoin
BCX - BitcoinX
BICC - BitClassic Coin (deposits not working anymore on the exchange)
BTP - Bitcoin Pay
BTW - Bitcoin World (Dead, network hashrate has come down to less than 1 block per day, and only exchange needs 120 confs)
LBTC - Lightning Bitcoin
BTF - Bitcoin Faith (Dead, network down, no more wallet on github)
BITE - BitEthereum
BTN - Bitcoin New (Dead. after coin hardforked, can only be sold at a korean exchange for 0.0000476 BTC each. As it is a 1:1 coin, I will not claim and sell it anymore)
FBTC - FastBitcoin
BCP - Bitcoin Cash Plus
B2X - Segwit2X
BPA - Bitcoin Pizza (dead, no more nodes running)
BTV - BitVote
BCI - Bitcoin Interest
BCA - Bitcoin Atom
BTCH - Bitcoin Hush
BTCP - Bitcoin Private
BCL - Bitcoin Clean
BBC - Big Bitcoin
GOD - Bitcoin God (not sellable yet)
BIFI - Bitcoin File
SEM - SEMUX (It was a registered airdrop, whoever got it, got it. I can sell it if you have it.)
XMC - Monero Classic
XMV - Monero V
Just PM me and we will talk. Cheers.
P.S: Please check my references (cryptosnake). This is a matter that involves trust, and you need to trust whoever you do business with. About my name, CryptoSnake, the "Snake" part is not an analogy or whatever. It was just a school nickname. :)
submitted by cryptosnake to BitcoinAirdrops [link] [comments]

I can help you claim and sell your BTC forked coins. Done forks of 62000 BTC+, more than 1.5 Million USD in BTC sent back to clients after the sales. DO NOT WAIT.

If you have Bitcoin, then you have a lot of other coins that came from the forks. I can help you claim and sell those.
Legacy addresses, Segwit addresses, multiple addresses from same seed, Ledger Nano, Trezor, Coinomi, Mycelium, whatever your wallet setup is, I can help you. If you are not tech savvy or just don't want the trouble, I can help you. If you are a whale, I can help you too: my biggest client had about 40k BTC to sell the forks.
A rough estimate is that you can get about 9% from the Bitcoin Cash fork, and about 0.5% from all the other forks. This is % of the BTC you had at the date of the fork.
DO NOT WAIT. Check below the list of dead coins. Everyday one of these dies, and some of these dead coins gave a LOT of money back to my clients.
Selling forked coins is a time-sensitive thing. Forked coins ALWAYS go down in price, sometimes the price drops 10 times in less than a week.
I have done it for a lot of people, check my references (comments) on these posts:
https://np.reddit.com/BitcoinAirdrops/comments/81fky0/you_are_not_tech_savvy_or_you_dont_want_to_do_it/
https://np.reddit.com/BitcoinAirdrops/comments/7rndu6/i_can_sell_your_bcx_btw_btf_or_fbtc_now_sold_fo
https://np.reddit.com/BitcoinAirdrops/comments/7ra6hx/i_can_sell_your_btw_btf_or_fbtc_now_sold_for_30/
https://np.reddit.com/CryptoCurrency/comments/7qkaio/i_can_sell_your_bitcoin_forks_btw_btf_or_fbtc_now/
https://np.reddit.com/BitcoinAirdrops/comments/7qjyiu/i_can_sell_your_btw_btf_or_fbtc_now_sold_for_30/
https://np.reddit.com/BitcoinAirdrops/comments/7qcf7z/i_can_sell_your_btw_bitcoin_world_btf_bitcoin/
https://np.reddit.com/BitcoinAirdrops/comments/7q2698/i_can_sell_your_btf_now_5_commission/
https://np.reddit.com/BitcoinMarkets/comments/7q1jyx/i_can_sell_your_btw_now_5_commission/
https://np.reddit.com/BitcoinAirdrops/comments/7pxdlm/i_can_sell_your_btw_now_5_commission/
I have created a blockchain-based feedback system for this service, check this link for details:
https://np.reddit.com/BitcoinAirdrops/comments/8f489a/cryptosnake_fork_claim_and_sell_service/
Some coins now are worth a really small amount, specially if you only had little btc before the fork. Talk to me (PM) and we will see if it's worth selling (sometimes it's not enough to sell and withdraw from the exchange, but I can sometimes consolidate a few sales and do individual withdrawals from my wallet, with lower fees).
It's good to say that its becoming harder and harder to sell and withdraw "small" amounts of BTC (like 200, 300), because of the price drops and withdrawal fees on the exchanges. Sometime I can get together groups of people and do a group claim, but these are becoming scarce as well. I'll try though.
The fee for sale at exchanges I'm KYC'd and verified is 5%, and the fee for claiming the fork coins and selling is 10%.
Sample report sent during and on completion: https://imgur.com/a/e53ObT3
If it's worth the work, I'll claim/sell them for you, and if not, I'll point you in the right direction.
There's an absurd amount of forks now (forkdrop.io is a good site to check forks), but it seems that I can help you with these:
CLAM - CLAMS
BCH - Bitcoin Cash
BTG - Bitcoin Gold
BTX - BitCore
BCD - Bitcoin Diamond
BCX - BitcoinX
B2X - Segwit2X (its been difficult to sell small batches, now needs hundreds to be sellable)
BCI - Bitcoin Interest
BCA - Bitcoin Atom
BTCP - Bitcoin Private
GOD - Bitcoin God (No exchanges/buy orders yet... oh god, when will this happen? haha)
BIFI - Bitcoin File
SEM - SEMUX (It was a registered airdrop, whoever got it, got it. I can sell it if you have it.)
XMC - Monero Classic
XMV - Monero V
UBTC - United Bitcoin (Developers stole the users coins. If you have it, I can sell. Check ub.com/explorer)
SBTC - Super Bitcoin (Deposits offline on all exchanges, pending something on the network. May come back)
BICC - BitClassic Coin (deposits not working anymore on the exchange)
BTP - Bitcoin Pay (Deposits offline on all exchanges)
BTW - Bitcoin World (Dead, network hashrate has come down to less than 1 block per day, and only exchange needs 120 confs)
LBTC - Lightning Bitcoin (Coins not claimable anymore as per network consensus of the new coin)
BTF - Bitcoin Faith (Dead, network down, no more wallet on github)
BITE - BitEthereum (blah)
BTN - Bitcoin New (Dead. after coin hardforked, can only be sold at a korean exchange for 0.0000476 BTC each. As it is a 1:1 coin, I will not claim and sell it anymore)
FBTC - FastBitcoin (not worth doing anymore, too much trouble for only a little cash)
BCP - Bitcoin Cash Plus (never sold this, dunno if its dead)
BPA - Bitcoin Pizza (dead, no more nodes running)
BTV - BitVote (its been difficult to sell small batches, now needs hundreds to be sellable)
BTCH - Bitcoin Hush (never sold this, dunno if its dead)
BCL - Bitcoin Clean (seems dead as deposits are halted, reason "hacker" on yobit)
BBC - Big Bitcoin (Only shady exchange, worth 0.30 USD for each bitcoin (0.03/BBC)
Just PM me and we will talk. Cheers.
P.S: Please check my references (cryptosnake). This is a matter that involves trust, and you need to trust whoever you do business with. About my name, CryptoSnake, the "Snake" part is not an analogy or whatever. It was just a school nickname. :)
submitted by cryptosnake to BitcoinAirdrops [link] [comments]

Bitcoind over tor. A miniguide from personal experience (I'm not an expert)

The problem

Light SPV clients are today the best solution to use bitcoin on a mobile without leaving your secret key in the hands of a company but:

Mitigation

1) With many SPV light clients today you can connect to nodes you choose and they can so be either trusted or even controlled by you (es: one node at home and one node at the office)
2) If this connection is over Tor you can avoid being eavesdropped by someone being it a criminal or a malicious or censoring third part
3) Your transactions are not linked to a given or known IP address

The setup

1) Download and synchronize the blockchain with your node
mv BitcoinDatadipeers.dat /tmp 
this will move the file peers.dat to /tmp (which is better for your privacy).
2) From your tor setup directory
cp torrc.sample torrc tor --hash-password "" ->  
to set up a control port and a password for an external application in our case is bitcoin
https://stem.torproject.org/tutorials/the_little_relay_that_could.html
3) add these lines to your torrc file

torrc

ControlPort 9051 CookieAuthentication 1 HashedControlPassword  
add these lines to your bitcoin.conf file

bitcoin.conf

 proxy=127.0.0.1:9050 listen=1 onlynet=onion listenonion=1 discover=0 torcontrol=127.0.0.1:9051 torpassword= 
4) start tor
tor 
5) start bitcoind
bitcoind -daemon 
On your mobile setup your SPV client to run on Tor.
Greenbits works well with Orbot.
Tell your client to connect via SPV to your new onion address.
Bonus: you don't need to open any port on your router at home or at the office.
This is a mini straight forward guide by a non expert.
I encourage you to study the documentation at
https://www.torproject.org/docs/documentation.html.en
as well as:
https://github.com/bitcoin/bitcoin/blob/mastedoc/tor.md
submitted by gabridome to Bitcoin [link] [comments]

I can help you claim and sell your BTC forked coins. Done forks of 62000 BTC+, more than 1.5 Million USD in BTC sent back to clients after the sales. PRICES GOING DOWN, DO NOT WAIT.

If you have Bitcoin, then you have a lot of other coins that came from the forks. I can help you claim and sell those.
Legacy addresses, Segwit addresses, multiple addresses from same seed, Ledger Nano, Trezor, Coinomi, Mycelium, whatever your wallet setup is, I can help you. If you are not tech savvy or just don't want the trouble, I can help you. If you are a whale, I can help you too: my biggest client had about 40k BTC to sell the forks.
A rough estimate is that you can get about 9% from the Bitcoin Cash fork, and about 0.5% from all the other forks. This is % of the BTC you had at the date of the fork.
DO NOT WAIT. Check below the list of dead coins. Everyday one of these dies, and some of these dead coins gave a LOT of money back to my clients.
Selling forked coins is a time-sensitive thing. Forked coins ALWAYS go down in price, sometimes the price drops 10 times in less than a week.
I have done it for a lot of people, check my references (comments) on these posts:
https://np.reddit.com/BitcoinAirdrops/comments/81fky0/you_are_not_tech_savvy_or_you_dont_want_to_do_it/
https://np.reddit.com/BitcoinAirdrops/comments/7rndu6/i_can_sell_your_bcx_btw_btf_or_fbtc_now_sold_fo
https://np.reddit.com/BitcoinAirdrops/comments/7ra6hx/i_can_sell_your_btw_btf_or_fbtc_now_sold_for_30/
https://np.reddit.com/CryptoCurrency/comments/7qkaio/i_can_sell_your_bitcoin_forks_btw_btf_or_fbtc_now/
https://np.reddit.com/BitcoinAirdrops/comments/7qjyiu/i_can_sell_your_btw_btf_or_fbtc_now_sold_for_30/
https://np.reddit.com/BitcoinAirdrops/comments/7qcf7z/i_can_sell_your_btw_bitcoin_world_btf_bitcoin/
https://np.reddit.com/BitcoinAirdrops/comments/7q2698/i_can_sell_your_btf_now_5_commission/
https://np.reddit.com/BitcoinMarkets/comments/7q1jyx/i_can_sell_your_btw_now_5_commission/
https://np.reddit.com/BitcoinAirdrops/comments/7pxdlm/i_can_sell_your_btw_now_5_commission/
I have created a blockchain-based feedback system for this service, check this link for details:
https://np.reddit.com/BitcoinAirdrops/comments/8f489a/cryptosnake_fork_claim_and_sell_service/
Some coins now are worth a really small amount, specially if you only had little btc before the fork. Talk to me (PM) and we will see if it's worth selling (sometimes it's not enough to sell and withdraw from the exchange, but I can sometimes consolidate a few sales and do individual withdrawals from my wallet, with lower fees).
It's good to say that its becoming harder and harder to sell and withdraw "small" amounts of BTC (like 200, 300), because of the price drops and withdrawal fees on the exchanges. Sometime I can get together groups of people and do a group claim, but these are becoming scarce as well. I'll try though.
The fee for sale at exchanges I'm KYC'd and verified is 5%, and the fee for claiming the fork coins and selling is 10%.
Sample report sent during and on completion: https://imgur.com/a/e53ObT3
If it's worth the work, I'll claim/sell them for you, and if not, I'll point you in the right direction.
There's an absurd amount of forks now (forkdrop.io is a good site to check forks), but it seems that I can help you with these:
CLAM - CLAMS
BCH - Bitcoin Cash
BTG - Bitcoin Gold
BTX - BitCore
BCD - Bitcoin Diamond
BCX - BitcoinX
B2X - Segwit2X (its been difficult to sell small batches, now needs hundreds to be sellable)
BCI - Bitcoin Interest
BCA - Bitcoin Atom
BTCP - Bitcoin Private
GOD - Bitcoin God (No exchanges/buy orders yet... oh god, when will this happen? haha)
BIFI - Bitcoin File
SEM - SEMUX (It was a registered airdrop, whoever got it, got it. I can sell it if you have it.)
XMC - Monero Classic
XMV - Monero V
UBTC - United Bitcoin (Developers stole the users coins. If you have it, I can sell. Check ub.com/explorer)
SBTC - Super Bitcoin (Deposits offline on all exchanges, pending something on the network. May come back)
BICC - BitClassic Coin (deposits not working anymore on the exchange)
BTP - Bitcoin Pay (Deposits offline on all exchanges)
BTW - Bitcoin World (Dead, network hashrate has come down to less than 1 block per day, and only exchange needs 120 confs)
LBTC - Lightning Bitcoin (Coins not claimable anymore as per network consensus of the new coin)
BTF - Bitcoin Faith (Dead, network down, no more wallet on github)
BITE - BitEthereum (blah)
BTN - Bitcoin New (Dead. after coin hardforked, can only be sold at a korean exchange for 0.0000476 BTC each. As it is a 1:1 coin, I will not claim and sell it anymore)
FBTC - FastBitcoin (not worth doing anymore, too much trouble for only a little cash)
BCP - Bitcoin Cash Plus (never sold this, dunno if its dead)
BPA - Bitcoin Pizza (dead, no more nodes running)
BTV - BitVote (its been difficult to sell small batches, now needs hundreds to be sellable)
BTCH - Bitcoin Hush (never sold this, dunno if its dead)
BCL - Bitcoin Clean (seems dead as deposits are halted, reason "hacker" on yobit)
BBC - Big Bitcoin (Only shady exchange, worth 0.30 USD for each bitcoin (0.03/BBC)
Just PM me and we will talk. Cheers.
P.S: Please check my references (cryptosnake). This is a matter that involves trust, and you need to trust whoever you do business with. About my name, CryptoSnake, the "Snake" part is not an analogy or whatever. It was just a school nickname. :)
submitted by cryptosnake to BitcoinAirdrops [link] [comments]

I can help you claim and sell your BTC or MONERO forked coins. Done forks of 62000 BTC+, more than 1.5 Million USD in BTC sent back to clients after the sales.

If you have Bitcoin, then you have a lot of other coins that came from the forks. I can help you claim and sell those.
Legacy addresses, Segwit addresses, multiple addresses from same seed, Ledger Nano, Trezor, Coinomi, Mycelium, whatever your wallet setup is, I can help you. If you are not tech savvy or just don't want the trouble, I can help you. If you are a whale, I can help you too: my biggest client had about 40k BTC to sell the forks.
A rough estimate is that you can get about 9% from the Bitcoin Cash fork, and about 0.8% from all the other forks. This is % of the BTC you had at the date of the fork.
Selling forked coins is a time-sensitive thing. Forked coins ALWAYS go down in price, sometimes the price drops 10 times in less than a week.
I have done it for a lot of people, check my references (comments) on these posts:
https://np.reddit.com/BitcoinAirdrops/comments/81fky0/you_are_not_tech_savvy_or_you_dont_want_to_do_it/
https://np.reddit.com/BitcoinAirdrops/comments/7rndu6/i_can_sell_your_bcx_btw_btf_or_fbtc_now_sold_fo
https://np.reddit.com/BitcoinAirdrops/comments/7ra6hx/i_can_sell_your_btw_btf_or_fbtc_now_sold_for_30/
https://np.reddit.com/CryptoCurrency/comments/7qkaio/i_can_sell_your_bitcoin_forks_btw_btf_or_fbtc_now/
https://np.reddit.com/BitcoinAirdrops/comments/7qjyiu/i_can_sell_your_btw_btf_or_fbtc_now_sold_for_30/
https://np.reddit.com/BitcoinAirdrops/comments/7qcf7z/i_can_sell_your_btw_bitcoin_world_btf_bitcoin/
https://np.reddit.com/BitcoinAirdrops/comments/7q2698/i_can_sell_your_btf_now_5_commission/
https://np.reddit.com/BitcoinMarkets/comments/7q1jyx/i_can_sell_your_btw_now_5_commission/
https://np.reddit.com/BitcoinAirdrops/comments/7pxdlm/i_can_sell_your_btw_now_5_commission/
I have created a blockchain-based feedback system for this service, check this link for details:
https://np.reddit.com/BitcoinAirdrops/comments/8f489a/cryptosnake_fork_claim_and_sell_service/
Some coins now are worth a really small amount, specially if you only had little btc before the fork. Talk to me (PM) and we will see if it's worth selling (sometimes it's not enough to sell and withdraw from the exchange, but I can sometimes consolidate a few sales and do individual withdrawals from my wallet, with lower fees).
The fee for sale at exchanges I'm KYC'd and verified is 5%, and the fee for claiming the fork coins and selling is 10%.
Sample report sent during and on completion: https://imgur.com/a/e53ObT3
If it's worth the work, I'll claim/sell them for you, and if not, I'll point you in the right direction.
There's an absurd amount of forks now (forkdrop.io is a good site to check forks), but it seems that I can help you with these:
CLAM - CLAMS
BCH - Bitcoin Cash
BTG - Bitcoin Gold
BTX - BitCore
UBTC - United Bitcoin (Developers stole the users coins. If you have it, I can sell. Check ub.com/explorer)
BCD - Bitcoin Diamond
SBTC - Super Bitcoin
BCX - BitcoinX
BICC - BitClassic Coin (deposits not working anymore on the exchange)
BTP - Bitcoin Pay
BTW - Bitcoin World (Dead, network hashrate has come down to less than 1 block per day, and only exchange needs 120 confs)
LBTC - Lightning Bitcoin
BTF - Bitcoin Faith (Dead, network down, no more wallet on github)
BITE - BitEthereum
BTN - Bitcoin New (Dead. after coin hardforked, can only be sold at a korean exchange for 0.0000476 BTC each. As it is a 1:1 coin, I will not claim and sell it anymore)
FBTC - FastBitcoin (not worth doing anymore, too much trouble for only a little cash)
BCP - Bitcoin Cash Plus
B2X - Segwit2X (its been difficult to sell small batches, now needs hundreds to be sellable)
BPA - Bitcoin Pizza (dead, no more nodes running)
BTV - BitVote (its been difficult to sell small batches, now needs hundreds to be sellable)
BCI - Bitcoin Interest (coin is undergoing a fork that will happen soon, deposits at exchanges halted, but will be sellable after that)
BCA - Bitcoin Atom
BTCH - Bitcoin Hush
BTCP - Bitcoin Private
BCL - Bitcoin Clean
BBC - Big Bitcoin
GOD - Bitcoin God (not sellable yet)
BIFI - Bitcoin File
SEM - SEMUX (It was a registered airdrop, whoever got it, got it. I can sell it if you have it.)
XMC - Monero Classic
XMV - Monero V
Just PM me and we will talk. Cheers.
P.S: Please check my references (cryptosnake). This is a matter that involves trust, and you need to trust whoever you do business with. About my name, CryptoSnake, the "Snake" part is not an analogy or whatever. It was just a school nickname. :)
submitted by cryptosnake to BitcoinAirdrops [link] [comments]

Zeus/Gaw ASIC Setup Guide for Linux/Raspberry Pi

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

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

Resources

About Cyrptocurrencies and Their Jargon

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

Linux

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

Computer Setup

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

Desktop/Laptop

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

Raspberry Pi

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

Miner Setup

Installing BFGMiner

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

Running BFGMiner

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

Start on Boot

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

Power Failure

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

Sources

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

Wrap Up

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

Some ideas for richer configuration options for tor

The problem

Between moving coins to segwit addresses, splitting BCH/BTC, and looking forward to splitting S2X and BTC in November to sell our Jeffcoins for a tidy dividend to mitigate the plummeting value of our holdings due to a botched hard fork without consensus or proper replay protection.......
I have been thinking about transaction privacy again, and am not happy with the tor options that the Bitcoin Core node provides. I don't like running my node on tor, because I don't like the idea of burdening exit nodes' bandwidth pointlessly with yet another copy of the blockchain. On the other hand, I don't like running my node without tor because I don't want my transactions to be linked to my IP.
I know, I know, I know, you get protection by virtue of the gossip network. This protection has never felt quantifiably robust to me, considering how many spy nodes there are (how many?) and considering that when splitting coins you originate the broadcast of spends on the same coins TWICE from your IP address.

Here are some modes I think would be helpful:

  1. Broadcast transactions over [ tor | clearnet | disabled ]
  2. Receive and/or send block [ headers | header-hashes ] over [ tor | clearnet ]
  3. Receive and/or send full blocks over [ tor | clearnet | disabled ]
  4. Receive and/or send unconfirmed transactions over [ tor | clearnet | disabled ]

Sample scenarios:

  1. Do everything over clearnet except broadcasting transactions, which is through tor (and Dandelion when it gets deployed.)
  2. No communication over internet except to broadcast transactions via tor and receive block header hashes from random peers over clearnet. Satellite is used to obtain everything else.

Making do with what we've got:

With the current node software, if you want to use tor for broadcast and clearnet for everything else, here is an idea. Make 2 different bitcoin.conf files. In one, set up your node to talk to the network normally (or to connect only to an always-on sentry node you control so you don't leave tell tails by popping in and out of the network) and set -walletbroadcast=0 so that you cannot broadcast transactions. In the other bitcoin.conf file, you set up your node to use tor, and you only run this config when you are going to do a broadcast.
Alternatively you could use Wladimir's submittx script
submitted by moral_agent to Bitcoin [link] [comments]

I have a beagleboard that came as part of a bitcoin mining appliance and I broke linux. Offering a reward for the solution.

THIS PROBLEM HAS BEEN SOLVED.
I received a brand new KnC Saturn bitcoin miner TODAY. I promptly logged into ssh to configure the miner and made a mistake that has caused the appliance not to boot.
I am willing to offer $200 in reward, by paypal or bitcoin to the person or persons who helps me get this miner working. If it starts working, I will award the entire sum to those who helped in a sum divisible at my discretion.
This is the KncMiner Saturn, the miner I received today.
Here is a picture of the the controller board
This is the front of the beaglebone attched to the controller
Here is a picture of the back of the beaglebone
I have no experience with beagle boards, though I am comfortable with Raspberry Pi's, and pretty comfortable with linux (though I'm questioning that considering my current predicament).
Here's a synopsis:
The beagleboard runs a custom linux firmware developed by KnCminer with a bitcoin mining program called cgminer. The interface is accessible primarily from a web interface, secondarily by ssh.
I am nearly certain that the only problem is that I removed a file that the board is searching for on boot. There is a directory called /config/ that directory contains mining configuration files.
I issued
mv /config/cgminer.conf.factory /config/cgminer.conf 
which effectively deleted /config/cgminer.conf.factory. This has rendered they system only partially bootable. The system lights up and it responds to ping, but I cannot access the system by ssh or by the web interface.
I believe that all I need to do is to get into the beaglebone and cp the cgminer.conf file back to cgminer.conf.factory in order to enable regular boot.
In addition, I may have exacerbated the problem by attempting a hardware reset described on page 5 of this manual.
The company, KncMiner, does offer a support page with clean firmwares, but I don't know how to apply any of these to a non-working system.
I am more than willing to answer any questions. As I stated, I will award $200 in bitcoin or paypal to the person or persons who helps me get this miner working. The payout will only occur if this thread results in a solution. I will award the entire prize at my discretion to those who help at a ratio of my determination.
UPDATE 6:30am 10/22/2013: I glad to see bonez656 post that this is happening to someone else. I am currently trying to acquire a complete dd image of the saturn/jupiter so I can reflash my beaglebone. If this works, I plan to offer 1/2 of the reward to bonez656 and the other half to whoever provides the dd image.
UPDATE 7am 10/22/2013: I received support from Emilia at KnC that may make a flash unncessary. The miner has an Emergency State that may allow me to access SSH and restore the bad file. I will attempt this first and follow up around 5pm EST with details.
UPDATE 4pm 10/23/2013: The miner is up and running! I'll be providing 0.25 BTC to bonez656 for providing comments that got me closest to the solution.
The solution actually came from KnC miner support:
  1. Shut down the power;
  2. Disconnect 12V power cables from all the ASIC boards;
  3. Turn the power on.
  4. The miner will start, and red LED will light up eventually - it is in errored state "No ASIC board found"
  5. SSH into the miner, restore factory configuration files (sample network.conf.factory and cgminer.conf.factory attached)
  6. sync (issue sync command in the command line interface)
  7. Turn the power off.
  8. Plug in back all the 12V cables to the ASIC boards.
  9. Turn the power on.
  10. Happy mining!
submitted by knc_shipping_problem to BeagleBone [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]

Working on an interface to Bitcoin-Qt's / bitcoind's API calls.

Right now, all it does that might be a bit handy is show you which addresses have how many bitcoins.
GitHub
Needed: python 2.7, wxPython 2.8
It is a bit rough at the moment, appearance-wise: a screenshot
I made this because the bitcoin-qt wallet does not have a way (that I've seen) to easily see all addresses, including un-labelled ones. There's the debug console, but that isn't really "easy", especially if you have a lot of addresses... I also use Armory, which will show you all addresses, but it is slow to start and a huge memory hog -- and it won't use the original client's wallet.
You'll need to set up the bitcoin.conf file to accept JSON-RPC commands (see this sample conf -- set server=1 and rpcuserpcpassword to whatever; this script will read them from the file)
It should work on Windows, *nix, and Mac, but I've only tested it in Windows.
If there's any interest, I might work on fleshing this out into a fuller interface. There's a lot of API calls that might be of use to someone.
PS: if you can think of a better name than "advbtc" please suggest it; I am terrible at naming things.
submitted by lowpass to Bitcoin [link] [comments]

Programming Bitcoin-qt using the RPC api (1 of 6) wordpress Site Hacking By Config php File - YouTube openHAB 2 Basics - Editing Configuration Files ... Complete WordPress Video Tutorial - 10 - Modifying the wp-config.php File Bitcoin JSON-RPC Tutorial 3 - bitcoin.conf

The client configuration file must be placed in the home category, ~ / .bitcoind, the file is called bitcoin.conf. nano ~/.bitcoin/bitcoin.conf. Enter: server=1 daemon=1 rpcuser=USERNAME rpcpassword=PASSWORD. Set the logs and password in place of USERNAME and PASSWORD. Now daemon is created to run in the background: The bitcoin.conf file is not created by default, you will need to create it yourself. And also, I never had a c:\users\[username]\appdata\roaming\bitcoin folder as many online answers will suggest, this is because when I installed the bitcoin core program, I chose to put my data directory in a different place than default. The above one is the default file path for Bitcoin and this is the data directory where you should find all your cryptocurrency wallet core files. Within each coin folder there will be a .conf file located. A user-friendly configuration file generator is available here. By default, Bitcoin (or bitcoind) will look for a file named 'bitcoin.conf' in the bitcoin data directory, but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments. Rpcport=8332 # You can use bitcoind to send commands to bitcoin-qt/bitcoind # 1) OK Disabling listening will result in fewer nodes connected (remember the maximum of; Sample Bitcoin.conf ## ## bitcoin.conf configuration file.How to set up a Bitcoin full node on Linux VPS (pruning node ; SYNOPSIS¶ No ultimately trusted keys found gpg:

[index] [38263] [62902] [13759] [61019] [52858] [25674] [58470] [31524] [34067] [47725]

Programming Bitcoin-qt using the RPC api (1 of 6)

In this openhab 2 Basics video, I show you a complete step-by-step guide on setting up Visual Studio Code (VSCode) and the openhab extension by Kuba Wolanin,... Bitcoin JSON-RPC tutorial. Set up your bitcoin.conf file and create custom settings with bitcoind. BTC: 1NPrfWgJfkANmd1jt88A141PjhiarT8d9U. In this video i'll show you how you can hack the wordpress website by configuring php File This is only for educational purpose. do not try to hack website t... Bitcoin-Core: Import private key from old watch only address into non spendable wallet - Duration: 8:10. Bitcoin Daytrader 7,463 views This video demonstrates how to change the modem config file that is assigned to a DOCSIS cable modem.

http://forex-viethnam.earnmining.pw