Gridcoin, what you're saying sounds like it's a bit centralized, isn't it? If you need a central SQL database to keep track of things, then there has to be an entity in charge of it right?
I've also never heard a solution to the problem of people mining random problems, and then just waiting for one of the solutions to become relevant. Is there a way around that now?
With hashes you can't tell what hash is going to be next. So it's pointless to try and premine the next block. This is how I understand it anyway.
Hi BigJohn,
Centralized: No; we're p2p for the coin, decentralized for the boinc clients, and the 3rd party PoW check is limited to 60 independent boinc apis, and we continue to function when an internet point of failure dies off (or if the APIs die off).
Our SQL servers are p2p; each client runs an sql server. The ledger is replicated and synchronized p2p.
I do not understand the part about premining. I was referencing storing generic data in a distributed fashion across multiple SQL servers with the cryptoexchange of new rows contributing to part of the PoW. Were going to use this for storing our leaderboard info and our cpuminers outstanding payment list, confirms of pool mining payments and transactions etc.
Thanks,
Rob H