Update README

[lukaw3d]

Cheatsheet "ROFL demo" links to this repo

Devs are trying to follow the README

• oasis rofl build
• oasis rofl build --verify

and then follow "ROFLize your Docker app" cheatsheet:

• oasis rofl update

this fails because they don't have test_a in their wallet. And it isn't a known test private key they can add.
So they add their own private key. But this isn't an admin of rofl1qp55evqls4qg6cjw5fnlv4al9ptc0fsakvxvd9uw

So they:

• delete rofl.yaml
• then follow "ROFLize your Docker app" cheatsheet again
• oasis rofl init
• oasis rofl create
• oasis rofl build
• oasis rofl update
• oasis rofl deploy
• they see "ROFL Market Machine Create" transaction on their account: https://explorer.dev.oasis.io/testnet/sapphire/tx/897634c62f5808bad9fcbd30922e20e1aeed3bf200c8d04395f1e9bbf30a1783
• it contains "app_id": "rofl1qzgqp4tqsd4a5w62d205jws79l5gpfrr7vmr23zx",
• https://explorer.dev.oasis.io/testnet/sapphire/rofl/app/rofl1qzgqp4tqsd4a5w62d205jws79l5gpfrr7vmr23zx doesn't expose anything about what contract it is trying to publish
• https://github.com/oasisprotocol/demo-rofl/blob/main/compose.yaml#L8 says CONTRACT_ADDRESS=1234845aaB7b6CD88c7fAd9E9E1cf07638805b20
• there are no new transactions on this https://explorer.dev.oasis.io/testnet/sapphire/address/0x1234845aaB7b6CD88c7fAd9E9E1cf07638805b20
• contract is not verified and it's source is not in this repo, so they can not deploy their own, nor use abi-playground

[kostko]

Not sure why this is on the cheat sheet, but this is used as part of a specific tutorial:
https://docs.oasis.io/build/rofl/app

The contract in question is this (also linked in the tutorial):
https://github.com/oasisprotocol/oasis-sdk/tree/main/examples/runtime-sdk/rofl-oracle/oracle

Anyone updating the README should take this into account. We could probably just remove (or rename) the deployment from the rofl.yaml file and remove/change the parts from the README.

The configured deployment is actually one of the live deployments that I am using to test various ROFL things. Passing a separate --deployment mydeployment to the various create/build/update/deploy subcommands will do the right thing, no need to delete rofl.yaml to create a new deployment. But probably should be documented in the README.

[kostko]

there are no new transactions on this https://explorer.dev.oasis.io/testnet/sapphire/address/0x1234845aaB7b6CD88c7fAd9E9E1cf07638805b20

The transactions are there as the instances are running on Testnet but the transactions are encrypted so they are not linked with the contract by the explorer.