[XMR] Monero - A secure, private, untraceable cryptocurrency

[drawingthesun]

I was thinking Mintpal would list this unique, innovative coin today. But instead they're adding another PoS clone. BC AC WC CINNI COMM XLB and now SYNC, what's the point of so many clone with different supply ?

This coin is a Bytecoin fork, aka a Bytecoin copy, nothing special about it...At least those PoS coins like Cinni don't copy Bitcoin down to the last coding like Monero has to Bytecoin..

There is something special about it, Monero has 0 days pre-mine, Bytecoin has 2 years premine.

If you don't understand why that bothers some people, read Satoshi's paper and recall his intention for creating Bitcoin.

Keyword: "Trustless."

When 80% of the entire coin supply and 99% of the current coin supply is owned by pre-miners, then you cease to be using a trustless coin because they can manipulate the price forever.

There is no free market, there is more centralised control in Bytecoin than the USD!

[cubydu]

   What happens with pools ?

[sammy007]

   What happens with pools ?

It seems some people mining with wrong addresses and payouts stuck. I just deleted stats for worker with wrong address on my http://monero.hashinvest.ws pool, because I don't wanna delay payouts for valid miners.

On my pool the wrong address was: 47shgHzm4mWfD2WM6YPAgLWvvx...

[Gambiman]

Pools have a lot of orphaned blocks don't they? like 1/4 or so.

[Sharecoin11234]

   What happens with pools ?

where did u get this screenshot?

[sammy007]

Pools have a lot of orphaned blocks don't they? like 1/4 or so.

Yes, that's sucks, because a lot of hashrate is consealed somewhere... it seems huge farms mining solo or on their own private pools.

[Gambiman]

Pools have a lot of orphaned blocks don't they? like 1/4 or so.

Yes, that's sucks, because a lot of hashrate is consealed somewhere... it seems huge farms mining solo or on their own private pools.

:/ sucks indeed.

[smooth]

Pools have a lot of orphaned blocks don't they? like 1/4 or so.

Whether using pools or not, this coin has a lot of orphaned blocks. When the original fork was done, several of us advised against 60 second blocks, but the warnings were not heeded.

I'm hopeful we can eventually make a change to more sane 2- or 2.5-minute blocks which should drastically reduce orphans, but that will require a hard fork, so not that easy.

[cubydu]

   What happens with pools ?

where did u get this screenshot?

http://moneropool.com/

[smooth]

Pools have a lot of orphaned blocks don't they? like 1/4 or so.

Yes, that's sucks, because a lot of hashrate is consealed somewhere... it seems huge farms mining solo or on their own private pools.

I can tell you are a lot of people mining solo, I'm one of them, and I have a significant number of high performance computers. I do this not only in part because the returns are better mining solo (since the pools and pool miners are not quite fully there yet) but also to help keep the coin decentralized. The more solo miners there are, the harder it is for any of the pools to become too dominant. If we are lucky there will continue to be a lot of solo miners, although other coins have struggled with this.

This has little if anything to do with orphans though. As I explained in my other post, a high rate of orphans comes with 60 second blocks. That is just too fast.

[sammy007]

Pools have a lot of orphaned blocks don't they? like 1/4 or so.

Yes, that's sucks, because a lot of hashrate is consealed somewhere... it seems huge farms mining solo or on their own private pools.

I can tell you are a lot of people mining solo, I'm one of them, and I have a significant number of high performance computers. I do this not only in part because the returns are better mining solo (since the pools and pool miners are not quite fully there yet) but also to help keep the coin decentralized. The more solo miners there are, the harder it is for any of the pools to become too dominant. If we are lucky there will continue to be a lot of solo miners, although other coins have struggled with this.

This has little if anything to do with orphans though. As I explained in my other post, a high rate of orphans comes with 60 second blocks. That is just too fast.

Yeah, solo is awesome, I am mining Vertcoin solo with small rigs and getting good reward. Also, I am running private pool for some dude, he wanna mine solo, so it's just like solo for him.

[aminorex]

I suggest conducting a poll regarding block times.  60 seconds is just batshit crazy, in my opinion.  My suggestion is to make block times a function of the number of transactions per block over the past N blocks, with a hard maximum to insure minimum emission rate and continuous mining.  BTC hasn't exactly suffered for its 10 minute confirms, so I would suggest a 10 minute maximum.  This would also encourage miners to use their monero, and accept payment in monero, since transactions increase the number of blocks per unit of time.  (If there is too much churn that can be dealt with in other, better, ways.)

I think botnets are the source of greatest existential danger.

[equipoise]

My new optimizations have been ported to Windows by Lucasjones and committed to the Git repo. If you want Win64 binaries, my thread on it is here:

https://bitcointalk.org/index.php?topic=619373

Crashes on my core i7 3rd gen Win 7 64x SP1. It was the same with the previous version. Compiled in Linux (VirtualBox with Ubuntu) it works, but have slower hash rate then bitmonerod.exe. I'm still solo mining.

[phzi]

Beware, moneropool.org is not paying... They claim they are held back due to a bug - but this "bug" has been explained above, is trivial to resolve (delete invalid addresses), and they haven't done anything about the situation.

I would stay away until we know more.

[smooth]

I suggest conducting a poll regarding block times.  60 seconds is just batshit crazy, in my opinion.  My suggestion is to make block times a function of the number of transactions per block over the past N blocks, with a hard maximum to insure minimum emission rate and continuous mining.

This won't work in the obvious way since there is already a dynamic scaling mechanism in cryptonote for block size (and therefore transactions per block). It is probably possible to create a stable scaling mechanism that uses both dependent variables, but how to do this is not really obvious. The choice of ideal block interval is not entirely a function of transaction volume, it is also a function of latency and propagation.

In the short term the easy and relatively uncontroversial fix is to go to something 2 or 2.5 minutes. Pretty much everyone who has actually studied the problem has concluded something in that range is the smallest interval that works well today, and indeed that Satoshi's choice of 10 minute was not excessive. Including, I suspect crytponote/bytecoin, when they picked 2 minutes.

Any hard fork is effectively a poll of miners anyway, since it won't be adopted if the majority of hash power doesn't adopt it.

[sammy007]

Beware, moneropool.org is not paying... They claim they are held back due to a bug - but this "bug" has been explained above, is trivial to resolve (delete invalid addresses), and they haven't done anything about the situation.

I would stay away until we know more.

Pool ops have to file a bugreport to pool software dev, because it's possible to attack pools with such invalid addresses and delay payments.

https://github.com/zone117x/node-cryptonote-pool

[surfer43]

Beware, moneropool.org is not paying... They claim they are held back due to a bug - but this "bug" has been explained above, is trivial to resolve (delete invalid addresses), and they haven't done anything about the situation.

I would stay away until we know more.

The bug is that someone mined with the invalid address while I was asleep, and the payment queue got too large. Now the daemon rejects the transaction because it is too large. I have already removed the shares of the invalid address in Redis.

I have paid out all along, even for many orphans. I'm not going to start stealing your MRO.

[sammy007]

Beware, moneropool.org is not paying... They claim they are held back due to a bug - but this "bug" has been explained above, is trivial to resolve (delete invalid addresses), and they haven't done anything about the situation.

I would stay away until we know more.

The bug is that someone mined with the invalid address while I was asleep, and the payment queue got too large. Now the daemon rejects the transaction, because it is too large.

I have paid out all along, even for many orphans. I'm not going to start stealing your MRO.

Could you please post a solution ITT how to fix this? I also running a pool and just got lucky, noticed this address early and deleted it. Have no idea how to handle your case.

[Jasmin68k]

hello



yesterday i started my adventure on monero... all fine i guess... i installed the simplewallet simple miner and bitmonerod.
runned bitmonerod thensimple walled and generated new wallet. then on simple miner i putted to mine to this pool
http://monerominers.com/pool/

as it offered a 100 monero bounty among the first miner to discover the block. we were 12 and we discovered the block after a while....

but my balance is still to 0 ... ( more block were discovered in the night but my balance still 0 in the wallet i mean) is there a minimal threshold payout ? im testing not at around 40- 170 h/s  i have quite many xeon machines to put on this if the pools reveals not a scam pool ... i just need more infos how to check my stats , my pending moneros and so ... this is my address

497viAVVKPC7vd5aA1m384eQbdAkWDMykaFdnDmYi3n1CNDZ93aSW7ZLxvGuGvizXsBXUVx5ntT2SSx TV47iYUWi5P1hUjG

please waiting for infos.

Payments will be carried out tonight!

I am in the same position as cptfisher.

Pointed some hashpower towards this pool the evening this 100 MRO bounty was announced.

Participated in finding the first (bounty) block and four blocks after and have yet to receive any of the bounty share or regular pool payout.

Despite Spollie's above announcement or the pool page saying that payments are live.

The MRO address used is this one:

43AoQ2heavdXk4Qoqv2CvPdktETqqqpqTJFEegnxNAph49h2gA3S33DCQ7i81W3aG9XENEdYfWUhP4V qvFN3U8LDBb8smHN

Have PM'ed Spollie earlier already.

Had just gotten into mining this coin on other pools for a day or so, where everything went smoothly.

Then switched to monerominers.com after that 100 MRO bounty was announced.

Seen it as a nice opportunity to make some extra MRO and support a small pool in the process while difficulty was still much lower.

Would be sad to have wasted my hashes on this pool...

Maybe just a glitch in the still new pool software?

Would be glad, if the admin could sort things out. Thanks in advance!

@cptfisher: Did you receive your payment yet?

Update: Pool site is now down, so far no payment or reply to PM (despite user's profile showing activity here in the meantime). eMail to support address support@monerominers.com could not be delivered earlier today (rejected).

[BitKoot]

Anyone with an idea, I'm having problems with the .net gui

It seems like it gets stuck with just a few blocks remaining,
plus the address is always initializing.

I have published a new version of the wallet which will hopefully fix the problem (couldn't reproduce it on my machine, but I have a hunch where the problem was). Download: https://dl.dropboxusercontent.com/u/6522303/CryptoNoteWallet_latest.zip

And please, post feedback about the GUI in the GUI bounty thread. I probably miss posts about the GUI in this thread because it grows to fast