Smart contracts

​

Template and instance

Template
  ├── allowed parameters
  ├── roles and parts
  ├── human-readable rendering
  └── optional lifecycle or state-machine rules
          ↓ instantiate
Contract instance
  ├── concrete parameter values
  ├── identified parties in roles
  ├── proposal and signature state
  └── current lifecycle state

​

Application responsibilities

• Use a template whose approval and compatibility are confirmed for the target Neuron.
• Bind Legal Identities to the intended parties and roles.
• Validate parameters before presenting human-readable text for signature.
• Persist the contract identifier and current proposal/signature state.
• Display the same material terms the application submits.
• Treat proposal, signature, and finalization as lifecycle states, not one synchronous request.
• Retrieve and verify the final contract rather than assuming the last command completed the workflow.

​

Learn, build, reference

• Overview: Agreements
• Quickstart: Contracts quickstart
• Guides: Agent API contract guide
• Concepts: Templates and instances, roles and parts, and lifecycle
• Reference: Contract operations