Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TAO V2 support in 07 client #1137

Merged
merged 20 commits into from
Aug 21, 2024
Merged
Prev Previous commit
Next Next commit
fixes
  • Loading branch information
sangier committed Aug 21, 2024
commit 9e3ebfea6d533251bec113710d6f43b9c08d352c
4 changes: 2 additions & 2 deletions spec/core/v2/ics-004-packet-semantics/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ In order to provide the desired ordering, exactly-once delivery, and module perm

`Identifier`, `get`, `set`, `delete`, `getCurrentHeight`, and module-system related primitives are as defined in [ICS 24](../ics-024-host-requirements).

See [upgrades spec](../../ics-004-packet-semantics/UPGRADES.md) for definition of `pendingInflightPackets` and `restoreChannel`.
See [upgrades spec](../../ics-004-channel-and-packet-semantics/UPGRADES.md) for definition of `pendingInflightPackets` and `restoreChannel`.

A *channel* is a pipeline for exactly-once packet delivery between specific modules on separate blockchains, which has at least one end capable of sending packets and one end capable of receiving packets.

Expand Down Expand Up @@ -184,7 +184,7 @@ enum PacketReceipt {

The architecture of clients, connections, channels and packets:

![Dataflow Visualisation](../../ics-004-packet-semantics/dataflow.png)
![Dataflow Visualisation](../../ics-004-channel-and-packet-semantics/dataflow.png)

### Preliminaries

Expand Down