ArticMine
Legendary
Offline
Activity: 2282
Merit: 1050
Monero Core Team
|
|
October 04, 2015, 02:49:32 AM |
|
We need a tie breaking mechanism. For example one can look at the result before the vote that led to the tie and use that instead.
We are now a few hours past UTC and the vote is still tied. If everyone could agree on a proposal like this we can proceed. Or another voter can break the tie. Anyone can calculate the result the above proposal would lead to for this move. Please try to decide on whether the tiebreak proposal one ArticMine is appropriate or not without taking into account the 4th move it would lead to in this game. I think in this particular instance since the situation of the tie occurred before a rule was proposed, a more fair method to resolve this tie is with a randomizer (for example last bit of a future Bitcoin block hash). Adopting the proposed rule going forward would be fine though. Yes. This makes sense to me.
|
|
|
|
boolberry (OP)
|
|
October 04, 2015, 02:50:26 AM Last edit: October 04, 2015, 03:05:23 AM by boolberry |
|
We need a tie breaking mechanism. For example one can look at the result before the vote that led to the tie and use that instead.
We are now a few hours past UTC and the vote is still tied. If everyone could agree on a proposal like this we can proceed. Or another voter can break the tie. Anyone can calculate the result the above proposal would lead to for this move. Please try to decide on whether the tiebreak proposal by ArticMine is appropriate or not without taking into account the 4th move it would lead to in this game. I think in this particular instance since the situation of the tie occurred before a rule was proposed, a more fair method to resolve this tie is with a randomizer (for example last bit of a future Bitcoin block hash). Adopting the proposed rule going forward would be fine though. I like your idea to avoid making any rule changes retroactive. Should we set a time now for the last bit of a future hash to decide things? Or should we just wait a little longer? I can't remember any ties delaying things for long in the other bitcointalk chess thread: https://bitcointalk.org/index.php?topic=1148538.0How about making the move Qxd4 if the last number in the first bitcoin hash after 12:00 UTC is even and Nxd4 if the last number in the first bitcoin hash after 12:00 UTC is odd? Any vote before 12:00 UTC would still break the tie. Is that fair?
|
|
|
|
onemorexmr
|
|
October 04, 2015, 02:51:57 AM |
|
I vote 4.Qxd4 in the spirit of the World Cup
i also vote Qxd4 to end this stall and following World Cup sounds good to me
|
|
|
|
boolberry (OP)
|
|
October 04, 2015, 03:04:42 AM |
|
I vote 4.Qxd4 in the spirit of the World Cup
i also vote Qxd4 to end this stall and following World Cup sounds good to me Team Monero (white pieces) vs. Team Boolberry (black pieces)black to move 1.e4 c5 2.Nf3 d6 3.d4 cxd4 4.Qxd4 Based on the votes in this thread Team Monero has chosen to play Qxd4 (4 votes) beating Nxd4 (3 votes) in close decision Now it is time for Team Boolberry to respond. Votes will be counted at 0:00 UTC tomorrow.
|
|
|
|
boolberry (OP)
|
|
October 04, 2015, 03:19:14 AM Last edit: October 04, 2015, 03:31:15 AM by boolberry |
|
I vote that we play a6. Team Monero will have to move their queen again after we attack it with Nc6 because Bb5 pinning our knight will no longer be possible.
If team Monero can play like Svidler we can play like Karjakin who just happened to win with black in this opening!
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
October 04, 2015, 05:05:47 AM |
|
I like your idea to avoid making any rule changes retroactive. Should we set a time now for the last bit of a future hash to decide things?
Are we all agreed now that future ties will use ArticMine's proposed tie-breaker rule?
|
|
|
|
XMRpromotions
|
|
October 04, 2015, 05:31:30 AM |
|
I like your idea to avoid making any rule changes retroactive. Should we set a time now for the last bit of a future hash to decide things?
Are we all agreed now that future ties will use ArticMine's proposed tie-breaker rule? Okay with me! Boolberry should update OP to make note of it.
|
|
|
|
newb4now
|
|
October 04, 2015, 07:14:47 AM |
|
Nc6
|
|
|
|
|
boolberry (OP)
|
|
October 04, 2015, 08:46:17 PM |
|
We need a tie breaking mechanism. For example one can look at the result before the vote that led to the tie and use that instead.
OP has been updated with your good suggestion. Current vote count is 2-1 in favor of a6 over Nc6. Votes will be counted at 0:00 UTC
|
|
|
|
boolberry (OP)
|
|
October 05, 2015, 07:01:17 AM |
|
Current positionBased on the votes in this thread Team Boolberry has chosen to play a6. Now it is time for Team Monero to respond. Since I was late posting the updated position, Team Monero may have another day (until 0:00 UTC on 10/7/15) to respond if needed. Team Monero (white pieces) vs. Team Boolberry (black pieces)white to move 1.e4 c5 2.Nf3 d6 3.d4 cxd4 4.Qxd4 a6 In the future if I am absent for long, anyone else should feel free to post a picture of the updated board after counting votes if they wish. My goal is to do so around 0:00 UTC daily, but today proves I may not always be on time.
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
October 05, 2015, 07:24:33 AM |
|
Now we have a choice of playing c4 to continue the exact line from the world cup game or we could do something else, like move the queen back, which we will very likely have to do in a move or two anyway (no way to stop Nc6)
I vote c4 mostly because I'm curious to see what team BBR does with that, but I may change my vote if other good moves are proposed.
|
|
|
|
LucyLovesCrypto
|
|
October 05, 2015, 10:39:05 AM |
|
Now we have a choice of playing c4 to continue the exact line from the world cup game or we could do something else, like move the queen back, which we will very likely have to do in a move or two anyway (no way to stop Nc6)
I vote c4 mostly because I'm curious to see what team BBR does with that, but I may change my vote if other good moves are proposed.
I like c4
|
|
|
|
|
XMRpromotions
|
|
October 05, 2015, 02:12:33 PM |
|
Now we have a choice of playing c4 to continue the exact line from the world cup game or we could do something else, like move the queen back, which we will very likely have to do in a move or two anyway (no way to stop Nc6)
I vote c4 mostly because I'm curious to see what team BBR does with that, but I may change my vote if other good moves are proposed.
I will make the 3rd vote for c4. We will have to make a new move at some point because black ended up with a good position in the World Cup game. I have an idea about when we can do something different, but I don't want to disclose that yet.
|
|
|
|
ArticMine
Legendary
Offline
Activity: 2282
Merit: 1050
Monero Core Team
|
|
October 05, 2015, 08:40:12 PM |
|
I am voting c4.
|
|
|
|
dEBRUYNE
Legendary
Offline
Activity: 2268
Merit: 1141
|
|
October 05, 2015, 08:43:50 PM |
|
Crosspost because relevant. I'll not clutter the chess game any further :-P MoneroMooo has been working on it in his own branch, but since it is not merged yet it probably isn't finished. See -> https://github.com/moneromooo-monero/bitmonero/commits/cold and in particular this commit: https://github.com/moneromooo-monero/bitmonero/commit/3c44e9fb6c1b57852d37780414ed6e42afc19afbThis change adds the ability to create a new unsigned transaction from a watch only wallet, and save it to a file. This file can then be moved to another computer/VM where a cold wallet may load it, sign it, and save it. That cold wallet does not need to have a blockchain nor daemon. The signed transaction file can then be moved back to the watch only wallet, which can load it and send it to the daemon.
Two new simplewallet commands to use it: sign_transfer (on the cold wallet) submit_transfer (on the watch only wallet)
The transfer command used on a watch only wallet now writes an unsigned transaction set in a file called 'unsigned_monero_tx' instead of submitting the tx to the daemon as a normal wallet does. The signed tx file is called 'signed_monero_tx'. It worked, though I'm not sure it still applies, though any conflicts should not be hard to solve, if there are any. What needs doing there is reducing the size of the exchange files, as they're a complete set of transactions plus relevant data, which means the whole deserilization code on the cold wallet is an attack surface. Cutting the size down will apparently make it easier to transfer via QR code scanning, avoiding attacks via filesystems and removable media firmware. But it works
|
|
|
|
languagehasmeaning
|
|
October 05, 2015, 09:42:57 PM |
|
Crosspost because relevant. I'll not clutter the chess game any further :-P
This change adds the ability to create a new unsigned transaction from a watch only wallet, and save it to a file. This file can then be moved to another computer/VM where a cold wallet may load it, sign it, and save it. That cold wallet does not need to have a blockchain nor daemon. The signed transaction file can then be moved back to the watch only wallet, which can load it and send it to the daemon.
Two new simplewallet commands to use it: sign_transfer (on the cold wallet) submit_transfer (on the watch only wallet)
The transfer command used on a watch only wallet now writes an unsigned transaction set in a file called 'unsigned_monero_tx' instead of submitting the tx to the daemon as a normal wallet does. The signed tx file is called 'signed_monero_tx'. Definitely relevant and good news.
|
|
|
|
boolberry (OP)
|
|
October 05, 2015, 11:37:52 PM |
|
Based on the votes in this thread Team Monero has chosen to play c4. Now it is time for Team Boolberry to respond. I will plan to count votes again tomorrow at approximately 0:00 UTC. Team Monero (white pieces) vs. Team Boolberry (black pieces)black to move 1.e4 c5 2.Nf3 d6 3.d4 cxd4 4.Qxd4 a6 5.c4
|
|
|
|
newb4now
|
|
October 06, 2015, 09:36:06 AM |
|
Nf6 please. Lets keep developing our pieces.
|
|
|
|
|