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

[treanski]

Can you sum up what happened in Intense? In our case it was not 51% attack of double spend. We had several types of attacks. First one was abusing vulnerability in difficulty algo which we were going to close - in the same day we put preparation on github there was an attack - having >51% hashrate they managed to temporarily lower the difficulty and got ~10k krb. in an hour. We decided that it's not worth rolling back chain. Aftherwards there were two spam attacks - spamming transactions with large mixins that were large in size and hard to verify so some nodes were crashing, after we set limit to max mixin they started to just spam so we had to set higher fee.

read yourself

https://intensecoin.com/2018/04/16/imminent-hard-fork-and-network-attack/

[1714606722]

1714606722

[1714606722]

1714606722

[Sberex]

Can you sum up what happened in Intense? In our case it was not 51% attack of double spend. We had several types of attacks. First one was abusing vulnerability in difficulty algo which we were going to close - in the same day we put preparation on github there was an attack - having >51% hashrate they managed to temporarily lower the difficulty and got ~10k krb. in an hour. We decided that it's not worth rolling back chain. Aftherwards there were two spam attacks - spamming transactions with large mixins that were large in size and hard to verify so some nodes were crashing, after we set limit to max mixin they started to just spam so we had to set higher fee.

read yourself

https://intensecoin.com/2018/04/16/imminent-hard-fork-and-network-attack/

“As almost 6,000 blocks were stolen by the attacker(s), the blockchain will be rolled back to the last normal block before the attack started.”

As far as I understand blocks were actually mined by attacker due to exploit in diff algo. Read yourself:

“Most significantly, the attacker manipulated timestamps of the blocks to exploit a weakness in the difficulty calculation algorithm of the coin. This manipulation allowed the attacker to find about 8 days worth of blocks in several hours.”

Highly likely this attack was conducted via NiceHash.

By the way, Karbo after recent hardfork is protected against this type of attack.

“The Intense Coin blockchain will hardfork to version 4 in the next several days as the developers conduct testing. Version 4 will include several new features:
- Adoption of zawy12’s LWMA difficulty algorithm, which is much more responsive to hash power fluctuations. LWMA has been live on several coin networks for a few months. Zawy and the coin developers have worked out the bugs, and the algorithm has proven to be very reliable in testing and production.”

Karbo successfully adopted zawy12’s diff algo about a year ago. So Karbo is actually the first from these “several coin networks”.

[PainKiller1986]

karbo isn't go migrate to other version of cryptonight 

[stna1981]

So I got it right that Karbo will not fork in any way to kick ASICS out, right? This makes mining this coin useless unfortunately. With 16 cards I would earn just 1.5 coins a day which are currently worth roughly 1 USD. Power cost would be more that 6 USD, makes no sense. Diff went up x10, before the profit per day was about 3 to 4 USD a day, which was not great, but ok.

Your decision if you want to put your coin in the hands of the community or a company that provides 75% of the hash rate with all the knows drawbacks.

[aiwe]

No we stated that we won't rush to change algo to Monero tweak. And that we might stay asic-compatible but it is not certain. As I said, our bigger concern is Nicehash and we don't want algo same as Monero or other large coin has which is present on Nicehash. We are researching and preparing for the upcoming hardfork.

[campurro]

No we stated that we won't rush to change algo to Monero tweak. And that we might stay asic-compatible but it is not certain. As I said, our bigger concern is Nicehash and we don't want algo same as Monero or other large coin has which is present on Nicehash. We are researching and preparing for the upcoming hardfork.

Turtlecoin, Iridium, Triton, Aeon and others have forked to use Cryptonight lite v1. Anti-ASIC and not present on Nicehash and good for small miners (CPU/GPU).

[aiwe]

It's not present untill it's not interesting for Nicehash. Wait for pump of some of those coins.
In the mean while we are the first Bytecoin based coin to have working CryptoNight Heavy algo on testnet (the rest are Monero based).

[stna1981]

CH Heavy would be fine and you would probably have to fork less often than XMR because they only do slight changes while CN Heavy should put much more effort into ASIC development...

[aiwe]

Some party is obstinately mining their alternative chain. All accepting Karbo please beware and make sure you are using karbo clients from official repository and are on correct chain, where's majority of pools and nodes are. Please refer to block explorer and tab Pools there.

Looks like forknote clients are affected.



Update. We think this is unmaintained private pool that is using outdated karbo deaemon and is accepting transactions from old outdated wallets with too small fees. Due to those transactions their blocks are rejected.

[aiwe]

Someone is still running pool on karbowanecd, please switch to forknoted - you're getting orphaned blocks anyway.

LOL, are you kidding?

[SuffXMR]

anit asic or not?

[PainKiller1986]

anit asic or not?

Not anti asic, using Cryptonight V1

[aiwe]

anit asic or not?

Not anti asic, using Cryptonight V1

Karbo has original CryptoNight POW. CryptoNight V1 is actually Monero's modified version, which is confused and often erratiacally referred to as CryptoNight V7. It's V1, v7 is Monero hard fork number.

And no, so far no plans to change POW to implemented and postponed CryptoNight Heavy.

[stna1981]

If CryptoNight Heavy is already implemented, why was it postponed?

[aiwe]

If CryptoNight Heavy is already implemented, why was it postponed?

Because of this

[stna1981]

Well, I don't really see the point here. The article just describes that it is not as easy as one might have thought to keep ASISs out in the long term with just small changes to the PoW.

But does that really mean to you that it's not even worth trying it? Is it then really better to do nothing and just let everything happen, to have 80% or 90% of your coin being mined by ASICs, meaning centralisation and 51% made easy as taking candy from a baby? For me, this is not the right approach, especially as for the moment, CN-Heavy would solve the problem, you just need to flip the switch.

Yes, we all do not know what's coming in the future, yes it might be (more) difficult in the future to keep ASISs out, yes, it will require some work from devs to keep their PoW up-to-date, but for me, this would definitely be worth the work.

"He who fights can lose, but he who does not fight has already lost!" - Brecht

[Sberex]

something that is certain to happen and cannot be prevented
change pow algorithm or KRB will die soon.

Why should KRB change POW algo? With current algo Karbo price and hash rate are growing, so KRB is growing while BTC is falling.





Karbo is the most pumped coin on livecoin exchange.

As far as I know coins are dying in a little bit different way.

[jerrimu]

If CryptoNight Heavy is already implemented, why was it postponed?

Because of this

 
 
 Thank you! I keep saying the same thing.  Why change algo when they stop mining in secret and make available foe everyone?  A baikal n+ (40kh CN) costs half of a 1080 (2kh CN).  You are just changing the method of centralization.

[jerrimu]

something that is certain to happen and cannot be prevented
change pow algorithm or KRB will die soon.

 
 Like asics killed BTC?

[Sberex]

something that is certain to happen and cannot be prevented
change pow algorithm or KRB will die soon.

 
 Like asics killed BTC?

I don't mind if Karbo someday will reach (die in your words) the price level of BTC.