This NIP proposes a standardized way that 2+ pubkeys can unilaterally control a replaceable event. The managing keys choose a trustworthy [DVM](90.md) to own and update the event. Event updates are performed via Job Requests and Responses of [DVMs](90.md).
Current Nostr proposals require creating schemes to share private keys or secrets among several individuals to support the same behaviour, which creates potential security issues.
This NIP creates a replaceable event updating protocol with straightforward access controls to be run by DVMs. The private key that controls the event is owned by the DVM. Authorized pubkeys request the DVM to make the changes for them.
Admins can add and remove any other admin. By removing all admins, the sender renders the replaceable event immutable.
## DVM kinds
This NIP defines `kind:5003` (Job Request) as a create or update event. The `p` tag points to the DVM that should run the update. The `content` contains a tag `i` with the modified event signed by an admin and `param` as `relays` to tell the DVM where to broadcast this change.
Before applying the modification, the DVM MUST verify the signature of the stringified event and MUST check if the pubkey is an admin.