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
Right now, it’s not clear if anything pertaining to the ZK part of light client should get stored (within the IBC store of Cosmos SDK chains) and updated during each light client update?!
Through this exploratory task we aim to learn the behaviour of a ZK WASM client by developing a naive client that enables ZK state transitions without relying on any information from Sovereign SDK chains.
The text was updated successfully, but these errors were encountered:
Background
Right now, it’s not clear if anything pertaining to the ZK part of light client should get stored (within the IBC store of Cosmos SDK chains) and updated during each light client update?!
Through this exploratory task we aim to learn the behaviour of a ZK WASM client by developing a naive client that enables ZK state transitions without relying on any information from Sovereign SDK chains.
The text was updated successfully, but these errors were encountered: