โšก ๐ŸงŸโ€โ™‚๏ธ โšก

The Resurrector

Bring your deleted Nostr profile back to life!

Part of Plebs vs. Zombies

๐Ÿ”’

Security Notice

โšก Recommended: Connect with Browser Extension (NIP-07) like Alby or nos2x
๐Ÿ›ก๏ธ Fallback: If you must use an nsec, it never leaves your browser
๐Ÿ” Privacy: All operations happen locally - no data sent to any server
๐Ÿ‘๏ธ Open Source: You can inspect the code below or on GitHub
๐Ÿ’ก

How It Works

Nostr accounts are "deleted" by setting a "deleted": true flag in your profile metadata. The Resurrector:

1 Scans for profile events with the deleted flag
2 Sends a deletion event (kind 5) to remove the deleted profile
3 Publishes a clean version of your profile without the deleted flag

Step 1: Choose Authentication Method

โ„น๏ธ Read-only mode - you can scan but not resurrect without signing

Common relays are pre-filled. You can add or remove as needed.

Step 2: Check Profile Status

โ„น๏ธ Read-Only Mode: You can scan profiles with an npub, but resurrection requires authentication. Choose "Browser Extension" or "Private Key" above to resurrect a profile.

๐Ÿ’ก How it works: Click the button below to scan for deleted profiles across all relays. If found and you're authenticated, it will remove the deleted flag and publish a clean version.

Need Help?

Q: Why would my profile be deleted?
Some Nostr clients allow you to "delete" your account by setting the deleted: true flag in your profile.

Q: Is this safe?
Yes! Your private key never leaves this browser window. All operations happen locally using secure cryptography.

Q: What's "Keep Profile Mode"?
When OFF (recommended), it republishes your profile. When ON, it only removes the deleted events without republishing. Use for more control.

โš ๏ธ

Important: Client Compatibility Disclaimer

The Resurrector is a best effort service. While it works in the majority of cases we've tested, there is no guarantee that all Nostr clients will behave the same way.

Known Client-Specific Issues:

  • Yakihonne: May require clearing the app cache or completely uninstalling and reinstalling the app before it will recognize your nsec as not deleted.
  • Primal: Some users may still experience errors logging in if delete flags are present in remote cache services (a known issue on their end).
  • Other clients: Each client handles profile metadata differently. Some may cache deleted status or have different relay configurations.

What We Offer: We publish the necessary events to clear the deleted flag from your profile across relays. In most cases tested, this successfully restores profile usability.

We provide this service with no assurances that every client will accept your nsec after resurrection. Results may vary depending on the client's implementation and caching behavior.

Made with ๐Ÿง  for the Nostr community

View on GitHub ยท Plebs vs. Zombies