informalsystems / informalsystems/quartz
Make enclave response optional
Open
- Dominant language
- Rust
- Stars
- 63
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
## Summary
An enclave may choose to not respond to an on-chain message/event.
Note: `Sequenced` messages should technically always be responded to, to indicate that the encalve processed them, so need to think more about how this is to be implemented.
## Acceptance Criteria
TBD
Contributor guide
Research direction
No files or tests are named. Start by tracing how the enclave handles on-chain messages and events, with particular attention to Sequenced messages. Clarify the response semantics and acceptance criteria before implementing the optional-response behavior.
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