For Sr. Member, Hero Member, Legendary.
Very nice!
the signatur shows wrong in my sig
Are you a senior member or higher??? Nope. Still, in your case Karbo is rising and lurking magnificently above the horizon
It was the Bitcointalk forum that inspired us to create Bitcointalksearch.org - Bitcointalk is an excellent site that should be the default page for anybody dealing in cryptocurrency, since it is a virtual gold-mine of data. However, our experience and user feedback led us create our site; Bitcointalk's search is slow, and difficult to get the results you need, because you need to log in first to find anything useful - furthermore, there are rate limiters for their search functionality.
The aim of our project is to create a faster website that yields more results and faster without having to create an account and eliminate the need to log in - your personal data, therefore, will never be in jeopardy since we are not asking for any of your data and you don't need to provide them to use our site with all of its capabilities.
We created this website with the sole purpose of users being able to search quickly and efficiently in the field of cryptocurrency so they will have access to the latest and most accurate information and thereby assisting the crypto-community at large.
█████▄▄██████████▄▄█████ ███▄████████████████▄███ ████████████████████████ ████████████████████████ ████████████████████████ ████████████████████████ ████████████████████████ ████████████████████████ ████████████████████████ ████████████████████████ ██▀██████████████████▀██ ████▀▀████████████▀▀████ |
December 05, 2017, 03:36:41 PM
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. December 05, 2017, 09:58:01 AM
Hi Folks,
how can I check the balance of a karbowanec paper wallet? Thx for answers. Regards. December 05, 2017, 04:23:01 AM
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. good time to re re buy 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. December 04, 2017, 04:58:35 AM
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. 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.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. P. S. Greetings with 25th anniversary of .UA TLD. December 03, 2017, 07:54:33 PM
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. December 03, 2017, 07:50:39 PM
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? December 03, 2017, 08:34:34 AM
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. December 03, 2017, 08:32:29 AM
Attention to all pool operators. 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 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. December 03, 2017, 08:22:54 AM
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. 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. December 03, 2017, 06:35:02 AM
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? 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: Quote 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: Quote 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 Quote 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.December 03, 2017, 05:02:19 AM
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? 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: Quote 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: Quote 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 December 03, 2017, 12:45:16 AM
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. December 02, 2017, 07:06:20 AM
Quote 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? Quote Yes, it was. But unlike Bytecoin it was patched immediately after bug disclosure. In fact Karbo was patched BEFORE the disclosurehttps://twitter.com/krbcoin/status/865185084403580929 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? Quote 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 December 02, 2017, 05:39:15 AM
Quote 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? Quote Yes, it was. But unlike Bytecoin it was patched immediately after bug disclosure. In fact Karbo was patched BEFORE the disclosurehttps://twitter.com/krbcoin/status/865185084403580929 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? Quote 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 December 02, 2017, 05:21:30 AM
KRB-he will have a good traction
Jump to:
|