Quote from: DannyHamilton on January 24, 2015, 07:46:11 AM

As I've said a few times. You REALLY need to think in terms of a decentralized system (where there is no identifying information available at all about the hasher), and in terms of a Sybil attack. Until you can get your mind into that mode, you aren't going to come up with any useable ideas at all.

Note, that it took decades of people thinking in terms of a decentralized system under a Sybil attack all failing to come up with a solution until Satoshi came up with the proof-of-work secured blockchain idea. If you seriously start thinking in terms of a decentralized system under a Sybil attack the first somewhat workable solutions that you'll come up with will all be "proof-of-something" (work, stake, storage, etc) solutions. All of these will have the same feature of a fixed reward for completing a fixed proof.

I dont know if you can read/understand this...

http://s9.postimg.org/agazobkfj/NEWCOIN.jpg

The "proof" could possibly be something like a SET hashrate somewhat determined by the user. Say your ASIC can run at 350 GH/s, there is a prompt that asks you to set your Hashrate statically, and then a RNG adds a xx number decimal point to that static rate. So you set your rate to 322 GH/s, and then the built in RNG puts in say, 12 decimal points, so it sets your static hashrate to 322.125875456251 GH/s and that is how the network issues you your "ID" starting at 1 and ending at 999999999999 based upon the numbers after the decimal point. Is that possible? **To maintain a static hashrate**

**=Edit

OH MY. I SPELLED BROADCAST WRONG Shocked