Is there an existing issue for this?
- I have searched the existing issues
Current behaviour
Testing in regtest mode, I have noticed that after 1 day of send some funds from A wallet to B, the unspent inputs disappear from wallet B.
bitcoin.conf
0# Generated by https://jlopp.github.io/bitcoin-core-config-generator/
1
2# This config should be placed in following path:
3# ~/.bitcoin/bitcoin.conf
4
5# [chain]
6# Run this node on its own independent test network. Equivalent to -chain=regtest
7regtest=1
8
9# [core]
10# Specify a non-default location to store blockchain and other data.
11datadir=/home/debian/.bitcoin
12# Reduce storage requirements by only storing most recent N MiB of block. This mode is incompatible with -txindex and -coinstatsindex. WARNING: Reverting this setting requires re-downloading th>
13prune=0
14
15# [wallet]
16# Bech32
17addresstype=bech32
18# Bech32
19changetype=bech32
20# Specify wallet database path. Can be specified multiple times to load multiple wallets. Path is interpreted relative to <walletdir> if it is not absolute and will be created if it does not ex>
21wallet=default
22
23# [Sections]
24# Most options automatically apply to mainnet, testnet, and regtest networks.
25# If you want to confine an option to just one network, you should add it in the relevant section.
26# EXCEPTIONS: The options addnode, connect, port, bind, rpcport, rpcbind and wallet
27# only apply to mainnet unless they appear in the appropriate section below.
28
29# Options only for mainnet
30[main]
31
32# Options only for testnet
33[test]
34
35# Options only for regtest
36[regtest]
37# Accept command line and JSON-RPC commands.
38server=1
39# Bind to given address to listen for JSON-RPC connections. This option is ignored unless -rpcallowip is also passed. Port is optional and overrides -rpcport. Use [host]:port notation for IPv6.>
40rpcbind=127.0.0.1
41# Listen for JSON-RPC connections on this port
42rpcport=10001
43# Allow JSON-RPC connections from specified source. Valid for <ip> are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). This optio>
44rpcallowip=127.0.0.1
45# Username and hashed password for JSON-RPC connections. The field <userpw> comes in the format: <USERNAME>:<SALT>$<HASH>. RPC clients connect using rpcuser=<USERNAME>/rpcpassword=<PASSWORD> ar>
46rpcauth=bitcoin:6e0efb08ebd20eff65959edc38d17bc4$9bc0e273f35e583d9b70071cfd71dc78034ff639d1900c780e3412d7011aab1f
Expected behaviour
Obtain unspent inputs
Steps to reproduce
0// Send unspent
1bitcoin-core.cli -named send outputs='{"bcrt1qugd904ne5z0ks45fgmdcne2qe37s2fv7jqra24": 0.034}' fee_rate=25
2
3// Generate blocks
4bitcoin-core.cli generatetoaddress 6 bcrt1qpg03lyd93mfvz56p92rl6e0mxzasrfskccn77k
5
6// List unspent
7bitcoin-core.cli listunspent 0 9999999 [\"bcrt1qugd904ne5z0ks45fgmdcne2qe37s2fv7jqra24\"]
After day, trying again to list with listunspent and the result is empty.
Relevant log output
No response
How did you obtain Bitcoin Core
Package manager
What version of Bitcoin Core are you using?
v0.25
Operating system and version
Debian 11
Machine specifications
No response
