Noobish question, but what is the difference between SuperNet and Komodo?
Are they linked to eachother somehow, do I need to own both if I want to invest myself in the project?
Topic: [ANN][KMD][dPoW] Komodo - An Open, Composable Smart Chain Platform, Secured by B - page 460. (Read 1192347 times)
April 17, 2017, 01:58:21 PM
April 17, 2017, 01:34:08 PM
any news on komodo getting on polo yet?
No plzz not yet! need to accumulate more coin!!!
April 17, 2017, 09:59:57 AM
any news on komodo getting on polo yet?
April 17, 2017, 09:07:37 AM
Last Friday, zcash disclosed a potential DOS attack vector that could remotely crash nodes. There has not been any attack and the patch to fix it was already released in the 1.8.0-1 release.
I have merged that patch, along with rebasing to the 1.8.0 release and this is now in the master branch. The notary nodes have updated and if you are running a mining pool or exchange it is a good idea to update over the coming days. As the bug causes a crash and it is not a consensus issue, if an attack materialized your node will crash, but it wont be able to do any damage other than that.
Granted it is an annoying thing, but no sense to disrupt normal operations for just this update.
So, update at your convenience. The next GUI update will have the 1.8.0-1 komodod in it.
Again, it is not a consensus issue, but a local node remote crash possibility. Since the notary nodes and some mining pools are already updated, you could just wait until your node crashes to update.
With all the attention given to this level of bug, it seems the zcash codebase is getting quite solid.
I have merged that patch, along with rebasing to the 1.8.0 release and this is now in the master branch. The notary nodes have updated and if you are running a mining pool or exchange it is a good idea to update over the coming days. As the bug causes a crash and it is not a consensus issue, if an attack materialized your node will crash, but it wont be able to do any damage other than that.
Granted it is an annoying thing, but no sense to disrupt normal operations for just this update.
So, update at your convenience. The next GUI update will have the 1.8.0-1 komodod in it.
Again, it is not a consensus issue, but a local node remote crash possibility. Since the notary nodes and some mining pools are already updated, you could just wait until your node crashes to update.
With all the attention given to this level of bug, it seems the zcash codebase is getting quite solid.
You are working hard and I can see your effort for all things running smoothly and I'm not wrong when I have bought 5k KMD with cheap price around 0,00012btc some days ago. now I can get a bit profit from this action but I want KMD to increase higher than 0.00025btc in next month.
If you want KMD price to go up, buy KMD. Tell your relatives to buy KMD. Tell you friends to buy KMD. And, after all that, buy some more KMD. That's how the price raises,
That would be nice so that his/her family can benefit kmd opportunities. Because sooner than later kmd will go to poloniex soon. And with or without you kmd will be more than 25,000 satohis. I am holding this in such a long time unless I need money or I felt the reward is more than enough.
April 17, 2017, 09:07:16 AM
hi - quick question - I am an old time holder of the Supernet/Unity asset - with the Komodo rollout, I am a little confused of the relationship between the two - is Unity still part of the equation? Is it still worth something? If so, if someone can explain why/how that would be extremely helpful. Thanks in advance and apologies for the cluelessness.
Nothing has changed, the asset will still get revenues from the Supernet services once they're active and people use them. The only difference is that the asset will be moved from Nxt to their own assetchain sometime this summer.
April 17, 2017, 09:01:03 AM
Last Friday, zcash disclosed a potential DOS attack vector that could remotely crash nodes. There has not been any attack and the patch to fix it was already released in the 1.8.0-1 release.
I have merged that patch, along with rebasing to the 1.8.0 release and this is now in the master branch. The notary nodes have updated and if you are running a mining pool or exchange it is a good idea to update over the coming days. As the bug causes a crash and it is not a consensus issue, if an attack materialized your node will crash, but it wont be able to do any damage other than that.
Granted it is an annoying thing, but no sense to disrupt normal operations for just this update.
So, update at your convenience. The next GUI update will have the 1.8.0-1 komodod in it.
Again, it is not a consensus issue, but a local node remote crash possibility. Since the notary nodes and some mining pools are already updated, you could just wait until your node crashes to update.
With all the attention given to this level of bug, it seems the zcash codebase is getting quite solid.
I have merged that patch, along with rebasing to the 1.8.0 release and this is now in the master branch. The notary nodes have updated and if you are running a mining pool or exchange it is a good idea to update over the coming days. As the bug causes a crash and it is not a consensus issue, if an attack materialized your node will crash, but it wont be able to do any damage other than that.
Granted it is an annoying thing, but no sense to disrupt normal operations for just this update.
So, update at your convenience. The next GUI update will have the 1.8.0-1 komodod in it.
Again, it is not a consensus issue, but a local node remote crash possibility. Since the notary nodes and some mining pools are already updated, you could just wait until your node crashes to update.
With all the attention given to this level of bug, it seems the zcash codebase is getting quite solid.
You are working hard and I can see your effort for all things running smoothly and I'm not wrong when I have bought 5k KMD with cheap price around 0,00012btc some days ago. now I can get a bit profit from this action but I want KMD to increase higher than 0.00025btc in next month.
If you want KMD price to go up, buy KMD. Tell your relatives to buy KMD. Tell you friends to buy KMD. And, after all that, buy some more KMD. That's how the price raises,
April 17, 2017, 08:55:25 AM
Last Friday, zcash disclosed a potential DOS attack vector that could remotely crash nodes. There has not been any attack and the patch to fix it was already released in the 1.8.0-1 release.
I have merged that patch, along with rebasing to the 1.8.0 release and this is now in the master branch. The notary nodes have updated and if you are running a mining pool or exchange it is a good idea to update over the coming days. As the bug causes a crash and it is not a consensus issue, if an attack materialized your node will crash, but it wont be able to do any damage other than that.
Granted it is an annoying thing, but no sense to disrupt normal operations for just this update.
So, update at your convenience. The next GUI update will have the 1.8.0-1 komodod in it.
Again, it is not a consensus issue, but a local node remote crash possibility. Since the notary nodes and some mining pools are already updated, you could just wait until your node crashes to update.
With all the attention given to this level of bug, it seems the zcash codebase is getting quite solid.
I have merged that patch, along with rebasing to the 1.8.0 release and this is now in the master branch. The notary nodes have updated and if you are running a mining pool or exchange it is a good idea to update over the coming days. As the bug causes a crash and it is not a consensus issue, if an attack materialized your node will crash, but it wont be able to do any damage other than that.
Granted it is an annoying thing, but no sense to disrupt normal operations for just this update.
So, update at your convenience. The next GUI update will have the 1.8.0-1 komodod in it.
Again, it is not a consensus issue, but a local node remote crash possibility. Since the notary nodes and some mining pools are already updated, you could just wait until your node crashes to update.
With all the attention given to this level of bug, it seems the zcash codebase is getting quite solid.
You are working hard and I can see your effort for all things running smoothly and I'm not wrong when I have bought 5k KMD with cheap price around 0,00012btc some days ago. now I can get a bit profit from this action but I want KMD to increase higher than 0.00025btc in next month.
April 17, 2017, 08:49:26 AM
hi - quick question - I am an old time holder of the Supernet/Unity asset - with the Komodo rollout, I am a little confused of the relationship between the two - is Unity still part of the equation? Is it still worth something? If so, if someone can explain why/how that would be extremely helpful. Thanks in advance and apologies for the cluelessness.
April 17, 2017, 07:30:46 AM
Last Friday, zcash disclosed a potential DOS attack vector that could remotely crash nodes. There has not been any attack and the patch to fix it was already released in the 1.8.0-1 release.
I have merged that patch, along with rebasing to the 1.8.0 release and this is now in the master branch. The notary nodes have updated and if you are running a mining pool or exchange it is a good idea to update over the coming days. As the bug causes a crash and it is not a consensus issue, if an attack materialized your node will crash, but it wont be able to do any damage other than that.
Granted it is an annoying thing, but no sense to disrupt normal operations for just this update.
So, update at your convenience. The next GUI update will have the 1.8.0-1 komodod in it.
Again, it is not a consensus issue, but a local node remote crash possibility. Since the notary nodes and some mining pools are already updated, you could just wait until your node crashes to update.
With all the attention given to this level of bug, it seems the zcash codebase is getting quite solid.
I have merged that patch, along with rebasing to the 1.8.0 release and this is now in the master branch. The notary nodes have updated and if you are running a mining pool or exchange it is a good idea to update over the coming days. As the bug causes a crash and it is not a consensus issue, if an attack materialized your node will crash, but it wont be able to do any damage other than that.
Granted it is an annoying thing, but no sense to disrupt normal operations for just this update.
So, update at your convenience. The next GUI update will have the 1.8.0-1 komodod in it.
Again, it is not a consensus issue, but a local node remote crash possibility. Since the notary nodes and some mining pools are already updated, you could just wait until your node crashes to update.
With all the attention given to this level of bug, it seems the zcash codebase is getting quite solid.
April 17, 2017, 07:22:13 AM
Hi, I was just wondering what DopW is and how does it work ?
Quote
In this whitepaper we discuss a completely new cryptocurrency consensus mechanism, that is as secure as the proof-of-work blockchain to which it attaches itself to (In this case: Bitcoin), but does not require computing power and energy to be wasted.
This system is called Delayed Proof of Work (dPoW) and is achieved by notarizing blocks created in the initial blockchain on the Bitcoin blockchain, ensuring that once the information is engraved on the Bitcoin blockchain, it would be required both blockchains in question to be compromised.
This system is called Delayed Proof of Work (dPoW) and is achieved by notarizing blocks created in the initial blockchain on the Bitcoin blockchain, ensuring that once the information is engraved on the Bitcoin blockchain, it would be required both blockchains in question to be compromised.
The above is the Abstract from this whitepaper https://supernet.org/en/technology/whitepapers/delayed-proof-of-work-dpow
April 17, 2017, 07:07:45 AM
Hi, I was just wondering what DopW is and how does it work ?
April 17, 2017, 06:52:57 AM
It's stuck at the `loading daemon'
You had this issue?
You had this issue?
Are you using the latest build?
https://github.com/SuperNETorg/Agama/releases
Also use the installer version and follow the upgrade instructions
Yes did all that and using agama. Just stuck at that window.
April 17, 2017, 06:32:59 AM
KMD making some nice price gains. Around 0.0015 now 
Someone suppressing price down and this looks like very long period of accumulation. You just don't need to be super smart to see what is going here. Better buy at those prices and wait for the big jump..My predictions are very closely 100k. 
April 17, 2017, 05:54:52 AM
KMD making some nice price gains. Around 0.0015 now
April 17, 2017, 03:25:26 AM
OH i had 1 older version, thanks for the link.
April 17, 2017, 03:21:13 AM
It's stuck at the `loading daemon'
You had this issue?
You had this issue?
Are you using the latest build?
https://github.com/SuperNETorg/Agama/releases
Also use the installer version and follow the upgrade instructions
April 17, 2017, 02:41:07 AM
When is the new wallet with no bugs being released. Still doesn't work on my windows 7 64 bit system which it should
Just keep closing the wallet and opening again until it works, it worked for me
It's stuck at the `loading daemon'
You had this issue?
what wallet you have? Iguana or Agama? I stopped using iguana and downloaded the new one which is agama. And yeah it had the same problem with me. I killed all processes related to Agama in the activity monitor in my mac and restarted the wallet until it got in.
April 16, 2017, 10:32:38 PM
When is the new wallet with no bugs being released. Still doesn't work on my windows 7 64 bit system which it should
Just keep closing the wallet and opening again until it works, it worked for me
It's stuck at the `loading daemon'
You had this issue?
April 16, 2017, 10:02:25 PM
When is the new wallet with no bugs being released. Still doesn't work on my windows 7 64 bit system which it should
Just keep closing the wallet and opening again until it works, it worked for me
April 16, 2017, 09:44:23 PM
When is the new wallet with no bugs being released. Still doesn't work on my windows 7 64 bit system which it should
Jump to: