Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update data collection spec #5

Merged
merged 1 commit into from
May 6, 2023
Merged

Update data collection spec #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions specs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,6 +162,9 @@ The response depends on the state of the smart contract, but it will be somethin
}
```

### Events
It is possible to send up to **16 fields** in events in a single transaction, and each field can be up to **255 bits**.

**HELP:**
1) Should we agree on particular structure for `Events` to identify its purpose? It could be the command (Add, Remove, Update, etc.).
2) When `events` are to be requested from the blockchain? Should we use a cron job or subscribe on node changes (if supported).
Expand Down