- Apr 8, 2014
- 1,953
- 1,315
- 1,283
Is this wallet ready to use for starting masternodes too or only for sending / receiving transactions?A nice, light-weight wallet, fast to sync, I love it. Thanks, vertoe and elbereth for the windows version!![]()
Is this wallet ready to use for starting masternodes too or only for sending / receiving transactions?A nice, light-weight wallet, fast to sync, I love it. Thanks, vertoe and elbereth for the windows version!![]()
The latter, full feature set will come with v0.10.18.xIs this wallet ready to use for starting masternodes too or only for sending / receiving transactions?
Ignore flare, he is in the wrong thread.The latter, full feature set will come with v0.10.18.x
It is the only wallet I can use to retrieve p2pool fees dust... The official one just freeze to hell.Oh and some disclaimer. Some of you are aware that I'm an official developer know. I want to highlight this is just a side project and I do not recommend using this software unless you know what you are doing and you have at least read and understood the README. Thanks.
Discussed this with flare today. We hope the darksend implementation in the new 0.11.x wallet will be a bit cleaner and show a better performance. We'll see.It is the only wallet I can use to retrieve p2pool fees dust... The official one just freeze to hell.
What was changed from previous version?Updated v0.9.17.24...
Look at the post above yours for the windows version.What was changed from previous version?
Any Windows version?
Thanks!
I guess this new version is to update the copyright comments and nothing else?Updated v0.9.17.24...
This wallet only gets version bumps and protocol updates. Currently there are no changes made on protocol level to the main client, thus all I have to do is to align the version numbers.What was changed from previous version?
Any Windows version?
Thanks!
Yes will drop the support soon for this version. It's hard to track upstream development after one year of nothing. The switch to v11 will improve a lot in terms of development, upstream updates and security fixes.(still using OpenSSL v1.0.1j)
I know. That's why I kept the previous OpenSSL version.Yes will drop the support soon for this version. It's hard to track upstream development after one year of nothing. The switch to v11 will improve a lot in terms of development, upstream updates and security fixes.
Thanks!https://github.com/vertoe/darkcoil/releases/tag/v0.9.18.9
darkcoil-0.9.18.9 alignes with darkcoin-core-0.11.0.9!
Please use this if you experience performance issues with v11 releases, but only if you read and understand the OP!
Do you have links to download for the Mac and Linux versions? Thanks.https://github.com/vertoe/darkcoil/releases/tag/v0.9.18.9
darkcoil-0.9.18.9 alignes with darkcoin-core-0.11.0.9!
Please use this if you experience performance issues with v11 releases, but only if you read and understand the OP!
Thanks again for this!darkcoil-0.9.18.9-win.zip
size: 12214955 bytes
sha256: b9d20634c57a636bf8532dad1bceda6f8b5f937f98f4b0239779cb63b065d5be
(still using OpenSSL v1.0.1j)
can you explain how to fix this? I just merged upstream and this is what I can find:(still using OpenSSL v1.0.1j)
Download the OpenSSL-archive (same link, just replace "h" with "j"), copy it to the input folder, change the references in the 3 *dep*.yml files from "h" to "j", and update the sha256sum with the one of the new OpenSSL-archive in those 3 files.can you explain how to fix this? I just merged upstream and this is what I can find:
only references to c, e and h but not j. what do I have to do to fix this?