Alexander Chepurnoy

@greenhat I moved boxes-to-spend check before outputs(w. creationHeight) check. Thus in case of empty boxesToSpend error would be "Missing inputs: ..."

Any details on the wallet? How many unspent outputs there?

> @kushti I think you misunderstood the logic behind migration, I described it here [#1668 (comment)](https://github.com/ergoplatform/ergo/issues/1668#issuecomment-1079763327) ... we migrate the ids at the boot time and then we type-safely work...

@pragmaxim made custom testing, no results returned for old scans

@guybrush do you have custom scans registered ?

@pragmaxim some earlier PR maybe then, I haven't tested payment/send in the presence of custom scans for a while

Please update the nodes to 4.0.30+ (better, 4.0.31). There were a couple of bugfixes in 4.0.28 for known cases when node may stuck (see https://github.com/ergoplatform/ergo/releases/tag/v4.0.28 for details). Likely, the issue...

So the node is stuck at some height for like 15 minutes then catching up ?

Registers are serialized, so box id should change when registers are added or removed. Where do you get this error? Can't find such a message in the sigmastate or this...

> I can take this one yes, please. Assigned