[ANN][RVC] / RevoCoin / POS - POW / 10,000kh miner limit / LAUNCH 22-07

[ocminer]

Ocminer, in the "getting started" menu - you've written nist5 algo, I think it should be bitblock ...

The pool is not ready yet, I'm just testing lots of stuff there, i'll redo everything when I'm ready, don't worry

thx for your headsup though

[go6ooo1212]

NP , You now I admire your work

[opossum]

Launch is today or next week?

[ddfd1]

 Launch time

[SecondsOld]

Let's get this party started!

[Bojcha]

From other forum..

Stop talking about revocoin here this coin is already doomed as there is one wallet already holding 3.5M coin which is around 40% of the total supply.

Is this true?

[SecondsOld]

From other forum..

Stop talking about revocoin here this coin is already doomed as there is one wallet already holding 3.5M coin which is around 40% of the total supply.

Is this true?

Sounds like FUD to me.  First off, they are probably talking about the IPO wallet.  Secondly, that is nowhere near 40% of the total coins.  Nice try though.

[antonio8]

Ocminer, in the "getting started" menu - you've written nist5 algo, I think it should be bitblock ...

The pool is not ready yet, I'm just testing lots of stuff there, i'll redo everything when I'm ready, don't worry

thx for your headsup though

If you have the exact url and port ready can you post it so I can have my .bat ready when this goes live?

With my luck I will be at work and miss the first 9 hours of mining.

[Bojcha]

Any good x15 miner?

[Amph]

Any good x15 miner?

for amd or nvidia? for nvidia check official cudaminer thread

[yellowduck2]

Any good x15 miner?

for amd or nvidia? for nvidia check official cudaminer thread

He might be asking for miner to rent.

[Bojcha]

No..
Miner for AMD.
Tried sgminer5 but it's just crap. I have different cards in rigs and not possible to have separate kernels for differnt cards.
So i need some normal sgminer with bitblock/bitblockold.

[shwin]

No..
Miner for AMD.
Tried sgminer5 but it's just crap. I have different cards in rigs and not possible to have separate kernels for differnt cards.
So i need some normal sgminer with bitblock/bitblockold.

start 2 instance of sgminer with device setting for different kernel

[Bojcha]

No..
Miner for AMD.
Tried sgminer5 but it's just crap. I have different cards in rigs and not possible to have separate kernels for differnt cards.
So i need some normal sgminer with bitblock/bitblockold.

start 2 instance of sgminer with device setting for different kernel

Yes that works. But will be possible to mine on One worker at pool?
Quickly tried with maia-coin and there was some problems with 2 miners on one worker.

[rvccoin]

IPO closed. All Participant will soon receive a final confirmation.

A little patience will reward you.

From other forum..

Stop talking about revocoin here this coin is already doomed as there is one wallet already holding 3.5M coin which is around 40% of the total supply.

Is this true?

Not a bit of it.

Hey Dev, the entire  Cryptoworld waiting around the start of this coin! Time to rock and roll!

Sorry, pools are not yet (but almost) ready.

[ocminer]

Ok so i've been mining with resolution 3 for a few hours now (other X15 coin) and there is one big problem:

If lets say 10 miner push 10 MH/s we will find a block every 2 minutes .. which is okay.

If 10 miners push 10 MH/s but ONE miner pushes falsely 100 MH/s (and only gets 10 credited), "the rest" of 90 MH/s are still "processed" by the daemon thus we will find block much faster than before.

So I've got find a way to really discard that rest of 90 MH/s and don't let it come to the daemon.. Which is my problem right now..

I'll probably have to do a mixed thing between 1 & 3 and/or 2 & 3... So if a miner pushes 100 MH/s and does not go back to 10 MH/s within a reasonable time, to protect the network, he will be banned or all his shares will be rejected by the daemon.

As soon as this is fixed, we can start.. I'm testing both ways currently, lets see which one actually works.

[SecondsOld]

Ok so i've been mining with resolution 3 for a few hours now (other X15 coin) and there is one big problem:

If lets say 10 miner push 10 MH/s we will find a block every 2 minutes .. which is okay.

If 10 miners push 10 MH/s but ONE miner pushes falsely 100 MH/s (and only gets 10 credited), "the rest" of 90 MH/s are still "processed" by the daemon thus we will find block much faster than before.

So I've got find a way to really discard that rest of 90 MH/s and don't let it come to the daemon.. Which is my problem right now..

I'll probably have to do a mixed thing between 1 & 3 and/or 2 & 3... So if a miner pushes 100 MH/s and does not go back to 10 MH/s within a reasonable time, to protect the network, he will be banned or all his shares will be rejected by the daemon.

As soon as this is fixed, we can start.. I'm testing both ways currently, lets see which one actually works.

Way to go ocminer, you're the man!

[MinermanNC]

Are we getting closer to a launch? ok, was just checking back in 

[bathrobehero]

Ok so i've been mining with resolution 3 for a few hours now (other X15 coin) and there is one big problem:

If lets say 10 miner push 10 MH/s we will find a block every 2 minutes .. which is okay.

If 10 miners push 10 MH/s but ONE miner pushes falsely 100 MH/s (and only gets 10 credited), "the rest" of 90 MH/s are still "processed" by the daemon thus we will find block much faster than before.

So I've got find a way to really discard that rest of 90 MH/s and don't let it come to the daemon.. Which is my problem right now..

I'll probably have to do a mixed thing between 1 & 3 and/or 2 & 3... So if a miner pushes 100 MH/s and does not go back to 10 MH/s within a reasonable time, to protect the network, he will be banned or all his shares will be rejected by the daemon.

As soon as this is fixed, we can start.. I'm testing both ways currently, lets see which one actually works.

You can't expect us to limit ourselves close to the 10 mh/s line, especially with fluctuations. I mean we really don't want to be banned for whatever amount for 10.1 mh/s and we don't want to mine at 7 mh/s just to be safe either.
Maybe you could set a fixed difficulty and only accept a calculated number of shares per minute or whatever preferably smaller intervals. If somene submits more shares have vardiff kick them until the end of that period where vardiff resets or just redirect the surplus shares to another x15 coin.

[yellowduck2]

Ok so i've been mining with resolution 3 for a few hours now (other X15 coin) and there is one big problem:

If lets say 10 miner push 10 MH/s we will find a block every 2 minutes .. which is okay.

If 10 miners push 10 MH/s but ONE miner pushes falsely 100 MH/s (and only gets 10 credited), "the rest" of 90 MH/s are still "processed" by the daemon thus we will find block much faster than before.

So I've got find a way to really discard that rest of 90 MH/s and don't let it come to the daemon.. Which is my problem right now..

I'll probably have to do a mixed thing between 1 & 3 and/or 2 & 3... So if a miner pushes 100 MH/s and does not go back to 10 MH/s within a reasonable time, to protect the network, he will be banned or all his shares will be rejected by the daemon.

As soon as this is fixed, we can start.. I'm testing both ways currently, lets see which one actually works.

If someone spike 10gh and find 10 blocks in 1 min , what happen to the block he found ?

Or maybe u can find out how mineral coin did this hash limit on pool.