We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description Currently the token list is shared through the link of https://raw.githubusercontent.com/superfluid-finance/tokenlist/main/superfluid.tokenlist.json or the NPM package from https://www.npmjs.com/package/@superfluid-finance/tokenlist. It's not a good look to share it through GitHub directly, i.e. it would would be better look to share it through our domain, e.g. https://tokenlist.superfluid.finance or https://superfluid.finance/superfluid.tokenlist.json
Solution Possible solution A. Set up Route53/Cloudfront in front of https://raw.githubusercontent.com/superfluid-finance/tokenlist/main/superfluid.tokenlist.json Possible solution B. Add a build step to upload the token list to S3 on publishing and expose that through our domain.
The text was updated successfully, but these errors were encountered:
should we add to infra backlog?
Sorry, something went wrong.
philipandersson
No branches or pull requests
Description
Currently the token list is shared through the link of https://raw.githubusercontent.com/superfluid-finance/tokenlist/main/superfluid.tokenlist.json or the NPM package from https://www.npmjs.com/package/@superfluid-finance/tokenlist. It's not a good look to share it through GitHub directly, i.e. it would would be better look to share it through our domain, e.g. https://tokenlist.superfluid.finance or https://superfluid.finance/superfluid.tokenlist.json
Solution
Possible solution A. Set up Route53/Cloudfront in front of https://raw.githubusercontent.com/superfluid-finance/tokenlist/main/superfluid.tokenlist.json
Possible solution B. Add a build step to upload the token list to S3 on publishing and expose that through our domain.
The text was updated successfully, but these errors were encountered: