Search content
Sort by
Showing 20 of 22 results by Bit LC Inc.
Re: [98 Gh/s] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP
Bit LC Inc. will, effective immediately, close down all services - read more at https://www.bitlc.net/
Re: [98 Gh/s] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP
Keep mining if you want to be honest and return the coins, or deposit a few coins using the wallet-service.
Or just register a new account, it's totally up to you.
I appreciate your honesty tho.
--
Regards, Jim
Bit LC Inc.
Or just register a new account, it's totally up to you.
I appreciate your honesty tho.
--
Regards, Jim
Bit LC Inc.
Re: [98 Gh/s] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP
Hi!
It's prob. because of the "leap-second" bug we encountered a few months back (check our twitter for more info on that), which made deposits to your account be processed more then once. (MySQL hung and became really unstable/unresponsive) If you made a outgoing payment during that bug, it will have set your balance to a negative amount to compensate for the "extra" coins your received due to the "extra" deposits.
There is only THREE accounts with a negative balance, and judging by your nick i can figure out which ones yours - I can reset your balance to zero if you want to.
--
Regards, Jim
Bit LC Inc.
It's prob. because of the "leap-second" bug we encountered a few months back (check our twitter for more info on that), which made deposits to your account be processed more then once. (MySQL hung and became really unstable/unresponsive) If you made a outgoing payment during that bug, it will have set your balance to a negative amount to compensate for the "extra" coins your received due to the "extra" deposits.
There is only THREE accounts with a negative balance, and judging by your nick i can figure out which ones yours - I can reset your balance to zero if you want to.
--
Regards, Jim
Bit LC Inc.
Re: Pool Operators - PLEASE BAN & BLOCK GPUMAX getwork/proxy access to your pool
As confirmed above, it was GPUMAX (or pirate40, to be precise - even tho I have no real proof for that) that was pool-hopping us, using his own account (registered with a fake e-mail of course).
Re: [98 Gh/s] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP
I'm only going to address the 4th point, as it's related to the stale/eff ratio.
4. Taken directly from our poolserver a few hours ago, associated with your worker, today:
If you have any more questions or similar on your mind, contact me using IRC or e-mail.
This "issue" is closed and it adds unnecessary posts to the thread.
4. Taken directly from our poolserver a few hours ago, associated with your worker, today:
Quote
jine@jine:~$ cat ipscrub | xargs -L1 host
205.233.163.109.in-addr.arpa domain name pointer gorz.torservers.net.
36.147.48.199.in-addr.arpa domain name pointer tor-exit-router36-readme.formlessnetworking.net.
200.233.163.109.in-addr.arpa domain name pointer wau.torservers.net.
Host 130.211.32.178.in-addr.arpa. not found: 3(NXDOMAIN)
132.13.120.74.in-addr.arpa domain name pointer bouazizi.torservers.net.
60.171.76.69.in-addr.arpa domain name pointer cpe-69-76-171-60.kc.res.rr.com.
150.15.120.74.in-addr.arpa domain name pointer raskin.torservers.net.
Host 243.73.110.208.in-addr.arpa. not found: 3(NXDOMAIN)
20.86.120.79.in-addr.arpa domain name pointer stargrave.org.
1.178.126.94.in-addr.arpa domain name pointer tor-exit01.solidonetworks.com.
45.147.48.199.in-addr.arpa domain name pointer tor-exit-router45-readme.formlessnetworking.net.
224.53.141.62.in-addr.arpa domain name pointer tor1.digineo.de.
78.216.192.173.in-addr.arpa domain name pointer 173.192.216.78-static.reverse.softlayer.com.
102.189.44.96.in-addr.arpa domain name pointer herngaard.torservers.net.
50.245.167.46.in-addr.arpa domain name pointer torsrvc.snydernet.net.
Host 140.211.32.178.in-addr.arpa. not found: 3(NXDOMAIN)
40.147.48.199.in-addr.arpa domain name pointer tor-exit-router40-readme.formlessnetworking.net.
41.147.48.199.in-addr.arpa domain name pointer tor-exit-router41-readme.formlessnetworking.net.
Host 18.82.110.208.in-addr.arpa. not found: 3(NXDOMAIN)
21.226.47.96.in-addr.arpa domain name pointer bolobolo2.torservers.net.
42.244.226.83.in-addr.arpa domain name pointer c-2af4e253.09-8-686c6d10.cust.bredbandsbolaget.se.
133.227.130.37.in-addr.arpa domain name pointer torland1-this.is.a.tor.exit.server.torland.is.
Host 92.32.173.46.in-addr.arpa. not found: 3(NXDOMAIN)
73.226.237.80.in-addr.arpa domain name pointer tor3.anonymizer.ccc.de.
66.164.14.67.in-addr.arpa domain name pointer 67-14-164-66.kcnap.net.
74.226.237.80.in-addr.arpa domain name pointer tor4.anonymizer.ccc.de.
76.226.237.80.in-addr.arpa domain name pointer tor6.anonymizer.ccc.de.
29.191.166.108.in-addr.arpa domain name pointer tor-exit.hexhost.net.
164.181.247.77.in-addr.arpa domain name pointer rainbowwarrior.torservers.net.
165.181.247.77.in-addr.arpa domain name pointer politkovskaja.torservers.net.
Host 146.137.195.69.in-addr.arpa. not found: 3(NXDOMAIN)
205.233.163.109.in-addr.arpa domain name pointer gorz.torservers.net.
36.147.48.199.in-addr.arpa domain name pointer tor-exit-router36-readme.formlessnetworking.net.
200.233.163.109.in-addr.arpa domain name pointer wau.torservers.net.
Host 130.211.32.178.in-addr.arpa. not found: 3(NXDOMAIN)
132.13.120.74.in-addr.arpa domain name pointer bouazizi.torservers.net.
60.171.76.69.in-addr.arpa domain name pointer cpe-69-76-171-60.kc.res.rr.com.
150.15.120.74.in-addr.arpa domain name pointer raskin.torservers.net.
Host 243.73.110.208.in-addr.arpa. not found: 3(NXDOMAIN)
20.86.120.79.in-addr.arpa domain name pointer stargrave.org.
1.178.126.94.in-addr.arpa domain name pointer tor-exit01.solidonetworks.com.
45.147.48.199.in-addr.arpa domain name pointer tor-exit-router45-readme.formlessnetworking.net.
224.53.141.62.in-addr.arpa domain name pointer tor1.digineo.de.
78.216.192.173.in-addr.arpa domain name pointer 173.192.216.78-static.reverse.softlayer.com.
102.189.44.96.in-addr.arpa domain name pointer herngaard.torservers.net.
50.245.167.46.in-addr.arpa domain name pointer torsrvc.snydernet.net.
Host 140.211.32.178.in-addr.arpa. not found: 3(NXDOMAIN)
40.147.48.199.in-addr.arpa domain name pointer tor-exit-router40-readme.formlessnetworking.net.
41.147.48.199.in-addr.arpa domain name pointer tor-exit-router41-readme.formlessnetworking.net.
Host 18.82.110.208.in-addr.arpa. not found: 3(NXDOMAIN)
21.226.47.96.in-addr.arpa domain name pointer bolobolo2.torservers.net.
42.244.226.83.in-addr.arpa domain name pointer c-2af4e253.09-8-686c6d10.cust.bredbandsbolaget.se.
133.227.130.37.in-addr.arpa domain name pointer torland1-this.is.a.tor.exit.server.torland.is.
Host 92.32.173.46.in-addr.arpa. not found: 3(NXDOMAIN)
73.226.237.80.in-addr.arpa domain name pointer tor3.anonymizer.ccc.de.
66.164.14.67.in-addr.arpa domain name pointer 67-14-164-66.kcnap.net.
74.226.237.80.in-addr.arpa domain name pointer tor4.anonymizer.ccc.de.
76.226.237.80.in-addr.arpa domain name pointer tor6.anonymizer.ccc.de.
29.191.166.108.in-addr.arpa domain name pointer tor-exit.hexhost.net.
164.181.247.77.in-addr.arpa domain name pointer rainbowwarrior.torservers.net.
165.181.247.77.in-addr.arpa domain name pointer politkovskaja.torservers.net.
Host 146.137.195.69.in-addr.arpa. not found: 3(NXDOMAIN)
If you have any more questions or similar on your mind, contact me using IRC or e-mail.
This "issue" is closed and it adds unnecessary posts to the thread.
Re: [98 Gh/s] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP
One question tho, why aren't you mining at your own pool, with your FPGAs?
EDIT: Funny, i just an e-mail AND a PM with people asking the same question. Things doesn't add upp here...
EDIT: Funny, i just an e-mail AND a PM with people asking the same question. Things doesn't add upp here...
Re: [98 Gh/s] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP
So you're claiming that you're mining with a FPGA cluster of far over 600gh? Jikes, that's impressive! Kudos for that!
2. The botnet detection is based upon the effeciency (getworks vs. stales in this case), amount of connections, source of connections, amount of unique IP's, IP2location for those IP's and much more I'm not going to publicly announce, as it in fact are there for a reason.
3. Yes, but stales do consume and waste bandwidth - the point i was trying to make was that it was no "small" operation, it was a massive spike in hashrate, connections, traffic, getworks and stales.
4. I really doubt that, especially as you're using TOR (might i ask why?) for the miners (which is one of the things our botnet detection adds points for).
5. We're working on that, see my posts above. I'm well aware of that. We've haven't just had the time (and money, as time is money) to implement it...
--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net
EDIT:
2. The botnet detection is based upon the effeciency (getworks vs. stales in this case), amount of connections, source of connections, amount of unique IP's, IP2location for those IP's and much more I'm not going to publicly announce, as it in fact are there for a reason.
3. Yes, but stales do consume and waste bandwidth - the point i was trying to make was that it was no "small" operation, it was a massive spike in hashrate, connections, traffic, getworks and stales.
4. I really doubt that, especially as you're using TOR (might i ask why?) for the miners (which is one of the things our botnet detection adds points for).
5. We're working on that, see my posts above. I'm well aware of that. We've haven't just had the time (and money, as time is money) to implement it...
--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net
EDIT:
Quote
I am also very disappointed that you have basically told me you are going to steal the funds that I have already accumulated for work performed simply because your pool can't handle my hashrate.
I've sent you an e-mail regarding that, we can take that privately.Re: Pool Operators - PLEASE BAN & BLOCK GPUMAX getwork/proxy access to your pool
I can write the short version of the story:
* I detected a huge increase in hashrate on our pool, and traced it back to GPUMAX (nothing strange there, so far, I've had heard about the service before)
* I checked which account it was mining against (and found that it was a private account by pirate40 (or who ever was/is behind GPUMAX))
* All mining-activity related to that account came directly from the same IP-addresses as GPUMAX used at the time.
* I spoke with pirate40 (I guess?) a year ago or so, in their official IRC channel regarding what was going on, and why he was using his "own" account to mine at our pool, with GPUMAX resources
* He pretty much asked me to fuck off and mind my own business, as he said he didn't do anything "wrong", it was some "load balancing between multiple pools"-feature he said.
* ... which still didn't explain why he was using his own account, and sending the earned funds directly to him self (Or well, his "personal" wallet, i think the IP was showing up on blockchain.info) - Not to anything related to GPUMAX as far as i could see.
* He wrote a few lines privately to me on IRC "trying" to explain "again", but at this time i was so suspicious that i doubted every word he said.
* I asked him a day later, again on exactly what was going on, and he mentioned the same thing about it was a load-balancing between pools - but i didn't really get how exactly his account and his IP became involved in everything - i asked why he was using his "own" account for it - but never got any response.
* I suspected, back then, that he was taking a bit of "extra" hashrate and mined (pool-hopped) to compensate for the 105% earnings (or whatever it was) and to earn some for himself. (Which i honestly still think)
* I issued a firewall ban against all EC2 nodes i could find, associated with GPUMAX, and disabled all related accounts.
Those bans maybe not be effective anymore, things might have changed during the past years, but i know that he disabled https://www.bitlc.net (Bitcoins.lc) on GPUMAX and posted an announcement of it here on the forums.
I never heard from him again.
--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net
* I detected a huge increase in hashrate on our pool, and traced it back to GPUMAX (nothing strange there, so far, I've had heard about the service before)
* I checked which account it was mining against (and found that it was a private account by pirate40 (or who ever was/is behind GPUMAX))
* All mining-activity related to that account came directly from the same IP-addresses as GPUMAX used at the time.
* I spoke with pirate40 (I guess?) a year ago or so, in their official IRC channel regarding what was going on, and why he was using his "own" account to mine at our pool, with GPUMAX resources
* He pretty much asked me to fuck off and mind my own business, as he said he didn't do anything "wrong", it was some "load balancing between multiple pools"-feature he said.
* ... which still didn't explain why he was using his own account, and sending the earned funds directly to him self (Or well, his "personal" wallet, i think the IP was showing up on blockchain.info) - Not to anything related to GPUMAX as far as i could see.
* He wrote a few lines privately to me on IRC "trying" to explain "again", but at this time i was so suspicious that i doubted every word he said.
* I asked him a day later, again on exactly what was going on, and he mentioned the same thing about it was a load-balancing between pools - but i didn't really get how exactly his account and his IP became involved in everything - i asked why he was using his "own" account for it - but never got any response.
* I suspected, back then, that he was taking a bit of "extra" hashrate and mined (pool-hopped) to compensate for the 105% earnings (or whatever it was) and to earn some for himself. (Which i honestly still think)
* I issued a firewall ban against all EC2 nodes i could find, associated with GPUMAX, and disabled all related accounts.
Those bans maybe not be effective anymore, things might have changed during the past years, but i know that he disabled https://www.bitlc.net (Bitcoins.lc) on GPUMAX and posted an announcement of it here on the forums.
I never heard from him again.
--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net
[QUESTION] Allow users to mine and access our wallet-service using TOR?
Hi!
The subject is pretty much self-explanatory, we've recently had some issues with a person mining via TOR to hide a huge botnet and/or a hopping proxy-pool.
What do YOU think about banning TOR-exit nodes from accessing bitcoin wallet and/or pool sites/services?
I guess it's a question of anonymity versus security here, we're going to discuss this internally to - but i want input from users regarding this.
Is there any reason NOT to? Besides the obvious reason of being truly anonymous.
The reasons i can think of, FOR doing so are plenty - hacked accounts, bruteforce attacks, money/bitcoin laundering and much more.
What do you think?
--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net
The subject is pretty much self-explanatory, we've recently had some issues with a person mining via TOR to hide a huge botnet and/or a hopping proxy-pool.
What do YOU think about banning TOR-exit nodes from accessing bitcoin wallet and/or pool sites/services?
I guess it's a question of anonymity versus security here, we're going to discuss this internally to - but i want input from users regarding this.
Is there any reason NOT to? Besides the obvious reason of being truly anonymous.
The reasons i can think of, FOR doing so are plenty - hacked accounts, bruteforce attacks, money/bitcoin laundering and much more.
What do you think?
--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net
Re: [98 Gh/s] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP
A short update from us.
We have decided to ban a user that previously has caused us trouble mining via larger botnets and/or a proxy-pool. I let him back in and even compensated him for the inconvenience back then.
He's was now using ~25-30 connections via TOR to hide his activity this time, we've been in contact with him and informed him about the situation. The amount of getworks was totally of the charts to, our environment can't handle spikes from a few hundred getworks/s to multiple thousands over a short period of time. Directly comparable with the "slashdot-effect".
Bandwidth wise it's a jump from about 1MB/s to 8-9MB/s during the hops - it's a pretty massive change.
He's the one responsible for the HUGE increase in hash rate right after new rounds (~800gh hopper, my guess it's some of the pool-hopping-proxys, maybe not ABCPool this time tho).
He's also the one responsible for the lowered efficiency during those rounds and connections troubles we've gotten reports for over the past days.
The payment issues (Insufficient funds error) should be resolved now, permanently. We've taken some actions to make it possible for us to access the cold-stored funds easier without making it a security risk.
Better safe then sorry!
PPLNS is still a top priority, to solve the "hopper problem" permanently.
I cannot express in words how I'm sorry I am for all the delays for that.
We've going to focus on that for the entire next week, you have my word on that.
If you have any questions, don't hesitate to contact us!
--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net/
We have decided to ban a user that previously has caused us trouble mining via larger botnets and/or a proxy-pool. I let him back in and even compensated him for the inconvenience back then.
He's was now using ~25-30 connections via TOR to hide his activity this time, we've been in contact with him and informed him about the situation. The amount of getworks was totally of the charts to, our environment can't handle spikes from a few hundred getworks/s to multiple thousands over a short period of time. Directly comparable with the "slashdot-effect".
Bandwidth wise it's a jump from about 1MB/s to 8-9MB/s during the hops - it's a pretty massive change.
He's the one responsible for the HUGE increase in hash rate right after new rounds (~800gh hopper, my guess it's some of the pool-hopping-proxys, maybe not ABCPool this time tho).
He's also the one responsible for the lowered efficiency during those rounds and connections troubles we've gotten reports for over the past days.
The payment issues (Insufficient funds error) should be resolved now, permanently. We've taken some actions to make it possible for us to access the cold-stored funds easier without making it a security risk.
Better safe then sorry!
PPLNS is still a top priority, to solve the "hopper problem" permanently.
I cannot express in words how I'm sorry I am for all the delays for that.
We've going to focus on that for the entire next week, you have my word on that.
If you have any questions, don't hesitate to contact us!
--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net/
Re: [98 Gh/s] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP
Hi guys!
This is due to a few larger transactions out from our hot-wallet, we're currently requesting funds from our off-line "cold-wallet" to compensate for this.
It may take a few hours tho, the private keys are in a safety deposit box rather far away physically which currently is being transported to me personally.
This is the first time our hot-wallet has run out of funds, and we're terribly sorry for any inconvenience this may cause you.
We're working as fast as we can to solve this issues.
All money is still safe and still in your possession, they are just not accessible right now.
--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net/
This is due to a few larger transactions out from our hot-wallet, we're currently requesting funds from our off-line "cold-wallet" to compensate for this.
It may take a few hours tho, the private keys are in a safety deposit box rather far away physically which currently is being transported to me personally.
This is the first time our hot-wallet has run out of funds, and we're terribly sorry for any inconvenience this may cause you.
We're working as fast as we can to solve this issues.
All money is still safe and still in your possession, they are just not accessible right now.
--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net/
Re: [205 Gh/s] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP
Hi!
You're absolutly right. It was I that have forgotten to remove a .lock-file from the webserver.
I've been doing some work to the share-calculation to prepare for the PPLNS-switch, so i needed to pause the scripts for a few minutes - but accidently left the file there...
I'm terrible sorry for that, i immediately initiated the script manually when I read the posts a few minutes ago. It was NOT anything intentional to stop the payments nor fake stats.
It won't happen again, once again. My apologies.
--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net
You're absolutly right. It was I that have forgotten to remove a .lock-file from the webserver.
I've been doing some work to the share-calculation to prepare for the PPLNS-switch, so i needed to pause the scripts for a few minutes - but accidently left the file there...
I'm terrible sorry for that, i immediately initiated the script manually when I read the posts a few minutes ago. It was NOT anything intentional to stop the payments nor fake stats.
It won't happen again, once again. My apologies.
--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net
Re: [205 Gh/s] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP
Hi ABCPool.co!
Yes, they do.
You see, we do not allow pool-hopping pools nor huge botnets on our pool. (We've written this multiple times on our twitter, and I KNOW that you're aware of it, since you're doing your best to avoid protections for that)
We've done a few changes to our environment to make it a harder use and register 10 accounts and use then for your own hopping-pool.
The payments for your account(s) will remain disabled until we're done with that. ABCPool and other pool-hopping pool is affected by this.
Sorry for the late response tho, seems like the update notifications for this thread bugs every now and then.
// Best Regards,
Bit LC Inc.
EDIT: Btw, why did you register a new account? Don't you want your users to know that you're hopping multiple pools to allow PPS for such a low charge (and then taking all other extra hopping income to yourself, incl. the 1.5% pps "fee"?)
Yes, they do.
You see, we do not allow pool-hopping pools nor huge botnets on our pool. (We've written this multiple times on our twitter, and I KNOW that you're aware of it, since you're doing your best to avoid protections for that)
We've done a few changes to our environment to make it a harder use and register 10 accounts and use then for your own hopping-pool.
The payments for your account(s) will remain disabled until we're done with that. ABCPool and other pool-hopping pool is affected by this.
Sorry for the late response tho, seems like the update notifications for this thread bugs every now and then.
// Best Regards,
Bit LC Inc.
EDIT: Btw, why did you register a new account? Don't you want your users to know that you're hopping multiple pools to allow PPS for such a low charge (and then taking all other extra hopping income to yourself, incl. the 1.5% pps "fee"?)
I found a post in our feedback-log with a link against this thread. I'm not sure if this app is in development still.
But anyway;
Our API is finally implemented now, please visit https://www.bitlc.net/user/api for more info.
Sorry for the extreme and insane delay(s).
Regards, JIm
BIt LC Inc.
But anyway;
Our API is finally implemented now, please visit https://www.bitlc.net/user/api for more info.
Sorry for the extreme and insane delay(s).
Regards, JIm
BIt LC Inc.
Re: [214 Gh/s] Bitcoins.lc - No invalid blocks, Instant payout, EU, IPv6, 0% fee, LP
A highly beta version of the User API is released, for now - only to get data (full JSON-RPC API comes later).
Visit https://www.bitlc.net/user/api for more info.
More to come later today
EDIT:
Released a full worker-stats api as well.
Now it's possible to get all previous round data for your users/workers..
I'm not sure if that's usable for anyone, but maybe!
Visit https://www.bitlc.net/user/api for more info.
More to come later today
EDIT:
Released a full worker-stats api as well.
Now it's possible to get all previous round data for your users/workers..
I'm not sure if that's usable for anyone, but maybe!
Re: [214 Gh/s] Bitcoins.lc - No invalid blocks, Instant payout, EU, IPv6, 0% fee, LP
Just a few hours after i wrote that last message, we hit the MySQL-connection limit and the webserver (not the pool) started timing out a bit.
Sorry for that, the issue was only for a few minutes..
Sorry for that, the issue was only for a few minutes..