v0.11.0 - Darkcoin Core Release

[tungfa]

No Mac Wallet Yet !
buhhhh ....>
:sad: :sad:

 

[weirdgod]

For start-many - are these the correct instructions (https://darkcointalk.org/threads/masternode-start-many-guide.2990/), od was there any update since?

Also - forum still says that latest version is 10.17.24 ...

 

[Lukas_Jackson]

What if I have spent all 0.1 1.0 10 denoms and only 100 left and I darksend 1 drk? Do I lose 99 drk change? Because change goes to miners.
I don't want to be that generous. Am I missing something?

Anybody is willing to answer? Only 100's denoms left in a wallet. What if I darksend few drk?

 

[thelonecrouton]

Anybody is willing to answer? Only 100's denoms left in a wallet. What if I darksend few drk?

You'll get your change, not miners.

 

[ourlink]

Will this version work with p2pool by changing the version number in the code?

Thanks!

Bump.... Anybody have an answer?

 

[Lukas_Jackson]

You'll get your change, not miners.

But I don't want to reveal any info. Simply I will have to mix them again.
So after shopping madness I will have to check coincontrol to see what size of denoms left

 

[thelonecrouton]

But I don't want to reveal any info. Simply I will have to mix them again.
So after shopping madness I will have to check coincontrol to see what size of denoms left

Yes, change needs to be remixed.

 

[thelonecrouton]

I've had 3 MNs just stop (daemon on server just quit, nothing odd in debug.log, no obvious signs in logs of RAM/CPU overuse) since updating to v11. They have all had to be restarted from the local wallet.

 

[thelonecrouton]

Local wallet got stuck after 7/8 rounds with two conflicting '!' txes, restarted with -zapwallettxes and now being hit with a string of charges and no DS progress:

 

[eduffield]

Local wallet got stuck after 7/8 rounds with two conflicting '!' txes, restarted with -zapwallettxes and now being hit with a string of charges and no DS progress:

Yikes, that's really weird.

 

[thelonecrouton]

Yikes, that's really weird.

Might just be bad luck. I left if for another hour and got a PTY 0.00 but it stayed stuck on 'Found unconfirmed... waiting...'

 

[Sub-Ether]

Local wallet got stuck after 7/8 rounds with two conflicting '!' txes, restarted with -zapwallettxes and now being hit with a string of charges and no DS progress:

On Win 7, I had 1 conflict tx stuck at 39%(for 16 hrs).Had saved a wallet from the start of version 11.0.6 before mixing and did the standard copy and paste thing, re ran same version and everything tickety boo now.

 

[camosoul]

I've had 3 MNs just stop (daemon on server just quit, nothing odd in debug.log, no obvious signs in logs of RAM/CPU overuse) since updating to v11. They have all had to be restarted from the local wallet.

I had the same problem on everything up to 0.11.0.4 - I skipped 0.11.0.5 - Have had this happen only one time since 0.11.0.6 and by pure coincidence, I was looking right at it when it happened. No output of any kind. I roll the command to execute like this in the same terminal so that any STDOUT or STDERR will hit the same screen session: ~/.darkcoin/darkcoind & tail -f ~/.darkcoin/debug.log - but nuthin'. No SEGFAULT, no stacktrace, just poof. The good news is that it is improved in it's occurrence by orders of magnitude in 0.11.0.6 - now over 40 nodes and it only happened once in 24 hours.

Evan suggested gdb to get some infos - this seems to stabilize them for some reason, and when using gdb, they won't freakin' crash anymore... I guess gdb is a workaround, lols. Doesn't get the info I'm looking for, but solves the crashing problem... [rolls eyes] It's like the problem knows I'm looking for it...

Can't offer anything on the DS issues... For the first time in months, I saw a successful denom. Not only that, but it denomed the whole stack in short order with no issues...

 

[crowning]

Just got a link to https://bitcointalk.org/index.php?topic=919373.0

According to deps-linux.yml we ARE building with Openssl-1.0.1k.

eduffield , shouldn't we temporarily use Openssl-1.0.1j ?

 

[xvpz-se]

Hi, first post here (but been into the dark for 8-9 months now).
Got a little bugreport:
Operating System: Windows 8.1 Home Ultimate 64bit
Issue: Random crashes in Wallet
Description: The wallet seems to randomly crash, the only thing I noticed during the last crash was that a block was created/found in the exactly same moment (was tailing logs).

Congrats to Dev team for a great release!

 

[DrkMiner]

Latest version is unresponsive and crashes often with "dust" transactions.

Windows 7 64 bit

Why can't we get the same performance as in Darkcoil wallet??

 

[oblox]

Latest version is unresponsive and crashes often with "dust" transactions.

Windows 7 64 bit

Why can't we get the same performance as in Darkcoil wallet??

Well, Darkcoil doesn't have DS (and masternode support iirc). Not sure where the optimizations lie.

 

[DrkMiner]

Well, Darkcoil doesn't have DS (and masternode support iirc). Not sure where the optimizations lie.

Problem is with very small payments from P2Pool. I'm talking about 15 "dust" payments per day.
DS and MN should not cause it. These are incoming transactions.

 

[oblox]

Problem is with very small payments from P2Pool. I'm talking about 15 "dust" payments per day.
DS and MN should not cause it. These are incoming transactions.

Yeah, I hear you. You're left at the moment with either using with daemon to group and send dust and micro payments or Darkcoil.

 

[crowning]

Just got a link to https://bitcointalk.org/index.php?topic=919373.0

According to deps-linux.yml we ARE building with Openssl-1.0.1k.

eduffield , shouldn't we temporarily use Openssl-1.0.1j ?

flare , I just built v0.11.0.6 with OpenSSL 1.0.1j , all 3 operating systems built without problems and Win and Linux clients also run without problems.

So _if_ there should be a problem with OpenSSL 1.0.1k we can easily switch back.