Can you confirm that you have DMC's claim of 1000 asicminer on your list?
Yes. I confirm. 
Topic: ASICMINER: Entering the Future of ASIC Mining by Inventing It - page 1309. (Read 3917468 times)
October 16, 2012, 12:10:59 AM
October 15, 2012, 10:27:36 PM
watching 
October 15, 2012, 09:59:58 PM
Would it be possible to purchase shares now?
Buying ASICMINER shares for 25% of the last traded price. October 15, 2012, 07:40:59 PM
Sent in my e-mail
October 15, 2012, 06:25:28 PM
Would it be possible to purchase shares now?
October 15, 2012, 05:36:47 PM
Daily Update
Till now we have collected the claims from 45 shareholders. We are still in waiting of the replies from GLBSE.
Shareholders who see this reply but haven't claimed, please contact us via this e-mail address: ([email protected]) and send us
your number of shares and your Bitcoin address for receiving dividends. Please annotate that they are ASICMINER shares to avoid confusion with MU or MOORE shares. You could accompany them with any evidence you think is OK to provide. It is highly recommended that you use an address that you have its private key. By that, you may enjoy more facilities provided by our future automatic migrating platform.
Till now we have collected the claims from 45 shareholders. We are still in waiting of the replies from GLBSE.
Shareholders who see this reply but haven't claimed, please contact us via this e-mail address: ([email protected]) and send us
your number of shares and your Bitcoin address for receiving dividends. Please annotate that they are ASICMINER shares to avoid confusion with MU or MOORE shares. You could accompany them with any evidence you think is OK to provide. It is highly recommended that you use an address that you have its private key. By that, you may enjoy more facilities provided by our future automatic migrating platform.
friedcat... so now 22, one half, of the good non-optimal estimation of 45 days until you have the asics are over. Did you contact the supplier and have some new info about the status in the meanwhile? I mean if you were rights its only 23 days now until it maybe could start. 
According to nearest update of foundry, we have past the mask-set process and are in queue of wafer process. We will keep the shareholders updated whenever we reach any new milestones.Friedcat, perhaps it is time to remove "[GLBSE]" from the topic.
[GLBSE] is removed from the title. Also are other two assets of my responsibility. Thanks.Can you confirm that you have DMC's claim of 1000 asicminer on your list?
October 15, 2012, 01:28:39 PM
@friedcat
I have 660 shares according to the memory of the human brain. Should I provide the account_history.csv of GLBSE? Although that's not an up-to-date information.
I have 660 shares according to the memory of the human brain. Should I provide the account_history.csv of GLBSE? Although that's not an up-to-date information.
October 15, 2012, 12:35:06 PM
I bought
[email protected]@2012-10-04 10:49:34 and [email protected]@2012-10-04 10:49:35
If you got a bit more BTC than you expected you might have me to thank!
[email protected]@2012-10-04 10:49:34 and [email protected]@2012-10-04 10:49:35
If you got a bit more BTC than you expected you might have me to thank!
October 15, 2012, 07:26:16 AM
i may or may not have between 100 and 300 shares, depending on if the orders got filled.
October 15, 2012, 06:09:07 AM
Daily Update
Till now we have collected the claims from 45 shareholders. We are still in waiting of the replies from GLBSE.
Shareholders who see this reply but haven't claimed, please contact us via this e-mail address: ([email protected]) and send us
your number of shares and your Bitcoin address for receiving dividends. Please annotate that they are ASICMINER shares to avoid confusion with MU or MOORE shares. You could accompany them with any evidence you think is OK to provide. It is highly recommended that you use an address that you have its private key. By that, you may enjoy more facilities provided by our future automatic migrating platform.
Till now we have collected the claims from 45 shareholders. We are still in waiting of the replies from GLBSE.
Shareholders who see this reply but haven't claimed, please contact us via this e-mail address: ([email protected]) and send us
your number of shares and your Bitcoin address for receiving dividends. Please annotate that they are ASICMINER shares to avoid confusion with MU or MOORE shares. You could accompany them with any evidence you think is OK to provide. It is highly recommended that you use an address that you have its private key. By that, you may enjoy more facilities provided by our future automatic migrating platform.
friedcat... so now 22, one half, of the good non-optimal estimation of 45 days until you have the asics are over. Did you contact the supplier and have some new info about the status in the meanwhile? I mean if you were rights its only 23 days now until it maybe could start.
According to nearest update of foundry, we have past the mask-set process and are in queue of wafer process. We will keep the shareholders updated whenever we reach any new milestones.Friedcat, perhaps it is time to remove "[GLBSE]" from the topic.
[GLBSE] is removed from the title. Also are other two assets of my responsibility. Thanks. 
October 14, 2012, 06:26:27 PM
Quote
Your GLBSE account has been processed for bitcoin. The next step will be to send you information about your assets, and to provide this information to issuers (if you agreed) allowing you to continue your relationship with your issuers.
Received this email couple of hours ago.
Strangely enough I did not have any BTC associated with this account
I did receive my BTC for the other account I had d011471253c62b762bcf3e70a3ff12d249804ccaf202173cdb65c9c7edfe8c70 Date: 13/10/2012 23:50 but have not yet received an email
I just hope I did not screw up my email on that one when I entered it....
I received my BTC for my account, but did not get an email either.
October 14, 2012, 02:35:55 PM
Quote
Your GLBSE account has been processed for bitcoin. The next step will be to send you information about your assets, and to provide this information to issuers (if you agreed) allowing you to continue your relationship with your issuers.
Received this email couple of hours ago.
Strangely enough I did not have any BTC associated with this account
I did receive my BTC for the other account I had d011471253c62b762bcf3e70a3ff12d249804ccaf202173cdb65c9c7edfe8c70 Date: 13/10/2012 23:50 but have not yet received an email
I just hope I did not screw up my email on that one when I entered it....
October 14, 2012, 07:44:21 AM
friedcat... so now 22, one half, of the good non-optimal estimation of 45 days until you have the asics are over. Did you contact the supplier and have some new info about the status in the meanwhile? I mean if you were rights its only 23 days now until it maybe could start.
October 14, 2012, 07:10:50 AM
Daily Update
We haven't got contacted from GLBSE yet.
Before we receive the shareholders information, we will continue collecting them.
We haven't got contacted from GLBSE yet.
Before we receive the shareholders information, we will continue collecting them.
October 13, 2012, 08:13:12 PM
I got the money i had in my glbse-account sent to the address i specified now. Not exactly but the most. 0.6BTC to be exact while i had some more digits at the end.
So friedcat did you get any infos about my shares yet too maybe?
So friedcat did you get any infos about my shares yet too maybe?
October 13, 2012, 06:03:34 PM
I thought till now that the api-keys are sent encrypted with ssl. But i didnt use the api of glbse till now. I planned to do but now im happy that i didnt spend the time to creat a bot yet. It would be lost time.
MtGox has an interesting approch for api-keys. From the start there is now api key. But you can create more than one and you can give each keys right. So you can create on only for trading but it cant withdraw. So you are save against your api used to steal your money.
If the connections to an https-server through curl isnt encrypted then maybe setup the bot at a website that has ssl themself. Then use the ssl with curl to gain security.
MtGox has an interesting approch for api-keys. From the start there is now api key. But you can create more than one and you can give each keys right. So you can create on only for trading but it cant withdraw. So you are save against your api used to steal your money.
If the connections to an https-server through curl isnt encrypted then maybe setup the bot at a website that has ssl themself. Then use the ssl with curl to gain security.
The API key is in the URL. The URL in SSL _is_ encrypted, but SSL is not 100% secure and there are known attacks against it (although, implementation specific ones). The problem is, if you're using the API keys non-locally (such as on a vps or a dedi), you have a gaping security hole. I'm not comfortable with how GLBSE implemented API keys.
October 13, 2012, 05:15:07 PM
I thought till now that the api-keys are sent encrypted with ssl. But i didnt use the api of glbse till now. I planned to do but now im happy that i didnt spend the time to creat a bot yet. It would be lost time.
MtGox has an interesting approch for api-keys. From the start there is now api key. But you can create more than one and you can give each keys right. So you can create on only for trading but it cant withdraw. So you are save against your api used to steal your money.
If the connections to an https-server through curl isnt encrypted then maybe setup the bot at a website that has ssl themself. Then use the ssl with curl to gain security.
MtGox has an interesting approch for api-keys. From the start there is now api key. But you can create more than one and you can give each keys right. So you can create on only for trading but it cant withdraw. So you are save against your api used to steal your money.
If the connections to an https-server through curl isnt encrypted then maybe setup the bot at a website that has ssl themself. Then use the ssl with curl to gain security.
October 13, 2012, 04:12:47 PM
Friedcat, perhaps it is time to remove "[GLBSE]" from the topic.
October 13, 2012, 03:11:15 PM
You mean the api worked with username and password? No api-key? But even when... who should the attacker get the logindetails? I mean most users probably hadnt used 2fa so attacker could simply login and claim the shares. But first he need the logindetails. Where should he get this?
Or does he mean that nefario could use user-pass to claim the shares for himself?
Or does he mean that nefario could use user-pass to claim the shares for himself?
API keys are not secure.
October 13, 2012, 08:43:17 AM
Or does he mean that nefario could use user-pass to claim the shares for himself?
If user's balances are not signed with the user's private key and the server's private key to bear witness that both agreed as to the balance, and to prevent either from changing it without the approval of the other, they yes, of course, it is totally just an ephemeral value maybe in a database or something and totally vulnerable to all kinds of nefariousness.
That is why you should always sign your balances and not accept any you have not signed as binding until you have signed them.
-MarkM-
Jump to: