Issue Details
- Number
- 31263
- Title
- importdescriptors always rescans
- Description
- ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behaviour
Running `importdescriptors` with `timestamp: now` rescans the last 2 hours worth of blocks.
The docs say that '"now" can be specified to bypass scanning' but that doesn't appear to be true:
```
"timestamp": timestamp | "now", (integer / string, required) Time from which to start rescanning the blockchain for this descriptor, in UNIX epoch time
Use the string "now" to substitute the current synced blockchain time.
"now" can be specified to bypass scanning, for outputs which are known to never have been used, and
0 can be specified to scan the entire blockchain. Blocks up to 2 hours before the earliest timestamp
of all descriptors being imported will be scanned as well as the mempool.
```
I also tried using timestamps several days into the future, but still see about 2 hours worth of blocks being rescanned. I want to be able to import a description without triggering any block rescan.
### Expected behaviour
I expect the behavior to match the docs.
### Steps to reproduce
1. Run importdescriptors with the timestamp set to "now"
2. See in the log that the wallet rescanned some blocks
### Relevant log output
_No response_
### How did you obtain Bitcoin Core
Compiled from source
### What version of Bitcoin Core are you using?
v28.0
### Operating system and version
Some kind of Debian
### Machine specifications
_No response_
- URL
-
https://github.com/bitcoin/bitcoin/issue/31263
- Closed by
-
Back to List