Skip to content

Conversation

@konradkonrad
Copy link
Contributor

Fixes #637

konradkonrad added a commit to shutter-network/shutter-api that referenced this pull request Oct 23, 2025
Copy link
Contributor

@jannikluhn jannikluhn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, just two comments where the text could potentially be slightly clearer


- **Topics (Offsets 0-3)**: The indexed parameters of the event log. A topic is
referenced by its index (0-3), where offset 0 is topic[0], etc.
- **Data (Offsets 4+)**: The non-indexed data section of the log. Offset
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For clarification, maybe add that this offset starts at 4 even if there's less than 4 topics.


### RLP Encoding Details

The RLP encoding format for the core structures is:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe clarify that these object definitions are supposed to be translated into (nested) RLP lists (so an event trigger definition becomes [contract_address, [...]]), but we write them as ordered objects to be able to name the list values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add rolling-shutter specs to include event-based decryption triggers

2 participants