| > Obviously a blockchain cannot magically make people do things they don't otherwise want to do. So, what's the point, really, especially if talk about "Distributed trust" if blockchain provides nothing to ensure that trust? > But what a blockchain can do is model parts as tokens that can only exist once on the chain, associate data like provenance documents with each token, then model sales as transfers of the token... a way that you don't have to trust any single entity So, the details and provenance magically appear on the blockchain. Who verifies them? Who makes sure they are complete? Let me guess, some centralised/external entity? So, there's some part associated with a token. What's to stop me from associating the same part with a different token? Or with 100 tokens? I'm guessing there is some centralised agency that verifies that a part is associated with a token through the part's serial number and that: a) no other token is associated with the same number and b) the seller associates serial numbers, and not some random numbers with the token? I'm not even going into such things as "seller A sold part B to buyer C, received the money and never sent the part", let's start with documents, parts, tokens and associations. |
As far as how to build that trust goes, what you're talking about is similar to the certificate signing problem. There are at least two ways to do this — a hierarchy trusted by everyone (akin to PKI) and a decentralized web of trust. Blockchains let you do either or both of those things since entities can sign off on the provenance on the blockchain. You can also have multiple entities sign off on it, similar to GPG keys.