Skip to content

fix: use finalized commitment for blocktime #2157

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

Merged
merged 2 commits into from
Dec 2, 2024

Conversation

guibescos
Copy link
Contributor

@guibescos guibescos commented Dec 2, 2024

By getting a finalized block, it is less likely than getBlockTime fails.

Copy link

vercel bot commented Dec 2, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
api-reference 🛑 Canceled (Inspect) Dec 2, 2024 4:57pm
proposals ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 2, 2024 4:57pm
staking ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 2, 2024 4:57pm
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
component-library ⬜️ Ignored (Inspect) Visit Preview Dec 2, 2024 4:57pm
insights ⬜️ Ignored (Inspect) Visit Preview Dec 2, 2024 4:57pm

@guibescos guibescos merged commit d290f4e into main Dec 2, 2024
9 checks passed
@guibescos guibescos deleted the fix/use-finalized-commitment-for-timestamp branch December 2, 2024 16:57
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.

3 participants