[ANN] SuperNET NXT asset 12071612744977229797, SUPERNET KMD assetchain in summer

[Valta Crypto]

^You said it. Keep up the good work James!

[1714855968]

1714855968

[1714855968]

1714855968

[1714855968]

1714855968

[jl777]

^You said it. Keep up the good work James!

thanks!
but I am just coding the API
we have almost 100 people in slack, generating around 10000 messages per week!

If you have any skills of any sort, you can help too.

GUI, testing, project management, marketing, etc. All these areas can always use more help. I cant do SuperNET all by myself. It is a team effort.

James

[JohnnyBTCSeed]

[durerus]

James, how high do you estimate the chance for you to win the first bonus? Do you still believe it is possible to tripple IPO price before year's end?

[bassguitarman]

Forum is down

[visual111]

James, how high do you estimate the chance for you to win the first bonus? Do you still believe it is possible to tripple IPO price before year's end?

do you think the finished tech will be worth 3x the price? finished as in, an end user friendly GUI with working protocols


understand what supernet is aiming to do and you will have an answer

[RichardT]

James, how high do you estimate the chance for you to win the first bonus? Do you still believe it is possible to tripple IPO price before year's end?

do you think the finished tech will be worth 3x the price? finished as in, an end user friendly GUI with working protocols


understand what supernet is aiming to do and you will have an answer

Well, releasing the finished tech at the end of this year would really just be the beginning.  I'm almost skeptical that the perceived value will reach 3x by the end of the year, because there will still be a lot of people who have either not heard of or do not understand what SuperNET is.  Not saying that James doesn't deserve his bonus, of course.

I actually think it's more likely it will go 10x by end of 2015, because by that time SuperNET will be much more established and it will have a lot more revenue and dividends coming through.

[windjc]

James, how high do you estimate the chance for you to win the first bonus? Do you still believe it is possible to tripple IPO price before year's end?

do you think the finished tech will be worth 3x the price? finished as in, an end user friendly GUI with working protocols


understand what supernet is aiming to do and you will have an answer

In my opinion, which is nothing more than a best guess, I think Supernet would have to get some significant press on top of a beautiful gui and working protocol to have a shot at reaching James' first goal. Supernet would have to go significantly above its NAV, meaning some speculative value would have to enter the system, because without a significant bull market reversal that fed the alts, the NAV is not going to triple in value anytime soon.

So it will be interesting to see. James has done some remarkable things in short periods of time, and I hope he reaches his goal, not for myself, but for himself, as he deserves it.

[jl777]

The new DB design made it so the old InstantDEX code was not quite right. I ended up rewriting it and most of it is gone! this is good as the less code, the less bugs. Still not fully debugged, but via DHT all orderbooks exist in the cloud

./b SuperNET '{"requestType":"placebid","baseid":"11060861818140490423","relid":"4551058913252105307","volume":"1.01","price":"0.006"}'
./b SuperNET '{"requestType":"placeask","baseid":"11060861818140490423","relid":"4551058913252105307","volume":"1.0","price":"0.0065"}'

You can dynamically create any orderbook between any two assets and the pricing is using arbitrary precision volume and price. this is converted internally to 64bit ints.

./b SuperNET '{"requestType":"orderbook","baseid":"11060861818140490423","relid":"4551058913252105307"}'
./b SuperNET '{"requestType":"orderbook","baseid":"4551058913252105307","relid":"11060861818140490423"}'

By changing the order of the base currency to relative currency, you can flip the orderbook to whichever orientation is more natural to you. Internally, there is only one orderbook with the "key" being (baseid XOR relid)
{
    "key":    "12008998766472701676",
    "baseid":    "11060861818140490423",
    "relid":    "4551058913252105307",
    "bids":    [["0.00600000000", "1.01000000"], ["0.00600000000", "1.01000000"], ["0.00500000000", "1.10000000"], ["0.00500000000", "1.10000000"]],
    "asks":    [["0.00500000000", "1.10000000"]]
}

{
    "key":    "12008998766472701676",
    "baseid":    "4551058913252105307",
    "relid":    "11060861818140490423",
    "bids":    [["200.00000000000", "0.00550000"]],
    "asks":    [["166.66666666667", "0.00606000"], ["166.66666666667", "0.00606000"], ["200.00000000000", "0.00550000"], ["200.00000000000", "0.00550000"]]
}

you can get more info by adding an "allfields":1, the most important is the address of the one making the bid/ask, that way you can directly "negotiate" the trade, so this means you can complete a trade offchain. To do this you need to use the makeoffer API and it will invoke the default tradebot on the other side, so I need to port the tradebots next.

{
    "key":    "12008998766472701676",
    "baseid":    "4551058913252105307",
    "relid":    "11060861818140490423",
    "bids":    [["200.00000000000", "0.00550000", 0, "7581814105672729429"]],
    "asks":    [["166.66666666667", "0.00606000", 0, "7581814105672729429"], ["166.66666666667", "0.00606000", 0, "7581814105672729429"], ["200.00000000000", "0.00550000", 0, "7581814105672729429"], ["200.00000000000", "0.00550000", 0, "7581814105672729429"],]
}

I have only tested this in some simple cases, so not sure how solid it is, but now I can maintain orderbooks for Telepods, so the needed components are coming into place.

James

P.S. Until the BTC bear market is over, I would not expect any big price increase, but there is still chances for this as things can happen very quickly in crypto

[_mr_e]

The new DB design made it so the old InstantDEX code was not quite right. I ended up rewriting it and most of it is gone! this is good as the less code, the less bugs. Still not fully debugged, but via DHT all orderbooks exist in the cloud

./b SuperNET '{"requestType":"placebid","baseid":"11060861818140490423","relid":"4551058913252105307","volume":"1.01","price":"0.006"}'
./b SuperNET '{"requestType":"placeask","baseid":"11060861818140490423","relid":"4551058913252105307","volume":"1.0","price":"0.0065"}'

You can dynamically create any orderbook between any two assets and the pricing is using arbitrary precision volume and price. this is converted internally to 64bit ints.

./b SuperNET '{"requestType":"orderbook","baseid":"11060861818140490423","relid":"4551058913252105307"}'
./b SuperNET '{"requestType":"orderbook","baseid":"4551058913252105307","relid":"11060861818140490423"}'

By changing the order of the base currency to relative currency, you can flip the orderbook to whichever orientation is more natural to you. Internally, there is only one orderbook with the "key" being (baseid XOR relid)
{
    "key":    "12008998766472701676",
    "baseid":    "11060861818140490423",
    "relid":    "4551058913252105307",
    "bids":    [["0.00600000000", "1.01000000"], ["0.00600000000", "1.01000000"], ["0.00500000000", "1.10000000"], ["0.00500000000", "1.10000000"]],
    "asks":    [["0.00500000000", "1.10000000"]]
}

{
    "key":    "12008998766472701676",
    "baseid":    "4551058913252105307",
    "relid":    "11060861818140490423",
    "bids":    [["200.00000000000", "0.00550000"]],
    "asks":    [["166.66666666667", "0.00606000"], ["166.66666666667", "0.00606000"], ["200.00000000000", "0.00550000"], ["200.00000000000", "0.00550000"]]
}

you can get more info by adding an "allfields":1, the most important is the address of the one making the bid/ask, that way you can directly "negotiate" the trade, so this means you can complete a trade offchain. To do this you need to use the makeoffer API and it will invoke the default tradebot on the other side, so I need to port the tradebots next.

{
    "key":    "12008998766472701676",
    "baseid":    "4551058913252105307",
    "relid":    "11060861818140490423",
    "bids":    [["200.00000000000", "0.00550000", 0, "7581814105672729429"]],
    "asks":    [["166.66666666667", "0.00606000", 0, "7581814105672729429"], ["166.66666666667", "0.00606000", 0, "7581814105672729429"], ["200.00000000000", "0.00550000", 0, "7581814105672729429"], ["200.00000000000", "0.00550000", 0, "7581814105672729429"],]
}

I have only tested this in some simple cases, so not sure how solid it is, but now I can maintain orderbooks for Telepods, so the needed components are coming into place.

James

P.S. Until the BTC bear market is over, I would not expect any big price increase, but there is still chances for this as things can happen very quickly in crypto

I've never been sexually arroused by code before.... That's the last time I'll be able to say that.

[yeXIABC]

The new DB design made it so the old InstantDEX code was not quite right. I ended up rewriting it and most of it is gone! this is good as the less code, the less bugs. Still not fully debugged, but via DHT all orderbooks exist in the cloud

./b SuperNET '{"requestType":"placebid","baseid":"11060861818140490423","relid":"4551058913252105307","volume":"1.01","price":"0.006"}'
./b SuperNET '{"requestType":"placeask","baseid":"11060861818140490423","relid":"4551058913252105307","volume":"1.0","price":"0.0065"}'

You can dynamically create any orderbook between any two assets and the pricing is using arbitrary precision volume and price. this is converted internally to 64bit ints.

./b SuperNET '{"requestType":"orderbook","baseid":"11060861818140490423","relid":"4551058913252105307"}'
./b SuperNET '{"requestType":"orderbook","baseid":"4551058913252105307","relid":"11060861818140490423"}'

By changing the order of the base currency to relative currency, you can flip the orderbook to whichever orientation is more natural to you. Internally, there is only one orderbook with the "key" being (baseid XOR relid)
{
    "key":    "12008998766472701676",
    "baseid":    "11060861818140490423",
    "relid":    "4551058913252105307",
    "bids":    [["0.00600000000", "1.01000000"], ["0.00600000000", "1.01000000"], ["0.00500000000", "1.10000000"], ["0.00500000000", "1.10000000"]],
    "asks":    [["0.00500000000", "1.10000000"]]
}

{
    "key":    "12008998766472701676",
    "baseid":    "4551058913252105307",
    "relid":    "11060861818140490423",
    "bids":    [["200.00000000000", "0.00550000"]],
    "asks":    [["166.66666666667", "0.00606000"], ["166.66666666667", "0.00606000"], ["200.00000000000", "0.00550000"], ["200.00000000000", "0.00550000"]]
}

you can get more info by adding an "allfields":1, the most important is the address of the one making the bid/ask, that way you can directly "negotiate" the trade, so this means you can complete a trade offchain. To do this you need to use the makeoffer API and it will invoke the default tradebot on the other side, so I need to port the tradebots next.

{
    "key":    "12008998766472701676",
    "baseid":    "4551058913252105307",
    "relid":    "11060861818140490423",
    "bids":    [["200.00000000000", "0.00550000", 0, "7581814105672729429"]],
    "asks":    [["166.66666666667", "0.00606000", 0, "7581814105672729429"], ["166.66666666667", "0.00606000", 0, "7581814105672729429"], ["200.00000000000", "0.00550000", 0, "7581814105672729429"], ["200.00000000000", "0.00550000", 0, "7581814105672729429"],]
}

I have only tested this in some simple cases, so not sure how solid it is, but now I can maintain orderbooks for Telepods, so the needed components are coming into place.

James

P.S. Until the BTC bear market is over, I would not expect any big price increase, but there is still chances for this as things can happen very quickly in crypto

I've never been sexually arroused by code before.... That's the last time I'll be able to say that.

             






       Our dev to do what two months? lnvestment to who ? The government?

[r3animation]

       Our dev to do what two months? lnvestment to who ? The government?

What? lol

[superresistant]

       Our dev to do what two months? lnvestment to who ? The government?

What? lol

It must be the effect of Chinese alcohol with a snake in the bottle or something like that. He don't know what he's doing.
Don't mind him.

[Este Nuno]

       Our dev to do what two months? lnvestment to who ? The government?

What? lol

I think he meant to respond to windjc.

[crackfoo]

       Our dev to do what two months? lnvestment to who ? The government?

What? lol

It must be the effect of Chinese alcohol with a snake in the bottle or something like that. He don't know what he's doing.
Don't mind him.

I think that's Thai or Laotian. I had some of that, they put cobra's in it. It is good and hits you nicely, so yea, perhaps too much of that stuff

[open82buy]

       Our dev to do what two months? lnvestment to who ? The government?

What? lol

It must be the effect of Chinese alcohol with a snake in the bottle or something like that. He don't know what he's doing.
Don't mind him.

Wow, seeing the words Chinese alcohol reminds me when I was there in 1989, no cars; bicycles everywhere and as for their rice wine!!!!! I am sure some of their brands had anti-freeze in them, a lot of bike accidents and blank/blackout evenings with one hell of a headache on waking. Anyway enough reminiscing and back to cryptos.  

[superresistant]

       Our dev to do what two months? lnvestment to who ? The government?

What? lol

It must be the effect of Chinese alcohol with a snake in the bottle or something like that. He don't know what he's doing.
Don't mind him.

I think that's Thai or Laotian. I had some of that, they put cobra's in it. It is good and hits you nicely, so yea, perhaps too much of that stuff

In Laos/Thailand/Vietnam they use gecko (baby Godzilla).





Strong stuff. You can't code on that.

Wow, seeing the words Chinese alcohol reminds me when I was there in 1989, no cars; bicycles everywhere and as for their rice wine!!!!! I am sure some of their brands had anti-freeze in them, a lot of bike accidents and blank/blackout evenings with one hell of a headache on waking. Anyway enough reminiscing and back to cryptos. 

Yeah let's get back to cryptos...

[PilotofBTC]

The new DB design made it so the old InstantDEX code was not quite right. I ended up rewriting it and most of it is gone! this is good as the less code, the less bugs. Still not fully debugged, but via DHT all orderbooks exist in the cloud

./b SuperNET '{"requestType":"placebid","baseid":"11060861818140490423","relid":"4551058913252105307","volume":"1.01","price":"0.006"}'
./b SuperNET '{"requestType":"placeask","baseid":"11060861818140490423","relid":"4551058913252105307","volume":"1.0","price":"0.0065"}'

You can dynamically create any orderbook between any two assets and the pricing is using arbitrary precision volume and price. this is converted internally to 64bit ints.

./b SuperNET '{"requestType":"orderbook","baseid":"11060861818140490423","relid":"4551058913252105307"}'
./b SuperNET '{"requestType":"orderbook","baseid":"4551058913252105307","relid":"11060861818140490423"}'

By changing the order of the base currency to relative currency, you can flip the orderbook to whichever orientation is more natural to you. Internally, there is only one orderbook with the "key" being (baseid XOR relid)
{
    "key":    "12008998766472701676",
    "baseid":    "11060861818140490423",
    "relid":    "4551058913252105307",
    "bids":    [["0.00600000000", "1.01000000"], ["0.00600000000", "1.01000000"], ["0.00500000000", "1.10000000"], ["0.00500000000", "1.10000000"]],
    "asks":    [["0.00500000000", "1.10000000"]]
}

{
    "key":    "12008998766472701676",
    "baseid":    "4551058913252105307",
    "relid":    "11060861818140490423",
    "bids":    [["200.00000000000", "0.00550000"]],
    "asks":    [["166.66666666667", "0.00606000"], ["166.66666666667", "0.00606000"], ["200.00000000000", "0.00550000"], ["200.00000000000", "0.00550000"]]
}

you can get more info by adding an "allfields":1, the most important is the address of the one making the bid/ask, that way you can directly "negotiate" the trade, so this means you can complete a trade offchain. To do this you need to use the makeoffer API and it will invoke the default tradebot on the other side, so I need to port the tradebots next.

{
    "key":    "12008998766472701676",
    "baseid":    "4551058913252105307",
    "relid":    "11060861818140490423",
    "bids":    [["200.00000000000", "0.00550000", 0, "7581814105672729429"]],
    "asks":    [["166.66666666667", "0.00606000", 0, "7581814105672729429"], ["166.66666666667", "0.00606000", 0, "7581814105672729429"], ["200.00000000000", "0.00550000", 0, "7581814105672729429"], ["200.00000000000", "0.00550000", 0, "7581814105672729429"],]
}

I have only tested this in some simple cases, so not sure how solid it is, but now I can maintain orderbooks for Telepods, so the needed components are coming into place.

James

P.S. Until the BTC bear market is over, I would not expect any big price increase, but there is still chances for this as things can happen very quickly in crypto

I've never been sexually arroused by code before.... That's the last time I'll be able to say that.

You still haven't been, there's no code there.

[TwinWinNerD]

TL;DR

summary pls

[stereotype]

TL;DR

summary pls

A random walk, time-travelling, dream-catcher moment, in the Nxt movie, i think.