Skip to content
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.

Internal testnet #126

Closed
mhluongo opened this issue May 16, 2019 · 6 comments
Closed

Internal testnet #126

mhluongo opened this issue May 16, 2019 · 6 comments

Comments

@mhluongo
Copy link
Member

tBTC needs an internal testnet that

  • Always has the latest (or nearly latest) Keep contracts
  • Pulls in any necessary external dependencies (eg Implement on-chain liquidation #105)
  • Can be used for testing by partners who want to integrate

@sthompson22 shit's getting real, prepare yourself

@sthompson22
Copy link
Contributor

keep-dev will already have these things, if we can use the same testnet the beacon runs on.

@sthompson22
Copy link
Contributor

Well let me peep the dependency note. Contracts and external integration are def there.

@mhluongo
Copy link
Member Author

@sthompson22 we sort of have this now, but a separate testnet for partners (or the same one we use for stakers) might make sense- thoughts?

@sthompson22
Copy link
Contributor

we sort of have this now, but a separate testnet for partners (or the same one we use for stakers) might make sense- thoughts?

What we have now is the "internal testnet". When needed I can replicate the deployment to our private testnet where beacon testing with external parties is happening. This runs the most recent blessed state of the beacon and isn't deployed unless we push the button. It should be stable enough for testing with tbtc external parties.

@mhluongo
Copy link
Member Author

@sthompson22 should we close this?

@mhluongo
Copy link
Member Author

We've had this for a while, thanks @sthompson22!

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

No branches or pull requests

2 participants