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
Objective:
Test if a developer on Osmosis can send an inference request to Warden via IBC, and retrieve the processed inference result.
Steps:
Set Up Test Environments:
Osmosis: Use a testnet or mainnet Osmosis account with IBC enabled.
Warden: Ensure Warden is set up to receive IBC transactions and process inference requests.
Deploy Inference Contract on Warden:
Deploy a smart contract on Warden with an inference_request function.
The function should accept input data, trigger inference, and store/return the result.
Send Inference Request from Osmosis to Warden:
On Osmosis, create an IBC transaction that calls the inference_request function on Warden with the required parameters (e.g., input data).
The message will be routed to Warden via IBC.
Process the Inference on Warden:
Warden processes the inference request and stores the result in the smart contract.
Fetch the Inference Result:
Query the result from Warden via another IBC transaction or callback mechanism, once the inference is processed.
Key Points:
Ensure that the IBC message is routed successfully from Osmosis to Warden.
Verify that the inference result is correctly returned after processing on Warden.
Success Criteria:
The inference request is sent from Osmosis, processed by Warden, and the result is fetched back via IBC.
The text was updated successfully, but these errors were encountered:
Objective:
Test if a developer on Osmosis can send an inference request to Warden via IBC, and retrieve the processed inference result.
Steps:
Key Points:
Ensure that the IBC message is routed successfully from Osmosis to Warden.
Verify that the inference result is correctly returned after processing on Warden.
Success Criteria:
The inference request is sent from Osmosis, processed by Warden, and the result is fetched back via IBC.
The text was updated successfully, but these errors were encountered: