Topic: [ANN] Syscoin- FINAL 2.0 LAUNCHED! *ENCRYPTION, MARKETPLACE, BTC INTEGRATION* - page 194. (Read 582967 times)

How do you create a name alias with the UI?  As I get an error as it requests my password, and not wanting my password to be part of my alias, I am holding off on testing this feature out. Where does the password go, and what do I enter in the Value field?

You guys need a simple FAQ to go with the release.  

According to roadmap, we should download V0.1.5 now, but where is it?

I will bet 50,000 SYS the wallet will be unusable when "released". Too late to make up for lost time.
Also, I just want the public to know they delete posts FOR NO REASON!!! September 21st came and went. No new wallet release that's a FACT.

.... September 21st came and went. No new wallet release that's a FACT.

i think you have shut him up ...NO REPLY...HE IS SCARED OF HIS OWN BET..

Appreciate the community support sorry if your quoting-reply got removed in the cleanup.

---

In real news we're going to publish Syscoin 0.1.5 RC1 tonight. Because we want to make sure everything is rock solid the release we publish tonight will be considered a "release candidate". What this means is - for all intensive purposes - this is the final release. Before we officially promote it to that position we want some users to get hands-on time with it.

Release Candidates will be a pattern we follow moving forward with future releases as well. This gives the community time to use the wallet and provide feedback to the team prior to that build becoming the "production wallet". We are merging some stuff in Github and will have binaries posted tonight. If no major issues or requests come up in 24-48hrs this will be promoted to a production release as-is. If items are found we will address them before promoting. Because this is a release candidate the 0.1.4c wallet will still remain the official "production wallet" pending community feedback on 0.1.5 RC1.

This strategy allows the community to provide feedback while also hardening/testing the client on a much larger scale than we are able to reproduce in our testing environments. This release doesn't introduce any changes that require a hardfork so you can use it freely on the main network and it is not restricted to testnet. In the future, if we have changes that do impact the actual network (such as assets feature, or other changes that may impact network) these will be released in "release candidate" form on the testnet first. We'll establish an official public testnet and testnet policy when we get to that point.

More coming very soon!

Ill take your bet, escrow please, pls put it in ASAP!

I will bet 50,000 SYS the wallet will be unusable when "released". Too late to make up for lost time.
Also, I just want the public to know they delete posts FOR NO REASON!!! September 21st came and went. No new wallet release that's a FACT.

Ill take your bet, escrow please, pls put it in ASAP!

I will bet 50,000 SYS the wallet will be unusable when "released". Too late to make up for lost time.
Also, I just want the public to know they delete posts FOR NO REASON!!! September 21st came and went. No new wallet release that's a FACT.

Appreciate the community support sorry if your quoting-reply got removed in the cleanup.

---

In real news we're going to publish Syscoin 0.1.5 RC1 tonight. Because we want to make sure everything is rock solid the release we publish tonight will be considered a "release candidate". What this means is - for all intensive purposes - this is the final release. Before we officially promote it to that position we want some users to get hands-on time with it.

Release Candidates will be a pattern we follow moving forward with future releases as well. This gives the community time to use the wallet and provide feedback to the team prior to that build becoming the "production wallet". We are merging some stuff in Github and will have binaries posted tonight. If no major issues or requests come up in 24-48hrs this will be promoted to a production release as-is. If items are found we will address them before promoting. Because this is a release candidate the 0.1.4c wallet will still remain the official "production wallet" pending community feedback on 0.1.5 RC1.

This strategy allows the community to provide feedback while also hardening/testing the client on a much larger scale than we are able to reproduce in our testing environments. This release doesn't introduce any changes that require a hardfork so you can use it freely on the main network and it is not restricted to testnet. In the future, if we have changes that do impact the actual network (such as assets feature, or other changes that may impact network) these will be released in "release candidate" form on the testnet first. We'll establish an official public testnet and testnet policy when we get to that point.

More coming very soon!

Appreciate the community support sorry if your quoting-reply got removed in the cleanup.

---

In real news we're going to publish Syscoin 0.1.5 RC1 tonight. Because we want to make sure everything is rock solid the release we publish tonight will be considered a "release candidate". What this means is - for all intensive purposes - this is the final release. Before we officially promote it to that position we want some users to get hands-on time with it.

Release Candidates will be a pattern we follow moving forward with future releases as well. This gives the community time to use the wallet and provide feedback to the team prior to that build becoming the "production wallet". We are merging some stuff in Github and will have binaries posted tonight. If no major issues or requests come up in 24-48hrs this will be promoted to a production release as-is. If items are found we will address them before promoting. Because this is a release candidate the 0.1.4c wallet will still remain the official "production wallet" pending community feedback on 0.1.5 RC1.

This strategy allows the community to provide feedback while also hardening/testing the client on a much larger scale than we are able to reproduce in our testing environments. This release doesn't introduce any changes that require a hardfork so you can use it freely on the main network and it is not restricted to testnet. In the future, if we have changes that do impact the actual network (such as assets feature, or other changes that may impact network) these will be released in "release candidate" form on the testnet first. We'll establish an official public testnet and testnet policy when we get to that point.

More coming very soon!