In open protocols, it's not just that you **can** just do things, you actually **MUST** JUST DO THINGS - or else they don't happen.
NIPs are a good example. Don't write a NIP and wait around to see if anyone likes it or starts to use it//. Build something new and shove it into the world. When it starts to work, _then_ write the NIP to explain to others how to talk to your stuff.
I feel like there's a ton of wisdom surrounding this subject that isn't included, and that I'm not quite synthesizing as thoroughly as would be possible with more time and explanation, and so I will think on it a bit and encourage you to write more about it, if that makes sense for you.
yea cool.
the backstory is basically about https://catallax.network ... I had originally written the NIP before I built anything and realize after the fact that that's exactly backwards. you don't describe an idea and wait for it to be "accepted". It's an open, permissionless protocol: you just do the things you have in mind. they don't happen otherwise.
Thank you, market needs to see it functional in reality for consensus to be possible? Or that there is no benchmark for 'accepted'? Or that an idea of a possibility is not persuasive or compelling enough to encourage collaboration? "Oh, I see, now I'm starting to get it."
