v0.18.0 testing #15555

issue Sjors opened this issue on March 7, 2019
  1. Sjors commented at 2:23 PM on March 7, 2019: member

    Link to binaries:

    Let us know which version you tested on which operating system. If you find an issue, please search Github for known issues first and then open a new Github issue.

    See Release Notes for a list of changes, and testing reports for earlier releases (v0.17.1), for an idea what to test.

  2. Sjors commented at 2:28 PM on March 7, 2019: member

    tACK v0.18.0rc1 on macOS 10.14.3:

    • tested installing from (signed) DMG
    • tested loading wallets
    • testing sending coins
    • testing receiving coins (notification)
  3. Sjors cross-referenced this on Mar 7, 2019 from issue Release schedule for 0.18.0 by MarcoFalke
  4. fanquake added the label Tests on Mar 7, 2019
  5. fanquake added this to the milestone 0.18.0 on Mar 7, 2019
  6. kiv06041992 commented at 7:03 AM on March 8, 2019: none

    q

  7. promag commented at 8:13 AM on March 8, 2019: member

    @kiv06041992 mind sharing relevant configuration?

  8. kiv06041992 commented at 10:59 AM on March 8, 2019: none

    OS: Ubuntu 18.04.2 LTS - x64 CPU: AMD® Fx(tm)-6100 six-core processor × 6 Memory: 11.6гб and russian language

    0.17.1 is working stable

    If you need you may connect towards my computer via TeamViewer

  9. makoting commented at 4:25 AM on March 9, 2019: none

    bitcoind v0.18.0rc1 is using 100% CPU resources while syncing the blocks. Top, the processes monitoring utility, shows bitcoind-opencon thread is the CPU hog. Ran with -proxy=127.0.0.1:9050.

    Debian 9.8 x86_64 Linux GNU as guest VM VirtualBox 6.0.4, Windows 10 as host Intel Core i5-8250U CPU

  10. fanquake pinned this on Mar 10, 2019
  11. hebasto commented at 6:15 PM on March 10, 2019: member

    @kiv06041992 I can try reproduce an issue on Ubuntu with Russian language. Which desktop environment do you use? Let us know your bitcoin.conf and your command-line options if any as well.

    On the other hand, you can submit a new issue.

  12. jasonzhouu commented at 2:42 AM on March 11, 2019: none

    tACK v0.18.0rc1 on macOS 10.14.2:

    • tested installing from (signed) DMG
    • tested loading wallets
    • tested sending coins
    • testing receiving coins (notification), testnet receive address:
      • tb1qcn58cs07dxg5292w3zrkvjapzgjdtts5lvx7s2
      • 2NBaJprx17hpMwo1Va15epfAC7iw8zVHuPT
    • tested language of en, zh_CN and zh. it shows Chinese successfully with zh_CN setting, but shows english with zh setting, which also means Chinese.

    en, zh image

    zh_CN image

  13. kiv06041992 commented at 6:49 AM on March 11, 2019: none

    @hebasto My bitcoin.conf is empty. I use Ubuntu Desktop 18.04.2 (64-bit) https://ubuntu.ru/get

    I looked debug.log and saw it. `2019-03-07T20:04:10Z GUI: Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must not let any exception whatsoever propagate through Qt code. If that is not possible, in Qt 5 you must at least reimplement QCoreApplication::notify() and catch all exceptions there.

    2019-03-07T20:04:10Z

    EXCEPTION: N5boost10filesystem16filesystem_errorE filesystem::recursive_directory_iterator directory error: Отказано в доступе bitcoin in Runaway exception`

    After this message bitcoin core crashed.

  14. MarcoFalke commented at 2:19 PM on March 11, 2019: member

    @kiv06041992 Could you please share the lines before that in the debug.log?

  15. promag commented at 2:30 PM on March 11, 2019: member

    @kiv06041992 looks like your exception is the same as https://stackoverflow.com/a/23135989.

    Mind sharing boost version used to build?

  17. MarcoFalke commented at 5:17 PM on March 11, 2019: member

    Does this also happen if you run bitcoind? If so, could you please run bitcoind in gdb to get a stack trace of the exception?

  18. kiv06041992 commented at 5:22 PM on March 11, 2019: none

    @promag I download bitcoin-0.18.0rc1-x86_64-linux-gnu.tar.gz https://bitcoincore.org/bin/bitcoin-core-0.18.0/test.rc1/ and put bitcoin-0.18.0rc1-x86_64-linux-gnu.tar.gz/bitcoin-0.18.0rc1/bin/bitcoin-qt in /usr/local/bin and run him ./bitcoin-qt I did not use build. Only 0.18.0 crashed. v0.17.1 work perfectly

    Sorry. I bad speak english but want help

  19. promag commented at 5:34 PM on March 11, 2019: member

    Please run bitcoin-qt -nowallet and see if the error occurs.

  20. kiv06041992 commented at 6:57 PM on March 11, 2019: none

    @promag I ran bitcoin-qt -nowallet and waiting @MarcoFalke I did not run bitcoind. If will bitcoin-qt -nowallet crash i will try run bitcoind in gdb

  21. promag commented at 10:37 PM on March 11, 2019: member

    I've managed to reproduce the problem (or apparently) in macos:

    # 1. create directory for -walletdir without read access
mkdir /tmp/foo && chmod a-r /tmp/foo

# 2. download and mount https://bitcoincore.org/bin/bitcoin-core-0.18.0/test.rc1/bitcoin-0.18.0rc1-osx.dmg

# 3. run bitcoin-qt and should print a error, but continues running
/Volumes/Bitcoin-Core/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt -regtest -walletdir=/tmp/foo
/private/tmp/foo: Permission denied

# 4. go to File -> Open Wallet and should segfault
EXCEPTION: N5boost10filesystem16filesystem_errorE
boost::filesystem::directory_iterator::construct: Permission denied: "/private/tmp/foo"
bitcoin in Runaway exception

    I'm working on a fix.

  22. promag cross-referenced this on Mar 11, 2019 from issue wallet: Log and ignore errors in ListWalletDir and IsBerkeleyBtree by promag
  23. MarcoFalke commented at 3:20 PM on March 12, 2019: member

    That fixes the underlying wallet issue, but it seems there is still the gui issue:

    Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.
If that is not possible, in Qt 5 you must at least reimplement
QCoreApplication::notify() and catch all exceptions there.
  24. promag commented at 3:42 PM on March 12, 2019: member

    must not let any exception whatsoever propagate @MarcoFalke the fix does this?

  25. kiv06041992 commented at 6:09 PM on March 12, 2019: none

    @promag

    Please run bitcoin-qt -nowallet and see if the error occurs.

    My node is still working. Thanks.

  26. promag commented at 11:51 PM on March 12, 2019: member

    @kiv06041992 note that running with -nowallet doesn't fix the issue.

  27. jonatack commented at 1:26 PM on March 14, 2019: contributor

    Partial tACK bitcoin-0.18.0rc1-x86_64-linux-gnu.tar.gz

    PureOS distribution of Linux Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux

    • tested installing
    • tested loading wallets
    • tested running bin/bitcoind with nearly up-to-date mainnet blocks, synced rapidly without issue
    • tested running bin/bitcoin-qt, verifying debug windows info/console/network/peers, and running cli commands in the console
  28. jonatack commented at 1:45 PM on March 14, 2019: contributor

    Idem for compiling v0.18.0rc1 tagged branch from source.

  29. jonatack cross-referenced this on Mar 15, 2019 from issue [Docs] Release process updates by jonatack
  30. jonatack referenced this in commit ff414288b5 on Mar 16, 2019
  31. MarcoFalke commented at 1:54 PM on March 18, 2019: member

    You can also report issues you found here

    I'd advise against reporting issues here. They should go in their own report. Otherwise it is hard to follow-up on reports when everything is in the same thread.

    See Release Notes for a list of changes

    The link points to the file in git, whereas the release notes draft is located in https://github.com/bitcoin-core/bitcoin-devwiki/wiki/0.18.0-Release-Notes-Draft

  32. Sjors commented at 3:27 PM on March 19, 2019: member

    I updated the release note link and changed the wording to encourage new tickets.

  33. jonatack referenced this in commit 7aa8c01b12 on Mar 22, 2019
  34. jonatack referenced this in commit 7a4f140c62 on Mar 22, 2019
  35. jonatack referenced this in commit 1874a21bec on Mar 22, 2019
  36. jonatack referenced this in commit 7ac42093f6 on Mar 22, 2019
  37. lucayepa commented at 5:01 PM on March 23, 2019: contributor

    Partially tested rc2 on Debian oldstable (8.11), Debian stable (9.8), Alpine (3.9.2):

    • bitcoind compiled from source, tested, used on mainnet with regular p2p activity
    • reindexed from scratch
    • txindex deleted and rebuilt from scratch
  38. farrilis commented at 4:51 PM on March 25, 2019: none

    CPU maxing out using 18 rc2 binaries, Debian 9.8, using prune=550 with bitcoin-qt

    importmulti -ing several hundred watch only addresses to a non-default wallet apparently triggered this, but subsequently executing with -disablewallet exhibits the same issue (CPU spikes to 100% for 5-10s every 30s)

    No such CPU spikes using 0.17.1 (either loading -wallet=mywatchonly or -disablewallet). 0.18.0rc2 does exhibit the described spikes with either -wallet=mywatchonly or -disablewallet. Hence maybe a prune=550 issue.

  39. MarcoFalke commented at 5:00 PM on March 25, 2019: member

    @farrilis Could you determine which thread is using the CPU? (Maybe with top or htop) Alternatively get a thread apply all bt in gdb when the spike happens to see the exact code location.

  40. farrilis commented at 6:26 PM on March 25, 2019: none

    $ gdb ./bitcoin-qt (gdb) thread apply all bt (gdb) run

    last 3 lines in gdb are:

    [New Thread 0x7fff41ffb700 (LWP 2406)] [Thread 0x7fff51063700 (LWP 2400) exited] [Thread 0x7fff52866700 (LWP 2395) exited]

    not too familiar with gdb, hope that's useful

  41. farrilis commented at 6:28 PM on March 25, 2019: none

    also, running with gdb seems to permanently peg CPU usage

  42. MarcoFalke commented at 7:02 PM on March 25, 2019: member

    With htop you can select F5 for tree view and F2-"Display options"-[x] thread names to get the thread names.

    In gdb, you'd have to break before the bt. I guess CTRL+C does this.

  43. farrilis commented at 9:04 PM on March 25, 2019: none

    htop is telling me bitcoin-opencon is responsible. Peers are neither added or dropped coinciding with the CPU spike

  44. MarcoFalke cross-referenced this on Mar 25, 2019 from issue 0.18.0 rc2 CPU spike in thread bitcoin-opencon by MarcoFalke
  45. practicalswift cross-referenced this on Mar 26, 2019 from issue Newsletters: add #39 (2019-03-26) by harding
  46. MarcoFalke commented at 9:57 PM on March 28, 2019: member

    @farrilis Could you do the following:

    • Open a terminal window with htop
    • Open another terminal window with gdb --args ./bitcoin-qt ** Type run in (gdb) ** Watch the CPU usage of the opencon thread in the htop window ** Hit CTRL+C in (gdb) when it is at 100% ** Type thread apply all bt in (gdb)
  47. jonatack referenced this in commit b9bdfe3e07 on Mar 28, 2019
  48. farrilis commented at 10:28 AM on March 29, 2019: none

    Ok:

    Thread 22 (Thread 0x7fff45fb0700 (LWP 2310)):
[#0](/github-metadata-backup-bitcoin-bitcoin/0/)  0x00007ffff637e981 in __GI_ppoll (fds=0x555557c58608, nfds=1, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
[#1](/github-metadata-backup-bitcoin-bitcoin/1/)  0x00005555562934c1 in ?? ()
[#2](/github-metadata-backup-bitcoin-bitcoin/2/)  0x0000555556294a99 in ?? ()
[#3](/github-metadata-backup-bitcoin-bitcoin/3/)  0x000055555624245f in ?? ()
[#4](/github-metadata-backup-bitcoin-bitcoin/4/)  0x00005555560e2956 in ?? ()
[#5](/github-metadata-backup-bitcoin-bitcoin/5/)  0x00005555560e4c25 in ?? ()
[#6](/github-metadata-backup-bitcoin-bitcoin/6/)  0x00007ffff79bb4a4 in start_thread (arg=0x7fff45fb0700) at pthread_create.c:456
[#7](/github-metadata-backup-bitcoin-bitcoin/7/)  0x00007ffff6387d0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 21 (Thread 0x7fff467b1700 (LWP 2309)):
[#0](/github-metadata-backup-bitcoin-bitcoin/0/)  0x00007ffff637e981 in __GI_ppoll (fds=0x7fff24000ac8, nfds=1, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
[#1](/github-metadata-backup-bitcoin-bitcoin/1/)  0x00005555562934c1 in ?? ()
[#2](/github-metadata-backup-bitcoin-bitcoin/2/)  0x0000555556294a99 in ?? ()
[#3](/github-metadata-backup-bitcoin-bitcoin/3/)  0x000055555624245f in ?? ()
[#4](/github-metadata-backup-bitcoin-bitcoin/4/)  0x00005555560e2956 in ?? ()
[#5](/github-metadata-backup-bitcoin-bitcoin/5/)  0x00005555560e4c25 in ?? ()
[#6](/github-metadata-backup-bitcoin-bitcoin/6/)  0x00007ffff79bb4a4 in start_thread (arg=0x7fff467b1700) at pthread_create.c:456
[#7](/github-metadata-backup-bitcoin-bitcoin/7/)  0x00007ffff6387d0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 20 (Thread 0x7fff47420700 (LWP 2308)):
[#0](/github-metadata-backup-bitcoin-bitcoin/0/)  0x00007ffff637e981 in __GI_ppoll (fds=0x7fff20000ac8, nfds=1, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
[#1](/github-metadata-backup-bitcoin-bitcoin/1/)  0x00005555562934c1 in ?? ()
[#2](/github-metadata-backup-bitcoin-bitcoin/2/)  0x0000555556294a99 in ?? ()
[#3](/github-metadata-backup-bitcoin-bitcoin/3/)  0x000055555624245f in ?? ()
[#4](/github-metadata-backup-bitcoin-bitcoin/4/)  0x00005555560e2956 in ?? ()
[#5](/github-metadata-backup-bitcoin-bitcoin/5/)  0x00005555560e4c25 in ?? ()
[#6](/github-metadata-backup-bitcoin-bitcoin/6/)  0x00007ffff79bb4a4 in start_thread (arg=0x7fff47420700) at pthread_create.c:456
[#7](/github-metadata-backup-bitcoin-bitcoin/7/)  0x00007ffff6387d0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 19 (Thread 0x7fff47c21700 (LWP 2307)):
[#0](/github-metadata-backup-bitcoin-bitcoin/0/)  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
[#1](/github-metadata-backup-bitcoin-bitcoin/1/)  0x000055555588049b in ?? ()
[#2](/github-metadata-backup-bitcoin-bitcoin/2/)  0x000055555586f885 in ?? ()
[#3](/github-metadata-backup-bitcoin-bitcoin/3/)  0x000055555588effb in ?? ()
[#4](/github-metadata-backup-bitcoin-bitcoin/4/)  0x0000555556afccbf in ?? ()
[#5](/github-metadata-backup-bitcoin-bitcoin/5/)  0x00007ffff79bb4a4 in start_thread (arg=0x7fff47c21700) at pthread_create.c:456
[#6](/github-metadata-backup-bitcoin-bitcoin/6/)  0x00007ffff6387d0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 18 (Thread 0x7fff48422700 (LWP 2306)):
[#0](/github-metadata-backup-bitcoin-bitcoin/0/)  0x00007ffff79c451f in __libc_recv (fd=42, buf=0x7fff48420ecc, n=4, flags=0) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:28
[#1](/github-metadata-backup-bitcoin-bitcoin/1/)  0x0000555555be958a in ?? ()
[#2](/github-metadata-backup-bitcoin-bitcoin/2/)  0x0000555555beee50 in ?? ()
[#3](/github-metadata-backup-bitcoin-bitcoin/3/)  0x0000555555bf0525 in ?? ()
[#4](/github-metadata-backup-bitcoin-bitcoin/4/)  0x000055555588af61 in ?? ()
[#5](/github-metadata-backup-bitcoin-bitcoin/5/)  0x000055555588b510 in ?? ()
[#6](/github-metadata-backup-bitcoin-bitcoin/6/)  0x000055555588c285 in ?? ()
[#7](/github-metadata-backup-bitcoin-bitcoin/7/)  0x00005555558948c7 in ?? ()
[#8](/github-metadata-backup-bitcoin-bitcoin/8/)  0x000055555586f885 in ?? ()`
  49. jonatack referenced this in commit dba0fbb2f1 on Mar 29, 2019
  50. MarcoFalke commented at 4:05 PM on March 29, 2019: member

    Hmm, looks like you are missing the debug symbols. You might want to try to download them into the same folder where your bitcoin-qt is located and then start gdb again (it should then print something like Reading symbols from ./bin/bitcoin-qt...Reading symbols from ./bin/bitcoin-qt.dbg...done.

    wget https://github.com/achow101/bitcoin/releases/download/v0.18.0rc2/bitcoin-0.18.0rc2-x86_64-linux-gnu-debug.tar.gz
echo '438c107c985c88fa7e2eec13f7c03cdfedf079698ef7ea07597962fad080b954  bitcoin-0.18.0rc2-x86_64-linux-gnu-debug.tar.gz' | sha256sum --check
# untar and repeat above steps with gdb
  51. farrilis commented at 3:47 PM on March 31, 2019: none

    result:

    Thread 1 "bitcoin-qt" received signal SIGINT, Interrupt.
0x00007ffff637e981 in __GI_ppoll (fds=0x555557f53618, nfds=2, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
39      ../sysdeps/unix/sysv/linux/ppoll.c: No such file or directory.
  52. promag commented at 11:06 PM on April 1, 2019: member

    Hence maybe a prune=550 issue. @farrilis but what happens without prune in 0.18?

  53. farrilis commented at 11:03 AM on April 2, 2019: none

    without prune I don't see this issue using 0.18. My full NETWORK_NODE is in a different VM.

  54. bitcoinhodler commented at 5:33 AM on April 3, 2019: contributor

    In 0.18.0rc3, the new getrpcinfo returns JSON with a key "duration", but there is nothing in that key name or in bitcoin-cli help getrpcinfo that tells me what time units it's counting in. Is that duration in seconds? Milliseconds? I have no idea.

  55. nitramiz commented at 4:41 PM on April 3, 2019: none

    tACK 0.18.0rc2 on MacOS 10.13.6:

    • Built a docker image for bitcoind (blockstream/bitcoind@sha256:4c072542ff148b99467cab32756c3c2cdd1e05a8b8e30c2b1fe28a9ca90ec0b8) from the binary at bitcoincore.org (x86_64-linux-gnu.tar.gz)
    • Ran with prune=10000 and dbcache=2500
    • Synced testnet from scratch and reindexed once
    • Tested createfunded/decode/finalize PSBT, importmulti and broadcasting a tx (with the help of HWI and a Trezor)
  56. MarcoFalke cross-referenced this on Apr 3, 2019 from issue Add getrpcinfo doc by MarcoFalke
  57. promag commented at 11:13 PM on April 8, 2019: member

    @bitcoinhodler it is microseconds. getrpcinfo help message was completed in #15754.

  58. jonatack commented at 12:39 PM on April 11, 2019: contributor

    Partial ACK bitcoin-0.18.0rc3-x86_64-linux-gnu.tar.gz

    Linux Debian 4.19.28-2 (2019-03-15) x86_64 GNU/Linux

    • tested installing
    • tested loading wallets
    • tested bitcoind with nearly up-to-date mainnet blocks, synced rapidly without issue
    • tested bitcoin-qt, verifying debug file, windows info/console/network/peers, and running cli commands in the console
  59. jonatack referenced this in commit 04415de8ed on Apr 16, 2019
  60. jonatack referenced this in commit a684f9a4db on Apr 16, 2019
  61. jonatack referenced this in commit 5eb28bb3a0 on Apr 16, 2019
  62. jonatack referenced this in commit a68cbce1e1 on Apr 16, 2019
  63. jonatack referenced this in commit 06d28351e0 on Apr 16, 2019
  64. jonatack referenced this in commit d9f7a33dc2 on Apr 16, 2019
  65. jonatack referenced this in commit 3c3d801f3c on Apr 16, 2019
  66. jonatack referenced this in commit 3fd0cf303e on Apr 16, 2019
  67. jonatack referenced this in commit 80ad32c519 on Apr 16, 2019
  68. cfromknecht commented at 2:29 AM on April 17, 2019: none

    A user recently reported https://github.com/lightningnetwork/lnd/issues/2961 in testing lnd with an 0.18-ish build. I was able to locate #13541 which introduces a breaking change to the sendrawtransaction API, preventing lnd from publishing transactions with the following error:

    Second argument must be numeric (maxfeerate) and no longer supports a boolean. To allow a transaction with high fees, set maxfeerate to 0.

    In skimming the draft release notes I could not find anything mentioning this change, is it worth adding?

    The change affects all prior versions of lnd including 0.6 tagged today, so we'll be working on an update to our rpcclient to support the new numeric value and support downgrading to the boolean value on pre-0.18 nodes in our next 0.6.1 release.

    (happy to make a separate issue if there's more to be done besides updating release notes)

  69. fanquake commented at 2:45 AM on April 17, 2019: member

    @cfromknecht #13541 isn't part of v0.18, (it's currently in master and will be released in v0.19), so I'd assume that user is running some version of master they've compiled themselves. Although looking at the related issue, they originally said they were running v0.17.1, so it's a bit hard to tell?

  70. cfromknecht commented at 3:08 AM on April 17, 2019: none

    @fanquake

    #13541 isn't part of v0.18, (it's currently in master and will be released in v0.19)

    oh i see, that then makes perfect sense why i couldn't find it in the release notes :) thank you for the clarification, that should give us plenty of time to support the change from our end

    they originally said they were running v0.17.1

    i presume it's because the versions may not be bumped in their branch, but yes it is unclear

  71. cfromknecht cross-referenced this on Apr 17, 2019 from issue rpcclient: support numeric maxfeerate in bitcoind sendrawtransaction by Rui2guo
  72. molxyz commented at 5:50 PM on April 23, 2019: none

    @Sjors Hi, thank you for this thread. I'm also trying to test 0.18.0rc4.

    I have a question if anyone knows what the button Main Window on bitcoin-qt is for? I am running v0.18.0rc4, started seeing this button since last RC version, could not get it to do anything, thought it would be fixed in RC4 but still the same. I have tried by going from one window to another and clicked on this button Main Window but it doesn't do anything so I am wondering why it's there.

    I compiled the software from source on WSL using bitcoin guide https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md and running it on Windows 10.

    image

  73. Sjors commented at 6:13 PM on April 23, 2019: member

    @molxyz please create a new issue for that; this issue is for finding potential release blocking problems. I think it was introduced here.

  74. molxyz commented at 8:01 PM on April 23, 2019: none

    @Sjors Thank you. Will do right now.

  75. jonatack referenced this in commit df173441ea on May 1, 2019
  76. laanwj unpinned this on May 2, 2019
  77. fanquake commented at 2:50 AM on May 3, 2019: member

    Closing this now that v0.18.0 has been released.

  78. fanquake closed this on May 3, 2019
  79. jonatack referenced this in commit 74a0ec559e on May 10, 2019
  80. jonatack referenced this in commit 96d32a7bc0 on May 10, 2019
  81. MarcoFalke referenced this in commit e79bbb73e0 on May 10, 2019
  82. sidhujag referenced this in commit 03cc71be5f on May 10, 2019
  83. HashUnlimited referenced this in commit cf13ffaba6 on Aug 30, 2019
  84. molxyz cross-referenced this on Aug 30, 2019 from issue gui: Remove unused menu items for Windows and Linux by GChuf
  85. Sjors cross-referenced this on Oct 8, 2019 from issue v0.19.0 testing by Sjors
  86. Munkybooty referenced this in commit 871dbb90ad on Oct 16, 2021
  87. Munkybooty referenced this in commit b138ac49b2 on Oct 16, 2021
  88. bitcoin locked this on Dec 16, 2021
Contributors
Sjorskiv06041992promagmakotinghebastojasonzhouuMarcoFalkejonatacklucayepafarrilisbitcoinhodlernitramizcfromknechtfanquakemolxyz
Labels
Tests

Milestone
0.18.0

Linked (view graph)
#2 Long-term, safe, store-of-value#3 Encrypt wallet#4 Export/Import wallet in a human readable, future-proof format#5 Make the version number the protocol version and not the client version#6 Treat wallet as a generic keystore#7 Block-header-only, faster startup client#8 RPC command to sign text with wallet private key#13541 wallet/rpc: sendrawtransaction maxfeerate#14438 Release schedule for 0.18.0#14573 qt: Add Window menu#14902 v0.17.1 testing#15583 wallet: Log and ignore errors in ListWalletDir and IsBerkeleyBtree#15607 [Docs] Release process updates#15665 0.18.0 rc2 CPU spike in thread bitcoin-opencon#15731 Add getrpcinfo doc#15754 rpc: getrpcinfo docs#16735 gui: Remove unused menu items for Windows and Linux#17079 v0.19.0 testing
github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-05-20 06:54 UTC