add test for tip header too
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jul 11 2024
remove unnecessary bridge
Jul 10 2024
Build Bitcoin ABC Diffs / Diff Testing (preview-e.cash) passed.
Preview is available at http://54.39.104.128:41367 for the next 60 minutes.
@bot preview-e.cash
trigger a diff build
@bot cashtab-tests
rebase, apply suggestions, fix json compilation errors
Jul 9 2024
note: tests are passing locally, CI failure does not seem related to this diff. Unable to parse issue from log
rebase
README patch per recommendation
add test case for Script.fromAddress use as leftover (change) output
Can you add a test case that uses Script.fromAddress for the change output as well ?
Otherwise the code LGTM
Jul 8 2024
In D16428#371852, @Fabien wrote:OK I get a better sense of what API you're trying to build then. I think creating the new type is the wrong approach because it makes the API inconsistent from the callsite perspective. You can specify any output as an TxBuilderAddress but the change output has to be a Script ? It is simpler imo to require the callsite to use Script.fromAddress() every time it uses an address: it's explicit and consistent because you will do that for the change output as well. It avoids the issue "address vs script as a key but not both" also which makes the code more robust by design.
What do you think ?
do not support new TxOutputAddress type, instead require Script.fromAddress() at callsite