very cool, congrats kushti.
|
|
|
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.
|
|
|
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.
|
|
|
here is another, more complex solution.
send a plain text message to yourself, containing a 'action directive' json. (this is not a valid json, just to show what i mean)
{
{ asset: skynet action: { split: curr } accounts: {
{ curr: btc, acc: 1234567, pct: 50 } { curr: nxt, acc: 1234567, pct: 25 } { curr: ltc, acc: 1234567, pct: 25 }
}
}
{ asset: supernet action: { split: acc, pct: equal } curr: btc accounts: {
{ 1234567, 345678, 4567890 } }
} ... }
this way nxt could add complex but easy divi handling on user side. a client plugin could provide this for the shareholder while asset issuers could read it to handle directives without tracking issues.
just an idea. however, i am sure nxt needs something like this sooner or later. a handfull succesfull assets, generating revenue streams outside crypto (fiat) could run quickly into conversion/book draining problems.
|
|
|
perhaps this is another, simple and solid solution for external divi payments.
shareholder register an alias pointing to a BTC address for dividends. no need for tracking ownership now. query the standard api for shareholders as usual when divis are triggered and pay out directly in BTC to the alias target.
target address can be modified also if needed. this approach can be used to handle any coin for any divis. alias could be like this: divi2btc1... or divi2ltc1...
would cost one time 1 cent for a schareholder but it's worth and very flexible.
ps: an divi2nxt... could be use to redirect divi payments into a cold storage for instance.
|
|
|
a gold/silver backed neodrachma, would be a perfect timing now.
|
|
|
great feature, thx kushti.
|
|
|
it's not all about money but punishment. greece has to suffer because left wing is getting stronger in south europe. a second greece in spain (podemos) would be a nightmare for brussels and elections are end this year.
SYRIZA came in to power in Greece, because it was the mainstream parties who destroyed the Greek economy. Now they are left with $350 billion in net debt, and a ruined economy. And regarding Spain, Podemos is not leading the polls right now. Currently, they are at 3rd or 4th position. However, there is a small chance that they will be able to form a coalition government with one of the mainstream parties. if you take a closer look to this graph you can see how fragil the situation in spain is. podemos jumped from off in no-time to pp level. i wouldn't call this a small chance. https://upload.wikimedia.org/wikipedia/commons/7/7d/ElectionMonthlyAverageGraphSpain2015.pngand greece is much higher in debt if you add target2, not talking about the 4T in derivates.
|
|
|
it's not all about money but punishment. greece has to suffer because left wing is getting stronger in south europe. a second greece in spain (podemos) would be a nightmare for brussels and elections are end this year.
|
|
|
The Greek Government's gamble with the future of its country / Europe doesn't seem to be working. The IMF and Germany have hardened their stand. A Grexit doesn't seem so unlikely now.
what future you are talking about, rising debt service until eternity?
|
|
|
The latest available there is 8u33 which has 13 security vulnerabilities currently (3 of them rated 10/10 for severity): http://www.cvedetails.com/vulnerability-list/vendor_id-93/product_id-19116/Oracle-JDK.htmlSo everyone running the latest NRS on an ARM device (Raspberry Pi, etc) is likely open to several severe security vulnerabilities. ARM users should be instructed to shut down their nodes until Oracle releases something newer than 8u40. NRS updates should have been delayed until a secure ARM binary is available from Oracle. This was not handled responsibly from a security standpoint. can't remember when jdk ever was bug free (like many other complex dev-stacks). however, since i am not a java coder but running an arm node, it would be helpfull if you could point me to a more concret security problem or better to a non theoretical attack vector, where running the arm node isn't secure. if this is a real world security problem it has to be adressed ofc.
|
|
|
Any word on what's going on with the exchanges? Disabled on bittrex and I tried to withdraw from Cryptsy to a new wallet and nothing coming although cryptsy saying deposit sent.
New to NXT and setting it up is proving a headache, how does one get their first NXT to activate an address?
If you just need to announce your public key, I suggest http://jnxt.org/keyIf you need some faucet nxt also, there are some sites for that, but I don't remember them off the top of my head, probably free nxt something.. Thanks that worked However Cryptsy NXT withdrawals are broken and bittrex disabled NXT. What's going on? there was a big, mandatory update at block 445,000, which brought tons of new features to nxt, so i guess the exchanges ensuring a smooth transition.
|
|
|
as long it is not an asymptotical 97% there is hope.
|
|
|
i think NXT has reached a new SCAM level with its upcoming 1.5 release...
i think the nxt devs are just pumping up THE JAM nxt by releasing new versions to keep up with the hype. epic scam in the making.... don't trust it...
do your own homework of course... try installing nxt and judge for yourself.
sure, here we go... https://www.youtube.com/watch?v=9EcjWd-O4jI
|
|
|
But it was the last Nxt Barbecue and the bacon writes NXT on the grill! Looks good, isn't it ?
ha! doesn't saw this, good one Ludom lol, really! You didn't see it? Would understand if it was this written in bacon ^^^ you an do this one this year Ludom harhar, noop. didn't see this. i guess i was mainly contentrated on the anti-yummy white lines in the meat...
|
|
|
But it was the last Nxt Barbecue and the bacon writes NXT on the grill! Looks good, isn't it ?
ha! doesn't saw this, good one Ludom
|
|
|
cool initiative and a beautiful location for this event but really Ludom, you should change this bbq image. this raw pork neck something doesn't fit well i think ;-)
|
|
|
very good! any near future plans to accept creditcard/recurring payments? (would be very usefull for crypto/software subscriptions)
|
|
|
|