Quote from: shmali on December 04, 2017, 09:54:12 PM

Next, The sender is determined by the first input in the tx. So you can fund the tx from several address if needed, however only the first input in the tx will signal to the Omni protocol who is sending the Omni Assets.

The receiver is chosen/indicated by the last output address that is not the sender. So if you want to send any extra btc change back to yourself or to a different address specify those first.
Signaling The receiver address only needs a fraction of btc, right now we're using 0.00005460 btc as that 'reference output amount'.

I found something relating to this in the code just yesterday - thank you for breaking it down in details!

I will give a try to simply sign the payload you provided. Thank you!

Quote from: shmali on December 04, 2017, 09:54:12 PM

A few more tools/resources that may be of use.

Bitcoin Scripting in general: https://en.bitcoin.it/wiki/Script

One of the Omni Dev's put together this interface for payload creations and commands to use with the Omnicore client: http://builder.bitwatch.co/

And then here is gist that shows how to use the omnicore client to manually create a tx with payload: https://gist.github.com/dexX7/352670c990ebf9ea31d6346a1519eb52

Amazing Thank you for that builder, I didn't find it