|
So if we find a block it pays out to the "Pay To:" address I put into CoinDaemon, right?
|
|
|
|
Also @Tittiez: I've heard that you want to start your own private pool with some friends. Keep in mind that ecoinpool currently doesn't have any payout mechanisms (neither do PoolserverJ nor pushpool), so you would have to manage that yourself. There is another ticket on my tracker that promises payout support for a future release, making ecoinpool the true all-in-one backend solution for mining. But - as you can imagine - it's a lot of work to get there. p2k Not a problem, we decided we would all split the blocks evenly anyway, its a lot easier that way. Oh and I got it working!  [07:18:54.068][ebitcoin/warn] ltc_block: Connecting to localhost:9335...
[07:18:54.071][ebitcoin/warn] ltc_block: Connection established.
[07:18:54.084][server/warn] Subpool b2fcfae2039213c8ae671ecc77006547 starting...
[07:18:54.170][ebitcoin/warn] ltc_block: Entering resync mode, getting 49745 block(s)...
[07:18:54.197][default/warn] ecoinpool_rpc: Started RPC on port 9339
[07:18:54.199][daemon/warn] SCrypt-ltc CoinDaemon starting...
[07:18:54.388][server/warn] ltc_pool: --- New main block! Assigned: 0; Shares: 0; Cached: 0; Longpolling: 0 ---
Got a few of my friends pointing their miners to my pool, its working fine now. Thanks! |
|
|
|
SURPRISE!!! 1000 Litecoins donated to the Litecoin P2Pool subsidy!! ^_^
715a86b3dc3e880f86774ab4fb3441d0ae40b1e2bfe066adef856997a518f080
Enjoy!!
I missed it  Aaaahhh... Be ready for the next time (maybe next sunday again)! Will do! Missed because timezones are off I think, I was still using my computer at 1AM (Around when you sent the LTC out). |
|
|
|
Phenom ii x4 955 @ 3.6GHz  |
|
|
|
|
What about p2pool? Its at 3.5MHash/s!
|
|
|
|
God I am making such simple errors over and over again, I really need to start sleeping. I swear I had it running though! I'm using 0.6.0rc1 64bit bitcoind. Bitcoind and the couchdb are both running, I get this at pool startup: http://pastebin.com/KcwAE47NSome other simple dumbass mistake I presume? |
|
|
|
SURPRISE!!! 1000 Litecoins donated to the Litecoin P2Pool subsidy!! ^_^
715a86b3dc3e880f86774ab4fb3441d0ae40b1e2bfe066adef856997a518f080
Enjoy!!
I missed it |
|
|
|
He really needs the boot  |
|
|
|
I am so glad to see the Litecoin P2Pool grow (from 400kH to 3000kH!) that I'll donate extra 1000 LTCs on sunday (tomorrow)!!!!
Lets make Bitcoin P2Pool reaches 1THash!!!
P2Pool is the future of Bitcoin / Litecoin Mining!!
Enjoy!!
LTC is at 3620kHash/s now, holy fuck! |
|
|
|
|
What caused the huge ass spike in LTC? Pool is at 3614kHash/s!
|
|
|
|
Realized my VPS was too cluttered, so I decided to reinstall it altogether. So this is on a fresh Ubuntu Server 11.04 Installation: I go to startup a testpool, and I get this error message: http://pastebin.com/kfP55yKdExact same one I had earlier today.  Since it works fine others I assume its my own fault and has something to do with the config correct? |
|
|
|
I vote to BAN CoinHunter/RealSolid for ever.
+1 |
|
|
|
|
I'll give your suggestions a shot, thanks guys!
|
|
|
|
|
So, me and a couple friends decided that we could mine in a private pool together.
Two Phenom ii X4, One X6's, One i5, and One i7.
I already own a ubuntu VPS and I have basic linux knowledge, can anyone give me an idea where to start? I understand PoolServerJ added Litecoin support, would it be best to try to use that? I just need pointed in the right direction.
|
|
|
|
 Holy fuck! That's BTC |
|
|
|
Finally: [22:21:12.418][ebitcoin/warn] btc-chain: Connecting to localhost:8333...
[22:21:12.419][ebitcoin/warn] btc-chain: Connection established.
[22:21:49.771][ebitcoin/warn] btc-chain: Entering resync mode, getting 101129 block(s)... Yay |
|
|
|
I realized that I wasn't turning on bitcoind, so I ran it then went to run ecoinpool but I get this at startup: config_db - couchbeam:open_or_create_db/3 returned
an error:
{conn_failed,{error,econnrefused}}
{"init terminating in do_boot",{{badmatch,{error,{shutdown,{ebitcoin_app,start,[normal,[]]}}}},[{ecoinpool_test
_launch,start,0,[{file,"src/ecoinpool_test_launch.erl"},{line,34}]},{init,start_it,1,[]},{init,start_em,1,[]}]}
}
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
Crash Dump File: http://lazycrazygaming.net/downloads/erl_crash.dump |
|
|
|
I see this line under current payouts.. is it anything to be worried about or is it someone just using a weird payout address?
"Unknown. Script: 202986d5879cfd55f909e272989e1bcc3861dbb8c0a8f4ecb4cf904bcecb5f2c90": 0,
Your solo mining, remember that. Therefor there is no payout address, but instead it goes directly into bitcoind. Ummmm? Eh? It goes to all the N addresses listed in the share chain - the coinbase txn lists all those addresses. Aside ... so as mentioned above ... could someone stop every block from being accepted by putting crap addresses in the share chain? Hope that problem doesn't exist or has been already dealt with if it did exist. I meant at least in our prospective. My payouts show as "Mined" in the bitcoin client. |
|
|
|
Went to create a worker, but I got this: While requesting a new user ID, the pool server did not
respond in time. This usually means that the pool server
is down or currently unreachable. When I start the pool in general, the console gets this error: =SUPERVISOR REPORT==== 11-Feb-2012::19:56:19 ===
Supervisor: {global,
ecoinpool_server_sup_1360b02e19d98482148d4c6dea0127eb}
Context: shutdown
Reason: reached_max_restart_intensity
Offender: [{pid,<0.753.0>},
{name,subpool},
{mfargs,
{ecoinpool_server,start_link,
[<<"1360b02e19d98482148d4c6dea0127eb">>]}},
{restart_type,permanent},
{shutdown,5000},
{child_type,worker}] |
|
|
|
|
Show Posts
