Topic: NXTsubatomic - atomic crosschain exchange & NXTatomic - atomic NXT tx swap (Read 36596 times)

jl777 · « **on:** April 18, 2014, 02:06:48 am »

I wasnt feeling too well today, so I didnt want to mess with multigateway. I ended up with a crazy idea that maybe just means I am really sick and delusional, or I have come up with a way to implement atomic cross chain exchanges!

Before getting too excited, I need a volunteer who has a Mac. I want to test LTC <-> DOGE atomic exchanges, so you need to have both litecoin and dogecoin wallets installed with the following in the conf files:

/Users/<your username>/Library/Application Support/Dogecoin/dogecoin.conf
/Users/<your username>/Library/Application Support/Litecoin/litecoin.conf

server=1
rpcuser=dogecoinrpc
rpcpassword=<wallet will tell you a password to use>
txindex=1

It will be totally user unfriendly to setup and you will have to manually input the trade parameters. I just want to verify that this method really works.

Since its not implemented as the usual atomic methods (from what I can tell, the current miners wont even relay those tx's), I am calling this "NXTsubatomic" exchange. If I am right, it will work with the current miners for most all the bitcoind forks.

PM me if you are willing to be a guinea pig

James

fanaticalfishing · « **Reply #1 on:** April 18, 2014, 03:22:22 am »

Quote from: jl777 on April 18, 2014, 02:06:48 am

I wasnt feeling too well today, so I didnt want to mess with multigateway. I ended up with a crazy idea that maybe just means I am really sick and delusional, or I have come up with a way to implement atomic cross chain exchanges!

Before getting too excited, I need a volunteer who has a Mac. I want to test LTC <-> DOGE atomic exchanges, so you need to have both litecoin and dogecoin wallets installed with the following in the conf files:

/Users/<your username>/Library/Application Support/Dogecoin/dogecoin.conf
/Users/<your username>/Library/Application Support/Litecoin/litecoin.conf

server=1
rpcuser=dogecoinrpc
rpcpassword=<wallet will tell you a password to use>
txindex=1

It will be totally user unfriendly to setup and you will have to manually input the trade parameters. I just want to verify that this method really works.

Since its not implemented as the usual atomic methods (from what I can tell, the current miners wont even relay those tx's), I am calling this "NXTsubatomic" exchange. If I am right, it will work with the current miners for most all the bitcoind forks.

PM me if you are willing to be a guinea pig

James

Hey James,
Im going to try and load Mac OS on a virtual machine. then I can help.

chanc3r · « **Reply #2 on:** April 18, 2014, 07:49:49 am »

BTW I forgot to mention - I'm on a mac

I'll get a bit of DOGE & LITE today once I've done the other stuff.

bitcoinpaul · « **Reply #3 on:** April 18, 2014, 09:23:46 am »

jl777 · « **Reply #4 on:** April 21, 2014, 05:22:06 pm »

Sorry for the delay. Low level functionality has been coded and mostly debugged. About to start debugging the actual subatomic transfer sequence. chanc3r has even reviewed the code and it seems I wasnt in a fever induced delusion the other day

More later today

James

rdanneskjoldr · « **Reply #5 on:** April 21, 2014, 08:14:44 pm »

swartzfeger · « **Reply #6 on:** April 22, 2014, 07:54:54 pm »

Quote from: jl777 on April 21, 2014, 05:22:06 pm

Sorry for the delay. Low level functionality has been coded and mostly debugged. About to start debugging the actual subatomic transfer sequence. chanc3r has even reviewed the code and it seems I wasnt in a fever induced delusion the other day

More later today

James

james, I PMd you. I'm back in the saddle after a few days delay. My .confs are properly set and ready to go if you still need a Mac guinea pig.

jl777 · « **Reply #7 on:** April 22, 2014, 08:17:46 pm »

Quote from: swartzfeger on April 22, 2014, 07:54:54 pm

Quote from: jl777 on April 21, 2014, 05:22:06 pm
Sorry for the delay. Low level functionality has been coded and mostly debugged. About to start debugging the actual subatomic transfer sequence. chanc3r has even reviewed the code and it seems I wasnt in a fever induced delusion the other day

More later today

James

james, I PMd you. I'm back in the saddle after a few days delay. My .confs are properly set and ready to go if you still need a Mac guinea pig.

Good timing!
I am seeing subatomic exchanges now. Just need to get all the satoshis exact

Hope to be able to make a very, very rough release in a few hours.
It will only be for LTC and DOGE for now

You will need to know your IP
my code will generate a new NXT acct, you will need to give it some testNXT
also, I know this is horrible, but for now you need to change your LTC and DOGE wallet passwords to the NXT acct #. Didnt have time to come up with a clean solution for that.

Once it is all setup, 127.0.0.1:7777 will bring up a form with the following fields:
Subatomic trade
your IP address:
source coin:
source amount:
source coinaddress:
dest coin:
dest amount:
dest coinaddress:
NXT address you are trading with:

You need to find the other party who will need to fill out the form with the exact mirror image values.

After you both submit the form and the AM's are processed, it will start the process. Not much error checking and everything has to be all happy, so dont do any large trades. It is on our testnet, but using real LTC and DOGE. For the first release, I will disable the actual broadcasting of transactions so it wont actually send funds.

Once it looks good enough, then I can activate that part.

James

Daedelus · « **Reply #8 on:** April 22, 2014, 08:32:43 pm »

Go guys go!

Will this be a first, the first atomic cct?

Also, Nxtsubatomic is high on my glossary to do list

jl777 · « **Reply #9 on:** April 22, 2014, 08:38:52 pm »

Quote from: Daedelus on April 22, 2014, 08:32:43 pm

Go guys go!

Will this be a first, the first atomic cct?

Also, Nxtsubatomic is high on my glossary to do list

Since its not actually atomic, but subatomic, not the first atomic
However, it could well be the first subatomic crosschain exchange

James

chanc3r · « **Reply #10 on:** April 22, 2014, 09:23:39 pm »

Quote from: jl777 on April 22, 2014, 08:17:46 pm

Quote from: swartzfeger on April 22, 2014, 07:54:54 pm
Quote from: jl777 on April 21, 2014, 05:22:06 pm
Sorry for the delay. Low level functionality has been coded and mostly debugged. About to start debugging the actual subatomic transfer sequence. chanc3r has even reviewed the code and it seems I wasnt in a fever induced delusion the other day

More later today

James

james, I PMd you. I'm back in the saddle after a few days delay. My .confs are properly set and ready to go if you still need a Mac guinea pig.
Good timing!
I am seeing subatomic exchanges now. Just need to get all the satoshis exact

Hope to be able to make a very, very rough release in a few hours.
It will only be for LTC and DOGE for now

You will need to know your IP
my code will generate a new NXT acct, you will need to give it some testNXT
also, I know this is horrible, but for now you need to change your LTC and DOGE wallet passwords to the NXT acct #. Didnt have time to come up with a clean solution for that.

Once it is all setup, 127.0.0.1:7777 will bring up a form with the following fields:
Subatomic trade
your IP address:
source coin:
source amount:
source coinaddress:
dest coin:
dest amount:
dest coinaddress:
NXT address you are trading with:

You need to find the other party who will need to fill out the form with the exact mirror image values.

After you both submit the form and the AM's are processed, it will start the process. Not much error checking and everything has to be all happy, so dont do any large trades. It is on our testnet, but using real LTC and DOGE. For the first release, I will disable the actual broadcasting of transactions so it wont actually send funds.

Once it looks good enough, then I can activate that part.

James

Jay - if i'm still awake and on our IRC channel - will run the other half...
Ian

jl777 · « **Reply #11 on:** April 22, 2014, 09:53:50 pm »

209.126.71.170/NXTsubatomic_v00.zip

Its there!

James

jl777 · « **Reply #12 on:** April 22, 2014, 10:06:49 pm »

209.126.71.170/NXTsubatomic_v00.zip

Is Mac only and does not actually submit any tx, but it gets them all ready and prints them out.

no fancy GUI, just text HTML form that appears at 127.0.0.1:7777

You need to coordinate with the other party and make sure all the fields matchup. Since it is such a pain to setup a trade, once one is setup, each time you restart the program,it will attempt to do it again.

The NXT acct it uses is the one that it prints in the text window. Dont forget it to send it some testNXT and make sure to change your wallet passwords to this NXT addr.

Once you get a trade matched up, it will startup pretty fast. You can use the status button and then refresh the page or just watch the text window

I am sure many things wrong, just wanted to get this out and tested on network connections that are not mine. I am not able to accept incoming network connections, so it makes things kind of hard to fully debug

One of the two sides of the trade becomes the initiator and drives the process, however there is a race condition and it is possible that both will start as initiators at the same time. I couldnt recreate this due to my network. I think it will handle it OK.

James

chanc3r · « **Reply #13 on:** April 22, 2014, 10:19:38 pm »

Quote from: jl777 on April 22, 2014, 09:53:50 pm

209.126.71.170/NXTsubatomic_v00.zip

Its there!

James

I have it running... now i need a partner...

I will be on freenode.net #nxtsubatomic for a while if anyone else wants to play...

WARNING....

Quote from: jl777 on April 22, 2014, 08:17:46 pm

I know this is horrible, but for now you need to change your LTC and DOGE wallet passwords to the NXT acct #. Didnt have time to come up with a clean solution for that.

If you use this NXT Account number printed here in the terminal window as the passphrase for your wallets REMEMBER TO STORE IT!!! or lose access to your DOGE and LITE wallets!!

*EDIT: THIS IS RUNNING ON TESTNET - so you need to start an NRS TestNet also... so subatomic can connect to it as it uses NXT AM!!

*EDIT: AND WE HAVE LIFTOFF - this is the screen up and running....

here is the JSON for the subatomic request (ip part blanked

)

Quote

Uri-Args: = {"requestType":"subatomic_trade","NXT":"8989816935121514892","coin":"LTE","amount":"0.1","coinaddr":"LVNE1nxeiAzx72MwY8rxw22V9BdTgNsSz6",
"senderip":"xx.xxx.44.220","destNXT":"3940521100773952218","destcoin":"DGE","destamount":"1000","destcoinaddr":"DEwmsmYq3rzbMdmM6xkJpNPtPg5CS1YSNf"}

Daedelus · « **Reply #14 on:** April 22, 2014, 10:29:29 pm »

This must be what watching the first moon landing was like...

jl777 · « **Reply #15 on:** April 22, 2014, 10:37:10 pm »

I hope it wont be confusing if I added NXTatomic to NXTsubatomic
NXTatomic will be "atomic" exchange of any two NXT tx
interface will be horrible, eg. you need to create the transaction bytes for both halves of the atomic pair, best to use http://127.0.0.1:6876/test

Then it will be like the NXTsubatomic matching, I dont think this will take 4 days like NXTsubatomic did

James

P.S. If anybody can figure out how to link the NXTatomic with NXTsubatomic, please post! That would really be the holy grail of crypto

chanc3r · « **Reply #16 on:** April 22, 2014, 10:50:22 pm »

Quote from: jl777 on April 22, 2014, 10:37:10 pm

I hope it wont be confusing if I added NXTatomic to NXTsubatomic
NXTatomic will be "atomic" exchange of any two NXT tx
interface will be horrible, eg. you need to create the transaction bytes for both halves of the atomic pair, best to use http://127.0.0.1:6876/test

Then it will be like the NXTsubatomic matching, I dont think this will take 4 days like NXTsubatomic did

James

P.S. If anybody can figure out how to link the NXTatomic with NXTsubatomic, please post! That would really be the holy grail of crypto

Is this too simple??

Post NXT Sub-Atomic offers as an AM from account making the offer - single AM containing all offers (JSON format)
People can scan and bind... basically accepting the offered Subatomic parameters into their subatomic form...
Then initiate TX? along as the Subatomic making the offer is ready and waiting it should proceed???

jl777 · « **Reply #17 on:** April 22, 2014, 11:04:55 pm »

Quote from: chanc3r on April 22, 2014, 10:50:22 pm

Quote from: jl777 on April 22, 2014, 10:37:10 pm
I hope it wont be confusing if I added NXTatomic to NXTsubatomic
NXTatomic will be "atomic" exchange of any two NXT tx
interface will be horrible, eg. you need to create the transaction bytes for both halves of the atomic pair, best to use http://127.0.0.1:6876/test

Then it will be like the NXTsubatomic matching, I dont think this will take 4 days like NXTsubatomic did

James

P.S. If anybody can figure out how to link the NXTatomic with NXTsubatomic, please post! That would really be the holy grail of crypto

Is this too simple??

Post NXT Sub-Atomic offers as an AM from account making the offer - single AM containing all offers (JSON format)
People can scan and bind... basically accepting the offered Subatomic parameters into their subatomic form...
Then initiate TX? along as the Subatomic making the offer is ready and waiting it should proceed???

I was planning on something like that. It is very similar to NXTorrent listings and I might actually merge all offer type things into a single API, not sure yet.

With subatomic, we have effectively atomic crypto <-> crypto
with NXTatomic, we have NXT tx <-> NXT tx
Now toss in multigateway crypto assets and NXT atomic becomes crypto asset <-> NXT/crypto asset

So, an external crypto wallet <-> multigateway <-> NXT acct is an atomic path, but multigateway is in the middle. I want a trustless way to do:
external crypto <-> NXT assets

Hmmm....
...
OK, I have an idea. More later

James

jl777 · « **Reply #18 on:** April 22, 2014, 11:06:54 pm »

Quote from: chanc3r on April 22, 2014, 10:19:38 pm

Quote from: jl777 on April 22, 2014, 09:53:50 pm
209.126.71.170/NXTsubatomic_v00.zip

Its there!

James

I have it running... now i need a partner...

I will be on freenode.net #nxtsubatomic for a while if anyone else wants to play...

WARNING....

Quote from: jl777 on April 22, 2014, 08:17:46 pm
I know this is horrible, but for now you need to change your LTC and DOGE wallet passwords to the NXT acct #. Didnt have time to come up with a clean solution for that.

If you use this NXT Account number printed here in the terminal window as the passphrase for your wallets REMEMBER TO STORE IT!!! or lose access to your DOGE and LITE wallets!!

*EDIT: THIS IS RUNNING ON TESTNET - so you need to start an NRS TestNet also... so subatomic can connect to it as it uses NXT AM!!

*EDIT: AND WE HAVE LIFTOFF - this is the screen up and running....

here is the JSON for the subatomic request (ip part blanked )
Quote
Uri-Args: = {"requestType":"subatomic_trade","NXT":"8989816935121514892","coin":"LTE","amount":"0.1","coinaddr":"LVNE1nxeiAzx72MwY8rxw22V9BdTgNsSz6",
"senderip":"xx.xxx.44.220","destNXT":"3940521100773952218","destcoin":"DGE","destamount":"1000","destcoinaddr":"DEwmsmYq3rzbMdmM6xkJpNPtPg5CS1YSNf"}

It needs to be exactly "LTC" and "DOGE" or it wont match up with the coin daemons

chanc3r · « **Reply #19 on:** April 22, 2014, 11:11:12 pm »

Quote from: jl777 on April 22, 2014, 11:06:54 pm

It needs to be exactly "LTC" and "DOGE" or it wont match up with the coin daemons

Was posting an example

I have another problem - its in email... think somethings point to /Users/jimbolaptop/Documents
drop down list in the next HTML maybe

chanc3r · « **Reply #20 on:** April 22, 2014, 11:15:30 pm »

Quote from: jl777 on April 22, 2014, 11:04:55 pm

With subatomic, we have effectively atomic crypto <-> crypto
with NXTatomic, we have NXT tx <-> NXT tx
Now toss in multigateway crypto assets and NXT atomic becomes crypto asset <-> NXT/crypto asset

So, an external crypto wallet <-> multigateway <-> NXT acct is an atomic path, but multigateway is in the middle. I want a trustless way to do:
external crypto <-> NXT assets

Hmmm....
...
OK, I have an idea. More later

James

Could see how MGW would help - I assumed you would want decentralised peering - if the IP for the offer is stored in the AM the Accepting SubAtomic could connect directly to the Offering SubAtomic... NXT Peer network is then assisting the connection...

Lol takes me back to my chemistry with catalysts and electron transfers...

jl777 · « **Reply #21 on:** April 22, 2014, 11:25:51 pm »

Quote from: chanc3r on April 22, 2014, 11:15:30 pm

Quote from: jl777 on April 22, 2014, 11:04:55 pm

With subatomic, we have effectively atomic crypto <-> crypto
with NXTatomic, we have NXT tx <-> NXT tx
Now toss in multigateway crypto assets and NXT atomic becomes crypto asset <-> NXT/crypto asset

So, an external crypto wallet <-> multigateway <-> NXT acct is an atomic path, but multigateway is in the middle. I want a trustless way to do:
external crypto <-> NXT assets

Hmmm....
...
OK, I have an idea. More later

James

Could see how MGW would help - I assumed you would want decentralised peering - if the IP for the offer is stored in the AM the Accepting SubAtomic could connect directly to the Offering SubAtomic... NXT Peer network is then assisting the connection...

Lol takes me back to my chemistry with catalysts and electron transfers...

yes, NXT AM's for seeding of peers and once connected to one peer, you get the rest. That is already done in InstantDEX.

I need to figure out one more thing about bitcoin tx and then I think I can create a decentralized atomic swap between bitcoin <-> NXT

James

swartzfeger · « **Reply #22 on:** April 23, 2014, 12:08:24 am »

Sorry, getting close... I need to update the doge blockchain. Also, is a dynamic IP a problem?

chanc3r · « **Reply #23 on:** April 23, 2014, 12:29:19 am »

Quote from: swartzfeger on April 23, 2014, 12:08:24 am

Sorry, getting close... I need to update the doge blockchain. Also, is a dynamic IP a problem?

I have dynamic IP - as long as you don't reboot your router we should be ok... I would hope..

Lol wait until you make the conf changes and re-index the DOGE and LTC block chains....

JAMES - is this still needed txindex=1

If it is ALL Potential SubAtomic testers PLEASE DO THIS NOW (see link) as it takes a while... like hours!!!

https://nxtforum.org/index.php?topic=665.msg9829#msg9829

jl777 · « **Reply #24 on:** April 23, 2014, 12:31:02 am »

Quote from: chanc3r on April 23, 2014, 12:29:19 am

Quote from: swartzfeger on April 23, 2014, 12:08:24 am
Sorry, getting close... I need to update the doge blockchain. Also, is a dynamic IP a problem?

I have dynamic IP - as long as you don't reboot your router we should be ok... I would hope..

Lol wait until you make the conf changes and re-index the DOGE and LTC block chains....

JAMES - is this still needed txindex=1

If it is ALL Potential SubAtomic testers PLEASE DO THIS NOW (see link) as it takes a while... like hours!!!

https://nxtforum.org/index.php?topic=665.msg9829#msg9829

I dont think txindex=1 is needed, but only one way to find out

swartzfeger · « **Reply #25 on:** April 23, 2014, 12:32:20 am »

Quote from: chanc3r on April 23, 2014, 12:29:19 am

Quote from: swartzfeger on April 23, 2014, 12:08:24 am
Sorry, getting close... I need to update the doge blockchain. Also, is a dynamic IP a problem?

I have dynamic IP - as long as you don't reboot your router we should be ok... I would hope..

Lol wait until you make the conf changes and re-index the DOGE and LTC block chains....

JAMES - is this still needed txindex=1

If it is ALL Potential SubAtomic testers PLEASE DO THIS NOW (see link) as it takes a while... like hours!!!

https://nxtforum.org/index.php?topic=665.msg9829#msg9829

Understood, thanks.

I'm at block 143k out of 192k. Ugh, this is why Doge is such a pain. Ignore the wallet for a few weeks and bam, 9 hour blockchain update.

At least my LTC is set to go.

swartzfeger · « **Reply #26 on:** April 23, 2014, 04:54:32 am »

Obviously missing something simple. From the terminal:

curl_easy_perform() failed: Couldn't connect to server NXT.(http://127.0.0.1:6876/nxt?requestType=getTime (null) (null) )

jl777 · « **Reply #27 on:** April 23, 2014, 05:04:49 am »

Quote from: swartzfeger on April 23, 2014, 04:54:32 am

Obviously missing something simple. From the terminal:

curl_easy_perform() failed: Couldn't connect to server NXT.(http://127.0.0.1:6876/nxt?requestType=getTime (null) (null) )

It seems to happen randomly with libcurl. Annoying, but just slows things down a bit

working on a new release that will allow you to configure things properly

swartzfeger · « **Reply #28 on:** April 23, 2014, 05:07:49 am »

Quote from: jl777 on April 23, 2014, 05:04:49 am

Quote from: swartzfeger on April 23, 2014, 04:54:32 am
Obviously missing something simple. From the terminal:

curl_easy_perform() failed: Couldn't connect to server NXT.(http://127.0.0.1:6876/nxt?requestType=getTime (null) (null) )
It seems to happen randomly with libcurl. Annoying, but just slows things down a bit

working on a new release that will allow you to configure things properly

That's great, James. What time zone are you, btw? I'm east coast US, but I will be up for at least another 5 hours (until about 6AM EDT). I'll stay up later if chanc3r gets back on and we can take 'one giant leap.'

jl777 · « **Reply #29 on:** April 23, 2014, 05:14:33 am »

Quote from: swartzfeger on April 23, 2014, 05:07:49 am

Quote from: jl777 on April 23, 2014, 05:04:49 am
Quote from: swartzfeger on April 23, 2014, 04:54:32 am
Obviously missing something simple. From the terminal:

curl_easy_perform() failed: Couldn't connect to server NXT.(http://127.0.0.1:6876/nxt?requestType=getTime (null) (null) )
It seems to happen randomly with libcurl. Annoying, but just slows things down a bit

working on a new release that will allow you to configure things properly

That's great, James. What time zone are you, btw? I'm east coast US, but I will be up for at least another 5 hours (until about 6AM EDT). I'll stay up later if chanc3r gets back on and we can take 'one giant leap.'

I am on a 28 hour per "day" schedule, the body's natural biorhythm for a day.

swartzfeger · « **Reply #30 on:** April 23, 2014, 05:32:11 am »

The exchange supports fractional amounts, correct? I don't hold a lot in either DOGE or LTC (edit: just checking cryptsy, I don't hold any LTC anymore, so I'll log into my old mining pages and see if I have some crumbs to cash out).

jl777 · « **Reply #31 on:** April 23, 2014, 05:36:09 am »

Quote from: swartzfeger on April 23, 2014, 05:32:11 am

The exchange supports fractional amounts, correct? I don't hold a lot in either DOGE or LTC (edit: just checking cryptsy, I don't hold any LTC anymore, so I'll log into my old mining pages and see if I have some crumbs to cash out).

its all satoshi based
mintx fee for DOGE is set to 2 as when I had it at 1, most multisig tx were rejected. If you need DOGE, I can send you some
mintx for LTC is .001
there is also a small donation set at .002 of tx value, which is the same as what centralized exchanges charge

If you are trading small amounts, the txfees will be a much larger percentage. Also, no actual trades will happen unless you explicitly enable it, but if your acct is underfunded, it will abort

James

jl777 · « **Reply #32 on:** April 23, 2014, 05:43:05 am »

Had to find the sequenceid inside a bitcoin rawtransaction. Unlike the locktime which is at the very end, the sequenceid is buried inside input structures, variable length, etc. I figured it would be useful someday, so I wrote a full parser for rawtransactions. I did look for one in C, but no luck, now I has one. It even seems to have all the txids and amounts correct, at least for the few tx I tested it with.

bunch of minor fixes.

You also dont need to put in your own IP address, I find it automatically

I also fixed the hardcoding of strings by using the NXT setAccountInfo!
got to 127.0.0.1:6876/test and find the setAccountInfo command
Set name to be how you want to be seen by others, easiest would be your handle
Then in the description field you need to put in JSON for your PC's "username" that your OS uses. I use this to find the ".conf" files, which all seem to be in the user specific directory.
For example: description field {"username":"jl777"}

dont worry if everything isnt quite right, if you go to 127.0.0.1:7777 it will display if anything needs to be done. There were some strange race conditions with both the historical and realtime processing, so I make the realtime processing wait until the historical is done now. Since the processing is a lot faster than before it shouldnt take more than a minute or so. You can tell if it is caught up to realtime when the NXT lines dont show "HIST". At that point the 127.0.0.1:7777 should appear

http://209.126.71.170/NXTsubatomic_v01.zip

Finally, I can start on the atomic swaps.

James

swartzfeger · « **Reply #33 on:** April 23, 2014, 05:48:18 am »

When I ./NXTsubatomic_v01, I still get

curl_easy_perform() failed: Couldn't connect to server NXT.(http://127.0.0.1:6876/nxt?requestType=getTime (null) (null) )

jl777 · « **Reply #34 on:** April 23, 2014, 05:50:42 am »

Quote from: swartzfeger on April 23, 2014, 05:48:18 am

When I ./NXTsubatomic_v01, I still get

curl_easy_perform() failed: Couldn't connect to server NXT.(http://127.0.0.1:6876/nxt?requestType=getTime (null) (null) )

Is that the only thing that appears, or anything else?
You do have testnet NXT running?
what happens if you put http://127.0.0.1:6876/nxt?requestType=getTime in your browser?

swartzfeger · « **Reply #35 on:** April 23, 2014, 05:54:28 am »

Quote from: jl777 on April 23, 2014, 05:50:42 am

Quote from: swartzfeger on April 23, 2014, 05:48:18 am
When I ./NXTsubatomic_v01, I still get

curl_easy_perform() failed: Couldn't connect to server NXT.(http://127.0.0.1:6876/nxt?requestType=getTime (null) (null) )
Is that the only thing that appears, or anything else?
You do have testnet NXT running?
what happens if you put http://127.0.0.1:6876/nxt?requestType=getTime in your browser?

Mea culpa. test net running now. Here's what I see with getTime:

{"time":12938006}

and http://127.0.0.1:7777 looks fine too.

jl777 · « **Reply #36 on:** April 23, 2014, 05:55:38 am »

Quote from: swartzfeger on April 23, 2014, 05:54:28 am

Quote from: jl777 on April 23, 2014, 05:50:42 am
Quote from: swartzfeger on April 23, 2014, 05:48:18 am
When I ./NXTsubatomic_v01, I still get

curl_easy_perform() failed: Couldn't connect to server NXT.(http://127.0.0.1:6876/nxt?requestType=getTime (null) (null) )
Is that the only thing that appears, or anything else?
You do have testnet NXT running?
what happens if you put http://127.0.0.1:6876/nxt?requestType=getTime in your browser?

Mea culpa. test net running now. Here's what I see with getTime:

{"time":12938006}

what about 127.0.0.1:7777

swartzfeger · « **Reply #37 on:** April 23, 2014, 05:56:45 am »

Quote from: jl777 on April 23, 2014, 05:55:38 am

Quote from: swartzfeger on April 23, 2014, 05:54:28 am
Quote from: jl777 on April 23, 2014, 05:50:42 am
Quote from: swartzfeger on April 23, 2014, 05:48:18 am
When I ./NXTsubatomic_v01, I still get

curl_easy_perform() failed: Couldn't connect to server NXT.(http://127.0.0.1:6876/nxt?requestType=getTime (null) (null) )
Is that the only thing that appears, or anything else?
You do have testnet NXT running?
what happens if you put http://127.0.0.1:6876/nxt?requestType=getTime in your browser?

Mea culpa. test net running now. Here's what I see with getTime:

{"time":12938006}

what about 127.0.0.1:7777

Yup. Looks fine.

jl777 · « **Reply #38 on:** April 23, 2014, 06:02:56 am »

Quote from: swartzfeger on April 23, 2014, 05:56:45 am

Quote from: jl777 on April 23, 2014, 05:55:38 am
Quote from: swartzfeger on April 23, 2014, 05:54:28 am
Quote from: jl777 on April 23, 2014, 05:50:42 am
Quote from: swartzfeger on April 23, 2014, 05:48:18 am
When I ./NXTsubatomic_v01, I still get

curl_easy_perform() failed: Couldn't connect to server NXT.(http://127.0.0.1:6876/nxt?requestType=getTime (null) (null) )
Is that the only thing that appears, or anything else?
You do have testnet NXT running?
what happens if you put http://127.0.0.1:6876/nxt?requestType=getTime in your browser?

Mea culpa. test net running now. Here's what I see with getTime:

{"time":12938006}

what about 127.0.0.1:7777

Yup. Looks fine.

It is important to make sure that NXTsubatomic is communicating properly with the LTC and DOGE RPC
at the beginning of the test window you should see messages about extract_userpass and there should be no errors from the coin daemons

James

swartzfeger · « **Reply #39 on:** April 23, 2014, 06:05:50 am »

Quote from: jl777 on April 23, 2014, 06:02:56 am

Quote from: swartzfeger on April 23, 2014, 05:56:45 am
Quote from: jl777 on April 23, 2014, 05:55:38 am
Quote from: swartzfeger on April 23, 2014, 05:54:28 am
Quote from: jl777 on April 23, 2014, 05:50:42 am
Quote from: swartzfeger on April 23, 2014, 05:48:18 am
When I ./NXTsubatomic_v01, I still get

curl_easy_perform() failed: Couldn't connect to server NXT.(http://127.0.0.1:6876/nxt?requestType=getTime (null) (null) )
Is that the only thing that appears, or anything else?
You do have testnet NXT running?
what happens if you put http://127.0.0.1:6876/nxt?requestType=getTime in your browser?

Mea culpa. test net running now. Here's what I see with getTime:

{"time":12938006}

what about 127.0.0.1:7777

Yup. Looks fine.
It is important to make sure that NXTsubatomic is communicating properly with the LTC and DOGE RPC
at the beginning of the test window you should see messages about extract_userpass and there should be no errors from the coin daemons

James

looks like it's trying to load a file from your machine?

couldnt load.(/Users/*censored*/Documents/NXT/gateway/gateway/NXTprotocol.html

jl777 · « **Reply #40 on:** April 23, 2014, 06:10:01 am »

Quote from: swartzfeger on April 23, 2014, 06:05:50 am

couldnt load.(/Users/*censored*/Documents/NXT/gateway/gateway/NXTprotocol.html

That's only if you have an html file to override the automatically generated page.
shouldnt be a problem if it isnt there

swartzfeger · « **Reply #41 on:** April 23, 2014, 06:12:18 am »

Does testnet need to be higher than 0.8.13? This blockchain keeps rolling back... I'm thinking I need to be on 0.9.x. I never updated because of Wesley's wallet barfing on 0.9.x on the main net.

jl777 · « **Reply #42 on:** April 23, 2014, 06:26:35 am »

Quote from: swartzfeger on April 23, 2014, 06:12:18 am

Does testnet need to be higher than 0.8.13? This blockchain keeps rolling back... I'm thinking I need to be on 0.9.x. I never updated because of Wesley's wallet barfing on 0.9.x on the main net.

yes,you need 9.9, especially to test NXTatomic

swartzfeger · « **Reply #43 on:** April 23, 2014, 06:29:06 am »

Quote from: jl777 on April 23, 2014, 06:26:35 am

Quote from: swartzfeger on April 23, 2014, 06:12:18 am
Does testnet need to be higher than 0.8.13? This blockchain keeps rolling back... I'm thinking I need to be on 0.9.x. I never updated because of Wesley's wallet barfing on 0.9.x on the main net.
yes,you need 9.9, especially to test NXTatomic

And NxtWallet keeps barfing on it, both main and test. I'm done with Wesley's wallet because the lack of updates is making it impossible to test.

Just download plain 9.9 and run it from the terminal?

jl777 · « **Reply #44 on:** April 23, 2014, 06:31:34 am »

Quote from: swartzfeger on April 23, 2014, 06:29:06 am

Quote from: jl777 on April 23, 2014, 06:26:35 am
Quote from: swartzfeger on April 23, 2014, 06:12:18 am
Does testnet need to be higher than 0.8.13? This blockchain keeps rolling back... I'm thinking I need to be on 0.9.x. I never updated because of Wesley's wallet barfing on 0.9.x on the main net.
yes,you need 9.9, especially to test NXTatomic

And NxtWallet keeps barfing on it, both main and test. I'm done with Wesley's wallet because the lack of updates is making it impossible to test.

Just download plain 9.9 and run it from the terminal?

you can run both testnet and main net at the same time
just download the new version in a new folder, edit the conf file to make sure testnet is set to true
now ports 68xx is testnet and mainnet is untouched
for my stuff, no need for wallet

swartzfeger · « **Reply #45 on:** April 23, 2014, 06:40:07 am »

Quote from: jl777 on April 23, 2014, 06:31:34 am

Quote from: swartzfeger on April 23, 2014, 06:29:06 am
Quote from: jl777 on April 23, 2014, 06:26:35 am
Quote from: swartzfeger on April 23, 2014, 06:12:18 am
Does testnet need to be higher than 0.8.13? This blockchain keeps rolling back... I'm thinking I need to be on 0.9.x. I never updated because of Wesley's wallet barfing on 0.9.x on the main net.
yes,you need 9.9, especially to test NXTatomic

And NxtWallet keeps barfing on it, both main and test. I'm done with Wesley's wallet because the lack of updates is making it impossible to test.

Just download plain 9.9 and run it from the terminal?
you can run both testnet and main net at the same time
just download the new version in a new folder, edit the conf file to make sure testnet is set to true
now ports 68xx is testnet and mainnet is untouched
for my stuff, no need for wallet

You're a star. Edited .conf, restarted, testnet is now running on :6875 and blockchain is updating. I'll get there.

jl777 · « **Reply #46 on:** April 23, 2014, 06:46:47 am »

Quote from: swartzfeger on April 23, 2014, 06:40:07 am

Quote from: jl777 on April 23, 2014, 06:31:34 am
Quote from: swartzfeger on April 23, 2014, 06:29:06 am
Quote from: jl777 on April 23, 2014, 06:26:35 am
Quote from: swartzfeger on April 23, 2014, 06:12:18 am
Does testnet need to be higher than 0.8.13? This blockchain keeps rolling back... I'm thinking I need to be on 0.9.x. I never updated because of Wesley's wallet barfing on 0.9.x on the main net.
yes,you need 9.9, especially to test NXTatomic

And NxtWallet keeps barfing on it, both main and test. I'm done with Wesley's wallet because the lack of updates is making it impossible to test.

Just download plain 9.9 and run it from the terminal?
you can run both testnet and main net at the same time
just download the new version in a new folder, edit the conf file to make sure testnet is set to true
now ports 68xx is testnet and mainnet is untouched
for my stuff, no need for wallet

You're a star. Edited .conf, restarted, testnet is now running on :6875 and blockchain is updating. I'll get there.

Just be REALLY careful when running both as it is easy to confuse them, especially if you end up on the /test screen

swartzfeger · « **Reply #47 on:** April 23, 2014, 06:50:07 am »

Quote from: jl777 on April 23, 2014, 06:46:47 am

Quote from: swartzfeger on April 23, 2014, 06:40:07 am
Quote from: jl777 on April 23, 2014, 06:31:34 am
Quote from: swartzfeger on April 23, 2014, 06:29:06 am
Quote from: jl777 on April 23, 2014, 06:26:35 am
Quote from: swartzfeger on April 23, 2014, 06:12:18 am
Does testnet need to be higher than 0.8.13? This blockchain keeps rolling back... I'm thinking I need to be on 0.9.x. I never updated because of Wesley's wallet barfing on 0.9.x on the main net.
yes,you need 9.9, especially to test NXTatomic

And NxtWallet keeps barfing on it, both main and test. I'm done with Wesley's wallet because the lack of updates is making it impossible to test.

Just download plain 9.9 and run it from the terminal?
you can run both testnet and main net at the same time
just download the new version in a new folder, edit the conf file to make sure testnet is set to true
now ports 68xx is testnet and mainnet is untouched
for my stuff, no need for wallet

You're a star. Edited .conf, restarted, testnet is now running on :6875 and blockchain is updating. I'll get there.
Just be REALLY careful when running both as it is easy to confuse them, especially if you end up on the /test screen

Do I need testNXT? Someone sent me 5000 last night but the balance is showing 0.00 (even tho I see the transaction for 5000 incoming last night).

11369639962571180006

never mind. logged out and back in, balance is all good.

swartzfeger · « **Reply #48 on:** April 23, 2014, 06:54:40 am »

Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Initial logging level 7
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Library version: 1.3 b25b85f
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: IPV6 compiled in and enabled
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: libev support not compiled in
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Started with daemon pid 0
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: static allocation: 4512 + (16 x 256 fds) = 8608 bytes
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: canonical_hostname = MBP.local
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: per-conn mem: 208 + 1554 headers + protocol rx buf
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Compiled with OpenSSL support
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Using non-SSL mode
Apr 23 02:52:11 MBP.local lwsts[12574] <Error>: ERROR on binding to port 7777 (-1 48)
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: mirror protocol cleaning up
Apr 23 02:52:11 MBP.local lwsts[12574] <Error>: libwebsocket init failed

swartzfeger · « **Reply #49 on:** April 23, 2014, 06:55:18 am »

and http://127.0.0.1:7777 won't load

jl777 · « **Reply #50 on:** April 23, 2014, 06:56:38 am »

Quote from: swartzfeger on April 23, 2014, 06:54:40 am

Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Initial logging level 7
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Library version: 1.3 b25b85f
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: IPV6 compiled in and enabled
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: libev support not compiled in
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Started with daemon pid 0
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: static allocation: 4512 + (16 x 256 fds) = 8608 bytes
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: canonical_hostname = MBP.local
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: per-conn mem: 208 + 1554 headers + protocol rx buf
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Compiled with OpenSSL support
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Using non-SSL mode
Apr 23 02:52:11 MBP.local lwsts[12574] <Error>: ERROR on binding to port 7777 (-1 48)
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: mirror protocol cleaning up
Apr 23 02:52:11 MBP.local lwsts[12574] <Error>: libwebsocket init failed

Apr 23 02:52:11 MBP.local lwsts[12574] <Error>: ERROR on binding to port 7777 (-1 48)
usually means you already have a copy running. only one instance is allowed as they all use the same port (for now)

swartzfeger · « **Reply #51 on:** April 23, 2014, 07:01:01 am »

Quote from: jl777 on April 23, 2014, 06:56:38 am

Quote from: swartzfeger on April 23, 2014, 06:54:40 am

Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Initial logging level 7
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Library version: 1.3 b25b85f
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: IPV6 compiled in and enabled
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: libev support not compiled in
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Started with daemon pid 0
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: static allocation: 4512 + (16 x 256 fds) = 8608 bytes
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: canonical_hostname = MBP.local
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: per-conn mem: 208 + 1554 headers + protocol rx buf
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Compiled with OpenSSL support
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Using non-SSL mode
Apr 23 02:52:11 MBP.local lwsts[12574] <Error>: ERROR on binding to port 7777 (-1 48)
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: mirror protocol cleaning up
Apr 23 02:52:11 MBP.local lwsts[12574] <Error>: libwebsocket init failed
Apr 23 02:52:11 MBP.local lwsts[12574] <Error>: ERROR on binding to port 7777 (-1 48)
usually means you already have a copy running. only one instance is allowed as they all use the same port (for now)

I'm only running one instance (as far as I know). I run v01, it does its thing, runs through all the timestamps, errors out on binding to 7777 and then quits to a $ prompt.

jl777 · « **Reply #52 on:** April 23, 2014, 07:08:38 am »

Quote from: swartzfeger on April 23, 2014, 07:01:01 am

Quote from: jl777 on April 23, 2014, 06:56:38 am
Quote from: swartzfeger on April 23, 2014, 06:54:40 am

Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Initial logging level 7
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Library version: 1.3 b25b85f
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: IPV6 compiled in and enabled
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: libev support not compiled in
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Started with daemon pid 0
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: static allocation: 4512 + (16 x 256 fds) = 8608 bytes
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: canonical_hostname = MBP.local
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: per-conn mem: 208 + 1554 headers + protocol rx buf
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Compiled with OpenSSL support
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: Using non-SSL mode
Apr 23 02:52:11 MBP.local lwsts[12574] <Error>: ERROR on binding to port 7777 (-1 48)
Apr 23 02:52:11 MBP.local lwsts[12574] <Notice>: mirror protocol cleaning up
Apr 23 02:52:11 MBP.local lwsts[12574] <Error>: libwebsocket init failed
Apr 23 02:52:11 MBP.local lwsts[12574] <Error>: ERROR on binding to port 7777 (-1 48)
usually means you already have a copy running. only one instance is allowed as they all use the same port (for now)

I'm only running one instance (as far as I know). I run v01, it does its thing, runs through all the timestamps, errors out on binding to 7777 and then quits to a $ prompt.

maybe there is something else using that port...
run the following from the terminal

lsof -n -i4TCP:7777

does anything show up?

swartzfeger · « **Reply #53 on:** April 23, 2014, 07:10:45 am »

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME com.apple 252 jay 11u IPv4 0x5edd11fff3d6235d 0t0 TCP 127.0.0.1:55589->127.0.0.1:cbt (ESTABLISHED) com.apple 252 jay 15u IPv4 0x5edd11fff3d6235d 0t0 TCP 127.0.0.1:55589->127.0.0.1:cbt (ESTABLISHED) NXTsubato 12249 jay 10u IPv6 0x5edd11ffebff7e7d 0t0 TCP *:cbt (LISTEN)

swartzfeger · « **Reply #54 on:** April 23, 2014, 07:12:56 am »

did a top and there were multiple copies running of v0 and v1 running.

swartzfeger · « **Reply #55 on:** April 23, 2014, 07:17:54 am »

Ok, I'm cooking now. Restarted 9.9, killed all the v0 and v1 and everything is fine now.

http://127.0.0.1:7777 loads fine too.

jl777 · « **Reply #56 on:** April 23, 2014, 07:48:48 am »

http://209.126.71.170/NXTsubatomic_v04.zip fixes a problem where the account cant be changed

If you and your subatomic trade partner are comfortable with enabling broadcasting the transactions (after making sure they look right!) the above version has a way to enable it. In the accountinfo JSON:

"enable_bitcoin_broadcast":"666"

I havent had a chance to try it yet, so be very careful! If both sides dont enable it, it would be a totally unfair trade

James

swartzfeger · « **Reply #57 on:** April 23, 2014, 08:54:51 am »

Quote from: jl777 on April 23, 2014, 07:48:48 am

http://209.126.71.170/NXTsubatomic_v02.zip fixes a problem where the account cant be changed

If you and your subatomic trade partner are comfortable with enabling broadcasting the transactions (after making sure they look right!) the above version has a way to enable it. In the accountinfo JSON:

"enable_bitcoin_broadcast":"666"

I havent had a chance to try it yet, so be very careful! If both sides dont enable it, it would be a totally unfair trade

James

No problems so far. Going to get a few hours sleep and see if I can pull this off with chanc3r or another partner.

jl777 · « **Reply #58 on:** April 23, 2014, 09:52:17 am »

make sure to use http://209.126.71.170/NXTsubatomic_v04.zip

chanc3r · « **Reply #59 on:** April 23, 2014, 03:22:04 pm »

Quote from: jl777 on April 18, 2014, 02:06:48 am

I wasnt feeling too well today, so I didnt want to mess with multigateway. I ended up with a crazy idea that maybe just means I am really sick and delusional, or I have come up with a way to implement atomic cross chain exchanges!

Before getting too excited, I need a volunteer who has a Mac. I want to test LTC <-> DOGE atomic exchanges, so you need to have both litecoin and dogecoin wallets installed with the following in the conf files:

/Users/<your username>/Library/Application Support/Dogecoin/dogecoin.conf
/Users/<your username>/Library/Application Support/Litecoin/litecoin.conf

server=1
rpcuser=dogecoinrpc
rpcpassword=<wallet will tell you a password to use>
txindex=1
rpcport=<see below>

I had to add rpcport with the following values;

litecoin 9332
dogecoin 22555

it should have just worked but my wallets seem to have refused to listen on those ports....
good news is subatomic 4 seems to read my account info on test net, find my two wallets DOGE and LTC and connect to all of it...

I managed to create a TX but no one to share it with at the moment... SO I sent it to myself which doesn't work unfortunately...

AM_subatomic({"type":"subatomic_crypto","completed":0,"received":0,"expected":128.84901888,"sent":0,"sending":0,
"NXT":"3940521100773952218","coin":"DOGE","amount":"1000.00000000","ipaddr":"88.82.0.8","destcoin":"LTC",
"destamount":"0.10000000","destNXT":"3940521100773952218",
"destNXTcoinaddr":"DEwmsmYq3rzbMdmM6xkJpNPtPg5CS1YSNf","destNXTdestcoinaddr":"LVNE1nxeiAzx72MwY8rxw22V9BdTgNsSz6"})

jl777 · « **Reply #60 on:** April 23, 2014, 04:27:09 pm »

v04 has NXTatomic pairing implemented,at least to where it will publish AM and get matched up. I just need to code the actual trade negotiation, but it will be much, much simpler than with bitcoind. I think I am deriving all the required fields.

I overloaded the subatomic form with a special case. If both coin and destcoin is "NXT", then the coinaddr and destcoinaddr are the raw transaction bytes. Again, this is not meant for normal end user usage, but rather for a higher level to push trades down into. The txbytes for your side need to be the signed transaction bytes that you can get from the JSON after any "money" transaction:
"transactionBytes": "00006991c5009a0225c5fed2690701cf06f267e7c227b1a3c0dfa9c6fc3cdb593b3af6f16d65302f8c71b555df3ec27c00e1f5050000000000e1f505000000000000000000000000000000000000000000000000000000000000000000000000d5df79c3ec5b58c1a1d7c5de16635db8c050d345080f9180538188e06a9f380f5c076a9b75b776c6ba775a027f14c60b0a054b18b2094dd3dc8d4d97f7273aa3",

The txbytes for the other side, will be the unsigned txbytes that you negotiated with the other party:
"unsignedTransactionBytes": "00006991c5009a0225c5fed2690701cf06f267e7c227b1a3c0dfa9c6fc3cdb593b3af6f16d65302f8c71b555df3ec27c00e1f5050000000000e1f50500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"

You need to come to agreement on the trade. What this means is that you can trade an asset for NXT, or AM for AM, etc.

I am not enforcing any security yet, so you can specify a tx issued from a different sender, but in that case you will not be able to complete the actual swap as you wont have the signaturehash

Next up is making it actually do the swap by sending proof of tx, confirming, tweaking, linking, broadcasting, etc.
And then it segues into a trading marketplace, but I need to figure out how to properly deal with that and NXTorrent. The issue is so similar might as well use the same method to solve it for both.

While that is percolating, I think I will rework the multigateway withdrawal mechanism. This work with subatomic made me realize how inefficient the internal multigateway withdraw process is. I also found a few small improvements in bitcoind interface code. All these projects keep feeding back into each other and making all of them better!

James

swartzfeger · « **Reply #61 on:** April 23, 2014, 05:37:26 pm »

just downloaded v4. Should be able to test here shortly.

swartzfeger · « **Reply #62 on:** April 23, 2014, 06:21:04 pm »

Running v4. Anyone want to try this?

Daedelus · « **Reply #63 on:** April 23, 2014, 06:32:28 pm »

http://youtube.com/watch?v=e-QFj59PON4

I would play this just as your setting up and about to press 'the button' for the first time

chanc3r · « **Reply #64 on:** April 23, 2014, 08:07:20 pm »

Quote from: swartzfeger on April 23, 2014, 06:21:04 pm

Running v4. Anyone want to try this?

I'm on IRC - where are you?

jl777 · « **Reply #65 on:** April 23, 2014, 09:04:06 pm »

Quote from: chanc3r on April 23, 2014, 08:07:20 pm

Quote from: swartzfeger on April 23, 2014, 06:21:04 pm
Running v4. Anyone want to try this?

I'm on IRC - where are you?

You will need to use http://209.126.71.170/NXTsubatomic_v05.zip
v04 will get confused by the NXTatomic AM's I am testing with

James

swartzfeger · « **Reply #66 on:** April 23, 2014, 09:20:04 pm »

Quote from: chanc3r on April 23, 2014, 08:07:20 pm

Quote from: swartzfeger on April 23, 2014, 06:21:04 pm
Running v4. Anyone want to try this?

I'm on IRC - where are you?

Had to run wedding errands. Home in 5.

Sent from my iPhone using Tapatalk

swartzfeger · « **Reply #67 on:** April 23, 2014, 09:47:34 pm »

Quote from: jl777 on April 23, 2014, 09:04:06 pm

Quote from: chanc3r on April 23, 2014, 08:07:20 pm
Quote from: swartzfeger on April 23, 2014, 06:21:04 pm
Running v4. Anyone want to try this?

I'm on IRC - where are you?
You will need to use http://209.126.71.170/NXTsubatomic_v05.zip
v04 will get confused by the NXTatomic AM's I am testing with

James

Downloaded, and chanc3r and I are coordinating. Only hold up now is updating DOGE wallet, another 600 blocks or so.

swartzfeger · « **Reply #68 on:** April 23, 2014, 11:11:11 pm »

got trade! flipped.0 | initflag.3

jl777 · « **Reply #69 on:** April 23, 2014, 11:23:48 pm »

What does the status button show?
Are you seeing stuff in the text window?

swartzfeger · « **Reply #70 on:** April 23, 2014, 11:29:40 pm »

Quote from: jl777 on April 23, 2014, 11:23:48 pm

What does the status button show?
Are you seeing stuff in the text window?

subatomic_send_pubkeys cantsend.0 send pubkeys DBc9VPgvBNovCB7stPkv4jUp3RaZg2Mpq5 (*censored* and ) Lay5W86ofFKzakoxT8A5mBWkcneczAHRA3 to got packet.(P) len.12304 from (::1) got pubkeys and cant gen multisig 68 48 68 0

jl777 · « **Reply #71 on:** April 23, 2014, 11:34:55 pm »

Quote from: swartzfeger on April 23, 2014, 11:29:40 pm

Quote from: jl777 on April 23, 2014, 11:23:48 pm
What does the status button show?
Are you seeing stuff in the text window?

subatomic_send_pubkeys cantsend.0 send pubkeys DBc9VPgvBNovCB7stPkv4jUp3RaZg2Mpq5 (*censored* and ) Lay5W86ofFKzakoxT8A5mBWkcneczAHRA3 to got packet.(P) len.12304 from (::1) got pubkeys and cant gen multisig 68 48 68 0

(::1) is not the right type of IP address...
it needs to be the normal IP address of the other party

chanc3r · « **Reply #72 on:** April 23, 2014, 11:35:26 pm »

Quote from: jl777 on April 23, 2014, 11:23:48 pm

What does the status button show?
Are you seeing stuff in the text window?

sent you an entire paste bin james

its looping on multi-sig so we got something wrong somewhere, status button shows nothing and can't seem to cancel it :/

*EDIT: if this works judging by how my testNXT is going down there will be lots more TX Fees to be forged.

jl777 · « **Reply #73 on:** April 23, 2014, 11:46:41 pm »

Quote from: chanc3r on April 23, 2014, 11:35:26 pm

Quote from: jl777 on April 23, 2014, 11:23:48 pm
What does the status button show?
Are you seeing stuff in the text window?

sent you an entire paste bin james

its looping on multi-sig so we got something wrong somewhere, status button shows nothing and can't seem to cancel it :/

*EDIT: if this works judging by how my testNXT is going down there will be lots more TX Fees to be forged.

control-C to kill the program

why is your testNXT going down??
Only one AM should be sent, any other NXT commands would be a bug

swartzfeger · « **Reply #74 on:** April 23, 2014, 11:48:55 pm »

Quote from: jl777 on April 23, 2014, 11:46:41 pm

Quote from: chanc3r on April 23, 2014, 11:35:26 pm
Quote from: jl777 on April 23, 2014, 11:23:48 pm
What does the status button show?
Are you seeing stuff in the text window?

sent you an entire paste bin james

its looping on multi-sig so we got something wrong somewhere, status button shows nothing and can't seem to cancel it :/

*EDIT: if this works judging by how my testNXT is going down there will be lots more TX Fees to be forged.
control-C to kill the program
why is your testNXT going down??
Only one AM should be sent, any other NXT commands would be a bug

Ok... but what about the ip address/address auto-detect? Is it broken?

chanc3r · « **Reply #75 on:** April 23, 2014, 11:52:29 pm »

Quote from: jl777 on April 23, 2014, 11:46:41 pm

control-C to kill the program
why is your testNXT going down??
Only one AM should be sent, any other NXT commands would be a bug

well you submit...
you cancel maybe
you submit a new one
you update your account info...

and I know many ways to kill a programme

jl777 · « **Reply #76 on:** April 23, 2014, 11:52:37 pm »

Quote from: swartzfeger on April 23, 2014, 11:48:55 pm

Quote from: jl777 on April 23, 2014, 11:46:41 pm
Quote from: chanc3r on April 23, 2014, 11:35:26 pm
Quote from: jl777 on April 23, 2014, 11:23:48 pm
What does the status button show?
Are you seeing stuff in the text window?

sent you an entire paste bin james

its looping on multi-sig so we got something wrong somewhere, status button shows nothing and can't seem to cancel it :/

*EDIT: if this works judging by how my testNXT is going down there will be lots more TX Fees to be forged.
control-C to kill the program
why is your testNXT going down??
Only one AM should be sent, any other NXT commands would be a bug

Ok... but what about the ip address/address auto-detect? Is it broken?

Not sure how I can detect the IP address of the person you are trading with.
The assumption is that there could be more than one exchange at a time, but only one to a specific NXT addr.

The AM packet is supposed to have your IP address and the other side uses that to contact you. Since things are going back and forth between both your computers, that part seems to beworking.

Making a test version. Now that you have it setup to start trading, it is much easier. just kill the old version, start th e new one and it will restart the trade cycle

jl777 · « **Reply #77 on:** April 23, 2014, 11:53:15 pm »

Quote from: chanc3r on April 23, 2014, 11:52:29 pm

Quote from: jl777 on April 23, 2014, 11:46:41 pm
control-C to kill the program
why is your testNXT going down??
Only one AM should be sent, any other NXT commands would be a bug

well you submit...
you cancel maybe
you submit a new one
you update your account info...

and I know many ways to kill a programme

Oh, ok, I thought you meant it was just draining it in a loop!

swartzfeger · « **Reply #78 on:** April 23, 2014, 11:55:51 pm »

Quote from: jl777 on April 23, 2014, 11:52:37 pm

Making a test version. Now that you have it setup to start trading, it is much easier. just kill the old version, start th e new one and it will restart the trade cycle

Should we wait for _v06?

chanc3r · « **Reply #79 on:** April 23, 2014, 11:56:49 pm »

Quote from: jl777 on April 23, 2014, 11:52:37 pm

Not sure how I can detect the IP address of the person you are trading with.
The assumption is that there could be more than one exchange at a time, but only one to a specific NXT addr.

The AM packet is supposed to have your IP address and the other side uses that to contact you. Since things are going back and forth between both your computers, that part seems to beworking.

Making a test version. Now that you have it setup to start trading, it is much easier. just kill the old version, start th e new one and it will restart the trade cycle

Last version we manually entered our IP addr...
In this version you detect the senders IP and put in the AM.. yes?
Could it be that detect is broken somehow? - I think jay is asking this then each party will receive the halfTX AMs with corrupt/wrong ip's an then the process breaks

jl777 · « **Reply #80 on:** April 24, 2014, 12:02:57 am »

Quote from: chanc3r on April 23, 2014, 11:56:49 pm

Quote from: jl777 on April 23, 2014, 11:52:37 pm

Not sure how I can detect the IP address of the person you are trading with.
The assumption is that there could be more than one exchange at a time, but only one to a specific NXT addr.

The AM packet is supposed to have your IP address and the other side uses that to contact you. Since things are going back and forth between both your computers, that part seems to beworking.

Making a test version. Now that you have it setup to start trading, it is much easier. just kill the old version, start th e new one and it will restart the trade cycle

Last version we manually entered our IP addr...
In this version you detect the senders IP and put in the AM.. yes?
Could it be that detect is broken somehow? - I think jay is asking this then each party will receive the halfTX AMs with corrupt/wrong ip's an then the process breaks

What did the AM packet have in it? process_subatomic_AM would have been printed right before. If I can see both AM's we can verify it is fine. Since there was contact between your computers, it must have gotten at least one IP address

swartzfeger · « **Reply #81 on:** April 24, 2014, 12:06:30 am »

I cleared my terminal window and don't see anything relevant in the console logs... how can I go back and look in the AM packets?

jl777 · « **Reply #82 on:** April 24, 2014, 12:09:25 am »

Quote from: swartzfeger on April 24, 2014, 12:06:30 am

I cleared my terminal window and don't see anything relevant in the console logs... how can I go back and look in the AM packets?

kill program and restart it

chanc3r · « **Reply #83 on:** April 24, 2014, 12:11:58 am »

Quote from: jl777 on April 24, 2014, 12:02:57 am

What did the AM packet have in it? process_subatomic_AM would have been printed right before. If I can see both AM's we can verify it is fine. Since there was contact between your computers, it must have gotten at least one IP address

its in the paste bin i sent by email - read the string can't see a field for IP...

process_subatomic_AM got jsontxt.({"type":"subatomic_crypto","NXT":"12670408480068341195","coin":"DOGE","amount":"20.00000000",
"coinaddr":"DBc9VPgvBNovCB7stPkv4jUp3RaZg2Mpq5","destcoin":"LTC","destamount":"0.00100000",
"destcoinaddr":"Lay5W86ofFKzakoxT8A5mBWkcneczAHRA3","destNXT":"3940521100773952218"})

jl777 · « **Reply #84 on:** April 24, 2014, 12:12:12 am »

v06 is there

jl777 · « **Reply #85 on:** April 24, 2014, 12:12:47 am »

Quote from: chanc3r on April 24, 2014, 12:11:58 am

Quote from: jl777 on April 24, 2014, 12:02:57 am
What did the AM packet have in it? process_subatomic_AM would have been printed right before. If I can see both AM's we can verify it is fine. Since there was contact between your computers, it must have gotten at least one IP address

its in the paste bin i sent by email - read the string can't see a field for IP...

process_subatomic_AM got jsontxt.({"type":"subatomic_crypto","NXT":"12670408480068341195","coin":"DOGE","amount":"20.00000000",
"coinaddr":"DBc9VPgvBNovCB7stPkv4jUp3RaZg2Mpq5","destcoin":"LTC","destamount":"0.00100000",
"destcoinaddr":"Lay5W86ofFKzakoxT8A5mBWkcneczAHRA3","destNXT":"3940521100773952218"})

that's a problem...
v07 coming up

jl777 · « **Reply #86 on:** April 24, 2014, 12:18:33 am »

v07 is there
you need to submit new AMs

chanc3r · « **Reply #87 on:** April 24, 2014, 12:24:40 am »

Quote from: jl777 on April 24, 2014, 12:18:33 am

v07 is there
you need to submit new AMs

that's http://209.126.71.170/NXTsubatomic_v07.zip then

EDIT: jimbolaptop is back :/

Jay Local patch is "cd /users; sudo ln -s <your username> jimbolaptop"

jl777 · « **Reply #88 on:** April 24, 2014, 12:35:55 am »

Quote from: chanc3r on April 24, 2014, 12:24:40 am

Quote from: jl777 on April 24, 2014, 12:18:33 am
v07 is there
you need to submit new AMs

that's http://209.126.71.170/NXTsubatomic_v07.zip then

EDIT: jimbolaptop is back :/

Jay Local patch is "cd /users; sudo ln -s <your username> jimbolaptop"

I removed the jimbolaptop code so it wont haunt us again

swartzfeger · « **Reply #89 on:** April 24, 2014, 12:48:47 am »

Quote from: jl777 on April 24, 2014, 12:35:55 am

Quote from: chanc3r on April 24, 2014, 12:24:40 am
Quote from: jl777 on April 24, 2014, 12:18:33 am
v07 is there
you need to submit new AMs

that's http://209.126.71.170/NXTsubatomic_v07.zip then

EDIT: jimbolaptop is back :/

Jay Local patch is "cd /users; sudo ln -s <your username> jimbolaptop"
I removed the jimbolaptop code so it wont haunt us again

James, how do we confirm we were successful?

jl777 · « **Reply #90 on:** April 24, 2014, 12:51:09 am »

Quote from: swartzfeger on April 24, 2014, 12:48:47 am

Quote from: jl777 on April 24, 2014, 12:35:55 am
Quote from: chanc3r on April 24, 2014, 12:24:40 am
Quote from: jl777 on April 24, 2014, 12:18:33 am
v07 is there
you need to submit new AMs

that's http://209.126.71.170/NXTsubatomic_v07.zip then

EDIT: jimbolaptop is back :/

Jay Local patch is "cd /users; sudo ln -s <your username> jimbolaptop"
I removed the jimbolaptop code so it wont haunt us again

James, how do we confirm we were successful?

Did you post the order again to generate the AM?

It is so close to starting the exchange sequence. Once it does, you will see something like:

Code: [Select]

refund signing completed.1
>>>>>>>>>>>>>>>>>>>>> refund at 193997 is locked! txid.e22817f274ef02d61c93e330d1f9752d8afb6c61b7192d234945f98db987d91e completed 1 95.80000000 -> DNbAcP82bpd9xdXNA1Vtf1Vo6yqP1rZvcu
broadcasting is disabled for now: (0100000001dfe116d176b3f5fa6578cad495e68d4583855b276f4469814e8343b8959fe10e00000000db0048304502206a70dc809933ba753c4cf56ea36ae96db961c129345d44a36a2d556e24fa9ab0022100b868eaecd21d37983fb500dd14ebac060891a2c1955237581a173725eda2d84e0148304502202dc5ce6fdb0e31e1a00c8e91fc51780f33677dbfff8371d45d8caf44539e52aa022100adfa676da67fab7bac36715527370f4531780636d035fe78c9416a660376420901475221031f55ec974a55df56d33755ec2c6be66ab719d21021e93e52f76ce58ace1591ff2103514fe44529b41340575d460059847730d67fd90662a3f7f21e422aa5aff86f7452aeffffffff020033033b020000001976a914bf685a09e61215c7e824d0b73bc6d6d3ba9d9d9688ac80969800000000001976a91414b24a5b6f8c8df0f7c9b519d362618ca211e60988accdf50200) ->
({
	"txid":	"e22817f274ef02d61c93e330d1f9752d8afb6c61b7192d234945f98db987d91e",
	"version":	1,
	"locktime":	193997,
	"vin":	[{
			"txid":	"0ee19f95b843834e8169446f275b8583458de695d4ca7865faf5b376d116e1df",
			"vout":	0,
			"scriptSig":	{
				"asm":	"0 304502206a70dc809933ba753c4cf56ea36ae96db961c129345d44a36a2d556e24fa9ab0022100b868eaecd21d37983fb500dd14ebac060891a2c1955237581a173725eda2d84e01 304502202dc5ce6fdb0e31e1a00c8e91fc51780f33677dbfff8371d45d8caf44539e52aa022100adfa676da67fab7bac36715527370f4531780636d035fe78c9416a660376420901 5221031f55ec974a55df56d33755ec2c6be66ab719d21021e93e52f76ce58ace1591ff2103514fe44529b41340575d460059847730d67fd90662a3f7f21e422aa5aff86f7452ae",
				"hex":	"0048304502206a70dc809933ba753c4cf56ea36ae96db961c129345d44a36a2d556e24fa9ab0022100b868eaecd21d37983fb500dd14ebac060891a2c1955237581a173725eda2d84e0148304502202dc5ce6fdb0e31e1a00c8e91fc51780f33677dbfff8371d45d8caf44539e52aa022100adfa676da67fab7bac36715527370f4531780636d035fe78c9416a660376420901475221031f55ec974a55df56d33755ec2c6be66ab719d21021e93e52f76ce58ace1591ff2103514fe44529b41340575d460059847730d67fd90662a3f7f21e422aa5aff86f7452ae"
			},
			"sequence":	4294967295
		}],
	"vout":	[{
			"value":	95.80000000,
			"n":	0,
			"scriptPubKey":	{
				"asm":	"OP_DUP OP_HASH160 bf685a09e61215c7e824d0b73bc6d6d3ba9d9d96 OP_EQUALVERIFY OP_CHECKSIG",
				"hex":	"76a914bf685a09e61215c7e824d0b73bc6d6d3ba9d9d9688ac",
				"reqSigs":	1,
				"type":	"pubkeyhash",
				"addresses":	["DNbAcP82bpd9xdXNA1Vtf1Vo6yqP1rZvcu"]
			}
		}, {
			"value":	0.10000000,
			"n":	1,
			"scriptPubKey":	{
				"asm":	"OP_DUP OP_HASH160 14b24a5b6f8c8df0f7c9b519d362618ca211e609 OP_EQUALVERIFY OP_CHECKSIG",
				"hex":	"76a91414b24a5b6f8c8df0f7c9b519d362618ca211e60988ac",
				"reqSigs":	1,
				"type":	"pubkeyhash",
				"addresses":	["D72Xdw5cVyuX9JLivLxG3V9awpvj7WvsMi"]
			}
		}]
})
variant.3764 [Client address is       181.112.16.145 | Client port is  57282] sdconn.14
got packet.(F) len.12304 from (181.112.16.145)
got.(F) packet from 181.112.16.145, len 12304 (8989816935121514892 vs NXT.8989816935121514892) LTC LRQ3ZyrZDhvKFkcbmC6cLutvJfPbxnYUep <-> otherNXT.423766016895692955
got funding.(01000000018c5009886324fbfcffad438ce3db7d375dfb236c51a7e1feac6fa8ed5e0013db000000006b483045022100f7461b956b9db8108219fc10e3076dba591fb72009bd96e21d49a934d67595fe0220243aec585a7533fe64433eff006de5069037cca815220280482112e8694751ad0121033f1da089735ac76e77f689efc679f9c332487c63c8df5142e759c51854c780e1ffffffff03d0e896000000000017a914fa3b5500b16e2d014048b0c89ba5685909a77c04871fd4583a000000001976a91443b95805905c01575d9e5d37f77e83c10b531ae788ac10270000000000001976a914cf9c30a4d4fa710a13025f9292a178de55bed0df88ac00000000)
broadcasting is disabled for now: (01000000018c5009886324fbfcffad438ce3db7d375dfb236c51a7e1feac6fa8ed5e0013db000000006b483045022100f7461b956b9db8108219fc10e3076dba591fb72009bd96e21d49a934d67595fe0220243aec585a7533fe64433eff006de5069037cca815220280482112e8694751ad0121033f1da089735ac76e77f689efc679f9c332487c63c8df5142e759c51854c780e1ffffffff03d0e896000000000017a914fa3b5500b16e2d014048b0c89ba5685909a77c04871fd4583a000000001976a91443b95805905c01575d9e5d37f77e83c10b531ae788ac10270000000000001976a914cf9c30a4d4fa710a13025f9292a178de55bed0df88ac00000000) ->
({
	"txid":	"a84a3dad2154a876cd9012b40f86557beaa4d5180b34a39c8f986a99acbce0b3",
	"version":	1,
	"locktime":	0,
	"vin":	[{
			"txid":	"db13005eeda86facfee1a7516c23fb5d377ddbe38c43adfffcfb24638809508c",
			"vout":	0,
			"scriptSig":	{
				"asm":	"3045022100f7461b956b9db8108219fc10e3076dba591fb72009bd96e21d49a934d67595fe0220243aec585a7533fe64433eff006de5069037cca815220280482112e8694751ad01 033f1da089735ac76e77f689efc679f9c332487c63c8df5142e759c51854c780e1",
				"hex":	"483045022100f7461b956b9db8108219fc10e3076dba591fb72009bd96e21d49a934d67595fe0220243aec585a7533fe64433eff006de5069037cca815220280482112e8694751ad0121033f1da089735ac76e77f689efc679f9c332487c63c8df5142e759c51854c780e1"
			},
			"sequence":	4294967295
		}],
	"vout":	[{
			"value":	0.09890000,
			"n":	0,
			"scriptPubKey":	{
				"asm":	"OP_HASH160 fa3b5500b16e2d014048b0c89ba5685909a77c04 OP_EQUAL",
				"hex":	"a914fa3b5500b16e2d014048b0c89ba5685909a77c0487",
				"reqSigs":	1,
				"type":	"scripthash",
				"addresses":	["3QW7vxroQj7ro8MfHtbGgsnMfhavpciDw4"]
			}
		}, {
			"value":	9.78899999,
			"n":	1,
			"scriptPubKey":	{
				"asm":	"OP_DUP OP_HASH160 43b95805905c01575d9e5d37f77e83c10b531ae7 OP_EQUALVERIFY OP_CHECKSIG",
				"hex":	"76a91443b95805905c01575d9e5d37f77e83c10b531ae788ac",
				"reqSigs":	1,
				"type":	"pubkeyhash",
				"addresses":	["LRQ3ZyrZDhvKFkcbmC6cLutvJfPbxnYUep"]
			}
		}, {
			"value":	0.00010000,
			"n":	2,
			"scriptPubKey":	{
				"asm":	"OP_DUP OP_HASH160 cf9c30a4d4fa710a13025f9292a178de55bed0df OP_EQUALVERIFY OP_CHECKSIG",
				"hex":	"76a914cf9c30a4d4fa710a13025f9292a178de55bed0df88ac",
				"reqSigs":	1,
				"type":	"pubkeyhash",
				"addresses":	["Le9hFCEGKDKp7qYpzfWyEFAq58kSQsjAqX"]
			}
		}]
})
variant.3764 [Client address is       181.112.16.145 | Client port is  57290] sdconn.14
got packet.(T) len.12304 from (181.112.16.145)
got.(T) packet from 181.112.16.145, len 12304 (8989816935121514892 vs NXT.8989816935121514892) LTC LRQ3ZyrZDhvKFkcbmC6cLutvJfPbxnYUep <-> otherNXT.423766016895692955
[ 1.00%] Received   0.00097799 of   0.09780000 | Sent  95.80000000 of  95.80000000
variant.3764 [Client address is       181.112.16.145 | Client port is  57304] sdconn.14
got packet.(T) len.12304 from (181.112.16.145)
got.(T) packet from 181.112.16.145, len 12304 (8989816935121514892 vs NXT.8989816935121514892) LTC LRQ3ZyrZDhvKFkcbmC6cLutvJfPbxnYUep <-> otherNXT.423766016895692955
[ 2.00%] Received   0.00195599 of   0.09780000 | Sent   0.95800000 of  95.80000000
variant.3764 [Client address is       181.112.16.145 | Client port is  57317] sdconn.14
got packet.(T) len.12304 from (181.112.16.145)
got.(T) packet from 181.112.16.145, len 12304 (8989816935121514892 vs NXT.8989816935121514892) LTC LRQ3ZyrZDhvKFkcbmC6cLutvJfPbxnYUep <-> otherNXT.423766016895692955
[ 3.00%] Received   0.00293400 of   0.09780000 | Sent   1.91600000 of  95.80000000
variant.3764 [Client address is       181.112.16.145 | Client port is  57330] sdconn.14
got packet.(T) len.12304 from (181.112.16.145)
got.(T) packet from 181.112.16.145, len 12304 (8989816935121514892 vs NXT.8989816935121514892) LTC LRQ3ZyrZDhvKFkcbmC6cLutvJfPbxnYUep <-> otherNXT.423766016895692955
[ 4.00%] Received   0.00391199 of   0.09780000 | Sent   2.87400000 of  95.80000000
variant.3764 [Client address is       181.112.16.145 | Client port is  57343] sdconn.14
got packet.(T) len.12304 from (181.112.16.145)
got.(T) packet from 181.112.16.145, len 12304 (8989816935121514892 vs NXT.8989816935121514892) LTC LRQ3ZyrZDhvKFkcbmC6cLutvJfPbxnYUep <-> otherNXT.423766016895692955
[ 5.00%] Received   0.00489000 of   0.09780000 | Sent   3.83200000 of  95.80000000
variant.3764 [Client address is       181.112.16.145 | Client port is  57358] sdconn.14
got packet.(T) len.12304 from (181.112.16.145)
got.(T) packet from 181.112.16.145, len 12304 (8989816935121514892 vs NXT.8989816935121514892) LTC LRQ3ZyrZDhvKFkcbmC6cLutvJfPbxnYUep <-> otherNXT.423766016895692955
[ 6.00%] Received   0.00586800 of   0.09780000 | Sent   4.79000000 of  95.80000000
variant.3764 [Client address is       181.112.16.145 | Client port is  57371] sdconn.14
got packet.(T) len.12304 from (181.112.16.145)
got.(T) packet from 181.112.16.145, len 12304 (8989816935121514892 vs NXT.8989816935121514892) LTC LRQ3ZyrZDhvKFkcbmC6cLutvJfPbxnYUep <-> otherNXT.423766016895692955
[ 7.00%] Received   0.00684600 of   0.09780000 | Sent   5.74800000 of  95.80000000
variant.3764 [Client address is       181.112.16.145 | Client port is  57383] sdconn.14
got packet.(T) len.12304 from (181.112.16.145)
got.(T) packet from 181.112.16.145, len 12304 (8989816935121514892 vs NXT.8989816935121514892) LTC LRQ3ZyrZDhvKFkcbmC6cLutvJfPbxnYUep <-> otherNXT.423766016895692955
[ 8.00%] Received   0.00782399 of   0.09780000 | Sent   6.70600000 of  95.80000000
variant.3764 [Client address is       181.112.16.145 | Client port is  57397] sdconn.14
got packet.(T) len.12304 from (181.112.16.145)
got.(T) packet from 181.112.16.145, len 12304 (8989816935121514892 vs NXT.8989816935121514892) LTC LRQ3ZyrZDhvKFkcbmC6cLutvJfPbxnYUep <-> otherNXT.423766016895692955
[ 9.00%] Received   0.00880200 of   0.09780000 | Sent   7.66400000 of  95.80000000
variant.3764 [Client address is       181.112.16.145 | Client port is  57409] sdconn.14
got packet.(T) len.12304 from (181.112.16.145)
got.(T) packet from 181.112.16.145, len 12304 (8989816935121514892 vs NXT.8989816935121514892) LTC LRQ3ZyrZDhvKFkcbmC6cLutvJfPbxnYUep <-> otherNXT.423766016895692955
[10.00%] Received   0.00978000 of   0.09780000 | Sent   8.62200000 of  95.80000000
...

jl777 · « **Reply #91 on:** April 24, 2014, 01:11:56 am »

prev v07 was DOA, I updated with new v07

swartzfeger · « **Reply #92 on:** April 24, 2014, 01:13:05 am »

Quote from: jl777 on April 24, 2014, 01:11:56 am

prev v07 was DOA, I updated with new v07

We had port connection errors, chanc3r should have a paste bin soon (and he's done for the night, waaaay past his bed time).

chanc3r · « **Reply #93 on:** April 24, 2014, 01:16:05 am »

Summary of Jay / my joint testing with some quick bug fixing from James..

We each submitted our trades into NXT via AM's
Subatomic:

found and matched the trades
bound to our respective DOGE and LTC local wallets
Set up the data for the exchange..
Discovering our wallet public keys..
Exchanged our IP Adresses...

Problem that stopped us - direct transmission of public keys between the two IPs...

nite...

jl777 · « **Reply #94 on:** April 24, 2014, 01:22:42 am »

Quote from: chanc3r on April 24, 2014, 01:16:05 am

Summary of Jay / my joint testing with some quick bug fixing from James..

We each submitted our trades into NXT via AM's
Subatomic:

found and matched the trades
bound to our respective DOGE and LTC local wallets
Set up the data for the exchange..
Discovering our wallet public keys..
Exchanged our IP Adresses...

Problem that stopped us - direct transmission of public keys between the two IPs...

nite...

If anybody knows of C code that can establish contact directly between peers, let me know. As soon as we get a reliable solution for that, all this will work wonderfully.

James

Edit: It seems I need a hole puncher! http://www.brynosaurus.com/pub/net/p2pnat/

swartzfeger · « **Reply #95 on:** April 24, 2014, 04:40:40 am »

Quote from: jl777 on April 24, 2014, 01:22:42 am

Edit: It seems I need a hole puncher! http://www.brynosaurus.com/pub/net/p2pnat/

How difficult is this NAT hole punch?

Sent from my iPhone using Tapatalk

jl777 · « **Reply #96 on:** April 24, 2014, 05:20:03 am »

Quote from: swartzfeger on April 24, 2014, 04:40:40 am

Quote from: jl777 on April 24, 2014, 01:22:42 am
Edit: It seems I need a hole puncher! http://www.brynosaurus.com/pub/net/p2pnat/

How difficult is this NAT hole punch?

Sent from my iPhone using Tapatalk

I think it could be a whole new project...
Then again I might already have a hole puncher implemented

James

jl777 · « **Reply #97 on:** April 24, 2014, 09:44:16 am »

http://209.126.71.170/NXTsubatomic_v08.zip has a test version

It is only to test the hole punching and whether the peer to peer comms work. I am almost done integrating it into NXTsubatomic, but couldnt quite get it debugged. Have to implement a checksum and retry layer on top of UDP, so not exactly a single late night task. The networking code is being overhauled, but since it couldnt even establish contact, you probably wont notice much of a difference.

Before I fully transition to this networking method, I need to know if it actually solves the problem.

I added a realtime chat to NXTsubatomic. Just start it like normal and if you dont have a "group" field in your description JSON, it will prompt you for a group to join. It can be anything, but for NXTsubatomic, I just use that. The following are the commands, they start with /

'?' to list online group members
'/member' to connect to 'member'
'/close member' to close a conversation with member
'/close' to close all conversations
'/rtt' to toggle printing of round trip times
'/status busy' sets the user status to 'busy'
'/help' for this information
'/exit' to exit group

Once corresponding, any text typed is sent to all correspondents. If corresponding with several users, prefix text with '@name' to send to just one

18 hours ago, I would have never imagined that I would have added a chat system to NXTsubatomic, but hole punching was a serious issue that has to be solved. It is limited to small text packets, but I already added binary data support, packetization with crc, feedback, so hopefully it is just a little more debugging and we can get back to testing actual functionality. I think I will add a command to send a file, later I can add encryption. I think NXTmixer will fit in nicely.

I also managed to get 90% of NXTatomic coded and debugged. All that is left is the networking comms.

I also made good progress on figuring out how to do atomic BTC <-> NXT exchange. I just need to find out two more critical issues to know if it can be done or not.

So, for this one, anybody with a Mac can test. Just download the zip, run the executable inside and join the NXTsubatomic group and see if you are able to contact the other peers

James

chanc3r · « **Reply #98 on:** April 24, 2014, 10:04:03 am »

Quote from: jl777 on April 24, 2014, 09:44:16 am

http://209.126.71.170/NXTsubatomic_v08.zip has a test version

So, for this one, anybody with a Mac can test. Just download the zip, run the executable inside and join the NXTsubatomic group and see if you are able to contact the other peers

James

Got it
Joined the channel
its working I think
trying to talk to someone called jl777 - maybe he's asleep

could be really cool built into the trade model...
as long as its not like the btc-e troll box

jl777 · « **Reply #99 on:** April 24, 2014, 10:14:10 am »

Quote from: chanc3r on April 24, 2014, 10:04:03 am

Quote from: jl777 on April 24, 2014, 09:44:16 am
http://209.126.71.170/NXTsubatomic_v08.zip has a test version

So, for this one, anybody with a Mac can test. Just download the zip, run the executable inside and join the NXTsubatomic group and see if you are able to contact the other peers

James

Got it
Joined the channel
its working I think
trying to talk to someone called jl777 - maybe he's asleep

could be really cool built into the trade model...
as long as its not like the btc-e troll box

I sent some chat, did you get it?

jl777 · « **Reply #100 on:** April 24, 2014, 10:15:47 am »

Quote from: chanc3r on April 24, 2014, 10:04:03 am

Quote from: jl777 on April 24, 2014, 09:44:16 am
http://209.126.71.170/NXTsubatomic_v08.zip has a test version

So, for this one, anybody with a Mac can test. Just download the zip, run the executable inside and join the NXTsubatomic group and see if you are able to contact the other peers

James

Got it
Joined the channel
its working I think
trying to talk to someone called jl777 - maybe he's asleep

could be really cool built into the trade model...
as long as its not like the btc-e troll box

You need to type
/jl777

to establish contact. just being in the same group isnt enough

chanc3r · « **Reply #101 on:** April 24, 2014, 10:39:23 am »

Quote from: jl777 on April 24, 2014, 10:14:10 am

Quote from: chanc3r on April 24, 2014, 10:04:03 am
Quote from: jl777 on April 24, 2014, 09:44:16 am
http://209.126.71.170/NXTsubatomic_v08.zip has a test version

So, for this one, anybody with a Mac can test. Just download the zip, run the executable inside and join the NXTsubatomic group and see if you are able to contact the other peers

James

Got it
Joined the channel
its working I think
trying to talk to someone called jl777 - maybe he's asleep

could be really cool built into the trade model...
as long as its not like the btc-e troll box
I sent some chat, did you get it?

Yeah sorry -replied - was on phone
My prompt looks like this

[jl777] chan3test/NXTsubatomic >>

so I assume I am connected to you.

-------------

Think there is a minor reconnection bug...
If I leave a group and then try to rejoin I get this

group name : NXTsubatomic
Connecting as 'chan3test' in group 'NXTsubatomic'
Server is at: 209.126.71.170:60218 (colo.hostirian.com)
server rejected user/group: group member with this name already exists

so it still thinks I'm connected after i've left..
might cause problems.

--------------

Question on the 'hole punch'

Read the doc you posted.

Have you implemented the one where the server helps two clients to establish a connection and then the server drops out of the conversation? OR does the server STAY IN the conversation...

IF not I am concerned about the risk of the server being able to 'change' the conversation between the two peers - a kind of spoofing of the trade... e.g. you think you are receiving person A's keys but the dest key has been swapped by Evil Bobs server for Bobs key so you start sending to Evil Bob thinking its the nice person you started the trade with...

I think the TX logic will detect it but not sure it can then reverse/refund it if bob is clever about which subatomic components he spoofs... Need to look deeper - its the introduction of the server that has made me think about malleability of the direct conversation between the two peers.

EDIT: If we are super paranoid - sign all direct TX messages with senders private key, they can't then be changed and receiver can decode with public key just like other tokens, then it doesn't matter what path the communication flows.,,, Evil Bob can watch and howl in frustration because he can't change the packets...

jl777 · « **Reply #102 on:** April 24, 2014, 07:22:38 pm »

Quote from: chanc3r on April 24, 2014, 01:42:19 pm

Question on the 'hole punch'

Read the doc you posted.

Have you implemented the one where the server helps two clients to establish a connection and then the server drops out of the conversation? OR does the server STAY IN the conversation...

IF not I am concerned about the risk of the server being able to 'change' the conversation between the two peers - a kind of spoofing of the trade... e.g. you think you are receiving person A's keys but the dest key has been swapped by Evil Bobs server for Bobs key so you start sending to Evil Bob thinking its the nice person you started the trade with...

I think the TX logic will detect it but not sure it can then reverse/refund it if bob is clever about which subatomic components he spoofs... Need to look deeper - its the introduction of the server that has made me think about malleability of the direct conversation between the two peers.

EDIT: If we are super paranoid - sign all direct TX messages with senders private key, they can't then be changed and receiver can decode with public key just like other tokens, then it doesn't matter what path the communication flows.,,, Evil Bob can watch and howl in frustration because he can't change the packets...

it is just a directory service. One you get the info on the peers, it is all locally maintained. I will most definitely add the tokened security before launch, it is just a pain to have to generate a token for every request.

I pushed the source to a modified version of http://basyl.co.uk/code/punch/doc/files/Readme-txt.html
It was a guy's toy project, and had some bugs, but easy to fix and I was able to integrate it into the source base pretty quickly. Enhancement for binary message support is working. Packetization is still a bit buggy, but not surprising since I coded it during hours 12+ of my coding day. Stuff like that is better during the first hours

Since peer to peer comms are pretty central to crypto, I figure its worth a couple day delay to get all this sorted. With the chat service active, I hope once I add windows support, we will be able to get more testers

James

--------------------------

Quote from: chanc3r on April 24, 2014, 11:04:19 am

Think there is a minor reconnection bug...
If I leave a group and then try to rejoin I get this

group name : NXTsubatomic
Connecting as 'chan3test' in group 'NXTsubatomic'
Server is at: 209.126.71.170:60218 (colo.hostirian.com)
server rejected user/group: group member with this name already exists

so it still thinks I'm connected after i've left..
might cause problems.

I've destabilized it a bit with lots of code changes. The most important thing for me to know is if you are able to chat with Jay. If you can that means the "cant open connection" problem is fixed and there are no roadblocks

James

---------------

http://209.126.71.170/NXTsubatomic_v09.ubuntu.zip
http://209.126.71.170/NXTsubatomic_v09.mac.zip

I think I stabilized the chat, at least it seems to work for me. While I was fixing bugs, I added automatic authentication using NXT tokens.

When you login to the chat, you MUST use the "name" from the AccountInfo, otherwise you will get rejected. You also need to make sure your time is synced to ntp, or you will get rejected. In the description field of Accountinfo, you need to set "username":"<username on your PC>" so it can find the coin daemons. If you set a "group" field, it will automatically log into that chat group. "NXTsubatomic" is where the default group is for now

Oh, I made it open a new terminal window for Mac so the chat is totally separate from all the debug printouts.

Oh, yes, what took most of the time was making it encrypt every chat message using a session specific public/private key. I use nacl library http://cr.yp.to/highspeed/naclcrypto-20090310.pdf e Curve25519 elliptic-curve-Diffie Hellman function, the Salsa20 stream cipher, and the Poly1305 message-authentication code. A 24 byte high entropy nonce is used for every message.

Now that encryption is part of the dataflow, we are one step closer to NXTmixer!

When you are doing a chat,you can always agree to go to a private group as you need to specify the destination or it goes to everyone in the group.

It would really be nice if we can verify that multiple people can all do encrypted chat. The server is used as a directory, but all the chats are point to point UDP using the hole puncher.

James

P.S. The ubuntu version does not spawn a new window, but it should work fine.

Edit: I am seeing several attempts to login without a name set. You need to do a setAccountInfo command from http://127.0.0.1:6876/test and set the name field (first one). Without that it wont authenticate

Daedelus · « **Reply #103 on:** April 25, 2014, 11:22:59 am »

Has your contract been renewed yet?

If not, I feel a NIP coming on

Mistafreeze · « **Reply #104 on:** April 25, 2014, 11:55:20 am »

Quote from: Daedelus on April 25, 2014, 11:22:59 am

Has your contract been renewed yet?

If not, I feel a NIP coming on

+ eleventy billion

chanc3r · « **Reply #105 on:** April 25, 2014, 12:44:08 pm »

Quote from: jl777 on April 25, 2014, 11:21:04 am

When you login to the chat, you MUST use the "name" from the AccountInfo, otherwise you will get rejected. You also need to make sure your time is synced to ntp, or you will get rejected. In the description field of Accountinfo, you need to set "username":"<username on your PC>" so it can find the coin daemons. If you set a "group" field, it will automatically log into that chat group. "NXTsubatomic" is where the default group is for now

http://127.0.0.1:6876/test and set the name field (first one). Without that it won't authenticate

Below is the section of that webpage you need to fill in... Needless to say you need a copy of NRS running with isTestNet=true in the config file....

An old reminder - ON TESTNET 'Don't use the same passphrase that you use on Main Net'

Where it says {"user":"chanc3r"} put in your own username

If you want to specify the default group I think its

{"user":"<your username>","group":"NXTsubatomic"}

You will also need a bit of test NXT, NQT amount is actually 1 NXT

It can take a bit of effort to get going but please join in....

jl777 · « **Reply #106 on:** April 26, 2014, 02:09:09 am »

InstantDEX will be issued and distributed on launch day, however there will be no official or unofficial IPO. There never was a public investment window to make sure that we avoid any regulatory issues. That being said I cannot control what people do with the InstantDEX they have. I expect that some people might put some up for sale on the AE, especially if there are bids. The only price point for InstantDEX to date is 7.5 NXT per InstantDEX asset.

There will be 1,000,000 InstantDEX issued.
jl777 30%
wesleyh 30%
aldrin 20%
consultants and advisors 9% (Come-from-Beyond, AdamLevine, fanaticalfishing, chanc3r, joefox, NXTminnow, allwelder)
InstantDEX working capital 11%

InstantDEX will generate revenues by charging 0.1% to 0.2% of transactions. If it is 0.2% to each side of the trade, that is a total of 0.4% of all trade volume. If InstantDEX is able to sustain a daily trade volume of 250 BTC -> 1 BTC/day of revenues.

InstantDEX will launch by supporting trading in multigateway assets, but it is asset agnostic and can be used for trading any NXT asset. Due to the tech not being completed yet, there is no launch date for InstantDEX. The main tech components are a UDP hole punching peer to peer comm system that enables not only realtime trade matching, but off blockchain nearly atomic trade settlements. Due to the differences in bitcoind forks (NXTsubatomic) and NXT transactions (NXTatomic), it is not clear yet if there is a way to directly connect the two types of trades. In that event multigateway services might be required. Also due to transaction malleability issues, it is not clear how many confirmations will be needed to be able to safely finalize trades.

InstantDEX will let people change their bid/ask without fees and only charge when a trade happens. The goal of InstantDEX is to provide a fully decentralized peer-to-peer realtime trustless trading environment. There is no guarantee that this ideal goal will be 100% achieved, but I will continue to innovate and improve the tech to get as close as possible. I believe that it is important to provide the market what the market wants, instead of forcing something against what the market wants. To that end, InstantDEX will allow for trading of any NXT asset, NXT, bitcoind crypto against each other. I will also test market using ripple IOU's for USD and CNY to see if such a proxy of a proxy will be acceptable for traders. If it is, then it will be fully integrated into InstantDEX

Wesleyh will work hard to make InstantDEX as easy to use as possible. Since we wont have large server expenses no matter how many active traders there are, our overhead will be the lowest in the industry. This will allow InstantDEX to have lower fees initially to gain marketshare. Exact specifics on fees are subject to change, with reasonable notice given to the customers.

It is expected that half the revenues will be distributed to InstantDEX holders, but probably not until there is an easy to use dividend mechanism. Exact distribution amounts and timing are subject to change. InstantDEX currently has over 1.5 million NXT 4383817337783094122 and I do not expect that we will need any additional capital to fund continued operations.

NXTsubatomic and NXTatomic will be part of InstantDEX. I believe both have no fundamental security issues, but due to the cutting edge nature of their implementation, it is possible for there to be incidents. We will of course do our best to avoid any such incidents, just a risk factor to keep in mind. Also, in the event that I or anybody else solves the BTC <-> NXT direct atomic exchange, I will of course integrate that tech into InstantDEX.

I cant make any promises about availability of InstantDEX, but if people posted their interest, that could help some of the holders to decide to put some up for sale.

The following threads have info on the progress of the tech:
https://nxtforum.org/multigateway-jl777/nxtsubatomic-atomic-crosschain-exchange/ and https://nxtforum.org/multigateway-jl777/secret-project/

James

swartzfeger · « **Reply #107 on:** April 26, 2014, 08:20:54 am »

James, chanc3r, whomever -- have we actually completed a subatomic trade yet, do we have a hole punch, etc?

I'm awake for another two hours if someone wants to test with me.

chanc3r · « **Reply #108 on:** April 26, 2014, 12:35:10 pm »

James,
will v09 likely work end 2 end for an actual TX or are you focussing on encrypted comms in that one.
I can try to set up a test again with Swartz(Jay) and see how far we get this time but only worth trying and debugging it if you feel the subatomic parts are sufficiently integrated.
Ian

jl777 · « **Reply #109 on:** April 26, 2014, 05:42:16 pm »

Quote from: chanc3r on April 26, 2014, 12:35:10 pm

James,
will v09 likely work end 2 end for an actual TX or are you focussing on encrypted comms in that one.
I can try to set up a test again with Swartz(Jay) and see how far we get this time but only worth trying and debugging it if you feel the subatomic parts are sufficiently integrated.
Ian

After three consecutive all nighters, it seems I slept for a long time!
Wait for v10, that will integrate encrypted hole punch UDP and subatomic comms. I think I will generalize the encrypted UDP comms so any NXTprotocol handler can automatically establish encrypted links with any other NXT account. A bit of a delay for everything, but well worth the added functionality

James

Daedelus · « **Reply #110 on:** April 26, 2014, 06:13:28 pm »

I'm still here too

I think it's just the four of us...

If we were all together in the same place, I'd be the one making the tea

swartzfeger · « **Reply #111 on:** April 26, 2014, 06:45:41 pm »

The next two days I work 24+ hours, then I'm off Mon/Tue/Wed. I can log a lot of test time starting early Monday morning.

Sent from my iPhone using Tapatalk

chanc3r · « **Reply #112 on:** April 26, 2014, 06:51:02 pm »

Quote from: swartzfeger on April 26, 2014, 06:45:41 pm

The next two days I work 24+ hours, then I'm off Mon/Tue/Wed. I can log a lot of test time starting early Monday morning.

Sent from my iPhone using Tapatalk

Jay/James - I'm flying to Africa all day tomorrow, then I'm GMT+3 Mon/Tues/Wed

Jay - will be looking out for you on Monday morning / Monday night for me..

James - its a long flight and will be reviewing NXTsubatomic v6 .h unless you send me an update

Ian

jl777 · « **Reply #113 on:** April 26, 2014, 10:29:33 pm »

Quote from: chanc3r on April 26, 2014, 06:51:02 pm

Quote from: swartzfeger on April 26, 2014, 06:45:41 pm
The next two days I work 24+ hours, then I'm off Mon/Tue/Wed. I can log a lot of test time starting early Monday morning.

Sent from my iPhone using Tapatalk

Jay/James - I'm flying to Africa all day tomorrow, then I'm GMT+3 Mon/Tues/Wed

Jay - will be looking out for you on Monday morning / Monday night for me..

James - its a long flight and will be reviewing NXTsubatomic v6 .h unless you send me an update

Ian

I PM'ed you details. I am working on a really cool transport layer that I think will actually be an improvement over how everybody else is doing peer-to-peer comms. Of course, I do it the way everybody has to via sockets, but I hate sockets and I bet a lot of other coders do too.

So, I am making peer to peer comms interface that I wished was already there.

Details end of this weekend or even early next week. With this new API that I will use in the other projects, it will dramatically simplify things, especially multigateway and even NXTorrent.

James

swartzfeger · « **Reply #114 on:** April 28, 2014, 07:14:16 am »

James, I've lost track... what's the latest version, v9? Do you have an updated link so I can be ready to roll when Ian and I get our schedules synced?

jl777 · « **Reply #115 on:** April 28, 2014, 07:36:29 am »

Quote from: swartzfeger on April 28, 2014, 07:14:16 am

James, I've lost track... what's the latest version, v9? Do you have an updated link so I can be ready to roll when Ian and I get our schedules synced?

UDP hole punching is no picnic. Been battling it all weekend, finally got file transfers to be somewhat reliable. Once that is done, then it will be much easier to get the rest done.

Aiming for release as soon as possible, but very difficult stuff. Everything is encrypted with session based keys and all file transfers require NXT token authorization. This prevents spoofing via man in the middle attacks.

I also got it so that the directory server can disappear and peer to peer comms continue. Of course making new peerto peer connections wont be possible until the server comes back, but I almost got a decentralized directory server to work, but it just wasnt cooperating and it was taking too long.

So, next version will be v10, but could be another day or two.

James

swartzfeger · « **Reply #116 on:** April 30, 2014, 07:31:20 am »

Quote from: jl777 on April 28, 2014, 07:36:29 am

Quote from: swartzfeger on April 28, 2014, 07:14:16 am
James, I've lost track... what's the latest version, v9? Do you have an updated link so I can be ready to roll when Ian and I get our schedules synced?
UDP hole punching is no picnic. Been battling it all weekend, finally got file transfers to be somewhat reliable. Once that is done, then it will be much easier to get the rest done.

Aiming for release as soon as possible, but very difficult stuff. Everything is encrypted with session based keys and all file transfers require NXT token authorization. This prevents spoofing via man in the middle attacks.

I also got it so that the directory server can disappear and peer to peer comms continue. Of course making new peerto peer connections wont be possible until the server comes back, but I almost got a decentralized directory server to work, but it just wasnt cooperating and it was taking too long.

So, next version will be v10, but could be another day or two.

James

Taking a quick pulse check. How're things going, James?

jl777 · « **Reply #117 on:** April 30, 2014, 07:59:45 am »

Finally got UDP hole punched peer to peer xfers somewhat stable
Still need to manually make sure the comms are getting through
Switching to sending files instead of debugging sharedmem for now
lost internet just as I was testing the pubkey swapping

pretty late for me, so no release till tomorrow, but I am debugging NXTsubatomic using NXTsync now, so pretty good bet a test release within 24 hours

James

allwelder · « **Reply #118 on:** May 01, 2014, 12:31:44 am »

Waiting for Windows test.

jl777 · « **Reply #119 on:** May 02, 2014, 05:37:56 am »

Almost had a subatomic transaction happen via NXTsync, but things werent quite in sync
After a week of UDP wonkiness, I figured Windows couldnt be as bad, so I started porting everything to Windows.
Down to just 12 compiler errors. Of course, need to make networking and timers and threads cross platform, plus all the other libraries, but not as bad as I feared

James

swartzfeger · « **Reply #120 on:** May 02, 2014, 06:36:22 am »

Quote from: jl777 on May 02, 2014, 05:37:56 am

Almost had a subatomic transaction happen via NXTsync, but things werent quite in sync
After a week of UDP wonkiness, I figured Windows couldnt be as bad, so I started porting everything to Windows.
Down to just 12 compiler errors. Of course, need to make networking and timers and threads cross platform, plus all the other libraries, but not as bad as I feared

James

Can we expect v10 this weekend?

jl777 · « **Reply #121 on:** May 02, 2014, 07:14:49 am »

Quote from: swartzfeger on May 02, 2014, 06:36:22 am

Quote from: jl777 on May 02, 2014, 05:37:56 am
Almost had a subatomic transaction happen via NXTsync, but things werent quite in sync
After a week of UDP wonkiness, I figured Windows couldnt be as bad, so I started porting everything to Windows.
Down to just 12 compiler errors. Of course, need to make networking and timers and threads cross platform, plus all the other libraries, but not as bad as I feared

James
yes

Can we expect v10 this weekend?

jl777 · « **Reply #122 on:** May 03, 2014, 10:33:53 pm »

It is finally there 209.126.71.170/NXTsubatomic_v10.zip

This version has NXTsync built into it
It is only for MAC
As before, you need to get all the fields right to make sure you match up with the other party
It is critical that you establish direct UDP contact with the other party.

Currently, the name used for the chat is set to the name that your NXT account has been set to. Let's assume bob and alice are trading with each other. To establish UDP contact, you need to hole punch by /<chat name>

So bob would type:
/alice

And alice would type:
/bob

You need to verify this is working by just chatting a bit by typing anything to each other. You can even send files by typing @<chat name> "<filename>"

The file will just get stored in /tmp/<filename> This is not really a supported feature yet, but might as well test it to see how well it works.

OK, so assuming there is good comms between alice and bob and NXTsubatomic matches up the trade properly from the AM's that are submitted, it will start the overlapped negotiations. Now that bidirectional comms are working, I decided to go to a state machine driven process to incrementally complete the transaction. There will be ~100 actual transactions for each side during this process and if all goes well you will see the percentage printed once per second.

There will also be printouts of the raw transactions that are being created. Currently not being broadcast, so this wont actually do any transactions. However, the signed raw transactions would actually send money if you manually broadcast it. Once we get verification on the accuracy of the transactions and the process, I will enable the submission to the respective networks.

So, I will await test results and until then, this project for me is on hold

James

chanc3r · « **Reply #123 on:** May 03, 2014, 11:03:54 pm »

Quote from: jl777 on May 03, 2014, 10:33:53 pm

There will be ~100 actual transactions for each side during this process and if all goes well you will see the percentage printed once per second.

James - what does this mean in terms of the network tx fees for the xxxcoind being traded?

jl777 · « **Reply #124 on:** May 03, 2014, 11:47:58 pm »

Quote from: chanc3r on May 03, 2014, 11:03:54 pm

Quote from: jl777 on May 03, 2014, 10:33:53 pm
There will be ~100 actual transactions for each side during this process and if all goes well you will see the percentage printed once per second.

James - what does this mean in terms of the network tx fees for the xxxcoind being traded?

There will only be two network txfees, one for the funding tx and one for either the refund tx or the claiming tx. All the transactions are peer to peer. The key is that they are signed and as long as all the inputs are valid, good as money in pocket, at least thats the theory

swartzfeger · « **Reply #125 on:** May 04, 2014, 01:10:36 am »

Quote from: chanc3r on May 03, 2014, 11:03:54 pm

Quote from: jl777 on May 03, 2014, 10:33:53 pm
There will be ~100 actual transactions for each side during this process and if all goes well you will see the percentage printed once per second.

James - what does this mean in terms of the network tx fees for the xxxcoind being traded?

Ian, where in the world are you this weekend?

I should be home and ready to test by 3am EDT/7am GMT. Will you be awake and available?

I can test as late 11am GMT.

Sent from my iPhone using Tapatalk

jl777 · « **Reply #126 on:** May 04, 2014, 04:22:00 am »

I wanted to finish up the NXTatomic side of things. It went a LOT faster than the bitcoin stuff!

209.126.71.170/NXTsubatomic_v11.zip

No difference from v10, except that this one processes NXTatomic swaps using a method similar to the method described on https://nxtforum.org/nrs-releases/nrs-v0-9-9/msg10942/#msg10942

It doesnt actually submit the txbytes, and I have only tested NXT for NXT, which is not too useful, but proves the mechanism. I will add asset transfers next, so that you can swap NXT assets for NXT.

James

jl777 · « **Reply #127 on:** May 04, 2014, 08:35:09 am »

After doing both the NXTsubatomic and NXTatomic, I was hoping that I would be able to see how to combine them somehow. If I could, that would mean a trustless exchange of bitcoin (and any bitcoin fork) for NXT (actually any supported NXT tx, like asset transfer)

Ignoring the difficulty in actually specifying the trade, eg. having to generate the raw transaction bytes and prearranging an exchange, I did have an idea on how to create a hybrid NXTsubatomic-NXTatomic exhange. What to call it is a problem...

The big issue is that it is totally asymmetric, but I think I was able to get a pretty good approach to it initially coded up. Still need to debug and autocreate a reference trade, but the hard part was abstracting the NXTsubatomic process and interfacing the NXTatomic to that. That's done. Too late today to finish debugging, but now that the UDP wonkiness is behind me, it feels like driving on the open highway, instead of hacking through the jungle on foot

No promises, but NXTsubatomic_v12 could actually implement direct peer to peer bitcoin <-> NXT trades
However, before I can even test it, I will need to get a much better API for it, and also trade matching. This just happens to be very similar to what NXTorrent needs and it is sorely needing an update so I will switch to that tomorrow. Also need to finish porting to Windows. I am now just networking functions away from getting it to compile and link, but not sure what sorts of bugs there will be.

James

TimmyD · « **Reply #128 on:** May 04, 2014, 09:05:55 am »

Just keep it simple NXTomic

swartzfeger · « **Reply #129 on:** May 06, 2014, 11:05:42 pm »

Where are we, James?

jl777 · « **Reply #130 on:** May 06, 2014, 11:17:05 pm »

Quote from: swartzfeger on May 06, 2014, 11:05:42 pm

Where are we, James?

I'm fighting Windows trying to get networking stable on it.
I am also waiting for your test results with v11

btc2nxt · « **Reply #131 on:** May 09, 2014, 03:18:37 am »

Quote from: jl777 on April 24, 2014, 07:22:38 pm

http://209.126.71.170/NXTsubatomic_v09.ubuntu.zip

cannot run it .

incorrect command.

jl777 · « **Reply #132 on:** May 09, 2014, 03:26:13 am »

Quote from: btc2nxt on May 09, 2014, 03:18:37 am

Quote from: jl777 on April 24, 2014, 07:22:38 pm

http://209.126.71.170/NXTsubatomic_v09.ubuntu.zip

cannot run it .

incorrect command.

that is very old version. also I havent added POST support yet, so you need to disable that in the .conf file

allwelder · « **Reply #133 on:** May 09, 2014, 03:35:13 am »

when release the windows test ?

jl777 · « **Reply #134 on:** May 09, 2014, 03:44:30 am »

Quote from: allwelder on May 09, 2014, 03:35:13 am

when release the windows test ?

as soon as I get keyboard input to work properly, everything else seems to be working

allwelder · « **Reply #135 on:** May 09, 2014, 09:30:35 am »

Quote from: jl777 on May 09, 2014, 03:44:30 am

Quote from: allwelder on May 09, 2014, 03:35:13 am
when release the windows test ?
as soon as I get keyboard input to work properly, everything else seems to be working

wow,cannot wait to test it.

jl777 · « **Reply #136 on:** May 09, 2014, 09:37:24 am »

Quote from: allwelder on May 09, 2014, 09:30:35 am

Quote from: jl777 on May 09, 2014, 03:44:30 am
Quote from: allwelder on May 09, 2014, 03:35:13 am
when release the windows test ?
as soon as I get keyboard input to work properly, everything else seems to be working
wow,cannot wait to test it.

Here it is: https://nxtforum.org/multigateway-jl777/nxtservices-release-v00-includes-windows-mac-ubuntu/msg17712/#msg17712

allwelder · « **Reply #137 on:** July 08, 2014, 07:54:32 am »

this some same with

Quote

6. After Smart Leasing, ChuckOne plans to focus on Atomic Cross-Chain Trading

from https://nxtforum.org/news-and-announcements/development-roadmap-update-2014-07-05/ ?

News:

Author Topic: NXTsubatomic - atomic crosschain exchange & NXTatomic - atomic NXT tx swap (Read 36596 times)