Coordinator selector / delegation policy for multi-party endorsement domains

[hosie]

What would you like to be added?

In domains ( such as Pente) where the spending rules for states allow any one of a group of parties to spend the state, then we need to coordinate the assembly of transactions across multiple nodes so that we can maximize the throughput by speculative spending new states and avoid transactions being reverted due to double concurrent spending / state contention.

The proposal for achieving this, is to implement a policy that complies with combination 2 + 1 from #327.

write up moved to architecture docs in #463

[github-actions]

This issue is stale because it has been open 30 days with no activity.

[github-actions]

This issue is stale because it has been open 30 days with no activity.

[github-actions]

This issue is stale because it has been open 30 days with no activity.

[hosie]

Concrete work items needed to support the algorithm described above:

• controlled handover on range boundary
  • transfer domain context to new coordinator node
  • previous coordinator abandons non dispatched transactions
  • sender re-delegates non dispatched transactions to new coordinator
  • new coordinator waits until the blockchain has caught up with the inflight domain context then starts submitting
• adjustments to the endorsement handshake to accommodate variations in block height between nodes
• adjustments to the delegation handshake to accommodate variations in block height between nodes
• framework and domain changes to define the committee make up and communicate that to all nodes
• (pending finalized decision) Framework and domain ( node side and base ledger contract) changes for assured once intent fulfillment.
• copy the words and diagrams above into an architecture document

[github-actions]

This issue is stale because it has been open 30 days with no activity.

[github-actions]

This issue is stale because it has been open 30 days with no activity.