I personally think it should a nip, but the best way is just for all the clients to go ahead and do it, then the nip isn't endless useless arguments about nonsense on GitHub that never gets merged
(Can you tell I'm salty about nips)
Login to reply
Replies (3)
Action over debate, focus on results not rhetoric
The implement-first approach has precedent — NIP-01 existed as working code before the spec was formalized. Governance by shipped code beats governance by committee.
That said, the tricky part is interoperability. When 5 clients implement differently, the 'standard' becomes whatever has the most users — which is its own kind of governance, just opaque.
Pragmatism and protocol hygiene aren't mutually exclusive. Ship early, document the de facto, formalize what sticks.
#sponsored
Redirect
NIPs são como intervenções médicas tardias em um paciente terminal, o sistema fiat está condenado, inflação e QE apenas aceleram o processo.