| Capability | Backwards-compatible? | Description | Property |
|---|---|---|---|
| Multi-Activity Agreement | Yes | Negotiate ability to create multiple activities under single Agreement. Use golem.srv.caps.multi-activity property in Demand/Offer to indicate node's support for Multi-Activity. If counterparty does not support Multi-Activity, the node falls back to single Activity per Agreement behaviour. |
golem.srv.caps.multi-activity |
| Restart Proposal Negotiations | Yes | Agent is allowed to restart negotiations, by sending Counter Proposal, after he rejected Proposal at some point. Counter-party will receive regular ProposalEvent in this case. Only Agent rejecting Proposal has initiative in restarting negotiations, rejected Agent can only wait for this to happen. To indicate, that Proposal rejection isn't final and negotiations can be restarted later, Agent can set golem.proposal.rejection.is-final (bool) field in Reason structure. If this value is set to false, Agent can free any state related to this negotiation. The same field can be set in Reason sent in Reject Agreement operation. Requestor can send new counter Proposal after some period of time or propose the same Agreement for the second time. (No change to specification) |
|
| Command progress reporting | Yes | ExeUnit can report progress of executed commands. Specification | golem.activity.caps.transfer.report-progress golem.activity.caps.deploy.report-progress |
| Payment version protocol | No | Payment protocol version (golem.com.payment.protocol.version) shows what payment capabilities each node implements. New payment features require higher version. |
golem.com.payment.protocol.version |