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

[Zer0Sum]

Trade KRB at Livecoin.net!

This great!

KRB is now #271 in cap, but only #344 in monthly volume at about 0.2 BTC/day.

As a trader, I've been trying to contribute by creating liquidity on Cryptopia (and doing about 5% of volume)...
Now let's ramp it up... and get Livecoin volume up there to 1-2 BTC/day.
 

It's interesting to see my first post in KRB thread only 13 months ago...
It was #271 at maybe $20,000 cap... today it's #348, but looks cheap at $6,000,000 cap  

[1714520586]

1714520586

[1714520586]

1714520586

[1714520586]

1714520586

[M.minor]

How are you a full member and still don't know that you not supposed to compare price of individual coins, but market caps?
That's still doesn't give you a full picture, but a much better metrics.

So it seemed for me Bytcoin is much less popular and much less developped.

You may google "bytecoin premine" and find how 80% of Bytecoins was mined secretly by developers themselves.
This fact alone give bytecoin a big red "scam" label by majority of crypto community. And nobody want to have a deal with it.
Sure, it pumps sometimes and have a big marketcap, but that's because majority of coins concentrated in few hands.

Recently Bytecoin has another nail in the coffin when it did not fix vulnerability in cryptonote coins and about 700 mln of bytecoins were created by hackers (or possibly insiders) out of thins air and solded on exchanges.

To be clear, karbo didn't suffer from same bug (was fixed in time) and has a clear launch history.

quite right for Bytecoins and his sad story ..,
-a Karbowanec will be an excellent coin!

[M.minor]

KRB-he will have a good traction

[Karbonator]

693 Million Bytecoin Tokens Were Artificially Created

https://www.cryptocoinsnews.com/cryptonote-currency-bug-allowed-creation-unlimited-number-coins/

Karbowanec was derived from Bytecoin, issnt it?

Yes, it was. But unlike Bytecoin it was patched immediately after bug disclosure.
https://twitter.com/krbcoin/status/865185084403580929

In fact Karbo was patched BEFORE the disclosure


I dont want to be distrustful but if Karbo team patched its coin BEFORE the disclosure it could have theoretically been able to exploit this insider knowledge, issnt it? Or did the Karbo team detected the bug, patched the bug with its own coin and reported the bug instantly to the Bytecoin-team?

Or did the Bytecoin-team knew from the bug BEFORE disclosure, told other CryptoNote-protocol based currencies from it and disclosed the bug only later?

What happened exactly and why it did happen this way?

And who is able to fix a bug? Who has the power to change CryptoNote-protocol or was it the CryptoNote algorithm? (protocol = algorithm? I dont know. I am not a programmer)? Was this made by voting system? Who is able to change the code? And why it is so? Not that I as a holder of Karbowanec want to decide in programming decisions because I do not have the required knowlege nor the skills but I as a stupid prospective buyer want to know how everything works more or less respectively is connected with each other. Just to be sure not to own something which could be worthless over night.

As a holder of Karbowanec I just ask myself: "How big or better low is my actual influence and power on the coin?"

Could you say that indeed the blockchain itself which contains the transactions is stored dezentralised and is therefore highly invulnerable and fraud resistent but the properties of the coin itself I am mining, buying, holding and transfering are managed centralized? (by the one or team who is able to change any source code like a bug? if there is no voting system where majority is deciding about major programming decisions)

And thx for the hint for the Karbo-white paper, I will read it. Maybe Karbo-website could link to this essential white paper below "documentation" or so?

If you would do some reading you would find all the answers, hint - CryptoNote whitepaper Grin

I found it (hopefully its the proper paper  ) here: https://cryptonote.org/whitepaper.pdf

Regards

[aiwe]

693 Million Bytecoin Tokens Were Artificially Created

https://www.cryptocoinsnews.com/cryptonote-currency-bug-allowed-creation-unlimited-number-coins/

Karbowanec was derived from Bytecoin, issnt it?

Yes, it was. But unlike Bytecoin it was patched immediately after bug disclosure.
https://twitter.com/krbcoin/status/865185084403580929

In fact Karbo was patched BEFORE the disclosure


I dont want to be distrustful but if Karbo team patched its coin BEFORE the disclosure it could have theoretically been able to exploit this insider knowledge, issnt it? Or did the Karbo team detected the bug, patched the bug with its own coin and reported the bug instantly to the Bytecoin-team?

Or did the Bytecoin-team knew from the bug BEFORE disclosure, told other CryptoNote-protocol based currencies from it and disclosed the bug only later?

What happened exactly and why it did happen this way?

And who is able to fix a bug? Who has the power to change CryptoNote-protocol or was it the CryptoNote algorithm? (protocol = algorithm? I dont know. I am not a programmer)? Was this made by voting system? Who is able to change the code? And why it is so? Not that I as a holder of Karbowanec want to decide in programming decisions because I do not have the required knowlege nor the skills but I as a stupid prospective buyer want to know how everything works more or less respectively is connected with each other. Just to be sure not to own something which could be worthless over night.

As a holder of Karbowanec I just ask myself: "How big or better low is my actual influence and power on the coin?"

Could you say that indeed the blockchain itself which contains the transactions is stored dezentralised and is therefore highly invulnerable and fraud resistent but the properties of the coin itself I am mining, buying, holding and transfering are managed centralized? (by the one or team who is able to change any source code like a bug? if there is no voting system where majority is deciding about major programming decisions)

And thx for the hint for the Karbo-white paper, I will read it. Maybe Karbo-website could link to this essential white paper below "documentation" or so?

If you would do some reading you would find all the answers, hint - CryptoNote whitepaper Grin

I found it (hopefully its the proper paper  ) here: https://cryptonote.org/whitepaper.pdf

Regards

If you want details you  really should read the disclosure itself before asking retared questions. We were warned by the Monero team as well as other coins. Go and ask those coin's devs why they didn't patch. We did. You can check the source code and check blockchain if you have doubts. We have this verification from the very first block so when you synchronize from scratch you will know if there was any forgery. I will not engage in flame with accusations that we used an exploit - you look really stupid. LOL 

[yg10]

I dont want to be distrustful but if Karbo team patched its coin BEFORE the disclosure it could have theoretically been able to exploit this insider knowledge, issnt it? Or did the Karbo team detected the bug, patched the bug with its own coin and reported the bug instantly to the Bytecoin-team?

...

Bold font is not a proof.
Monero team twitted disclosure about the bug 3:28 AM - 18 May 2017
https://getmonero.org/2017/05/17/disclosure-of-a-major-bug-in-cryptonote-based-currencies.html

And KRB team twited about bug fix tw hours later: 5:39 AM - 18 May 2017
https://twitter.com/krbcoin/status/865185084403580929

So your statement is a lie.

[Karbonator]

I dont want to be distrustful but if Karbo team patched its coin BEFORE the disclosure it could have theoretically been able to exploit this insider knowledge, issnt it? Or did the Karbo team detected the bug, patched the bug with its own coin and reported the bug instantly to the Bytecoin-team?

...

Bold font is not a proof.
Monero team twitted disclosure about the bug 3:28 AM - 18 May 2017
https://getmonero.org/2017/05/17/disclosure-of-a-major-bug-in-cryptonote-based-currencies.html

And KRB team twited about bug fix tw hours later: 5:39 AM - 18 May 2017
https://twitter.com/krbcoin/status/865185084403580929

So your statement is a lie.

First. It was no statement but an assumption within a question.

And Second. In my statement (see post #1270) I was quoting "aiwe" (see post #1261) in which he corrected the statement of "Andretti83" (see post #1258) with the words: "In fact Karbo was patched BEFORE the disclosure [of Bytecoin, own note]" because "Andretti83" in turn was answering on my question from post #1257 in his post #1258 with:

Karbowanec was derived from Bytecoin, issnt it?

Yes, it was. But unlike Bytecoin it was patched immediately after bug disclosure.
https://twitter.com/krbcoin/status/865185084403580929

So, if the statement "Karbo was patched BEFORE the disclosure" should not be true, what I am doubting because "aiwe" belongs to the dev-team and I believe him for reasons I do not know, I for one did not state this.

And KRB team twittered 2 hours and 11 minutes later than Monero team at 18 May 2017, 5:39 AM that "#karbowanec is patched and safe". They did not inform about the fact WHEN it was patched.

I was solely wondering why a bug should have been patched before a disclosure. At first glance it sounds a little bit absurd. Thats why I asked in my post #1270:

I dont want to be distrustful but if Karbo team patched its coin BEFORE the disclosure it could have theoretically been able to exploit this insider knowledge, issnt it?

I was originally referring to this news from 28/05/2017: https://www.cryptocoinsnews.com/cryptonote-currency-bug-allowed-creation-unlimited-number-coins/ in which was statet:

After a complete network update, Monero’s team notified all affected CryptoNote-based cryptocurrencies that they had until mid-May to patch the vulnerability. These include Boolberry, Bytecoin, DigitalNote, and DashCoin. (note that DashCoin and Dash are different currencies).

At the time of the initial disclosure, Monero, Aeon, Forknote and Boolberry had already patched the bug. DashCoin, DigitalNote and Bytecoin had not, although now that the vulnerability was made public the developers of these currencies have reportedly fixed the problem.

In any case I did not want to accuse KRB-team to exploit a bug. On the one hand I was surprised that such a heavy weighting bug could be possible and on the other hand I was surprised that the bug was already fixed by the teams of the Bytecoin forked coins like Monero, Karbowanec etc. see

https://upload.wikimedia.org/wikipedia/commons/7/7a/Forks-tree-fixed.png

while in contrast to them the team of Bytecoin which is the parent coin of several coins was not able to fix the bug instantly.

Regards

[yg10]

I dont want to be distrustful but if Karbo team patched its coin BEFORE the disclosure it could have theoretically been able to exploit this insider knowledge, issnt it? Or did the Karbo team detected the bug, patched the bug with its own coin and reported the bug instantly to the Bytecoin-team?

...

Bold font is not a proof.
Monero team twitted disclosure about the bug 3:28 AM - 18 May 2017
https://getmonero.org/2017/05/17/disclosure-of-a-major-bug-in-cryptonote-based-currencies.html

And KRB team twited about bug fix tw hours later: 5:39 AM - 18 May 2017
https://twitter.com/krbcoin/status/865185084403580929

So your statement is a lie.

First. It was no statement but an assumption within a question.

And Second. In my statement (see post #1270) I was quoting "aiwe" (see post #1261) in which he corrected the statement of "Andretti83" (see post #1258) with the words: "In fact Karbo was patched BEFORE the disclosure [of Bytecoin, own note]" because "Andretti83" in turn was answering on my question from post #1257 in his post #1258 with:

Karbowanec was derived from Bytecoin, issnt it?

Yes, it was. But unlike Bytecoin it was patched immediately after bug disclosure.
https://twitter.com/krbcoin/status/865185084403580929

So, if the statement "Karbo was patched BEFORE the disclosure" should not be true, what I am doubting because "aiwe" belongs to the dev-team and I believe him for reasons I do not know, I for one did not state this.

And KRB team twittered 2 hours and 11 minutes later than Monero team at 18 May 2017, 5:39 AM that "#karbowanec is patched and safe". They did not inform about the fact WHEN it was patched.

I was solely wondering why a bug should have been patched before a disclosure. At first glance it sounds a little bit absurd. Thats why I asked in my post #1270:

I dont want to be distrustful but if Karbo team patched its coin BEFORE the disclosure it could have theoretically been able to exploit this insider knowledge, issnt it?

I was originally referring to this news from 28/05/2017: https://www.cryptocoinsnews.com/cryptonote-currency-bug-allowed-creation-unlimited-number-coins/ in which was statet:

After a complete network update, Monero’s team notified all affected CryptoNote-based cryptocurrencies that they had until mid-May to patch the vulnerability. These include Boolberry, Bytecoin, DigitalNote, and DashCoin. (note that DashCoin and Dash are different currencies).

At the time of the initial disclosure, Monero, Aeon, Forknote and Boolberry had already patched the bug. DashCoin, DigitalNote and Bytecoin had not, although now that the vulnerability was made public the developers of these currencies have reportedly fixed the problem.

In any case I did not want to accuse KRB-team to exploit a bug. On the one hand I was surprised that such a heavy weighting bug could be possible and on the other hand I was surprised that the bug was already fixed by the teams of the Bytecoin forked coins like Monero, Karbowanec etc. see

https://upload.wikimedia.org/wikipedia/commons/7/7a/Forks-tree-fixed.png

while in contrast to them the team of Bytecoin which is the parent coin of several coins was not able to fix the bug instantly.

Regards

You have said literally

In fact Karbo was patched BEFORE the disclosure

That was a statement, even with bold shout (capital letters). So you are lying again. Please try to read times  that I provided for you.

[aiwe]

I dont want to be distrustful but if Karbo team patched its coin BEFORE the disclosure it could have theoretically been able to exploit this insider knowledge, issnt it? Or did the Karbo team detected the bug, patched the bug with its own coin and reported the bug instantly to the Bytecoin-team?

...

Bold font is not a proof.
Monero team twitted disclosure about the bug 3:28 AM - 18 May 2017
https://getmonero.org/2017/05/17/disclosure-of-a-major-bug-in-cryptonote-based-currencies.html

And KRB team twited about bug fix tw hours later: 5:39 AM - 18 May 2017
https://twitter.com/krbcoin/status/865185084403580929

So your statement is a lie.

Read the code on a github

update, this is the correction of the threat in question

https://github.com/seredat/karbowanec/commit/4da156f2f07784ac24dde65d98517b1ffc99156f

committed BEFORE the disclosure

PPS. we just waited till Monero team announces this and stated that we're safe and no any forgery ever happened in karbo blockchain.

[aiwe]

Attention to all pool operators.

A security fix was pushed to github:
https://github.com/forknote/forknote

Issue was discovered by Monero Lab and they kindly noticed me about this case.
I strongly advice everyone who run Forknote daemons or daemons of compatible blockchains to update to it ASAP.

....

We announced network id change that will be conducted together with this security update. If you're using Forknote binaries at your pools update ASAP when binaries are published. I will publish them here too.

Tomorrow all you will have to do to change network id is small edit of config file.


Security fix for Karbo is also published on Github. As announced, tomorrow we will release new binaries and wallets containing this fix and new network id.

And here is the announcement where we made an update, just look at the dates, it was BEFORE the disclosure, just  no one knew what for is this

[aiwe]

Thus, yg10, it's you are lying and are making false accusations whether because you don't know the facts or willingly because you're troll or shill


All software updates and announcements concering this bug in cryptonote you can find on page 45 of this thread https://bitcointalk.org/index.php?topic=1491747.880
Way before the disclosure of Monero team. So we were safe. 

[yg10]

Thus, yg10, it's you are lying and are making false accusations whether because you don't know the facts or willingly because you're troll or shill


All software updates and announcements concering this bug in cryptonote you can find on page 45 of this thread https://bitcointalk.org/index.php?topic=1491747.880
Way before the disclosure of Monero team. So we were safe. 

I have posted two timestamps:
1. Disclosure of Monero team. 3:28 AM - 18 May 2017
2. Notification from KRB team that bug was fixed.  5:39 AM - 18 May 2017

Where do you see a lie here?

The intent of my post was to prove to karbonator that KRB team did not exploit the bug.
How do you see the trolling in this?

[aiwe]

Apologies then, but still we have patched our code before the disclosure. Tweet about that was just confirmation for our users that we're fine.

Update, just for clarity:   This means that we, as well as other cryptonote coins, knew about this bug and patched it before the publication of the disclosure because we among other coins were given time to implement patch by Monero devs. Why some coins didn't do this I don't know.

Oh, I won't comment Karbonator's comment about possibilty of using the exploit. Facepalm.

[yg10]

Apologies then, but still we have patched our code before the disclosure. Tweet about that was just confirmation for our users that we're fine.

Update, just for clarity:   This means that we, as well as other cryptonote coins, knew about this bug and patched it before the publication of the disclosure because we among other coins were given time to implement patch by Monero devs. Why some coins didn't do this I don't know.

Oh, I won't comment Karbonator's comment about possibilty of using the exploit. Facepalm.

I am happy that we got to understanding. I quite understand the complexity of problem with security bug especially when multiple projects and teams are involved.

P. S. Greetings with 25th anniversary of .UA TLD.

[valkr2005]

Apologies then, but still we have patched our code before the disclosure. Tweet about that was just confirmation for our users that we're fine.

Update, just for clarity:   This means that we, as well as other cryptonote coins, knew about this bug and patched it before the publication of the disclosure because we among other coins were given time to implement patch by Monero devs. Why some coins didn't do this I don't know.

Oh, I won't comment Karbonator's comment about possibilty of using the exploit. Facepalm.

good time to re re buy

[Karbonator]

Hi Folks,

how can I check the balance of a karbowanec paper wallet?

Thx for answers. Regards.

[Karbonator]

Hi Folks,

how can I check the balance of a karbowanec paper wallet?

Thx for answers. Regards.

problem solved, thx. sorry for being unbelievable dumb and half-cocked. paper wallet is a great tool.

[yubit]

For KARBO supporters!

For Sr. Member, Hero Member, Legendary.

1. Avatar here https://i.imgur.com/33trt0w.png






2. Signature

█████▄▄██████████▄▄█████ ███▄████████████████▄███ ████████████████████████ ████████████████████████ ████████████████████████ ████████████████████████ ████████████████████████ ████████████████████████ ████████████████████████ ████████████████████████ ██▀██████████████████▀██ ████▀▀████████████▀▀████

K A R B O w  w  w  .  k  a  r  b  o  .  i  o

Ҝ Ҝ Ҝ

DECENTRALIZED EXCHANGE MEDIUM ANN THREAD       TWITTER       TELEGRAM EN       TELEGRAM UA/RU

Ҝ Ҝ Ҝ

· Anonymity by CryptoNote · Zero premine & instamine · Low transaction fee

Code:

[center]
[table]
[tr]
[td][size=2pt][color=transparent]█████[color=#00a0e2]▄▄██████████▄▄[color=transparent]█████[/color]
[color=transparent]███[color=#00a0e2]▄████████████████▄[color=transparent]███[/color]
[color=transparent]██[color=#00a0e2]█████[color=#ffed00]███[color=#00a0e2]█████[color=#ffed00]███[color=#00a0e2]████[color=transparent]██[/color]
[color=transparent]█[color=#00a0e2]██████[color=#ffed00]███[color=#00a0e2]████[color=#ffed00]███[color=#00a0e2]██████[color=transparent]█[/color]
[color=#00a0e2]███████[color=#ffed00]███[color=#6bc084]█[color=#ffed00]█[color=#00a0e2]█[color=#ffed00]███[color=#00a0e2]████████[/color]
[color=#00a0e2]███████[color=#ffed00]████████[color=#00a0e2]█████████[/color]
[color=#00a0e2]███████[color=#ffed00]████████[color=#00a0e2]█████████[/color]
[color=#00a0e2]███████[color=#ffed00]███[color=#6bc084]█[color=#ffed00]█[color=#00a0e2]█[color=#ffed00]███[color=#00a0e2]████████[/color]
[color=#00a0e2]███████[color=#ffed00]███[color=#00a0e2]████[color=#ffed00]███[color=#00a0e2]███████[/color]
[color=transparent]█[color=#00a0e2]██████[color=#ffed00]███[color=#00a0e2]█████[color=#ffed00]███[color=#00a0e2]█████[color=transparent]█[/color]
[color=transparent]██[color=#00a0e2]▀██████████████████▀[color=transparent]██[/color]
[color=transparent]████[color=#00a0e2]▀▀████████████▀▀[color=transparent]████[/color][/size][/td]
[td]  [/td]
[td][center][b][url=https://karbo.io][size=18pt][color=#0090cc][font=Verdana]K A R B O
[size=6pt][color=#01adf4]w  w  w  .  k  a  r  b  o  .  i  o[/font][/color][/size][/url][/b][/center][/td]
[td]  [/td]
[td][size=9pt][color=#f4e300]Ҝ
Ҝ
Ҝ[/color][/size][/td]
[td]  [/td]
[td][center][b][font=Verdana][size=2pt]   [/size]
[url=https://karbo.io][size=13pt][color=#01adf4][u]DECENTRALIZED EXCHANGE MEDIUM[/u][/color][/size][/url]
[color=#00a0e2][size=7pt][url=https://bitcointalk.org/index.php?topic=1491747]ANN THREAD[/url]       [url=https://twitter.com/krbcoin]TWITTER[/url]       [url=https://t.me/karbo_en]TELEGRAM EN[/url]       [url=https://t.me/karbowanec]TELEGRAM UA/RU[/url][/size][/color][/font][/b][/center][/td]
[td]  [/td]
[td][size=9pt][color=#f4e300]Ҝ
Ҝ
Ҝ[/color][/size][/td]
[td]  [/td]
[td][color=#0090cc][size=9pt][font=Verdana][url=https://karbo.io]· Anonymity by CryptoNote
· Zero premine & instamine
· Low transaction fee[/url][/font][/size][/color][/td]
[/tr]
[/table]
[/center]

[miner.rocks]

Hello, fellow miners!

New pool started:
krb.miner.rocks

Features:
- email notifications when worker went down
- workers status on site
- every port supports secure SSL/TLS connection as well as insecure one
- port 80 available for firewalled miners

Welcome!

[yg10]

Yet another two masternodes.

1. karb.stranger.com:32348  (35.202.141.131)
    Location Google Cloud us-central

2. 24.6.172.202:32348
    Location US, California.