looks like someone is ready to dump  i think you are right. someone warned me about HYPER before that dumped too. i was fortunate to get out at a good price. This coin is in the accumulation zone right now. Whoever plucked that sell at 830 is going to be happy. Bookmark this post. Did you bookmark it? |
|
|
|
 The accumulation phase is wrapping up. |
|
|
|
I guess you have to take the good with the bad.
Decred is the good.
This is the bad.
It is a pretty senseless conclusion. Decred is good of course but i don't see any reason why would this be the bad. Because this coin has all the makings of one that will be abandoned in 2 weeks. It's a lame copycat where the "devs" have absolutely no intention of any real development. I predict a nice 4 BTC yobit dump. |
|
|
|
I wasn't talking from that point of view..
I was talking from the point of view about thinking about the technology behind Decred and what impact it can have. The majority won't focus on that but "how big it can get".
This is normal and expected, and am more keen on what this project will bring to the table.
How big it can get is really all that matters for a decentralized currency. It's part and parcel with the tech. For example, can bitcoin itself scale to make it a global currency for everyday use? It's probably consistent with the motivation behind bitcoin to say that the answer to that question is fundamentally important to the future of human liberty. |
|
|
|
|
I guess you have to take the good with the bad.
Decred is the good.
This is the bad.
|
|
|
|
So much inevitable greed over here.
But it has to be this way as money is what moves the world and motivates even the peasant..
Look at Socrates. I guess you live on the street, are barely clothed, and eat only food that has fallen from trees. Anything more would be greedy. |
|
|
|
This looks useful. I do so much TA and trading, I need to work this bot into my arsenal of tools. |
|
|
|
Happy New Years to all from Team Synergy!! We look forward to an innovative 2016 and encourage you to join us in our Slack channel to stay current and chat with the team! Register Here! It's great to see that the devs are still active. Happy new year.  |
|
|
|
looks like someone is ready to dump i think you are right. someone warned me about HYPER before that dumped too. i was fortunate to get out at a good price. This coin is in the accumulation zone right now. Whoever plucked that sell at 830 is going to be happy. Bookmark this post. |
|
|
|
You left out the world's most famous plagiarist of all:
It's pretty much accepted that the book your reference is anti-semitic propaganda cooked up by German Nazis. No further "research" has advanced the claims in that book. |
|
|
|
|
The negative trust ratings on John Connor's bitcointalk account appear petty and are evidence of a bankrupt trust system where insiders are granted license to damage the reputation of others in order to further their own agenda.
Even if those who have penalized John Connor's trust rating have nobel intentions, they completely miss the mark. The "misattribution" attack is an old, tired play, that indicates a vacuum of ideas or technical knowledge that could nourish better critique.
To summarize how this topic has devolved, the attacks here are based on John Connor's claim that VNL is "written from scratch in its entirety". This quote comes from a single post on the launch thread. It is not a central aspect of the coin's marketing. The closest the marketing gets is to say "it is not a clone of any other project". Technically, the marketing is correct, as clones are understood to be 100% identical.
Now, it can be argued that "written from scratch in its entirety" is not perfectly accurate. However, the question is whether this statement should be grounds to reduce John Connor's trust rating. Was this statement used to solicit funds? No. Was it used to dump premine? No.
In fact, that these answers are "no" is evidence that those who have damaged John Connor's trust rating should themselves lose trust as it is clear these individuals have damaged his rating for their own selfish financial reasons. There can be no other explanation.
|
|
|
|
I read that Vanillacoin aims to become anonymous. Is there any technical information available how it attempts to achieve anonymous transactions? So far all the coins that claim to be anonymous have actually a flawed anonymity which I wouldn't even call anonymity.
There's a whitepaper. I'd point you to it but according to crypto gurus I've talked to, it's too thin on details. Maybe I'll send one here to say why. |
|
|
|
Hello everyone in this thread. Today someone posted a C++ job advertisement on the bitcoin's block chain: http://cryptograffiti.info/?txnr=4054 the above link finally guides you here: https://talk.vanillacoin.net/topic/284/job-listingsSo, out of curiosity I sent my CV to that John Connor dude. I have 10 years of C and C++ development experience and turned out it didn't satisfy John's needs (for whatever the actual reason was). His e-mails were rather cocky and his reasoning is sort of alien to me from the software developer's point of view. For example, if I was to look for a C++ programmer, I wouldn't immediately discard someone for 10 years of experience as if it was not enough. A good lead programmer chooses their team by the actual skills of people (testing them if needed) not just blatantly stating strange stuff such as "university experience does not count". Since I'm also a cryptocurrency investor, I started to investigate whether Vanillacoin is worth investment. Here's one article about it that I found particularly interesting: http://www.cryptocollectorsclub.com/vanillacoin-secrets.htmlthe dev is a bit of an egomaniac, perhaps just doesn't care about the community or gaining fans early on? I laughed when I read this because it proves that John Connor is actually an arrogant person and it was not just me who perceived him as such  I then stumbled upon this reddit section: https://www.reddit.com/r/VanillaCoin/comments/3b25f6/welcome_to_the_uncensored_vanillacoin_subreddit/It doesn't paint a nice picture of neither Vanillacoin nor John Connor. I was going to buy some vanillacoins but after reading this stuff I am having second thoughts. Smells like Paycoin all over again. Any reason why this criticism should be discarded? I mean, this could all be just unintentional FUD by me. In that case, prove me wrong. I can lurk no longer in this thread. To this post, I must reply. WHO FUCKING CARES WHAT KIND OF PERSONALITY THE DEV HAS?? He doesn't like your 10 yrs experience. That doesn't matter. It's more likely he wants someone with this fancy network programming experience anyway, which is unlikely that you have. Lots of talented people are painfully arrogant. You know why? Because everyone they interact with is technically incompetent by their standards and it gets a little frustrating. If anyone sells because John Connor doesn't make a good guest at a dinner party, then they deserve to lose any and all money they lose. And they probably lose it on a regular basis. |
|
|
|
Still here. Still sick. Major depression.. maybe start coding again will help me with this, activate the brain. Im really sorry guys, it was never meant to be like this, its just happened.
I've heard that the best cure for depression is to publicly burn the premine. |
|
|
|
 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 An update--I didn't expect this today! |
|
|
|
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.
This looks like the right way to do it. Hmmmm....I wonder what hashing algorithm they are using?  It looks like they might be using scrypt from their last commits. Or why else make this commit at this time? I hope it's a lot of rounds. https://github.com/Grandpa-Jones/Synergy/commit/df02c93105bc03772e9af58f6b80f6886cfb61e5#diff-31dd861cd0a6a9747cbc540ac1e3bf72R362Value scrypthash(const Array& params, bool fHelp)
{
if (fHelp || params.size() < 3 || params.size() > 4)
throw runtime_error(
"scrypthash <message> <salt> <rounds> [force=false]\n"
"The <message> and <salt> arguments are strings, <rounds> is an integer.\n"
"If [force] is false, then <rounds> bigger than 1024 trigger an error.\n"
"Returns hex of the hash sha256(scrypt(sha256(message, salt)))."); It is, of course, irrelevant that you or anyone has "discovered" the hashing algorithm we use. The security doesn't depend on an attacker's not knowing the hashing algorithm. It's good to keep as much secret as possible, but real security does not rely on keeping algorithms (or even the salt) secret. It's how you use them that matters. The original implementation of the hashing algo we use was pure C# and was too slow. To make it faster, I used the C++ scrypt implementation already in the wallet code base and made an RPC call from it. We could have re-wrote the C# implementation to make it as fast as the C++ implementation, but there was no need. We have to have a wallet running anyway to do things like burn coins. As usual, I have no idea what you are talking about, but it sounds great. Keep it up Grandpa! |
|
|
|
Thank you for yuor answer.
However why there is so small voices? Shy people or what?
I'm just a SNRG supporter and lurker with a really small voice.But I see new updates on github..... I'm a lurker too in the slack, but the devs are on fire in there. You can't go by what they post on bitcointalk even though they don't leave you guessing. Join the slack and lurk like me if you don't have time to chat to see what is really going on. |
|
|
|
Woah! Nice update!!!! That was today? |
|
|
|
|
Show Posts
