Skip to content
This repository was archived by the owner on Aug 7, 2018. It is now read-only.
This repository was archived by the owner on Aug 7, 2018. It is now read-only.

ALP08: Asset-Based Confederations #10

Open
@tenthirtyone

Description

@tenthirtyone

Proposal: Asset-based Confederations

Author(s): Alex Sherbuck [email protected]

Last updated: 2018/02/07

Abstract

Agree upon a scoring mechanism for non-fungible assets. Form a confederation where asset holdings represent each sovereigns' votes. Voting weight is determined by asset scores. Weight may be delegated to represent split control of an asset.

Using this property we may form organizations around our collective asset holdings. This is a means of distinguishing value between non-fungible assets, whose value differ by their nature.

Proposal

Upon forming an organization (Cryptokitties Collectors Club) we set rules relative to our interests. We assign point values based on the traits of our NFTs (rare genes = 10 points, common genes = 1 point). All NFTs are scored equally. NFTs determined to be of the highest value by the group are awarded the highest voting weight.

As the group makes decisions they may use their NFT weight to vote to come to consensus.

Split voting weight can be used to determine internal decisions for joint ownership (Renting space in a building). In the case of an asset that is co-owned or leased among multiple parties control of voting weight may be split according to ownership percentage.

A DAO may form around a single asset split between many owners.

Rationale

ERC-20 Voting is effective to represent shares or investment in an organization. ERC-721 voting can represent interests that move beyond financial stake. Asset voting weight gives rise to governing bodies around any asset holding.

All vote weight may be renting or sold, but the asset owner still retains the property rights of the asset by holding the NFT.

Implementation & Example

Weighted Digital Asset Registry - w/ DAO voting

EIP

Changelog

March 1 - Cleaned up explanation and examples

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions