Topic: [ANN][KMD][dPoW] Komodo - An Open, Composable Smart Chain Platform, Secured by B - page 503. (Read 1192347 times)
March 23, 2017, 03:52:41 PM
I wonder when the 10k sat will pass. I guess the full version of the wallet will be effective instead of the betas.
March 23, 2017, 03:24:50 PM
I am curious as to back story of the lizard names. Where are these names coming from? Why are they chosen?
Agama is a very curious name, I had to look it up as I had never heard of an Agama before. Very nice colors on that lizard, is that why it was chosen? Why not something cool like an alligator or a triceratops? Komodo is a big lizard after all.
Why not have renamed iguana core, supernet core and kept Iguana instead of Agama? Or call it "Lounge Core"; you know a group of lizards is called a lounge.
Will jumblr be renamed to chameleon?
Community voting on names?
Agama is a very curious name, I had to look it up as I had never heard of an Agama before. Very nice colors on that lizard, is that why it was chosen? Why not something cool like an alligator or a triceratops? Komodo is a big lizard after all.
Why not have renamed iguana core, supernet core and kept Iguana instead of Agama? Or call it "Lounge Core"; you know a group of lizards is called a lounge.
Will jumblr be renamed to chameleon?
Community voting on names?
March 23, 2017, 02:58:59 PM
Getting Bus error (core dumped) when trying to run Agama from terminal.
Wait for new version.
Some more GUI bugs fixed.
And new komodod will be shipped with next release.
March 23, 2017, 02:52:25 PM
Getting Bus error (core dumped) when trying to run Agama from terminal.
March 23, 2017, 02:29:40 PM
We will pause the mainchain at 247204, when things are sorted it will resume from there.
March 23, 2017, 02:24:45 PM
I am still not happy with the hotfix, but need to get some coffee.
So there will be more updates to bulletproof this area
So there will be more updates to bulletproof this area
March 23, 2017, 02:16:42 PM
As I wrote before there is now a one hour timeframe for a tx, so there is a compare against (timestamp - 3600) to check for tx nLockTime validity.
This one hour of leeway does allow collecting one hour's interest, but at 250000 we will subtract 59 minutes from the effective time. So this free interest will close soon.
We saw that the attacker was taking advantage of this, which made little sense as it is only getting small fractional KMD. Until we realized it also had the effect of creating edge cases, which would make a node create a block that it would then reject on restart.
The error is totally my fault, I used the chaintip's timestamp instead of the block's timestamp, not even sure why.
Now to make things more interesting as things would be so boring with just an issue like the above, there appears to be a DOS attack with killer network messages that crashes nodes randomly. Not sure if it is an intentional thing, or maybe it is just due to the current chain's state.
Anyway, I put a patch in for the crash, so it stops crashing now, but the cause of it is not time enough yet to solve.
I also pushed a version that uses the consensus safe value for the timestamp check. Notaries are in the process of verifying this.
From what I can tell the vast majority of the network is on the same chain, so we might not even have a fork, but with nodes randomly crashing it is hard to say. When the crash resistant version is propagated we can better assess things.
The black hat made something like 1400 KMD from his attacks. He could make far more if he just reported these issues...
Anyway, it is very good that we are getting help from very capable people to help solve these issues in a timely fashion. Thanks to all!
This one hour of leeway does allow collecting one hour's interest, but at 250000 we will subtract 59 minutes from the effective time. So this free interest will close soon.
We saw that the attacker was taking advantage of this, which made little sense as it is only getting small fractional KMD. Until we realized it also had the effect of creating edge cases, which would make a node create a block that it would then reject on restart.
The error is totally my fault, I used the chaintip's timestamp instead of the block's timestamp, not even sure why.
Now to make things more interesting as things would be so boring with just an issue like the above, there appears to be a DOS attack with killer network messages that crashes nodes randomly. Not sure if it is an intentional thing, or maybe it is just due to the current chain's state.
Anyway, I put a patch in for the crash, so it stops crashing now, but the cause of it is not time enough yet to solve.
I also pushed a version that uses the consensus safe value for the timestamp check. Notaries are in the process of verifying this.
From what I can tell the vast majority of the network is on the same chain, so we might not even have a fork, but with nodes randomly crashing it is hard to say. When the crash resistant version is propagated we can better assess things.
The black hat made something like 1400 KMD from his attacks. He could make far more if he just reported these issues...
Anyway, it is very good that we are getting help from very capable people to help solve these issues in a timely fashion. Thanks to all!
March 23, 2017, 02:15:05 PM
It seems I wont ever get to sleep for more than 3 hours at a time...
KMD network is processing some killer messages and nodes are being killed. This sounds somewhat familiar. We are investigating.
Also, the recent attacker has constructed a problematic transaction, which might have caused a fork at 247204. First step is to stop the killer message, but best to assume chain is stopped at 247204
KMD network is processing some killer messages and nodes are being killed. This sounds somewhat familiar. We are investigating.
Also, the recent attacker has constructed a problematic transaction, which might have caused a fork at 247204. First step is to stop the killer message, but best to assume chain is stopped at 247204
Thanks a lot James!
Obviously, someone who knows quite a lot about blockchains and blockchain coding is doing their best to bring down your stuff - and failing badly
I wonder how that is paying off for the loser
March 23, 2017, 02:14:48 PM
There will be a reward for those who believed!
March 23, 2017, 02:10:27 PM
What doesn't kill it makes it stronger. It's actually good to have attention of some smart cookies. Better stress-test it now guys.
No one wants these hiccups while getting closer to the top.
No one wants these hiccups while getting closer to the top.
March 23, 2017, 01:41:41 PM
How long do you folks give the attacker to figure out that the only way to end up with any decent amount of KMD is to buy them from us? 
It's a never ending Tom & Jerry Game.
Thanks for being on top of things!
Agree with that! You guys are fast and furious!
March 23, 2017, 12:47:34 PM
How long do you folks give the attacker to figure out that the only way to end up with any decent amount of KMD is to buy them from us?
It's a never ending Tom & Jerry Game.
March 23, 2017, 12:42:41 PM
Another release of wallet will be released.
So hold on tight until next release with updated komodod comes out with the new version of Agama App.
I also found some GUI bugs, which are fixed and will be shipped in next release.
So hold on tight until next release with updated komodod comes out with the new version of Agama App.
I also found some GUI bugs, which are fixed and will be shipped in next release.
March 23, 2017, 12:34:28 PM
It seems I wont ever get to sleep for more than 3 hours at a time...
KMD network is processing some killer messages and nodes are being killed. This sounds somewhat familiar. We are investigating.
Also, the recent attacker has constructed a problematic transaction, which might have caused a fork at 247204. First step is to stop the killer message, but best to assume chain is stopped at 247204
KMD network is processing some killer messages and nodes are being killed. This sounds somewhat familiar. We are investigating.
Also, the recent attacker has constructed a problematic transaction, which might have caused a fork at 247204. First step is to stop the killer message, but best to assume chain is stopped at 247204
March 23, 2017, 11:52:58 AM
Mandatory Update: Agama #Multicoin Wallet v0.1.5.6e with Jumblr KMD BTC Anonymizer (Bitcoinmixer) – Download
Twitter : https://twitter.com/KomodoPlatform/status/844932024322404352
Reddit : https://www.reddit.com/r/komodoplatform/comments/612i0a/mandatory_update_agama_multicoin_wallet_v0156e/
Facebook : https://www.facebook.com/KomodoPlatform/photos/a.330322533980991.1073741828.321638648182713/428592014154042/?type=3&theater
News SuperNET : http://news.supernet.org/posts/xAgWNyKoDuMd27727/mandatory-update-agama-multicoin-wallet-v0-1-5-6e-with
Reddit : https://www.reddit.com/r/komodoplatform/comments/612i0a/mandatory_update_agama_multicoin_wallet_v0156e/
Facebook : https://www.facebook.com/KomodoPlatform/photos/a.330322533980991.1073741828.321638648182713/428592014154042/?type=3&theater
News SuperNET : http://news.supernet.org/posts/xAgWNyKoDuMd27727/mandatory-update-agama-multicoin-wallet-v0-1-5-6e-with
It is Linux and OS, not still for windows?
Windows version is bit delayed. It will be released soon.
March 23, 2017, 11:51:59 AM
Mandatory Update: Agama #Multicoin Wallet v0.1.5.6e with Jumblr KMD BTC Anonymizer (Bitcoinmixer) – Download
Twitter : https://twitter.com/KomodoPlatform/status/844932024322404352
Reddit : https://www.reddit.com/r/komodoplatform/comments/612i0a/mandatory_update_agama_multicoin_wallet_v0156e/
Facebook : https://www.facebook.com/KomodoPlatform/photos/a.330322533980991.1073741828.321638648182713/428592014154042/?type=3&theater
News SuperNET : http://news.supernet.org/posts/xAgWNyKoDuMd27727/mandatory-update-agama-multicoin-wallet-v0-1-5-6e-with
Reddit : https://www.reddit.com/r/komodoplatform/comments/612i0a/mandatory_update_agama_multicoin_wallet_v0156e/
Facebook : https://www.facebook.com/KomodoPlatform/photos/a.330322533980991.1073741828.321638648182713/428592014154042/?type=3&theater
News SuperNET : http://news.supernet.org/posts/xAgWNyKoDuMd27727/mandatory-update-agama-multicoin-wallet-v0-1-5-6e-with
It is Linux and OS, not still for windows?
March 23, 2017, 10:28:45 AM
AikaPool is work!
https://aikapool.com/kmd
BlockExplorer not work! Last block 2 hours ago! - https://kpx.io/
https://aikapool.com/kmd
BlockExplorer not work! Last block 2 hours ago! - https://kpx.io/
March 23, 2017, 10:23:32 AM
Mandatory Update: Agama #Multicoin Wallet v0.1.5.6e with Jumblr KMD BTC Anonymizer (Bitcoinmixer) – Download
Twitter : https://twitter.com/KomodoPlatform/status/844932024322404352
Reddit : https://www.reddit.com/r/komodoplatform/comments/612i0a/mandatory_update_agama_multicoin_wallet_v0156e/
Facebook : https://www.facebook.com/KomodoPlatform/photos/a.330322533980991.1073741828.321638648182713/428592014154042/?type=3&theater
News SuperNET : http://news.supernet.org/posts/xAgWNyKoDuMd27727/mandatory-update-agama-multicoin-wallet-v0-1-5-6e-with
Reddit : https://www.reddit.com/r/komodoplatform/comments/612i0a/mandatory_update_agama_multicoin_wallet_v0156e/
Facebook : https://www.facebook.com/KomodoPlatform/photos/a.330322533980991.1073741828.321638648182713/428592014154042/?type=3&theater
News SuperNET : http://news.supernet.org/posts/xAgWNyKoDuMd27727/mandatory-update-agama-multicoin-wallet-v0-1-5-6e-with
March 23, 2017, 08:20:07 AM
Mainchain has now advanced hundreds of blocks and the fork event is behind us.
Wasnt that fun!
For basilisk users, in the next hours it should start performing better and better, but please be patient if it is slow or you cant see your balance. check on kpx.io and if your funds are there, your coins are safe. basilisk mode is a convenience way to access your coins.
For those that require constant, continual and always accessible relations with your KMD, then I strongly suggest that you run native mode. That is simply the only way to achieve this. To expect a little basilisk to do what a komodo does... Just not realistic.
For the people who are running a native komodod, you will need to update to the post-hardfork version. GUIs are being built right now, please dont ask me when they will be released, I plan to get some rest soon. If you ended up sending transactions during the last day and the txid does not appear on kpx.io, but your wallet says it is spent, then it could be that you need to rescan your wallet to get things back in sync.
Of course the first thing to do is get back in sync, then do the wallet rescan if some tx are missing.
KMD has a new feature by the way. Part of the fix required was to make mempool transactions expire after an hour. Since KMD has 1 minute blocktimes and the blocks are far from full, I dont expect this to be an issue any time soon. If in some years it becomes an issue and for whatever reason the blocksize isnt just increased in size, please refer them to this post where I say, "just increase the blocksize to handle the transaction load!!"
With a one hour expiration time, that means if it isnt confirmed after an hour, it is invalid and you dont have to worry that it comes back and unexpectedly spends the inputs. So even if KMD mempool does ever grow to a backlog, the longest you have to wait wondering whether it will be confirmed or no, is one hour.
Wasnt that fun!
For basilisk users, in the next hours it should start performing better and better, but please be patient if it is slow or you cant see your balance. check on kpx.io and if your funds are there, your coins are safe. basilisk mode is a convenience way to access your coins.
For those that require constant, continual and always accessible relations with your KMD, then I strongly suggest that you run native mode. That is simply the only way to achieve this. To expect a little basilisk to do what a komodo does... Just not realistic.
For the people who are running a native komodod, you will need to update to the post-hardfork version. GUIs are being built right now, please dont ask me when they will be released, I plan to get some rest soon. If you ended up sending transactions during the last day and the txid does not appear on kpx.io, but your wallet says it is spent, then it could be that you need to rescan your wallet to get things back in sync.
Of course the first thing to do is get back in sync, then do the wallet rescan if some tx are missing.
KMD has a new feature by the way. Part of the fix required was to make mempool transactions expire after an hour. Since KMD has 1 minute blocktimes and the blocks are far from full, I dont expect this to be an issue any time soon. If in some years it becomes an issue and for whatever reason the blocksize isnt just increased in size, please refer them to this post where I say, "just increase the blocksize to handle the transaction load!!"
With a one hour expiration time, that means if it isnt confirmed after an hour, it is invalid and you dont have to worry that it comes back and unexpectedly spends the inputs. So even if KMD mempool does ever grow to a backlog, the longest you have to wait wondering whether it will be confirmed or no, is one hour.
March 23, 2017, 07:24:19 AM
Wallet of last version...
you are on the right chain, it is rejecting the invalid blocks.Code:
2017-03-23 11:14:39 UpdateTip: new best=030a219fffd4c021aefd38aa9fc0b6acc756009cab64c03ff276401c67e4e7c6 height=246745 log2_work=45.798086 tx=298786 date=2017-03-22 05:03:05 progress=0.975281 cache=8.7M
iB(35731tx)
2017-03-23 11:14:39 UpdateTip: new best=0e2b582e659f88eea868ce9bdf3e55c259ba4d2393fdc481b5b53d53754ba0cc height=246746 log2_work=45.798086 tx=298788 date=2017-03-22 05:04:04 progress=0.975294 cache=8.7M
iB(35732tx)
2017-03-23 11:14:39 UpdateTip: new best=000000772efd452a280771771d8d51ed89dc1818dec5a911cc0c23212aace50a height=246747 log2_work=45.798087 tx=298791 date=2017-03-22 05:05:59 progress=0.975320 cache=8.7M
iB(35733tx)
2017-03-23 11:14:39 UpdateTip: new best=0000398fec970c5db676d476d32b479c6308a56525f70e77f9ab3b03f1280a72 height=246748 log2_work=45.798087 tx=298794 date=2017-03-22 05:06:11 progress=0.975323 cache=8.7M
iB(35734tx)
2017-03-23 11:14:39 ERROR: CheckBlock: komodo_validate_interest failed
2017-03-23 11:14:39 ERROR: ConnectTip(): ConnectBlock 0000009b0532d029d58bd425370f005c09854d647a021a79bef5cc816e4ca86c failed
2017-03-23 11:14:39 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-03-23 11:14:39 ERROR: CheckBlock: komodo_validate_interest failed
2017-03-23 11:14:39 ERROR: ConnectTip(): ConnectBlock 0000009b0532d029d58bd425370f005c09854d647a021a79bef5cc816e4ca86c failed
2017-03-23 11:14:39 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-03-23 11:14:39 ERROR: CheckBlock: komodo_validate_interest failed
2017-03-23 11:14:39 ERROR: ConnectTip(): ConnectBlock 0000009b0532d029d58bd425370f005c09854d647a021a79bef5cc816e4ca86c failed
2017-03-23 11:14:39 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-03-23 11:14:39 ERROR: CheckBlock: komodo_validate_interest failed
2017-03-23 11:14:39 ERROR: ConnectTip(): ConnectBlock 0000009b0532d029d58bd425370f005c09854d647a021a79bef5cc816e4ca86c failed
2017-03-23 11:14:39 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-03-23 11:14:39 ERROR: CheckBlock: komodo_validate_interest failed
2017-03-23 11:14:39 ERROR: ConnectTip(): ConnectBlock 0000009b0532d029d58bd425370f005c09854d647a021a79bef5cc816e4ca86c failed
2017-03-23 11:14:39 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-03-23 11:14:39 ERROR: CheckBlock: komodo_validate_interest failed
2017-03-23 11:14:39 ERROR: ConnectTip(): ConnectBlock 0000009b0532d029d58bd425370f005c09854d647a021a79bef5cc816e4ca86c failed
2017-03-23 11:14:39 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-03-23 11:14:39 ERROR: CheckBlock: komodo_validate_interest failed
2017-03-23 11:14:39 ERROR: ConnectTip(): ConnectBlock 0000009b0532d029d58bd425370f005c09854d647a021a79bef5cc816e4ca86c failed
2017-03-23 11:14:39 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-03-23 11:14:39 ERROR: CheckBlock: komodo_validate_interest failed
2017-03-23 11:14:39 ERROR: ConnectTip(): ConnectBlock 0000009b0532d029d58bd425370f005c09854d647a021a79bef5cc816e4ca86c failed
2
i think you just need some recent peers.
kpx.io is almost current
http://www.zpool.ca/explorer/1720 is current to mainchain
try removing peers.dat and launching again, that should work. if not, try:
./komodod -addnode=78.47.196.146 &
Jump to: