Uploaded image for project: 'Corda'
  1. CORDA-2477

Signature Constraints end-user documentation is limited

    Details

    • Type: Story
    • Status: Done (View workflow)
    • Priority: Medium
    • Resolution: Done
    • Affects versions: Corda 4 RC02
    • Fix versions: Corda 4.1
    • Components: None
    • Labels:
      None
    • Feature Team:
      Corda Core
    • Target Version/s:
    • Story Points:
      2
    • Sprint:
      V&M Sprint 4, V&M Sprint 5, Corda Core Sprint 1, Corda Core Sprint 2

      Description

      Whilst there is a detailed design on Signature Constraints,
      the end-user documentation is limited to a single paragraph embedded quite far down on the following page:
      https://docs.corda.net/head/api-contract-constraints.html

      Signature constraints. These enforce an association between a state and its associated contract JAR which must be signed by a specified identity, via the regular Java jarsigner tool. This is the most flexible type and the smoothest to deploy: no restarts or contract upgrade transactions are needed. When a CorDapp is build using corda-gradle-plugin the JAR is signed by Corda development key by default, an external keystore can be configured or signing can be disabled.

      For example, the highlighted sentence above requires further clarification and elaboration with examples.

      Overall, a more prominent and better explanation of this key new feature would be welcome.

        Attachments

          Activity

            People

            • Assignee:
              dan.newton Dan Newton
              Reporter:
              Jose.Coll Jose Coll
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: