Bitcoin Block Explorer BlockCypher

12-07 18:47 - 'Stuck with an unconfirmed transaction? Try BTC.COM's transaction fee tracker, seems simpler than others.' (btc.com) by /u/nishant_sharma removed from /r/Bitcoin within 559-564min

Stuck with an unconfirmed transaction? Try BTC.COM's transaction fee tracker, seems simpler than others.
Go1dfish undelete link
unreddit undelete link
Author: nishant_sharma
submitted by removalbot to removalbot [link] [comments]

MiningPoolHub/AwesomeMiner/MultiMinningPool FAQ

Hello everyone,
As some of you have probably noticed I have been taking the time to try my best to help some of you answer some questions.
 
However there has been a lot of repeat questions lately so hopefully this will help. I will continue to update this as we go, please check back if you have any questions as I will try to update this frequently
 
 
If you have a question you do not see covered please feel free to comment and I'll add it and try to answer it. I have added a unresolved to the beginning of this FAQ. I will number them below. Please comment below with the answer, to help me identify which question you are answering please add. UR#(x) to your comment as well, with x being the number of the unresolved question.
 
 
Before we start I will get my disclaimer out of the way.
I do not work with/for any of the developers of these programs. I do not have all the answers. Some of these are my best guess, others may be wrong or may have a better solution than the one I give. Please feel free to correct me if this is the case and I will edit as we go.
 
 
Set-up
We have two text guides here by waffleflops one for awesome miner and one for multi mining pool.
We also have a YouTube video guide by razorseal
 
YouTube Video Guide: Here
Awesome Miner(AM): Text Tutorial
MultiPoolMiner(MPM): Text Tutorial
 
 
So which one should I use?
It seems like it depends on what you want from the program, Awesome Miner is more like Nicehash in the way it looks but can be a little more complicated. MPM is pretty simple but it has less customization for those not familiar with programming.
 
NX18: "I find MPM to be better. No stability issues, no funky windows service always running in the background, and it checks MPH for best coin to mine whereas AM checks whattomine.com and they differ significantly sometimes."
 
MPM also has a minimum dev fee of 10 minutes per day (even if you set donate to 0) whereas AM does not seem to have dev fees. Both I believe have fees included that go to the devs of the miner programs themselves. However these fees for the miner devs will be attached whether you use MPM/AM or solo miner with the miner dev programs anyway.
 
 
Unresolved Questions
 
1. Anyone have solutions on crashing or very low Hashrates in sgminers with AMD GPU's in Awesome Miner?
2. Why is Lyra2Z using only 40% power from my GPU (GTX980ti)? Where/how can it tweak the settings?
I believe this is having to do with Awesome Miner 3.I did not see it asked or posted but I am curious if there's a way to bench all gpus. Instead of selecting gpu 0 and benching, waiting until its done and moving on to gpu 1 and so on. I have 8 nvidia gpus, just wondering if there's a way to auto bench all of them in a row so I can walk away and go to bed, be done I'm the middle of the night.
 
 
General MPH Questions
 
1.Hashrate is not the same on my miner as it is on the dashboard?
From MPH: "Hashrate showing on site is just an estimated value. Pool doesn't know about miner very much. It just collects certain "shares" which is some piece of hash that satisfies certain conditions. So don't worry, it's all about probability thing. Your hashrate on site can go up and down time to time."
There is some luck involved when mining in pools it is like playing the lottery. NiceHash paid at a certain rate because you were not mining coins and getting paid you were getting paid for the hash you are providing.
 
2. Balances on MPH what are the brackets?
The brackets are coins that have not yet been confirmed enough times on the blockchain. Any coins not in brackets have been confirmed.
 
3. How long will it take for my coins to show up, transfer to and from the exchange, be credited to my auto exchange coin?
 
I have been seeing a lot of questions about this so I made a flowchart which you can view Here
 
Short Answer: It depends could be minutes could be days
Long Answer: It has to be exchanged first and then placed in auto-exchange balance balance.
So you mine coin
Coin credited but unconfirmed (this can take time depending on coin)
Coin is confirmed and credited for auto exchange.
Coin is then placed on exchange. So again has to be transferred and again has to be confirmed but on exchange side.
Coin is most likely converted into btc then into auto-exchange coin at exchange.
Then auto-exchange coin is sent back to your balance on mph. So again has to be confirmed before appearing.
Depending on how fast a coin is confirmed will depend on how fast it appears in your balance.
If you stopped mining today it your balance most likely continue to grow over time.
However if you continue to mine it should in theory catch up and you will see you balance grow at a semi if not expected rate.
 
Supplemental:Forgive me if I'm misunderstanding, but this should mean it changes column, not disappears from balance entirely, no?
You will not know exact balance until it is sent back over from the exchange. This is because of the fact that you are exchanging the coins against one another. If one coin is up and one is down you could be losing or gaining value depending on the situation. This is why it seems that coins on the exchange disappear without your auto-exchange coins balance going up right away. Reference question 8 for more info
 
4. What is the best coin to auto-exchange?
This depends, just remember BTC has high transaction fees and can take some time to confirm. You will want to have a good amount of BTC before moving to your wallet to minimize the amount you lose to transaction fees.
I personally use LTC, it is quick and transaction fees are low compared to BTC but can still be exchanged for fiat on coinbase.
At the time of writing this, if you move BTC from MPH you will be charged a $4.96 fee, if you move LTC the fee to move to your wallet is $0.19
 
5. Can I hold on to certain coins instead of auto-exchanging them?
Yes, just go to auto exchange on MPH and switch off the coin you do not want to auto exchange.
 
6. This dashboard sucks! Why do they not have a one page dashboard?
Good news it is in the works, improvements are on the way so no need to keep posting about it!
 
7. Why is my coin not being exchanged?
Two possible reasons A)On balances page it says "coins that don't have enough volume on exchange for a certain amount of time will not be auto exchanged to desired coin. These coins may be sent back as original coin or btc."
B)On auto-exchange page. Mph accumulates coins so that they can be efficiently converted at the exchange. If a coins pool has not mined a certain amount it will not be sent over until it reaches the set number. It seems like it is transferred over to the exchange as one large amount instead of small amounts.
 
8. AwesomeMiner said I was going to make $X.XX dollars and when auto-exchange coins came in I made less than it said!
Couple things, do not take to heart the exact number it gives you. It is not exact remember it is like a lottery.
Remember your coins at first will trickle in over time but the longer you mine it will begin to average out.
Remember you are exchanging coins for you auto-exchange coin this means if there is a decrease or increase between them you could gain more or less.
Example if you mine VTC and auto-exchange into LTC.
You send VTC to auto-exchange it will most likely be converted into BTC first. If BTC is having a good day that day and has increased in price by 30% and VTC has not grown well that day you will be trading your VTC at a loss.
Then this same situation will happen again when converting the BTC to LTC.
So again a bit of a lottery you may gain or lose some of your mined coins value depending on the exchange rate between the coins at the time.
 
9. Add more Cryptonight coins please.
They are apparently working on adding new coins like Electroneum.
 
10. Why can't I auto-exchange BTC?
My theory is that it is because BTC is not mined on MPH, remember the coins are sent to the exchange when they hit a certain amount in order to make it efficient. Because BTC is not mined on MPH it would not be efficient to exchange BTC to other coins once it has been credited to your account.
 
11. Do I need a wallet for each coin I mine? How do I set-up a wallet?
No, only the coin(s) you want to get paid in. Click on coins pool on MPH and you will see a wallet option Add the correct address for each coin you want to be paid in, note you cannot use another coins address or you risk losing your coins. For example you should not put your Bitcoin address into your Litecoin wallet address section.
 
12. My wallet address keeps on changing, do I need to keep updating my wallet address?
Take from Coinbase: This is done to protect your privacy, so that a third-party can not view all other transactions associated with your account simply by using a blockchain explorer to look-up an address they know to be yours.
All addresses that have been generated for your account will remain associated with your account forever. They are safe to re-use to receive future payments, but for the prior stated reasons, we recommend using a unique address for all transactions.
 
13.Is there a easy way I can track my Profits/Hashrate/Workers?
Yes credit to JaymZZZ Click Here
 
14. I click on manage wallet from the balances menu and enter my account number, I get the error saying Failed to update your account: Invalid coin address.
Make sure you are adding the address to the correct coin. A bitcoin address for example should only be added to the bitcoin wallet, it should not be added to any other wallet. (Reference question 11)
 
15. Is there a fee for auto-exchange?
Yes 0.2%
 
 
Awesome Miner
 
1. I do not want to mine that algo, I turn it off but it still mines it!
Go to online services, edit, change profit switching from yes to no
 
2. Why is it mining something less profitable?
Make sure you go to tools and then benchmark Make sure you right click and save hashrate occasionally it will improve your profit switching over time.
 
3. I can't get the miner to run?
Did you exclude it from anti-virus?
You may need to reinstall.
Uninstall
then in search bar type in %localappdata%\awesomeminer (delete this folder)
Type in %appdata% go to awesome miner folder and delete this one as well
Reinstall awesomeminer
Do not run aweseomminer
Go to anti-virus and exclude all folders with awesomeminer (including the ones in the local and appdata folders)
 
4. How do i delete a Miner?
samualsmash: https://i.imgur.com/SSr1rnH.png
 
5. Can I do anything to make improvements?
puch0021:You can use VertMiner (which is what is used by OCM) to increase your hash rate compared to AwesomeMiner's default CCminer. You have to choose it for Lyra instead of CC miner. See: http://www.awesomeminer.com/help/managedsoftware.aspx Download Vertminer and extract software. Go to awesomeminer's options -> managed software -> add new user defined mining software: Type in VertMiner for description, full compatibility mode, and compatible software as CCminer. Everything in the algorithm should be disabled expect Lyra2ReV2 which should be enabled. Double click in under defined command line argument and add lyra2v2 as text. Click ok. Go to profit profiles in awesome miner. Select nvidia GPU and edit. In the mining software list there should be a new VertMiner entry. Check this box to enable it. Then click configure and then under path click browse. Click local. Select the Vertminer folder you previously made. Now whenever lyra is called for, vertminer should be used. If you try to bench mark with this enabled, it will fail but it works for mining. You can then use your mining results to manually edit your profit profile value for Lyra2REv2 (that was otherwise has the old value for ccminer.) On my 1060 it went from 21 to 22.8. Keep in mind vertminer takes 2% dev fees but it still works out to be faster than cc miner. let me know if this was any help!
I used one click miners vertminer since it was already installed.
 
6. Whenever Awesome Miner starts on a new algo and opens new instances of the CLI miner application/s, the window steal the focus from whatever you're doing. Anyone else super annoyed by this? Anyone know of a way to prevent this?
Stop mining, click more, properties, environment, console window mode, hide window, start mining again.
 
 
MultiPoolMiner (MPM)
 
1. I see a yellow stripe wich says multipoolminer is between 7% and 17% more profitable, which is nice. under this strip I see 2 lines with miner, BTC and Euro. (in my case) which of those btc values end up on your miningpoolhub balance? or both?
NX18:" Neither. Those values are best guesses by that script, hence why beside the dollar figure it shows the +/- variance which sometimes is really high like 25%, meaning that scripts best guess could be wrong by that much"
It is showing the 2nd best, If it is not the best at the time it will not show that text and just give you the comparison.
 
2. It keeps say NiceHash API failed what should I do? You can ignore it or as chillfisch points out that you can just delete the nicehash folder to get rid of this warning.
 
 
Tips
Gator-Empire
BTC: 16pVcKVFRJnCpR3hohMZtSTuiFiYy8MuCY LTC: LagCM9kiRHSbfx7ycCdrsae3QxqyycrFEr ETH: 0x6bbfe42dadc1894a19ad448b8296E7e7da383D2d
 
Waffleflops (MPM and Awesome Miner tutorial creator)
BTC: 17zd54AxSZekcPkVyEiX6TrcJkUe2qja51 LTC: LeyvTNrQfrhHK8TgtB8qWzKTMmNSaRif5m ETH: 0xaE19a33f3f9568e8775A05A92DF2fca4f3a5405b
 
JaymZZZ (Profit/Hashrate/Worker tracker creator)
BTC: 17ZjS6ZJTCNWrd17kkZpgRHYZJjkq5qT5A LTC: LdGQgurUKH2J7iBBPcXWyLKUb8uUgXCfFF ETH: 0x6e259a08a1596653cbf66b2ae2c36c46ca123523
 
razorseal (YouTube video guide creator)
BTC: 13UtW3vN4DKmmjV45dL5LHwcV8svu9tuzz LTC: Lh2DiirhVhFdX9VwWS5cY9dxyRGKV9JDGs ETH:0x260fAdC32972ca102C5CA3fAF3996C609C6C0311
submitted by Gator-Empire to MiningPoolHub [link] [comments]

r/Bitcoin recap - February 2018

Hi Bitcoiners!
I’m back with the fourteenth monthly Bitcoin news recap.
For those unfamiliar, each day I pick out the most popularelevant/interesting stories in Bitcoin and save them. At the end of the month I release them in one batch, to give you a quick (but not necessarily the best) overview of what happened in bitcoin over the past month.
You can see recaps of the previous months on Bitcoinsnippets.com
A recap of Bitcoin in February 2018
submitted by SamWouters to Bitcoin [link] [comments]

[uncensored-r/Bitcoin] r/Bitcoin recap - February 2018

The following post by SamWouters is being replicated because some comments within the post(but not the post itself) have been silently removed.
The original post can be found(in censored form) at this link:
np.reddit.com/ Bitcoin/comments/818fkc
The original post's content was as follows:
Hi Bitcoiners!
I’m back with the fourteenth monthly Bitcoin news recap.
For those unfamiliar, each day I pick out the most popularelevant/interesting stories in Bitcoin and save them. At the end of the month I release them in one batch, to give you a quick (but not necessarily the best) overview of what happened in bitcoin over the past month.
You can see recaps of the previous months on Bitcoinsnippets.com
A recap of Bitcoin in February 2018
submitted by censorship_notifier to noncensored_bitcoin [link] [comments]

Bitcoin Core 0.13.2 released | Wladimir J. van der Laan | Jan 03 2017

Wladimir J. van der Laan on Jan 03 2017:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Bitcoin Core version 0.13.2 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.13.2/
Or by bittorrent:
magnet:?xt=urn:btih:746697d03db3ff531158b1133bab5d1e4cef4e5a&dn;=bitcoin-core-0.13.2&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%2Ftracker.leechers-paradise.org%3A6969&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoincore.org/en/list/announcements/join/
Compatibility

Microsoft ended support for Windows XP on April 8th, 2014,
an OS initially released in 2001. This means that not even critical security
updates will be released anymore. Without security updates, using a bitcoin
wallet on a XP machine is irresponsible at least.
In addition to that, with 0.12.x there have been varied reports of Bitcoin Core
randomly crashing on Windows XP. It is not clear
what the source of these crashes is, but it is likely that upstream
libraries such as Qt are no longer being tested on XP.
We do not have time nor resources to provide support for an OS that is
end-of-life. From 0.13.0 on, Windows XP is no longer supported. Users are
suggested to upgrade to a newer version of Windows, or install an alternative OS
that is supported.
No attempt is made to prevent installing or running the software on Windows XP,
you can still do so at your own risk, but do not expect it to work: do not
report issues about Windows XP to the issue tracker.
but severe issues with the libc++ version on 10.7.x keep it from running reliably.
0.13.1 now requires 10.8+, and will communicate that to 10.7 users, rather than crashing unexpectedly.
Notable changes

Change to wallet handling of mempool rejection
When a newly created transaction failed to enter the mempool due to
the limits on chains of unconfirmed transactions the sending RPC
calls would return an error. The transaction would still be queued
in the wallet and, once some of the parent transactions were
confirmed, broadcast after the software was restarted.
This behavior has been changed to return success and to reattempt
mempool insertion at the same time transaction rebroadcast is
attempted, avoiding a need for a restart.
Transactions in the wallet which cannot be accepted into the mempool
can be abandoned with the previously existing abandontransaction RPC
(or in the GUI via a context menu on the transaction).
0.13.2 Change log

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

Consensus

RPC and other APIs

Block and transaction handling

P2P protocol and network code

Build system

GUI

Wallet

Tests and QA

Miscellaneous

Credits

Thanks to everyone who directly contributed to this release:
As well as everyone that helped translating on Transifex.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJYa2IbAAoJEHSBCwEjRsmmiQsIALbkHVVwO7nViQKH1Ub2qpD4
TplOuAP0/4vYotizuI12Gqdnu8SjPmhKwAgIXhVinE6TS4OzGNjy+6LtWGzpcpud
B1pcziZ72Mlfxdbdd1UhDMWEjoBumS9RmXMSqzTlMVlHRv4iiISzdaAROu1jHvdF
YTsnmKXB8OvcXOecxRMY9LrnpSzLALM2MYTDmYwlhhExHIA8ZqI2niky6GCfyfDi
KD7bgfIFJzlgFTpAdhQXOXtWoRV5iHqN7T29ot8Y+yIhVCRhHYXS93Z50GKbkqYV
MXsVAkpZF3qqcKYSPFjbif7faMdrMqcEiII6QhXdDTRGI/35IfuTDbWzzQlnVyY=
=ncCY
-----END PGP SIGNATURE-----
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-January/013412.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

[Meta] Re: Bitcoin Core 0.13.2 released | Luke Dashjr | Jan 07 2017

Luke Dashjr on Jan 07 2017:
I don't think release announcements are really appropriate for the bitcoin-dev
mailing list. People who want these can subscribe to the bitcoin-core-dev list
and/or the Core announce mailing list. Maybe sending to bitcoin-discuss would
also make sense, but not bitcoin-dev...
Luke
On Tuesday, January 03, 2017 8:47:36 AM Wladimir J. van der Laan via bitcoin-
dev wrote:
Bitcoin Core version 0.13.2 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.13.2/
Or by bittorrent:
magnet:?xt=urn:btih:746697d03db3ff531158b1133bab5d1e4cef4e5a&dn=bitcoin-co
re-0.13.2&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%
2Ftracker.leechers-paradise.org%3A6969&ws=https%3A%2F%2Fbitcoin.org%2Fbin%2
F
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoincore.org/en/list/announcements/join/
Compatibility

Microsoft ended support for Windows XP on [April 8th,
2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support
), an OS initially released in 2001. This means that not even critical
security updates will be released anymore. Without security updates, using
a bitcoin wallet on a XP machine is irresponsible at least.
In addition to that, with 0.12.x there have been varied reports of Bitcoin
Core randomly crashing on Windows XP. It is [not
clear](https://github.com/bitcoin/bitcoin/issues/7681#issuecomment-2174398
91) what the source of these crashes is, but it is likely that upstream
libraries such as Qt are no longer being tested on XP.
We do not have time nor resources to provide support for an OS that is
end-of-life. From 0.13.0 on, Windows XP is no longer supported. Users are
suggested to upgrade to a newer version of Windows, or install an
alternative OS that is supported.
No attempt is made to prevent installing or running the software on Windows
XP, you can still do so at your own risk, but do not expect it to work: do
not report issues about Windows XP to the issue tracker.
From 0.13.1 onwards OS X 10.7 is no longer supported. 0.13.0 was intended
to work on 10.7+, but severe issues with the libc++ version on 10.7.x keep
it from running reliably. 0.13.1 now requires 10.8+, and will communicate
that to 10.7 users, rather than crashing unexpectedly.
Notable changes

Change to wallet handling of mempool rejection
When a newly created transaction failed to enter the mempool due to
the limits on chains of unconfirmed transactions the sending RPC
calls would return an error. The transaction would still be queued
in the wallet and, once some of the parent transactions were
confirmed, broadcast after the software was restarted.
This behavior has been changed to return success and to reattempt
mempool insertion at the same time transaction rebroadcast is
attempted, avoiding a need for a restart.
Transactions in the wallet which cannot be accepted into the mempool
can be abandoned with the previously existing abandontransaction RPC
(or in the GUI via a context menu on the transaction).
0.13.2 Change log

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

Consensus

  • #9293 e591c10 [0.13 Backport #9053] IBD using chainwork instead of
height and not using header timestamp (gmaxwell) - #9053 5b93eee IBD
using chainwork instead of height and not using header timestamps
(gmaxwell)

RPC and other APIs

  • 8845 1d048b9 Don't return the address of a P2SH of a P2SH (jnewbery)

  • 9041 87fbced keypoololdest denote Unix epoch, not GMT

(s-matthew-english) - #9122 f82c81b fix getnettotals RPC description
about timemillis (visvirial) - #9042 5bcb05d [rpc] ParseHash: Fail when
length is not 64 (MarcoFalke) - #9194 f26dab7 Add option to return
non-segwit serialization via rpc (instagibbs) - #9347 b711390 [0.13.2]
wallet/rpc backports (MarcoFalke)
  • #9292 c365556 Complain when unknown rpcserialversion is specified
(sipa) - #9322 49a612f [qa] Don't set unknown rpcserialversion
(MarcoFalke)

Block and transaction handling

  • 8357 ce0d817 [mempool] Fix relaypriority calculation error (maiiz)

  • 9267 0a4aa87 [0.13 backport #9239] Disable fee estimates for a confirm

target of 1 block (morcos) - #9196 0c09d9f Send tip change notification
from invalidateblock (ryanofsky)

P2P protocol and network code

  • #8995 9ef3875 Add missing cs_main lock to ::GETBLOCKTXN processing
(TheBlueMatt) - #9234 94531b5 torcontrol: Explicitly request RSA1024
private key (laanwj) - #8637 2cad5db Compact Block Tweaks (rebase of

8235) (sipa)

  • #9058 286e548 Fixes for p2p-compactblocks.py test timeouts on travis
(#8842) (ryanofsky) - #8865 4c71fc4 Decouple peer-processing-logic from
block-connection-logic (TheBlueMatt) - #9117 6fe3981 net: don't send
feefilter messages before the version handshake is complete (theuni) -

9188 ca1fd75 Make orphan parent fetching ask for witnesses (gmaxwell) -

9052 3a3bcbf Use RelevantServices instead of node_network in

AttemptToEvict (gmaxwell) - #9048 9460771 [0.13 backport #9026] Fix
handling of invalid compact blocks (sdaftuar) - #9357 03b6f62 [0.13
backport #9352] Attempt reconstruction from all compact block
announcements (sdaftuar) - #9189 b96a8f7 Always add
default_witness_commitment with GBT client support (sipa) - #9253
28d0f22 Fix calculation of number of bound sockets to use (TheBlueMatt)
  • #9199 da5a16b Always drop the least preferred HB peer when adding a
new one (gmaxwell)

Build system

  • 9169 d1b4da9 build: fix qt5.7 build under macOS (theuni)

  • 9326 a0f7ece Update for OpenSSL 1.1 API (gmaxwell)

  • 9224 396c405 Prevent FD_SETSIZE error building on OpenBSD (ivdsangen)

GUI

  • #8972 6f86b53 Make warnings label selectable (jonasschnelli)
(MarcoFalke) - #9185 6d70a73 Fix coincontrol sort issue (jonasschnelli)
  • #9094 5f3a12c Use correct conversion function for boost::path datadir
(laanwj) - #8908 4a974b2 Update bitcoin-qt.desktop (s-matthew-english)
  • #9190 dc46b10 Plug many memory leaks (laanwj)

Wallet

  • #9290 35174a0 Make RelayWalletTransaction attempt to AcceptToMemoryPool
(gmaxwell) - #9295 43bcfca Bugfix: Fundrawtransaction: don't terminate
when keypool is empty (jonasschnelli) - #9302 f5d606e Return txid even
if ATMP fails for new transaction (sipa) - #9262 fe39f26 Prefer coins
that have fewer ancestors, sanity check txn before ATMP (instagibbs)

Tests and QA

  • #9159 eca9b46 Wait for specific block announcement in p2p-compactblocks
(ryanofsky) - #9186 dccdc3a Fix use-after-free in scheduler tests
(laanwj)
  • #9168 3107280 Add assert_raises_message to check specific error message
(mrbandrews) - #9191 29435db 0.13.2 Backports (MarcoFalke)
  • 9077 1d4c884 Increase wallet-dump RPC timeout (ryanofsky)

  • 9098 ecd7db5 Handle zombies and cluttered tmpdirs (MarcoFalke)

  • 8927 387ec9d Add script tests for FindAndDelete in pre-segwit and

segwit scripts (jl2012) - #9200 eebc699 bench: Fix subtle counting issue
when rescaling iteration count (laanwj)

Miscellaneous

  • #8838 094848b Calculate size and weight of block correctly in
CreateNewBlock() (jnewbery) - #8920 40169dc Set minimum required Boost
to 1.47.0 (fanquake)
  • #9251 a710a43 Improvement of documentation of command line parameter
'whitelist' (wodry) - #8932 106da69 Allow bitcoin-tx to create v2
transactions (btcdrak) - #8929 12428b4 add software-properties-common
(sigwo)
  • #9120 08d1c90 bug: Missed one "return false" in recent refactoring in

9067 (UdjinM6) - #9067 f85ee01 Fix exit codes (UdjinM6)

  • 9340 fb987b3 [0.13] Update secp256k1 subtree (MarcoFalke)

  • 9229 b172377 Remove calls to getaddrinfo_a (TheBlueMatt)

Credits

Thanks to everyone who directly contributed to this release:
  • Alex Morcos
  • BtcDrak
  • Cory Fields
  • fanquake
  • Gregory Maxwell
  • Gregory Sanders
  • instagibbs
  • Ivo van der Sangen
  • jnewbery
  • Johnson Lau
  • Jonas Schnelli
  • Luke Dashjr
  • maiiz
  • MarcoFalke
  • Masahiko Hyuga
  • Matt Corallo
  • matthias
  • mrbandrews
  • Pavel Janík
  • Pieter Wuille
  • randy-waterhouse
  • Russell Yanofsky
  • S. Matthew English
  • Steven
  • Suhas Daftuar
  • UdjinM6
  • Wladimir J. van der Laan
  • wodry
As well as everyone that helped translating on
Transifex.
bitcoin-dev mailing list
bitcoin-dev at lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-January/013442.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

Bitcoin-QT 0.9 disponível para download

The Core Developers of Bitcoin released the 0.9.0 FINAL of Bitcoin Core (aka Bitcoin QT).
DOWNLOAD:
This is a Final Version, but its the same as 0.9.0rc3
Sources: https://github.com/bitcoin/bitcoin/releases http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.9.0/ https://bitcoin.org/bin/0.9.0/README.txt
Bitcoin Core version 0.9.0 is now available from:
https://bitcoin.org/bin/0.9.0/
This is a release candidate for a new major version. A major version brings both new features and bug fixes.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

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), uninstall all earlier versions of Bitcoin, then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).
If you are upgrading from version 0.7.2 or earlier, the first time you run 0.9.0 your blockchain files will be re-indexed, which will take anywhere from 30 minutes to several hours, depending on the speed of your machine.
On Windows, do not forget to uninstall all earlier versions of the Bitcoin client first, especially if you are switching to the 64-bit version.

Windows 64-bit installer

New in 0.9.0 is the Windows 64-bit version of the client. There have been frequent reports of users running out of virtual memory on 32-bit systems during the initial sync. Because of this it is recommended to install the 64-bit version if your system supports it.
NOTE: Release candidate 2 Windows binaries are not code-signed; use PGP and the SHA256SUMS.asc file to make sure your binaries are correct. In the final 0.9.0 release, Windows setup.exe binaries will be code-signed.

OSX 10.5 / 32-bit no longer supported

0.9.0 drops support for older Macs. The minimum requirements are now: * A 64-bit-capable CPU (see http://support.apple.com/kb/ht3696); * Mac OS 10.6 or later (see https://support.apple.com/kb/ht1633).

Downgrading warnings

The 'chainstate' for this release is not always compatible with previous releases, so if you run 0.9 and then decide to switch back to a 0.8.x release you might get a blockchain validation error when starting the old release (due to 'pruned outputs' being omitted from the index of unspent transaction outputs).
Running the old release with the -reindex option will rebuild the chainstate data structures and correct the problem.
Also, the first time you run a 0.8.x release on a 0.9 wallet it will rescan the blockchain for missing spent coins, which will take a long time (tens of minutes on a typical machine).

Rebranding to Bitcoin Core

To reduce confusion between Bitcoin-the-network and Bitcoin-the-software we have renamed the reference client to Bitcoin Core.

Autotools build system

For 0.9.0 we switched to an autotools-based build system instead of individual (q)makefiles.
Using the standard "./autogen.sh; ./configure; make" to build Bitcoin-Qt and bitcoind makes it easier for experienced open source developers to contribute to the project.
Be sure to check doc/build-*.md for your platform before building from source.

Bitcoin-cli

Another change in the 0.9 release is moving away from the bitcoind executable functioning both as a server and as a RPC client. The RPC client functionality ("tell the running bitcoin daemon to do THIS") was split into a separate executable, 'bitcoin-cli'. The RPC client code will eventually be removed from bitcoind, but will be kept for backwards compatibility for a release or two.

walletpassphrase RPC

The behavior of the walletpassphrase RPC when the wallet is already unlocked has changed between 0.8 and 0.9.
The 0.8 behavior of walletpassphrase is to fail when the wallet is already unlocked:
> walletpassphrase 1000 walletunlocktime = now + 1000 > walletpassphrase 10 Error: Wallet is already unlocked (old unlock time stays) 
The new behavior of walletpassphrase is to set a new unlock time overriding the old one:
> walletpassphrase 1000 walletunlocktime = now + 1000 > walletpassphrase 10 walletunlocktime = now + 10 (overriding the old unlock time) 

Transaction malleability-related fixes

This release contains a few fixes for transaction ID (TXID) malleability issues:

Transaction Fees

This release drops the default fee required to relay transactions across the network and for miners to consider the transaction in their blocks to 0.01mBTC per kilobyte.
Note that getting a transaction relayed across the network does NOT guarantee that the transaction will be accepted by a miner; by default, miners fill their blocks with 50 kilobytes of high-priority transactions, and then with 700 kilobytes of the highest-fee-per-kilobyte transactions.
The minimum relay/mining fee-per-kilobyte may be changed with the minrelaytxfee option. Note that previous releases incorrectly used the mintxfee setting to determine which low-priority transactions should be considered for inclusion in blocks.
The wallet code still uses a default fee for low-priority transactions of 0.1mBTC per kilobyte. During periods of heavy transaction volume, even this fee may not be enough to get transactions confirmed quickly; the mintxfee option may be used to override the default.

0.9.0 Release notes

RPC:
Command-line options:
Block-chain handling and storage:
Wallet:
Mining:
Protocol and network:
Validation:
Build system:
GUI:
submitted by allex2501 to BrasilBitcoin [link] [comments]

EARN BITCOIN DAILY  BTC UNCONFIRMED TRANSACTION $ MAKE ... Best Bitcoin Unconfirmed Transaction Software  Get Funds ... Withdraw Any Bitcoin Blockchain Unconfirmed Transaction ... Blockchain Unconfirmed Transactions Hacked Free Script ... Bitcoin Unconfirmed Transaction,fake bitcoin transaction ...

Unconfirmed transactions do not have a block height since they haven’t been included in a block (yet). In the hex format of block 498303, we can confirm that the transaction exists. Block 498303 in Hex. We shall dissect this transaction. We shall use Blockcypher to decode the transaction. Take the transaction hex and paste into the decoder. Coinbase Transaction decoder. The transaction ... Free Bitcoin Transaction Accelerator. BitAccelerate is a free Bitcoin transaction accelerator that allows you to get faster confirmations on your unconfirmed transactions. Just enter the transaction ID (TXID) and click the "Accelerate" button. Our service will rebroadcast the transaction via 10 Bitcoin nodes.. When more people start to use Bitcoin, the block size reaches the limit and leads to ... This page displays the number and size of the unconfirmed bitcoin transactions, also known as the transactions in the mempool. It gives a real-time view and shows how the mempool evolves over the time. The transactions are colored by the amount of fee they pay per (virtual) byte. The data is generated from my full node and is updated every minute. Note that in bitcoin there is no global ... Check Bitcoin addresses, lookup transactions & monitor wallet balances with our block explorer & BTC address finder. No signup required, free to use! Lookup your bitcoin address / wallet Bitcoin Invoice + Search Search tips: Multiple addresses can be searched at once by seperating with whitespace; Xpub can be searched to get complete wallet balance; To create invoice search your receiving ... Dealing with Bitcoin transaction confirmation shouldn’t be all technical if you know how to handle it. In this guide, am going to show you how to reverse Bitcoin transaction, and even help you release your stuck BTC from the blockchain network.. Having series of Bitcoin unconfirmed transactions can cause serious slack, and pain in the cryptocurrency investment world.

[index] [13851] [45348] [22134] [30683] [11287] [48231] [29219] [23257] [37107] [3271]

EARN BITCOIN DAILY BTC UNCONFIRMED TRANSACTION $ MAKE ...

Blockchain Script Download : http://bit.ly/2krjzpa Earn upto 1BTC per month using this browser. https://in.orangepie.biz/9958813 PLS NOTE: THE VIDEO IS FOR E... In this video, I show you bitcoin unconfirmed transaction hack - bitcoin unconfirmed transaction script hack 2020 (no scam) bitcoin unconfirmed transaction... #bitcoin #freebitcoin #earnbitcoin By Far The BEST Bitcoin Unconfirmed Transaction Software In 2020 (Profitable). This is a review on the most profitable, ea... Cryptocurrency Passive Income 2020: In this video we discuss how to earn crypto and bitcoin easily! It's not easy to earn Bitcoin, especially in cryptocurren... #fakebitcoinsender #bitcoinunconfirmedtransactiob #fakebitcoinsoftware #inthetrend #Hackbitcoinwallet #hackblockchain #bitcoingenerator #bitcoingeneratorhack...

#