# Support Web3 wallets in StarkNet

**URL:** <https://community.starknet.io/t/support-web3-wallets-in-starknet/192>\
**Category:** Starknet Technical Development\
**Tags:** tooling\
**Created:** [December 12, 2021, 10:07am UTC](https://community.starknet.io/t/support-web3-wallets-in-starknet/192 "2021-12-12T10:07:34Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![martriay](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/martriay/32/25_2.png) [@martriay](https://community.starknet.io/u/martriay)\
**Post date:** [December 16, 2021, 5:09am UTC](https://community.starknet.io/t/support-web3-wallets-in-starknet/192/10 "2021-12-16T05:09:32Z")

</div>

Hmm although I don’t think user onboarding should be handled by the RPC, it’s true that someone, whoever is onboarding the user, has the power to influence what account contract will be associated to the user’s keys.

So it makes sense to have an upgradeable proxy associated to a pair of ethereum keys for the reasons stated above, but there’s the problem of some party (e.g. uniswap, coinbase, infura) choosing your account contract for life. I’m buying into forcing that this `CREATE` method instantiates a proxy, to protect users from tying themselves to a given contract unknowingly.

---

_[View the full topic](https://community.starknet.io/t/support-web3-wallets-in-starknet/192)._