Adapted appchain integration for new wasm functions #36
Conversation
ORA-408 Replace the Ignite client logic with wasm code
Currently most of the topic-specific weight-adjustment logic is ran within the b7s using the Ignite client. Ideally this is all callable within wasm. This implies that the fetching of current weights, the fetching of inferences from the appropriate timestep, the topic-specific weight-adjustment logic itself, and then the tx to write the new weights to the appchain should all be in wasm. If we do this, we can later add zk proofs to verify that this wasm was actually ran => that the right proofs were used and the right logic was ran upon them. Ideally, you're able to wrap all of that in the wasm for nodes of both Eth price + index topics. All those queries and txs could be written in cosmjs, which I hear is at least "somewhat" compilable to wasm (cc derek). At minimum (not ideal, but workable for now), if you can't get the cosmjs to compile to wasm, you wrap just the weight-adjustment part in wasm and provide some means of ensuring that only nodes capable of making these calls with a cosmos client are allowed to be headnodes for our weight-adjustment function calls, probably by setting certain attributes. |
No description provided.