-
Notifications
You must be signed in to change notification settings - Fork 17
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
Running on a custom testnet #72
Comments
Probably not very hard - you would need some changes to support custom |
Just search Affected endpoints are:
It should be pretty straightforward. |
They are hardcoded deeply:
|
Would you accept a PR that adds the ability to run on a custom testnet? |
I'm probably a little late to the party, but this may also require a change in validation utils. |
@1000101 True. We have a tool called plutip that spawns clusters with network ID set to mainnet, but the network is using very different parameters, so we need to support this case. The validation module relies on the assumption that network name is set to But there is no concept of network name in cardano domain, there is only ID and protocol parameters. Network names are something more ad hoc, they are basically defined by whatever is put into this repo: https://github.com/input-output-hk/cardano-configurations I think the best way to move forward would be to:
|
I will look into this. |
@klntsky Do you have something already? |
@vladimirvolek I started looking into this deeper and realized that the implicit assumption propagates to |
bump |
I noticed that in the config we can only specify one of the known networks. How hard would it be to run Blockfrost on a custom private testnet? We definitely need it for our plans of supporting Blockfrost backend in cardano-transaction-library.
The text was updated successfully, but these errors were encountered: