# 0xDeadList: Why we should collect a list of addresses with leaked private keys

**Published by:** [0xDeadList](https://paragraph.com/@0xdeadlist/)
**Published on:** 2022-07-31
**URL:** https://paragraph.com/@0xdeadlist/0xdeadlist-why-we-should-collect-a-list-of-addresses-with-leaked-private-keys

## Content

When we say that an Ethereum account has been lost, it refers to two cases: the owner forgets the private key, or the owner leaks the private key. The latter case is very dangerous as anyone with the private key can act the same as the account owner. The account owner loses the exclusive right to use the account, and the account and its address are not secure anymore. DApps should be aware of leaked or disclosed accounts in a timely manner, and provide protection to the owners of these accounts. For example, web3 mail needs to suspend users' access to these accounts' emails; agreements signed after the private key is leaked will not be regarded as authorized by the real owner of the address. In order to solve the above problems, we propose the 0xDeadList project to maintain a list of addresses whose private keys have been leaked. By rewarding NFTs, 0xDeadList encourages users and hackers to report accounts with lost private keys, and stores the information of these leaked accounts on the chain to facilitate DApps project parties to query these insecure accounts.0xDeadList Project Introduction0xDeadList encourages users to collect addresses that have leaked private keys. Users can directly log in to 0xdeadlist.io to report the leaked account. To prevent front-running attacks and let the owner has some processing time before the private key is fully disclosed, the 0xDeadList contract provides a simple two steps: lock address and bury address. In the first step, the user locks the address to be buried, and the contract records the address of the locker. At this time, the private key of the locked address will not be disclosed. In the second step, the user uploads the private key of the burial address, and the locker address recorded in the contract will receive an NFT reward, indicating that the address is buried, and the buried address will receive an SBT as a tombstone, indicating that the address’s private key has been leaked. In this step, the private key of the buried address will be made public (recorded on-chain).Burier NFTTombstone SBTAt present, the project is supported by MetaMail and EthSign. In the future, we will provide rewards to users who bury private key leaked addresses according to the value of these addresses.How to Bury Address:Log in to 0xdeadlist.io, connect the wallet, and bury the address according to the instructions. After the burial is successful, users can view the rewarded NFT and the SBT of the buried address on OpenSea. Burier NFT: OpenSea. Tombstone SBT: OpenSea.How to get the address list of 0xDeadList:Locked and disclosed addresses can be obtained through on-chain/off-chain APIs. For details, please refer to Github.About us:Website | Twitter | Discord | Github

## Publication Information

- [0xDeadList](https://paragraph.com/@0xdeadlist/): Publication homepage
- [All Posts](https://paragraph.com/@0xdeadlist/): More posts from this publication
- [RSS Feed](https://api.paragraph.com/blogs/rss/@0xdeadlist): Subscribe to updates