MAID => SNToken issuance at launch

[jlpell]

@Nigel

Instead of simply recording the public key for transaction signatures, the hash of a “contract” was recorded in the DBC. A contract is a boolean expression describing the conditions under which a DBC will be reissued.

Furthermore the contract can apply to more than a single DBC transaction. eCache supported “combined” transactions in which two or more DBC transactions could be presented to the mint at the same time, the conditions of each of the input DBCs referring to the output DBC templates of the other transaction. This allows creating schemes that allow swapping the ownership of two certificates presented by two different users

@happybeing

The multi input multi output features described above for combined transactions appear to describe how to handle farming rewards in a secure way.

Spitball 2: a) If initial dbcs are created and seeded throughout the network, then b) a farmer (or elder?) could combine 1 with proof of a valid storage/retreival to c) get the dbc reissued with a portion of it equal to the current farming reward and then transferred to the farmer.

The process is a “Safe Contract”, but it also bears resemblance to classic safecoin by analogy.