Open
Description
The new Sample dApp will be a more developer focussed website, similar to a "getting started" page.
Overall
- Examples should be executable
- Users are able to exit examples
- Each example should contain explanations what is done
- Examples need to be compiled at build time to see breaking changes
Features dApp
We need to explain when people need taquito and when not. And we need to decide how we set up the examples for "with" and "without" taquito.
- 1. How to create a dAppClient (explain automatic connection to Extension + P2P)
- 2. How to read previous state (active accounts)
- 3. How to connect to testnet
- 4. How to enable dark mode
- 5. How to use a custom block explorer
- 6. How to subscribe to events
- 7. How to handle "error" responses from dApp
Advanced
- How to overwrite default UI (but keep pairing screen)
- Explain Acknowledgement behaviour
- Enable Logging
Features Wallet
- How to create a WalletClient
- How to connect to a dApp
- How to listen to messages
- How to respond to a message
- Example: Permission Response
- Example: Operation Response
- Example: Sign Response
- Example: Broadcast Response
- Example: Aborted Error
- Example: Other errors
Testing
In this section, there will be some predefined actions with described expected behaviour. This can be used to test the functionality of beacon across multiple wallets.
- Send permission request (mainnet)
- Send permission request (edonet)
- Send permission request (florencenet)
- Send request and abort => Expect abortion message
- Send operation request (simple spend)
- Send operation request (contract call with params)
- Send operation request (delegation)
- Sign Payload (string = "test")
- Sign Payload (string = "03...")
- Sign Payload (string = "05...")
- Send broadcast request
Metadata
Metadata
Assignees
Labels
No labels
Activity