6 ms·
I would just like to say that if anyone has a rational counterargument to this, I really want to hear it. This is precisely the observation past which the logic
by rebelos 6y ago
I would just like to say that if anyone has a rational counterargument to this, I really want to hear it. This is precisely the observation past which the logic becomes less coherent in just about any conversation I've had on blockchain applications.
- beh9540 6y agoMaybe instead of an image, both parties could use an ODB reader that signs the mileage cryptographically, and pushes it to the blockchain? This way both parties could verify the transaction was completed as contracted (IE no joyrides). I'm still in the camp this probably doesn't need blockchain, but that would at least handle the image manipulation problem.
- FunkyMJ 6y agoWhy can't you just sign the image of the odometer?
- thekevan 6y agoWell in this specific example, what would they change to photo to? The case is to stop joyrides. Who would be able to take a joyride and end up with the odometer exactly as they had Photoshopped it to hours or days ago? But yes, depending on the application, photos can be manipulated. But that is stating the problem with using photos, not the timestamping app.
- saati 6y agoIt would be cool to have technology that tells you how long is a trip, oh wait, precise maps are hundreds of years old.
- sebmellen 6y agoPlease see my comment in response to the grandparent comment. I think it will address your concerns with a rational counterargument. Basically, yes, you could, in theory, maybe, sort of, possibly, build a similar system without a public blockchain. But why? I'm sure there are people who can build houses with a few hand tools, but there's a reason we have power tools and heavy machinery — they are more efficient and fit the job better. The same goes for blockchain in this case. If you can point out where my logic is incoherent, please do, but to me the following: "oh, just set up a distributed git repo or database with checksums and append-only permissions that you control but replicate to other servers not controlled by you so that you can't tamper with the outputs and read from that global state and verify against the other mirrors of the database or repo every time you read from global state" sounds like a stupider alternative to blockchain. This is what blockchains were made for!!! Distributed consensus!
- Spivak 6y agoI think the thing that you have to answer is why you need distributed consensus. You're a startup with a business relationship with your customers -- you're the common trusted party. Your customers are using your software so if they were worried about you cheating the system they (and you) have bigger problems since your business is reputation. Also what is the point of mining or and proof of $whatever system? The thing your customers provide is a signed attestation of some fact and you provide a signed attestation of the time that fact was received. Why is there a need to "vote" in way on what is true? This is just a database or honestly a folder of signed messages. And I say signed, but none of this really need to be cryptographic in any way since they're customers that could just authenticate to you which is as much a proof of their identity as any key.
- sebmellen 6y agoYou're right about everything but that we're the common trusted party. We have a relationship with the receiver. They want to be sure nothing happens in transit from origin. We do not have a business relationship with the transporters (many of whom are independent). The way the transporters know they're getting a fair deal is precisely because we are not the source of truth — a database outside of our control is (a blockchain, in this case). We're not voting on what is true, we're relying on the blockchain as an immutable representation of state. An append-only, distributed database that we do not control. And please don't downvote my comments out of a misunderstanding. That's juvenile.
- Niksko 6y agoI don't want to malign the transporters in your business, but the chance that they actually meaningfully understand the nuance of this is slim to none. This is a trust problem. Either people trust you, or they don't. You've attempted to increase their trust in you by creating a system that would increase somebody's trust if they had your understanding of the underlying technology. Very few people have this, and the overlap between the people with that understanding and your customers and clients is vanishingly small.