Topic: [ANN] SuperNET NXT asset 12071612744977229797, SUPERNET KMD assetchain in summer - page 59. (Read 736772 times)

Crypto is not a 0-sum game. Blockchain-networks are currently a duopoly with Super being a head of the game. Supers success will contribute to Blocknet's success. They have slightly different approaches but the end service is very similar. Who knows maybe in the future coins will benefit from using both protocols but for different applications.
I think even the devs of these two protocols doesn't entirely fathom the disruptive impact of what they are currently working on. This and the Ether+ADEPT project will pave the way for internet of things and distributed computing.
The Fan culture of crypto sometimes resembles the mentality of football hooligans rather than looking at the bigger picture. Let's be better than that.
Congrats to both Super and Fibre from a Block supporter.

Welcome everyone

You can catch up with most important info here https://slack-files.com/T02PXPVUF-F03DM47DB-f06e9352fd

We have fibre channel in supernet slack already

Cheers, the future is bright

FibreOS is pretty unique, it is a feature I never even thought of. So that is quite a rare thing to happen
and with Windows still around, it is clear that the world needs a way to create a safe place for crypto wallets that is accessible to Windows users, but not running under windows

James

Fantastic news

I can confirm this. It is hard to find coins with real dev teams and I am glad to have FIBRE joining SuperNET

James

superNET is officially welcoming FIBRE as its latest CORE coin from today on,  their development team will be actively contributing in the expansion of our network, and integrating their innovative tech to the already  superb superNET powerhouse.

superNET is happy to receive such a serious and professional team to the family. May the future bring great things for us all.

Eth.

We have first submission for the InstantDEX bounty. this starts the clock, so there is 24hrs for the other submissions

https://vid.me/kIcS

James

added a "gui" field so we can track what GUI people are using, maybe even some revshare to the most popular third party GUI's

also a "quoteid" field to allow realtime propagation of orderbooks status of other nodes. unfunded order detection to prevent wasting time on order match attempts that are sure to fail

some other minor things, but it is getting down to the small things for the main functionality. Just need GUI release so it can be tested and find all the bugs

James

pushed a version that supports cancelquote and also automatches bids and asks. with this InstantDEX core API is feature complete other than automatching hybrid orderbooks. but I need to get bug reports back for all the simpler cases before it makes sense to finalize that part. So I will start on the getsignal API


James

Big Players Of The Future, welcome
https://bitcointalksearch.org/topic/big-players-of-the-future-979561

good progress. got asset <-> asset swap to do all the required error checks and then matchup and even make a balancing payment so everything adds up properly.

takes 7 NXT tx to do an asset <-> asset swap and 5NXT in InstantDEX fees, so a cost of 5.5NXT and 6.5NXT to the two traders.

For the simpler asset <-> NXT case it is 4 NXT tx for 4.5NXT cost per trader

The hybrid case can be up to 11 NXT tx, but it would only make sense if the net cost for the extra trades and extra 2.5NXT gets you a better effective price. For now, I will skip this case and work on making the order matching easier, eg. make placebid/placeask automatically generate a makeoffer2

Depending on the relative mix of order types, it seems we will get 5 to 7.5 NXT of InstantDEX fees and NXT itself will get 4 to 11 txfees. At the high end of daily order levels, the yield of NXT will go to ~10% per year.

Since doing a trade with each orderbook entry incurs trade costs, I will calculate a metric for all the eligible trades and choose the one closest to optimal. currently only trades that are for 75% or more of the requested volume and within 0.1% of the price are eligible. If there are no such orders, then it will get passed through.

I think this is a decent initial solution. Fancier things like combining multiple quotes from the same user, etc. I will leave for later. Better to get something basic working first

James

https://nxtforum.org/general-discussion/confused-about-supernet-multigateway-instantdex-atomic-bitcoindark-co/msg167243/#msg167243 has more details on the asset <-> asset swap

found a few more unhandled cases for the "simple" asset/NXT
but I think now it is pretty complete so what is left are the automatic creation of halflegs

assetA <-> assetB needs to become assetA -> NXT + NXT -> assetB, and assetB -> NXT + NXT -> assetA

basically the same thing you (and the other trader) would have to do to sell your asset and buy the other asset

Once this is debugged, then all the non-hybrid cases will be ready for more thorough testing, eg. assets with 0 decimals, 8 decimals, etc.

Then the hybrid case is essentially a pair of normal cases, with possibly a balancing payment needed if things are too out of balance.

This is taking so much time (all week!) because all the cases look reasonable, but it is very easy to get the price upside down, which is a very big problem. So I am having to test each possible permutation. Once I get through this rough patch, then it will be adding some more error checking (user settable minconfirms), historical stats and signals/price  data

So my goal is to be at a point where InstantDEX is in maintenance mode for me this weekend. We have put together a team to start testing it more thorougly and I hope the GUI is soon. But it is good I am a bit ahead of the GUI as I can work on enhancing the network security and also do some of the easier things like more signals

James

I put error checks for outofband pricematches, so they are rejected.
block 373464 has txid 14565979118655674082, which is the first successful trigger tx for an InstantDEX trade.

I did 72NXT for 1 coinoUSD

1424647629882861488 is the ask, it is in the unconfirmed trades along with 8698983672084812764 for the fee and 11440344300163450416 is the matching bid.

These tx are done for a few minutes now, even though NXT is on a long block. so when the new block comes in they should all get confirmed. yes and they just did!

Now I can move to debugging the other ordermatch cases.

James

###
for those curious about how atomic and InstantDEX trade can be while at the same time being fast, https://nxtforum.org/index.php?topic=8535.msg166751#msg166751 is a good discussion

Using NXT it is possible to setup the fastest decentralized trading, literally seconds and the trade is completed. Also, contrary to what anybody says InstantDEX is FULLY decentralized.

I even made a diagram: [InstantDEX] <-> (NXT assets) <-> MGW <-> native crypto

so you can see from the pretty picture above that InstantDEX is dealing purely with the NXT asset abstraction layer. Of course some assets are centralized, some are multisig backed crypto deposits, others are whatever thet are. InstantDEX is dealing with assets and NXT itself for now. Once this is solid then I will add more methods of trade matching

let us all hope they will process things...

MY Supernet still not shown up from BTE-R but the withdrawal is showing as processed on their site, all my Neodice and other dividends have come through ok. I'm sending them to a NXT wallet. any help please it is over 48 Hours now.

Can't wait for InstantDEX and Jay 

Litewallets will bring SuperNET to the masses.

Matthew

what is this?

After much troubles:

6896683649204647244 which triggered all three trades in block 32701 14538633590799539701

13096393609126587603 and 4709644894619028652 and 3507227284564623028

The first one was a 2.5 NXT fee that acted as a trigger for the other three. One of them was a 2.5 NXT fee for the other acct and the remaining two are NXT AE orders that exactly matched each other, so of course only half got filled as it wasnt in between the bid/ask like it should be.

So still a bug with choosing the right price, but this is small matter considering what I have had to deal with so far. It completed as quickly as I  posted the curl command on one window and before I could click to the other window, the trade was finalized!

Not out of the forest of complications yet, but with the makeoffer2 all legs (and halflegs) are matched NXT AE bid/ask so solving this is 90%.

the important thing to note is that with this approach, the worst thing that happens is what happened with this trade, eg. one side gets their half filled and the other side is just posting a bid on the AE. When I fix the price matching bug, this will be a very rare case, but even in such rare cases (block longer than 10 or 20 minutes, evil block generator not accepting your half and then draining their acct, race condition where trigger is executed but some or all dependent tradelegs dont get filled)

When I get the jnxt block time predictor then the timing issue will be gone and with both sides essentially instantly negotiating the trade sequence, the evil block generator is the case most likely. However why would a hacker bother with messing with half a trade when it is just a marketrate swap? Especially since the cost is not being able to make any new blocks for almost 2 days and it only works if they have a trade happening for a block they generate.

So there are no hostage scenarios that are possible with the timelocks on multisigs or one transfer done without any compensation, and with the worst that can happen being an unmatched halftrade I feel comfortable with this trade clearing. there are cases for assets without decimals where the original makeoffer method is required to achieve effective decimal pricepoints and its advantage is also that it doesnt require any NXT in reserve to conduct the trades. I think I will need to cap the value of such makeoffer trades just to prevent any large exposure to the above rare case and most assets have decimals so this is not a large percentage of assets.

Now onto fixing the matched price and debugging the more complicated cases.

James

P.S. I realized the pricematch "bug" was because I used a hardcoded price from a couple days ago. so this is pilot error, but I should automate the price selection