D-States
We require a reusable capability in the REST and JSON-RPC API to manage dynamic client-defined states which we refer to here on as D-States. A D-State logically has the following fields:
API functions are required for CRUD operations.
The state can be created by any party.
Only the updaters
are allowed to update or delete the state.
During update on the following fields can be altered:
- participants
- updaters
- value
- tags
The state must be retrievable using its linearState ID.
The state can be queried using its tags.
Outside of scope:
- alterations to the tag query API to allow for complex queries. For now, we propose a simple implicit logical
AND
of all tags specified in the query.