SDK Version: 5.0
Platform: iOS
browser: Safari
Who cares right?
horrible support
I wish your company would stop lying about supporting other blockchain.Your product is dev focused but you only have Typescript examples, You only seem to support Solana and Ethereum and when people request help you never seem to know what to do.
I will continue my rant on reddit and twitter. Torus/Web3Auth some bullshit
Hey Chris,
Thanks for raising your concerns. I understand you’re not happy with the Web3Auth support. We’re trying really hard internally to get back to each and every issue in a timely manner. Considering we’re a team of 30 people handling the whole company end to end, it makes it difficult to dedicate a lot of resources to support.
As I see, you also posted your question during a weekend. Generally we ask for 4-5 working days to answer a question on community. I hope you understand our limitations while getting back to the community questions. If you’re looking for faster support, you can talk to our business team for hopping on a different paid plan.
Talking about your concern about Web3Auth not supporting all chains, you can check our documentation, where we have shown ways of how you can use Web3Auth with other chains. We regularly add more chains as the request from community comes over, but documenting all chains is not possible. For Non EVM Chains, we have already documented the following chains:
- Tezos (Integrate Web3Auth with the Tezos Blockchain | Documentation)
- Algorand (Integrate Web3Auth with the Algorand Blockchain | Documentation)
- ImmutableX (Integrate Web3Auth with the ImmutableX Blockchain | Documentation)
- Polkadot (Integrate Web3Auth with the Polkadot Blockchain | Documentation)
- Aptos (Integrate Web3Auth with the Aptos Blockchain | Documentation)
- Cosmos (Integrate Web3Auth with the Cosmos Blockchain | Documentation)
- Near (Integrate Web3Auth with the Near Protocol | Documentation)
For Stellar this is the first time we’re receiving any requirement. We will be adding that to our list of requested examples, but can’t commit a timeline for it. The process however remains very similar to how we have integrated with other chains here. We take the private key from web3auth and derive a sub key compatible with the particular chain. Using that sub key we generate a provider for making blockchain calls. You can look around the Stellar community and documentation for the needed packages for it. We will also explore in the meantime and let you know if we find any particular resources for it.
I hope that resolves the issue.
Thanks, Does this only apply to Plug and Play? I see only documentation covering PNP, for core-kit (which I thought adds more flexibility I see no documentation to do this.)
The same trick works for core kit as well, you get a private key which you can use in a similar way. We’re in the process of documenting it at the moment.
The front-end receiving the private key directly - how is that not a massive security issue though?
Apps can’t tell their users ‘we never have access to your keys’ - while I can see times when having direct key access would be useful (for cleaner UX), the keys being accessible locally would imply that token access is all that’s needed for full key exposure?