linux up..
does the current DS master compile? there was some revert sometime ago..
I just reverted back as a lot of code was committed that needed a rollback. Clone now and you should be ok. However, I have changes I need to implement such as addrman changes, net changes, header re-ordering and a fair few other bits  compiled, crash reason: segmentation fault my setup wrong...? ubuntu 15.10 64bit btw. before revert. there was some misspells in the code, (script folder) edit: i was using git before: "Revert to to RPC and a lot more" Bear with me. I've rolled back and now working my way back through the commits. Im fixing and committing  trying now the latest git. not so sure if my linux build is correct, not tested with any other coin. after i get this done i will setup mxe to make win wallet. (amir! i may need your help with mxe..) now using:Revert to working state edit: success client running, downloading blocks now its time to seek exploits glad to see my build setup is valid ps. check out for null pointers. (still want this to work with mingw..) and main.cpp has little part of c++11 |
|
|
|
linux up..
does the current DS master compile? there was some revert sometime ago..
I just reverted back as a lot of code was committed that needed a rollback. Clone now and you should be ok. However, I have changes I need to implement such as addrman changes, net changes, header re-ordering and a fair few other bits compiled, crash reason: segmentation fault my setup wrong...? ubuntu 15.10 64bit btw. before revert. there was some misspells in the code, (script folder) edit: i was using git before: "Revert to to RPC and a lot more" |
|
|
|
|
linux up..
does the current DS master compile? there was some revert sometime ago..
|
|
|
|
|
lets try this with linux while windows is stuck as gummy..
|
|
|
|
|
1) Are there any possible attack vectors in DarkSilk that have not been patched?
one point generaly about pow/pos hybrids, pos gives you extra security to so called 30-50 attacks.
currently btc is constantly under a attack. some pools use custom software where they ignore last block submited by network(for sometime). if they can generate two blocks in a row their chain will be longest and valid. then this earlier found&ignored block ends upto be an orphan.
that can be totally be eliminated with pos/pow ratio, depens what rules dev wants to be the final ones.
i think the point is that there would never be a need to do a hardfork.
|
|
|
|
not to make too long, clear start.
about block download.
would it be too easy to have effective p2p like torrentz, make a fast buffer file for chain, and then same time load it.
current hd first just did not make btc dl any better.
every time i use my btc wallet, wait a day or two for synch, that sucks.
Because of Stormnodes and their incentivisation, we will be developing headless wallets after the DarkSilk Core is released. that is a one way, a short cut for many users. just opened my btc wallet, wow i have somehow empty chain, lets wait a week.. using the:Latest "stable" version of Bitcoin Core: 0.11.2 |
|
|
|
|
not to make too long, clear start.
about block download.
would it be too easy to have effective p2p like torrentz, make a fast buffer file for chain, and then same time load it.
current hd first just did not make btc dl any better.
every time i use my btc wallet, wait a day or two for synch, that sucks.
|
|
|
|
code got some new blood into it.. looking way better again.
but, "DarkSilk should take a maximum of 4-6 weeks to be finalised"
i think it can take more time..
What makes you say that Cisa? after the base code and rules done: optimization of the final code..etc that will take time and more people needed to see all the points of view from other os than linux. of course it can be done after first release, maybe it is the way to go. code has many parts(mostly argon source is not optimal) that could be changed to drop out some build deps needed. Argon2d branch is by no means final. We have Wolf looking over the code and Amir is adding this to the wallet. We need to add chainactive and then the rest of the list posted on the last page. The hashes of the Stormnodes will be switched to the Argon2d PoW hash and the PoS blocks will be using Blake2B. Travis is also needed and some other bits for building. Then we test. We have multiple devs on all OS's, including yourself good. gcc calls to emmintrin are causing me headache.. also the official argon branch is still having updates Can always pull request fixes for building on your platform you know how lazy i am according that. just a feeling, darksilkgui has some part eating cpu.. Overprinting to debug and CPU usage are on the list. Those are in fact the last two jobs before and during the UI which is the last job. EDIT: Last job, lol that never ends, it is a infinity loop to make a good one. imagine all the work, time and number of peoples behind current btc code, and now btc is making suicide because minor things, worst one is too late and missing consensus to blocksize. |
|
|
|
code got some new blood into it.. looking way better again.
but, "DarkSilk should take a maximum of 4-6 weeks to be finalised"
i think it can take more time..
What makes you say that Cisa? after the base code and rules done: optimization of the final code..etc that will take time and more people needed to see all the points of view from other os than linux. of course it can be done after first release, maybe it is the way to go. code has many parts(mostly argon source is not optimal) that could be changed to drop out some build deps needed. Argon2d branch is by no means final. We have Wolf looking over the code and Amir is adding this to the wallet. We need to add chainactive and then the rest of the list posted on the last page. The hashes of the Stormnodes will be switched to the Argon2d PoW hash and the PoS blocks will be using Blake2B. Travis is also needed and some other bits for building. Then we test. We have multiple devs on all OS's, including yourself good. gcc calls to emmintrin are causing me headache.. also the official argon branch is still having updates Can always pull request fixes for building on your platform you know how lazy i am according that. just a feeling, darksilkgui has some part eating cpu.. |
|
|
|
code got some new blood into it.. looking way better again.
but, "DarkSilk should take a maximum of 4-6 weeks to be finalised"
i think it can take more time..
What makes you say that Cisa? after the base code and rules done: optimization of the final code..etc that will take time and more people needed to see all the points of view from other os than linux. of course it can be done after first release, maybe it is the way to go. code has many parts(mostly argon source is not optimal) that could be changed to drop out some build deps needed. Argon2d branch is by no means final. We have Wolf looking over the code and Amir is adding this to the wallet. We need to add chainactive and then the rest of the list posted on the last page. The hashes of the Stormnodes will be switched to the Argon2d PoW hash and the PoS blocks will be using Blake2B. Travis is also needed and some other bits for building. Then we test. We have multiple devs on all OS's, including yourself good. gcc calls to emmintrin are causing me headache.. also the official argon branch is still having updates |
|
|
|
code got some new blood into it.. looking way better again.
but, "DarkSilk should take a maximum of 4-6 weeks to be finalised"
i think it can take more time..
What makes you say that Cisa? after the base code and rules done: optimization of the final code..etc that will take time and more people needed to see all the points of view from other os than linux. of course it can be done after first release, maybe it is the way to go. code has many parts(mostly argon source is not optimal) that could be changed to drop out some build deps needed. |
|
|
|
|
code got some new blood into it.. looking way better again.
but, "DarkSilk should take a maximum of 4-6 weeks to be finalised"
i think it can take more time..
|
|
|
|
hey need help to build the wallet and the miner on linux! tryed this: git clone https://github.com/Encel-US/Argon2.gitcd Argon2/src/ make -f makefile.unix getting this errors: if i use make USE_UPNP=- -f makefile.unix DEFS += -DSTATICLIB -DUSE_UPNP=$(USE_UPNP) if still not working update source code, or use older upnp. source code is out dated according upnp. add new rules to net.cpp if you want it uptodate |
|
|
|
|
happy i did not waste any of my idle cpu time into this one.
it crossed my mind but there where bad sings in the air..
|
|
|
|
about the cpu mining..
sounds good and easy way for new users.
but we have seen how botnets will crash those coins in no time.
also there is lot of people who have acces to datacenters and other bigger pc groups.
cpu mining is a good way to use to instamine a coin like darkcoin did.
relesease the algo but not the gpu miner, 2 million darkcoins instamined in one day..
and one part of that was so called bug in the code.. that was planned to happen.
and there are still big rigs out there and it is sure that rental power will come around if the coin kicks out.
Yes. We thought about this long and hard on many levels. We are attempting to make this coin as fair as possible. In terms of release, mining, distribution and use. Thank you Cisa for making these points. I am keeping a neutral stance on Darkcoin and the instamine, but yes Argon2d and the fact we are releasing miners and the UNOMP module eliminates that issue. One good reason why I've never made a coin and don't plan to - that kind of diplomatic bullshit. I do wonder what he actually thinks about that, though. a man who could do another evil pharma coin or extremely fair coin to mine. guess i told that to you ages ago.. i agree with this diplomatic thing.. and all the promotion needed.. those are not neither in my interest. let the right guys handle those.. just got the latest git compiled for win.. and testing.. ProcessBlock: ORPHAN BLOCK 1, prev=083e9d9651532df339fa2952ed8be5030143c36573c2125de89eb5931315ebfd ERROR: AcceptBlock() : reject proof-of-work at height 1 ERROR: ProcessBlock() : AcceptBlock FAILED shall we have new chain.. |
|
|
|
|
about the cpu mining..
sounds good and easy way for new users.
but we have seen how botnets will crash those coins in no time.
also there is lot of people who have acces to datacenters and other bigger pc groups.
cpu mining is a good way to use to instamine a coin like darkcoin did.
relesease the algo but not the gpu miner, 2 million darkcoins instamined in one day..
and one part of that was so called bug in the code.. that was planned to happen.
and there are still big rigs out there and it is sure that rental power will come around if the coin kicks out.
|
|
|
|
Can the public know how many devs this coin has? It seems someone enters this coin every now and then. I would like to read more about the weaver, where can I find some more info? Why don't you have an internet site for god's sake  4 developers, full time - Spencer Lievens, Matthew Langdon, Amir Abrams, Gregory Betz (in order of joining) 1 developer, work hand-in-hand - Alistair Clark a.k.a Infernoman i.e. Transfercoin 2 freelancers, whenever needed - Sakr (Mobile Applications) and Wolf0 (Algorithms/Programming) current git ignored, no tx yet. and master issues still there. i have my own working one, but i dont want to mess up your development. conf rule.. fix it. so i am waiting you guys to get this UP! and BIG.. ps. orphan rules are outdated and stalled rules has to time to correct. still the best coin i have ever seen, ( when it is ready) Thank you Cisa, if only the non-code literate could realise the depth and technicality of DarkSilk  if people could read the code.. they would see this will outdate btc ,dash and all the pos coins. but there is still road to move on.. |
|
|
|
Can the public know how many devs this coin has? It seems someone enters this coin every now and then. I would like to read more about the weaver, where can I find some more info? Why don't you have an internet site for god's sake 4 developers, full time - Spencer Lievens, Matthew Langdon, Amir Abrams, Gregory Betz (in order of joining) 1 developer, work hand-in-hand - Alistair Clark a.k.a Infernoman i.e. Transfercoin 2 freelancers, whenever needed - Sakr (Mobile Applications) and Wolf0 (Algorithms/Programming) current git ignored, no tx yet. and master issues still there. i have my own working one, but i dont want to mess up your development. conf rule.. fix it. so i am waiting you guys to get this UP! and BIG.. ps. orphan rules are outdated and stalled rules has to time to correct. still the best coin i have ever seen, ( when it is ready) |
|
|
|
Any chances of having SHA256 or Scrypt mining algorithm? I don't do GPU/CPU at all
Sorry no. Argon2d will be the PoW mining algorithm and Blake2B will be the PoS algorithm. good selections! how did you end up to those? waiting to see gpu vs cpu results.. I recommended them to him. really? you are one of the bests!!! |
|
|
|
|
Show Posts
