|
Is there a guide for mining while using the new GUI Qt? Not sure how to set this up to mine solo.
|
|
|
|
I think that Ethereum is too slow in development considering the fact that it had a huge ICO. There was a lot of investing in this project and still up to this date there is no stable release of a GUI wallet? Still, I like Ethereum's technology but the lack of a GUI wallet makes it somewhat unpromising. I have faith in Ethereum and would hope for massive adoption in the near future.  Go back a page or two, there is a GUI wallet, and it's been working fine for me. |
|
|
|
|
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.
|
|
|
|
Does anybody else mining on Windows have periodic crashes? Every time I begin mining (single R9 290 GPU) it starts up just fine. I submit shares and everything is happy. At some point (usually 1-2 hours later) it will eventually hang everything up and crash the computer. Geth and ethminer are not reporting any errors, it just suddenly stops working. Anybody else having these issues?
Yes, constantly. |
|
|
|
so confused...nothing about distribution other then mention of a swap?
It will be swapped from Moincoin Okay...so what is a Moincoin and how does one obtain some? See, if you want people to get involved, you need to tell them how... |
|
|
|
|
so confused...nothing about distribution other then mention of a swap?
|
|
|
|
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 stop staking a few weeks ago and now you come back? What's the deal?  |
|
|
|
I'm gonna be on a road trip for a few days and I feel iffy leaving ETH in an exchange. Which ethereum wallet is good to use?
Thanks.
Why don't you just use the beta GUI wallet? |
|
|
|
Any plans to try and implement arb function?
Would be interested as well on what the plan is for that function. 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. I will not implement a manual arb functio,n so if we're going to do it, it needs to be done right which would take a decent amount of resources. Definitely something we'll discuss, but at this point we have no solid plans or timeline. |
|
|
|
My wallet doesn't look like it's syncing up and I sent coins to it 10/28 and they still aren't there.
I have three connections currently.
Is there a new wallet since I downloaded this one last week or something else I need to do.
Any help would be greatly appreciated,
Brett
Hey Brett, Can you confirm the number of blocks in your debug console matches what is in the explorer? https://chainz.cryptoid.info/snrg/If you want to join Slack I can help you out in real time: http://www.synergycoin.com/wp-login.php?action=slack-invitation-nextgen |
|
|
|
@NextGenCrypto
you couldn't make hot in a fire !
EvilDave insulted you pretty much and you agreed with him LOL
What is it your arguing with me here again ?
who you defending ?
How is it an insult when nothing he said applies to me? Moron. Look at all of your pathetic shill accounts come out to bump your thread. Like I said, nothing but a wannabe do-gooder. Such a pathetic life you live... |
|
|
|
Agree keep it up good things take time! Can't wait for website
+1 I'd help out a bit for the explorer as well...what's the deal there? Did we just agree on something We likely agree on more than you think.  |
|
|
|
Agree keep it up good things take time! Can't wait for website
+1 I'd help out a bit for the explorer as well...what's the deal there? |
|
|
|
 The following updates to Synergy Cloud will be made at 8:30pm pacific this evening (29-Oct-2015).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. Please Note: Due to the change in the way API keys are being stored, when you log in to your account after the update you will need to re-add the keys from the exchanges you wish to use. To ensure maximum security, please generate and use new keys. Google Two Factor AuthenticationGoogle Two Factor Authentication will be added to the site in order to increase your account security. Please visit your account settings to activate as soon as possible. We encourage ALL users to activate 2FA in order to better protect your account.Automated Calculation and Updating of SNRG Burning Price:The SNRG burn rate will now be updated daily based on market indicators. This will allow us to automatically maintain a consistent rate for using the sites services without having to do daily, manual calculations. This will mark the end of the introductory burn rate of 3 SNRG/day. Enabling of Automated System Email:Automated email functionality has been added in order to allow users to be able to utilize the Password Reset functionality should it be needed. Users will now also be required to confirm their email address prior to using the sites functionality. This will allow us to ensure users will have access to reset their password and additional site functionality that will be added in the future. As always, please feel free to let myself or Grandpa Jones know if you have any questions. We'll be available in the Slack channel tonight during the release to keep an eye on things and make sure the release goes as smoothly as possible for our users. -nextgen |
|
|
|
There are a lot of scammers around: do your own research and never rush to buy in to a hype.
Finally, someone with some good advice. Shouldn't that just be common sense though? |
|
|
|
Thanks
Thanks? Really? Nobody would bother to post that but a shill who wanted to bump is own topic. Another useless thread by a butthurt troll who has fallen for too many scams... nice sig.. synergycoin ? LOL in case you didn't know i cashed out while Bitcoin was a grand each smart ass  i knew you guys with your crap coins would ruin all of this with your greedy antics. butthurt ? about what now ? that i am trolling by warning some guys that forum games made the creator a ton of money ? ..and others lost money. trolling by warning others that some guys get money and some lose it ? read what i said earlier.. reptiela admitted on Polonioex chat he made $1,000's on his forum game topic here. and that means other guys LOST money. since there seems to be more of these pouring in now i thought a warning was a good idea. Yep, at least I'm doing something with my time. Unlike you who is nothing but a wannabe do-gooder who's trying to get a little attention by making a minimum of 10 posts per day in the ALTCOIN section about how terrible altcoins are and how they're nothing but a scam. You're just an oblivious, lonely troll looking for some attention from all of those who have been scammed. That is a fact. Your post history shows your desperation. It's pretty pathetic. |
|
|
|
The following updates to Synergy Cloud will be made at 8:30pm pacific this evening (29-Oct-2015).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. Please Note: Due to the change in the way API keys are being stored, when you log in to your account after the update you will need to re-add the keys from the exchanges you wish to use. To ensure maximum security, please generate and use new keys. Google Two Factor AuthenticationGoogle Two Factor Authentication will be added to the site in order to increase your account security. Please visit your account settings to activate as soon as possible. We encourage ALL users to activate 2FA in order to better protect your account.Automated Calculation and Updating of SNRG Burning Price:The SNRG burn rate will now be updated daily based on market indicators. This will allow us to automatically maintain a consistent rate for using the sites services without having to do daily, manual calculations. This will mark the end of the introductory burn rate of 3 SNRG/day. Enabling of Automated System Email:Automated email functionality has been added in order to allow users to be able to utilize the Password Reset functionality should it be needed. Users will now also be required to confirm their email address prior to using the sites functionality. This will allow us to ensure users will have access to reset their password and additional site functionality that will be added in the future. As always, please feel free to let myself or Grandpa Jones know if you have any questions. We'll be available in the Slack channel tonight during the release to keep an eye on things and make sure the release goes as smoothly as possible for our users. -nextgen
|
|
|
|
Thanks
Thanks? Really? Nobody would bother to post that but a shill who wanted to bump is own topic. Another useless thread by a butthurt troll who has fallen for too many scams... |
|
|
|
|
Show Posts
