Skip to content
This repository was archived by the owner on Feb 24, 2025. It is now read-only.

Add fields to chain JSONs that specify chain idiosyncrasies #264

Open
bbenligiray opened this issue Apr 30, 2024 · 1 comment
Open

Add fields to chain JSONs that specify chain idiosyncrasies #264

bbenligiray opened this issue Apr 30, 2024 · 1 comment

Comments

@bbenligiray
Copy link
Member

bbenligiray commented Apr 30, 2024

PLACEHOLDER

@bbenligiray
Copy link
Member Author

@bdrhn9 we want to add parameters to chains so that you don't have to hardcode chain aliases in https://github.com/api3dao/nodary-rpc-watcher/blob/main/src/total-fee.ts

What would these parameters be? I think there are two options

  • Parameterize based on the stack they use, for example op-stack, etc. I don't like this because there are probably multiple versions of that that we'll have to treat differently.
  • Parameterize based on how the chain should be treated. In this case we need a list of the variety of ways you treat the chains (in https://github.com/api3dao/nodary-rpc-watcher/blob/main/src/total-fee.ts), ideally as succinctly as possible

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant