Someone said I didn't reply to the exact points brought up. I hope this helps.
- Me and flare talk outside of Darkcointalk. The rc4 launch was not a hardfork and couldn't fail. Plus as the main developer, I have rollback plans already. Remember I rolled back RC2/RC3?
- Reduced scope? RC4 was a complete rewrite of Darksend. Release candidates aren't suppose to have new code unless it's absolutely necessary and the new way Darksend works was just too good not to implement it in. It was such a large ticket item that it shifted the entire release and it became impossible to test the voting system in the given time. Enforcement in any form is the most risky thing we can do and we have 80%+ payments currently. This isn't a high priority and can be done later. Why delay the entire launch of Darksend by a month or more just to gain 15-20% masternode payments? People were itching to have RC4 on mainnet and I knew it worked, so we launched.
- Flare isn't a programmer.
- Unknown? When upgrading an encrypted wallet from 100 to 1000 sized keypool, sometimes they became corrupted. This was only a problem between v28 and v31. Also it only affected one wallet. In v32 users are prompted to move funds to a new wallet if they're possibly at risk.
Someone said I didn't reply to the exact points brought up. I hope this helps.
- Me and flare talk outside of Darkcointalk. The rc4 launch was not a hardfork and couldn't fail. Plus as the main developer, I have rollback plans already. Remember I rolled back RC2/RC3?
- Reduced scope? RC4 was a complete rewrite of Darksend. Release candidates aren't suppose to have new code unless it's absolutely necessary and the new way Darksend works was just too good not to implement it in. It was such a large ticket item that it shifted the entire release and it became impossible to test the voting system in the given time. Enforcement in any form is the most risky thing we can do and we have 80%+ payments currently. This isn't a high priority and can be done later. Why delay the entire launch of Darksend by a month or more just to gain 15-20% masternode payments? People were itching to have RC4 on mainnet and I knew it worked, so we launched.
- Flare isn't a programmer.
- Unknown? When upgrading an encrypted wallet from 100 to 1000 sized keypool, sometimes they became corrupted. This was only a problem between v28 and v31. Also it only affected one wallet. In v32 users are prompted to move funds to a new wallet if they're possibly at risk.
Someone said I didn't reply to the exact points brought up. I hope this helps.
- Me and flare talk outside of Darkcointalk. The rc4 launch was not a hardfork and couldn't fail. Plus as the main developer, I have rollback plans already. Remember I rolled back RC2/RC3?
- Reduced scope? RC4 was a complete rewrite of Darksend. Release candidates aren't suppose to have new code unless it's absolutely necessary and the new way Darksend works was just too good not to implement it in. It was such a large ticket item that it shifted the entire release and it became impossible to test the voting system in the given time. Enforcement in any form is the most risky thing we can do and we have 80%+ payments currently. This isn't a high priority and can be done later. Why delay the entire launch of Darksend by a month or more just to gain 15-20% masternode payments? People were itching to have RC4 on mainnet and I knew it worked, so we launched.
- Flare isn't a programmer.
- Unknown? When upgrading an encrypted wallet from 100 to 1000 sized keypool, sometimes they became corrupted. This was only a problem between v28 and v31. Also it only affected one wallet. In v32 users are prompted to move funds to a new wallet if they're possibly at risk.
A couple more answers:
I'm going to kick older protocol versions off of the network with RC5. We should be able to get 90%+ because of this. This is also another reason enforcement isn't needed right now, I'd like to try this first.
I haven't heard for DRKLord in awhile, however I heard he's really ill. I'll reach out to him and made sure he's OK.
I wanted to put this out there to get the communities take on what Darkcoin should be in the future. I think there's a fork is the road for Darkcoin. I have a few different ideas for what masternodes could do. A few months ago when I came up with the idea of paying Masternodes I was thinking they could pretty much decentralize everything on the internet. That being said, it looks like other coins are already focusing on this.
As a result I don't believe we should do what others are doing. The thing I think we've really succeeded at is building an anonymity layer that's robust enough to provide nearly total anonymity while also not bloating the blockchain. I don't think there's much competition on that front and we have the brand for that service.
So we need to choose one of these options:
1.) We provide services and try to compete with centralized and next-gen decentralized providers. I think this hurts the anonymity brand by diluting what we're doing.
2.) We focus on providing a host of anonymity services using the Darksend implementation. This would mean my next project would be to rewrite electrum to use the masternodes to anonymize funds, then an android wallet that can use Darksend, then iPhone, etc. The foundation would also be tasked with trying to get businesses to accept Darkcoin and expand the user base.
I think I want to go with #2. It means that ALL users will have an out-of-the-box nearly perfect anonymous payment solution, which could be a big deal in the near term future.
Also, going with #2 would mean we abandon providing Darktor/Iris and similar services.
****** PLEASE UPDATE TO 9.13.0 OR 10.13.0 *******
Hello everyone!
Development has been going great and the last few things must be done on testnet.
RC5 includes these items so far:
- Darksend queue improvements : Matching should be much faster and more accurate
- Progress indication on creating a new wallet, shows up on the splash screen
- CLI help has been updated to show new commands
- Masternode payments reverted back to RC3 version (I'll do enforcement later after opensourcing)
- Collateral turned back on
- Darksend simple configuration screen on startup
- Darksend transaction filters
- When sending to yourself, n/a appeared instead of the address
- Large wallets wouldn't begin darksending
- New overview for Darksend info
Note: Let me know if you get a collateral payment. Please send me the debug.log and wallet.dat if you do to
evan@darkcoin.ioRC5 Binaries ( masternodes )
http://www.darkcoin.io/downloads/rc5/darkcoin-qthttp://www.darkcoin.io/downloads/rc5/darkcoindMpos + Stratum:
http://ec2-54-91-161-78.compute-1.amazonaws.com/index.php-- connection string: sgminer.exe -o stratum+tcp://54.91.161.78:3333 -u eduffield.1 -p x
Nomp :
http://54.183.73.24/How can you help?
1.) Point some hashing power at once of the pools!
2.) Run the "masternode-rc5" branch on testnet:
https://github.com/darkcoinproject/darkcoin/tree/master-rc53.) Run a masternode
4.) Anonymize some money (faucet :
https://drkipn.com/test/faucet/)
Thanks everyone,
The Darkcoin Team
PS: Can people send money to the faucet? mmfb6hxTdLT3gQGAEDr2g6Qug8ew2MwKoJ
BUMP
