Vinculin
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 03:36:08 PM |
|
Honestly are those people criticizing devs new-comers?
I have been here since the early days and what i only found is devs always deliver what they promised.
As long as they deliver, i don't mind there is a little delay to such a big innovation.
edit: Many people also called "Darkcoin" and "Blackcoin" are P&D/scam in the early days.
|
|
|
|
zing96
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 03:39:54 PM |
|
Implicit in that original statement was that information about the flaw would be made clear at the time of patch release. This has not happened. It is a big thing to a big claim about a flaw affecting other coins, and then not communicate at the specified time.
What did my last sentence say??? "It might be inferred now that the patch has released they may divulge information about it, but that was never explicitly stated." You can infer all you want, but no one ever said this would be made public.
|
|
|
|
drizzle2405
Legendary
Offline
Activity: 1148
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 03:48:07 PM |
|
And as to your repeated statements about 'drama', give it a rest. Unresolved information about a flaw, upcoming hardfork, delayed release heading into a weekend - these are solid elements in any trader's evaluation.
Difference is most aren't trading Cloak... You're already late to the party if you are trying to "trade" Cloak.
|
|
|
|
drizzle2405
Legendary
Offline
Activity: 1148
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 03:53:22 PM |
|
Implicit in that original statement was that information about the flaw would be made clear at the time of patch release. This has not happened. It is a big thing to a big claim about a flaw affecting other coins, and then not communicate at the specified time.
What did my last sentence say??? "It might be inferred now that the patch has released they may divulge information about it, but that was never explicitly stated." You can infer all you want, but no one ever said this would be made public. Thumbs up zing... threecats can't read...
|
|
|
|
cryptodaknight
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 03:54:17 PM |
|
Same here. Great work devs!
Got the dreaded LIVEAY32.dll is missing message when I started the new wallet. Fixed it but wondering why I never saw that error with any of the earlier versions of the wallet. ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Got this too, what do i do to fix this, wallet won't open cause of missing this file?
|
|
|
|
Coolstoryteller
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 03:56:56 PM |
|
For anyone that missed the news yesterday: I finished building us an Official Forum for Cloak - http://www.cloaktalk.org/. Anyone looking to further the cloak discussion without the presence of these toe jammers on bitcointalk feel free to join. Note that any posting of FUD in the non-FUD section will result in the automatic IP BAN. I would like to thank all the scum on bitcointrashtalk that motivated me to build us a new forum. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
conf
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 04:01:56 PM |
|
i have my stake reward confirmed. Thx devs
|
,╓▄▄▄▄▄▄▄▄▄╓ ╓▄█████████████████▄╖ ╓▄█████▀▀'▒,,,,,╠'▀▀█████▄, ,▓███▀╜,▄▄███████████▄▄,╙▀████╖ ▄███▀ ▄█████▀▀"``╙"▀▀█████▄ ▀███▄ ▓███╜╓████▀ ,▄▄█████▄▄, ▀████,╙███▌ ▓███`╔███▀ ╓▓███▀▀▀▀▀████╖ ▀███@"███▌ ]███▌┌███▌ ▐███ ███▄ ▐███ ▐███, ▐███ ▐███ .███ ███ ███▌ ███▌ ▐███ ▐███ '███ ███ ███▌ ███▌ ]███@╙███@ ▀██▌ ,▄██▌ ▐███ ▐███` ▓███ ▐███▄ ╙██▀╩ 9███╜ ╔███▀,███▌ ████,╙███▌ ▓███╜,████ ▀███▄ ▀╜ ▀▀ ▄███▌ ╙████▄, ╓▄████╜ ╙█████▄▄╓, ,╓▄▄█████▀ ▀▀█████████████████▀▀ '▀▀▀▀▀▀▀▀▀▀▀'
| CloakCoin | Trustless Anonymous Cryptocurrency | PoSA3 Forum | Bitcointalk | Twitter | Slack | Facebook | VK | Reddit | CloakTV | Instagram | IRC-Chat | Faucet
|
|
|
|
bangomatic
Legendary
Offline
Activity: 1246
Merit: 1000
ARK Team likes to ban and delete posts in reddit.
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 04:09:12 PM |
|
Same here. Great work devs!
Got the dreaded LIVEAY32.dll is missing message when I started the new wallet. Fixed it but wondering why I never saw that error with any of the earlier versions of the wallet. ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Got this too, what do i do to fix this, wallet won't open cause of missing this file? Installing the latest Open SSL should fix it. http://slproweb.com/download/Win32OpenSSL-1_0_1h.exeAlthough I had to install some Microsoft C++ dependencies before hand.
|
|
|
|
threecats
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 04:09:51 PM |
|
Implicit in that original statement was that information about the flaw would be made clear at the time of patch release. This has not happened. It is a big thing to a big claim about a flaw affecting other coins, and then not communicate at the specified time.
What did my last sentence say??? "It might be inferred now that the patch has released they may divulge information about it, but that was never explicitly stated." You can infer all you want, but no one ever said this would be made public. Thumbs up zing... threecats can't read... Sad thing. You both ignore the question at hand: the seriousness of making a claim about a flaw affecting other coins, but then failing to demonstrate or clarify that claim. Instead you resort to ad hominem attacks against me for posing this question - and reposing the question, since no one is answering it.
|
|
|
|
threecats
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 04:11:57 PM |
|
And as to your repeated statements about 'drama', give it a rest. Unresolved information about a flaw, upcoming hardfork, delayed release heading into a weekend - these are solid elements in any trader's evaluation.
Difference is most aren't trading Cloak... You're already late to the party if you are trying to "trade" Cloak. Volume says otherwise. Quite a healthy trade these last hours.
|
|
|
|
darkproton
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 04:15:56 PM |
|
Implicit in that original statement was that information about the flaw would be made clear at the time of patch release. This has not happened. It is a big thing to a big claim about a flaw affecting other coins, and then not communicate at the specified time.
What did my last sentence say??? "It might be inferred now that the patch has released they may divulge information about it, but that was never explicitly stated." You can infer all you want, but no one ever said this would be made public. Thumbs up zing... threecats can't read... Sad thing. You both ignore the question at hand: the seriousness of making a claim about a flaw affecting other coins, but then failing to demonstrate or clarify that claim. Instead you resort to ad hominem attacks against me for posing this question - and reposing the question, since no one is answering it. I hear what you're saying. I would advise to wait 24-48 hours before making a decision based solely on this patch. My belief, a mixture of conjecture and communication with parties involved, is that the devs are busting their butts to get all the features up and running and will reaccess the situation when they have completed. Not saying they will/won't answer your question, but I believe it will be addressed when they have finished. I know it doesn't give you the answer now, but that's all I got for you. If I can answer anything else, let me know. [edit] I believe they are being intentionally vague to protect other pos coins[/edit]
|
|
|
|
threecats
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 04:17:24 PM |
|
[/quote] I hear what you're saying. I would advise to wait 24-48 hours before making a decision based solely on this patch. My belief, a mixture of conjecture and communication with parties involved, is that the devs are busting their butts to get all the features up and running and will reaccess the situation when they have completed. Not saying they will/won't answer your question, but I believe it will be addressed when they have finished. I know it doesn't give you the answer now, but that's all I got for you. If I can answer anything else, let me know. [/quote]
Thanks. I appreciate your response.
|
|
|
|
zing96
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 04:33:43 PM |
|
Implicit in that original statement was that information about the flaw would be made clear at the time of patch release. This has not happened. It is a big thing to a big claim about a flaw affecting other coins, and then not communicate at the specified time.
What did my last sentence say??? "It might be inferred now that the patch has released they may divulge information about it, but that was never explicitly stated." You can infer all you want, but no one ever said this would be made public. Thumbs up zing... threecats can't read... Sad thing. You both ignore the question at hand: the seriousness of making a claim about a flaw affecting other coins, but then failing to demonstrate or clarify that claim. Instead you resort to ad hominem attacks against me for posing this question - and reposing the question, since no one is answering it. Not once did I resort to ad hominem attacks. The issue is that you feel you're owed an explanation when you're not. They can explain the flaw if and when they feel like it. If they do, I'm sure they'll issue a statement and update. I'd like to know what it is also, but I'm not pestering this board for an answer nor am I speculating that this unknown is or will contribute to a downfall in price. That's the "U" in FUD.
|
|
|
|
nanoprobe
Legendary
Offline
Activity: 980
Merit: 1000
Traveling in subspace
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 04:46:46 PM |
|
Talk about manipulation... Some ass hat just threw in a 82k sell on Mintpal...
That didn't last long!
Price may go down even lower...someone said 60's. If it does, I'm happy to buy more! 40's if Christmas comes early ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Seriously, 40's would be like a dream come true. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) I'm transferring more bitcoin to mintpal. OH YEAH!
|
You'll never know what you're living for until you know what you're willing to die for. Never look back, something might be gaining on you.
|
|
|
threecats
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 04:48:04 PM |
|
Thumbs up zing... threecats can't read... [/quote]
Sad thing. You both ignore the question at hand: the seriousness of making a claim about a flaw affecting other coins, but then failing to demonstrate or clarify that claim. Instead you resort to ad hominem attacks against me for posing this question - and reposing the question, since no one is answering it. [/quote]
Not once did I resort to ad hominem attacks. The issue is that you feel you're owed an explanation when you're not. They can explain the flaw if and when they feel like it. If they do, I'm sure they'll issue a statement and update. I'd like to know what it is also, but I'm not pestering this board for an answer nor am I speculating that this unknown is or will contribute to a downfall in price. That's the "U" in FUD. [/quote]
Actually the uncertainty is clearly contributing to a downfall in price, that is quite obvious. My questions have nothing to with this price fall, nor are they FUD.
Where we differ is this: I believe that when one coin makes an assertion serious as this - that there may be a flaw affecting other coins - an clear and coherent explanation is owed. Not to me personally but to the communities affected by this assertion, the communities of all coins involved.
This is a simple matter of ethics, of reasonable ethical conduct.
|
|
|
|
TheDagger (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 04:56:08 PM |
|
There are still vulnerabilities until the patch kicks in.
Clearly not a good idea to tell the world about a potential exploit until after we are less exposed.
|
|
|
|
jorrr
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 04:57:39 PM |
|
There are still vulnerabilities until the patch kicks in.
Clearly not a good idea to tell the world about a potential exploit until after we are less exposed.
+1 Good job Dev team! You're dedication and work is awesome!
|
|
|
|
cryptodaknight
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 04:58:37 PM |
|
guys, seriously how long are you willing to wait for PosA? no fud. serious question. serious answers. if you say 1 year or 1 month or forever, it is not realistic view. remember that dev said 2 days ago it was almost ready to release within 12 hours.
What's with this guy? Seriously? Do you not think prices are pretty nice right now? Oh, maybe you bought into cloak at these prices, if you did then your just a foolish spewing bs since you would have known you bought on top, or if you did buy on top you know its going higher? What's the bitching for? I'm trying to figure out you concern, if you were here long time, then you made money, move on and sell and leave us alone. If not, and bought at these levels, then wait it out as thing are coming. If you didn't know all this then your a noob to cloakcoin, and just looking to get a quick return trading to BTC. If that is the case your just a troll, and please leave. Your obsession with trolling this thread is starting to look mental.
|
|
|
|
drizzle2405
Legendary
Offline
Activity: 1148
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 05:03:47 PM |
|
Thumbs up zing... threecats can't read...
Sad thing. You both ignore the question at hand: the seriousness of making a claim about a flaw affecting other coins, but then failing to demonstrate or clarify that claim. Instead you resort to ad hominem attacks against me for posing this question - and reposing the question, since no one is answering it.
Not once did I resort to ad hominem attacks. The issue is that you feel you're owed an explanation when you're not. They can explain the flaw if and when they feel like it. If they do, I'm sure they'll issue a statement and update. I'd like to know what it is also, but I'm not pestering this board for an answer nor am I speculating that this unknown is or will contribute to a downfall in price. That's the "U" in FUD.
Actually the uncertainty is clearly contributing to a downfall in price, that is quite obvious. My questions have nothing to with this price fall, nor are they FUD.
Where we differ is this: I believe that when one coin makes an assertion serious as this - that there may be a flaw affecting other coins - an clear and coherent explanation is owed. Not to me personally but to the communities affected by this assertion, the communities of all coins involved.
This is a simple matter of ethics, of reasonable ethical conduct.
Ethics? You are a daytrader. What the hell do you care about "ethics". You make your "profit" and move on to the next. Your goal is not about ethics. It's about profit. "Ethics"... lol
|
|
|
|
turner3d
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 76
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 11, 2014, 05:04:57 PM |
|
If there is a flaw in POS of this and other coins, the truly responsible thing to do would be to notify the devs of the other affected coins directly before releasing anything to the public. Simply releasing details of a flaw to the public after fixing it for only your own product is exactly what Cloudflare did with the Heartbleed OpenSSL bug.
I know there are a LOT of POS coins out there (both proof-of-stake and piece-of-shit), and contacting each and every dev individually would be nearly impossible, not to mention extremely time-consuming. I unfortunately don't have a constructive suggestion for what to do here, but this is factor that should be considered.
|
|
|
|
|