Dappy delta network is live
Why is there another network ?
Prior to the release of Dappy browser 0.3.3 there were two Dappy networks deployed, and they were both called betanetwork. One betanetwork was connected to RChain testnet and the other to RChain mainnet. It means that you had to use the same address notation for both : betanetwork/bob for example.
It often caused misunderstanding, we did not know if this application, or this name was to be accessed through the betanetwork testnet or betanetwork mainnet.
Dappy browser 0.3.3 now references two networks. The betanetwork mainnet stays the same, and the betanetwork testnet becomes deltanetwork.
Lots of dapps deployed on the betanetwork (testnet) may break, because they still refer to the betanetwork in the javascript. Dappy pages for example will have to be redeployed.
How to configure Dappy browser ?
If your Dappy browser was connected to the betanetwork (mainnet), you should not have to change anything.
If it was connected to the betanetwork (testnet). Follow the usual protocol for changing the network in Dappy browser : remove network, and then add a network with the nodes of delta network.
Shortcut notation
In order to avoid network modifications breaking dapps in the future, we have added the shortcut notation. In the javascript or HTML, anytime you issue a request or load a resource from the blockchain, you do not have to reference the network anymore, Dappy browser will take care of completing the address with current network.
dappyRChain.fetch(“dappy://deltanetwork/REGISTRY_URI”)
We now advise you to do it this way
dappyRChain.fetch(“dappy://REGISTRY_URI”)
A note on this shortcut notation has been added to the dapp tutorial
