PAOM tee shirt

The Tee Shirt Protocol


I am attaching a preliminary write up of the tee shirt protocol that we are working on at PAOM. Right now only for tee shirts 🙂

The Tee Shirt Protocol

The goal of Tee Shirt Protocol is to break the manufacturing supply chain into different components and allow different actors to participate in and own different stages of product development.

To start this will all be implemented for a small subset of (PAOM) PRODUCTS (we will launch with one – a tee shirt)

  1. Convert the designed PRODUCT (teeshirt) into a non-fungible token that keeps track of the history of creation and ownership.
  2. Add an additional interface method to the non-fungible that allows for reification (the creation of a physical object). Ideally there should be an option to allow forms of reifications and different people to reify, but right now it will just be PAOM.

III. The Flow

  1. a) A designer creates a piece via a web interface
  2. b) The designer connects this with her metamask account
  3. c) The address is connected as the creator or designer of this piece with the following data:
    • the type of piece – are there sizes (maybe we put this on IPFS or this could be its own smart contract or built into the smart contract – to start will just be tee shirts so lets not spend too much time on this – we can hard code it and call it the tee shirt protocol)
    • how many can be made (if there is a limit)
    • the print IPFS
  1. d) This is submitted to a DB
  2. e) A cron job or lambda process or worker process pulls this new data
  3. f) a modified paom non-fungible token is created
  4. g) the print file (also in db) is associated with the token and is added to IPFS
  5. e) A website pulls all available paom tokens for sale (like cryptokitties)
  6. f) Someone buys a paom Token with metamask with the following data:

available for sale

available for reification

quantity available if designer did not specify

  1. g) owner transfer is triggered on the smart contract:

Owner information changes from designer to owner, or from last owner to owner and the paom token is modified – the smart contract function is triggered

  1. h) A website pulls all available paom tokens for reification (like cryptokitties)
  2. I) Someone reifies a paom Token with metamask with the following data:

– size (if specified)

– a shipping address (QUESTION – how do we store obfuscate shipping address)

– can we store this on ipfs obfuscated? PGP?

  1. J) Smart Contract update – order made

– Move funds to temp escrow account

– 50% money disbursed for manufacturing

– availability of limited edition pieces reduced

  1. K) Smart Contract update – order shipped

– rest money disbursed for manufacturing, designer ownership, each past owner, current owner, we could even add past reifiers

  1. L) Smart Contract update – order problem (NOT v1)

– Everyone involved with the product at any point (all buyers, manufacturers, owners and designer) vote on whether to

– refund 50% of manufacture fee, design commission and sales commission

– refund everything

– refund nothing

– all parties can leave comments

  1. The data we are keeping track of:
  • the original designer
    • everyone that has every own the token
    • the print file -IPFS
    • how many times a piece can be reified (limited edition). This is set by the designer or current owner of the virtual object if the designer does not specify.
    • current reifications (open orders)
      • shipping address
      • variant or customization information (size only for now)
  1. Other data for v2:
  • everyone that has ever reified the token
    • who owned the token while it at each point of reification.
    • possible manufacturers
    • who has ‘manufactured’ each reification
    • variant or customization information expanded (fabric, notions, etc)

Leave a Reply