Bitcoin Forum
June 21, 2024, 06:20:32 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency - 0.8.8.6 on: April 04, 2015, 07:34:19 PM
chainradar seems to be doing more of an educated guess, it kinda gets it right. so let's figure out why and how to avoid it

If the ring signature involves n outputs, then you can guess with 1/n probability -- no fancy analysis needed. Try your tests with higher mixin and see how often it gets it right. Over enough tests it should converge to 1/n. Basically, chainradar is just bullshitting but it looks like it succeeds occasionally because its random guess lands on the right one. Dart-throwing monkeys can pull off the very same.

first 2 tx were 150 and 70 mixin. didn't help
the others I tried to make identical ones at the same time.
but should have made the following txes in reverse order. I'll try that later. If that doesn't work, I'm out of ideas

Posting guesses and suppositions on this thread 10 times in a row is counter-productive. Go read MRL-0004, and you'll see how we've addressed this.

Hey! You don't have a "Warning: Read MRL-0004" anywhere. How was I to know? that's why I asked. It's good that chainradar exposed it then.
I erased my other posts. It's obvious that MRL-0004 is the issue. Minimum mix in requirements is the solution. So, I hope you will make that hardfork soon.

If I can make a suggestion: You could make it minimum 5 mix ins, not just 1, to avoid any further problems. And make it 10 by default. And don't allow dust amounts. Privacy is the main feature of monero, it can't be overlooked.

If I recall correctly, mixing will be at minimum 3. I think he said it, because he already stated that you should read MRL-0004, you shouldn't feel attacked though :-)

I'm not. What I've meant is before I started this, I had no way of knowing about MRL-0004. You should put it on the OP. I think it's very important to know this.
Ok, didn't go through the full document, if 3 is the way, I assume you did the math, 1 just didn't seem good.

My suggestion will be then just:  default 10 mixins, and no dust allowed.

Hope that we'll see it fixed soon. And thanks for explaining this to me, and for your patience!
2  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency - 0.8.8.6 on: April 04, 2015, 07:20:36 PM
chainradar seems to be doing more of an educated guess, it kinda gets it right. so let's figure out why and how to avoid it

If the ring signature involves n outputs, then you can guess with 1/n probability -- no fancy analysis needed. Try your tests with higher mixin and see how often it gets it right. Over enough tests it should converge to 1/n. Basically, chainradar is just bullshitting but it looks like it succeeds occasionally because its random guess lands on the right one. Dart-throwing monkeys can pull off the very same.

first 2 tx were 150 and 70 mixin. didn't help
the others I tried to make identical ones at the same time.
but should have made the following txes in reverse order. I'll try that later. If that doesn't work, I'm out of ideas

Posting guesses and suppositions on this thread 10 times in a row is counter-productive. Go read MRL-0004, and you'll see how we've addressed this.

Hey! You don't have a "Warning: Read MRL-0004" anywhere. How was I to know? that's why I asked. It's good that chainradar exposed it then.
I erased my other posts. It's obvious that MRL-0004 is the issue. Minimum mix in requirements is the solution. So, I hope you will make that hardfork soon.

If I can make a suggestion: You could make it minimum 5 mix ins, not just 1, to avoid any further problems. And make it 10 by default. And don't allow dust amounts. Privacy is the main feature of monero, it can't be overlooked.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!