-
Notifications
You must be signed in to change notification settings - Fork 29
feat: inclusion lists #158
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
Conversation
dc885d1
to
c5dfae8
Compare
empty api basic api & IL fetching move list fetching into chain event updater better IL slot cutoff timing .gitignore local config etc lint cleanup
bfad01f
to
3af26b2
Compare
a2c69f5
to
3923e3c
Compare
let slot: i32 = self.head_slot.try_into().unwrap(); | ||
let slot_coordinate = get_slot_coordinate(slot, pub_key, parent_hash); | ||
let (postgres_result, redis_result) = tokio::join!( | ||
self.database.save_inclusion_list(&inclusion_list, slot), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be a good not to join on the db task here. We've seen some spikes when writing to the db lately and wouldn't want to delay the completion of this process_slot task.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, that's a fair point - we could move the error handling, etc., into the future and leave it as a tokio::spawn, so we don't await it?
Working V1 for relay support of inclusion lists.
/relay/v1/builder/inclusion_list
which returns a copy of this slots relay list (if one exists)We fetch the IL as part of the housekeeper and communicate with the API through a redis pub sub channel. We also store inclusion lists in postgres so we can look back at things if needed.