# kaal:claim:3405401-034

**Claim.** 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.

**Type.** design  **Support.** argued

**Source quote.**

> 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, page 8

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

**Verify.** sha256 of source PDF `bc2d6f0ddc0852fb4085c4543c7c1dec19aaf8745eb67e3acc637e552bd7fb7d` at https://raw.githubusercontent.com/wulfkaal/Academic-Papers/main/papers/pdf/Kaal%20-%202019%20-%20Decentralized%20Commerce%20%E2%80%93%20A%20Primer%20on%20Why%20Decentralized%20Reputation%20Verification%20Systems%20Are%20Needed.pdf

**Topics.** reputation, smart-contracts

**Keywords.** reputation-platform, smart-contracts, design, dual-reputation

**Canonical form.** This markdown file is the canonical hashed representation of the claim. Its sha256 is the content hash used for attestation.