You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We consider the leashing implementation utilising the existing LoE mechanism.
364
364
365
-
1. We introduce a `LeashingState blk = Map LeashID (AnchoredFragment (HeaderWithTime blk))` structure to keep the leashing fragments associated with each leashing client.
365
+
1. We introduce a `LeashingState blk = Map LeashId (AnchoredFragment (HeaderWithTime blk))` structure to keep the leashing fragments associated with each leashing client.
366
366
2. We update the `LocalStateQuery` server to interact with that state:
367
367
- If a new client connects to the server with `leashId`, the server will put the `leashId` together with the client's leashing fragment into the leashing state;
368
368
- The leashing fragment is calculated using the current chain of the node and the `Target (Point Block)` provided by user. It's either a `SpecificPoint pt`, `ImmutableTip` or `VolatileTip`.
0 commit comments