Creating account handles using existing WalletConnect session objects, or an alternative #1038
-
In the Reach docs under "using account handles" I've noticed a lack of functionality that is otherwise provided by the conventional WalletConnect object. This includes things like sending generic transactions and disconnecting the wallet. Please refer to the PR by xarmian, which outlines the same: Is there any alternative for this as of now? And the chances of official support? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
PR #765 is about providing a custom WC... that is, it is about the PRODUCTION of an account handle in some sense. You seem to be asking about the USE of an account handle. I think that the answer to your question is that you can use Maybe you can help me understand what you're looking for exactly and we turn those into feature requests? |
Beta Was this translation helpful? Give feedback.
PR #765 is about providing a custom WC... that is, it is about the PRODUCTION of an account handle in some sense.
You seem to be asking about the USE of an account handle. I think that the answer to your question is that you can use
acc.networkAccount
to get the underlying handle --- https://docs.reach.sh/frontend/#js_networkAccount --- and just do stuff that is customized to your network. You can also directly communicate with the provider --- https://docs.reach.sh/frontend/#js_setProvider --- and send arbitrary transactions.Maybe you can help me understand what you're looking for exactly and we turn those into feature requests?