str4d
str4d
I personally use xxdiff, and AFAICT most merge tools support being called on the command line with `name dir1 dir2`, so generalizing the script in this way makes adding other...
At present, we only track what is in the UTXO set at the time that UTXO information is requested from the light wallet server. This is sufficient for shielding funds,...
As part of enabling wallets to track multiple candidate chain tips (instead of implementing rewind logic for reorgs), it is necessary to track multiple alternative evolutions of the commitment trees...
Both `zcashd` and `zcash_client_*` build their state around a canonical chain tip. When a reorg happens, that state is rewound to undo the effects of the old chain, and then...
zcash_primitives: Rework the transparent bundle builder to be more like the shielded bundle builders
The main pattern is the same: construct a `Builder`, add spends and outputs, build a `Bundle`, and apply signatures. However, there are some annoying API differences that cause problems at...
_If_ we decide to support drop-in RPC methods, then we will need to implement those APIs for the wallet service.
Currently `scan_cached_blocks` takes a `BlockSource` and a `WalletWrite`, and combines their information to scan a given range of blocks. It would be useful to clearly denote the dataflows here, as...
We have a rudimentary `Script` type there that is only used for P2PKH and very specific P2SH usage. We will need to expand and enhance its functionality in order to...
In addition to secp256k1 key material (both derived and imported), this includes the scripts that are necessary to be exposed when spending P2SH outputs (for e.g. transparent Bitcoin-style multisig), and...