Seven or so Sentiments Surrounding Success

Assign Onward Should Stay:
  • Simple
  • Secure
  • Small
  • Scalable
  • Synchronized
  • Shared
  • Social
  • Serviceable
Less lyrically,


in rough order of priority:
  • Secure
    • Establish un-alterable records, including records of title
      *Title meaning: ownership of a number of shares which can be divided, or merged when assigning onward.
    • Assignment of title
      *Assignment of title means recording a change of ownership of shares from the holder of one secret to the holder of a different secret.
      can only be accomplished with a secret that need never be revealed
    • Resistant to malicious confusion of records
  • Open (shared), anyone can:
    • receive or assign title
      • receive title under a secret that only they know
      • propose assignment of title to any secret known/controlled by another
        *Assignment of title requires offer and acceptance, each identity (public key) can only receive title once, therefore it is required that the holder of the private key accept assignment of title under their public key.
    • obtain all records
    • verify validity of all records
      • title
        • chain of title
          *For any given title to shares, anyone can trace the source(s) of the shares back to the genesis block.
        • absence of double spend
          *confirm that title has not been assigned from the record of initial receipt of title through to the recording of assignment of title.
      • recording process
    • participate in the recording process
      *by running software that creates, validates, and proposes pages and blocks for inclusion in the blockchain. This goal will not be addressed for single chains until the Ⓐ² protocol, although anyone who wants to can start their own independent Ⓐ¹ blockchain.
    • examine
      *also copy and modify if desired. Essentially, no dependence on protections like trade secrets, copyright, patent or legislation to secure functionality of the system.
      the computer code that implements the system
  • Accessible
    • simple, (small) clearly expressed processes, not un-necessarily baffling
    • minimize real-world cost of participation (social) in any part of the process
      • easy to detect loss of synchronization between recording nodes
    • serve the users of the system, not the owners of the infrastructure
    • scalable refers to the abilty of multiple chains to interact, serving large numbers of people and transactions not by a single massive system, but by a cooperating network of smaller systems each of which is readily understood and maintained by a single person.
      *This doesn't mean a single person should do all the setup and maintenance of each chain by themselves, it's better handled by a team, but on a scale that a single member could easily handle it all if they wanted/needed to.
    • Launch Time: when it's ready.
  • Extensible (serviceable)
    • interoperability with other systems
    • designed for inclusion of or migration to new technologies when desired
    • tunable parameters to adjust to changing use conditions
As with any non-trivial project, several goals are in opposition. The goal not stated above is to optimize tradeoffs making the system as valuable as possible to users. Users are the value in the system, the system should return as much of that value as possible to them, encouraging wider adoption and increasing total value.

See also: Buzzword Bingo.