Looking for a Nostr developer who can help build NIP-05 support for bitcoin.rocks and let anyone register their own @bitcoin.rocks identifier Backend only, I will handle the frontend design This job pays in #bitcoin Please repost to get the word out πŸ€™

Replies (9)

I've built 75% of it in the past but have ended up with database errors ChatGPT couldn't solve πŸ˜‚ As I added complexity (blacklist, check if a name exists before it is added) more things broke I'm really a front end dev so I need help with the database side
This should be really easy to do! But I am very busy with IRL things these days. So, here's some free thoughts: - Flat database (SurrealDB, MongoDB) - endpoints /api/register to finalize a registration prepped in the frontend; perhaps by first proving Bitcoin ownership or something? I dont know how "walled" you want it to be in that regard. - Handle /.well-known/nostr.json?username=$name by just looking it up in the database. - A registered user may interact with /api/update to change relay info. - Authentication can be done using the nostr window object - in fact, this way you can have the user sign something using their nsec and validate against their npub to check authenticity. Good luck!!
↑