Quote from: CoinHunter on April 19, 2012, 03:18:44 PM

Sounds like they are storing the public key with the accounts so that it is "Set" once and can't be changed. This way it won't be relying upon a potentially weak hash to secure a public key anymore, but the actual public key. Probably also why they can reduce transaction size so drastically.

who is this proverbial they? are you no longer part of this development team?
And I kinda had a feeling you were gonna say something about the hash->public key thing, and you've got that backwards. As long as you have a known collision-resistant hash function, you gain both the security of the one-way hash and the public key. Until the account gets used anyway. Tx size isn't so bloated because of the hash+pubkey combo, it's so bloated because bitcoin is just a bloated protocol.

and no mention of the 51% prevention? does realsolid just say "this is the secure block" from here on out? why even pretend at decentralized anymore, right?