My friend and I are creating an Avalon/Asic friendly Bitcoin mining Pool

[AtomSea]

My friend and I are creating an Avalon/Asic friendly Bitcoin mining Pool

We are finishing up Alpha testing and are inviting some early Beta testers.

We are called HugPuddle and give out 98%.
1% goes to HP - 1% goes to the developer of the p2p pool.

We are using a virtual server that is designed to balance load and give optimal performance for Asics and their unique power capabilities.

Point your miners here if you are interested:
108.161.129.247:9332

Use your BTC address as your User Name.
Your password can be anything - there is no login.

Make sure your BTC addy is your User Name or the entire hashrate will go to the pool.

That same URL can be used in the URL box to check on the status of your account - just look for your BTC address

We have Avalon chips on the way and are soon to be thrashing Asics style too.
In the meantime, if anyone wants to try our low cost site please feel free

Thanks for trying us out! PM me for any specific questions - we hope to have our own thread up really soon.

Peace.

[1715467354]

1715467354

[1715467354]

1715467354

[1715467354]

1715467354

[1715467354]

1715467354

[lano1106]

Hi,

I have few questions.

What is the pool hash rate currently?

Do you have a website with real-time stats?

JSON API?

[HellDiverUK]

You should get yourself on the P2Pool node list.

1.5GH/s is a very slow start, though...

Your getwork latency sucks, too - you should be aiming below 0.2s - take a look at the stats on my P2Pool node @ http://847pool.no-ip.biz:9332/static/graphs.html?Day - it's not ideal either, but it's in the right ballpark.  Your suckky latency is why you've got two orphaned blocks, which isn't good.  It'll be horrible once you put any sort of load on there (IE Avalon).

Also check out http://p2pool.mjke.de:9332/static/ - that's the sort of stats you should be aiming for when running a P2Pool for Avalons.

[ebereon]

You should get yourself on the P2Pool node list.

1.5GH/s is a very slow start, though...

Your getwork latency sucks, too - you should be aiming below 0.2s - take a look at the stats on my P2Pool node @ http://847pool.no-ip.biz:9332/static/graphs.html?Day - it's not ideal either, but it's in the right ballpark.  Your suckky latency is why you've got two orphaned blocks, which isn't good.  It'll be horrible once you put any sort of load on there (IE Avalon).

Also check out http://p2pool.mjke.de:9332/static/ - that's the sort of stats you should be aiming for when running a P2Pool for Avalons.

Thanks for the reputation here as a good p2pool node setup. It took me some days to optimise it to what it is now. But even with 0.1% fee and 0.1% give to author, nobody is using my p2pool node which gives 110% efficiency at this very moment :-/.

That said for the thread starter, no one will use your pool with 1% fee. Sorry to say, but no one will pay for service these days.

[polrpaul]

^^ what he said..

what makes you think you have the best paying p2pool?

[HellDiverUK]

what makes you think you have the best paying p2pool?

Lack of research, and cluelessness, I think.

2 hours of setup on a machine with less CPU power than an iPod, I have a better p2pool node running.  I've not advertised mine yet, as I'm still tweaking, so it may be a bit up and down.  Then again, anyone interested in running a P2Pool node will just set it up for themselves, it's not rocket science.