Quote from: girino on November 22, 2014, 02:17:00 PM

Quote from: Rols on November 22, 2014, 02:07:08 PM

Quote from: cointhinkers on November 22, 2014, 01:22:00 PM

Quote from: e1ghtSpace on November 22, 2014, 11:26:39 AM

Quote from: Rols on November 22, 2014, 08:33:34 AM

Quote from: e1ghtSpace on November 22, 2014, 02:44:32 AM

Quote from: mdsn on November 22, 2014, 12:42:23 AM

Whats a pool resistant cpu only coin?

This is the only Pool resistant coin to ever be created. (as far as i'm aware)

You dont know much @e1ghtSpace. This coin is not pool resistant.

Can you please elaborate? I'm genuinely interested.

Now you get to see who really "don't know much".

@e1ghtSpace ,he is stupid guy,just ignore him.

The most stupid thing is to ignore facts and people. I'm a programmer and I speak 7 languages. So im not stupid but maybe my opinion is stupid but then you have to tell me why.

You speak all those languages and can't read a white paper? That's odd!

Guys, Rols is right. You didn't read the whole thread? I literally posted evidence.

Quote from: e1ghtSpace on November 22, 2014, 09:35:23 AM

Quote from: Rols on November 22, 2014, 08:33:34 AM

Quote from: e1ghtSpace on November 22, 2014, 02:44:32 AM

Quote from: mdsn on November 22, 2014, 12:42:23 AM

Whats a pool resistant cpu only coin?

This is the only Pool resistant coin to ever be created. (as far as i'm aware)

You dont know much @e1ghtSpace. This coin is not pool resistant.

I guess it is pool resistant but not solo-mining only.

Quote from: Mr. Spread on October 19, 2014, 07:07:47 PM

Quote from: HunterMinerCrafter on October 19, 2014, 04:55:01 PM

Most importantly, what prevents a pool from using indistinguishability obfuscation of garbled circuits or Gentry style FHE to deliver (each block) a circuit to a worker that allows the worker to sign valid work, but nothing else? This would add quite a bit of overhead to the signing step for the worker (hitting 1kh/s might even be optimistic, heh) but pooling can still occur and that overhead will only come down in time.

(This is generally an open question going back to at least 2011. My understanding is it is commonly held that avoiding pooling in general is just mathematically impossible, and specifically because of secure function evaluation.)

I doubt that you will hit even 1kh/s with homomorphic encryption. Overhead will definitely be lowered in the future by further researches but it is very unlikely that it will ever be possible to perform encrypted computations with the same speed as unencrypted ones without significant overhead. Creating pool with very large overhead may be possible even now.