So do you believe that we get our coins back this year ?
The process of receiving them will start this week. Neo & Bee have no liability, this is me as an individual helping you out to ensure you get your BTC back, can I expect a thank you card when its completed or continued demands from you?
I guess this also applies here. But hey, would be great news, if it'd be true. |
|
|
|
The update that I had planned for today shall now be made at noon (GMT+2) tomorrow. Sincere apologies for this, however the information that can be provided tomorrow will be much more detailed than previously expected.
Thanks for the update on the update. Should we expect this next update to finally give us info regarding the actual problem/solution? My guess is that it will be already known information and they'll most likely tell us, that we won't get our coins back this year. |
|
|
|
Guess there will be no update as promised, no excuse, no update, no btc.  Since this is an update about WeExchange, US hours are applicable. Do you really believe that? |
|
|
|
I think the chance is high the divs are caught in weexchange wallet and owners have to wait for the problems to be solved.
I think by now its quite clear that there are no technical issues with WeEx's wallet. |
|
|
|
Or another option could have been to sell all the coins on the market, which should cause the market to plummet a few hundred dollars as people would panic and think the bubble's bursting, wait an hour or two and then buy the exact same number of bitcoins back at the lower & falling price. Ukyo pockets the cash difference then releases the same number of bitcoins back to the community... win win scenario!
total market volume (24h) ฿ 158604.130 At this moment we know that Ukyo was handling at most a couple thousand BTC. That's definitely not enough to cause a panic. But it's still possible that he thought bitcoin was at an all-time high and sold the coins hoping the price would drop. Unfortunately it did not and somehow "technical issues" with the bitcoind occurred. But also that is just speculation and meant for entertainment only. |
|
|
|
jesus fuck this isnt basic-mining chill your pants
I will not chill my pants. I am waiting for my PT shares for half a month now and haven't received a satoshi of the divivends up until now. Also at no point did Garrett state that he will plot historic data from before now. But that's exactly the kind of information that we need to verify the last dividend. It is absolutely not difficult to post the payout address and possibly sign a message with it, to verify it's his. One could assume that he isn't posting the address because he wasn't honest with us. |
|
|
|
Also, COG.F and COG.F2 will be online today. Please create accounts at Havelock with the same email addresses used on BTC-TC and your shares will be deposited within one business day.
Cheers
I am still waiting for my PT shares. Hello all, I do aim to resolve all of the issues at hand, and I apologize for this, but it is simply not feasible for me to read the forum more than once a day every day. You all ask a lot of me, and I ask to please be more patient in waiting for responses from me, so long as I do answer in a timely manner. I have come up with a plan to satisfy all of these questions. Do do this, we're going to set up a way to view realtime and historic charts of Cognitive's hashrate, live payout address & balance, and possibly a live video feed of the miners, which will be available at http://cognitivemining.com/chartsI have not been logging hashrate so far, because there has been no demand for it. All of these things will be up and running by January. I do understand the increased concern for the transparency due to the increased value of our coins, and I respect that highly. Moving to a pool where we have a dedicated payout address is the simplest and most important step to take, so I will do this before the next dividend, so we can start out the next dividend-week with the same payout address. Then there will be full transparency with the financials, because as we all know and love, bitcoin doesn't lie  We want you to verify the last dividend payment. Your intent to verify upcoming dividends is nice, but not sufficient. Last dividend was terribly low, so you should understand why we want to verify it. |
|
|
|
BTW You're accusing someone of stealing when the only thing that's actually public is we cannot move our funds out. That's bad, no question, but it doesn't prove theft.
I've commented enough on what's being done, as much as I can do, and if you have money stuck then either hire a lawyer and do as I suggested or give Neo/ukyo time to resolve this. Neo have said there will be more information on Friday.
That's hardly derailing the thread. That's how people should deal with the situation, not posting what lophie did.
Let's say Ukyo continues to prolong the process? At which point should we take actions in your opinion? A few weeks? Months? Years? It also doesn't make sense that everyone (who feels like it) contacts their lawyers to explore legal options. But I agree that we should get back to topic. |
|
|
|
I wonder about the G.ASICMINER dividends that haven't been paid yet.
Most likely Ukyo has "technical issues" paying the dividends. |
|
|
|
Please remove quotes and text and stop messing up the order book. |
|
|
|
|
For the $2m they want to collect, they have not delivered enough information, like estimated profits, share holder structure etc.
Also they're asking for $2m, that should be reason enough not to invest.
|
|
|
|
Take it easy lophie. Either lots of people are in this together or just perhaps it isn't a scam and the right things are being done behind the scenes to try and help. Meanwhile, accusations and personal attacks which had started crossing the line were, at best, not helpful.
It's frustrating having to wait but that's because there is a right way to do things, and that's what is happening. It can't be done in public however much people want. The only important thing is having access to our funds again.
So step away, take a deep breath, and try and be objective. You have a major company working on this on your behalf - that hardly ever happens when trouble strikes. We need to let them get on with it.
This is a much to one-sided opinion. We can't just sit on our hands and wait. We have to group up and discuss other options. If that is beeing censored by the admins/mods, that would be horrible and not acceptable. |
|
|
|
from IRC november 27: ... [01:48] <dexX7> hm.. let's use timeframe 0-2 weeks, 2-6 weeks, 6-more weeks? [01:48] <@Ukyo> CuWireBeard: at this point, I would ask that until the next big announcement is made that we wait and see how that turns out [01:49] <@Ukyo> i dunno 3~4 ? ... So we're facing another holiday where he can make more excuses, which makes it 4-6 weeks. That's absolutely unacceptable. |
|
|
|
The old bonds product you linked is no longer available - I don't want to confuse people. If I understand correctly, you want to do the same thing as with BTC-EQTY but pay out a flat interest. What is your rescue plan in case your holdings dramatically loose value? How are you going to repay creditors? |
|
|
|
News: If you used your password to login between 06:00 Dec 1 UTC and 20:00 Dec 2 UTC, then your password may have been captured in a man-in-the-middle attack, and you should change your password here and wherever else you used it. If you were only logged in via the "remember me" feature, then you're OK. -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Here's what we think happened:
8-14 hours ago, an attacker used a flaw in the forum's AnonymousSpeech registrar to change the forum's DNS to point to 108.162.197.161 (exact details unknown). Sirius noticed this 8 hours ago and immediately transferred bitcointalk.org to a different registrar. However, such changes take about 24 hours to propagate.
Because the HTTPS protocol is pretty terrible, this alone could have allowed the attacker to intercept and modify encrypted forum transmissions, allowing them to see passwords sent during login, authentication cookies, PMs, etc. Your password only could have been intercepted if you actually entered it while the forum was affected. I invalidated all security codes, so you're not at risk of having your account stolen if you logged in using the "remember me" feature without actually entering your password.
For the next ~20 hours, you should only log into the forum if you're quite sure that you're talking to the correct server. This can be done by adding '109.201.133.195 bitcointalk.org' to your hosts file (remember to remove it later!), or by using some browser plugin to ensure that you're talking to the server with TLS certificate SHA1 fingerprint of:
29:0E:CC:82:2B:3C:CE:0A:73:94:35:A0:26:15:EC:D3:EB:1F:46:6B
Simultaniously, the forum has been the target of a massive DDoS attack. These two events are probably related, though I'm not yet sure why an attacker would do both of these things at once.
-----BEGIN PGP SIGNATURE-----
iF4EAREIAAYFAlKb2nkACgkQxlVWk9q1kefhTwD+Ni5k7CUrHjvzG29wO3Gx4Am+
MV5tdw8zE1AAWvbstt8BAIrndOXCYmawoXN+VeSZkLXHnCyQbR8IOftQnpl2aXYs
=465T
-----END PGP SIGNATURE-----
I think the end date in the news is wrong, it seems to be in the future. Or is that a precaution regarding DNS propagation? |
|
|
|
|
Show Posts
