-
Notifications
You must be signed in to change notification settings - Fork 373
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
ProtocolId Registry #2537
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed this with @markusbkoch and decided to put down some thoughts about the ProtocolId Registry in an issue for any future developments of linear pools:
In general, the idea of having a protocol Id in the Linear pools (specifically in the ERC4626 linears) is for the user (SDK, frontend, backend, api, etc.) to be able to identify the underlying protocol. This can be used mainly for two purposes:
First of all, this feature is completely unused currently. Neither the frontend, nor the SDK or the backend make use of it.
I only stumbled on the ProtocolId Registry by accident. When investigating it, I found a few drawbacks which make me reluctant to integrate it:
While I do like having as much data as possible onchain and also query data from there, above points make me still use hardcoded tokens addresses. It let's me keep full flexibility although it is more work to add new tokens for a protocol.
The text was updated successfully, but these errors were encountered: