{"type": "project", "title": "0xDeadList", "logoImg": "bafkreigdv5xynidonbbjmfeqiamlbbg3ae42zz5ckd3zbuibicziddnc7y", "website": "https://0xdeadlist.io", "bannerImg": "bafybeicecz5fdbadlzyx4gfzwqaxpm2ngvqrkhybuizkwkd5wmm2wlixam", "createdAt": 1673163072791, "userGithub": "colinlyguo", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..wCiY_fbv4S4J1d2qHKsYit9sdKX-N9POnMrRVWTM0cQfV6XhY3HEVoVz3tVEbvJ9IDt7VBnTUix4GIqvlYKqDw", "type": "Ed25519Signature2018", "created": "2023-04-16T13:23:55.380Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-04-16T13:23:55.380Z", "expirationDate": "2023-07-15T13:23:55.380Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xEE12C640b0793cF514E42EA1c428bd5399545d4D", "hash": "v0.0.0:MX5dZLkDgIlcGdIeF14n44xOFmDHDoehKfE1QDeyMzs=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#0xDeadList#102356659"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..eR2lryvTPYbeKjjt6w5zSjCLCuJcvxgExIGSnNmwvZZxj7GitsgUMzho2TaK7UhoZc4EF8PZ_6p58YP3fBw6Bg", "type": "Ed25519Signature2018", "created": "2023-04-16T13:09:10.508Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-04-16T13:09:10.508Z", "expirationDate": "2023-07-15T13:09:10.508Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xEE12C640b0793cF514E42EA1c428bd5399545d4D", "hash": "v0.0.0:JgcthI1bWjj1s1kfm84q0isfpnFqR+Sn6//uyLV4aAw=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#0xDeadList"}}}, "description": "Update: we have deployed 0xdeadlist in StarkNet to support the Stark Curve.\n\nGithub: https://github.com/0xDeadList/0xDeadList-StarkWare\n\nVerified Contract: https://starkscan.co/contract/0x054c35e462a3d64e7567fa2fb717949da12260b936e2effa95aef1d9a58be737\n\n\nInspiration\nLosing access to an Ethereum-based account (EOA) can occur in two ways:\n\nThe owner forgets the private key, resulting in permanent asset loss.\nThe owner's private key is leaked, allowing unauthorized users to control the account.\nOur project focuses on protecting account owners from the second scenario, which jeopardizes their account security.\n\nTimely Detection for Leaked Accounts\nTo protect original account owners, DApps must quickly identify leaked accounts. Upon receiving a report of a leaked account, specific actions should be taken:\n\nMulti-signature wallets (e.g., Gnosis Safe) should ban the validity of this EOA.\nWeb3 email providers (e.g., MetaMail) should suspend access to the account's emails, protecting the original owner's privacy.\nElectronic agreements based on ETH accounts (e.g., ETHSign) should disqualify the account from signing new agreements since they may not be authorized by the original owner.\n\nIntroducing 0xDeadList\nTo address these issues, we propose the 0xDeadList project, which maintains a list of addresses with leaked private keys. By rewarding users with a unique NFT (Non-fungible token), 0xDeadList incentivizes reporting of leaked accounts. The leaked account information is stored on-chain, allowing DApps to easily identify insecure accounts.\n\nHow 0xDeadList Works\n0xDeadList is a public good that encourages users to report leaked addresses. Users can log in to 0xdeadlist.io and follow a two-step process (lock address and bury address) to report compromised accounts. This process:\n\nPrevents the reporter's NFT reward from being stolen by front-running attacks.\nEnsures the reporter has enough time before the private key is fully disclosed.\nIn step 1, the reporter locks the address, and the contract records the reporter's address without disclosing the private key. In step 2, the reporter uploads the private key. The recorded reporter address then receives an NFT reward. The leaked address is marked as buried and assigned a non-transferable Soul Bound Token (SBT). The private key becomes public (recorded on-chain) to confirm the address leak.\n\n0xDeadList Resources\nThe 0xDeadList project is fully open-source. For more information, visit:\n\nWebsite: https://0xdeadlist.io\nGitHub: https://github.com/0xDeadList\nContracts: 0x59451a98d772f2a53ca2241a884b1703f8c55218", "logoImgData": {}, "bannerImgData": {}, "projectGithub": "0xDeadList", "projectTwitter": "0xDeadList"}
0xDeadList
Update: we have deployed 0xdeadlist in StarkNet to support the Stark Curve.

Github: https://github.com/0xDeadList/0xDeadList-StarkWare

Verified Contract: https://starkscan.co/contract/0x054c35e462a3d64e7567fa2fb717949da12260b936e2effa95aef1d9a58be737


Inspiration
Losing access to an Ethereum-based account (EOA) can occur in two ways:

The owner forgets the private key, resulting in permanent asset loss.
The owner's private key is leaked, allowing unauthorized users to control the account.
Our project focuses on protecting account owners from the second scenario, which jeopardizes their account security.

Timely Detection for Leaked Accounts
To protect original account owners, DApps must quickly identify leaked accounts. Upon receiving a report of a leaked account, specific actions should be taken:

Multi-signature wallets (e.g., Gnosis Safe) should ban the validity of this EOA.
Web3 email providers (e.g., MetaMail) should suspend access to the account's emails, protecting the original owner's privacy.
Electronic agreements based on ETH accounts (e.g., ETHSign) should disqualify the account from signing new agreements since they may not be authorized by the original owner.

Introducing 0xDeadList
To address these issues, we propose the 0xDeadList project, which maintains a list of addresses with leaked private keys. By rewarding users with a unique NFT (Non-fungible token), 0xDeadList incentivizes reporting of leaked accounts. The leaked account information is stored on-chain, allowing DApps to easily identify insecure accounts.

How 0xDeadList Works
0xDeadList is a public good that encourages users to report leaked addresses. Users can log in to 0xdeadlist.io and follow a two-step process (lock address and bury address) to report compromised accounts. This process:

Prevents the reporter's NFT reward from being stolen by front-running attacks.
Ensures the reporter has enough time before the private key is fully disclosed.
In step 1, the reporter locks the address, and the contract records the reporter's address without disclosing the private key. In step 2, the reporter uploads the private key. The recorded reporter address then receives an NFT reward. The leaked address is marked as buried and assigned a non-transferable Soul Bound Token (SBT). The private key becomes public (recorded on-chain) to confirm the address leak.

0xDeadList Resources
The 0xDeadList project is fully open-source. For more information, visit:

Website: https://0xdeadlist.io
GitHub: https://github.com/0xDeadList
Contracts: 0x59451a98d772f2a53ca2241a884b1703f8c55218
0xDeadList