[ANN] [KRB] Karbo (Ҝ) Кapбoвaнeць - Ukrainian Electronic Karbovanets CryptoNote

[aiwe]

Happy new year everyone! Democats pool is back online:
http://democats.org/pool/?name=karbowanec

Great news! The best New Year Gift!

Thank you for your work and supporting Karbo! It was really non trivial task to add support of our changes, we appreciate that.

It looks like there are still some problems. The daemon crushed after a block was found. Back offline, I hope I will bring it back up today

It still shows a little different difficulty though it block was accepted by the network

[MWD64]

Happy new year everyone! Democats pool is back online:
http://democats.org/pool/?name=karbowanec

Great news! The best New Year Gift!

Thank you for your work and supporting Karbo! It was really non trivial task to add support of our changes, we appreciate that.

It looks like there are still some problems. The daemon crushed after a block was found. Back offline, I hope I will bring it back up today

It still shows a little different difficulty though it block was accepted by the network

When a pool is starting back up it takes a while for the difficulty to show what other pools are showing. Is that possibly what you're seeing?

[karman383]

Is there anyone here tell me, where can I rent rigs to mine Karbowanec.
Thanks!

[hugabase]

goo KRB..!!!!

[aiwe]

Happy new year everyone! Democats pool is back online:
http://democats.org/pool/?name=karbowanec

Great news! The best New Year Gift!

Thank you for your work and supporting Karbo! It was really non trivial task to add support of our changes, we appreciate that.

It looks like there are still some problems. The daemon crushed after a block was found. Back offline, I hope I will bring it back up today

It still shows a little different difficulty though it block was accepted by the network

When a pool is starting back up it takes a while for the difficulty to show what other pools are showing. Is that possibly what you're seeing?

No, I believe it is still some difference in diff formula.

Is there anyone here tell me, where can I rent rigs to mine Karbowanec.
Thanks!

At Nicehash but limit to low hashrate for longer period of time, big hashrate won't give you advantage for longer than few minutes.

[aiwe]

goo KRB..!!!!

It is goin, have you seen vol at Cryptopia?

[karman383]

Happy new year everyone! Democats pool is back online:
http://democats.org/pool/?name=karbowanec

Great news! The best New Year Gift!

Thank you for your work and supporting Karbo! It was really non trivial task to add support of our changes, we appreciate that.

It looks like there are still some problems. The daemon crushed after a block was found. Back offline, I hope I will bring it back up today

It still shows a little different difficulty though it block was accepted by the network

When a pool is starting back up it takes a while for the difficulty to show what other pools are showing. Is that possibly what you're seeing?

No, I believe it is still some difference in diff formula.

Is there anyone here tell me, where can I rent rigs to mine Karbowanec.
Thanks!

At Nicehash but limit to low hashrate for longer period of time, big hashrate won't give you advantage for longer than few minutes.

Yeah it seems difficult for the benefit of mine, I want mining with own GPU, but here is constrained electricity.
So...Thanks for your advice

[MWD64]

Happy new year everyone! Democats pool is back online:
http://democats.org/pool/?name=karbowanec

Great news! The best New Year Gift!

Thank you for your work and supporting Karbo! It was really non trivial task to add support of our changes, we appreciate that.

It looks like there are still some problems. The daemon crushed after a block was found. Back offline, I hope I will bring it back up today

It still shows a little different difficulty though it block was accepted by the network

When a pool is starting back up it takes a while for the difficulty to show what other pools are showing. Is that possibly what you're seeing?

No, I believe it is still some difference in diff formula.

You sure? It seems to be catching up. compare this:
http://democats.org/pool/?name=karbowanec

to this:
http://krb.cryptonotepool.com/
(I assume correct)

I could be wrong, but I think it's still catching up. It's closer now than it was when I posted before.  Though it's hard to tell. Seems like a bunch of hash is coming on the Karbo network right now.

[slb]

Attempt N2. Help us find a few blocks to see is it all fine. Don't commit big hashrate please or you risk to loose your money:
http://democats.org/pool/?name=karbowanec

[aiwe]

Attempt N2. Help us find a few blocks to see is it all fine. Don't commit big hashrate please or you risk to loose your money:
http://democats.org/pool/?name=karbowanec

Judging from the correct difficulty at the pool and in block explorer in block 63876 found by pool it should be now fine.

Amazing work!

[JerryWinski]

Is there anyone here tell me, where can I rent rigs to mine Karbowanec.
Thanks!

nicehash has it. Its called cryptonote or cryptonight.

[aiwe]

BTW FYI Claymore's CryptoNight GPU Miner v9.7 is out. Now it is possible to mine Karbo with flag -allpools 1  

Code:

NsGpuCNMiner.exe -dbg -1 -allpools 1 -o stratum+tcp://pool.karbowanec.com:5555 -u YOUR_WALLET_ADDRESS -p -x

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

[aiwe]

The result and the reason of the hardfork:



Thanks Democats we have stats with nice charts.

[MWD64]

The result and the reason of the hardfork:



Thanks Democats we have stats with nice charts.

Can you explain this a little more please?

Did Karbo have a blockchain fork before or after the mandatory software update?

Or are you saying that the mandatory software update was needed because the block times on Karbo got so long sometimes?

And did the block times get long because of the high hash attacks?

Is Karbo responding better now to those attacks?

thank you!
MWD

[aiwe]

The result and the reason of the hardfork:



Thanks Democats we have stats with nice charts.

Can you explain this a little more please?

Did Karbo have a blockchain fork before or after the mandatory software update?

For hardfork software update was necessary, so first was mandatory update then hardfork.

Or are you saying that the mandatory software update was needed because the block times on Karbo got so long sometimes?

It was the reason. Updated software allowed us to conduce hardfork to block version 2 with new difficulty algorithm.

And did the block times get long because of the high hash attacks?

Exactly. The default Cryptonote difficulty algorithm with our realtively low average hashrate was abused starting the end of October by invasions of Nicehash miners who threw in relatively huge hashrate and mined ~300 easy blocks  before lagging difficulty wast starting to rise, and when difficulty was at last climbing high they were going away leaving the rest of the miners and network with big gaps between blocks causing delays in transactions confirmations. What we did in the hardfork -  changed difficulty calculation algorithm, now difficulty reacts much more quickly making impossible for Nicehash miners to mine easy blocks. It is because before hardfork difficulty was calculated based on window of around 300 blocks, i.e. Nicehash miner renting some 1Mh for an hour could easily mine 300 blocks at low difficulty before difficulty was starting to rise, now after the fork the window is much more smaller, 17 blocks and without lag so difficulty starts react to massive hashrate almost immediately. It wouldn't be the problem if they continue to mine, but after ther rizing of difficulty those Nicehash miners were leaving and the hashrate of the rest of the miners was too small for that difficulty therefore there were big intervals between blocks. This was unacceptable because confirmation time of transactions was too big, we had to wait for few hours for confirmations. The delays after the sudden drop of the hashrate was the reason of the hardfork.

Is Karbo responding better now to those attacks?

thank you!
MWD

As you can see on chart after December 22 when hardfork occured Niecehash attacks ceased, chart is now straing and we have stable ~240 seconds average block time. They were trying, but literally after few blocks (around 5-10) difficulty starts to rise very quickly making Nicechash mining with comparatively massive hashrate unprofitable.

[MWD64]

The result and the reason of the hardfork:



Thanks Democats we have stats with nice charts.

Can you explain this a little more please?

Did Karbo have a blockchain fork before or after the mandatory software update?

For hardfork software update was necessary, so first was mandatory update then hardfork.

Or are you saying that the mandatory software update was needed because the block times on Karbo got so long sometimes?

It was the reason. Updated software allowed us to conduce hardfork to block version 2 with new difficulty algorithm.

And did the block times get long because of the high hash attacks?

Exactly. The default Cryptonote difficulty algorithm with our realtively low average hashrate was abused starting the end of October by invasions of Nicehash miners who threw in relatively huge hashrate and mined ~300 easy blocks  before lagging difficulty wast starting to rise, and when difficulty was at last climbing high they were going away leaving the rest of the miners and network with big gaps between blocks causing delays in transactions confirmations. What we did in the hardfork -  changed difficulty calculation algorithm, now difficulty reacts much more quickly making impossible for Nicehash miners to mine easy blocks. It is because before hardfork difficulty was calculated based on window of around 300 blocks, i.e. Nicehash miner renting some 1Mh for an hour could easily mine 300 blocks at low difficulty before difficulty was starting to rise, now after the fork the window is much more smaller, 17 blocks and without lag so difficulty starts react to massive hashrate almost immediately. It wouldn't be the problem if they continue to mine, but after ther rizing of difficulty those Nicehash miners were leaving and the hashrate of the rest of the miners was too small for that difficulty therefore there were big intervals between blocks. This was unacceptable because confirmation time of transactions was too big, we had to wait for few hours for confirmations. The delays after the sudden drop of the hashrate was the reason of the hardfork.

Is Karbo responding better now to those attacks?

thank you!
MWD

As you can see on chart after December 22 when hardfork occured Niecehash attacks ceased, chart is now straing and we have stable ~240 seconds average block time. They were trying, but literally after few blocks (around 5-10) difficulty starts to rise very quickly making Nicechash mining with comparatively massive hashrate unprofitable.

Thank you!

So is this something that all CryptoNote coins should probably do?

[aiwe]

....
Thank you!

So is this something that all CryptoNote coins should probably do?

Not necessarily. For the coins with average hashrate about 1Mh this type of attack will not be so noticeable. Another way to resolve this problem is to stick to the bigger CN coin via merged mining like XDN or FCN merged mined with XMR.  For small coins, they have to do their research and decide.

[MWD64]

....
Thank you!

So is this something that all CryptoNote coins should probably do?

Not necessarily. For the coins with average hashrate about 1Mh this type of attack will not be so noticeable. Another way to resolve this problem is to stick to the bigger CN coin via merged mining like XDN or FCN merged mined with XMR.  For small coins, they have to do their research and decide.

Thank you.

so have the huge hash attempts stopped on your coin after the hard fork? Because my theory was that since this seems to happen on all new CryptoNote coins, and they use way more hash power than they'd probably need to get all the blocks for a while, that it wasn't someone mining for profit, but rather an attack.

[aiwe]

....
Thank you!

So is this something that all CryptoNote coins should probably do?

Not necessarily. For the coins with average hashrate about 1Mh this type of attack will not be so noticeable. Another way to resolve this problem is to stick to the bigger CN coin via merged mining like XDN or FCN merged mined with XMR.  For small coins, they have to do their research and decide.

Thank you.

so have the huge hash attempts stopped on your coin after the hard fork? Because my theory was that since this seems to happen on all new CryptoNote coins, and they use way more hash power than they'd probably need to get all the blocks for a while, that it wasn't someone mining for profit, but rather an attack.

They stopped. Because it was not profitable anymore with our coin. It was not an attack just greedy mining. It looks like there was more hashpower than needed because there were few such miners and they did not coordinate their 'efforts'. It was very profitable to throw big hashrate for an hour and get few hundreds blocks and therefore few thousands KRB. You see, the cost of one KRB for them was in a range 300-1300 sat. It is at the time when avg price was above 2000 sat. And they are just miners, they are not adepts of the currency, they did not care that those invasions were causing delays in transactions. Not only that, it also was slowering emission rate. Instead of few days we have to wait for a hardfork from block height ~ 55000 when in was announced to 60000 when it occured for a month!

[MWD64]

They stopped. Because it was not profitable anymore with our coin. It was not an attack just greedy mining..,...



ah. OK. Thank you.