pull down to refresh
0 sats \ 0 replies \ @gzuuus_ OP 10h \ parent \ on: DVMCP Updates, a brief why, what and when nostr
Mmm its different stuff, doesn't work in the same way, also have centralization built in, ofc can be tweaked and just pick the best parts, but they are not the same
Not really, here all the notes would be published with the nsec/npub of the relay, if you generate new keys for every note all of them would be published by different identities. Application cases... I don't really know, may be some interesting use cases, for example you can set the nsec of your main account in the relay and all the notes would be signed with your identity, some kind of remote signer... Other for example may be some merge between nip 29 and lowent.xyz
What if the government only allows you to use BTC that are "compliant", and for them to be that way they have to be at an address with a covenant that limits how you can move your utxo, those limits are not set by you. It's just a possibility... But without a doubt, anything that limits or restricts your ability to move your utxos freely must be considered with great caution. In any case I am not against it, I would simply like to understand all the implications that this would have.
I need to look at the details, but my biggest concern with whatever proposal of covenants is that by setting conditions they can limit or even prevent you from having control over your addresses. Edge cases and "creative" censorship can happen.
There are a prNIP-302 about relay pools, that maybe can fits with what you are thinking about 🤔
https://github.com/nostr-protocol/nips/pull/1035
I had another idea about this topic, using bip32 on nostr. Maybe it can be complemented with nip05... but maybe not necessary. Ill publish the proposal soon TM 🤙