oasisprotocol / oasisprotocol/oasis-sdk
Support synchronous cross-contract queries
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 90
- Forks
- 35
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 5
Description
Being able to synchronously query cross-contract state (without the need of emitting messages and using callbacks), would make some use-cases much nicer to implement.
Ref: cosm-wasm internal queries: https://docs.cosmwasm.com/docs/0.14/architecture/query/#internal-queries
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked CosmWasm internal-queries documentation and compare its synchronous cross-contract query model with the SDK's current message-and-callback approach. Identify the contract and runtime entry points involved, then define support for synchronous cross-contract state queries and verify that the existing callback-based flow remains unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100