New feature: support WalletConnect #176
Conversation
poor-defined
commented
May 30, 2023
•
poor-defined
commented
- Project Research & Management integrating with WalletConnect to work with dapp #144
- namespaces for WalletConnect #148
- PRD
- UI
- Neuron GUI
- Research for Launching Neuron from DApp #153
- Backend
- Discussion
- Should an account be able to verify ownership through signature, similar to an address? #220
- Address conflict solution #197
- Display the amount difference of an account within wallet-connect #212
- Rename of lockCodeHashes and adjust its params #213
- Should Dapp be able to get address set by set or one by one #215
- A process and a dataflow of how Neuron/JoyID work with this protocol #214
|
@Kirl70 I have updated the Send Tx section of the Axure link, could you pls design it before next monday? |
Design Draft ( 3-1 ~ 3-7 ): |
|
|
||
| - Click the arrow next to the address. The Data and Witness will display(elaborately speaking, these details will move upwards) | ||
|  | ||
| - In the UI demo, click this arrow, users can view all the receiving addresses, then view the data and witness the one you want by click the arrow next to the address on list. |
There was a problem hiding this comment.
The detail should be described by text clearly and abstractly.
click this arrow is concrete, check more addresses is abstract
There was a problem hiding this comment.
How is the abbreviation of address list shown should be described.
In the screenshot, To address: ckt...s49 / ckt...82 / ... is meaning less.
What if show the addresses in various format based on the count:
- only 1 address: display the full address
- more than 1 address: show the count of addresses and check address list in another view.
1. Fee Rate is not intuitive for users, so fee could be displayed along with fee rate 2. Locktime is not obligatory
