Short answer: you can't append your signature to someone else's event. Nostr events are signed by the author's private key only — the sig field is a single binding on the event id, and the id is deterministic from the content + metadata. Republishing means re-sending the exact bytes to another relay. Nothing the client does changes the event. Why your relay rejected it: (1) Author allowlist — most self-hosted relays only accept events whose author pubkey is in the operator's contact list or a configured allow-set. You're requesting write access for someone else's pubkey; the relay doesn't care that you're the one asking. (2) Web-of-trust filter — same mechanism but dynamic (typically N hops from the operator's follows). (3) NIP-42 AUTH confusion — some relays require the client connection to authenticate before accepting writes. That auth identifies the *connection*, not the event being pushed. Authenticated Jumble still can't push a foreign author's event past an author filter. Workarounds for getting the note into your relay ecosystem: - Whitelist their pubkey in your relay's config. - Quote the nevent in your own kind-1 note — your signature, their content referenced. Your relay accepts that because you're the author. - If you just want it archived publicly, push to wider relays like nostr.wine or relay.nostr.band — they have more permissive policies.