[ANN] MMCPool.com - GPU,CPU(yam) - The Awesomest Pool!

[arcke]

I keep getting this, mining for an hour
 
PROOF OF WORK RESULT: Rejected

On another machine I start the miner

./minerd --url http://work.mmcpool.com/ --user <address> --threads 1

and it says "KIlled" after being. What can be wrong?

If its two different machines we can rule out it being them (well, its unlikely).

Whats your network setup?

The first is behind a firewall at my home only getting rejects.
The second is a cloud vps server (512MB,  1 virtual core)

You need 1gb ram to mine MMC and try disabling the firewall and setting up portforwarding.

Yes, i was guessing at a memory limit problem. Maybe I will try a 1 GB solution.

[Chronos24]

I pointed my 8320 rig at your pool. I'm pushing 3.0 HPM, Seems to be working great!

[isaacgoldbourne]

I keep getting this, mining for an hour
 
PROOF OF WORK RESULT: Rejected

On another machine I start the miner

./minerd --url http://work.mmcpool.com/ --user <address> --threads 1

and it says "KIlled" after being. What can be wrong?

If its two different machines we can rule out it being them (well, its unlikely).

Whats your network setup?

The first is behind a firewall at my home only getting rejects.
The second is a cloud vps server (512MB,  1 virtual core)

You need 1gb ram to mine MMC and try disabling the firewall and setting up portforwarding.

[isaacgoldbourne]

Ypool had 120% network rate on PTS in the early days, and nothing went WRONG

Even if we have 51% on the pool no fork will be initiated if we have strong connection to the main node.

I think the source to the pool needs to be released. It won't do the coin any favors if this gets to 51% (by the looks of things it will by tomorrow)

I know it won't fork, but it undermines the security of the coin for any one entity to have 51% of the hashing power as they could perform a 51% attack.

I'm not saying they will, but because they have the capability it devalues the coin.

120%?

Having one pool is not good for any coin. We need 10 pools, competition is good for the miners and good for the coin. We need distributed hashing before we can become worth a serious amount of money.

Already at 33% of the network, christ.

[arcke]

I keep getting this, mining for an hour
 
PROOF OF WORK RESULT: Rejected

On another machine I start the miner

./minerd --url http://work.mmcpool.com/ --user <address> --threads 1

and it says "KIlled" after being. What can be wrong?

If its two different machines we can rule out it being them (well, its unlikely).

Whats your network setup?

The first is behind a firewall at my home only getting rejects.
The second is a cloud vps server (512MB,  1 virtual core)

[dima1236]

new hash rate : 2006.09HPM , keep it going guys , we should be finding 2-3 blocks / hr at least now 

[isaacgoldbourne]

I keep getting this, mining for an hour
 
PROOF OF WORK RESULT: Rejected

On another machine I start the miner

./minerd --url http://work.mmcpool.com/ --user <address> --threads 1

and it says "KIlled" after being. What can be wrong?

If its two different machines we can rule out it being them (well, its unlikely).

Whats your network setup?

[dima1236]

Ypool had 120% network rate on PTS in the early days, and nothing went WRONG

Even if we have 51% on the pool no fork will be initiated if we have strong connection to the main node.

I think the source to the pool needs to be released. It won't do the coin any favors if this gets to 51% (by the looks of things it will by tomorrow)

I know it won't fork, but it undermines the security of the coin for any one entity to have 51% of the hashing power as they could perform a 51% attack.

I'm not saying they will, but because they have the capability it devalues the coin.

[arcke]

I keep getting this, mining for an hour
 
PROOF OF WORK RESULT: Rejected

On another machine I start the miner

./minerd --url http://work.mmcpool.com/ --user <address> --threads 1

and it says "KIlled" after being. What can be wrong?

[isaacgoldbourne]

Even if we have 51% on the pool no fork will be initiated if we have strong connection to the main node.

I think the source to the pool needs to be released. It won't do the coin any favors if this gets to 51% (by the looks of things it will by tomorrow)

I know it won't fork, but it undermines the security of the coin for any one entity to have 51% of the hashing power as they could perform a 51% attack.

I'm not saying they will, but because they have the capability it devalues the coin.

[dima1236]

Even if we have 51% on the pool no fork will be initiated if we have strong connection to the main node.

I think the source to the pool needs to be released. It won't do the coin any favors if this gets to 51% (by the looks of things it will by tomorrow)

[isaacgoldbourne]

I think the source to the pool needs to be released. It won't do the coin any favors if this gets to 51% (by the looks of things it will by tomorrow)

[alachua]

we just found one

[dima1236]

So lets sum some things

1. Big thank you for the pool
2. Network Hashrate ATM = 2^32 * 0.00000949 / 6 = 6793 HPM
3. Pool Hashrate ATM = 1684.64 HPM and growing
4. Pool / Network = ~25%
5. We still ain't finding any blocks
6. Anything wrong ??

[foolsh]

Just replying to leave a note that libtool is also required for Ubuntu

Nice job on the pool!