"inputs and outputs do not balance" - composer and validator inconsistency about ocore HOT 2 CLOSED

The above unit breaks another rule: it has two messages with payments in bytes, which is not allowed.

		if (objValidationState.bHasBasePayment)
			return callback("can have only one base payment");
		objValidationState.bHasBasePayment = true;

The bytes payment doesn't have to be the first but it must be unique. The error message is misleading indeed since the first message is checked first but the unit is invalid anyway. You have to merge the two bytes payments in one message.

from ocore.

I see. I didn't know about that restriction. It's gonna be tricky to combine the base payments and issue an asset in one unit. My goal here is to sweep 1000 bytes from a smart contract and issue 1 asset in exchange all in as single unit, but it appears a difficult task to solve with the current API.

from ocore.