Is there a sensible way to link npubs? Either from the client side or publisher side.
My thought is that additionally to owning npubs, you could publish from platforms with their own delegate keys and you could endorse its npub as your own.
So then if someone wanted to follow me and I was publishing through a number of services, then they would see all of my content as if it were from me.
I think this would be super powerful. It diverges from "not your keys", but you can own a master key that only endorses and possibly revokes keys, it could provide a timespan, "this was my key from Jan 2020 till Jan 2026" (and I know timestamps are forgable, but ots could help with that too).
And for the complexity of having a hot key like an nsec bunker, ready to sign on your behalf, that can be replaced with accounts for people who want or need them.
I think we'd need a spec about this and then a common way of presenting this on clients.
This idea came after listening to a podcast with fiatjaf (nprofile…nj27).
Big Barry Bitcoin
npub1pk…tpxa6
2026-10-12 11:30:04 UTC
Author Public Key
npub1pktmatjk0l8vn3jhfuwxaasjd65kn4ye9sce3egup7k993f8fg2q5tpxa6Published at
2026-10-12 11:30:04 UTCEvent JSON
{
"id": "09e4e2e2e72667f696302b765ccbd32946c23fbfee7588a3b2b07e6b65159dc9",
"pubkey": "0d97beae567fcec9c6574f1c6ef6126ea969d4992c3198e51c0fac52c5274a14",
"created_at": 1791804604,
"kind": 1,
"tags": [
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"wss://pyramid.fiatjaf.com/"
],
[
"client",
"Amethyst"
]
],
"content": "Is there a sensible way to link npubs? Either from the client side or publisher side.\n\nMy thought is that additionally to owning npubs, you could publish from platforms with their own delegate keys and you could endorse its npub as your own.\n\nSo then if someone wanted to follow me and I was publishing through a number of services, then they would see all of my content as if it were from me.\n\nI think this would be super powerful. It diverges from \"not your keys\", but you can own a master key that only endorses and possibly revokes keys, it could provide a timespan, \"this was my key from Jan 2020 till Jan 2026\" (and I know timestamps are forgable, but ots could help with that too).\n\nAnd for the complexity of having a hot key like an nsec bunker, ready to sign on your behalf, that can be replaced with accounts for people who want or need them.\n\nI think we'd need a spec about this and then a common way of presenting this on clients.\n\nThis idea came after listening to a podcast with nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9thwden5te0vfshxumsd9ehgmmv9ehhyee0qyv8wumn8ghj7umsv96xjcfdv9exxctwvyhxxmmd9udlnj27.",
"sig": "827fd1208446a3d4b8e255e7bf5e4cd70680d2d26b5b3dfd2f36287ae88a1853d3f591c94584109b95a05b5c6130d87defeb7b9181077f78c2c2e9561ae14764"
}