Following test instructions on https://bitcoincore.reviews/v23-rc-testing
- Downloaded binary bitcoin-23.0rc2-arm64-apple-darwin.dmg for Apple M1 ARM64 from https://bitcoincore.org/bin/bitcoin-core-23.0/test.rc2/
- Verify GPG signature and SHA256 hash
- Installed binary to ~/Documents with drag and drop
- Apple M1 MacBook Pro (13-inch, M1, 2020)
- macOS Big Sur 11.6.4 (20G417)
- Started IBD on mainnet with a pruned node using the default settings
- Changed units from BTC to mBTC to µBTc (bits) to Satoshi (sat)
- Inspected peers tab, switched through the tabs to see information, console and network traffic
- On Console tab, tested reducing and increasing font size using A-/A+ buttons
- On Console tab, tested gettxoutsetinfo command and clear button
- On Network Traffic tab, tested the horizontal scrollbar which seems to change the interval (not super intuitive) what it does should there be a label here?
- On Network Traffic tab, tested reset button
- On Information tab, opened debug log file
- Hid the IBD window
- Created a new wallet, named it Wallet 1, with default options Encrypt Wallet = false, Disable Private Keys = false, Make Blank Wallet = false, Descripor Wallet = true
- If I check Disable Private Keys, then Make Blank Wallet is also checked. If I uncheck it Disable Private Keys is also unchecked. Intentional?
- Before clicking create, tried erasing the Wallet Name to make sure the Create button is disabled when name is empty
- Switch to Transactions tab, click export. MacOS will ask for permission to my data folder. Exported the CSV file. Opened it in an editor to inspect content.
- Switch to Receive tab, generated all kinds of receive address with no fields filled in. Removed all receive addresses, both one by one and then by selecting all.
- Switched over to do the Signet and Testnet tests and then returned here to let the IBD finish, restarting in between to try out the encrypted wallet problems that were discussed in bitcoin/bitcoin#24501 (comment) and bitcoin-core/gui#571
- Completed the IBD and 2 GB of storage is used for the pruned blockchain.
- Tried to reopen Wallet 1 got two error messages
Tried a restart and then the app froze! on this screen, which required a force quit
- After about four or five restart attempts the wallet is successfully loaded and I'm able to generate all four types of receiving addresses.
- Is this mainly a problem with wallets created during IBD and when using a pruned node? I think the errors could be improved or users facing this error and unable to load the wallet could think they have lost their funds.
- Edited
bitcoin.conf
and setsignet=1
- Restarted app
- Splash screen and dock icon changed to yellow
- IBD completed
- Created wallet with name Signet Wallet 1!"#€!", options Encrypt Wallet = true, Disable Private Keys = false (disabled), Make Blank Wallet = false, Descriptor Wallet = true, External signer = false (disabled)
- Added a 100 character long password
- Received from faucet to all three addresses available on Signet:
- Base58 (Legacy)
- Base58 (P2SH-SegWit)
- Bech32 (SegWit)
- Tested a self transfer from P2SH-SegWit to Legacy
- Tested a self transfer from P2SH-SegWit to Bech32
- Edited
bitcoin.conf
and settestnet=1
to activate Testnet - Restarted app
- Splash screen and dock icon changed to green
- In the Receive tab, if I double click (or triple click depending on how fast I am) the Create new receiving address two or more addresses are generated and multiple QR codes are shown
- Regarding consistency, some buttons are
Named With Capital
letters, but most areNamed with only starting capital
letters. Is there a reason for this, or should they all follow the same pattern? Some examples:External signer
,Generate receiving address
,Use available balance
butAdd Recipient
,Clear All
,Open Configuration File
,Reset Options
- If I right click and edit label on a self transfer transaction which contains many addresses, I get an error:
The entered address "myBWQQjTUdyBCVbFPzEpY7Rv3K3LbpHnR3, mir36n3M4GBt6sZVZ4FpCrBHYJiCTCTVix" is not a valid Bitcoin address.
- In some dialogs, there is no space after dot/comma in the error message (see screenshots above for an example).