-
Notifications
You must be signed in to change notification settings - Fork 205
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.
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
Data Model and Events and Docs #2747
Labels
Milestone
Comments
Some standard textual representation of events:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need a better and more formal data model, which we should be able to represent clearly with the events API (which downstream users should be working off of). There should be a hierarchy of which events are at the top level (
NEW_BLOCK
), which events are sub-events of each of those (NEW_TRANSACTION
,ORDER_MATCH_EXPIRED
), and so forth (NEW_FAIRMINTER
) till the end (CREDIT
).It should also be clear when we use
asset_events
. And which events are associated with each transactions, per #2796An example use case is "I want to get a list of all recent transactions sorted by type (dividend, bet, send, fair minter, issuance, dispenser, dispense, order, etc.) that's comprehensive and with no duplicates."
The trick is to not have this too coupled to the DB stuff and the
messages
table.Successor to #2746 and #2743
The text was updated successfully, but these errors were encountered: