kaal:claim:3405401-034

The required review of counterparty history is possible through a platform that creates reputation for both parties and for the smart contract itself, so reputation must attach to code as well as to persons.

Source quote, verbatim

This is possible through a platform that creates reputation for both parties and for the smart contract itself.

From

Wulf A. Kaal, Decentralized Commerce – A Primer on Why Decentralized Reputation Verification Systems Are Needed (2019), VI. Decentralized Reputation as the Solution, p. 8
https://ssrn.com/abstract=3405401 · source PDF

Cite as

Wulf A. Kaal, Decentralized Commerce – A Primer on Why Decentralized Reputation Verification Systems Are Needed (2019). SSRN: https://ssrn.com/abstract=3405401

Classification

designsupport: arguedreputationsmart-contracts

Verify

The quote above is an exact substring of the source PDF, whose sha256 is bc2d6f0ddc0852fb4085c4543c7c1dec19aaf8745eb67e3acc637e552bd7fb7d. Extraction method: pdf-text-layer.
Attestation record: colloquium/attestations/76d91d71e1b96f7f...json
Verify the binding yourself: curl -s https://wulfkaal.github.io/claims/3405401-034.md | sha256sum