Archived Content from Web3Auth Community
This topic was originally posted by zilinissleepin on 8/13/2024.
This content has been migrated from our previous community forum to preserve valuable discussions.
I am an senior web3 engineer in a large web3 company. I have encountered some confusion while researching and getting hands-on experience with your MPC toolkit. I would be extremely grateful if you could assist me.
The Demo Core MPC Web Kit and React Native, and the demo site: mpc-core-kit-react-quick-start.vercel.app
Do these demos actually generates 3 shares locally and one for local device(frontend cache), one for additional storage and one for remote web3auth server? I have tested and found when login the servers are five: h t t ps://node-1.node.web3auth.io/ and so on… Why there are 5 servers? I think only one remote web3auth server is enough. Is something wrong?
In additonally, Do these demos send tx or sign message with multi rounds local and remote signing? I have tested and found when signing the demo site sent many requests to many nodes: such as sending GET “h t t ps://node-4.node.web3auth.io/tss/precompute” and “h t t ps://node-4.node.web3auth.io/tss/sign”. Is there any local signing computation process here in addition to the remote procedure?
Thanks!