[SNRG] 🔥 Synergy 🔥 Cloud.Synergycoin.com Cloud Bot Now Live!! 🔥

[HoLeeDik]

Wallets have been updated with the latest logo and colors.  Update to the new look today!

i update wallet to keep stake coins!  thank you for update please keep going.

[NextGenCrypto]

This is something that has been requested by a couple users, however, I personally feel some of the items we have on our list would be more utilized by the community.

"Some of the items"? Come on, tease us 

I'd like to see some functionality be built around the staking of SNRG.   

[TrueAnon]

Nice work here gents

[lajz99]

This is something that has been requested by a couple users, however, I personally feel some of the items we have on our list would be more utilized by the community.

"Some of the items"? Come on, tease us 

I'd like to see some functionality be built around the staking of SNRG.   

I miss Turbo Stake!

New Qt wallet looks good guys.  Keep on delivering and Synergy will do well.  I cant wait to see whats next.

[NextGenCrypto]

I just want to make sure those that are new to Synergy Cloud see this and understand that we make security a top priority.  If you've got any questions, please feel free to ask.  If it's too technical, I'll find someone to get an answer for you!

Enhanced API Key Encryption:
This update vastly improves password and API security. According to security best practices, passwords are not stored on our servers (and never were). Instead only the cryptographic fingerprint ("hash") of a password is stored. When a user logs in, the hash of the attempted password is calculated and then compared to what is stored on our server. To discover the password, an attacker can try to hash many different passwords to find those that match hashes stored on our servers.

To thwart this type of brute force search, we do not use a simple one-step hash. Instead, our new system stores the a hash of the password using a large number of cycles of a very computationally expensive hash, made more secure with a large 256 bit random salt. To get a sense of how long a 256 bit salt is, an example would be bb5d3f9c0e396c3f8884f24ec43a16a31e6139e4e10d44512c261fc305df427f.
These security measures mean that an attacker must have a prohibitive amount of computing resources to "crack" any passwords that may be exposed if our database server, hosted by a third party, is compromised.

We use similar technology to protect API keys. We do not store the actual API key on our servers. Instead we store the encrypted version, using AES encryption, which is one of the strongest encryption algorithms available. We also do not store the decryption keys to the encrypted API keys anywhere. When a user logs in, the decryption key is generated dynamically from the user's password, using a key derivation method similar to the method we use to create the password hashes for login. Are the password hashes and API decryption keys the same? No. Just the method to generate them are similar in that they are created using numerous rounds of strong cryptographic hashing with a random salt. The random salts are different.

Finally, the salts are stored and the hashing is performed on a server remote from our database server, meaning that even if an attacker recovers the password hashes and encrypted API keys, they will still have to compromise the remote server to learn the hashing algorithm and salts. But, even in the highly unlikely event that they compromise both servers, discovering the hashes, encrypted keys, salts, and hashing algorithms, they will still be stifled by the need to brute force passwords under the burden of our very computationally expensive hashing system.

[ASICrefugee]

I just want to make sure those that are new to Synergy Cloud see this and understand that we make security a top priority.  If you've got any questions, please feel free to ask.  If it's too technical, I'll find someone to get an answer for you!

Enhanced API Key Encryption:
This update vastly improves password and API security. According to security best practices, passwords are not stored on our servers (and never were). Instead only the cryptographic fingerprint ("hash") of a password is stored. When a user logs in, the hash of the attempted password is calculated and then compared to what is stored on our server. To discover the password, an attacker can try to hash many different passwords to find those that match hashes stored on our servers.

To thwart this type of brute force search, we do not use a simple one-step hash. Instead, our new system stores the a hash of the password using a large number of cycles of a very computationally expensive hash, made more secure with a large 256 bit random salt. To get a sense of how long a 256 bit salt is, an example would be bb5d3f9c0e396c3f8884f24ec43a16a31e6139e4e10d44512c261fc305df427f.
These security measures mean that an attacker must have a prohibitive amount of computing resources to "crack" any passwords that may be exposed if our database server, hosted by a third party, is compromised.

We use similar technology to protect API keys. We do not store the actual API key on our servers. Instead we store the encrypted version, using AES encryption, which is one of the strongest encryption algorithms available. We also do not store the decryption keys to the encrypted API keys anywhere. When a user logs in, the decryption key is generated dynamically from the user's password, using a key derivation method similar to the method we use to create the password hashes for login. Are the password hashes and API decryption keys the same? No. Just the method to generate them are similar in that they are created using numerous rounds of strong cryptographic hashing with a random salt. The random salts are different.

Finally, the salts are stored and the hashing is performed on a server remote from our database server, meaning that even if an attacker recovers the password hashes and encrypted API keys, they will still have to compromise the remote server to learn the hashing algorithm and salts. But, even in the highly unlikely event that they compromise both servers, discovering the hashes, encrypted keys, salts, and hashing algorithms, they will still be stifled by the need to brute force passwords under the burden of our very computationally expensive hashing system.

I think there is a job going at Talk Talk 

[zen2]

this looks interesting. Can anybody give me short introduction about synergy? Never heard of it. Did it have ICO or premine/instamine?

[Woody20285]

this looks interesting. Can anybody give me short introduction about synergy? Never heard of it. Did it have ICO or premine/instamine?

Originally POW which ended forever ago - approx 4300 blocks total (see ann) - now POS.
Very innovative Dev and Team - always coming up with new twists.
Always under-promise and over-deliver.

Latest development is Trading bot that you can pay for only when you use it -
Pay 1 day use 1 day - pay 3 days and it is 3 consecutive days.
Payment in Synergy that is Burned - over 1000 SNRG burned so far.
Max. funding of bot is 30 days - If send over 30 days extra is burned - so don't .

More developments coming soon.

[bluehorseshoe]

I still can't get my wallet to update, stuck on block 37294 using client version 1.2.0.1

I am running two other wallets without issue on the same machine so I don't believe it's a firewall issue.

Already have tried rebooting and relaunching wallet over and over.

Any ideas would be greatly appreciated.


-Brett

[NextGenCrypto]

The following updates to Synergy Cloud have been pushed live to the production site.

Buy/Sell Only on Accumulator Bot:
The Accumulator bot has been updated with the options to allow you to re-list only buys, sells or both and the % difference you indicate.

Timed Orders / Ping Pong Update
The Timed Orders and Ping Pong bots have been updated to allow for continuous monitoring of balances in order to execute transactions.  What this means is that if you are attempting to sell coin XYZ and the balance of this coin goes below the criteria you set, the bot will continue to check the balance and when the balance is within range of what is programmed for the bot an order will execute.

The bot updates above were made in order to improve bot flexibility and allow for different strategies using multiple bots together.  With a little thought, you'll likely see why these small updates were made.

Bug Fixes:
- Code for "Stop if Coin Price Less Than" was corrected, previous functionality was reversed.


-nextgen

[Macno]

Very nice! Thanks for the update!

[NextGenCrypto]

Very nice! Thanks for the update!

Thanks, Macno.  We're glad to have you as such a great supporter.

[OZmaster]

nice update:) cool new feature for gathering some coins

[NextGenCrypto]

nice update:) cool new feature for gathering some coins

That's the spirit, glad some are understanding there is no single bot that is just going to create profit for its users.  If there were, everyone would be using it and how would that be profitable?

Right now, we're focusing on making the platform as versatile as possible so people can use multiple tools to create their own trading strategy.

If ANYONE has any suggestions on the bots, PLEASE let us know.  Put up a post, tell us in Slack, shoot me a PM, send a smoke signal...just put the idea out there!  We want to know what YOU, the community wants in the platform.  Your voice will be heard.

[irwanjabryg]

nice update:) cool new feature for gathering some coins

That's the spirit, glad some are understanding there is no single bot that is just going to create profit for its users.  If there were, everyone would be using it and how would that be profitable?

Right now, we're focusing on making the platform as versatile as possible so people can use multiple tools to create their own trading strategy.

If ANYONE has any suggestions on the bots, PLEASE let us know.  Put up a post, tell us in Slack, shoot me a PM, send a smoke signal...just put the idea out there!  We want to know what YOU, the community wants in the platform.  Your voice will be heard.

What SNRG lowest price whether today

[Macno]

What SNRG lowest price whether today

what is your question?

[Digital_Currency_LTD]

why is the price so low? 

[NextGenCrypto]

why is the price so low?  

Posts like this do not help.

In order for a coin to be successful, it takes more than 3 people posting and spreading the word about Synergy.  Macno has been great about this.  Gramps and myself can only do so much and we both prefer to focus on the tech side of things as that is our specialty.  We just don't have the time to start multiple threads and post every hour at this point.

If you want to help promote Synergy, which would likely result in increased interest and an increased price we would love the help!  Please feel free to reach out.

[Macno]

The demand for a trading bot seems to be either much lower than expected or people do really prefer to use bots like the Circ one and they do not care for having been scammed and the lack of a dev team.

Does anyone have an idea how many SNRG one needs to stake what`s needed for 1) a day 2) a week 3) 28 days of bot use?

[djhomeschool]

The demand for a trading bot seems to be either much lower than expected or people do really prefer to use bots like the Circ one and they do not care for having been scammed and the lack of a dev team.

Does anyone have an idea how many SNRG one needs to stake what`s needed for 1) a day 2) a week 3) 28 days of bot use?

Starting balance on November 1st: 931.
Ending balance on December 1st: 1091.

Each staking paid out 10 coins, so I staked 16 times during the months. That help to give you a number?