Note private store key flexibility (ref #145)

cosmos · Sep 20, 2019 · c88e721 · c88e721
1 parent 9f7f20c
commit c88e721
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 2 deletions.
diff --git a/spec.pdf b/spec.pdf
diff --git a/spec/ics-004-channel-and-packet-semantics/README.md b/spec/ics-004-channel-and-packet-semantics/README.md
@@ -78,7 +78,7 @@ interface Channel {
 - The `nextSequenceSend`, stored separately, tracks the sequence number for the next packet to be sent.
 - The `nextSequenceRecv`, stored separately, tracks the sequence number for the next packet to be received.
 - The `connectionHops` stores the list of connection identifiers, in order, along which packets sent on this channel will travel. At the moment this list must be of length 1. In the future multi-hop channels may be supported.
-- The `version` string stores an opaque channel version, which is agreed upon during the handshake. This can determine module-level configuration such as which packet encoding is used for the channel.
+- The `version` string stores an opaque channel version, which is agreed upon during the handshake. This can determine module-level configuration such as which packet encoding is used for the channel. This version is not used by the core IBC protocol.
 
 Channel ends have a *state*:
 

diff --git a/spec/ics-024-host-requirements/README.md b/spec/ics-024-host-requirements/README.md
@@ -87,7 +87,13 @@ The `privateStore`:
 
 ### Path-space
 
-At present, IBC/TAO utilises the following path prefixes for the `provableStore` and `privateStore`. Future paths may be used in future versions of the protocol, so the entire key-space in both stores MUST be reserved for the IBC handler.
+At present, IBC/TAO utilises the following path prefixes for the `provableStore` and `privateStore`.
+
+Future paths may be used in future versions of the protocol, so the entire key-space in the provable store MUST be reserved for the IBC handler.
+
+Parts of the private store MAY safely be used for other purposes as long as the IBC handler has exclusive access to the specific keys required.
+Keys used in the private store MAY safely vary as long as there exists a bipartite mapping between the key formats defined herein and the ones
+actually used in the private store implementation.
 
 | Store | Path format | Value type | Defined in |
 | -------------- | ------------------------------------------------------------------------ | ----------------- | ---------------------- |