Custom RPCs #33
Replies: 4 comments 2 replies
-
|
Not an issue, please propose ideas on other channels |
Beta Was this translation helpful? Give feedback.
-
|
@hazae41 Very disappointing. First of all, this is an issue. Your 'privacy' wallet is just a larp unless you allow users to customize RPC. Missing a basic feature for trustless operation = a serious issue. I can see you find this as more of a feature request, in that case a suggest you add flag to label this issue as 'feature request' which is a regular way of tracking requested features in public github repo. In case you are choosing other project management with less transparency, please point me to right channel instead. Your readme doesn't specify any and your comment doesn't recommend any channel either |
Beta Was this translation helpful? Give feedback.
-
|
You can discuss such things on Twitter, Discord, SimpleX All links there |
Beta Was this translation helpful? Give feedback.
-
|
Or better in GitHub Discussion if you want a detailed public feature proposal |
Beta Was this translation helpful? Give feedback.
-
|
It's a discussion now. Any update on this? |
Beta Was this translation helpful? Give feedback.
-
|
If there is no message there is no update |
Beta Was this translation helpful? Give feedback.
-
From what I can tell, the wallet supports only a couple of hardcoded rpc providers and it doesn't allow users to input their own rpc address. This is a crucial feature in privacy wallet. Even if requests are torified, using trusted third party is inferior to your own node. The only current solution is compile it with own address added to the code which is not very practical
Beta Was this translation helpful? Give feedback.
All reactions