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.

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

Track lost sat ranges #1227

Merged
merged 7 commits into from
Jan 16, 2023
Merged

Track lost sat ranges #1227

merged 7 commits into from
Jan 16, 2023

Conversation

casey
Copy link
Collaborator

@casey casey commented Jan 14, 2023

This will allow us to easily see which sats have been lost on every chain by looking up the null outpoint.

This depends on #1223, which should be merged first.

@casey casey enabled auto-merge (squash) January 16, 2023 19:05
@casey casey disabled auto-merge January 16, 2023 19:05
@casey casey enabled auto-merge (squash) January 16, 2023 19:05
@casey casey linked an issue Jan 16, 2023 that may be closed by this pull request
@casey casey removed a link to an issue Jan 16, 2023
@casey casey merged commit a78c42b into master Jan 16, 2023
@casey casey deleted the track-lost-sat-ranges branch January 16, 2023 19:09
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.

Update null outpoint with lost sat ranges in OUTPOINT_TO_SAT_RANGES table
2 participants