beancounter
beancounter copied to clipboard
square
Utility to audit the balance of Hierarchical Deterministic (HD) wallets. Supports multisig + segwit wallets.
Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.7.0 to 1.8.0. Commits 181cea6 impr: CallerInfo should print full paths to the terminal (#1201) cf1284f Allow mock expectations to be ordered (#1106) 66eef0e fix: assert.MapSubset (or...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Hey guys, I'm trying to run the beancounter tool but receive a `Failed negotiate version` error: `go run ./main.go compute-balance --type multisig --block-height 1438791 --debug` paste public key: `tpubDBrCAXucLxvjC9n9nZGGcYS8pk4X1N97YJmUgdDSwG2p36gbSqeRuytHYCHe2dHxLsV2EchX9ePaFdRwp7cNLrSpnr3PsoPLUQqbvLBDWv` Result...
Small outputs cannot be used (because the fee per byte x bytes required to use the output is greater than the output) and are called dust. Should we track dust...
The accounter should only schedule additional addresses after checking each transaction's height.
We have a bunch of unittests, but no integration tests. We should probably think of integration testing at the same time as https://github.com/square/beancounter/issues/43, as they both might require specific architectural...
We should fail (instead of returning an incorrect) result if find-block lands on current-height - 11. Otherwise, invocations such as `./beancounter find-block "2022-01-01 12:00:00 GMT"` will return a different result...
To ensure reproducible results, we filter some blocks: When computing a balance: Beancounter only computes balances up-to "current height" - 6 blocks. We discard the last 6 blocks + unconfirmed...
We should go back to showing something like this: ``` +---------------+--------------------+-------------------+---------------------+-------+ | TOTAL BALANCE | LAST RECEIVE INDEX | LAST CHANGE INDEX | REPORT TIME | BLOCK | +---------------+--------------------+-------------------+---------------------+-------+ |...
It's possible for an electrum server to have stale data. When we connect to a server, we should do a height check.
Given that the tool can take a few hours in some cases, we should support saving the state / resuming. We need to be careful about not using outdated state...