|
Sounds to me like you don't have any mining hardware. Hint: Your computer doesn't mine, it controls mining hardware you connect to it. Read up about ASICs and bitcoin mining.
|
|
|
|
|
Hi all. I'm sorry to say I'm withdrawing my offer to manage the funds for this as an escrow. Due to personal reasons I don't want to dedicate the potential extra time and resources to do this.
|
|
|
|
[2015-05-31 07:29:42] Possible block solve diff 137949033258.993622 !
[2015-05-31 07:29:42] BLOCK ACCEPTED!
[2015-05-31 07:29:42] Solved and confirmed block 358774
|
|
|
|
Well done, and with less than 3TH/s, very cool.
Look harder homer. found a block 358682
user with 2.88P |
|
|
|
[2015-05-30 16:30:12] Possible block solve diff 111073631914.175095 !
[2015-05-30 16:30:12] BLOCK ACCEPTED!
[2015-05-30 16:30:12] Solved and confirmed block 358682
|
|
|
|
|
Update: Pool's back online it seems, sorry about the inconvenience.
|
|
|
|
Understatement unfortunately as per always providers try to play down the severity. They've updated it with: We are aware of an issue affecting service to this Linode.
If you are experiencing issues with this Linode, there is no need to issue any jobs or open a support ticket at this time. Please monitor our status blog for further information. Thank you for your patience and understanding.
An issue affecting the physical hardware this Linode resides on has been detected.
We are working to resolve the issue as quickly as possible and will update you as soon as we have more information.
Your Linode will return to its previous state once the issue is resolved. Thank you for your patience and understanding.
and the datacentre status: Update - Our upstream provider has provided a new estimated time to restoration of 11:30PM PDT.
May 30, 05:08 UTC
Update - Our upstream provider has provided a new estimated time to restoration of 10:00PM PDT.
May 30, 04:37 UTC
Update - At approximately 6:30PM PDT, the Fremont datacenter experienced a power utility outage. One out of eight generators also experienced an electromechanical failure. The estimated time to restoration is currently 9:30PM PDT. Linode has all hands on deck to get Linodes online as soon as power is restored.
May 30, 03:21 UTC
Update - We have received word from our colocation provider that there has been a power event in a section of the Fremont datacenter. The affected space is where a critical part of the datacenter network is located. The datacenter's electric provider is working with staff to restore power as soon as possible. Please watch this status page for further updates.
May 30, 02:25 UTC
Identified - We are aware of an issue within our Fremont datacenter and are investigating at this time. We will provide additional information as it becomes available.
May 30, 01:47 UTC
|
|
|
|
|
I had already put in a support ticket. The Datacenter is having a routing issue. Many will still be able to connect but from some locations there is no way to reach the pool, even though it's still up and running so it's out of my hands till they fix it.
|
|
|
|
What is a respectable amount that makes it worth your time for lets say 10 people instead of 5?
I guess 4% would make it nice round figures and put it on par with mining on the current most popular PPS pool. But no more than 10 people... |
|
|
|
Here are the console logs for the last 5 blocks that were solved during the forum downtime for those interested. [2015-05-24 03:28:48] Possible block solve diff 54142132995.418602 !
[2015-05-24 03:28:48] BLOCK ACCEPTED!
[2015-05-24 03:28:48] Solved and confirmed block 357759
[2015-05-24 16:15:01] Possible block solve diff 174814867550.862122 !
[2015-05-24 16:15:01] BLOCK ACCEPTED!
[2015-05-24 16:15:01] Solved and confirmed block 357840
[2015-05-25 02:20:29] Possible block solve diff 249407221993.210571 !
[2015-05-25 02:20:29] BLOCK ACCEPTED!
[2015-05-25 02:20:29] Solved and confirmed block 357904
[2015-05-25 04:12:40] Possible block solve diff 53202934179.518593 !
[2015-05-25 04:12:40] BLOCK ACCEPTED!
[2015-05-25 04:12:40] Solved and confirmed block 357922
[2015-05-26 13:41:18] Possible block solve diff 67716111510.573845 !
[2015-05-26 13:41:18] BLOCK ACCEPTED!
[2015-05-26 13:41:18] Solved and confirmed block 358109
|
|
|
|
|
There is still one phase of the trust equation here that will entrust coin to ezeminer and that's the initial rental fee being entrusted to him (say it's 5BTC). There is no way around that aspect but at the very least putting up their BTC shows some element of trust. If you only have 5 or so users I don't mind being used as escrow for the fee described. What I would suggest is the following:
We call my fee 2% since you offered 0.5 as the final extra donation. In the following example 5BTC is used to mine with.
1. Coordinate amongst yourselves who are the 5 miners to be involved - don't start the process till you know you have enough people.
2. Once you know you have enough people, each person emails me in private and in response I'll give them a unique address to send their initial funds.
3. Each person sends me their 1/5th +2% contribution so 1.02 BTC each to the unique address I gave them in (2) and emails me the transaction ID and their return/receive address which I will store and cannot be changed after this time.
4a. Once I have received all funds I'll release the mining BTC to the coordinator so 5 BTC and will keep the 2% as fee.
4b. Should not enough people get funds together I return the funds to each miner, minus the 2% from each.
5. I provide the coordinator with a mineto address.
...
profit
7. I distribute any block rewards to the addresses I personally received in private -0.4 BTC for the first block and -0.5 for 2nd and subsequent blocks.
This would be too labour intensive for more than 5 people to make it worth it.
|
|
|
|
Hey -ck would you consider displaying the biggest share found up to date?
Which best share? User's? Worker's? The pool's? The current round's or all time? None of that pool data is exported in any way I can display it at the moment and would require a code update and pool restart. Plus there's no long term record of shares like that currently so the best all time share is whatever the biggest diff block solve to date has been (which I don't keep records of but may be somewhere in this forum thread). |
|
|
|
Hey question about the pool. I got alerts on my SP20 that has been pointed to the solo pool for 2 days now that it has found 2 blocks. Nothing hitting the confirmation with my wallet though.  I've never seen that before. Pretty sure the sp20 code is fine and doesn't have false positives. If it says you've solved blocks it has determined that you have solved a block of whatever coin you are mining. Chances are your SP20s spent some time on some other pool that was mining some random shit coin and solved a block there. All the solo.ckpool.org blocks are easy to spot here in this link I've posted before as newly minted coins https://www.blocktrail.com/BTC/address/1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ/transactions/in/0 |
|
|
|
By the way, here is my promised 'Thank You' to the Pool/creator(s) for the 2 solo coins we hit last week.
Great work, much appreciated, though I'm old enough to be her father. |
|
|
|
Good to know you're using ckpool's code, can't go wrong with that. You must have had to make a few modifications to it, though? It only supports bitcoin mining by default doesn't it?
CK's pool code is certainly only BTC - I'm pretty sure Con would just erase all coins other than BTC if he could  . If the folks over at NH are indeed using ckpool and ckdb for pools other than their BTC solo mining operation, then they've absolutely made modifications to it  . Correct, there's no altcoin support in ckpool. Also there is no solo mining code in the freely available code either as it is unique to my solo pool. Both have been added by NH's own programmers to my code and I've had nothing to do with those modifications. |
|
|
|
Can't complain |
|
|
|
|
5 blocks solved during the forum downtime.
|
|
|
|
if i may ask to those hitting all the blocks the past week, how much hash are you running,
Look back over the posts where each block solve was announced, the associated hashrate is usually mentioned at the same time. |
|
|
|
|
Show Posts
