elective-stereophonic
elective-stereophonic
Shuffling Sunday ! (testing NRS 1.7.4 CoinShuffle, 10+17-01-2016 ) singapore
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Pages: 1 [2] 3 4 5  All

Author Topic: Shuffling Sunday ! (testing NRS 1.7.4 CoinShuffle, 10+17-01-2016 )  (Read 28498 times)

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #20 on: December 13, 2015, 01:16:05 pm »

You need 1012 NXT in order not to fail the shuffling, 1000 for the shuffling and 1+10+1 for the fees.
Thanks. So joining a shuffle you started is free? I've created two, both for 10 NXT, that I didn't join. I cancelled out of the second screen in the UI.  As I understand it, I could have joined them later, in a separate UI step, and I guess that would not have cost me anything because I'm the creator. Now both have expired, and I see in the ledger I have gained 3 NXT twice. Presumably that is 10 NXT for the shuffle less 7 NXT for the fine (I guess you get fined for not joining your own shuffle). So that seems to be working correctly as I understand it. The numbers were 5736017174669521577 and 8680532674290409359.

The shuffles were created for 3 participants. After two other accounts joined, was the final slot reserved for me? Was it listed as 2/3 but didn't allow other people to join? Did anyone notice if that worked correctly?

If one shuffling is marked as canceled (8680532674290409359) why is it prohibited to sign up for another shuffling with the same recipient account?
"Incorrect recipient public key. Another shuffler with the same recipient account already running"

- has already been answered:
The recipient accounts are created and their public keys announced as soon as the last participant completes processing. Even if the shuffling is cancelled after that, allowing them to be reused would reduce anonymity.
Sorry, lurker10, for using up your account number. Although I don't understand why you can't reuse it in this case. I did not join the shuffle myself, and when I click on 8680532674290409359 in the UI, no recipients are listed. Doesn't this mean the processing stage never completed and no public keys got announced? If they were announced, how can I see them? If they weren't announced, surely you should be able to reuse the recipient account?
Logged

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #21 on: December 13, 2015, 01:26:50 pm »

You need 1012 NXT in order not to fail the shuffling, 1000 for the shuffling and 1+10+1 for the fees.
It is better to leave some extra balance in the account for fees, not just 12 NXT. Even though at the end the total fees you will pay cannot exceed 12 NXT, if there are a few blockchain forks, in which the shuffling is in a different state, and your node switches from one to the other and back, your shuffler will need to submit more than one processing transaction, to match the shuffling state on each fork. So temporarily the fees for those multiple processing transactions will be deducted from your available balance, until one of the fork wins, then the other transactions will expire unconfirmed. But if you have planned to leave exactly 12 NXT for fees, and are unable to submit a processing transaction on the right fork because you already submitted on another one, the shuffling will fail and you will pay the penalty.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #22 on: December 13, 2015, 01:49:40 pm »

So joining a shuffle you started is free? I've created two, both for 10 NXT, that I didn't join. I cancelled out of the second screen in the UI.  As I understand it, I could have joined them later, in a separate UI step, and I guess that would not have cost me anything because I'm the creator. Now both have expired, and I see in the ledger I have gained 3 NXT twice. Presumably that is 10 NXT for the shuffle less 7 NXT for the fine (I guess you get fined for not joining your own shuffle). So that seems to be working correctly as I understand it. The numbers were 5736017174669521577 and 8680532674290409359.

The shuffles were created for 3 participants. After two other accounts joined, was the final slot reserved for me? Was it listed as 2/3 but didn't allow other people to join? Did anyone notice if that worked correctly?
When you create a shuffling, you automatically get registered for it as first participant. The joining step that you didn't do was supposed to start a shuffler, which is free. Those shufflings failed because you were not running a shuffler and did not submit processing transaction. The assignee account for a cancelled shuffling shows the account that was blamed for the shuffling failure.

Quote
If one shuffling is marked as canceled (8680532674290409359) why is it prohibited to sign up for another shuffling with the same recipient account?
"Incorrect recipient public key. Another shuffler with the same recipient account already running"

- has already been answered:
The recipient accounts are created and their public keys announced as soon as the last participant completes processing. Even if the shuffling is cancelled after that, allowing them to be reused would reduce anonymity.
Sorry, lurker10, for using up your account number. Although I don't understand why you can't reuse it in this case. I did not join the shuffle myself, and when I click on 8680532674290409359 in the UI, no recipients are listed. Doesn't this mean the processing stage never completed and no public keys got announced? If they were announced, how can I see them? If they weren't announced, surely you should be able to reuse the recipient account?
In this case, the shuffler for that shuffling must still have been running, as they continue to do for 720 blocks after, and this is why lurker10 got the error, because there was an active shuffler in memory with this designated recipient account. If he had stopped that shuffler by restarting the node, or using the stopShuffler API directly, it would have been possible to start another one for a different shuffling with the same recipient account.

We did not want to add an option to stop shufflers from the UI, even though such an API exists, because it would make the UI more complicated, and inevitably some users would lose money by stopping the shuffler (thinking this is a legal way to back out of participating), and then getting charged the penalty for missing their turn.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

EvilDave

  • Hero Member
  • *****
  • Karma: +341/-40
  • Offline Offline
  • Posts: 1789
    • View Profile
    • NXT Foundation
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #23 on: December 13, 2015, 01:52:59 pm »

Monetary System Shuffle !

Someone (not me) created the SHUFF MS currency......so lets use it:



I've bought a handful, and set up a shuffle for 250 SHUFF with 5 participants......


Logged
Nulli Dei, nulli Reges, solum NXT
NXT Donations: NXT-BNZB-9V8M-XRPW-3S3WD
We will ride eternal, shiny and chrome!

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #24 on: December 13, 2015, 02:28:46 pm »

When you create a shuffling, you automatically get registered for it as first participant. The joining step that you didn't do was supposed to start a shuffler, which is free. Those shufflings failed because you were not running a shuffler and did not submit processing transaction. The assignee account for a cancelled shuffling shows the account that was blamed for the shuffling failure.
Understood, I think. Would it be a UI improvement if the dialog to start the shuffler was combined with the one to create the shuffle, so that the participant pass phrase only had to be entered once? Alternatively, not create the shuffle from the first dialog until after the second dialog has been accepted. Either way, the UI can not let the user create a shuffle without starting a shuffler. I don't think anything good can come from allowing that.

Quote
In this case, the shuffler for that shuffling must still have been running, as they continue to do for 720 blocks after, and this is why lurker10 got the error, because there was an active shuffler in memory with this designated recipient account. If he had stopped that shuffler by restarting the node, or using the stopShuffler API directly, it would have been possible to start another one for a different shuffling with the same recipient account.
Thanks. So if he waits 720 blocks, his shuffler will die, and then he'll be able to use that recipient account again.
Logged

allwelder

  • Hero Member
  • *****
  • Karma: +196/-13
  • Offline Offline
  • Posts: 1867
  • NxtChina.org
    • View Profile
    • NxtChina.org
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #25 on: December 13, 2015, 02:52:16 pm »

I click join button:

Recipient Passphrase:

I typed the Passphrase of a new created account ,it displayed incorrect passphrase.

If i typed the PS of the logged in account now ,it displayed:
Incorrect recipient public key. Existing account cannot be used as shuffling recipient.

Any suggestion?
Logged
NxtChina |Weibo |Twitter Donation welcomed:NXT-APL9-66GU-K8LY-B3JJJ

PoofKnuckle

  • Hero Member
  • *****
  • Karma: +111/-7
  • Offline Offline
  • Posts: 849
  • Your Concern is Noted.
    • View Profile
    • NXT FreeMarket
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #26 on: December 13, 2015, 02:57:29 pm »

Logged
NXT: NXT-WBVP-83YM-FRB3-9MQLY
BM-NBTVHaA41Ejh2G6krD9p5vM62vk84isM

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #27 on: December 13, 2015, 03:04:07 pm »

I click join button:

Recipient Passphrase:

I typed the Passphrase of a new created account ,it displayed incorrect passphrase.

If i typed the PS of the logged in account now ,it displayed:
Incorrect recipient public key. Existing account cannot be used as shuffling recipient.

Any suggestion?

In the recipient passphrase field specify a passphrase for a newly created account into which the shuffled funds are distributed. In the passphrase field specify your account passphrase. Both fields are mandatory of course.
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

allwelder

  • Hero Member
  • *****
  • Karma: +196/-13
  • Offline Offline
  • Posts: 1867
  • NxtChina.org
    • View Profile
    • NxtChina.org
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #28 on: December 13, 2015, 03:07:25 pm »

I click join button:

Recipient Passphrase:

I typed the Passphrase of a new created account ,it displayed incorrect passphrase.

If i typed the PS of the logged in account now ,it displayed:
Incorrect recipient public key. Existing account cannot be used as shuffling recipient.

Any suggestion?

In the recipient passphrase field specify a passphrase for a newly created account into which the shuffled funds are distributed. In the passphrase field specify your account passphrase. Both fields are mandatory of course.
Thanks,seems joined. :)
Logged
NxtChina |Weibo |Twitter Donation welcomed:NXT-APL9-66GU-K8LY-B3JJJ

allwelder

  • Hero Member
  • *****
  • Karma: +196/-13
  • Offline Offline
  • Posts: 1867
  • NxtChina.org
    • View Profile
    • NxtChina.org
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #29 on: December 13, 2015, 03:10:48 pm »

The required Recipient acc must be a new created acc,right?
So What will happen if I click join a shuffler and send some coins to this new created acc at the same time?
Logged
NxtChina |Weibo |Twitter Donation welcomed:NXT-APL9-66GU-K8LY-B3JJJ

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #30 on: December 13, 2015, 03:25:31 pm »

The required Recipient acc must be a new created acc,right?
So What will happen if I click join a shuffler and send some coins to this new created acc at the same time?
The shuffling will still work, this restriction is enforced only in the beginning, when a new shuffler is started. Otherwise, anyone could sabotage a shuffling by submitting coins to one of the recipient accounts after they become known but before the verification ends.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

allwelder

  • Hero Member
  • *****
  • Karma: +196/-13
  • Offline Offline
  • Posts: 1867
  • NxtChina.org
    • View Profile
    • NxtChina.org
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #31 on: December 13, 2015, 03:46:46 pm »

Send NXT or with other type transaction:

We can set the fee=0,and the transaction will be processed.
But in fact it still cost mininum 1 NXT,not 0 .

Whereas in BTC,user can set the fee=0,and the real cost is 0.

This give some misunderstanding.

bug or not?


Logged
NxtChina |Weibo |Twitter Donation welcomed:NXT-APL9-66GU-K8LY-B3JJJ

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #32 on: December 13, 2015, 04:04:56 pm »

Just set up a mega-shuffle with 20 participants (in theory):
11532228444168389193 has completed successfully.

I joined it four times to help it along. At one point I restarted my node to see if that let me reuse accounts from cancelled shuffles, and then later I remembered and had to go round restarting all the shufflers again.
Logged

allwelder

  • Hero Member
  • *****
  • Karma: +196/-13
  • Offline Offline
  • Posts: 1867
  • NxtChina.org
    • View Profile
    • NxtChina.org
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #33 on: December 13, 2015, 04:06:38 pm »

Just set up a mega-shuffle with 20 participants (in theory):



Registration will close at 16.00 UTC today (hopefully), so four hours from now.....come and play !
Joined.
Verified. :D
Logged
NxtChina |Weibo |Twitter Donation welcomed:NXT-APL9-66GU-K8LY-B3JJJ

EvilDave

  • Hero Member
  • *****
  • Karma: +341/-40
  • Offline Offline
  • Posts: 1789
    • View Profile
    • NXT Foundation
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #34 on: December 13, 2015, 04:34:18 pm »

Thanks, guys. Lots of good shuffles happening today.....I'll set up another Asset and MS shuffle in a while.
Would be nice to see if we can get to 30 participants in one of the larger NXT shuffles, though....take a look at 'Active Shufflings' in the  NRS client.
Logged
Nulli Dei, nulli Reges, solum NXT
NXT Donations: NXT-BNZB-9V8M-XRPW-3S3WD
We will ride eternal, shiny and chrome!

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #35 on: December 13, 2015, 06:07:55 pm »

Account NXT-F2AU-FH46-MS95-2TG2L was about to fail shuffling 6909397291130772366 because its balance was 0. I sent it 15 NXT, and apparently the shuffler was running and managed to submit the processing transaction in time once it received them. However, that shuffling still failed because NXT-AMPQ-B6ZZ-S8TL-EFDBH did not submit processing.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

Espo

  • Newbie
  • *
  • Karma: +0/-0
  • Offline Offline
  • Posts: 7
    • View Profile
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #36 on: December 13, 2015, 06:15:04 pm »

I want to help the testing.
Can someone send some test NXT ti my account?

NXT-RAC7-3767-7SXL-HSRPQ

Or what is the official way to get the test NXT?
Logged

EvilDave

  • Hero Member
  • *****
  • Karma: +341/-40
  • Offline Offline
  • Posts: 1789
    • View Profile
    • NXT Foundation
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #37 on: December 13, 2015, 06:17:47 pm »

I'll send 5000 testNXT in your direction.....one second.sent.... ;D
« Last Edit: December 13, 2015, 06:20:56 pm by EvilDave »
Logged
Nulli Dei, nulli Reges, solum NXT
NXT Donations: NXT-BNZB-9V8M-XRPW-3S3WD
We will ride eternal, shiny and chrome!

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #38 on: December 13, 2015, 07:11:27 pm »

The 10 slots for the asset shuffling 4158327067862189538 filled fast, and two users NXT-ZATQ-NWCX-MBUP-3EAUG and NXT-NPZ3-DACN-E4G6-EDBVZ were left out, their transactions are now staying in the unconfirmed pool until expiration. It is working as intended.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

lopalcar

  • Hero Member
  • *****
  • Karma: +99/-15
  • Offline Offline
  • Posts: 561
    • View Profile
Re: Shuffling Sunday ! (testing NRS 1.7.2e CoinShuffle, 13-12-2015 )
« Reply #39 on: December 13, 2015, 07:23:23 pm »

The 10 slots for the asset shuffling 4158327067862189538 filled fast, and two users NXT-ZATQ-NWCX-MBUP-3EAUG and NXT-NPZ3-DACN-E4G6-EDBVZ were left out, their transactions are now staying in the unconfirmed pool until expiration. It is working as intended.

I was in 4158327067862189538, my destination was NXT-ZHNC-W7JP-FPG7-GWLYG, I sent money from another account to it before shuffling started "without announcing public key" but after registering in the shuffling and the shufling went through, is this expected to by this way?
Logged
Pages: 1 [2] 3 4 5  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly