Clarify and enhance data model of counterparties and signatories about themis-contract HOT 4 CLOSED

Is this the correct type for what you're proposing?

enum Counterparty {
    Collective(Set<Signatory>),
    Singular(Signatory)
}

from themis-contract.

Is this the correct type for what you're proposing?

Sure, that's how you'd implement it in Rust 👍

from themis-contract.

I just picked rust syntax thinking it would be most perspicuous in this context, but guess I should have used TypeScript. The type reflecting this structure should be the same, regardless of the syntax.

from themis-contract.

We are no longer going to implement this model in v0.2 (currently on branch prototype/v2, soon to be merged to master).

We're now requiring that contracts expose a signatories array that, at a minimum, is of the following (Dhall) type:

let Signatory : Type =
  { id : Text
  , name : Text
  , email : Text
  }

let signatories : List Signatory =
  [ { id = "signatory1"
    , name = "Harry Henderson"
    , email = "[email protected]"
    }
  ]

in { signatories = signatories }

You can add any additional arbitrary fields to the signatory type (these will be passed through to your contract when rendering), but any notion of counterparties/organizations/etc. is totally up to you to define in your own contract. This is the only way we're going to get flexibility, while also providing Themis Contract with the minimum amount of information it needs to facilitate its signing mechanics.

from themis-contract.