https://www.bitcoins.lc/transactions
[x] Transaction history
Topic: [DOWN] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP - page 51. (Read 180991 times)
June 04, 2011, 01:38:59 AM
June 04, 2011, 12:08:55 AM
One thing more.
Someone was fetching our .json files hundreds of times per sec, which was totally destroying the JSON-RPC against bitcoind. It could have something to do with yesterdays problems with upstream RPC-errors.
For now - that function is disabled. We'll implement memcaching for that later on.
EDIT:
Changed req/s, the last hour we got about 6 000 requests for listtransactions only.
Each request was ~60-80KB.. Do the math on your own.
EDIT2:
The person who did this, please contact me at [email protected] and we'll work out an API for wtf you were doing.
Someone was fetching our .json files hundreds of times per sec, which was totally destroying the JSON-RPC against bitcoind. It could have something to do with yesterdays problems with upstream RPC-errors.
For now - that function is disabled. We'll implement memcaching for that later on.
EDIT:
Changed req/s, the last hour we got about 6 000 requests for listtransactions only.
Each request was ~60-80KB.. Do the math on your own.
EDIT2:
The person who did this, please contact me at [email protected] and we'll work out an API for wtf you were doing.
June 03, 2011, 11:31:19 PM
And btw.
The last block was http://blockexplorer.com/block/00000000000020f6edfa93c9147bf03f11cc1b0635a3ba934debcefd26ebab55
And it's mature in 16 blocks.
The last block was http://blockexplorer.com/block/00000000000020f6edfa93c9147bf03f11cc1b0635a3ba934debcefd26ebab55
And it's mature in 16 blocks.
Code:
{
"account" : "",
"category" : "immature",
"amount" : 50.15050000,
"confirmations" : 104,
"txid" : "27e96d0b7dca34311b9c71b4265b85c94c68eff4bca2cfd88770ffdad47d92eb",
"time" : 1307117383
},
June 03, 2011, 11:29:25 PM
Everything should be up and running.
And here is some stuff from the last round - this time is the data correct however (it showed the wrong amount of shares in output.txt erlier)
http://www.bitcoins.lc/sharelog.txt
/ Jim
EDIT:
Here is the source for the script that generates that output.
https://www.bitcoins.lc/source/unverified.php
Just to confirm that it's nothing strange going on
Now It's time for building the last part of the transaction history(!)
And here is some stuff from the last round - this time is the data correct however (it showed the wrong amount of shares in output.txt erlier)
http://www.bitcoins.lc/sharelog.txt
/ Jim
EDIT:
Here is the source for the script that generates that output.
https://www.bitcoins.lc/source/unverified.php
Just to confirm that it's nothing strange going on
Now It's time for building the last part of the transaction history(!)
June 03, 2011, 04:29:58 PM
Cmon... Fix it! 
June 03, 2011, 03:33:25 PM
502 Bad Gateway on the "stats" page and "generate bitcoins" page 
June 03, 2011, 02:43:41 PM
June 03, 2011, 02:35:54 PM
502 Bad Gateway
In my days we used Apache and we liked it!
In my days we used Apache and we liked it!
June 03, 2011, 01:06:14 PM
I really had to emergency change our tablestructure for the shares-table to innodb.
MyISAM couldn't take it anymore. Locked table each time i tried to do something.
It's running now, it could however take a while... It's about 4 million rows at 600MB.
Sorry about the inconvenience.
EDIT:
Finished.
Please follow our twitter tho.
We're doing some work with the payout system to. (This is what started the emergency switch to InnoDB)
Unverified funds will remain unknown until we're finished.
http://twitter.com/BitcoinsLC
MyISAM couldn't take it anymore. Locked table each time i tried to do something.
It's running now, it could however take a while... It's about 4 million rows at 600MB.
Sorry about the inconvenience.
EDIT:
Finished.
Please follow our twitter tho.
We're doing some work with the payout system to. (This is what started the emergency switch to InnoDB)
Unverified funds will remain unknown until we're finished.
http://twitter.com/BitcoinsLC
June 03, 2011, 12:26:08 PM
Hey, I mined in your pool for about 7ish hours last night and noticed my funds didn't make any movement at all. I figured I'd wait til we found a block to see if things changed but nothing changed. Are there issues with displaying or calculating rewards for the last block? I believe I submitted around 3k shares.
June 03, 2011, 12:23:36 PM
PabloW: If you're willing to give us 50-100 BTC so we can get started with doing so - it would be my plesure to implement it.
As we don't have the amount of "available funds" for that payment method, it's currently impossible for us to do so.
I understand. But in the future, when the pool has more hash rate and probably be more succesful, do you think this could be implemented?
I mean, its not minor stuff, I thinks this could be the most important thing for a pool (stability also obviously)
June 03, 2011, 12:13:15 PM
It's just a security measure.
We're going to make it possible to rename your workers as you wish, but first things first.
Transaction history added (not incoming payments yet tho).
A couple of bugs with donations are fixed, some more caching is added to.
The server is more stable then ever now, and should be for a while now.
I'm currently working on improving the payout/transaction system to make it totally failsafe. AND TO BE ABLE TO DISPLAY BLOCKSTATUS!
We're aiming at making it fully transparent, with display of each and every share that contributed that round.
Here's a little output from the last round that we finished about 30-40min ago.
http://www.bitcoins.lc/output.txt
It only displays user id's, not nicks tho. (I'm user #1 btw)
PabloW: If you're willing to give us 50-100 BTC so we can get started with doing so - it would be my plesure to implement it.
As we don't have the amount of "available funds" for that payment method, it's currently impossible for us to do so.
Regards, Jim
EDIT:
The script seems to have some bugs, we discovered that the testoutput above was a bit wrong.
We're going to make it possible to rename your workers as you wish, but first things first.
Transaction history added (not incoming payments yet tho).
A couple of bugs with donations are fixed, some more caching is added to.
The server is more stable then ever now, and should be for a while now.
I'm currently working on improving the payout/transaction system to make it totally failsafe. AND TO BE ABLE TO DISPLAY BLOCKSTATUS!
We're aiming at making it fully transparent, with display of each and every share that contributed that round.
Here's a little output from the last round that we finished about 30-40min ago.
http://www.bitcoins.lc/output.txt
It only displays user id's, not nicks tho. (I'm user #1 btw)
PabloW: If you're willing to give us 50-100 BTC so we can get started with doing so - it would be my plesure to implement it.
As we don't have the amount of "available funds" for that payment method, it's currently impossible for us to do so.
Regards, Jim
EDIT:
The script seems to have some bugs, we discovered that the testoutput above was a bit wrong.
June 03, 2011, 12:08:29 PM
I realized that deepbit attracts people because of this
YOU CAN PAYOUT YOUR UNCONFIRMED BTC
simple as that. Its just 1 single counter that goes up every hour. You dont have to be thinking of confirmed/unconfirmed, or even payouts, cause you can set the amount you want for doing automatic payouts.
If you implement THIS in bitcoins.lc, I can assure you, your pool will be at least the second biggest
YOU CAN PAYOUT YOUR UNCONFIRMED BTC
simple as that. Its just 1 single counter that goes up every hour. You dont have to be thinking of confirmed/unconfirmed, or even payouts, cause you can set the amount you want for doing automatic payouts.
If you implement THIS in bitcoins.lc, I can assure you, your pool will be at least the second biggest
June 03, 2011, 04:42:41 AM
I can not ping you at the moment - is that a security measure because of the ddos?
with scripting it is rather painful to use a user/pw for every worker. I assume it will also work with one account for several workers? otherwise it would be cool to just have one user/pw with the worker number added.
with scripting it is rather painful to use a user/pw for every worker. I assume it will also work with one account for several workers? otherwise it would be cool to just have one user/pw with the worker number added.
June 02, 2011, 08:43:45 PM
Please implement in some place a "X BTC in last 24hs"
Im ready to move my 770 Mhash to bitcoins.lc tomorrow, when deepbit start with their fees again hehe
Im ready to move my 770 Mhash to bitcoins.lc tomorrow, when deepbit start with their fees again hehe
June 02, 2011, 05:06:37 PM
pool shouldnt be so far down on page 5! Much better than that now
June 01, 2011, 04:37:37 PM
Ah - looks like I've found a small bug. I hadn't updated my account with a receiving address. Once I put that in it works fine
You're absolutely correct. The bug is fixed now
Thanks for reporting it!
June 01, 2011, 09:48:29 AM
Strange, have you tried again after that?
Could have been some temporary error while i was pushing changes or similar from my dev-enviorment... :/
I just made an instant payout to my self, and no-one else has reported it (And according to listtransactions, transactions do work)
Please provide me with more information and we'll try to solve it.
--
Regards, Jim
Ah - looks like I've found a small bug. I hadn't updated my account with a receiving address. Once I put that in it works fine Could have been some temporary error while i was pushing changes or similar from my dev-enviorment... :/
I just made an instant payout to my self, and no-one else has reported it (And according to listtransactions, transactions do work)
Please provide me with more information and we'll try to solve it.
--
Regards, Jim
June 01, 2011, 09:23:08 AM
Strange, have you tried again after that?
Could have been some temporary error while i was pushing changes or similar from my dev-enviorment... :/
I just made an instant payout to my self, and no-one else has reported it (And according to listtransactions, transactions do work)
Please provide me with more information and we'll try to solve it.
--
Regards, Jim
Could have been some temporary error while i was pushing changes or similar from my dev-enviorment... :/
I just made an instant payout to my self, and no-one else has reported it (And according to listtransactions, transactions do work)
Please provide me with more information and we'll try to solve it.
--
Regards, Jim
June 01, 2011, 08:42:51 AM
I'm having trouble accessing the instant payout page:
Quote
HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfil the request.
Apologies if this has already been brought up and I missed it. Jump to: