My latest transaction has been unconfirmed since 27.02.13
If it cant be fixed, can you remove it?
My username is: HotHubHD
Topic: Bitcoin MineField - 10%-2300% winings, fully automated, with cool technologies:) - page 10. (Read 88284 times)
March 15, 2013, 11:22:26 AM
March 13, 2013, 05:18:11 PM
service is offline atm,
my bitcoind is stuck at a block 225459 so transactions after that block didn't get registered.
An upgrade should fix it, I'm running a really old (debian package) version.
the site will be online in a few hours.
my bitcoind is stuck at a block 225459 so transactions after that block didn't get registered.
An upgrade should fix it, I'm running a really old (debian package) version.
the site will be online in a few hours.
ok, back online, let me know if your transaction didn't get registered and I'll credit your account manually.
oh, in case you've won something but can't cash out due to 'not enough funds' error, please wait 30ish minutes, funds have been sent to this new wallet, the transaction just needs to be confirmed.
March 13, 2013, 04:38:57 PM
service is offline atm,
my bitcoind is stuck at a block 225459 so transactions after that block didn't get registered.
An upgrade should fix it, I'm running a really old (debian package) version.
the site will be online in a few hours.
my bitcoind is stuck at a block 225459 so transactions after that block didn't get registered.
An upgrade should fix it, I'm running a really old (debian package) version.
the site will be online in a few hours.
ok, back online, let me know if your transaction didn't get registered and I'll credit your account manually.
March 13, 2013, 12:14:44 PM
service is offline atm,
my bitcoind is stuck at a block 225459 so transactions after that block didn't get registered.
An upgrade should fix it, I'm running a really old (debian package) version.
the site will be online in a few hours.
my bitcoind is stuck at a block 225459 so transactions after that block didn't get registered.
An upgrade should fix it, I'm running a really old (debian package) version.
the site will be online in a few hours.
March 13, 2013, 12:12:48 PM
I'm really interested to see more details from my referrals
yeah yeah will implement it
I'm finishing another project these days, in a month or two I'll be able to get back to this..
user-5125f42adf7b95cc10034bba
just so this isn't a last message in a thread, we've resolved this
February 21, 2013, 05:19:55 AM
I'm really interested to see more details from my referrals
yeah yeah will implement it
I'm finishing another project these days, in a month or two I'll be able to get back to this..user-5125f42adf7b95cc10034bba
February 18, 2013, 06:53:39 AM
I'm really interested to see more details from my referrals
yeah yeah will implement it
I'm finishing another project these days, in a month or two I'll be able to get back to this.. 
February 18, 2013, 04:27:21 AM
I'm really interested to see more details from my referrals
February 17, 2013, 10:29:40 AM
i dont understand how i lost 3 - 4 btc playing this.....
waste of btc.
waste of btc.
February 14, 2013, 03:27:33 PM
hey, yeah I'm aware of this, I do know what https is and what it is for
February 14, 2013, 08:21:09 AM
Hello,
I would like to report a possible security hole in the current scheme of things.
The idea to use only 'url with secret' for logging in is neat but not entirely safe because the web server uses plain http with no encryption.
Let's say you open the site for the first time and it gives you secret like http://minefield.bitcoinlab.org/?secret=fngrOdO23tDOTuPW
Then you deposit some btc.
If someone is sniffing the traffic it is fairly easy to extract the GET /?secret=fngrOdO23tDOTuPW string from the HTTP request. Then he needs simply to open the site with that secret and he can withdraw the btc to address of his choice.
I can mention two solutions.
1/ get a https certificate and the run the website over ssl/tls. This will resolve the sniffing problem since all traffic would be encrypted.
2/ Make withdraw only possible to addresses from which deposits were received. But on second thought this is not very secure either. A hacker could break into your account, deposit minimal amount of btc and after the deposit is confirmed (and the sending address accepted as viable for withdraw) the hacker request the whole amount to his address.
Best~
I would like to report a possible security hole in the current scheme of things.
The idea to use only 'url with secret' for logging in is neat but not entirely safe because the web server uses plain http with no encryption.
Let's say you open the site for the first time and it gives you secret like http://minefield.bitcoinlab.org/?secret=fngrOdO23tDOTuPW
Then you deposit some btc.
If someone is sniffing the traffic it is fairly easy to extract the GET /?secret=fngrOdO23tDOTuPW string from the HTTP request. Then he needs simply to open the site with that secret and he can withdraw the btc to address of his choice.
I can mention two solutions.
1/ get a https certificate and the run the website over ssl/tls. This will resolve the sniffing problem since all traffic would be encrypted.
2/ Make withdraw only possible to addresses from which deposits were received. But on second thought this is not very secure either. A hacker could break into your account, deposit minimal amount of btc and after the deposit is confirmed (and the sending address accepted as viable for withdraw) the hacker request the whole amount to his address.
Best~
hey, yeah I'm aware of this, I do know what https is and what it is for
I don't think that this is very important, but I do plan to switch to https soon.
and on why I don't think its important:
the number of local networks being sniffed by attackers interested in bitcoin is super small, people that know what https and sniffing is, will make sure that they have a secure connection if they care to, and people that don't, will probably get owned anyway. so I'm maybe saving one person in a few millions, and this website didn't receive that much GET requests yet. and statistically, I'm saving them around 0.05 bitcoin...
but still, yes, https, soon.
PS
I may sound too dismissive, that's not the idea, thanks for reporting
February 14, 2013, 07:59:17 AM
Hello,
I would like to report a possible security hole in the current scheme of things.
The idea to use only 'url with secret' for logging in is neat but not entirely safe because the web server uses plain http with no encryption.
Let's say you open the site for the first time and it gives you secret like http://minefield.bitcoinlab.org/?secret=fngrOdO23tDOTuPW
Then you deposit some btc.
If someone is sniffing the traffic it is fairly easy to extract the GET /?secret=fngrOdO23tDOTuPW string from the HTTP request. Then he needs simply to open the site with that secret and he can withdraw the btc to address of his choice.
I can mention two solutions.
1/ get a https certificate and the run the website over ssl/tls. This will resolve the sniffing problem since all traffic would be encrypted.
2/ Make withdraw only possible to addresses from which deposits were received. But on second thought this is not very secure either. A hacker could break into your account, deposit minimal amount of btc and after the deposit is confirmed (and the sending address accepted as viable for withdraw) the hacker request the whole amount to his address.
Best~
I would like to report a possible security hole in the current scheme of things.
The idea to use only 'url with secret' for logging in is neat but not entirely safe because the web server uses plain http with no encryption.
Let's say you open the site for the first time and it gives you secret like http://minefield.bitcoinlab.org/?secret=fngrOdO23tDOTuPW
Then you deposit some btc.
If someone is sniffing the traffic it is fairly easy to extract the GET /?secret=fngrOdO23tDOTuPW string from the HTTP request. Then he needs simply to open the site with that secret and he can withdraw the btc to address of his choice.
I can mention two solutions.
1/ get a https certificate and the run the website over ssl/tls. This will resolve the sniffing problem since all traffic would be encrypted.
2/ Make withdraw only possible to addresses from which deposits were received. But on second thought this is not very secure either. A hacker could break into your account, deposit minimal amount of btc and after the deposit is confirmed (and the sending address accepted as viable for withdraw) the hacker request the whole amount to his address.
Best~
February 10, 2013, 01:23:09 PM
Thank you.
February 09, 2013, 08:09:18 AM
I sent 0.025 BTC to an address that was generated for me (you can see here: 1EY6boTD4jCY9CNdfP4i8BMioF1m4NYJ7b) but it never went through, it wasn't every added to my account...
What should I do?
What should I do?
you are right, I'm not sure what happened, sorry about that.
the transaction wasn't registered by the system.. I've credited your account manually and I'll investigate.
February 08, 2013, 09:25:11 PM
I sent 0.025 BTC to an address that was generated for me (you can see here: 1EY6boTD4jCY9CNdfP4i8BMioF1m4NYJ7b) but it never went through, it wasn't every added to my account...
What should I do?
What should I do?
February 05, 2013, 05:24:26 PM
hold on, it might be because I lack 4 confirmations on my deposit? just noticed that note
edit: thank you for your quick reaction though, gives me a lot more confidence in your service
edit: thank you for your quick reaction though, gives me a lot more confidence in your service
don't worry your btc is safe
it still shouldn't tell you that the address is invalid, I've updated a code a bit, try it now. (reload page)
and I've changed the confirmation requirement to 2, so you'll be able to cash out sooner.
February 05, 2013, 05:01:30 PM
hold on, it might be because I lack 4 confirmations on my deposit? just noticed that note
edit: thank you for your quick reaction though, gives me a lot more confidence in your service
edit: thank you for your quick reaction though, gives me a lot more confidence in your service
February 05, 2013, 04:53:08 PM
I keep getting "invalid address" when I'm trying to withdraw. I tried with several addresses. I'm 100% sure these are working addresses. What's the matter there?
strange, can you give me your username and an address you are trying to use?
February 05, 2013, 04:50:24 PM
I keep getting "invalid address" when I'm trying to withdraw. I tried with several addresses. I'm 100% sure these are working addresses. What's the matter there?
February 04, 2013, 01:35:07 PM
Just a friendly tip: It's funds
haha thanks
Jump to: