Yes you are missing something. The pool hasn't solved any blocks yet. You will only get paid for shares you contributed to a particular block that the pool solves and gets the reward.

At this stage all bitcoin.lc users should have a 0 balance.

"Current block received Saturday 28 May 11:30:47"

Shouldn't that mean that the old block is solved?

But you are right, still saying "Solved blocks 0"..

Then I will wait and see. But my hashrate on the site is 0 now, and I've been using my worker for over 30 minutes.

Yes that means the block was solved but by someone else. The pool will get new blocks all the time and unfortunately if the pool doesn't solve it then the shares contributed are wasted and nobody gets paid!

There are pools that pay per share regardless of if the pool solves the block or not.

3) Attack against the pool it self - Thousands of invalid shares are sent. (Not stale work, but purely false work)- Banned workers & ip-addresses responsible for this attack, and also implementing a protection against it in the future. (Auto blacklist/ban)

The pool is still operational no real shares should been lost and the mining continues.Please show those bad guys that we won't give up that easy!

Also implementing some new features right now, I'll keep you guys updated!

I wish the origin of these attacks were known so a majority of users could just shun these idiots.

It's entirely possible the owner of the pool has nothing to do with it. Pool participants can become very competitive and protective of their "team." Any one idiot with a botnet who becomes emotionally attached to "their" pool is going to try this.

All just part of the cost of doing business on the Internet.

Now here's an idea: build a peer-to-peer pool using cryptography, so is no central pool host to attack.

Just directed 660 Mh/s towards your pool. Let's see what we will accomplish.As for the suggestions, considering that the pool is (for now) quite small and solving a block could take a couple of days, I think it will be a good ideea for you to email us when a block is solved.

Now here's an idea: build a peer-to-peer pool using cryptography, so is no central pool host to attack.

This would require miners to install software additionally to the mining software. P2P applications also very often require forwarded ports (current mining software just does some [imho highly inefficient] HTTP requests as far as I've understood) and it would also require bandwidth as well as introducing latency issues. In the end, light takes half a second to travel around the globe, you can't transmit data faster than that.

I'm btw. also VERY interested how transaction fees are being handled!

https://bitfinex.com <-- leveraged trading of BTCUSD, LTCUSD and LTCBTC (long and short) - 10% discount on fees for the first 30 days with this refcode: x5K9YtL3ZbMail me at Bitmessage: BM-BbiHiVv5qh858ULsyRDtpRrG9WjXN3xf

Now here's an idea: build a peer-to-peer pool using cryptography, so is no central pool host to attack.

This would require miners to install software additionally to the mining software. P2P applications also very often require forwarded ports (current mining software just does some [imho highly inefficient] HTTP requests as far as I've understood) and it would also require bandwidth as well as introducing latency issues. In the end, light takes half a second to travel around the globe, you can't transmit data faster than that.

All the P2P stuff you mention (ports, etc.) is no worse than Bitcoin itself.

As for bandwidth and latency, I wasn't talking about the hashing itself as much as sharing the reward (which is what a pool does). If there were some way to collaboratively agree on a transaction block that gave the rewards to the miners in some sort of fair approximation of their effort, then there wouldn't be a need for a pool server; whichever miner found the block would just submit it and the rewards would be shared.

Especially protection against malicious nodes + share verification, the main reason why servers are used for pools despite being single points of failure in the first place (as you just have to trust the server operator, not everyone in the pool)

https://bitfinex.com <-- leveraged trading of BTCUSD, LTCUSD and LTCBTC (long and short) - 10% discount on fees for the first 30 days with this refcode: x5K9YtL3ZbMail me at Bitmessage: BM-BbiHiVv5qh858ULsyRDtpRrG9WjXN3xf

Especially protection against malicious nodes + share verification, the main reason why servers are used for pools despite being single points of failure in the first place (as you just have to trust the server operator, not everyone in the pool)

When the pool solves a block, are you dividing up 50 BTC among the miners or are you dividing up (for example) 50 + 0.89428576 BTC among the miners?

We're not dividing up the 0.89 BTC (transactions fees) to users as of now.We do however use these extra funds to pay the instant payouts you as a user does.

Are you following?

New for tonight:* Stats page is updated with round-stats and a new page for solved blocks is coming in a couple of hours.* Site is now fully available as HTTPS (SSL) for logged in users (and it's REQUIRED to use SSL for all account-related stuff, forgot password etc)** Note: The system enforces it automatically. Noting you'll need to do.

We're also thinking of providing a encrypted channel for the getwork json-rpc interface to our pool.What do you guys think about that?