News for hackers. Stuff that matters.
Re:On the dangers of a blockchain monoculture by derefr on Tuesday January 05, 2016 @04:17PM (#10846122)
So, a blockchain is just a special kind of distributed ledger; and a ledger is just a particular thing to store in a distributed database. What makes a blockchain special (and thus, I think, what informs the common usage more than any technical definition involving proofs of work) is basically what it accomplishes, that a regular distributed database cannot: a blockchain allows N mutually-untrustworthy parties—that is, people who would pick one-anothers' pockets if they could—to co-author a history they're all happy with, without having to put their trust in any particular party (who, again, might want to pick everyone's pockets), but instead only in the system as a whole.

My favorite comparison is to leaderboard ranking in competitive games (let's use Starcraft 2 as an example.) This is another place where everyone would love to cheat if they could.

Let's say you set up a blockchain where each "transaction" contained someone's SCII 1v1 gameplay-record from their perspective (i.e. their own input events, and the received network movement- and action-events from their opponent) for a ladder match they played. You'd get two "transactions" in a pair for each match—each submitted by one player—and each one would would move the players' ladder rankings and leaderboard positions around (though in an idempotent way, if both records happen to be valid.)

In this model, instead of having to have an authoritative "ladder server" that simulates all the game's physics for the players, or building any sort of anti-cheating tech into the game-client, each player would just be part of the ladder blockchain and therefore would "audit" each entered game-record after the fact, by running the game's physics engine against the gameplay-records to determine their validity, and translating the valid records into changes in the ladder-ledger.

Every player that bothers to run the ladder-chain daemon (which might-as-well just be embedded into the game-client as a nice'd background process) would be auditing every other player's game-record for physics discrepancies. Records from matches where either player was using a hacked game-client would simply be dropped from history rather than affecting the ladder (or could be encoded as a forfeit for the hacker.)

The game's manufacturer could have server-nodes of their own, purely for auditing—but they likely wouldn't need to. In fact, there wouldn't even need to be a game company; the game could be completely abandonware with no server infrastructure, yet the ladder and leaderboard system would continue to function indefinitely.

The properties that let you do this are what make a blockchain a blockchain. The other properties are implementation details.

There are no comments on this comment yet.