This change was inspired by #1984 - the underlying call to ListUnspent supports a (min, max) range so it makes sense that the WalletController interface can also support this; a default no-maximum can be expressed using a MaxInt32 value.
This change was inspired by #1984 - the underlying call to ListUnspent supports a (min, max) range so it makes sense that the WalletController interface can also support this; a default no-maximum can be expressed using a MaxInt32 value.