Bitcoin Forum
November 25, 2020, 05:54:39 AM *
News: Latest Bitcoin Core release: 0.20.1 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 »
1  Bitcoin / Development & Technical Discussion / MuSig2: Simple Two-Round Schnorr Multi-Signatures on: October 14, 2020, 07:00:30 PM
New paper from Jonas Nick, Tim Ruffing, and Yannick Seurin for a 2 round Schnorr Multisignature scheme based upon the original 3 round MuSig scheme.

Quote
Abstract: Multi-signatures enable a group of signers to produce a single signature on a given message. Recently, Drijvers et al. (S&P'19) showed that all thus far proposed two-round multi-signature schemes in the DL setting (without pairings) are insecure under concurrent sessions, i.e., if a single signer participates in multiple signing sessions concurrently. While Drijvers et al. improve the situation by constructing a secure two-round scheme, saving a round comes with the price of having less compact signatures. In particular, the signatures produced by their scheme are more than twice as large as Schnorr signatures, which arguably are the most natural and compact among all practical DL signatures and are therefore becoming popular in cryptographic applications (e.g., support for Schnorr signature verification has been proposed to be included in Bitcoin). If one needs a multi-signature scheme that can be used as a drop-in replacement for Schnorr signatures, then one is either forced to resort to a three-round scheme such as MuSig (Maxwell et al., DCC 2019) or MSDL-pop (Boneh, Drijvers, and Neven, ASIACRYPT 2018), or to accept that signing sessions are only secure when run sequentially, which may be hard to enforce in practice, e.g., when the same signing key is used by multiple devices.

In this work, we propose MuSig2, a novel and simple two-round multi-signature scheme variant of the MuSig scheme. Our scheme is the first multi-signature scheme that simultaneously i) is secure under concurrent signing sessions, ii) supports key aggregation, iii) outputs ordinary Schnorr signatures, iv) needs only two communication rounds, and v) has similar signer complexity as regular Schnorr signatures. Furthermore, our scheme is the first multi-signature scheme in the DL setting that supports preprocessing of all but one rounds, effectively enabling a non-interactive signing process, without forgoing security under concurrent sessions. The combination of all these features makes MuSig2 highly practical. We prove the security of MuSig2 under the one-more discrete logarithm (OMDL) assumption in the random oracle model, and the security of a more efficient variant in the combination of the random oracle and algebraic group models.

https://eprint.iacr.org/2020/1261
2  Bitcoin / Bitcoin Discussion / Bitcoin Core 0.20.1 Released on: August 01, 2020, 04:18:25 PM
0.20.1 Release Notes

Bitcoin Core version 0.20.1 is now available from:

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

This minor release includes various bug fixes 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 in some cases), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac)
or bitcoind/bitcoin-qt (on Linux).

Upgrading directly from a version of Bitcoin Core that has reached its EOL is
possible, but it might take some time if the data directory needs to be migrated. Old
wallet versions of Bitcoin Core are generally supported.

Compatibility

Bitcoin Core is supported and extensively tested on operating systems
using the Linux kernel, macOS 10.12+, and Windows 7 and newer.  Bitcoin
Core should also work on most other Unix-like systems but is not as
frequently tested on them.  It is not recommended to use Bitcoin Core on
unsupported systems.

From Bitcoin Core 0.20.0 onwards, macOS versions earlier than 10.12 are no
longer supported. Additionally, Bitcoin Core does not yet change appearance
when macOS "dark mode" is activated.

Known Bugs

The process for generating the source code release ("tarball") has changed in an
effort to make it more complete, however, there are a few regressions in
this release:
  • The generated configure script is currently missing, and you will need to
      install autotools and run ./autogen.sh before you can run
      ./configure. This is the same as when checking out from git.
  • Instead of running make simply, you should instead run
      BITCOIN_GENBUILD_NO_GIT=1 make.

Notable changes

Changes regarding misbehaving peers

Peers that misbehave (e.g. send us invalid blocks) are now referred to as
discouraged nodes in log output, as they're not (and weren't) strictly banned:
incoming connections are still allowed from them, but they're preferred for
eviction.

Furthermore, a few additional changes are introduced to how discouraged
addresses are treated:
  • Discouraging an address does not time out automatically after 24 hours
      (or the -bantime setting). Depending on traffic from other peers,
      discouragement may time out at an indeterminate time.
  • Discouragement is not persisted over restarts.
  • There is no method to list discouraged addresses. They are not returned by
      the listbanned RPC. That RPC also no longer reports the ban_reason
      field, as "manually added" is the only remaining option.
  • Discouragement cannot be removed with the setban remove RPC command.
      If you need to remove a discouragement, you can remove all discouragements by
      stop-starting your node.

Notification changes

-walletnotify notifications are now sent for wallet transactions that are
removed from the mempool because they conflict with a new block. These
notifications were sent previously before the v0.19 release, but had been
broken since that release (bug
[#18325](https://github.com/bitcoin/bitcoin/pull/18325)).

PSBT changes

PSBTs will contain both the non-witness utxo and the witness utxo for segwit
inputs in order to restore compatibility with wallet software that are now
requiring the full previous transaction for segwit inputs. The witness utxo
is still provided to maintain compatibility with software which relied on its
existence to determine whether an input was segwit.

0.20.1 change log

Mining
  • #19019 Fix GBT: Restore "!segwit" and "csv" to "rules" key (luke-jr)

P2P protocol and network code
  • #19219 Replace automatic bans with discouragement filter (sipa)

Wallet
  • #19300 Handle concurrent wallet loading (promag)
  • #18982 Minimal fix to restore conflicted transaction notifications (ryanofsky)

RPC and other APIs
  • #19524 Increment input value sum only once per UTXO in decodepsbt (fanquake)
  • #19517 psbt: Increment input value sum only once per UTXO in decodepsbt (achow101)
  • #19215 psbt: Include and allow both non_witness_utxo and witness_utxo for segwit inputs (achow101)

GUI
  • #19097 Add missing QPainterPath include (achow101)
  • #19059 update Qt base translations for macOS release (fanquake)

Build system
  • #19152 improve build OS configure output (skmcontrib)
  • #19536 qt, build: Fix QFileDialog for static builds (hebasto)

Tests and QA
  • #19444 Remove cached directories and associated script blocks from appveyor config (sipsorcery)
  • #18640 appveyor: Remove clcache (MarcoFalke)

Miscellaneous
  • #19194 util: Don't reference errno when pthread fails (miztake)
  • #18700 Fix locking on WSL using flock instead of fcntl (meshcollider)

Credits

Thanks to everyone who directly contributed to this release:
  • Aaron Clauson
  • Andrew Chow
  • fanquake
  • Hennadii Stepanov
  • Joćo Barbosa
  • Luke Dashjr
  • MarcoFalke
  • MIZUTA Takeshi
  • Pieter Wuille
  • Russell Yanofsky
  • sachinkm77
  • Samuel Dobson
  • Wladimir J. van der Laan

As well as to everyone that helped with translations on
Transifex.
3  Bitcoin / Bitcoin Discussion / Bitcoin Core 0.20.0 Released on: June 03, 2020, 04:19:36 PM
0.20.0 Release Notes

Bitcoin Core version 0.20.0 is now available from:

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

This release includes new features, various bug fixes 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 in some cases), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac)
or bitcoind/bitcoin-qt (on Linux).

Upgrading directly from a version of Bitcoin Core that has reached its EOL is
possible, but it might take some time if the data directory needs to be migrated. Old
wallet versions of Bitcoin Core are generally supported.

Compatibility

Bitcoin Core is supported and extensively tested on operating systems
using the Linux kernel, macOS 10.12+, and Windows 7 and newer.  Bitcoin
Core should also work on most other Unix-like systems but is not as
frequently tested on them.  It is not recommended to use Bitcoin Core on
unsupported systems.

From Bitcoin Core 0.20.0 onwards, macOS versions earlier than 10.12 are no
longer supported. Additionally, Bitcoin Core does not yet change appearance
when macOS "dark mode" is activated.

Known Bugs

The process for generating the source code release ("tarball") has changed in an
effort to make it more complete, however, there are a few regressions in
this release:
  • The generated configure script is currently missing, and you will need to
      install autotools and run ./autogen.sh before you can run
      ./configure. This is the same as when checking out from git.
  • Instead of running make simply, you should instead run
      BITCOIN_GENBUILD_NO_GIT=1 make.

Notable changes

P2P and network changes
Removal of BIP61 reject network messages from Bitcoin Core

The -enablebip61 command line option to enable BIP61 has been removed.
(#17004)

This feature has been disabled by default since Bitcoin Core version 0.18.0.
Nodes on the network can not generally be trusted to send valid messages
(including reject messages), so this should only ever be used when
connected to a trusted node.  Please use the alternatives recommended
below if you rely on this removed feature:
  • Testing or debugging of implementations of the Bitcoin P2P network protocol
      should be done by inspecting the log messages that are produced by a recent
      version of Bitcoin Core. Bitcoin Core logs debug messages
      (-debug=<category>) to a stream (-printtoconsole) or to a file
      (-debuglogfile=<debug.log>).
  • Testing the validity of a block can be achieved by specific RPCs:
  • submitblock
  • getblocktemplate with 'mode' set to 'proposal' for blocks with
        potentially invalid POW
  • Testing the validity of a transaction can be achieved by specific RPCs:
  • sendrawtransaction
  • testmempoolaccept
  • Wallets should not assume a transaction has propagated to the network
      just because there are no reject messages.  Instead, listen for the
      transaction to be announced by other peers on the network.  Wallets
      should not assume a lack of reject messages means a transaction pays
      an appropriate fee.  Instead, set fees using fee estimation and use
      replace-by-fee to increase a transaction's fee if it hasn't confirmed
      within the desired amount of time.

The removal of BIP61 reject message support also has the following minor RPC
and logging implications:
  • testmempoolaccept and sendrawtransaction no longer return the P2P reject
      code when a transaction is not accepted to the mempool. They still return the
      verbal reject reason.
  • Log messages that previously reported the reject code when a transaction was
      not accepted to the mempool now no longer report the reject code. The reason
      for rejection is still reported.

Updated RPCs
  • The RPCs which accept descriptors now accept the new sortedmulti(...) descriptor
      type which supports multisig scripts where the public keys are sorted
      lexicographically in the resulting script.  (#17056)
  • The walletprocesspsbt and walletcreatefundedpsbt RPCs now include
      BIP32 derivation paths by default for public keys if we know them.
      This can be disabled by setting the bip32derivs parameter to
      false.  (#17264)
  • The bumpfee RPC's parameter totalFee, which was deprecated in
      0.19, has been removed.  (#18312)
  • The bumpfee RPC will return a PSBT when used with wallets that have
      private keys disabled.  (#16373)
  • The getpeerinfo RPC now includes a mapped_as field to indicate the
      mapped Autonomous System used for diversifying peer selection. See the
      -asmap configuration option described below in <em>New Settings</em>.  (#16702)
  • The createmultisig and addmultisigaddress RPCs now return an
      output script descriptor for the newly created address.  (#18032)

Build System
  • OpenSSL is no longer used by Bitcoin Core.  (#17265)
  • BIP70 support has been fully removed from Bitcoin Core. The
      --enable-bip70 option remains, but it will throw an error during configure.
      (#17165)
  • glibc 2.17 or greater is now required to run the release binaries. This
      retains compatibility with RHEL 7, CentOS 7, Debian 8 and Ubuntu 14.04 LTS. (#17538)
  • The source code archives that are provided with gitian builds no longer contain
      any autotools artifacts. Therefore, to build from such source, a user
      should run the ./autogen.sh script from the root of the unpacked archive.
      This implies that autotools and other required packages are installed on the
      user's system. (#18331)

New settings
  • New rpcwhitelist and rpcwhitelistdefault configuration parameters
      allow giving certain RPC users permissions to only some RPC calls.
      (#12763)
  • A new -asmap configuration option has been added to diversify the
      node's network connections by mapping IP addresses Autonomous System
      Numbers (ASNs) and then limiting the number of connections made to any
      single ASN.  See issue  #16599,
      PR #16702, and the
      bitcoind help for more information.  This option is experimental and
      subject to removal or breaking changes in future releases, so the
      legacy /16 prefix mapping of IP addresses remains the default.  (#16702)

Updated settings
  • All custom settings configured when Bitcoin Core starts are now
      written to the debug.log file to assist troubleshooting.  (#16115)
  • Importing blocks upon startup via the bootstrap.dat file no longer
      occurs by default. The file must now be specified with
      -loadblock=<file>.  (#17044)
  • The -debug=db logging category has been renamed to
      -debug=walletdb to distinguish it from coindb.  The -debug=db
      option has been deprecated and will be removed in the next major
      release.  (#17410)
  • The -walletnotify configuration parameter will now replace any %w
      in its argument with the name of the wallet generating the
      notification.  This is not supported on Windows. (#13339)

Removed settings
  • The -whitelistforcerelay configuration parameter has been removed after
      it was discovered that it was rendered ineffective in version 0.13 and
      hasn't actually been supported for almost four years.  (#17985)

GUI changes
  • The "Start Bitcoin Core on system login" option has been removed on macOS.
      (#17567)
  • In the Peers window, the details for a peer now displays a Mapped AS
      field to indicate the mapped Autonomous System used for diversifying
      peer selection. See the -asmap configuration option in <em>New
      Settings</em>, above.  (#18402)
  • A "known bug" announced
      in the release notes of version 0.18 has been fixed.  The issue
      affected anyone who simultaneously used multiple Bitcoin Core wallets
      and the GUI coin control feature. (#18894)
  • For watch-only wallets, creating a new transaction in the Send screen
      or fee bumping an existing transaction in the Transactions screen will
      automatically copy a Partially-Signed Bitcoin Transaction (PSBT) to
      the system clipboard.  This can then be pasted into an external
      program such as HWI for
      signing.  Future versions of Bitcoin Core should support a GUI option
      for finalizing and broadcasting PSBTs, but for now the debug console
      may be used with the finalizepsbt and sendrawtransaction RPCs.
      (#16944, #17492)

Wallet
  • The wallet now by default uses bech32 addresses when using RPC, and
      creates native segwit change outputs.  (#16884)
  • The way that output trust was computed has been fixed, which affects
      confirmed/unconfirmed balance status and coin selection.  (#16766)
  • The gettransaction, listtransactions and listsinceblock RPC
      responses now also include the height of the block that contains the
      wallet transaction, if any.  (#17437)
  • The getaddressinfo RPC has had its label field deprecated
      (re-enable for this release using the configuration parameter
      -deprecatedrpc=label).  The labels field is altered from returning
      JSON objects to returning a JSON array of label names (re-enable
      previous behavior for this release using the configuration parameter
      -deprecatedrpc=labelspurpose).  Backwards compatibility using the
      deprecated configuration parameters is expected to be dropped in the
      0.21 release.  (#17585, #17578)

Documentation changes

Low-level changes

Utilities
  • The bitcoin-cli utility used with the -getinfo parameter now
      returns a headers field with the number of downloaded block headers
      on the best headers chain (similar to the blocks field that is also
      returned) and a verificationprogress field that estimates how much
      of the best block chain has been synced by the local node.  The
      information returned no longer includes the protocolversion,
      walletversion, and keypoololdest fields.  (#17302, #17650)
  • The bitcoin-cli utility now accepts a -stdinwalletpassphrase
      parameter that can be used when calling the walletpassphrase and
      walletpassphrasechange RPCs to read the passphrase from standard
      input without echoing it to the terminal, improving security against
      anyone who can look at your screen.  The existing -stdinrpcpass
      parameter is also updated to not echo the passphrase. (#13716)

Command line
  • Command line options prefixed with main/test/regtest network names like
      -main.port=8333 -test.server=1 previously were allowed but ignored. Now
      they trigger "Invalid parameter" errors on startup. (#17482)

New RPCs
  • The dumptxoutset RPC outputs a serialized snapshot of the current
      UTXO set.  A script is provided in the contrib/devtools directory
      for generating a snapshot of the UTXO set at a particular block
      height.  (#16899)
  • The generatetodescriptor RPC allows testers using regtest mode to
      generate blocks that pay an arbitrary output script descriptor.
      (#16943)

Updated RPCs
  • The verifychain RPC default values are now static instead of
      depending on the command line options or configuration file
      (-checklevel, and -checkblocks). Users can pass in the RPC
      arguments explicitly when they don't want to rely on the default
      values. (#18541)
  • The getblockchaininfo RPC's verificationprogress field will no
      longer report values higher than 1.  Previously it would occasionally
      report the chain was more than 100% verified.  (#17328)

Tests
  • It is now an error to use an unqualified walletdir=path setting in
      the config file if running on testnet or regtest networks. The setting
      now needs to be qualified as chain.walletdir=path or placed in the
      appropriate [chain] section. (#17447)
  • -fallbackfee was 0 (disabled) by default for the main chain, but
      0.0002 by default for the test chains. Now it is 0 by default for all
      chains. Testnet and regtest users will have to add
      fallbackfee=0.0002 to their configuration if they weren't setting it
      and they want it to keep working like before. (#16524)

Build system
  • Support is provided for building with the Android Native Development
      Kit (NDK).  (#16110)



Code:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

081b30b0f1af95656242c83eef30bbf7216b1a30fa8e8f29b3b160fe520d28f6  bitcoin-0.20.0-aarch64-linux-gnu.tar.gz
05014c7ff00f4496b1f389f0961d807e04505d8721d5c6f69567f2a0ec1985cc  bitcoin-0.20.0-arm-linux-gnueabihf.tar.gz
34f377fee2c7adf59981dde7e41215765d47b466f773cf2673137d30495b2675  bitcoin-0.20.0-osx64.tar.gz
a6e44b928d9ac04f11d43e920f4971fbdf1e77a8c28f7c14fafdd741ca7bc99f  bitcoin-0.20.0-osx.dmg
5b9cae3aa4197d1e557ff236754f489bce877ebba2267ce33af79b2ca4a13af6  bitcoin-0.20.0-riscv64-linux-gnu.tar.gz
ec5a2358ee868d845115dc4fc3ed631ff063c57d5e0a713562d083c5c45efb28  bitcoin-0.20.0.tar.gz
0f1ea61a9aa9aba383a43bcdb5755b072cfff016b9c6bb0afa772a8685bcf7b0  bitcoin-0.20.0-win64-setup.exe
3e9ddfa05b7967e43fb502b735b6c4d716ec06f63ab7183df2e006ed4a6a431f  bitcoin-0.20.0-win64.zip
35ec10f87b6bc1e44fd9cd1157e5dfa483eaf14d7d9a9c274774539e7824c427  bitcoin-0.20.0-x86_64-linux-gnu.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJe13SYAAoJEJDIAZ42wulkYrwQAIcbo6TAtb0AZkyC4ewM7+80
nQZTx7d0w9ljdr/0Wt9B/2F6BNhiW2TR1n+tYZ//Juk+kH79qQSVwsBSSdMpQJOR
7hlivCHUx5fwJEhtP7mEtuMnu/9o1YOX5lahPV3Yjfv8l3zdec6Dwlf6OAsPX8Dc
PAiWfhu/UplQnnI1U47LctwqTD6F5ywYunQ4U7S6Qfd8jqvQUTT7JQ68au1P1oHM
29/FCc9Qx7KbSVDgRWe9cjok7R6XRal1rQUz/4HW9OClRDUAsQym0Kxf3OzJVgJi
5hUq666Ld/rh7jQVjlMkSK8vrQn6VaNKk15q8TM238kRwj932zeZn9swkPaNf6ml
+pKFu7HxZhYpACa97vlHwEais4e/mVanTI5MBtt2POTT5ffkSD3isTfkiPHgYV3D
rTo4pmhAcFiOkXWcuNe5yWV2zZFkwy0gRgL/aNwHc3jnuv3foMkgS4SApL1/RnUs
hFf/Ce299c7WQa73tupHUJI0PrTggvvQHniGEZdomlFxaEzcTbOIW3Ao5IizZ5Yw
Aaum8n5/lRQgUMOQgF6EeWxEMKoqCA3wZITZ6mqoJBega52o3anZam5Lu+UKqhLV
a7May7n6L4acZkeJLKeJ4cMSsQYQ45Cc3dQJTmEmNicL9ix/crig38mKGLi7Sj6T
s3iI+NZb2h7g7gYg93MF
=e/wL
-----END PGP SIGNATURE-----
4  Bitcoin / Bitcoin Discussion / Bitcoin Core 0.19.1 Released on: March 10, 2020, 04:13:58 PM

0.19.1 Release Notes

Bitcoin Core version 0.19.1 is now available from:

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

This minor release includes various bug fixes 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).

Upgrading directly from a version of Bitcoin Core that has reached its EOL is
possible, but it might take some time if the datadir needs to be migrated. Old
wallet versions of Bitcoin Core are generally supported.

Compatibility

Bitcoin Core is supported and extensively tested on operating systems using
the Linux kernel, macOS 10.10+, and Windows 7 and newer. It is not recommended
to use Bitcoin Core on unsupported systems.

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

From Bitcoin Core 0.17.0 onwards, macOS versions earlier than 10.10 are no
longer supported, as Bitcoin Core is now built using Qt 5.9.x which requires
macOS 10.10+. Additionally, Bitcoin Core does not yet change appearance when
macOS "dark mode" is activated.

In addition to previously supported CPU platforms, this release's pre-compiled
distribution provides binaries for the RISC-V platform.

0.19.1 change log

Wallet
  • #17643 Fix origfee return for bumpfee with feerate arg (instagibbs)
  • #16963 Fix unique_ptr usage in boost::signals2 (promag)
  • #17258 Fix issue with conflicted mempool tx in listsinceblock (adamjonas, mchrostowski)
  • #17924 Bug: IsUsedDestination shouldn't use key id as script id for ScriptHash (instagibbs)
  • #17621 IsUsedDestination should count any known single-key address (instagibbs)
  • #17843 Reset reused transactions cache (fjahr)

RPC and other APIs
  • #17687 cli: Fix fatal leveldb error when specifying -blockfilterindex=basic twice (brakmic)
  • #17728 require second argument only for scantxoutset start action (achow101)
  • #17445 zmq: Fix due to invalid argument and multiple notifiers (promag)
  • #17524 psbt: handle unspendable psbts (achow101)
  • #17156 psbt: check that various indexes and amounts are within bounds (achow101)

GUI
  • #17427 Fix missing qRegisterMetaType for size_t (hebasto)
  • #17695 disable File->CreateWallet during startup (fanquake)
  • #17634 Fix comparison function signature (hebasto)
  • #18062 Fix unintialized WalletView::progressDialog (promag)

Tests and QA
  • #17416 Appveyor improvement - text file for vcpkg package list (sipsorcery)
  • #17488 fix "bitcoind already running" warnings on macOS (fanquake)
  • #17980 add missing #include to fix compiler errors (kallewoof)

Platform support
  • #17736 Update msvc build for Visual Studio 2019 v16.4 (sipsorcery)
  • #17364 Updates to appveyor config for VS2019 and Qt5.9.8 + msvc project fixes (sipsorcery)
  • #17887 bug-fix macos: give free bytes to F_PREALLOCATE (kallewoof)

Miscellaneous
  • #17897 init: Stop indexes on shutdown after ChainStateFlushed callback (jimpo)
  • #17450 util: Add missing headers to util/fees.cpp (hebasto)
  • #17654 Unbreak build with Boost 1.72.0 (jbeich)
  • #17857 scripts: Fix symbol-check &amp; security-check argument passing (fanquake)
  • #17762 Log to net category for exceptions in ProcessMessages (laanwj)
  • #18100 Update univalue subtree (MarcoFalke)

Credits

Thanks to everyone who directly contributed to this release:
  • Aaron Clauson
  • Adam Jonas
  • Andrew Chow
  • Fabian Jahr
  • fanquake
  • Gregory Sanders
  • Harris
  • Hennadii Stepanov
  • Jan Beich
  • Jim Posen
  • Joćo Barbosa
  • Karl-Johan Alm
  • Luke Dashjr
  • MarcoFalke
  • Michael Chrostowski
  • Russell Yanofsky
  • Wladimir J. van der Laan

As well as to everyone that helped with translations on
Transifex.



Code:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

3a80431717842672df682bdb619e66523b59541483297772a7969413be3502ff  bitcoin-0.19.1-aarch64-linux-gnu.tar.gz
657f28213823d240dd3324d14829702f9ad6f0710f8bdd1c379cb3c447197f48  bitcoin-0.19.1-arm-linux-gnueabihf.tar.gz
10d1e53208aa7603022f4acc084a046299ab4ccf25fe01e81b3fb6f856772589  bitcoin-0.19.1-i686-pc-linux-gnu.tar.gz
1ae1b87de26487075cd2fd22e0d4ead87d969bd55c44f2f1d873ecdc6147ebb3  bitcoin-0.19.1-osx64.tar.gz
206d8d92189d22e735393abebeb7a2e7237a119dd448b4a40df8c357da1287b2  bitcoin-0.19.1-osx.dmg
aa7a9563b48aa79252c8e7b6a41c07a5441bd9f14c5e4562cc72720ea6cb0ee5  bitcoin-0.19.1-riscv64-linux-gnu.tar.gz
f2591d555b8e8c2e1bd780e40d53a91e165d8b3c7e0391ae2d24a0c0f23a7cc0  bitcoin-0.19.1.tar.gz
69e4d7f710a29be6ead2ef5da2905736b7cea107213ae6ddde3bcca8affbb8fd  bitcoin-0.19.1-win64-setup.exe
56323ec91afecd8e321a2925c0ca5f1da8b2ae1c99f4e08a3652e1dc68908717  bitcoin-0.19.1-win64.zip
5fcac9416e486d4960e1a946145566350ca670f9aaba99de6542080851122e4c  bitcoin-0.19.1-x86_64-linux-gnu.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJeZiE8AAoJEJDIAZ42wulkkQsQAIlvZ9Em4wm2jpn4L7QUJgCE
4Mr6Q/tCPMs4U15q4wkjoBbdP06Bts1DzV0m/qoirTKoTKCCyRwdaeRn+Oj5Kkoh
MuyPt9EEsrnNk80xaPXSpYnhYjqSGrKux+IuHrlZtCy0QEoeIiOVaWWEtEe6I/eU
lvooE8ywxcUvsOwU3Kga0WnCA0WsfwduMAU+LvmtiXgjudsWvoERwHav+eiQva60
kgfwK5W+XI0lt7clFw6zPXBTZeWWhc97fp1uKv7KBPpACHWgKUaXP3WPMHZhsnSF
1L5fi5EcafjNzbbUusmgo807xThM5eMFZQpzHFZhiFNngW6mjxyEo1m2vrvVE8mN
1LZ7h1QahdSUVsgr+w/JkN1Wx9WcJyzGvFuH7dIbe1J6kb5IMyUKESEtTkWgJeo4
5MCk9pwvstAXcXPnWbNolrBo2IB9mrFC9o/9n2ZCyncCofre8BmbIsvxVqBu4hfE
9E4rCTHDGwWvCDYY68iWdlnyUl9FAvYB8UEOYs4o4f1fDMLdbOEqDojIa7ZnOJwV
oPth/MJxHcaCHNTAk7981LbOyn/oJMMzly4br5WFqWbdgzdXUSBTZDoeT26gdX8P
rnCo7JMvaxcvE8AASD9OpegKZP/E5TnHEzcgkVncABj9gVrsuOm7DlTFsE9YuRv+
jerPsU4Izg+hoVdUiuPT
=Iefa
-----END PGP SIGNATURE-----
5  Bitcoin / Bitcoin Technical Support / MOVED: serious problem electrum on: December 31, 2019, 12:18:21 AM
This topic has been moved to Trashcan.

Duplicate
6  Bitcoin / Bitcoin Discussion / Bitcoin Core 0.19.0.1 Released on: November 24, 2019, 05:04:58 PM
Note: A bug was found after 0.19.0 was tagged, so it was not released. 0.19.0.1 contains the bug fix as well as everything 0.19.0 has. It is the 0.19  major release.


Bitcoin Core version 0.19.0.1 is now available from:

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

or through BitTorrent:

  magnet:?xt=urn:btih:436859e8dddf4d8bd22d9ecc826139b6749a9a4a&dn=bitcoin-core-0.19.0.1&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969%2Fannounce&tr=udp%3A%2F%2Fexplodie.org%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.torrent.eu.org%3A451%2Fannounce&tr=udp%3A%2F%2Ftracker.bitcoin.sprovoost.nl%3A6969

This release includes new features, various bug fixes 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).

Upgrading directly from a version of Bitcoin Core that has reached its EOL is
possible, but might take some time if the datadir needs to be migrated.  Old
wallet versions of Bitcoin Core are generally supported.

Compatibility

Bitcoin Core is supported and extensively tested on operating systems using
the Linux kernel, macOS 10.10+, and Windows 7 and newer. It is not recommended
to use Bitcoin Core on unsupported systems.

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

From 0.17.0 onwards, macOS &lt;10.10 is no longer supported. 0.17.0 is
built using Qt 5.9.x, which doesn't support versions of macOS older than
10.10. Additionally, Bitcoin Core does not yet change appearance when
macOS "dark mode" is activated.

Users running macOS Catalina may need to "right-click" and then choose "Open"
to open the Bitcoin Core .dmg. This is due to new signing requirements
imposed by Apple, which the Bitcoin Core project does not yet adhere too.

Notable changes

New user documentation
  • Reduce memory
      suggests configuration tweaks for running Bitcoin Core on systems with
      limited memory. (#16339)

New RPCs
  • getbalances returns an object with all balances (mine,
    untrusted_pending and immature). Please refer to the RPC help of
    getbalances for details. The new RPC is intended to replace
    getbalance, getunconfirmedbalance, and the balance fields in
    getwalletinfo.  These old calls and fields may be removed in a
      future version. (#15930, #16239)
  • setwalletflag sets and unsets wallet flags that enable or disable
      features specific to that existing wallet, such as the new
    avoid_reuse feature documented elsewhere in these release notes.
      (#13756)
  • getblockfilter gets the BIP158 filter for the specified block.  This
      RPC is only enabled if block filters have been created using the
    -blockfilterindex configuration option. (#14121)

New settings
  • -blockfilterindex enables the creation of BIP158 block filters for
      the entire blockchain.  Filters will be created in the background and
      currently use about 4 GiB of space.  Note: this version of Bitcoin
      Core does not serve block filters over the P2P network, although the
      local user may obtain block filters using the getblockfilter RPC.
      (#14121)

Updated settings
  • whitebind and whitelist now accept a list of permissions to
      provide peers connecting using the indicated interfaces or IP
      addresses.  If no permissions are specified with an address or CIDR
      network, the implicit default permissions are the same as previous
      releases.  See the bitcoind -help output for these two options for
      details about the available permissions. (#16248)
  • Users setting custom dbcache values can increase their setting slightly
      without using any more real memory.  Recent changes reduced the memory use
      by about 9% and made chainstate accounting more accurate (it was underestimating
      the use of memory before).  For example, if you set a value of "450" before, you
      may now set a value of "500" to use about the same real amount of memory. (#16957)

Updated RPCs

Note: some low-level RPC changes mainly useful for testing are described in the
Low-level Changes section below.
  • sendmany no longer has a minconf argument.  This argument was not
      well-specified and would lead to RPC errors even when the wallet's
      coin selection succeeded.  Users who want to influence coin selection
      can use the existing -spendzeroconfchange, -limitancestorcount,
    -limitdescendantcount and -walletrejectlongchains configuration
      arguments. (#15596)
  • getbalance and sendtoaddress, plus the new RPCs getbalances and
    createwallet, now accept an "avoid_reuse" parameter that controls
      whether already used addresses should be included in the operation.
      Additionally, sendtoaddress will avoid partial spends when
    avoid_reuse is enabled even if this feature is not already enabled
      via the -avoidpartialspends command line flag because not doing so
      would risk using up the "wrong" UTXO for an address reuse case.
      (#13756)
  • RPCs which have an include_watchonly argument or includeWatching option now default to true for watch-only
      wallets. Affected RPCs are: getbalance, listreceivedbyaddress, listreceivedbylabel, listtransactions,
    listsinceblock, gettransaction, walletcreatefundedpsbt, and fundrawtransaction. (#16383)
  • listunspent now returns a "reused" bool for each output if the
      wallet flag "avoid_reuse" is enabled. (#13756)
  • getblockstats now uses BlockUndo data instead of the transaction
      index, making it much faster, no longer dependent on the -txindex
      configuration option, and functional for all non-pruned blocks.
      (#14802)
  • utxoupdatepsbt now accepts a descriptors parameter that will fill
      out input and output scripts and keys when known. P2SH-witness inputs
      will be filled in from the UTXO set when a descriptor is provided that
      shows they're spending segwit outputs.  See the RPC help text for full
      details. (#15427)
  • sendrawtransaction and testmempoolaccept no longer accept a
    allowhighfees parameter to fail mempool acceptance if the
      transaction fee exceeds the value of the configuration option
    -maxtxfee.  Now there is a hardcoded default maximum feerate that
      can be changed when calling either RPC using a maxfeerate parameter.
      (#15620)
  • getmempoolancestors, getmempooldescendants, getmempoolentry, and
    getrawmempool no longer return a size field unless the
      configuration option -deprecatedrpc=size is used.  Instead a new
    vsize field is returned with the transaction's virtual size
      (consistent with other RPCs such as getrawtransaction). (#15637)
  • getwalletinfo now includes a scanning field that is either false
      (no scanning) or an object with information about the duration and
      progress of the wallet's scanning historical blocks for transactions
      affecting its balances. (#15730)
  • gettransaction now accepts a third (boolean) argument verbose. If
      set to true, a new decoded field will be added to the response containing
      the decoded transaction. This field is equivalent to RPC decoderawtransaction,
      or RPC getrawtransaction when verbose is passed. (#16185, #16866, #16873)
  • createwallet accepts a new passphrase parameter.  If set, this
      will create the new wallet encrypted with the given passphrase.  If
      unset (the default) or set to an empty string, no encryption will be
      used. (#16394)
  • getchaintxstats RPC now returns the additional key of
    window_final_block_height. (#16695)
  • getmempoolentry now provides a weight field containing the
      transaction weight as defined in BIP141. (#16647)
  • The getnetworkinfo and getpeerinfo commands now contain a new field with decoded network service flags. (#16786)
  • getdescriptorinfo now returns an additional checksum field
      containing the checksum for the unmodified descriptor provided by the
      user (that is, before the descriptor is normalized for the
    descriptor field). (#15986)
  • joinpsbts now shuffles the order of the inputs and outputs of the resulting
      joined PSBT. Previously, inputs and outputs were added in the order PSBTs were
      provided. This made it easy to correlate inputs to outputs, representing a
      privacy leak. (#16512)
  • walletcreatefundedpsbt now signals BIP125 Replace-by-Fee if the
    -walletrbf configuration option is set to true. (#15911)

GUI changes
  • The GUI wallet now provides bech32 addresses by default.  The user may change the address type
      during invoice generation using a GUI toggle, or the default address
      type may be changed with the -addresstype configuration option.
      (#15711, #16497)
  • In 0.18.0, a ./configure flag was introduced to allow disabling BIP70 support in the GUI (support was enabled by default). In 0.19.0, this flag is now <strong>disabled</strong> by default. If you want to compile Bitcoin Core with BIP70 support in the GUI, you can pass --enable-bip70 to ./configure. (#15584)

Deprecated or removed configuration options
  • -mempoolreplacement is removed, although default node behavior
      remains the same.  This option previously allowed the user to prevent
      the node from accepting or relaying BIP125 transaction replacements.
      This is different from the remaining configuration option
    -walletrbf. (#16171)

Deprecated or removed RPCs
  • bumpfee no longer accepts a totalFee option unless the
      configuration parameter deprecatedrpc=totalFee is specified.  This
      parameter will be fully removed in a subsequent release. (#15996)
  • bumpfee has a new fee_rate option as a replacement for the deprecated totalFee. (#16727)
  • generate is now removed after being deprecated in Bitcoin Core 0.18.
      Use the generatetoaddress RPC instead. (#15492)

P2P changes
  • BIP 61 reject messages were deprecated in v0.18. They are now disabled
      by default, but can be enabled by setting the -enablebip61 command
      line option.  BIP 61 reject messages will be removed entirely in a
      future version of Bitcoin Core. (#14054)
  • To eliminate well-known denial-of-service vectors in Bitcoin Core,
      especially for nodes with spinning disks, the default value for the
    -peerbloomfilters configuration option has been changed to false.
      This prevents Bitcoin Core from sending the BIP111 NODE_BLOOM service
      flag, accepting BIP37 bloom filters, or serving merkle blocks or
      transactions matching a bloom filter.  Users who still want to provide
      bloom filter support may either set the configuration option to true
      to re-enable both BIP111 and BIP37 support or enable just BIP37
      support for specific peers using the updated -whitelist and
    -whitebind configuration options described elsewhere in these
      release notes.  For the near future, lightweight clients using public
      BIP111/BIP37 nodes should still be able to connect to older versions
      of Bitcoin Core and nodes that have manually enabled BIP37 support,
      but developers of such software should consider migrating to either
      using specific BIP37 nodes or an alternative transaction filtering
      system. (#16152)
  • By default, Bitcoin Core will now make two additional outbound connections that are exclusively used for block-relay.  No transactions or addr messages will be processed on these connections. These connections are designed to add little additional memory or bandwidth resource requirements but should make some partitioning attacks more difficult to carry out. (#15759)

Miscellaneous CLI Changes
  • The testnet field in bitcoin-cli -getinfo has been renamed to
    chain and now returns the current network name as defined in BIP70
      (main, test, regtest). (#15566)

Low-level changes

RPC
  • getblockchaininfo no longer returns a bip9_softforks object.
      Instead, information has been moved into the softforks object and
      an additional type field describes how Bitcoin Core determines
      whether that soft fork is active (e.g. BIP9 or BIP90).  See the RPC
      help for details. (#16060)
  • getblocktemplate no longer returns a rules array containing CSV
      and segwit (the BIP9 deployments that are currently in active
      state). (#16060)
  • getrpcinfo now returns a logpath field with the path to
    debug.log. (#15483)

Tests
  • The regression test chain enabled by the -regtest command line flag
      now requires transactions to not violate standard policy by default.
      This is the same default used for mainnet and makes it easier to test
      mainnet behavior on regtest. Note that the testnet still allows
      non-standard txs by default and that the policy can be locally
      adjusted with the -acceptnonstdtxn command line flag for both test
      chains. (#15891)

Configuration
  • A setting specified in the default section but not also specified in a
      network-specific section (e.g. testnet) will now produce an error
      preventing startup instead of just a warning unless the network is
      mainnet.  This prevents settings intended for mainnet from being
      applied to testnet or regtest. (#15629)
  • On platforms supporting thread_local, log lines can be prefixed with
      the name of the thread that caused the log. To enable this behavior,
      use -logthreadnames=1. (#15849)

Network
  • When fetching a transaction announced by multiple peers, previous versions of
      Bitcoin Core would sequentially attempt to download the transaction from each
      announcing peer until the transaction is received, in the order that those
      peers' announcements were received.  In this release, the download logic has
      changed to randomize the fetch order across peers and to prefer sending
      download requests to outbound peers over inbound peers. This fixes an issue
      where inbound peers could prevent a node from getting a transaction.
      (#14897, #15834)
  • If a Tor hidden service is being used, Bitcoin Core will be bound to
      the standard port 8333 even if a different port is configured for
      clearnet connections.  This prevents leaking node identity through use
      of identical non-default port numbers. (#15651)

Mempool and transaction relay
  • Allows one extra single-ancestor transaction per package.  Previously,
      if a transaction in the mempool had 25 descendants, or it and all of
      its descendants were over 101,000 vbytes, any newly-received
      transaction that was also a descendant would be ignored.  Now, one
      extra descendant will be allowed provided it is an immediate
      descendant (child) and the child's size is 10,000 vbytes or less.
      This makes it possible for two-party contract protocols such as
      Lightning Network to give each participant an output they can spend
      immediately for Child-Pays-For-Parent (CPFP) fee bumping without
      allowing one malicious participant to fill the entire package and thus
      prevent the other participant from spending their output. (#15681)
  • Transactions with outputs paying v1 to v16 witness versions (future
      segwit versions) are now accepted into the mempool, relayed, and
      mined.  Attempting to spend those outputs remains forbidden by policy
      ("non-standard").  When this change has been widely deployed, wallets
      and services can accept any valid bech32 Bitcoin address without
      concern that transactions paying future segwit versions will become
      stuck in an unconfirmed state. (#15846)
  • Legacy transactions (transactions with no segwit inputs) must now be
      sent using the legacy encoding format, enforcing the rule specified in
      BIP144.  (#14039)

Wallet
  • When in pruned mode, a rescan that was triggered by an importwallet,
    importpubkey, importaddress, or importprivkey RPC will only fail
      when blocks have been pruned. Previously it would fail when -prune
      has been set.  This change allows setting -prune to a high value
      (e.g. the disk size) without the calls to any of the import RPCs
      failing until the first block is pruned. (#15870)
  • When creating a transaction with a fee above -maxtxfee (default 0.1
      BTC), the RPC commands walletcreatefundedpsbt and
    fundrawtransaction will now fail instead of rounding down the fee.
      Be aware that the feeRate argument is specified in BTC per 1,000
      vbytes, not satoshi per vbyte. (#16257)
  • A new wallet flag avoid_reuse has been added (default off). When
      enabled, a wallet will distinguish between used and unused addresses,
      and default to not use the former in coin selection.  When setting
      this flag on an existing wallet, rescanning the blockchain is required
      to correctly mark previously used destinations.  Together with "avoid
      partial spends" (added in Bitcoin Core v0.17.0), this can eliminate a
      serious privacy issue where a malicious user can track spends by
      sending small payments to a previously-paid address that would then
      be included with unrelated inputs in future payments. (#13756)

Build system changes
  • Python &gt;=3.5 is now required by all aspects of the project. This
      includes the build systems, test framework and linters. The previously
      supported minimum (3.4), was EOL in March 2019. (#14954)
  • The minimum supported miniUPnPc API version is set to 10. This keeps
      compatibility with Ubuntu 16.04 LTS and Debian 8 libminiupnpc-dev
      packages. Please note, on Debian this package is still vulnerable to
    CVE-2017-8798
      (in jessie only) and
    CVE-2017-1000494
      (both in jessie and in stretch). (#15993)



Code:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

c258c6416225afb08c4396847eb3d5da61a124f1b5c61cccb5a2e903e453ce7f  bitcoin-0.19.0.1-aarch64-linux-gnu.tar.gz
c9335ab5286b66b3fd93be5cd21695885765cb2ffea2a90d92bf99b43f549787  bitcoin-0.19.0.1-arm-linux-gnueabihf.tar.gz
94d1b581dfd21dc64e5510c3b31d6592aed9d33851db5795fb549354f00b3e72  bitcoin-0.19.0.1-i686-pc-linux-gnu.tar.gz
a64e4174e400f3a389abd76f4d6b1853788730013ab1dedc0e64b0a0025a0923  bitcoin-0.19.0.1-osx64.tar.gz
1a8865ac84de9710633ad89b3f6b7c08281a0298d47e8ce7d4f5bb52f765f06e  bitcoin-0.19.0.1-osx.dmg
3e35dccc55b6de206a9c9b21c2d10fb79a184e817906bf75a6f47b57a3f1df66  bitcoin-0.19.0.1-riscv64-linux-gnu.tar.gz
7ac9f972249a0a16ed01352ca2a199a5448fe87a4ea74923404a40b4086de284  bitcoin-0.19.0.1.tar.gz
4abca9419e83581209a3654a33da504998cf2f470993ee6d71f6b47fefe631a0  bitcoin-0.19.0.1-win64-setup.exe
7706593de727d893e4b1e750dc296ea682ccee79acdd08bbc81eaacf3b3173cf  bitcoin-0.19.0.1-win64.zip
732cc96ae2e5e25603edf76b8c8af976fe518dd925f7e674710c6c8ee5189204  bitcoin-0.19.0.1-x86_64-linux-gnu.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJd2koCAAoJEJDIAZ42wulkZH0P/RJlDRXWxmu1A5McDqA1tW0h
tTZDYdE6kxYPySRHLcVtdVr1V9GLFLS9BHqogNGdN93IkTR4nfU6A8sd+MOyhUbk
HBTTkyq2Vz5DI9+tMrP20VABQYeG/+Yon5dS5J0LfYOgffH7NPTyUxWVK2QLuT7F
4mYmLVm8Rv4z/gFtWrJ15r8dqMcc2NsBY0wHwrstiUhUuhh8Ws+ZhVAaa1iULNww
IgJMm5lpJqKUt6MfyF6C6MgHkgdABxWDlS9ESbSZg7JIvCSgIwKvosPxPsk5wJkY
UauzhuiiBFmKUWGydZCDbwcuhNXRZkNuwViQBpQ6fCmcqgcTFIrbHEZCmPqEcHK3
USfeG+yz1FibN0toxA6Nl9thI8Jv3ffjc7w/tJ9VeYU1GkiOEaCe7zuhqrqmO/Id
ZLc5zmxwG7xjTh2PBh09FvB/AyOHwKSHfqvx0oNobSblgAidsXUScysTK218T8Dv
GQYdCbsyq/6qo5sYNAIPdRHZ7JS5pCXgkZ3FWPT4uPSAKw2zHwtiWO+1Ve96dTpa
nVmJ1KXwwERvwk3swOY7YCm9mPJadSyjk8/qZMyx/YMdyd2cGYBuxenZW3ZJEDWg
2IWj2szbl0Evr1fKtzNEDlrXO2Xqq9UrMzjyYIdhULW3WKvJoYVXahWdvF0Tqn+n
zRRgyGwFDvGTFN29pYM2
=4m4p
-----END PGP SIGNATURE-----
7  Bitcoin / Bitcoin Technical Support / MOVED: I was mining in 2009 on: October 31, 2019, 03:31:57 PM
This topic has been moved to Trashcan.

User requested deletion
8  Bitcoin / Bitcoin Technical Support / MOVED: Forgot your Bitcoin wallet password, who can help? on: October 26, 2019, 03:50:02 AM
This topic has been moved to Trashcan.

Malware links
9  Bitcoin / Development & Technical Discussion / Miniscript: Enabling Composition and Analysis of Bitcoin Script on: August 20, 2019, 04:49:19 AM
Hi all,

Miniscript is a project we've been working on for the past year or so,
and is now at a stage where I'd like to get it some more attention. It is joint
work with Andrew Poelstra and Sanket Sanjalkar.

It's a language for writing (a subset of) Bitcoin Scripts in a structured way,
enabling analysis, composition, generic signing and more.

For example the script

  <A> OP_CHECKSIG OP_IFDUP OP_NOTIF OP_DUP OP_HASH160 <hash160(B)>
  OP_EQUALVERIFY OP_CHECKSIGVERIFY <144> OP_CSV OP_ENDIF

in Miniscript notation would be

  or_d(c:pk(A),and_v(vc:pk_h(B),older(144)))

making it human (engineer?) readable that this is a script that permits A to
take the coins at any time, and B after 1 day. A full description of the
language can be found on the project website http://bitcoin.sipa.be/miniscript

Using Miniscript it's possible to:
* Write descriptors for addresses for scripts that implement things more
  complicated than multisig.
* Make software that can deal with composition of policies (e.g. have funds
  in a 2-of-3 setup where one of the 3 "keys" is itself a policy that involves
  perhaps multiple devices and timeouts).
* Compile complex spending policies to efficient scripts.
* Figure out under what necessary and/or sufficient conditions a script can be
  satisfied.
* Given signatures for a sufficient set of keys (and hash preimages, if needed),
  generically construct a witness for arbitrary scripts, without metadata
  apart from the script itself and public keys appearing in it. This means
  generic PSBT signers are possible for this class of scripts.
* Compute the bounds on the size of a witness for arbitrary scripts.
* Perform static analysis to see if any of Script's resource limitations
  (ops limit, stack size, ...) might interfere with the ability to spend.
* Who knows what else...

We have two implementations:
* a C++ one (https://github.com/sipa/miniscript)
* a Rust library (https://github.com/apoelstra/rust-miniscript).

The implementations are a work in progress, but through large scale randomized
tests we have confidence that the language design and associated witnesses are
compatible with the existing consensus and standardness rules.

To be clear: Miniscript is designed for Bitcoin as it exists today (primarily
P2WSH), and does not need any consensus changes. That said, we plan to extend
the design to support future script changes Bitcoin may include.

Cheers,

--
Pieter

Some more layman's explanation on twitter: https://twitter.com/pwuille/status/1163592166062473217

Website to play around with Miniscript: http://bitcoin.sipa.be/miniscript/
10  Bitcoin / Bitcoin Discussion / Bitcoin Core 0.18.1 Released on: August 09, 2019, 09:41:16 PM
Bitcoin Core version 0.18.1 is now available from:

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

Or through BitTorrent:

    magnet:?xt=urn:btih:c3ba0cfee3ef8413098ac5e81db08a2670e9da8c&dn=bitcoin-core-0.18.1&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Fzer0day.ch%3A1337&tr=udp%3A%2F%2Fexplodie.org%3A6969

This is a new minor version release, including new features, various bug
fixes 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 newer, 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.

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 or later. Upgrading directly from 0.7.x and earlier without
redownloading the blockchain is not supported.  However, as usual, old
wallet versions are still supported.

Compatibility

Bitcoin Core is supported and extensively tested on operating systems
using the Linux kernel, macOS 10.10+, and Windows 7 and newer. It is not
recommended to use Bitcoin Core on unsupported systems.

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

From 0.17.0 onwards, macOS &lt;10.10 is no longer supported. 0.17.0 is
built using Qt 5.9.x, which doesn't support versions of macOS older than
10.10. Additionally, Bitcoin Core does not yet change appearance when
macOS "dark mode" is activated.

Known issues

Wallet GUI

For advanced users who have both (1) enabled coin control features, and
(2) are using multiple wallets loaded at the same time: The coin control
input selection dialog can erroneously retain wrong-wallet state when
switching wallets using the dropdown menu. For now, it is recommended
not to use coin control features with multiple wallets loaded.

0.18.1 change log

P2P protocol and network code
  • #15990 Add tests and documentation for blocksonly (MarcoFalke)
  • #16021 Avoid logging transaction decode errors to stderr (MarcoFalke)
  • #16405 fix: tor: Call event_base_loopbreak from the event's callback (promag)
  • #16412 Make poll in InterruptibleRecv only filter for POLLIN events (tecnovert)

Wallet
  • #15913 Add -ignorepartialspends to list of ignored wallet options (luke-jr)

RPC and other APIs
  • #15991 Bugfix: fix pruneblockchain returned prune height (jonasschnelli)
  • #15899 Document iswitness flag and fix bug in converttopsbt (MarcoFalke)
  • #16026 Ensure that uncompressed public keys in a multisig always returns a legacy address (achow101)
  • #14039 Disallow extended encoding for non-witness transactions (sipa)
  • #16210 add 2nd arg to signrawtransactionwithkey examples (dooglus)
  • #16250 signrawtransactionwithkey: report error when missing redeemScript/witnessScript (ajtowns)

GUI
  • #16044 fix the bug of OPEN CONFIGURATION FILE on Mac (shannon1916)
  • #15957 Show "No wallets available" in open menu instead of nothing (meshcollider)
  • #16118 Enable open wallet menu on setWalletController (promag)
  • #16135 Set progressDialog to nullptr (promag)
  • #16231 Fix open wallet menu initialization order (promag)
  • #16254 Set AA_EnableHighDpiScaling attribute early (hebasto)
  • #16122 Enable console line edit on setClientModel (promag)
  • #16348 Assert QMetaObject::invokeMethod result (promag)

Build system
  • #15985 Add test for GCC bug 90348 (sipa)
  • #15947 Install bitcoin-wallet manpage (domob1812)
  • #15983 build with -fstack-reuse=none (MarcoFalke)

Tests and QA
  • #15826 Pure python EC (sipa)
  • #15893 Add test for superfluous witness record in deserialization (instagibbs)
  • #14818 Bugfix: test/functional/rpc_psbt: Remove check for specific error message that depends on uncertain assumptions (luke-jr)
  • #15831 Add test that addmultisigaddress fails for watchonly addresses (MarcoFalke)

Documentation
  • #15890 Remove text about txes always relayed from -whitelist (harding)

Miscellaneous
  • #16095 Catch by reference not value in wallettool (kristapsk)
  • #16205 Replace fprintf with tfm::format (MarcoFalke)

Credits

Thanks to everyone who directly contributed to this release:
  • Andrew Chow
  • Anthony Towns
  • Chris Moore
  • Daniel Kraft
  • David A. Harding
  • fanquake
  • Gregory Sanders
  • Hennadii Stepanov
  • John Newbery
  • Jonas Schnelli
  • Joćo Barbosa
  • Kristaps Kaupe
  • Luke Dashjr
  • MarcoFalke
  • MeshCollider
  • Pieter Wuille
  • shannon1916
  • tecnovert
  • Wladimir J. van der Laan

As well as everyone that helped translating on Transifex.



Code:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

88f343af72803b851c7da13874cc5525026b0b55e63e1b5e1298390c4688adc6  bitcoin-0.18.1-aarch64-linux-gnu.tar.gz
cc7d483e4b20c5dabd4dcaf304965214cf4934bcc029ca99cbc9af00d3771a1f  bitcoin-0.18.1-arm-linux-gnueabihf.tar.gz
989e847b3e95fc9fedc0b109cae1b4fa43348f2f712e187a118461876af9bd16  bitcoin-0.18.1-i686-pc-linux-gnu.tar.gz
b7bbcee7a7540f711b171d6981f939ca8482005fde22689bc016596d80548bb1  bitcoin-0.18.1-osx64.tar.gz
063b757820fead6e94eac5a52859bcb6421e23db71e562ddd2ebacdeecc621b7  bitcoin-0.18.1-osx.dmg
425ee5ec631ae8da71ebc1c3f5c0269c627cf459379b9b030f047107a28e3ef8  bitcoin-0.18.1-riscv64-linux-gnu.tar.gz
5c7d93f15579e37aa2d1dc79e8f5ac675f59045fceddf604ae0f1550eb03bf96  bitcoin-0.18.1.tar.gz
3bac0674c0786689167be2b9f35d2d6e91d5477dee11de753fe3b6e22b93d47c  bitcoin-0.18.1-win64-setup.exe
b0f94ab43c068bac9c10a59cb3f1b595817256a00b84f0b724f8504b44e1314f  bitcoin-0.18.1-win64.zip
600d1db5e751fa85903e935a01a74f5cc57e1e7473c15fd3e17ed21e202cfe5a  bitcoin-0.18.1-x86_64-linux-gnu.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJdTRv7AAoJEJDIAZ42wulkf8wP/jADLdlJnXYIZACzR8fMF6Pc
HkDUU9wAspKwynYFIzz2hWT9zG7AANBOpHJFDuRRXklSOsRKGFXpQ9tfhkVrQCX8
nNWXzwRZYb9AZctbUctvj6XGm6+3kGGtCjrQUp3Cs4RDOSlRnhb2pA42g2dU9mcM
V9IkvGnGYka/0i2wYbO7EhgFHKxP0Kff9RmG+HW09sYGw+/3tpgoi0AfwK34vXBu
vxw3Urw3Ch3gf+pZ0GzV3O/kOleCeQDq/w52G1hy4yQC4eNFojY9hN9qBD46LMR/
wmly1LrWP9H/46+j7wXqHeEoplqPx4M6l6DLaKVWJQqnz4lQXDtZ1Tq5IjgAeT7Z
7oPNt7pJ11o/mVSGT5wTNF3+i+4FZOnRjQ22nlNtOkpdnNPL9jJYVCO9o17yfNu+
Qym+6MbN5LpYTzPkMgnY69Ezw+kZAeKmoeigtfrICkJYzOMYpXvj+vPDZZy6dEqf
TS0jsDYMel2YvFopBn+oIvLijnwqtf07oZ1ZERyhKAjot8Hy6242C6yedgIDhpWh
XTOfMifDmF88YRGMu3axpfVDDfZh+MeLpLYNL1TqRTp51MhK7xFBvnApcwCT69og
6Vxh+1q1lAlyXt+iI2UzXk7PO1fwWbFcYkjWW5n2Eqw1CnUAI1SRfLc/fWzHDSj5
pBqqYxrEUK7+OVqaBdFC
=iy6G
-----END PGP SIGNATURE-----
11  Bitcoin / Bitcoin Technical Support / MOVED: C R Y P T O S T A M P with BITCOIN (solutions? thoughts & questions) - HELP! on: August 06, 2019, 05:33:30 PM
This topic has been moved to Trashcan.

Duplicate
12  Bitcoin / Wallet software / MOVED: Is there a TREZOR wallet that can import a list of derivation paths? on: June 29, 2019, 03:12:37 AM
This topic has been moved to Trashcan.

Duplicate
13  Bitcoin / Development & Technical Discussion / MOVED: Any recommended simple lightweight javascript module that helps sign messages? on: June 23, 2019, 03:58:37 PM
This topic has been moved to Trashcan.

Duplicate
14  Bitcoin / Development & Technical Discussion / MOVED: Question about exchange and other platform on: April 27, 2019, 03:51:19 PM
This topic has been moved to Trashcan.

Duplicate
15  Bitcoin / Bitcoin Technical Support / MOVED: How to assemble this type of pay to pubkey hash transaction ? on: April 04, 2019, 08:43:45 PM
This topic has been moved to Trashcan.

Duplicate
16  Bitcoin / Development & Technical Discussion / MOVED: Bip39helper to work with brainflayer on: March 14, 2019, 02:51:08 PM
This topic has been moved to Trashcan.

Duplicate
17  Bitcoin / Bitcoin Technical Support / MOVED: Generate address from mnemonic seed on: February 12, 2019, 01:24:54 AM
This topic has been moved to Trashcan.

Duplicate
18  Bitcoin / Development & Technical Discussion / MOVED: cryptocurrency owner??? on: January 19, 2019, 12:22:02 AM
This topic has been moved to Trashcan.

Duplicate
19  Bitcoin / Bitcoin Discussion / Bitcoin Core 0.17.1 Released on: December 25, 2018, 04:09:05 PM
Bitcoin Core version 0.17.1 is now available from:

  <https://bitcoincore.org/bin/bitcoin-core-0.17.1/>

or through BitTorrent:

    magnet:?xt=urn:btih:c56c87ccfaa8e6fbccc90d549121e61efd97cb6f&dn=bitcoin-core-0.17.1&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Fzer0day.ch%3A1337&tr=udp%3A%2F%2Fexplodie.org%3A6969    

This is a new minor version release, with 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).

If your node has a txindex, the txindex db will be migrated the first time you run 0.17.0 or newer, which may take up to a few hours. Your node will not be functional until this migration completes.

The first time you run version 0.15.0 or newer, 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.

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.10+, and Windows 7 and newer (Windows XP is not supported).

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

From 0.17.0 onwards macOS <10.10 is no longer supported. 0.17.0 is built using Qt 5.9.x, which doesn't
support versions of macOS older than 10.10.

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

`listtransactions` label support
--------------------------------

The `listtransactions` RPC `account` parameter which was deprecated in 0.17.0
and renamed to `dummy` has been un-deprecated and renamed again to `label`.

When bitcoin is configured with the `-deprecatedrpc=accounts` setting, specifying
a label/account/dummy argument will return both outgoing and incoming
transactions. Without the `-deprecatedrpc=accounts` setting, it will only return
incoming transactions (because it used to be possible to create transactions
spending from specific accounts, but this is no longer possible with labels).

When `-deprecatedrpc=accounts` is set, it's possible to pass the empty string ""
to list transactions that don't have any label. Without
`-deprecatedrpc=accounts`, passing the empty string is an error because returning
only non-labeled transactions is not generally useful behavior and can cause
confusion.

0.17.1 change log
=================

### P2P protocol and network code
- #14685 `9406502` Fix a deserialization overflow edge case (kazcw)
- #14728 `b901578` Fix uninitialized read when stringifying an addrLocal (kazcw)

### Wallet
- #14441 `5150acc` Restore ability to list incoming transactions by label (jnewbery)
- #13546 `91fa15a` Fix use of uninitialized value `bnb_used` in CWallet::CreateTransaction(…) (practicalswift)
- #14310 `bb90695` Ensure wallet is unlocked before signing (gustavonalle)
- #14690 `5782fdc` Throw error if CPubKey is invalid during PSBT keypath serialization (instagibbs)
- #14852 `2528443` backport: [tests] Add `wallet_balance.py` (MarcoFalke)
- #14196 `3362a95` psbt: always drop the unnecessary utxo and convert non-witness utxo to witness when necessary (achow101)
- #14588 `70ee1f8` Refactor PSBT signing logic to enforce invariant and fix signing bug (gwillen)
- #14424 `89a9a9d` Stop requiring imported pubkey to sign non-PKH schemes (sipa, MeshCollider)

### RPC and other APIs
- #14417 `fb9ad04` Fix listreceivedbyaddress not taking address as a string (etscrivner)
- #14596 `de5e48a` Bugfix: RPC: Add `address_type` named param for createmultisig (luke-jr)
- #14618 `9666dba` Make HTTP RPC debug logging more informative (practicalswift)
- #14197 `7bee414` [psbt] Convert non-witness UTXOs to witness if witness sig created (achow101)
- #14377 `a3fe125` Check that a separator is found for psbt inputs, outputs, and global map (achow101)
- #14356 `7a590d8` Fix converttopsbt permitsigdata arg, add basic test (instagibbs)
- #14453 `75b5d8c` Fix wallet unload during walletpassphrase timeout (promag)

### GUI
- #14403 `0242b5a` Revert "Force TLS1.0+ for SSL connections" (real-or-random)
- #14593 `df5131b` Explicitly disable "Dark Mode" appearance on macOS (fanquake)

### Build system
- #14647 `7edebed` Remove illegal spacing in darwin.mk (ch4ot1c)
- #14698 `ec71f06` Add bitcoin-tx.exe into Windows installer (ken2812221)

### Tests and QA
- #13965 `29899ec` Fix extended functional tests fail (ken2812221)
- #14011 `9461f98` Disable wallet and address book Qt tests on macOS minimal platform (ryanofsky)
- #14180 `86fadee` Run all tests even if wallet is not compiled (MarcoFalke)
- #14122 `8bc1bad` Test `rpc_help.py` failed: Check whether ZMQ is enabled or not (Kvaciral)
- #14101 `96dc936` Use named args in validation acceptance tests (MarcoFalke)
- #14020 `24d796a` Add tests for RPC help (promag)
- #14052 `7ff32a6` Add some actual witness in `rpc_rawtransaction` (MarcoFalke)
- #14215 `b72fbab` Use correct python index slices in example test (sdaftuar)
- #14024 `06544fa` Add `TestNode::assert_debug_log` (MarcoFalke)
- #14658 `60f7a97` Add test to ensure node can generate all rpc help texts at runtime (MarcoFalke)
- #14632 `96f15e8` Fix a comment (fridokus)
- #14700 `f9db08e` Avoid race in `p2p_invalid_block` by waiting for the block request (MarcoFalke)
- #14845 `67225e2` Add `wallet_balance.py` (jnewbery)

### Documentation
- #14161 `5f51fd6` doc/descriptors.md tweaks (ryanofsky)
- #14276 `85aacc4` Add autogen.sh in ARM Cross-compilation (walterwhite81)

Credits
=======

Thanks to everyone who directly contributed to this release:

- Andrew Chow
- Chun Kuan Lee
- David A. Harding
- Eric Scrivner
- fanquake
- fridokus
- Glenn Willen
- Gregory Sanders
- gustavonalle
- John Newbery
- Jon Layton
- Jonas Schnelli
- Joćo Barbosa
- Kaz Wesley
- Kvaciral
- Luke Dashjr
- MarcoFalke
- MeshCollider
- Pieter Wuille
- practicalswift
- Russell Yanofsky
- Sjors Provoost
- Suhas Daftuar
- Tim Ruffing
- Walter
- Wladimir J. van der Laan

As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).



Code:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

5659c436ca92eed8ef42d5b2d162ff6283feba220748f9a373a5a53968975e34  bitcoin-0.17.1-aarch64-linux-gnu.tar.gz
aab3c1fb92e47734fadded1d3f9ccf0ac5a59e3cdc28c43a52fcab9f0cb395bc  bitcoin-0.17.1-arm-linux-gnueabihf.tar.gz
b1e1dcf8265521fef9021a9d49d8661833e3f844ca9a410a9dd12a617553dda1  bitcoin-0.17.1-i686-pc-linux-gnu.tar.gz
6aa567381b95a20ac96b0b949701b04729a0c5796c320481bfa1db22da25efdb  bitcoin-0.17.1-osx64.tar.gz
e3d785d800b71d277959d15b2c2b33d44dd72c1288e559928a40488dd935c949  bitcoin-0.17.1-osx.dmg
3e564fb5cf832f39e930e19c83ea53e09cfe6f93a663294ed83a32e194bda42a  bitcoin-0.17.1.tar.gz
e9245e682126ef9fa4998eabbbdd1c3959df811dc10df60be626a5e5ffba9b78  bitcoin-0.17.1-win32-setup.exe
6464aa2d338f3697950613bb88124e58d6ce78ead5e9ecacb5ba79d1e86a4e30  bitcoin-0.17.1-win32.zip
fa1e80c5e4ecc705549a8061e5e7e0aa6b2d26967f99681b5989d9bd938d8467  bitcoin-0.17.1-win64-setup.exe
1abbe6aa170ce7d8263d262f8cb0ae2a5bb3993aacd2f0c7e5316ae595fe81d7  bitcoin-0.17.1-win64.zip
53ffca45809127c9ba33ce0080558634101ec49de5224b2998c489b6d0fc2b17  bitcoin-0.17.1-x86_64-linux-gnu.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJcIeQ5AAoJEJDIAZ42wulk0NoQAIunIBT06bd2IhhxV/48NUvf
sgTto4qYrKuX5Vkn+kfGuMBvNpmILi5CiVtnucWo7fKM6k5IPMyBQuE9iDVDzT9i
YemA9Au8Xy2aIGmVriuQoXxk8b17wAMS9uw362A3nXCz3kA+BWMDuMfBp3P3NPM/
PeOg6n04Q7seO/zNdT5i/ysaFB/XA8szrQxCRukSrXeGMUpv79UbcWOu3+nfGit9
yYo/F2yO57Yacv597rKILlg29QxEVTqa5+slMdwuU7NP5AdAcQV4EtFqoCOqM7C7
JL/zZWYnTywK3l0hOuCBJiY86izutWME5xgm7Eh3ORj+K6ZYT4iXw2JIkTdumeuS
X0WDE3ShH4rb35IaQX75FJLp5R7hLTXiNgng7b8Xhy/62bJ75Ob4HVVSLG1Lkhps
vtml10br+78qXiofzk8zaAW6KaG7G9nbBa0hfDjUEsYzA6P5iWA+53ykupc82HNa
ZT2gk+wWhNhZOd/ANheriM0eqm/ZlK7oydYRRtf9Tamk+XJgREU1x8cWlMZcCPEE
uIUzb7/REvYSjwcwArYLCq/eFPfjQe7jcG2WexnpxxkKJBvu2v4zVw9LLUPll094
BAmfk34iJKhN2cGVhvjO0Q9GKk0B2HzvhD5xn1Hnlp+NbXVNbKonYvkB71D3GY4W
t/eRyv7Erfi4dhHf+8oQ
=UEoM
-----END PGP SIGNATURE-----
20  Bitcoin / Development & Technical Discussion / MOVED: Help to Windows compile for my crypto. on: December 17, 2018, 12:40:12 AM
This topic has been moved to Trashcan.

Duplicate
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!