use slip10 1.0.1 to better satisfy the trezorlib >= 1.0.1 requirements (the AppImage build works with 1.0.0, but with more recent versions of pip the conflict becomes an error)

update the repo and commit hash to ecash/2.8.9 tag from the Bitcoin ABC repo

factor the token detection into a wallet.has_tokens(coin) method and fix one more thing that could cause accidental spending of ALP tokens (for users who enabled "Spend only fused coins", if a token is sent to the same address as a fused coin)

In D17806#405784, @bytesofman wrote:

TIL coin consolidator is a thing in electrum

how is this used in the GUI? is this just called in normal tx building?

As an additional test I'm also going to try to be in a few CashFusion rounds to confirm no tokens are burned. But I cannot guarantee the tests will be conclusive in a timely manner.

tested with python3.11 (via AppImage)

rebase on D17797 (extracted some changes not directly related to trezor)

my review collided with an update that fixed the issue

This diff somehow pulls blockfitter.cpp into bitcoin-chainstate's dependencies, so you need to add it a second time in CMakeList.txt

feedback + handle case of same transaction added twice without clearing first (don't duplicate outpoints, don't even bother rescanning the transaction)

minor UI improvement (change the greyed out spend action text to tell why the coin is unspendable)

remove a print

support opcode 0x01, write more tests, find out that the op == OpCodes.OP_PUSHDATA4 branch is wrong, fix it

A flynt false positive

add tests for incorrect data length in otherwise valid succession of push ops

make this a move only commit

let's add the headers in a separate diff, so it is clear that no code was changed