You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use 2 hour grace period for key timestamps in importmulti rescans
Gregory Maxwell <[email protected]> pointed out the lack of grace period in
bitcoin/bitcoin#9490 (comment).
The importwallet RPC which uses key timestamps in a similar way already has a 2
hour grace period.
" or the string \"now\" to substitute the current synced blockchain time. The timestamp of the oldest\n"
989
989
" key will determine how far back blockchain rescans need to begin for missing wallet transactions.\n"
990
990
"\"now\" can be specified to bypass scanning, for keys which are known to never have been used, and\n"
991
-
" 0 can be specified to scan the entire blockchain.\n"
991
+
" 0 can be specified to scan the entire blockchain. Blocks up to 2 hours before the earliest key\n"
992
+
" creation time of all keys being imported by the importmulti call will be scanned.\n"
992
993
"\"redeemscript\": \"<script>\" , (string, optional) Allowed only if the scriptPubKey is a P2SH address or a P2SH scriptPubKey\n"
993
994
"\"pubkeys\": [\"<pubKey>\", ... ] , (array, optional) Array of strings giving pubkeys that must occur in the output or redeemscript\n"
994
995
"\"keys\": [\"<key>\", ... ] , (array, optional) Array of strings giving private keys whose corresponding public keys must occur in the output or redeemscript\n"
0 commit comments