# \[Archive\] Developer Trust and Self-Custodial Wallets | Web3Auth

**URL:** <https://builder.metamask.io/t/archive-developer-trust-and-self-custodial-wallets-web3auth/1423>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [April 12, 2024, 11:15pm UTC](https://builder.metamask.io/t/archive-developer-trust-and-self-custodial-wallets-web3auth/1423 "2024-04-12T23:15:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [April 12, 2024, 11:15pm UTC](https://builder.metamask.io/t/archive-developer-trust-and-self-custodial-wallets-web3auth/1423/1 "2024-04-12T23:15:27Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **shahbaz** on 4/13/2024.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

Few weeks ago, Paris-based wallet maker Ledger faced severe backlash for their ‘Ledger Recover’ feature which exposed a rather unsettling truth — Ledger’s firmware updates could now access user keys stored on its hardware.

* * *
This is a companion discussion topic for the original entry at [https://blog.web3auth.io/what-is-developer-trust-and-how-it-applies-to-self-custody](https://blog.web3auth.io/what-is-developer-trust-and-how-it-applies-to-self-custody)