Author

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

newbie
Activity: 41
Merit: 0
JL or others, can you please explain where the UNITY (nxt asset exchange) fits into all this?  what will become of it? 
full member
Activity: 476
Merit: 133
I get this error while compiling komodo from master branch.


https://z.cash/depends-sources/libsnark-3854b20c25e8bc567aab2b558dec84d45f4a3e73.tar.gz:
2017-10-13 05:46:16 ERROR 404: Not Found.
https://supernetorg.bintray.com/misc//libsnark-3854b20c25e8bc567aab2b558dec84d45f4a3e73.tar.gz:
2017-10-13 05:46:16 ERROR 403: Forbidden.


As z.cash server doesn't host libsnark files any more, you should prepare it for Komodo.
Are you using jl777 or supernetorg repo?

jl777 repo.
try again
full member
Activity: 476
Merit: 133

from the readme:

We have a release process that goes through several stages before it reaches master. This allows the most conservative users just use the master branch, which is only updated after the other branches have signed off on a release.

99% of the activity is in the dev branch, this is where I am testing each change one by one and there are literally thousands of updates. Only use this branch if you really want to be on the bleeding edge. I try to keep things stable, but there are times where necessarily there are bugs in the dev branch, since I am actively developing and debugging here. A good rule is to wait for at least 4 hours from the last update before using the dev branch (unless you know what you are doing)

After things look good in the dev branch, it is propagated to the beta branch, this is the version the notary nodes use. They are knowledegable command line server guys and so they have a keen eye for anything that wasnt caught during the dev cycle.

After the notary nodes verify things are working and the latest release is deemed stable, it is propagated to the dPoW branch. From here an automated Jenkins process builds it for all OS, and since the notary nodes are all unix, it is possible for some issues to be caught at this stage. The dPoW branch is what goes into the GUI installers.

After the GUI are updated and released and it is verified that no significant support issues were created, the master branch is finally updated.

Master branch: exchanges and users that build from the repo without changing branches
dPoW branch: autobuild into GUI installers, unix, osx, windows
beta branch: notary nodes, command line unix
dev branch: bleeding edge, possibly wont even compile, multiple updates per hour



Thanks for detailed explanation.

Can you make tag and release binaries time to time? So that we can communicate with version number if there's some bug in it.

I mostly think that official stable version should be released.
Current latest release date was on 9 Sep, 2016. I think it's too old.
master branch was updated 23 days ago, I dont think that it's too old (just updated to fix build issue)
dPoW branch was updated 4 days ago
beta branch was updated 4 days ago
dev branch was updated 12 hours ago

each git commit has a hash, you can always report a bug against a specific commit hash.

exactly what bug do you want to report? Or is it a theoretical need to be able to refer to some version number in case you find a bug? If so, just use the github hash, why to spend time to manually tag things when git does it automatically?

The release process above is made so you can pull from master and get a stable release. Is it not stable? Did you find a bug in master branch?
legendary
Activity: 1456
Merit: 1006
Mining Pool Hub
I get this error while compiling komodo from master branch.


https://z.cash/depends-sources/libsnark-3854b20c25e8bc567aab2b558dec84d45f4a3e73.tar.gz:
2017-10-13 05:46:16 ERROR 404: Not Found.
https://supernetorg.bintray.com/misc//libsnark-3854b20c25e8bc567aab2b558dec84d45f4a3e73.tar.gz:
2017-10-13 05:46:16 ERROR 403: Forbidden.


As z.cash server doesn't host libsnark files any more, you should prepare it for Komodo.
Are you using jl777 or supernetorg repo?

jl777 repo.
sr. member
Activity: 466
Merit: 253
Imagine a world without banks.......
I get this error while compiling komodo from master branch.


https://z.cash/depends-sources/libsnark-3854b20c25e8bc567aab2b558dec84d45f4a3e73.tar.gz:
2017-10-13 05:46:16 ERROR 404: Not Found.
https://supernetorg.bintray.com/misc//libsnark-3854b20c25e8bc567aab2b558dec84d45f4a3e73.tar.gz:
2017-10-13 05:46:16 ERROR 403: Forbidden.


As z.cash server doesn't host libsnark files any more, you should prepare it for Komodo.
Are you using jl777 or supernetorg repo?
legendary
Activity: 1456
Merit: 1006
Mining Pool Hub
I get this error while compiling komodo from master branch.


https://z.cash/depends-sources/libsnark-3854b20c25e8bc567aab2b558dec84d45f4a3e73.tar.gz:
2017-10-13 05:46:16 ERROR 404: Not Found.
https://supernetorg.bintray.com/misc//libsnark-3854b20c25e8bc567aab2b558dec84d45f4a3e73.tar.gz:
2017-10-13 05:46:16 ERROR 403: Forbidden.


As z.cash server doesn't host libsnark files any more, you should prepare it for Komodo.
legendary
Activity: 1456
Merit: 1006
Mining Pool Hub

from the readme:

We have a release process that goes through several stages before it reaches master. This allows the most conservative users just use the master branch, which is only updated after the other branches have signed off on a release.

99% of the activity is in the dev branch, this is where I am testing each change one by one and there are literally thousands of updates. Only use this branch if you really want to be on the bleeding edge. I try to keep things stable, but there are times where necessarily there are bugs in the dev branch, since I am actively developing and debugging here. A good rule is to wait for at least 4 hours from the last update before using the dev branch (unless you know what you are doing)

After things look good in the dev branch, it is propagated to the beta branch, this is the version the notary nodes use. They are knowledegable command line server guys and so they have a keen eye for anything that wasnt caught during the dev cycle.

After the notary nodes verify things are working and the latest release is deemed stable, it is propagated to the dPoW branch. From here an automated Jenkins process builds it for all OS, and since the notary nodes are all unix, it is possible for some issues to be caught at this stage. The dPoW branch is what goes into the GUI installers.

After the GUI are updated and released and it is verified that no significant support issues were created, the master branch is finally updated.

Master branch: exchanges and users that build from the repo without changing branches
dPoW branch: autobuild into GUI installers, unix, osx, windows
beta branch: notary nodes, command line unix
dev branch: bleeding edge, possibly wont even compile, multiple updates per hour



Thanks for detailed explanation.

Can you make tag and release binaries time to time? So that we can communicate with version number if there's some bug in it.

I mostly think that official stable version should be released.
Current latest release date was on 9 Sep, 2016. I think it's too old.
full member
Activity: 225
Merit: 100
I am no expert when speaking of bitcoin, but I have been watching the value and evolution since just a few years after it was started. the recent bizarre events regarding bitcoin have caused me to summarize a brief statement, here follows. just now I am looking at coinmarketcap and they are showing btc at $5500 .. some short time ago the coins were $400. I have a theory about what happened to it because it started to seem absurd just after the $400 point (in my opinion). bitcoin was bought (everyone has seen the so called 'whales') well, a substantial portion of bitcoin was bought, by the same entity that would seek to control it, obviously. if having bought a significant portion of the total available supply then one can set the price at any moment. we all know this but who has considered that a very significant portion of the bitcoin network (just like the mining) is owned by very few entities (if not a single entity/corporation/whatnot). it is not out of the question at all to consider such a move as this would be common strategy for anyone (anything) with enough wealth wishing to purchase the controlling power of the network. when the price was set to 10X over the years following, there is no room for loss, because all of the earnings were made back since the price increase. the remaining portion of the coins could be dispensed at whatever cost.. now at the most absurd time the coins have gained so much value in 2 days? yeah right. I may be mistaken but it seems that any sane person would probably panic sell considering the severity and relevance of the proposed blockchain split. yet the price just keeps going up.. ? seems like sabotage to me. anyway, thats my 2 cents.

why I am posting this in the komodo thread? really I guess just to share a perspective but also and more importantly to make those who are holding aware that bitcoin is not the king and it will not be the king because it is most likely controlled by a single entity. just an encouragement for komodo as it seems obvious to me that komodo has the potential to rise to the top.
hero member
Activity: 1022
Merit: 504
GoMeat - Digitalizing Meat Stores - ICO
Excited for the swap in a few days... and getting my wallet going again.

Currently... Komodo Swing Wallet

komodoOSX - Version 1.0.0 (0.8.0)

"please wait - daemon takes longer to start"

Is this normal for over half a day?




I have been using Komodo Swing Wallet and yes it loads almost 4-5 hours . Hope devs are doing some kind of improvement. Agama wallet is not as reliable as Swing so I am still confident of using the Swing wallet.
member
Activity: 63
Merit: 10
any master or push plan for 2018? i like this coin but no realy trust invest to it.
member
Activity: 109
Merit: 10
Excited for the swap in a few days... and getting my wallet going again.

Currently... Komodo Swing Wallet

komodoOSX - Version 1.0.0 (0.8.0)

"please wait - daemon takes longer to start"

Is this normal for over half a day?

sr. member
Activity: 391
Merit: 250
I'm sure everybody of the team will be super happy that everything is over on the 16th :')

Then we'll have a few people jumping up and down crying because they failed to convert the BTCD despite having a full year to do it.

You just know its coming.

I would have no sympathy for these people and kindly ask them to stop investing in crypto altogether.  No other team goes to such great lengths to maintain the swap for this long.

To help jl777 out, I'll try to repeat the dates with every post I make from now on.

Next payout is Oct. 15
Last payout is Jan. 15

Don't procrastinate or you will really piss jl777 off!
member
Activity: 115
Merit: 11
https://dexstats.info
I'm sure everybody of the team will be super happy that everything is over on the 16th :')

Then we'll have a few people jumping up and down crying because they failed to convert the BTCD despite having a full year to do it.

You just know its coming.

Are there also accounts which have ICO KMD and not requested payout yet? If so an email reminder could be a good idea to avoid a few angry guys.
legendary
Activity: 2254
Merit: 1043
I'm sure everybody of the team will be super happy that everything is over on the 16th :')

Then we'll have a few people jumping up and down crying because they failed to convert the BTCD despite having a full year to do it.

You just know its coming.
sr. member
Activity: 399
Merit: 251
second to last payout will be in 3 days
please do not complain if you miss the deadline, it is repeated many times as October 15th

after this payout, there will only be the LAST payout on January 15th. Constantly maintaining the ICO site has taken a fair amount of time, but we said we would keep it open for a year, so we will.

However, it is time for us to move to the next set of things to do, instead of maintaining an ICO site for an ICO that has been completed for almost a year.

I STRONGLY suggest you do a payout before this payout. Dont procrastinate until the final payout.

i want to swap all my btcd this month, i must wait until january 15th ??!
now i have a pending payout over 1 month and i can't do another one to swap now all my btcd ?!

No, he said do BEFORE Jan 15th...

I'm sure everybody of the team will be super happy that everything is over on the 16th :')
sr. member
Activity: 1078
Merit: 310
AKA RJF - Member since '13
second to last payout will be in 3 days
please do not complain if you miss the deadline, it is repeated many times as October 15th

after this payout, there will only be the LAST payout on January 15th. Constantly maintaining the ICO site has taken a fair amount of time, but we said we would keep it open for a year, so we will.

However, it is time for us to move to the next set of things to do, instead of maintaining an ICO site for an ICO that has been completed for almost a year.

I STRONGLY suggest you do a payout before this payout. Dont procrastinate until the final payout.

i want to swap all my btcd this month, i must wait until january 15th ??!
now i have a pending payout over 1 month and i can't do another one to swap now all my btcd ?!

No, he said do BEFORE Jan 15th...
full member
Activity: 476
Merit: 133
second to last payout will be in 3 days
please do not complain if you miss the deadline, it is repeated many times as October 15th

after this payout, there will only be the LAST payout on January 15th. Constantly maintaining the ICO site has taken a fair amount of time, but we said we would keep it open for a year, so we will.

However, it is time for us to move to the next set of things to do, instead of maintaining an ICO site for an ICO that has been completed for almost a year.

I STRONGLY suggest you do a payout before this payout. Dont procrastinate until the final payout.

i want to swap all my btcd this month, i must wait until january 15th ??!
now i have a pending payout over 1 month and i can't do another one to swap now all my btcd ?!
maybe there is time to contact @vanbreuk to cancel the existing request and make a new one
newbie
Activity: 36
Merit: 0
second to last payout will be in 3 days
please do not complain if you miss the deadline, it is repeated many times as October 15th

after this payout, there will only be the LAST payout on January 15th. Constantly maintaining the ICO site has taken a fair amount of time, but we said we would keep it open for a year, so we will.

However, it is time for us to move to the next set of things to do, instead of maintaining an ICO site for an ICO that has been completed for almost a year.

I STRONGLY suggest you do a payout before this payout. Dont procrastinate until the final payout.

i want to swap all my btcd this month, i must wait until january 15th ??!
now i have a pending payout over 1 month and i can't do another one to swap now all my btcd ?!
full member
Activity: 476
Merit: 133
second to last payout will be in 3 days
please do not complain if you miss the deadline, it is repeated many times as October 15th

after this payout, there will only be the LAST payout on January 15th. Constantly maintaining the ICO site has taken a fair amount of time, but we said we would keep it open for a year, so we will.

However, it is time for us to move to the next set of things to do, instead of maintaining an ICO site for an ICO that has been completed for almost a year.

I STRONGLY suggest you do a payout before this payout. Dont procrastinate until the final payout.
member
Activity: 109
Merit: 10
Swing wallet is slow but reliable wallet as of the moment for me . It doesn't matter if it loads almost 4 hours before the qt interface would show up and download the remaining blockchain transanctions to sync. As long as I regularly collecting the interest and be able to send or receive KMD.

Your definitely a "Hero member"


Thank YOU!

Jump to: