Greg Hill

This is now mostly a non-issue, and as @sander2 states we can batch in the client - closing for now

See also: - https://github.com/interlay/interbtc/issues/605 - https://github.com/interlay/interbtc/issues/482 - https://github.com/interlay/interbtc/issues/481

Closes #594

https://github.com/interlay/interbtc/commit/da3b55e793675a06fe291d0a65a7fa8845e55575

Before we merge this, we should consider the following proxy types (requested): - claiming rewards - transfers - issues / redeems

> Wouldn't switching over without migration lead to their KINT/INTR being locked forever? And wouldn't it lead to problems when existing collators quit, as we would attempt to unlock vKINT...

@sander2 do you think we should explicitly clear storage (for refund) in the migration?

Linking my issue on [ledgerjs](https://github.com/LedgerHQ/ledgerjs/issues/516) for relevance; incorrect signature produced for tx with one segwit input.

Thanks for the info @LarryRuane! Let me look into this approach and get back to you.

Please see the discussion in #33, recommendations / contributions would be appreciated!