50 lines
3.2 KiB
Markdown
50 lines
3.2 KiB
Markdown
|
# Submit Vega transaction
|
||
|
|
|
||
|
|
A dapp sends a transaction to a wallet, that wallet then broadcasts the transaction to a network. Therefore the following is broken up into two steps. The transaction could fail at either. Generally: Once the transaction has gone to the network a user can use block explorer to track the transaction, but some tracking in Dapp or wallet will help.
|
||
|
|
|
||
|
|
When submitting a Vega transaction of any kind, I...
|
||
|
|
|
||
|
|
## Track transaction to wallet
|
||
|
|
|
||
|
|
if not connected to a Vega wallet:
|
||
|
|
|
||
|
|
- **must** be told that I am not connected, so can not submit a transaction, and given the [option to connect](0012-WCON-connect_vega_wallet.md). (Note: this may have happened if the wallet has become disconnected without the user knowing) (<a name="0003-WTXN-001" href="#0003-WTXN-001">0003-WTXN-001</a>)
|
||
|
|
|
||
|
|
if transaction not auto approved by wallet:
|
||
|
|
|
||
|
|
- **must** see a prompt to check connected vega wallet to approve transaction (<a name="0003-WTXN-002" href="#0003-WTXN-002">0003-WTXN-002</a>)
|
||
|
|
- **could** see the transaction details that has been passed to the wallet for broadcast
|
||
|
|
|
||
|
|
if transaction is approved by wallet:
|
||
|
|
|
||
|
|
- **must** see A [transaction hash](DATA-data_display.md#transaction-hash) (<a name="0003-WTXN-003" href="#0003-WTXN-003">0003-WTXN-003</a>)
|
||
|
|
- **must** see the public key that this transaction was submitted for (<a name="0003-WTXN-004" href="#0003-WTXN-004">0003-WTXN-004</a>)
|
||
|
|
- **should** see the alias for the key that submitted this transaction
|
||
|
|
- **could** see a prompt to set this app to [auto approve](0001-WALL-wallet.md#approving-transactions) in wallet app
|
||
|
|
|
||
|
|
if transaction is rejected by wallet:
|
||
|
|
|
||
|
|
- **could** see that the order was rejected by the connected wallet (closing the window automatically may be appropriate) (<a name="0003-WTXN-007" href="#0003-WTXN-007">0003-WTXN-007</a>)
|
||
|
|
|
||
|
|
if the wallet does not respond:
|
||
|
|
|
||
|
|
- **must** not be able prevented from using the app, e.g. you can (<a name="0003-WTXN-008" href="#0003-WTXN-008">0003-WTXN-008</a>)
|
||
|
|
- **would** like to be able to cancel the transaction from the dapp so that the wallet is no longer in the state where it is asking user to confirm
|
||
|
|
|
||
|
|
if the wallet highlights an issue with the transaction:
|
||
|
|
|
||
|
|
- **must** show that the transaction was marked as invalid by the wallet and not broadcast (aka an error was returned from Wallet) (<a name="0003-WTXN-009" href="#0003-WTXN-009">0003-WTXN-009</a>)
|
||
|
|
- **should** see the error returned highlighted in context of the form that submitted the transaction in Dapp
|
||
|
|
- **must** show error returned by wallet (<a name="0003-WTXN-011" href="#0003-WTXN-011">0003-WTXN-011</a>)
|
||
|
|
|
||
|
|
## Track transaction on network
|
||
|
|
|
||
|
|
- **must** see a link to that transaction in a block explorer for the appropriate network (<a name="0003-WTXN-012" href="#0003-WTXN-012">0003-WTXN-012</a>)
|
||
|
|
- **should** see an indication transaction status
|
||
|
|
- **should** see the network the transaction was broadcast to
|
||
|
|
- **should** see the block the transaction was processed in
|
||
|
|
- **should** show the node the transaction was broadcast to
|
||
|
|
- **could** see the validator that processed the block the transaction was processed in
|
||
|
|
|
||
|
|
... so I am aware of the transactions status of the transactions my wallet is sending and that are being processed by the network
|