-
Notifications
You must be signed in to change notification settings - Fork 606
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
Mark addresses used #183
Mark addresses used #183
Conversation
Thanks. I took a very quick look and noticed that the serialization formation of addresses has been changed, but there is no code to upgrade the existing addresses which will be in the old format. |
OK, didn't consider that since the integration branch is not on master, but I'll add it in case anyone is already using the branch. |
3b73209
to
d3c4e23
Compare
This commit converts the wallet to use the new secure hierarchical deterministic wallet address manager package as well as the walletdb package. The following is an overview of modified functionality: - The wallet must now be created before starting the executable - A new flag --create has been added to create the new wallet using wizard style question and answer prompts - Starting the process without an existing wallet will instruct now display a message to run it with --create - Providing the --create flag with an existing wallet will simply show an error and return
Previously a runtime.GC was being invoked which forced it to release the memory as far as the garbage collector is concerned, but the memory was not released back to the OS immediatley. This modification allows the memory to be released immedately since it won't be needed again until the next wallet unlock.
Conflicts: btcwallet.go chain/chain.go wallet.go
d3c4e23
to
744319d
Compare
744319d
to
d09ce1d
Compare
Looks like build failed due to travis:
A forced rebuild should set this back to green. |
Closing in favor of #196 which is based on intwaddrmgr instead of master |
* Ticket purchasing code overhaul This pull request removes the old, buggy ticket purchase code and replaces it with code that is more robust. In particular, chains of tickets can now be purchased with ease because outputs to be consumed by tickets are now pregenerated in split transactions. Ticket expiry can now be added to ensure that the tickets will expire in a short time frame, so that the end user can update the ticket fees if their tickets fail to be added to a block. A new feature that was added was pool fees. Tickets can now pay a fee to a pool that is set by the user. The fee determines the amount that the user will contribute to the pool. The pool then receives this amount plus subsidy.
Added a database flag on Address to mark used addresses and prevent address re-use.