kaal:claim:3782203-036

Paying contributors in reputation tokens rather than fees, and then distributing all fees as a periodic reputation weighted salary, defeats the sockpuppet attack because splitting a holding across many accounts yields exactly the same share of fees.

A periodic reputation-weighted salary will distribute all fees the DAO earns to all members. Individuals who perform tasks that bring fees to the DAO will be rewarded with reputation tokens, not the fees. Members who own more reputation tokens share in a larger percentage of the fees.

Craig Calcaterra, Wulf A. Kaal, A Technical Perspective on Decentralization (2021), How to build a DAO, p. 23
https://ssrn.com/abstract=3782203 · source PDF

Craig Calcaterra, Wulf A. Kaal, A Technical Perspective on Decentralization (2021). SSRN: https://ssrn.com/abstract=3782203

• anonymous DAOs with multiple accounts per member
• all DAO fees pooled and shared

designsupport: arguedreputationconsensus-and-securitydaotokenomicsai-and-agentsrisk-and-incentives

• restated_by kaal:claim:3799320-039 Reputation weighted salary distribution solves the sockpuppet attack, because a member who creates ten account...
• restated_by kaal:claim:3782210-018 Distributing salary equitably, for example equally to all members, is self-defeating: the obvious gaming strat...
• extends kaal:claim:3125827-004 Because all block creation fees are shared with the whole group as a reputation weighted salary, SPoS removes ...
• extended_by kaal:claim:5887242-022 Paying treasury distributions in fungible tokens or stablecoins in direct proportion to reputation holdings cr...
• extends kaal:claim:3441904-038 Optimized DAO governance should pay members only indirectly, through fungible salary tokens issued in proporti...
• extended_by kaal:claim:3782216-014 Reputation must be grounded to be meaningful, so reputation tokens should be minted only when policy premia en...
• restates kaal:claim:3652481-039 Reputation weighted salary distribution defeats sock puppet attacks, because a member who creates ten accounts...

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