darkcoind does not denominate etc. unless told to.That's amazing!!. A lot if hard work has gone into this.
One other question. How are exchanges going to handle dark given it now mixes?
darkcoind does not denominate etc. unless told to.That's amazing!!. A lot if hard work has gone into this.
One other question. How are exchanges going to handle dark given it now mixes?
Well spotted, have not run it through a spell checker - if you find more please PMGreat notes, just my inner grammar nazi kicks in: participants not partisipants :tongue:
P.S: Sorry :sad:
Can any who's gotten charged collateral send me their debug log and the txid? Thanks
You need to put "& disown" at the end of your command line. Without the quotesRunning wallet by command line (./darcoin-qt -testnet=1) and noticed that every time I open option dialog it writes "QMetaObject::connectSlotsByName: No matching signal for on_resetButton_clicked()" in console.
Thanks for that one! But doesn't this means that there is something wrong with that dialog itself too?You need to put "& disown" at the end of your command line. Without the quotes
You can ignore that warning.Running wallet by command line (./darcoin-qt -testnet=1) and noticed that every time I open option dialog it writes "QMetaObject::connectSlotsByName: No matching signal for on_resetButton_clicked()" in console.
Should work without.You need to put "& disown" at the end of your command line. Without the quotes
No.Thanks for that one! But doesn't this means that there is something wrong with that dialog itself too?
I really feel like to make a plea with Evan not to release RC4 today or tomorrow. We are so close to make DRK perfect. The market/supporters have been supporting and waiting this far, they can wait for a few more days. What do you guys think?
I don't know Evan or any of the devs but I find it highly unlikely that they will be releasing RC4 until they have done everything they possibly can to ensure stability. We're all in this together.
However...there are some issues IMHO that will not be found in testnet. There will be minor fixes after release. This has to be expected.
I haven't seen any official statements about release dates anyway.
i want to see a lot more than 24hrs bug free before it gets launched. Gotta be 110% working perfect. I'd like to see a solid week with absolutely zero issues on testnet.
However, no deal breakers appeared, AFAICT.At the time of the last update Evan mentioned "Monday or Tuesday", but I don't think he expected as many issues as were found in the last 24 hours.
****** Please Update To 10.12.20 or 9.12.20 *******
We should be good to go. Let us know if there's anything critical that still needs to be fixed before launch. Otherwise, I'll merge into master later on today.
- Disabled collateral charging for now. We'll work on this after RC4 is released and update the masternode network after it's working properly. It's not incredibly important at this stage (while we're closed source), so I don't want it holding up the release. Plus it's really the only issue we're experiencing
- Merged rebroad's (https://github.com/rebroad) changes to bring debugging output more in line with the bitcoin project. Output is now much cleaner and can be split by category.
- Removed some debug messages
- Merged mac/windows build icons
- Fixed windows "Apply" configuration bug
Stable Binaries
http://www.darkcoin.io/downloads/master-rc4/darkcoin-qt
http://www.darkcoin.io/downloads/master-rc4/darkcoind
RC4 Binaries ( masternodes / auto-denom )
http://www.darkcoin.io/downloads/rc4/darkcoin-qt
http://www.darkcoin.io/downloads/rc4/darkcoind
actually debug messages are now splited between standard output and debug.log: masternodes messages comes to stdout only and connection messages comes to debug.log onlygetting debug messages in the console with this update
edit: Evan, pretty sure this is critical. debug is coming to the standard output.