Your cat is famous @Jeroen ✅

@♡°˖✧ ˚ claire ˚ ✧˖°♡ , @Morgan Maksoud-Miller really likes your stuff.

I think this is important. Not just because Broodwar is the best game ever in existence ever, but: assuming this will be a ''thing'', it is an incentive to build out tooling. Use of nip29 groups, calendar events, tournament NIP and app etc. etc. Actually dog-fooding the stack, such that it can mature and be used elsewhere effortlessly View quoted note →

Check out Merged Mechs (alpha version). Generate a keypair, be 1 of 4 mechs, merge with other players to become a Battle Mech, fight in battles and upgrade your mech by winning a daily Tournament round. https://cdn.azzamo.media/acdebf3f08eebcec8b2d9e64329a4ab9a352d1c5df39da57f5d28dbe5ed345f8 (also known as my (nested)musig2 OTS back game engine tech demo)

Zapstore

Merged Mechs — Zapstore

Merged Mechs is a trustless mech-battle game with no central server — your Nostr keypair IS your pilot, and your mech

nostr:View article →

For real though, when wallet descriptors via Nostr? View quoted note →

Your npub is not also a bitcoin address... Your bitcoin address is also an npub ;) Money speaks!

One thing i learned when making an app (with a robot). If you think you are almost done....add another week. Almost done though

hahaha what a banger

Claude: This will be a multi-day project Also Claude an hour later: Done, what do you want to do next

To all the devs wondering about Musig2. The issue is not so much the crypto/signing here, that base is covered by libsecp256k1. The issue obviously is the coordination. I (well, the robot), made a general musig2 NIP for the general parts irt Nostr tags, verification and how signing/ceremonies go in general. That nip does NOT specify the specific coordination method, those are separate NIPs. I went the route of building out a reference coordination method using plain Nostr events because its the most straightforward, easy, stable and transparent process. It is not private, so not ideal, but that is a separate concern and has no influence on the integrity of the musig2 ceremony (assuming your client picks its nonces right). To try stuff out I initially asked the robot to implement ceremonies using FIPS and one using Marmot. NIP17, Marmot, NIP29 groups, all are reasonable candidates to do this sort of stuff. Who knows, maybe some 'super' implementation is able to manage all of them at the same time, especially if you do the ceremony via a coordinator. Will publish documentation soon and we can have a chat about this. View quoted note →