ScriptBuilder emitting trimmed hexstring about neo-lux HOT 2 CLOSED

I was investigating this now after reading the issue, as I checked that transaction, got the bytecode from it here:

https://neoscan-testnet.io/transaction/78a1552b1a4cf1eb04a9cfa4998965603a0beb148a80354f0d2d58ef5aeb58c2

Then I ran it through the official NEO VM, and the "amount" decodes correctly as a BigInteger with value 100000000000.

Also the code I'm using to include a BigInteger in the transaction comes from the official source too:
https://github.com/neo-project/neo-vm/blob/master/src/neo-vm/ScriptBuilder.cs#L48
The padding should make no difference and might be a red herring, the problem could lie in something else.

Could be a temporary network problem that made the tokens being reported as 0. I will investigate this further.

from neo-lux.

Fixed token transfer, in the end there were 3 different problems affecting like, like lack of nonce added to each tx meaning repeated transfers from same address with same quantity would fail, also for some reason the order of the script parameters was incorrect, just even if tx would get accepted it would fail at VM level.

from neo-lux.