[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[RenegadeMan]

0.11.0.4 on mainnet?
https://drk.mn/

impossible. I`ve seen that, probably monitoring have some issue.

There are dozens of them appearing now. Are the monitoring daemons on Elbereth's site somehow picking this version number up incorrectly from the 10.17.26 code?

[eduffield]

0.11.0.4 on mainnet?
https://drk.mn/

impossible. I`ve seen that, probably monitoring have some issue.

There is often a MN with advance version.
Should be for testing purpose (Evan's or Flare's node)

v0.11.0.4

This version has everything and works on mainnet.

https://darkcointalk.org/threads/v0-11-0-x-testing.3401/page-20#post-35889

v11 works on mainnet and if you want to help testing, you could run it too. Just make sure you compile from source and run it in a debugger. (The protocol is backwards compatible so separate releases can survive side-by-side together)

[tungfa]

10.17.26 Onyx V3 - All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.17.26-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.17.26-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.17.26-linux.tar.gz

10.17.25/26
- Fixed bugs with Start-many
- Fixed an issue where clients might not be able to validate a block and get stuck

MAC Link is working now !
Tx Evan
 

[stonehedge]

An unstable release on main net is unacceptable in my view.  Testnet should be scaled up rather than put the network at risk.  If this is testing by the devs, it makes me wonder why I pay FIAT to subsidise a portion of testnet to avoid exactly this sort of thing.

[stonehedge]

0.11.0.4 on mainnet?
https://drk.mn/

impossible. I`ve seen that, probably monitoring have some issue.

There is often a MN with advance version.
Should be for testing purpose (Evan's or Flare's node)

v0.11.0.4

This version has everything and works on mainnet.

https://darkcointalk.org/threads/v0-11-0-x-testing.3401/page-20#post-35889

v11 works on mainnet and if you want to help testing, you could run it too. Just make sure you compile from source and run it in a debugger. (The protocol is backwards compatible so separate releases can survive side-by-side together)

Of course, Evan knows the true risks.  I can't say I agree with it though. 

[eduffield]

An unstable release on main net is unacceptable in my view.  Testnet should be scaled up rather than put the network at risk.  If this is testing by the devs, it makes me wonder why I pay FIAT to subsidise a portion of testnet to avoid exactly this sort of thing.

V11 is in a state where it's releasable, the final stage of testing is to have some of the main network begin to update and report back. It actually gives us a much lower risk of breaking something when we do it this way. It's not any of the devs though, but I support it if it's just for testing.

[eduffield]

0.11.0.4 on mainnet?
https://drk.mn/

impossible. I`ve seen that, probably monitoring have some issue.

There is often a MN with advance version.
Should be for testing purpose (Evan's or Flare's node)

v0.11.0.4

This version has everything and works on mainnet.

https://darkcointalk.org/threads/v0-11-0-x-testing.3401/page-20#post-35889

v11 works on mainnet and if you want to help testing, you could run it too. Just make sure you compile from source and run it in a debugger. (The protocol is backwards compatible so separate releases can survive side-by-side together)

Of course, Evan knows the true risks.  I can't say I agree with it though. 

It's essentially zero risk. 

[Jestah]

10.17.26 Onyx V3 - All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.17.26-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.17.26-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.17.26-linux.tar.gz

10.17.25/26
- Fixed bugs with Start-many
- Fixed an issue where clients might not be able to validate a block and get stuck

MAC Link is working now !
Tx Evan
 

It's telling me it's v10.17.25 in the qt debug window when I downloaded 10.17.26....

[qwizzie]

maybe we should make a formal announcement on all forums that v0.11.0.4 is since today available to test on
Mainnet and that any feedback is appreciated ? And point them to the binaries as well...
Just make sure they all know its for test purposes.

[GilAlexander]

An unstable release on main net is unacceptable in my view.  Testnet should be scaled up rather than put the network at risk.  If this is testing by the devs, it makes me wonder why I pay FIAT to subsidise a portion of testnet to avoid exactly this sort of thing.

An unstable release can't put the network at risk - just because onyone can build his own 'evil' client in a way he wants and that isn't a way to exploit the good decentralised cryptonetwork.

[BiteMyShinyMetalAss]

DRK is amazing! Developers - even more! Soon DRK will be the cardinal Richelieu to the Bitcoin!  LTC is like a patient in  severe coma, each day new organ fails, soon it will be done...

[stonehedge]

0.11.0.4 on mainnet?
https://drk.mn/

impossible. I`ve seen that, probably monitoring have some issue.

There is often a MN with advance version.
Should be for testing purpose (Evan's or Flare's node)

v0.11.0.4

This version has everything and works on mainnet.

https://darkcointalk.org/threads/v0-11-0-x-testing.3401/page-20#post-35889

v11 works on mainnet and if you want to help testing, you could run it too. Just make sure you compile from source and run it in a debugger. (The protocol is backwards compatible so separate releases can survive side-by-side together)

Of course, Evan knows the true risks.  I can't say I agree with it though. 

It's essentially zero risk. 

Fair enough Ed.  Apologies for sounding terse and assuming it was testing by devs.  Obviously you can't stop people using test releases on main net if they want to. I work in environments with full on release management and obviously not the freedom of open source so tend to be on a hair trigger with this kind of thing!

[RenegadeMan]

0.11.0.4 on mainnet?
https://drk.mn/

impossible. I`ve seen that, probably monitoring have some issue.

There is often a MN with advance version.
Should be for testing purpose (Evan's or Flare's node)

v0.11.0.4

This version has everything and works on mainnet.

https://darkcointalk.org/threads/v0-11-0-x-testing.3401/page-20#post-35889

v11 works on mainnet and if you want to help testing, you could run it too. Just make sure you compile from source and run it in a debugger. (The protocol is backwards compatible so separate releases can survive side-by-side together)

Of course, Evan knows the true risks.  I can't say I agree with it though. 

It's essentially zero risk. 

Fair enough Ed.  Apologies for sounding terse and assuming it was testing by devs.  Obviously you can't stop people using test releases on main net if they want to. I work in environments with full on release management and obviously not the freedom of open source so tend to be on a hair trigger with this kind of thing!

Same here! On most projects I work on if code was introduced into a production environment prior to its passing through formal SIT (systems integration testing) and UAT (user acceptance testing) there'd be a big red flag go up and a rollback would have to be instigated to maintain various certification levels. All very serious by comparison. Once DRK's beyond this beta stage and a 1.x system I'd expect something pretty similar.

[Libertario]

Official: Etherum start on March; IBM adopt etherum-blockchain technology.

When a "darkchain"? It's good for smartcontract!

[stonehedge]

Official: Etherum start on March; IBM adopt etherum-blockchain technology.

When a "darkchain"? It's good for smartcontract!

I'm guessing they are forking it for their "internet of things" blockchain plans rather than currency purposes.

[GhostPlayer]

Same here! On most projects I work on if code was introduced into a production environment prior to its passing through formal SIT (systems integration testing) and UAT (user acceptance testing) there'd be a big red flag go up and a rollback would have to be instigated to maintain various certification levels. All very serious by comparison. Once DRK's beyond this beta stage and a 1.x system I'd expect something pretty similar.

 Understandable, but does that apply to the open source world where anyone is able to compile their own code, or closed-source in-house dev?
 If its on Ghub there is no way to prevent anyone from doing it anyways or even write their own code.

[vertoe]

HEADS UP!

Version 0.10.17.25 changes the public address of your multisignature holdings! The private keys and redeemscripts are untouched and you can still access your funds without any problems. You just might wish to regenerate the script to update the public key to recieve funds! Multisignature addresses start with '7' now. (Example.)

This is a backported feature from the upcoming 0.11 release. Join testing.

Hey Vertoe,
What to you mean exactly by "regenerate the script to update the public key to recieve funds" ??
Which script? (a patential script that use multisig? if we don't use multi sig : nothing change? and this imply no impact on MN?)

Edit : and the version is 25 or 26?  

it's 25. and its affecting main network. and if you dont know what i'm talking about, you are pretty fine (only affects multisig).

[vertoe]

An unstable release on main net is unacceptable in my view.  Testnet should be scaled up rather than put the network at risk.  If this is testing by the devs, it makes me wonder why I pay FIAT to subsidise a portion of testnet to avoid exactly this sort of thing.

I agree and I oppose any of evans comments about using v11 on main net.

An unstable release on main net is unacceptable in my view.  Testnet should be scaled up rather than put the network at risk.  If this is testing by the devs, it makes me wonder why I pay FIAT to subsidise a portion of testnet to avoid exactly this sort of thing.

V11 is in a state where it's releasable, the final stage of testing is to have some of the main network begin to update and report back. It actually gives us a much lower risk of breaking something when we do it this way. It's not any of the devs though, but I support it if it's just for testing.

please, read your PMs or at least the testing thread on dct  

why bothering going main net if not everything is working on testnet still?

and, recent v10 is broken too, we have to look into the address versions again (not sure what went wrong there), see onyx v3 thread on dct.

[eahmadov]

10.17.26 Onyx V3 - All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.17.26-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.17.26-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.17.26-linux.tar.gz

10.17.25/26
- Fixed bugs with Start-many
- Fixed an issue where clients might not be able to validate a block and get stuck

MAC Link is working now !
Tx Evan
 

New Mac wallet is experiencing problem with addresses. Please don't install it yet. Wait for a fix. Somebody posted that in DCT: https://darkcointalk.org/threads/onyx-v3-10-17.3141/page-7

[KryptoFoo]

An unstable release on main net is unacceptable in my view.  Testnet should be scaled up rather than put the network at risk.  If this is testing by the devs, it makes me wonder why I pay FIAT to subsidise a portion of testnet to avoid exactly this sort of thing.

I agree and I oppose any of evans comments about using v11 on main net.

An unstable release on main net is unacceptable in my view.  Testnet should be scaled up rather than put the network at risk.  If this is testing by the devs, it makes me wonder why I pay FIAT to subsidise a portion of testnet to avoid exactly this sort of thing.

V11 is in a state where it's releasable, the final stage of testing is to have some of the main network begin to update and report back. It actually gives us a much lower risk of breaking something when we do it this way. It's not any of the devs though, but I support it if it's just for testing.

please, read your PMs or at least the testing thread on dct  

why bothering going main net if not everything is working on testnet still?

and, recent v10 is broken too, we have to look into the address versions again (not sure what went wrong there), see onyx v3 thread on dct.

Vertoe put together a very well organized list of open items here https://darkcointalk.org/threads/v0-11-0-x-testing.3401/page-22#post-35996. The open items appear to only affect end user experience. My only concern is that if there was significant code changes in v11 there may be unknown unknowns lurking. No nothing can stop folks from running v11 on mainnet, but it doesn't hurt to have more time on testnet right? Ideally the dev team should be discouraging everyone from using v11 on mainnet until the main UX issues are resolved on testnet. Saying it is OK to use it now - a kind of defacto release notice - is confusing to us readers who are eager to use the latest and greatest versions of stuff and who may feel they lose some advantage by not updating immediately and before everyone else. And maybe no harm done if we do, but what's the rush. Would be nice to have a fully functional mostly bug free UX before devs start saying it is OK to upgrade.