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

Create working testnet environment #122

Open
kallemoen opened this issue Dec 31, 2024 · 4 comments
Open

Create working testnet environment #122

kallemoen opened this issue Dec 31, 2024 · 4 comments
Assignees
Labels
epic Collection of features that solves a specific user problem or business goal

Comments

@kallemoen
Copy link

Aim: Set up a fully functional front-end targetting our testnet environment, such that we can deploy features in our front-end there and test before pushing to production.

@kallemoen kallemoen added stability user experience Improvment in user experience on current features. epic Collection of features that solves a specific user problem or business goal and removed stability user experience Improvment in user experience on current features. labels Dec 31, 2024
@amaljosea
Copy link
Contributor

Currently, the web app only supports mainnet, which makes it impossible to test new features.

So now the new features that involve some transaction in the chain directly go to production.

See a sample comment here #114 (comment). Please see the loom video in that PR. (#114 (comment))

The goal of this issue is to research and document how we can support test net.

@amaljosea
Copy link
Contributor

@amaljosea
Copy link
Contributor

amaljosea commented Jan 6, 2025

Hi @FossilFrank @kallemoen

Please check if I am moving in the right direction.

Questions:

  • Do we have a testnet where all the smart contracts are deployed? Which one?
  • Do you think we need a separate indexer for testnet?

https://www.loom.com/share/6e67f476b4374cb18e8409222b2fa533?from_recorder=1&focus_title=1

@FossilFrank
Copy link
Contributor

Hey @amaljosea, your assessment seems correct. The testnet contract is deployed at 0xd5a716d967a9137222219657d7877bd8c79c64e1edb5de9f2901c98ebe74da80, and yes we'll probably need to make a separate indexer deployment for testnet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Collection of features that solves a specific user problem or business goal
Projects
None yet
Development

No branches or pull requests

4 participants