Bitcoin Forum
December 16, 2018, 04:37:50 PM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 [51] 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 ... 548 »
1001  Bitcoin / Bitcoin Technical Support / Re: BitCoin core writes too fragmented data on: November 13, 2017, 04:49:23 PM
This is not something that Bitcoin Core can control. It is entirely based upon the filesystem and how it allocates space to store data. Bitcoin Core itself has no control over that and cannot control where data is physically located on disk.
1002  Bitcoin / Electrum / Re: BCC/BCH Late claim of bcc with electrum/eletron wallet! on: November 13, 2017, 04:29:25 AM
Your address is a P2SH address; it is likely a multisig address. This means that there are actually multiple seeds. If you only have one seed and are importing that, it will not work because you did not import the other seeds for the other keys in the multisig.

You are probably using the 2 factor authentication thing, so you will need to restore as a 2fa wallet, not a standard wallet.
1003  Bitcoin / Bitcoin Technical Support / Re: Bitcoin "replaceable" for 3 days on: November 13, 2017, 04:25:41 AM
4 days in now... Nothing transaction still hasn't been sent...
Instead of complaining about it, how about you do some of the things that people have suggested to you?

Like this:
See the transaction, right click on the transaction and click "Increase the fee" and a dialog should show up for you to increase the fee. The amount that you are sending to the address will decrease however. I'm actually not really sure how Electrum handles it but that should be the case.
1004  Bitcoin / Armory / Re: chained ZC transaction unconfirmed after 3 days on: November 13, 2017, 04:24:17 AM
Chained ZC means that the transaction spends from a transaction which is also unconfirmed. Your transaction cannot confirm until all unconfirmed transactions that your transaction depends on also confirm.
1005  Other / Beginners & Help / Re: Incredible -Transfer BTC from Homeblockcoin Wallet to Ucoincash Waller very fast on: November 13, 2017, 04:23:22 AM
I mean, as i know, when you withdraw BTC, the transfer take minimum 15 minutes or more.
No, that is not true.

This is normal and not a miracle. You might have been lucky or you don't understand how Bitcoin works. Either a miner saw your transaction when you broadcast it and mined it in a block that was found shortly after you broadcast it, OR your wallet is showing the transaction before it confirms. Nothing special, nothing new.
1006  Bitcoin / Bitcoin Technical Support / Re: BTC Legacy vs Segwit wallet on: November 12, 2017, 05:16:00 AM
There is no "the Segwit chain". That chain is Bitcoin, and all Bitcoin wallets support it and use it regardless of whether they have implemented segwit itself or not.

Will I run into any issues transferring BTC from, say, Coinbase (Segwit) to Exodus (non-Segwit) to Ledger (Segwit)?  Will the middle link (Exodus which is non-Segwit) mess up the transaction in any way?
There is no problem because it is all still Bitcoin and on the Bitcoin chain.
1007  Bitcoin / Development & Technical Discussion / Re: main() in bitcoin-tx.cpp on: November 12, 2017, 05:14:09 AM
What about the in format ? what is 0fb9df56..... ? It is previous tx or scriptSig?
Read https://bitcoin.org/en/developer-reference#raw-transaction-format
1008  Bitcoin / Bitcoin Technical Support / Re: Sent with normal miner fee 28 hours ago and STILL no confirmations. Help! Hash! on: November 12, 2017, 02:22:05 AM
Read https://bitcointalk.org/index.php?topic=1802212.0

Bumping this and any other thread within 24 hours of the previous bump or creation of the thread is a violation for forum rules. Do not do it again.
1009  Bitcoin / Development & Technical Discussion / Re: main() in bitcoin-tx.cpp on: November 12, 2017, 02:05:47 AM
It looks like bitcoin-tx.cpp is never built into the bincoind binary of Bitcoin core, isn't  it?
No, it is not. bitcoin-tx.cpp is for bitcoin-tx, a completely separate binary. It only exists to provide the separate bitcoin-tx binary.
1010  Bitcoin / Development & Technical Discussion / Re: Bitcoin scalability - unite transactions transaction. on: November 12, 2017, 02:04:52 AM
It does not require balance calculation for address/all addresses. It just requires finding all transactions of the address(es), listed in such transaction in specified block number.
... You are contradicting yourself. Balance calculation means "finding all transaction of the addresses". So for your idea to work, you would need to calculate the balance for a given address.

And I guess it should not be difficult to implement.?
That is incorrect. It would be both difficulty to implement, and completely unsafe. Making it safe would make this even harder to implement.

First of all, on the technical level, addresses don't exist. What exist are transaction outputs, and transaction outputs themselves don't have addresses, they have output scripts. An address only encodes what a wallet should use as an output script, but there are infinitely many output scripts that are not related to any address whatsoever.

Furthermore your idea is completely unsafe. What you propose is to use accounts and balances, but such systems are known to be unsafe in the context of a cryptocurrency. For example, suppose you want to pay me and you do so by constructing one of these special transactions. Now later, you receive money to the same addresses, and once the balances are high enough, I broadcast the special transaction again and send your money to myself.
1011  Bitcoin / Armory / Re: Node offline help on: November 11, 2017, 10:07:15 PM
Post the armory log files.
1012  Bitcoin / Development & Technical Discussion / Re: Setting up a Private Regression Test Blockchain with Bitcoincore on: November 11, 2017, 07:12:57 PM
I highly advise that you not follow that article you are following or any other article about compiling Bitcoin Core that is not from the Bitcoin Core developers. Such articles are likely to become outdated as things are changed (the one you are following already is outdated). Instead you should follow the build instructions provided in the Bitcoin Core repository: https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md
1013  Alternate cryptocurrencies / Altcoin Discussion / Re: Obtaining BCash throught a pruned node on: November 11, 2017, 07:07:53 PM
Well that's good hear, im sick of spending 100 GB of data in a coin that I only expect to dump. So I need to wait for the blockchain to be fully synced? Im only 2 weeks away but it's really slow for some reason. Is there a away to add more peers or something to make it go faster? Bitcoin Core goes faster and the blocks are bigger, but the software is the same, so i guess it is a lack of peers?
The software is not the same. The Bitcoin ABC developers have made significant modifications since they forked from Core and those modifications could have drastically reduced the performance of their software.

You can try increasing the dbcache if you have lots of RAM.
1014  Alternate cryptocurrencies / Altcoin Discussion / Re: Obtaining BCash throught a pruned node on: November 11, 2017, 05:20:40 PM
Pruning only effects the blockchain data, not your wallet nor any of your transactions. The UTXO set and the transactions in your wallet are pulled out and stored separately from the blockchain data that is deleted. So yes, with pruning you are able to access your coins even if the transaction that created the output was thrown away by the pruning.
1015  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.15.0.1 Released on: November 11, 2017, 05:07:13 PM
Bitcoin Core 0.15.1 has been released https://bitcointalk.org/index.php?topic=2388679
1016  Bitcoin / Bitcoin Discussion / Bitcoin Core 0.15.1 Released on: November 11, 2017, 05:06:31 PM
Bitcoin Core version *0.15.1* is now available from:

  https://bitcoincore.org/bin/bitcoin-core-0.15.1

or

  https://bitcoin.org/bin/bitcoin-core-0.15.1

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/

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

The first time you run version 0.15.0 or higher, your chainstate database will
be converted to a new format, which will take anywhere from a few minutes to
half an hour, depending on the speed of your machine.

The file format of `fee_estimates.dat` changed in version 0.15.0. Hence, a
downgrade from version 0.15 or upgrade to version 0.15 will cause all fee
estimates to be discarded.

Note that the block database format also changed in version 0.8.0 and there is no
automatic upgrade code from before version 0.8 to version 0.15.0. Upgrading
directly from 0.7.x and earlier without redownloading the blockchain is not supported.
However, as usual, old wallet versions are still supported.

Downgrading warning
-------------------

The chainstate database for this release is not compatible with previous
releases, so if you run 0.15 and then decide to switch back to any
older version, you will need to run the old release with the `-reindex-chainstate`
option to rebuild the chainstate data structures in the old format.

If your node has pruning enabled, this will entail re-downloading and
processing the entire blockchain.

Compatibility
==============

Bitcoin Core is extensively tested on multiple operating systems using
the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported.

Bitcoin Core should also work on most other Unix-like systems but is not
frequently tested on them.


Notable changes
===============

Network fork safety enhancements
--------------------------------

A number of changes to the way Bitcoin Core deals with peer connections and invalid blocks
have been made, as a safety precaution against blockchain forks and misbehaving peers.

- Unrequested blocks with less work than the minimum-chain-work are now no longer processed even
if they have more work than the tip (a potential issue during IBD where the tip may have low-work).
This prevents peers wasting the resources of a node.

- Peers which provide a chain with less work than the minimum-chain-work during IBD will now be disconnected.

- For a given outbound peer, we now check whether their best known block has at least as much work as our tip. If it
doesn't, and if we still haven't heard about a block with sufficient work after a 20 minute timeout, then we send
a single getheaders message, and wait 2 more minutes. If after two minutes their best known block has insufficient
work, we disconnect that peer. We protect 4 of our outbound peers from being disconnected by this logic to prevent
excessive network topology changes as a result of this algorithm, while still ensuring that we have a reasonable
number of nodes not known to be on bogus chains.

- Outbound (non-manual) peers that serve us block headers that are already known to be invalid (other than compact
block announcements, because BIP 152 explicitly permits nodes to relay compact blocks before fully validating them)
will now be disconnected.

- If the chain tip has not been advanced for over 30 minutes, we now assume the tip may be stale and will try to connect
to an additional outbound peer. A periodic check ensures that if this extra peer connection is in use, we will disconnect
the peer that least recently announced a new block.

- The set of all known invalid-themselves blocks (i.e. blocks which we attempted to connect but which were found to be
invalid) are now tracked and used to check if new headers build on an invalid chain. This ensures that everything that
descends from an invalid block is marked as such.


Miner block size limiting deprecated
------------------------------------

Though blockmaxweight has been preferred for limiting the size of blocks returned by
getblocktemplate since 0.13.0, blockmaxsize remained as an option for those who wished
to limit their block size directly. Using this option resulted in a few UI issues as
well as non-optimal fee selection and ever-so-slightly worse performance, and has thus
now been deprecated. Further, the blockmaxsize option is now used only to calculate an
implied blockmaxweight, instead of limiting block size directly. Any miners who wish
to limit their blocks by size, instead of by weight, will have to do so manually by
removing transactions from their block template directly.


GUI settings backed up on reset
-------------------------------

The GUI settings will now be written to `guisettings.ini.bak` in the data directory before wiping them when
the `-resetguisettings` argument is used. This can be used to retroactively troubleshoot issues due to the
GUI settings.


Duplicate wallets disallowed
----------------------------

Previously, it was possible to open the same wallet twice by manually copying the wallet file, causing
issues when both were opened simultaneously. It is no longer possible to open copies of the same wallet.


Debug `-minimumchainwork` argument added
----------------------------------------

A hidden debug argument `-minimumchainwork` has been added to allow a custom minimum work value to be used
when validating a chain.


Low-level RPC changes
----------------------

- The "currentblocksize" value in getmininginfo has been removed.

- `dumpwallet` no longer allows overwriting files. This is a security measure
  as well as prevents dangerous user mistakes.

- `backupwallet` will now fail when attempting to backup to source file, rather than
  destroying the wallet.

- `listsinceblock` will now throw an error if an unknown `blockhash` argument
  value is passed, instead of returning a list of all wallet transactions since
  the genesis block. The behaviour is unchanged when an empty string is provided.

0.15.1 Change log
=================

### Mining
- #11100 `7871a7d` Fix confusing blockmax{size,weight} options, dont default to throwing away money (TheBlueMatt)

### RPC and other APIs
- #10859 `2a5d099` gettxout: Slightly improve doc and tests (jtimon)
- #11267 `b1a6c94` update cli for estimate\*fee argument rename (laanwj)
- #11483 `20cdc2b` Fix importmulti bug when importing an already imported key (pedrobranco)
- #9937 `a43be5b` Prevent `dumpwallet` from overwriting files (laanwj)
- #11465 `405e069` Update named args documentation for importprivkey (dusty-wil)
- #11131 `b278a43` Write authcookie atomically (laanwj)
- #11565 `7d4546f` Make listsinceblock refuse unknown block hash (ryanofsky)
- #11593 `8195cb0` Work-around an upstream libevent bug (theuni)

### P2P protocol and network code
- #11397 `27e861a` Improve and document SOCKS code (laanwj)
- #11252 `0fe2a9a` When clearing addrman clear mapInfo and mapAddr (instagibbs)
- #11527 `a2bd86a` Remove my testnet DNS seed (schildbach)
- #10756 `0a5477c` net processing: swap out signals for an interface class (theuni)
- #11531 `55b7abf` Check that new headers are not a descendant of an invalid block (more effeciently) (TheBlueMatt)
- #11560 `49bf090` Connect to a new outbound peer if our tip is stale (sdaftuar)
- #11568 `fc966bb` Disconnect outbound peers on invalid chains (sdaftuar)
- #11578 `ec8dedf` Add missing lock in ProcessHeadersMessage(...) (practicalswift)
- #11456 `6f27965` Replace relevant services logic with a function suite (TheBlueMatt)
- #11490 `bf191a7` Disconnect from outbound peers with bad headers chains (sdaftuar)

### Validation
- #10357 `da4908c` Allow setting nMinimumChainWork on command line (sdaftuar)
- #11458 `2df65ee` Don't process unrequested, low-work blocks (sdaftuar)

### Build system
- #11440 `b6c0209` Fix validationinterface build on super old boost/clang (TheBlueMatt)
- #11530 `265bb21` Add share/rpcuser to dist. source code archive (MarcoFalke)

### GUI
- #11334 `19d63e8` Remove custom fee radio group and remove nCustomFeeRadio setting (achow101)
- #11198 `7310f1f` Fix display of package name on 'open config file' tooltip (esotericnonsense)
- #11015 `6642558` Add delay before filtering transactions (lclc)
- #11338 `6a62c74` Backup former GUI settings on `-resetguisettings` (laanwj)
- #11335 `8d13b42` Replace save|restoreWindowGeometry with Qt functions (MeshCollider)
- #11237 `2e31b1d` Fixing division by zero in time remaining (MeshCollider)
- #11247 `47c02a8` Use IsMine to validate custom change address (MarcoFalke)

### Wallet
- #11017 `9e8aae3` Close DB on error (kallewoof)
- #11225 `6b4d9f2` Update stored witness in AddToWallet (sdaftuar)
- #11126 `2cb720a` Acquire cs_main lock before cs_wallet during wallet initialization (ryanofsky)
- #11476 `9c8006d` Avoid opening copied wallet databases simultaneously (ryanofsky)
- #11492 `de7053f` Fix leak in CDB constructor (promag)
- #11376 `fd79ed6` Ensure backupwallet fails when attempting to backup to source file (tomasvdw)
- #11326 `d570aa4` Fix crash on shutdown with invalid wallet (MeshCollider)

### Tests and QA
- #11399 `a825d4a` Fix bip68-sequence rpc test (jl2012)
- #11150 `847c75e` Add getmininginfo test (mess110)
- #11407 `806c78f` add functional test for mempoolreplacement command line arg (instagibbs)
- #11433 `e169349` Restore bitcoin-util-test py2 compatibility (MarcoFalke)
- #11308 `2e1ac70` zapwallettxes: Wait up to 3s for mempool reload (MarcoFalke)
- #10798 `716066d` test bitcoin-cli (jnewbery)
- #11443 `019c492` Allow "make cov" out-of-tree; Fix rpc mapping check (MarcoFalke)
- #11445 `51bad91` 0.15.1 Backports (MarcoFalke)
- #11319 `2f0b30a` Fix error introduced into p2p-segwit.py, and prevent future similar errors (sdaftuar)
- #10552 `e4605d9` Tests for zmqpubrawtx and zmqpubrawblock (achow101)
- #11067 `eeb24a3` TestNode: Add wait_until_stopped helper method (MarcoFalke)
- #11068 `5398f20` Move wait_until to util (MarcoFalke)
- #11125 `812c870` Add bitcoin-cli -stdin and -stdinrpcpass functional tests (promag)
- #11077 `1d80d1e` fix timeout issues from TestNode (jnewbery)
- #11078 `f1ced0d` Make p2p-leaktests.py more robust (jnewbery)
- #11210 `f3f7891` Stop test_bitcoin-qt touching ~/.bitcoin (MeshCollider)
- #11234 `f0b6795` Remove redundant testutil.cpp|h files (MeshCollider)
- #11215 `cef0319` fixups from set_test_params() (jnewbery)
- #11345 `f9cf7b5` Check connectivity before sending in assumevalid.py (jnewbery)
- #11091 `c276c1e` Increase initial RPC timeout to 60 seconds (laanwj)
- #10711 `fc2aa09` Introduce TestNode (jnewbery)
- #11230 `d8dd8e7` Fixup dbcrash interaction with add_nodes() (jnewbery)
- #11241 `4424176` Improve signmessages functional test (mess110)
- #11116 `2c4ff35` Unit tests for script/standard and IsMine functions (jimpo)
- #11422 `a36f332` Verify DBWrapper iterators are taking snapshots (TheBlueMatt)
- #11121 `bb5e7cb` TestNode tidyups (jnewbery)
- #11521 `ca0f3f7` travis: move back to the minimal image (theuni)
- #11538 `adbc9d1` Fix race condition failures in replace-by-fee.py, sendheaders.py (sdaftuar)
- #11472 `4108879` Make tmpdir option an absolute path, misc cleanup (MarcoFalke)
- #10853 `5b728c8` Fix RPC failure testing (again) (jnewbery)
- #11310 `b6468d3` Test listwallets RPC (mess110)

### Miscellaneous
- #11377 `75997c3` Disallow uncompressed pubkeys in bitcoin-tx [multisig] output adds (TheBlueMatt)
- #11437 `dea3b87` [Docs] Update Windows build instructions for using WSL and Ubuntu 17.04 (fanquake)
- #11318 `8b61aee` Put back inadvertently removed copyright notices (gmaxwell)
- #11442 `cf18f42` [Docs] Update OpenBSD Build Instructions for OpenBSD 6.2 (fanquake)
- #10957 `50bd3f6` Avoid returning a BIP9Stats object with uninitialized values (practicalswift)
- #11539 `01223a0` [verify-commits] Allow revoked keys to expire (TheBlueMatt)


Credits
=======

Thanks to everyone who directly contributed to this release:

- Andreas Schildbach
- Andrew Chow
- Chris Moore
- Cory Fields
- Cristian Mircea Messel
- Daniel Edgecumbe
- Donal OConnor
- Dusty Williams
- fanquake
- Gregory Sanders
- Jim Posen
- John Newbery
- Johnson Lau
- João Barbosa
- Jorge Timón
- Karl-Johan Alm
- Lucas Betschart
- MarcoFalke
- Matt Corallo
- Paul Berg
- Pedro Branco
- Pieter Wuille
- practicalswift
- Russell Yanofsky
- Samuel Dobson
- Suhas Daftuar
- Tomas van der Wansem
- Wladimir J. van der Laan

As well as everyone that helped translating on Transifex.
1017  Other / Beginners & Help / Re: Bit coin scam on: November 11, 2017, 05:00:36 PM
Use your brain and think before investing any money into anything. If it looks too good to be true, then it probably is.
1018  Bitcoin / Armory / Re: Node offline help on: November 11, 2017, 04:49:36 PM
In Armory's settings, there is a field for "Bitcoin Core datadir location" (something like that). You must set that to be the location where you have Bitcoin Core's datadir, i.e. your external drive.
1019  Alternate cryptocurrencies / Altcoin Discussion / Re: How install BTH node? on: November 11, 2017, 04:47:47 PM
You must install a Bitcoin Cash node software. Most people use Bitcoin ABC to do that. There are also versions of Bitcoin Unlimited, Bitcoin Classic, and Bitcoin XT which are compatible with Bitcoin Cash.
1020  Bitcoin / Development & Technical Discussion / Re: are fork splits because of private block chain creations? on: November 11, 2017, 04:44:30 PM
Blockchain forks have nothing to do with private blockchains. Anyone can create a blockchain fork (and thus a new cryptocurrency) by deciding on some activation parameter (e.g. block height after X) and changing a consensus rule in some backwards incompatible way (e.g. raising the maximum block size). Then they write or modify a full node software to follow these new consensus rules (which includes the activation parameter). When the activation parameter is met, if the people making the fork have enough hash rate, they will create a blockchain split and there will then be two branches of the blockchain. One will be for Bitcoin and the other for the altcoin that was created.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 [51] 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 ... 548 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!