it is very easy. the alias solution is max. simple and solid and it has zero side effects on trading.
for the issuer it means just ~20 lines of additional code, that's it. skynet for instance will support this
divi solution later just by traversing the shareholders list, scanning for a divi alias. if found, it is used,
if not, a standard nxt payment is made.
however, multigateway is good too.
Ok, then lets speak a bit more about that json. Im not so much into nxt that i know already what its about.
The json is a action directive that gets triggered when paying out divs?
So lets assume you implement the json, then you can have your bitcoins in your own wallet and how would you send out divs then? The shareholders could get their divs as real btc in their own wallets. Not btc tokens?
Im sorry but im very new to nxt and i did not understand the system so well.
the json example is, as mentioned, a more advanced solution where additional logic could be added but
let's stick with the simple and effective alias path.
you asked (for good reasons) for the possibilities to pay dividends in BTC instead nxt.
here is how skynet will handle this as soon divis and amount reaches an uncomfortable book threshold.
what the issuer do:1. announcing to support additional currency divi support to shareholders and defining alias syntax (like below)
what the shareholder do:1. register an alias e.g. sky2btc1...[1] with account holding the shares (duration: 10 sec. | costs: 1 cent one time)
that's it. nothing more todo. this has also an interesting effect. since this is a free decision, the shareholders are
voting with this alias bridge for constant buy pressure on NXT (due to conversion) or not.
issuer divi payment flow is very simple also:
1. api call for all shareholders and traversing shareholders alias for above mentioned alias prefix (sky2btc)
2. pipe divi payments to alias BTC address (real BTC)
if found or NXT as usual if not
[1] since aliases are unique, a random sequence has to added at the tail.