Skip to content
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

Add Optimism and Scroll to Production Database #352

Open
Shallysunny opened this issue Aug 7, 2024 · 1 comment
Open

Add Optimism and Scroll to Production Database #352

Shallysunny opened this issue Aug 7, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@Shallysunny
Copy link

User Story
As a developer, I want to add Optimism and Scroll to the production database so that these networks are available for use in the application.

Acceptance Criteria

  1. GIVEN the production database,
    WHEN the update script is executed,
    THEN Optimism and Scroll networks should be added to the list of supported networks.

  2. GIVEN the production database,
    WHEN queried,
    THEN the Optimism and Scroll networks should be retrievable along with their respective metadata.

Tech Details:

  • Add entries for Optimism and Scroll networks to the production database.
  • Ensure each entry includes necessary details such as:
    • Network name
    • Network ID
    • RPC URL
    • Explorer URL
    • Logo URL
  • Validate the data before insertion to avoid any inconsistencies.
  • Test the database update in a staging environment before applying to production.

Open Questions:

  • Are there any additional fields required for the network entries?
  • Are there any specific security or validation checks needed before updating the production database?

Notes/Assumptions:

  • Assume the existing database schema supports the addition of new networks.
  • Ensure the changes do not disrupt existing functionality.
  • Coordinate with the DevOps team to schedule a maintenance window for the database update if necessary.

Relevant log output:
(Include any relevant log output or error messages, if available)

Screenshots:
(Provide screenshots showing the data to be added, if available)

Additional Information:

  • Ensure proper backups are taken before making changes to the production database.
  • Document the changes and update any relevant documentation or configuration files.
@chibie chibie added the enhancement New feature or request label Nov 25, 2024
@Supa-mega
Copy link

Can I try solving this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants