Topic: [ANN][KMD][dPoW] Komodo - An Open, Composable Smart Chain Platform, Secured by B - page 95. (Read 1192053 times)

Blocnation dICO less than a week away! Call me excited!

Report to moderator ! 
I made it!

I'm really interested in this one. Thanks!

Users and supporters of Komodo platform must be careful and vigilant about download links . Better check officially release clients form official website of Komodo. Hackers are rampant because they know how valuable and promising this project can be.

Thanks for the heads up

Wait for new version!! 

Updated all my branches (master, beta, dev) with a fix for "stuck nodes". This is only needed if your node was stuck on the mainchain and not advancing to the chaintip.

I apologize for having taken this long to get a fix for this out and until we see that there are no more stuck nodes we cant be 100% sure this fix will fully fix it, however in my tests so far it is running stable after over 200 machine hours.

The behavior is much improved and I finally have some time to explain what I was up against. The changes I made last week to prevent the banning of valid nodes was the right track, but not complete enough. There were a few other cases where in effect the same thing happened, ie. valid blocks got marked as invalid and once that happened, you needed to stop and relaunch to get it to accept the valid block.

This combined with a miner change I made that had the combined effect of something that is much like a timewarp attack and blocks with future timestamps were broadcast to the network. I made things even worse by proactively pushing new blocks out to the network to solve the issue of a newly mined block not propagating fast enough.

With the natural variance in the system clocks of nodes and the calculated timeoffset, if a block is right on the borderline of the allowed futurestamping (+60 seconds), it is possible for some nodes to not only reject that block, but to start banning the peer and marking the block as permanently invalid. This seems an overreaction as the difference of 1 second would be the difference between a block being permablocked or not. and if a node marks as invalid a block on the mainchain... it gets stuck. What made things worse was the rapid propagation of the new block!

That made it that much more likely for a node to get a futurestamped block too soon. So the first step was to allow futurestamped blocks to have a less severe treatment and this made things much better. However still some nodes got stuck...

The reason is that deep inside the bitcoin syncing logic is the assumption that the blockheader for a block is arrived before the block, so my broadcasting of new blocks was violating this. However extending the chaintip was handled as its previous block is already known and it would just extend the chain. The problem arose when multiple blocks were found and then propagated out of order. In this case it was possible for a block to arrive that didnt have the prevblock ever seen, even at the header level.

And to support the rapid propagation of new blocks, which reduces the undesired small forks that are natural for blockchains, I needed to dynamically add the out of order blocks into the blockchain data.

Anyway, the stuck blocks was totally self-inflicted and I apologize for any inconvenience, but now newly mined blocks will propagate faster. Also, we are now resistant to a timewarp attack and even an out of order block broadcast.

Along the way I fixed the bug where invalid tx in the mempool were not being purged. Now any tx that is spending interest that stays in the mempool for over an hour will be purged. This means if after an hour your tx doesnt confirm, you dont have to worry about it coming back to life and confirming. It couldnt do that before, but having it staying in the mempool wasnt good as it prevented spending the same vins.


tl:dr if your node hasnt been stuck, there is no need to update. if it is, plz either update from my repo or wait for the new binaries on komodoplatform

I’m talking abt the coming days...I know that Komodo is an excellent Long term coin.
These pumps are based on news and hype. I prefer continuous steady rise over time, that’s how good project works.

Komodo mining has made it to minergate pool. Being exposed to more popular mining pool is really a plus factor for those are having difficulty in finding a decent pool for mining komodo.

Developers are vigilant enough to fix and came up an upgraded wallet. With ICO coming it is really good to know if there is still lingering bug around wallets .  Eventually those hard work will be pay off massively.

Thank you for the FAQ. To confirm: BTCD submitted for swap will be credited as Komodo IN THE ICO USER ACCOUNT area, for withdrawal as normal afterwards?
If this is the case, BTCD holders will need to open an account before the ICO is over, or else ICO account creation will need to continue after funds are no longer being collected.
Just useful to clarify these points, thanks.

That's correct. The wallet was updated yesterday. New videos and tutorials will follow on the new encrypt wallet feature.

It's not now I just downloaded it.

Posted:

"Version: 0.2.34-beta

Date: Sat Apr 21 22:10:03 CEST 2018"

the wallet is currently being updated, that's why there is no download link.

i saw aswell the issue... take a look please admin...

and what is the last agama wallet?

The desktop wallets on https://komodoplatform.com don't seem to download, is the wallet under maintenance?

i pushed a fix to dev branch to prevent nodes from getting stuck.