We originally designed dash and explorer to support one Spacemesh network at a time. e.g. a testnet. Later we added a drop-down in the dash and explore front-ends to enable user to switch between live networks so we can support more than one network. This solution is unsatisfactory as the urls created for data on different networks are identical to each other and this causes lots of confusion.
What we'd like to do is to properly support multiple networks and have friendly content urls that clearly identify a specific network.
We also want to automatically redirect https://explorer.spacemesh.io and https://dash.spacemesh.ioto one of the live networks specified in the discovery meta-data for quick and easy access to a default network via a super friendly url.
It gives users greater reassurance that they are looking at data of a network they are interested at if that network id is in the url. Etherscan is using a similar pattern.
Having an explorer and dash urls w/o network name is very confusing as these links all become bad once the network is taken down and therefore are no longer valid. So this will greatly assist in user bug reports.
changes
An explorer and dash for a supported spacemesh network should have the network friendly name in the friendly url path. e.g. for devnet210 the base friendly urls should be: https://explorer-devnet210.sapcemesh.io and the dashboard's should be available on https://dash-devnet210.spacemesh.io. This is a consistent naming patterns with what we already do in the discovery service for dash and explore backend apis. For example, the explorer backend api for devnet210 is currently: https://explorer-api-devnet210.spacemesh.io.
All links generated in dash and explorer html should be updated to use this url scheme.
Selecting a network from the drop-down on the top-right side of explorer and dash should navigate to the selected network using the new url scheme.
Smapp should embed dash by using the network-specific url and not by https://dashboard.spacemesh.io - this will ensure that Smapp always displays the correct dash for the current network it is configured to use by the wallet or user settings.
Discovery service should have a notion of a default spacemesh network. This should be used to redirect requested to the canonical urls of explorer and dash to that network. e.g. if user navigates to https://explorer.spacemesh.io and devnet210 is specified in web-services as the default live network then the server should redirect the request to https://explorer-devnet210.spacemesh.io. When mainnet launches, the default networks will be the mainnet networks and the urls for mainnent should be https://explorer-mainnet.spacemesh.io and https://dash-mainnet.spacemesh.io.
Close to 0.3 testnets we will likely have https://dash-testnetx.y.z/spacemesh.io as the default network and potentially additional devnets.
motivation
We originally designed dash and explorer to support one Spacemesh network at a time. e.g. a testnet. Later we added a drop-down in the dash and explore front-ends to enable user to switch between live networks so we can support more than one network. This solution is unsatisfactory as the urls created for data on different networks are identical to each other and this causes lots of confusion.
What we'd like to do is to properly support multiple networks and have friendly content urls that clearly identify a specific network.
We also want to automatically redirect
https://explorer.spacemesh.ioandhttps://dash.spacemesh.ioto one of the live networks specified in the discovery meta-data for quick and easy access to a default network via a super friendly url.It gives users greater reassurance that they are looking at data of a network they are interested at if that network id is in the url. Etherscan is using a similar pattern.
Having an explorer and dash urls w/o network name is very confusing as these links all become bad once the network is taken down and therefore are no longer valid. So this will greatly assist in user bug reports.
changes
An explorer and dash for a supported spacemesh network should have the network friendly name in the friendly url path. e.g. for
devnet210the base friendly urls should be:https://explorer-devnet210.sapcemesh.ioand the dashboard's should be available onhttps://dash-devnet210.spacemesh.io. This is a consistent naming patterns with what we already do in the discovery service for dash and explore backend apis. For example, the explorer backend api for devnet210 is currently:https://explorer-api-devnet210.spacemesh.io.All links generated in dash and explorer html should be updated to use this url scheme.
Selecting a network from the drop-down on the top-right side of explorer and dash should navigate to the selected network using the new url scheme.
Smapp should embed dash by using the network-specific url and not by
https://dashboard.spacemesh.io- this will ensure that Smapp always displays the correct dash for the current network it is configured to use by the wallet or user settings.Discovery service should have a notion of a
default spacemesh network. This should be used to redirect requested to the canonical urls of explorer and dash to that network. e.g. if user navigates tohttps://explorer.spacemesh.ioanddevnet210is specified in web-services as the default live network then the server should redirect the request tohttps://explorer-devnet210.spacemesh.io. When mainnet launches, the default networks will be the mainnet networks and the urls for mainnent should behttps://explorer-mainnet.spacemesh.ioandhttps://dash-mainnet.spacemesh.io.Close to 0.3 testnets we will likely have
https://dash-testnetx.y.z/spacemesh.ioas the default network and potentially additional devnets.