Skip to content

chore(entropy) Dyamic Fee table #773

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 13 commits into from
Jul 30, 2025
Merged

Conversation

aditya520
Copy link
Member

@aditya520 aditya520 commented Jul 28, 2025

Description

This PR take updated configs from fortuna v1/chains/configs and updates contract address table. I use network-id/chain-id to map with viem to get up-to-date explorer and RPC, hence removes the need of updating docs for new chains.
Moreover, we can manually edit/add link and rpcs as some chains are still not supported by viem.

Type of Change

  • New Page
  • Page update/improvement
  • Fix typo/grammar
  • Restructure/reorganize content
  • Update links/references
  • Other (please describe):

Areas Affected

Checklist

  • I ran pre-commit run --all-files to check for linting errors
  • I have reviewed my changes for clarity and accuracy
  • All links are valid and working
  • Images (if any) are properly formatted and include alt text
  • Code examples (if any) are complete and functional
  • Content follows the established style guide
  • Changes are properly formatted in Markdown
  • Preview renders correctly in development environment

Related Issues

Closes #

Additional Notes

Contributor Information

  • Name:
  • Email:

Screenshots

Copy link

vercel bot commented Jul 28, 2025

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

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 30, 2025 5:18pm
documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 30, 2025 5:18pm

Copy link
Contributor

@tejasbadadare tejasbadadare left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable to me, left a couple comments. It would be great if you also run it by someone with better TS chops, maybe @cprussin ?

chain.reveal_delay_blocks !== 1 ? "s" : ""
}`,
gasLimit: chain.gas_limit.toLocaleString(),
default_fee: chain.default_fee,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should show this since it could confuse people or lead them to hardcode a value. Can we omit this or point them to the fee table with the correct dynamic values?

Copy link
Member Author

@aditya520 aditya520 Jul 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are not showing this at all. It's just there, not using this.

explorer?: string;
}

export const EntropyDeploymentsConfig: Record<string, ChainOverride> = {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe rename this to EntropyDeploymentsOverride or add a comment to communicate that this overrides the data from fortuna's chains/configs/ API?

Copy link
Contributor

@cprussin cprussin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly LGTM but some small things, biggest thing is to not abuse components where a hook should be used and to avoid typecasting

KemarTiti and others added 2 commits July 30, 2025 12:10
* Update solana_mainnet.json

ADD JUPSOL TO DOCS

* Update solana_mainnet.json

---------

Co-authored-by: Ali Behjati <[email protected]>
* chore(entropy) What's new

* update

* requested changes
@aditya520 aditya520 merged commit e625bc2 into main Jul 30, 2025
5 checks passed
@aditya520 aditya520 deleted the chore(entropy)-dynamic-fee-table branch July 30, 2025 18: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.

5 participants