-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timing and rpcauth #95
Merged
adrienlacombe
merged 11 commits into
LedgerHQ:master
from
ziggie1984:timing-and-hashing
Jan 11, 2023
Merged
Timing and rpcauth #95
adrienlacombe
merged 11 commits into
LedgerHQ:master
from
ziggie1984:timing-and-hashing
Jan 11, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR builds on the previous change, sothat I could test it way more easily, in case the other change is merged, I will rebase this change. |
ziggie1984
force-pushed
the
timing-and-hashing
branch
from
December 22, 2022 17:49
70de3a8
to
cb35381
Compare
The lss_rescan.json has the following information and will reside in the same dir as the lss.json:
|
ziggie1984
force-pushed
the
timing-and-hashing
branch
from
December 22, 2022 18:07
ba66b59
to
a6c37b7
Compare
ziggie1984
force-pushed
the
timing-and-hashing
branch
from
December 22, 2022 18:16
a6c37b7
to
c8e2f6f
Compare
If you want to scan the wallet from a specific block, just edit the lss_rescan.json and paste the lastblock you want to rescan from. |
ziggie1984
force-pushed
the
timing-and-hashing
branch
from
December 22, 2022 23:03
dee5acd
to
55f3690
Compare
ziggie1984
force-pushed
the
timing-and-hashing
branch
3 times, most recently
from
January 10, 2023 08:54
c946133
to
dfef163
Compare
ziggie1984
force-pushed
the
timing-and-hashing
branch
from
January 10, 2023 09:03
dfef163
to
fdee767
Compare
ziggie1984
force-pushed
the
timing-and-hashing
branch
from
January 11, 2023 10:06
c3059c2
to
70a95e9
Compare
ziggie1984
force-pushed
the
timing-and-hashing
branch
from
January 11, 2023 10:09
70a95e9
to
d1ac916
Compare
adrienlacombe
approved these changes
Jan 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is hopefully the final change I have to make to use satstack on the raspiblitz.
It changes the README to use rpcauth in the bitcoin.conf instead of the normal rpcuser/rpcpassword
It adds a new config file
lss_rescan.json
which will remember the latest block this wallet was synced. Every time the user ends the program, the current state is dumped into the file leading to way fewer loading times, making this whole project more userfriendly.