Thanks for this. I admit that the frustration of the latest BTC forking got me wound up and that overflowed to my comments. I realise James has had bigger issues at hand with the recent bugs. If it's worth attacking then it must be a threat to someone which is positive.
One other issue, when/if Bitcoin Unlimited is deemed a failure, how does that affect the notary servers going forward?
I can break these down
Brands:
- SuperNET
- Agama
- Komodo
Not brands:
- EasyDEX (the shapeshift like exchange service in Agama)
- Full/Native/basilisk Mode (i.e. blockchain download or no blockchain download in Agama)
The 'Mode' situation has been further simplified as we disabled 'Full Mode' from all the coins that have 'Native Mode'. So what the end user has to decide is simple: a) download the blockchain, or b) don't download it. We can illustrate the difference with icons and simple description.
SuperNET = the main brand, the organization behind the other brands
Agama and Komodo are/will be endorsed semi-independent brands. They have a loose connection to the parent SuperNET organization.
The effect on notaries if BU fails is they have to run the following commands: cd ~/BitcoinUnlimited/src; ./bitcoin-cli stop; cd ~/bitcoin/src; ./bitcoind & |
|
|
|
It was issued and in the pipeline, but never matured to be ready even for doing a sharedrop, let alone sales. I believe the project sold some assets to private investors on an occasional basis, but if you look at the asset distribution, it is mostly in its initial capitalization phase |
|
|
|
|
Finally got a version that is able to resync and also resume. Off by one in the same code due to different contexts having slightly different datasets.
Not exactly the type of thing to be dealing with after an allnighter...
Anyway, now notaries have a version that can resume the mainchain, it is a matter to get the blocks going regular again and then we will reenable exchange deposits when the evil chain has dissipated.
|
|
|
|
hi jl777 I would like to know if it is this
Asset still exists = omnigames = Or is it dead
I dont believe omnigames was ever distributed, at least it was still in the incubation stage, so there shouldnt have been any assets available. I have not heard from the project leader in a while |
|
|
|
|
In order to avoid any lost funds, we asked exchanges to stop deposits/withdraws while the mainchain gets back to normal.
I expect things to get resolved today, thank you for your patience
|
|
|
|
|
Now that we are past the hardfork block 246748, I updated to a version that hardcodes that.
If your node went past that block, you will need to resync. If not, just update and it will get onto the mainchain.
This time around could have gone a bit smoother, I had botched the initial hotfix. If I didnt, we could have avoided resyncing. Unfortunately, at middle of the night hours it wasnt possible to get the code reviewed so I had to do the best given the time available (< 1hr).
As I wrote last week, it is not possible to live in an attack free environment. If you rely on that, then the first attack and there is trouble. We are getting better at dealing with these attacks, our immune system is getting better, but we can still do better. And we will.
Due to needing resync, basilisk mode will be spotty for some hours. Best to not do any large transactions until it is announced mainchain is like clockwork again and evilchain is gone
|
|
|
|
|
Mainchain is paused as it tries to find consensus to move forward. So without tx being possible it seems relatively safe, but this means basilisk mode wont work until the chain gets going again.
|
|
|
|
|
As you know we are offering bounties for finding security issues in the code base. Approx 16 hours ago, we received a vulnerability report.
Within 6 hours we had verified it, developed and tested a fix and started updating the notary nodes. In order to give enough time for the field to update, I set the fix to activate at 4:30 PM UTC. This was about 16 hours time and I was hoping long enough for the field to update and short enough to avoid a zeroday attack.
Unfortunately, the attacker sees the fix on github as it is open source and he deployed an attack within the last hour. I was forced to move up the activation time to 5am UTC, which is less than half an hour from now.
Exchanges have been notified, along with pools. Notaries are almost completed the update. The damage from this attack will be minimal, actually zero, as the security bounty is offset by whatever damage is done, so the total cost remains the same.
If you are running a native komodod, you need to update. The network is about to do a controlled fork.
The problem of fixing things in an open source project is a difficult problem to solve. In this case we deployed a fix within 6 hours of being notified, had everything update and still we get hit with an attack. It does feel like antivirus vs virus.
Anyway, we will get better and better and dealing with these things more efficiently, but it is much better to already have the fix deployed than getting blindsided by an attack. Next time I will set the activation time shorter to give less time for attacker to deploy. (always assume and prepare for next time, so if it happens you are ready)
|
|
|
|
I was wondering, how can I backup my Iguana wallet? In case it gets corrupted, would it be possible to reinstall it and get inside only with the seed without importing any .dat files for instance?
the seed is the backup for the main address,which is the only address a wallet would have unless you importprivkey or generate new addresses. The latter operation is something you need to do by command line and if you are importing privkeys then the assumption is that you have backup of it. so, for most people most of the time, all that is needed is the seed |
|
|
|
|
iguana core is still iguana so for those who like iguana name, it is still there
there was just so much confusions about iguana core vs iguana gui
and with upcoming tradeshow and marketing, it is best to do any name changes beforehand
|
|
|
|
Had over 200 KMD balance on Suprnova. Now it shows 0, all gone.
I checked transactions, shows nothing. Earnings have been reset to zero as well.
Do not worry. I am working with suprnova to resolve this situation. I will support the people that support komodo and that includes all parts of the ecosystem. |
|
|
|
so when is the stable wallet released ? I need the wallet to run perfectly and it shouldn't cause many issues to effect all investors. I did not dare to withdraw all my KMD coins to the wallet to stake it due to this issue.
From what I can tell the wallet is stable, unless you have a system configuration where it still has some troubles. Getting 100% smooth install/function on all possible variations of OS/computers will take some time. We are working to resolve such incompatibilities as quickly as possible. Also, there is no staking, the interest accumulates automatically, so just doing a payout to your address you will start earning interest and your coins are on the blockchain. |
|
|
|
tried this option
have inscription at the first start of the wallet(starting iguana daemon....)
and all the wallet doesn't open
Have you tried uninstalling/deleting everything and trying again through a clean install? Last thing I could think of...  I have tried all the options that are available for my brain))) only thing I haven't tried is installing on a clean operating system))) I don't want to reinstall Windows because all other programs and wallets are working fine!!! Deleted the folders from roaming? Yes in the first place Robot like answer: Insufficient data. Unable to process request. Join Slack, go to #support channel there, and explain in all details. Can you give me the link to join Slack-Support? slackinvite.supernet.org |
|
|
|
in case of hard fork of bitcoin and split of the blockchain how the dPow algorithm will work?
sorry about the late response, been a bit busy recently. A few weeks ago when the mempool backlog started, I asked all the notary nodes to switch to BU. My logic was that if there is no hardfork, there is no difference which version is running. If there is a hardfork, it would only be if BU is the hashrate leader (it already has 40%), so by running BU ahead of time we wont have to do anything at all. |
|
|
|
HEAT is creating false Komodo. Explanation: I traded on heatwallet.com HEAT <-> Komodo(KMD) Link: https://heatwallet.com/#/trader/Later the lead developer said, it's not a real Komodo, it's an assed called Komodo (KMD) without any value and not removable. An anonymous person can create on HEAT any existing currency without having a cent?? No, that's not right, it costs money, they pay the developers to create any fake coin. So the developers are earning money by creating false komodos! Lost all my HEAT into false Komodos and false Golems. Now I hear, that the supernet is invested in HEAT. This is very disturbing! So is the meaning of P2P-trading to trade hot air??? Is this also the Komodo way? I thought you are planning to trade real blockchains? What are you talking about? The HEAT assets are only as good as the issuer and the issuer for the KMD and Golem assets on HEAT is an anonymous uncertified issuer. That means it can be anybody doing it and without any assurance of validity. Even with a certified asset, there is risk of trusting whoever is certifying it. However there are usecases where this is acceptable. The iguana DEX is a native DEX, meaning there is no issuer of an intermediate asset, you always control your crypto even for trading. THAT is the SuperNET way. Buying uncertified assets is not recommended in any way shape or form. Also, holding a position in a separate project just means that we have that position. It does not mean anything more, or less. |
|
|
|
Version: 1.0.5 (last version)
Errors: WARNING: check your network connection, 105 blocks received in the last 4 hours (240 expected)
Current Block: 242687
What this?
it just means blocks have been slower than expected. Also, that indicator's time base is not quite right so in general it isnt anything to worry about. much better indication is the recent blocktime on kpx.io, which shows 70.11s versus the expected 60 seconds per block. Well within the expected variation due to mining. Keep in mind we did have a fork yesterday, so if the blockchain is an ocean, there are bigger waves than normal in the water |
|
|
|
|
The network is on a fork starting at 241777.
The latest version needs to be updated to.
I sent PM to cryptopia, but no response. if they have not updated, they need to and also best to stop deposits until the situation resolves.
if you are running an old komodod, then update and then run the command:
./komodo-cli invalidateblock 00000299dd7a22edc91e1d43ac11f83e2d3d7a1c536d4a7bc6cfa0533244634f
that will get you in sync to the mainchain
We had already patched the vulnerability (in a separate area) and were in the process of validating it. Everything prior to 241777 is fine
|
|
|
|
how many TPS komdo can handle? Bitcoin can handle only 4 TPS.
20x the transparent TPS as it has 10x faster blocks and 2MB blocksize z-transactions are about 5x larger, so if 100% of transactions are z-transactions, then "only" 4x faster, but it is highly unlikely to go 100% ztransactions, so most likely in the 10x to 20x. Now that is counting just KMD. If assetchains are added into the mix, there are almost 50 assetchains, so that is another 50x multiplier, which would end up at some crazy 500x to 1000x capacity if you count all assetchains that currently exist. of course, hundreds more assetchains can be created. scaling tps can be done by replicating already working tech |
|
|
|
So if the hacker was able to mine block after block... does that indicate the hacker is running a notary node?...... as Notary Nodes get to mine most blocks......I'm asking this as I have not seen this conspiracy theory raised yet..... I struggle with lets run decentralized coin by centralizing most of the mining power, sounds a little oxymoronic to me.......Anyway if someone can explain how someone could mine block after block I for one would love to know how....AFAIK this is the real question Cheers Jon  notary nodes sign each block they mine attacker used GPU to mine and when he was the only one left mining on his chain, he was getting all the blocks. you can do that with any coin, even bitcoin. Just disconnect from all peers and start mining. When you go on a fork, you often end up mining many blocks, its just not anything others will recognize. 64 nodes is a bit of a distance away from being centralized. Many coins have about that many total nodes. KMD has all the notary nodes, plus mining pools and independent miners, all able to mine blocks. Current balance is about 70% notary nodes, 30% others, but some of the big mining pools are not back online yet, I think we will end up in the 40/60 to 60/40 range. By dividing the blocks in to roughly equal halves, neither population can get any confidence to conduct an attack and this provides more security |
|
|
|
|
Show Posts
