Josh Rickmar
Josh Rickmar
I would like to continue using as much of the existing spend tracking as there is, since this can get very complicated to implement correctly across reorganizations and replacement transactions...
The transaction is too large, you will need to abandon it (dcrctl abandontransaction) and create new transactions that do not include as many inputs/outputs.
Is this still a draft or ready for review?
Few issues: A long time ago we had several different components (address manager, tx store, stake store) all being saved in the database, but they were versioned separately and one...
Also, be aware of golang/go#18007 when generating the testdata files. I have needed to rename testdata to something else just to `go run` the generators.
After upgrading, the database will be compatible with the older db test artifacts, however those won't expose the problem we are trying to fix here.
The error is fixed on master now. As for creating the test db, you can just write keys/values directly to the DB. This is fine for this case since we...
The invalid DB for the test can be created in a more simpler way by using keys and values created from the `keyMultisigOut` and `valueMultisigOut` functions. Since these are unexported,...
The purchaseticket method needs to be replaced with something more flexible. Here is the problem: ``` $ dcrctl -l | grep purchaseticket purchaseticket "fromaccount" spendlimit (minconf=1 "ticketaddress" numtickets "pooladdress" poolfees...
Send the logs from the working wallet and at least one of the wallets that is not working.