Nxt Forum
Nxt Discussion => -Old and Inactive Projects- => Nxt Projects => Quack => Topic started by: blackyblack1 on January 07, 2016, 06:14:34 pm
-
Thread started here: https://nxtforum.org/general-discussion/quack-nxt-atomic-asset-swap/
-
Everyone fill free to add more Q and A to Quack FAQ.
-
abctc donated 15000 NXT to the project. Thanks!
-
I have uploaded the plugin to http://nxtplugins.com/
-
Version updated to 1.3: https://bitbucket.org/blackyblack/quackplugin/downloads/quack-1.3.zip
Fixed minor bug with status showing Expired instead of Done.
Client-side signing of the transactions supported.
-
I have installed the plugin on my node: http://91.235.72.49:7876/
Now you can give it a try without installing the plugin on your wallet.
The plugin supports client-side signing so it should be safe to enter your passphrase but I recommend to install the plugin on your local wallet for safety.
-
I have installed the plugin on my node: http://91.235.72.49:7876/
Now you can give it a try without installing the plugin on your wallet.
The plugin supports client-side signing so it should be safe to enter your passphrase but I recommend to install the plugin on your local wallet for safety.
Nope. Client-side signing does not work (just tried on the remote server). Will try to fix it shortly.
-
I have installed the plugin on my node: http://91.235.72.49:7876/
Now you can give it a try without installing the plugin on your wallet.
The plugin supports client-side signing so it should be safe to enter your passphrase but I recommend to install the plugin on your local wallet for safety.
Nope. Client-side signing does not work (just tried on the remote server). Will try to fix it shortly.
It was a tricky bit but I think I solved this issue. Will update the working client-side signing soon.
-
I have updated a version with client-side signing on my node http://91.235.72.49:7876/. Feel free to try it.
This fixed version is not released yet. Small delay till the weekend is over.
-
contact these guys: https://www.reddit.com/r/NXT/comments/40z6c7/impressed_by_the_nxt_decentralized_exchange_but/
-
contact these guys: https://www.reddit.com/r/NXT/comments/40z6c7/impressed_by_the_nxt_decentralized_exchange_but/
Contacted. Thanks.
-
Spent quite a lot of time debugging client-side signing. Looks like there is no way to implement client-side signing with "Remember password" option turned on. We will need to wait for NRS devs to fix it. Yet you can safely use Quack on remote hosts with this option switched off (if you believe that JS code was not tampered by node owner).
-
1.4 is here: https://bitbucket.org/blackyblack/quackplugin/downloads/quack-1.4.zip
What's new:
- Working client-side signing ("Remember Password" on remote nodes does not support client-side signing, do not use this feature)
- Fee calculation
-
Hey Quacky,
How this can be translated and introduced to wider audience?
-
Hey Quacky,
How this can be translated and introduced to wider audience?
Multi language UI is not supported. I can add support for multiple languages in the core and accept translations.
Do you have any specific language in mind?
-
I see, so you want to call NRS.signBytes(converters.byteArrayToHexString(transactionBytes) and let the client use the remembered passphrase.
I can add this to 1.7.5
"Remeber password" option on remote hosts will be possible to support in Quack when this fix will come.
-
New fees are active after block 621000. I will update FAQ and tutorial.
-
I mean Bulgarian language translation
-
I mean Bulgarian language translation
Will you create a Bulgarian translation if I'd add multilanguage support in Quack?
-
Nice article: http://coremedia.info/index.php/nxt-news/item/210-quack-decentralized-escrow-on-the-nxt-blockchain
Thanks to Core Media guys.
-
Is this right:
Quack uses a pre-prepared trigger transaction (any tx, could be a simple send message or NXT). This is not sent at first but the txhash is used as a condition of executing asset swap transactions from the two parties involved. Once it's set up and they can both see each others' tx on the blockchain, the trigger tx is sent and off they both go.
Why not use just two transactions? Could be done like this:
Alice creates a transaction to Bob, sending 10 superBTC when the secret of a hash is revealed.
Bob uses the txhash of that transaction as a condition to send 10 NEXTBOND to Alice.
Alice enters the secret phrase, and both txs execute.
-
Is this right:
Quack uses a pre-prepared trigger transaction (any tx, could be a simple send message or NXT). This is not sent at first but the txhash is used as a condition of executing asset swap transactions from the two parties involved. Once it's set up and they can both see each others' tx on the blockchain, the trigger tx is sent and off they both go.
Yes this is right.
Why not use just two transactions? Could be done like this:
Alice creates a transaction to Bob, sending 10 superBTC when the secret of a hash is revealed.
Bob uses the txhash of that transaction as a condition to send 10 NEXTBOND to Alice.
Alice enters the secret phrase, and both txs execute.
Alice's transaction will be created on the blockchain? How the secret of a hash is revealed? Does it require additional transaction?
If Bob is using the txhash of Alice's transaction and Alice's transaction is on the blockchain Bob's tx will be released immediately.
-
Why not use just two transactions? Could be done like this:
Alice creates a transaction to Bob, sending 10 superBTC when the secret of a hash is revealed.
Bob uses the txhash of that transaction as a condition to send 10 NEXTBOND to Alice.
Alice enters the secret phrase, and both txs execute.
Alice's transaction will be created on the blockchain? How the secret of a hash is revealed? Does it require additional transaction?
If Bob is using the txhash of Alice's transaction and Alice's transaction is on the blockchain Bob's tx will be released immediately.
Good point, I don't think that would work. Would need to check what happens with such a tx but I suspect you're right.
I'm just trying to understand what's possible here. There are building blocks that might be put together in any number of ways. Could be some very cool stuff that borders on smart contracts.
-
Ok I have no idea how to create a proper translation for a plugin... I could create separate releases for each language but do not like this solution.
-
This looks great blackyblack1.. Can this work for cross chain swaps?? like for ETH or BTC? that would be really handy.
-
This looks great blackyblack1.. Can this work for cross chain swaps?? like for ETH or BTC? that would be really handy.
I have started working on cross-chain atomic swap (BTC-NXT to start with) but put it aside to focus on FM project.