You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 3, 2024. It is now read-only.
Once an user register a chain we should store the network type, such as: Orion, Tessera, ....
Background information
In order to provide a better user experience to our user of the tx-scheduler when they send a private transaction we could infer the private network type instead of forcing users to provide that redundant information.
Steps to resolve
User register a chain with a private network: Orion, Tesssera
Infer network type and store it along with rest network information
Implement an endpoint at chain-registry to expose that information
Additional work
Once the endpoint is ready and information about private network type is exposed we could/should replace the usage of method/network from send private transaction API
Feature
Purpose of the feature
Once an user register a chain we should store the network type, such as: Orion, Tessera, ....
Background information
In order to provide a better user experience to our user of the tx-scheduler when they send a private transaction we could infer the private network type instead of forcing users to provide that redundant information.
Steps to resolve
Additional work
Once the endpoint is ready and information about private network type is exposed we could/should replace the usage of
method/networkfrom send private transaction API