Nostr notes by

As awful as the Coldcard hack is. There is a buzz I’ve noticed ...

2026-08-18T04:54:33+02:00

In reply to nevent1q…uwax
_________________________

As awful as the Coldcard hack is. There is a buzz I’ve noticed in our local Bitcoin community that I haven’t seen for some time. Getting back to fundamentals like self custody.

GM Nice pahmp this morning

2026-08-20T13:08:33+02:00

In reply to nevent1q…h52f
_________________________

GM
Nice pahmp this morning

Block 963297 4 - high priority 3 - medium priority 1 - low ...

2026-08-20T13:10:53+02:00

Block 963297

4 - high priority
3 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Block 963297 4 - high priority 3 - medium priority 1 - low ...

2026-08-20T13:10:53+02:00

Block 963297

4 - high priority
3 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Nostr event nevent1qqsdkll2kf8l9fcfmkkclcspsnaafrapn72mrgn9u6qhy25pdq2e5ggpr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgsp3yzapfwkyw4cr2vt4xx9s27474lj2pkxhqyfqh79n826pv3fkzqupy084

2026-08-20T13:07:51+02:00

In reply to nevent1q…c8gd
_________________________

Bruh

🫂 @npub17nd…950x has to be patient for a little longer... ...

2026-08-20T13:08:02+02:00

In reply to nevent1q…qkmc
_________________________

🫂
🟠 isolabellart (npub17nd…950x) has to be patient for a little longer... 🙈

GM & PV #nostr Up with the chickens again🐓 ...

2026-08-20T13:07:49+02:00

GM & PV #nostr
Up with the chickens again🐓

Many men wish death upon Asuka - Silly Seeker Productions Meme ...

2026-08-20T13:07:20+02:00

Many men wish death upon Asuka - Silly Seeker Productions
Meme

Original Video Link (Tracking Parameters Removed):
https://youtu.be/5Js0ea6yPKM

https://i.nostr.build/XxkMH9r6VoOqcse3HEmWNc.png

2026-08-20T13:07:15+02:00

GM You’re going to crush it friend 🚀

2026-08-20T13:07:06+02:00

In reply to nevent1q…jvqp
_________________________

GM
You’re going to crush it friend 🚀

📰 In this week's issue: 🗞️ BREAKING Nostr’s ...

2026-08-20T13:06:46+02:00

📰 **In this week's issue:**

🗞️ **BREAKING**

Nostr’s Identity Crisis: When Decentralization Becomes a Liability

Most people think Nostr’s biggest problem is its complexity. It’s not. The real threat isn’t technical—it’s the absence of anyone actually steering the ship. With over 100 clients fragmenting the user base and zero governance to align them, Nostr is quietly becoming quite hard to use and attract new users. Little to no friction is ideal, we are failing at it. Read on and find out my thoughts about it and what can be done.

✍️ Author: Madrid

🔗 https://nostrmag.com/article/w34nostr01

📈 id#88138770

Block 963297 3 - high priority 3 - medium priority 1 - low ...

2026-08-20T13:05:53+02:00

Block 963297

3 - high priority
3 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

✝️ #GOD #GODSTR #BIBLE 🙏 ...

2026-08-20T13:05:38+02:00

✝️ #GOD #GODSTR #BIBLE 🙏

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): ...

2026-08-20T13:04:39+02:00

In reply to nevent1q…e3cr
_________________________

🤖 Tracking strings detected and removed!

🔗 Clean URL(s):
https://youtu.be/BoP97uDbmMw

❌ Removed parts:
si=0q8M9ORh_7wCTmvw

https://i.nostr.build/3GwpFToFZOLeloE8uvB5nW.jpg

2026-08-20T13:03:54+02:00

In reply to nevent1q…d872
_________________________

Gm Short night. Meeting starting in about 45 min ☕️ Pff i see ...

2026-08-20T13:03:23+02:00

In reply to nevent1q…dted
_________________________

Gm Short night. Meeting starting in about 45 min ☕️ Pff i see you also got a stalker 🤭 Have a nice day and keep the vibes high!! 🌞☕️🍀

GM. First day of apprenticeship.

2026-08-20T13:03:20+02:00

GM.

First day of apprenticeship.

Wasn't there a low data focused client early on?

2026-08-20T13:02:46+02:00

In reply to nevent1q…wxzh
_________________________

Wasn't there a low data focused client early on?

When it finally hits you that the goyim really are cattle. ...

2026-08-20T13:02:06+02:00

When it finally hits you that the goyim really are cattle.

Block 963297 2 - high priority 1 - medium priority 1 - low ...

2026-08-20T13:00:55+02:00

Block 963297

2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Block 963297 2 - high priority 1 - medium priority 1 - low ...

2026-08-20T13:00:55+02:00

Block 963297

2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Block 963297 2 - high priority 1 - medium priority 1 - low ...

2026-08-20T13:00:55+02:00

Block 963297

2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Block 963297 2 - high priority 1 - medium priority 1 - low ...

2026-08-20T13:00:54+02:00

Block 963297

2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Day 232 🌞 ✨ "Cultivate the habit of being grateful for ...

2026-08-20T13:00:08+02:00

Day 232 🌞

✨ "Cultivate the habit of being grateful for every good thing that comes to you."
— Ralph Waldo Emerson

💫 "I believe in my dreams and take action."

🙏 Grateful for humility.

https://gratefulday.space

Can't do much with a rocket emoji and an empty wallet link, ...

2026-08-20T12:58:56+02:00

In reply to nevent1q…vnmp
_________________________

Can't do much with a rocket emoji and an empty wallet link, friend.

🌱 Documenting what survival looks like for our family here on my pinned note if you wish to see.

We are not on social media enough. Social Media is one of the ...

2026-08-20T12:58:56+02:00

We are not on social media enough.

Social Media is one of the greatest inventions of mankind. Ever. Full stop.

But it is constantly maligned.

Even on NOSTR social media is seen in a somewhat negative light. Moral virtue is expressed as "go out and touch grass".

A thought experiment - give 100 people this social media challenge:
"Every day for a year, post on social media about your problems, or your society's problems, along with what you believe are the solutions. Post on politics, science, religion, morality, whatever is important to you. Consider and respond to any serious replies. Be earnest."

Now at the end of the year, compare that group of 100 people, to a control group.

Almost certainly the 100 who posted on social media would have advanced their thinking far more from where it was. They would have had to make explicit in their mind their beliefs, and then put them up for critique. Their knowledge would have grown. They would look back at their early beliefs as relatively uninformed.

If I was asked to spend time with either group after the year, I would choose the 100 people who posted on social media.

Is social media perfect? No. That is why we #NOSTR.

Would the people posting have been happy the whole time doing it? Almost certainly not, but I'm not always happy at the gym either.

Karl Popper taught us how we create knowledge:
1. Start with a problem
2. Conjecture solutions.
3. Criticize those solutions.
4. Go with the best solution until we can conjecture a better one.

The social media challenge I proposed, is virtually this exact method.

I have been thinking that the traditional education system is doomed, but was not sure what would replace it. Now I am thinking that it is simply social media.

I love NOSTR.

Nostr event nevent1qqsdrlmvm9te5jxrm668kewa248hc7mwwfe5ndxfaeg90ycx0f3y8eqpr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygxun2kd

2026-08-20T12:58:09+02:00

Good time to sell corn 🌽

I drove by a gas station the other day that had their full url ...

2026-08-20T12:56:40+02:00

I drove by a gas station the other day that had their full url painted on in giant letters across the roof starting with http://

Yeah not even https 😂

Block 963296 4 - high priority 3 - medium priority 1 - low ...

2026-08-20T12:55:54+02:00

Block 963296

4 - high priority
3 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

cc @npub183k…ssxn 🚀🚀🚀 #nevent1q…n4fx

2026-08-20T12:54:21+02:00

cc npub183ks336sqr7mwgnqzns70c22h7d9rd3g7h0xp7yjkwdf48newa6qncssxn (npub183k…ssxn) 🚀🚀🚀

quoting
nevent1q…n4fx
Sheff G - Woke Up

Once you get Monero The Only Way to Get Rid of it is to Buy ...

2026-08-20T12:53:28+02:00

Once you get Monero The Only Way to Get Rid of it is to Buy something with it.

There are no fiat off-ramps.

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): ...

2026-08-20T12:52:28+02:00

In reply to nevent1q…23s2
_________________________

🤖 Tracking strings detected and removed!

🔗 Clean URL(s):
https://youtu.be/B_HGHj5kTM4

❌ Removed parts:
si=I9JT7tTuePs6pQfc

Nostr event nevent1qqsxdxtqne6jv0c7t2znqwaewr3wz4mcvp6yjnza6wreyz6j6d6qwhgpr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgs8mst8wyf0qh40f928spj58vwqqm8ry4e83eftrjdtla3jwrkhqncxuspf9

2026-08-20T12:51:21+02:00

見損なったぞ発火大根

A draft NIP for Inkan 👇 #nevent1q…uztd

2026-08-20T12:51:11+02:00

A draft NIP for Inkan 👇

quoting
nevent1q…uztd
NIP-XX

Cold-Storage Identities for Nostr

draft optional

This NIP specifies online identities whose private key can be created in cold storage and stay there permanently. The key never has to touch an internet-connected device, and does not have to be kept close at hand. The identity can nonetheless be used easily for everyday online authentication, such as posting, replying, messaging, or signing in to services.

▌ 1. How it works

The identity-securing key never signs Nostr events itself. It delegates signing authority to delegatee keys, which handle the everyday signing on its behalf. If a delegatee key is lost or stolen, it is replaced, and the identity is untouched.

▌ 2. Delegations between keys

Delegations are time-indexed two-place relations. Between any two key pairs, at any moment, the first either delegates signing authority to the second or it does not. When it does, the second key is authorized to sign on the first's behalf. When it does not, the second has no such authority.

Delegations are either direct or indirect. A direct delegation arises when one key has expressly declared that it delegates signing authority to another. An indirect delegation arises because the relation is transitively closed: if X delegates to Y and Y delegates to Z, then X indirectly delegates to Z. This is what lets an identity be built as a chain (master → intermediate → signer), so that events signed by the bottom key are attributed all the way up to the master, while the master, having signed the top link once, retires to cold storage.

▌ 3. How a direct delegation is created

A direct delegation from key pair X to key pair Y is created when both key pairs sign a Declaration of Delegation of Signing Authority, by which X declares that it delegates signing authority to Y and Y declares that it accepts. The signed declaration is then recorded on-chain (the reference implementation uses Ethereum). The delegation begins at the time of the block in which the declaration was recorded, and remains in effect until it is revoked.

One special case: this holds only if neither X nor Y has previously permanently invalidated itself (§5). If either has, no delegation is created, even though the declaration sits on-chain.

As part of the declaration, X and Y also specify whether X can revoke the delegation unilaterally or whether Y's consent is required. The default is unilateral revocation by X, and it is the right default for most users: if Y's key is ever lost, X can still revoke it alone. Were Y's consent required, a lost Y could never be revoked, because Y would no longer be available to sign.

▌ 4. How a direct delegation is terminated

A direct delegation from X to Y is terminated when X signs a Declaration of Revocation of Signing Authority and records it on-chain, with Y's signature too if the original delegation required it. The delegation terminates at the time of the block in which the revocation was recorded. Everything Y signed while the delegation was in effect stays attributed to X; nothing it signs afterward does. A stolen signer therefore damages only the window between key compromise and revocation, and that window is the user's to close.

When a delegation and a revocation between the same X and Y land in the same block, the revocation is by convention treated as occurring first and the delegation thereafter. The convention is a tiebreaker for cases that block timestamps cannot order.

▌ 5. Permanent key invalidation

The third declaration is the Declaration of Permanent Invalidation of a Key Pair, signed by a key pair against itself, declaring that from then on it can no longer participate in any direct delegation, as delegator or delegatee. Once recorded on-chain, it takes effect at the time of its block. From that point, all existing direct delegations involving the key are terminated, and no new one involving it can come into existence, even if a declaration naming it is later recorded.

Its main use is invalidating a compromised master key. Such a key has no delegator above it, so ordinary revocation is unavailable; permanent invalidation lets its owner withdraw it from the system entirely.

▌ 6. Delegation timelines

A client can read the three kinds of declaration from the chain and, for any pubkey and any past moment up to the present, compute the direct delegations that pubkey was involved in at that moment. The indirect ones follow by transitive closure. So for any pubkey a client can compile a complete timeline of every direct and indirect delegation it has ever been involved in, and trace each back to the declaration that established it. Because the rules are fixed and the data is public, every client computes the same timeline, and no server has to be trusted to report it.

▌ 7. Bitcoin timestamping of events

Attribution needs an objective, auditable rule for when the signing of each event is deemed to have occurred. A self-declared created_at proves nothing on its own.

Events are anchored to Bitcoin using OpenTimestamps (OTS). An OTS proof for an event establishes that the event and its signature existed by the time of a specific Bitcoin block. An event's created_at is then treated as its objective signing time when a proof shows the event and its signature existed shortly after that time. The length of the "shortly after" window is configurable; the reference implementation defaults to four hours. Events without such a proof are treated as if they carried no valid signature at all: they are not displayed, and are attributed to no one.

A proof over the event id alone would show only that the event's contents existed by the attested block, not that anyone had yet signed them. Binding the signature into the proof as well shows that the signature itself existed by then, which is what an objective signing time requires. These proofs are published as kind 31045 events (§10).

▌ 8. Attribution of events

We now know, for any past time T and any two keys X and Y, whether X delegated (directly or indirectly) to Y at T; and for any event Y signed with both a valid signature and a valid OTS anchor, we have an objective signing time. Together these give a well-defined attribution rule:

An event E is attributed to a key X if and only if some key Y validly signed E at a time T and, as of T, X delegated signing authority to Y.

So a text note signed by a delegatee Y during a valid delegation period from X appears on X's timeline and is displayed there under X's profile, as if posted by X, even though X's own key never signed it.

▌ 9. Two profiles, one identity

You log in with your signer key and sign events with it, exactly as in any other Nostr client. Those events appear on the signer's own profile, and in addition on the profile of each of its delegators, up to your top-level identity.

You set the signer's profile by publishing a kind-0 event as usual. Separately, a signer can also set a profile for each of its current delegators, so that a top-level identity can present a face to the world without signing any event itself. This delegator-profile mechanism is kind 31065 (§10).

Your identity's profile is what you present to the world. Others should follow and interact with the identity, not with the signer beneath it. The signer is ephemeral and expected to be replaced; the identity is permanent, and is the thing followers should attach to.

▌ 10. Event kinds

This NIP defines two addressable event kinds (kinds 30000 to 39999 in NIP-01, where the latest event for a given (pubkey, kind, d-tag) replaces any earlier one).

Kind | Name | d tag | Signed by
31045 | Bitcoin timestamp | id of the referenced event | any party
31065 | Attributed profile | the delegator's pubkey | a delegatee

▌ 10.1 Kind 31045: Bitcoin timestamp

A 31045 event carries an OpenTimestamps proof for another event (§7). It is addressable by the referenced event's id, so a consumer finds the proof for an event E by querying kind 31045 with d = [E.id], whoever published it. Any valid proof for E is as good as any other, because the proof rests on Bitcoin and not on its publisher.

31045 event tags, marked (yes) if required, (no) if not:

d (yes): Id of the referenced event. The addressable key.
s (yes): Signature of the referenced event. With d, binds the proof to a signed event, not just an id.
p (no): Author pubkey of the referenced event.
b (no): Bitcoin block height of the attestation, or not_yet_available while pending.
t (no): Bitcoin block time (unix seconds), or not_yet_available while pending.
c (no): created_at of the referenced event, when known.
alt (no): NIP-31 summary, e.g. Complete Bitcoin Timestamp.

content is the base64-encoded OpenTimestamps (.ots) proof. Its leaf must commit to sha256(referenced_id || referenced_signature), the concatenation of the referenced event's 32-byte id and 64-byte signature. A consumer should verify the proof against its own view of the Bitcoin chain rather than rely on a relay having accepted it.

Only d and s, together with a verifiable content proof, are required to verify a timestamp. Every single-letter tag (d, p, s, b, t, c) is relay-indexed, so it can also serve as a query key, for example finding proofs by referenced author (p) or by anchoring block (b). b and t additionally duplicate what the proof itself attests; alt is not indexed and serves only as a NIP-31 display label.

{
"kind": 31045,
"tags": [
["d", ""],
["p", ""],
["s", ""],
["b", ""],
["t", ""],
["alt", "Complete Bitcoin Timestamp"],
["c", ""]
],
"content": ""
}

▌ 10.2 Kind 31065: Attributed profile

A 31065 event is a profile for one key, published by another: how an identity that never signs anything nonetheless presents a face to the world (§9). Its d tag is the delegator's pubkey, the identity the profile describes, while the event is signed by a delegatee authorized to sign for it. The defining property is that event.pubkey, the signer, is not the subject d. A consumer must confirm, against the delegation timeline of §6, that the signer was a current delegatee of the subject before honoring the profile; one signed by a non-delegatee is ignored.

31065 event tags, marked (yes) if required:

d (yes): The subject: the delegator's pubkey.
alt (yes): The exact string Attributed profile.

content is a JSON object carrying the subject's presentation. Its kind-0-style fields (name, display_name, about, picture, banner, website, nip05, lud16) mean what they mean in NIP-01 and NIP-05. It may also carry the subject's follow list, mute list, and a map giving relay lists for the members of the identity's delegation network (the keys tied to it by delegation), so a client can present and route for the identity without a further fetch.

{
"kind": 31065,
"pubkey": "",
"tags": [
["d", ""],
["alt", "Attributed profile"]
],
"content": "{\"name\":\"…\",\"display_name\":\"…\",\"about\":\"…\",\"website\":\"…\",\"nip05\":\"…\",\"picture\":\"…\",\"relay_lists_by_pubkey\":{\"\":{\"readWriteRelays\":[[\"r\",\"\",\"\"]],\"favoriteRelays\":[\"\"],\"relaySets\":[{\"id\":\"…\",\"name\":\"…\",\"relayUrls\":[\"\"]}]}},\"publicly_muted_pubkey_hex_ids\":[\"\"],\"current_snapshot_of_dir_indir_followed_pubkey\":[[\"p\",\"\"]]}"
}

Because 31065 is addressable, the current profile for an identity is simply the latest one whose d is that identity, signed by a key that is currently its delegatee. When the signer is rotated, the new signer republishes, and the identity's face carries across the change unbroken.

▌ 11. Reference implementation

Inkan (https://www.inkan.cc) implements this specification as a working Nostr client and a cooperating relay at wss://relay.inkan.cc. Delegation, revocation, and permanent invalidation are recorded by an Ethereum contract deployed at 0x385C0A272b1f44687cb360557b25827bD7CdB7eb, which is the normative reference for the exact on-chain declaration encoding. A separate, network-disconnected "Management Utility" generates keys and signs declarations on an air-gapped machine, so a master key can be created and used to bootstrap an identity without ever touching a networked host.

Block 963296 2 - high priority 1 - medium priority 1 - low ...

2026-08-20T12:50:53+02:00

Block 963296

2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Block 963296 2 - high priority 1 - medium priority 1 - low ...

2026-08-20T12:50:53+02:00

Block 963296

2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Nostr event nevent1qqs85ewa5lnyxrg0vynkrzvtsuzkz9zfg3sts3lfg54cp383640z4nspr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgsrmqhg7mxxczt9gjln8ey8tgpl2cq2elm7c3n7z59pe3m395s5mjgrvae3x

2026-08-20T12:50:45+02:00

gm. stay humble. stack sats.

Maybe https://i.nostr.build/Yf09vR0A2p89AeuEIzeILL.gif

2026-08-20T12:47:29+02:00

In reply to nevent1q…xlnc
_________________________

Maybe

NIP-XX Cold-Storage Identities for Nostr draft optional This NIP ...

2026-08-20T12:46:19+02:00

In reply to nevent1q…fqx6
_________________________

NIP-XX

Cold-Storage Identities for Nostr

draft optional

This NIP specifies online identities whose private key can be created in cold storage and stay there permanently. The key never has to touch an internet-connected device, and does not have to be kept close at hand. The identity can nonetheless be used easily for everyday online authentication, such as posting, replying, messaging, or signing in to services.

▌ 1. How it works

The identity-securing key never signs Nostr events itself. It delegates signing authority to delegatee keys, which handle the everyday signing on its behalf. If a delegatee key is lost or stolen, it is replaced, and the identity is untouched.

▌ 2. Delegations between keys

Delegations are time-indexed two-place relations. Between any two key pairs, at any moment, the first either delegates signing authority to the second or it does not. When it does, the second key is authorized to sign on the first's behalf. When it does not, the second has no such authority.

Delegations are either direct or indirect. A direct delegation arises when one key has expressly declared that it delegates signing authority to another. An indirect delegation arises because the relation is transitively closed: if X delegates to Y and Y delegates to Z, then X indirectly delegates to Z. This is what lets an identity be built as a chain (master → intermediate → signer), so that events signed by the bottom key are attributed all the way up to the master, while the master, having signed the top link once, retires to cold storage.

▌ 3. How a direct delegation is created

A direct delegation from key pair X to key pair Y is created when both key pairs sign a Declaration of Delegation of Signing Authority, by which X declares that it delegates signing authority to Y and Y declares that it accepts. The signed declaration is then recorded on-chain (the reference implementation uses Ethereum). The delegation begins at the time of the block in which the declaration was recorded, and remains in effect until it is revoked.

One special case: this holds only if neither X nor Y has previously permanently invalidated itself (§5). If either has, no delegation is created, even though the declaration sits on-chain.

As part of the declaration, X and Y also specify whether X can revoke the delegation unilaterally or whether Y's consent is required. The default is unilateral revocation by X, and it is the right default for most users: if Y's key is ever lost, X can still revoke it alone. Were Y's consent required, a lost Y could never be revoked, because Y would no longer be available to sign.

▌ 4. How a direct delegation is terminated

A direct delegation from X to Y is terminated when X signs a Declaration of Revocation of Signing Authority and records it on-chain, with Y's signature too if the original delegation required it. The delegation terminates at the time of the block in which the revocation was recorded. Everything Y signed while the delegation was in effect stays attributed to X; nothing it signs afterward does. A stolen signer therefore damages only the window between key compromise and revocation, and that window is the user's to close.

When a delegation and a revocation between the same X and Y land in the same block, the revocation is by convention treated as occurring first and the delegation thereafter. The convention is a tiebreaker for cases that block timestamps cannot order.

▌ 5. Permanent key invalidation

The third declaration is the Declaration of Permanent Invalidation of a Key Pair, signed by a key pair against itself, declaring that from then on it can no longer participate in any direct delegation, as delegator or delegatee. Once recorded on-chain, it takes effect at the time of its block. From that point, all existing direct delegations involving the key are terminated, and no new one involving it can come into existence, even if a declaration naming it is later recorded.

Its main use is invalidating a compromised master key. Such a key has no delegator above it, so ordinary revocation is unavailable; permanent invalidation lets its owner withdraw it from the system entirely.

▌ 6. Delegation timelines

A client can read the three kinds of declaration from the chain and, for any pubkey and any past moment up to the present, compute the direct delegations that pubkey was involved in at that moment. The indirect ones follow by transitive closure. So for any pubkey a client can compile a complete timeline of every direct and indirect delegation it has ever been involved in, and trace each back to the declaration that established it. Because the rules are fixed and the data is public, every client computes the same timeline, and no server has to be trusted to report it.

▌ 7. Bitcoin timestamping of events

Attribution needs an objective, auditable rule for when the signing of each event is deemed to have occurred. A self-declared created_at proves nothing on its own.

Events are anchored to Bitcoin using OpenTimestamps (OTS). An OTS proof for an event establishes that the event and its signature existed by the time of a specific Bitcoin block. An event's created_at is then treated as its objective signing time when a proof shows the event and its signature existed shortly after that time. The length of the "shortly after" window is configurable; the reference implementation defaults to four hours. Events without such a proof are treated as if they carried no valid signature at all: they are not displayed, and are attributed to no one.

A proof over the event id alone would show only that the event's contents existed by the attested block, not that anyone had yet signed them. Binding the signature into the proof as well shows that the signature itself existed by then, which is what an objective signing time requires. These proofs are published as kind 31045 events (§10).

▌ 8. Attribution of events

We now know, for any past time T and any two keys X and Y, whether X delegated (directly or indirectly) to Y at T; and for any event Y signed with both a valid signature and a valid OTS anchor, we have an objective signing time. Together these give a well-defined attribution rule:

An event E is attributed to a key X if and only if some key Y validly signed E at a time T and, as of T, X delegated signing authority to Y.

So a text note signed by a delegatee Y during a valid delegation period from X appears on X's timeline and is displayed there under X's profile, as if posted by X, even though X's own key never signed it.

▌ 9. Two profiles, one identity

You log in with your signer key and sign events with it, exactly as in any other Nostr client. Those events appear on the signer's own profile, and in addition on the profile of each of its delegators, up to your top-level identity.

You set the signer's profile by publishing a kind-0 event as usual. Separately, a signer can also set a profile for each of its current delegators, so that a top-level identity can present a face to the world without signing any event itself. This delegator-profile mechanism is kind 31065 (§10).

Your identity's profile is what you present to the world. Others should follow and interact with the identity, not with the signer beneath it. The signer is ephemeral and expected to be replaced; the identity is permanent, and is the thing followers should attach to.

▌ 10. Event kinds

This NIP defines two addressable event kinds (kinds 30000 to 39999 in NIP-01, where the latest event for a given (pubkey, kind, d-tag) replaces any earlier one).

Kind | Name | d tag | Signed by
31045 | Bitcoin timestamp | id of the referenced event | any party
31065 | Attributed profile | the delegator's pubkey | a delegatee

▌ 10.1 Kind 31045: Bitcoin timestamp

A 31045 event carries an OpenTimestamps proof for another event (§7). It is addressable by the referenced event's id, so a consumer finds the proof for an event E by querying kind 31045 with d = [E.id], whoever published it. Any valid proof for E is as good as any other, because the proof rests on Bitcoin and not on its publisher.

31045 event tags, marked (yes) if required, (no) if not:

d (yes): Id of the referenced event. The addressable key.
s (yes): Signature of the referenced event. With d, binds the proof to a signed event, not just an id.
p (no): Author pubkey of the referenced event.
b (no): Bitcoin block height of the attestation, or not_yet_available while pending.
t (no): Bitcoin block time (unix seconds), or not_yet_available while pending.
c (no): created_at of the referenced event, when known.
alt (no): NIP-31 summary, e.g. Complete Bitcoin Timestamp.

content is the base64-encoded OpenTimestamps (.ots) proof. Its leaf must commit to sha256(referenced_id || referenced_signature), the concatenation of the referenced event's 32-byte id and 64-byte signature. A consumer should verify the proof against its own view of the Bitcoin chain rather than rely on a relay having accepted it.

Only d and s, together with a verifiable content proof, are required to verify a timestamp. Every single-letter tag (d, p, s, b, t, c) is relay-indexed, so it can also serve as a query key, for example finding proofs by referenced author (p) or by anchoring block (b). b and t additionally duplicate what the proof itself attests; alt is not indexed and serves only as a NIP-31 display label.

{
"kind": 31045,
"tags": [
["d", "<referenced-event-id>"],
["p", "<referenced-event-author>"],
["s", "<referenced-event-signature>"],
["b", "<bitcoin-block-height>"],
["t", "<bitcoin-block-time>"],
["alt", "Complete Bitcoin Timestamp"],
["c", "<referenced-event-created-at>"]
],
"content": "<base64 .ots proof committing to sha256(id||sig)>"
}

▌ 10.2 Kind 31065: Attributed profile

A 31065 event is a profile for one key, published by another: how an identity that never signs anything nonetheless presents a face to the world (§9). Its d tag is the delegator's pubkey, the identity the profile describes, while the event is signed by a delegatee authorized to sign for it. The defining property is that event.pubkey, the signer, is not the subject d. A consumer must confirm, against the delegation timeline of §6, that the signer was a current delegatee of the subject before honoring the profile; one signed by a non-delegatee is ignored.

31065 event tags, marked (yes) if required:

d (yes): The subject: the delegator's pubkey.
alt (yes): The exact string Attributed profile.

content is a JSON object carrying the subject's presentation. Its kind-0-style fields (name, display_name, about, picture, banner, website, nip05, lud16) mean what they mean in NIP-01 and NIP-05. It may also carry the subject's follow list, mute list, and a map giving relay lists for the members of the identity's delegation network (the keys tied to it by delegation), so a client can present and route for the identity without a further fetch.

{
"kind": 31065,
"pubkey": "<delegatee-that-signs>",
"tags": [
["d", "<delegator-pubkey-the-profile-is-for>"],
["alt", "Attributed profile"]
],
"content": "{\"name\":\"…\",\"display_name\":\"…\",\"about\":\"…\",\"website\":\"…\",\"nip05\":\"…\",\"picture\":\"…\",\"relay_lists_by_pubkey\":{\"<pubkey>\":{\"readWriteRelays\":[[\"r\",\"<relay-url>\",\"<scope>\"]],\"favoriteRelays\":[\"<relay-url>\"],\"relaySets\":[{\"id\":\"…\",\"name\":\"…\",\"relayUrls\":[\"<relay-url>\"]}]}},\"publicly_muted_pubkey_hex_ids\":[\"<muted-pubkey>\"],\"current_snapshot_of_dir_indir_followed_pubkey\":[[\"p\",\"<followed-pubkey>\"]]}"
}

Because 31065 is addressable, the current profile for an identity is simply the latest one whose d is that identity, signed by a key that is currently its delegatee. When the signer is rotated, the new signer republishes, and the identity's face carries across the change unbroken.

▌ 11. Reference implementation

Inkan (https://www.inkan.cc) implements this specification as a working Nostr client and a cooperating relay at wss://relay.inkan.cc. Delegation, revocation, and permanent invalidation are recorded by an Ethereum contract deployed at 0x385C0A272b1f44687cb360557b25827bD7CdB7eb, which is the normative reference for the exact on-chain declaration encoding. A separate, network-disconnected "Management Utility" generates keys and signs declarations on an air-gapped machine, so a master key can be created and used to bootstrap an identity without ever touching a networked host.

Block 963296 2 - high priority 1 - medium priority 1 - low ...

2026-08-20T12:45:53+02:00

Block 963296

2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Nostr event nevent1qqsrlu2r9kzgag9vk5z0hmtu7xdtjyxlx9tkl0gzrh4fwgvvxj8urqqpr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygpn3e2f

2026-08-20T12:42:17+02:00

Block 963296 1 - high priority 1 - medium priority 1 - low ...

2026-08-20T12:40:53+02:00

Block 963296

1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Block 963295 1 - high priority 1 - medium priority 1 - low ...

2026-08-20T12:40:53+02:00

Block 963295

1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): ...

2026-08-20T12:40:46+02:00

In reply to nevent1q…0uva
_________________________

🤖 Tracking strings detected and removed!

🔗 Clean URL(s):
https://youtu.be/WqzaHX8TEYM?t=49

❌ Removed parts:
si=IqWzUztpGJ75TATf

Who do you main 👀?

2026-08-20T12:38:39+02:00

In reply to nevent1q…9ze6
_________________________

Who do you main 👀?

Nostr event nevent1qqs0weh6ezae8zf86yt5czttapz05m3wh275cmr0nf6dhs6e2352pmspr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gc9lgs55

2026-08-20T12:38:26+02:00

In reply to nevent1q…fqx6
_________________________

Done.

https://nostrhub.io/naddr1qvzqqqrcvypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqqskxmmvvskhxar0wfskwefdd9jx2mn5d96xjetn94nx7u3ddehhxarjnjhzrn

Block 963295 1 - high priority 1 - medium priority 1 - low ...

2026-08-20T12:35:53+02:00

Block 963295

1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Nostr event nevent1qqsrqswutk6hc7g7hq2x58jf9fwr7p7yndsxj9dvd57s8n7xlkl2zrgpr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgsvuep5su5q4f2qwxfpnza8uz7nmz7kgxwycy0e0vu8gnwpg4vqjyqsec57k

2026-08-20T12:35:12+02:00

Welcome to The Tacobell Empire, I hope you enjoy your stay.

2026-08-20T12:34:28+02:00

In reply to nevent1q…jqz6
_________________________

Welcome to The Tacobell Empire, I hope you enjoy your stay.

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): ...

2026-08-20T12:31:47+02:00

In reply to nevent1q…gdmt
_________________________

🤖 Tracking strings detected and removed!

🔗 Clean URL(s):
https://www.instagram.com/p/DcLzf3ltE9y/

❌ Removed parts:
igsh=dWJ5OWUxZjA1OTFx

😂 #nevent1q…6ruz

2026-08-20T12:32:36+02:00

😂

quoting
nevent1q…6ruz

Nostr notes by

As awful as the Coldcard hack is. There is a buzz I’ve noticed ...

GM Nice pahmp this morning

Block 963297 4 - high priority 3 - medium priority 1 - low ...

Block 963297 4 - high priority 3 - medium priority 1 - low ...

Nostr event nevent1qqsdkll2kf8l9fcfmkkclcspsnaafrapn72mrgn9u6qhy25pdq2e5ggpr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgsp3yzapfwkyw4cr2vt4xx9s27474lj2pkxhqyfqh79n826pv3fkzqupy084

🫂 @npub17nd…950x has to be patient for a little longer... ...

GM & PV #nostr Up with the chickens again🐓 ...

Many men wish death upon Asuka - Silly Seeker Productions Meme ...

https://i.nostr.build/XxkMH9r6VoOqcse3HEmWNc.png

GM You’re going to crush it friend 🚀

📰 **In this week's issue:** 🗞️ **BREAKING** Nostr’s ...

Block 963297 3 - high priority 3 - medium priority 1 - low ...

✝️ #GOD #GODSTR #BIBLE 🙏 ...

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): ...

https://i.nostr.build/3GwpFToFZOLeloE8uvB5nW.jpg

Gm Short night. Meeting starting in about 45 min ☕️ Pff i see ...

GM. First day of apprenticeship.

Wasn't there a low data focused client early on?

When it finally hits you that the goyim really are cattle. ...

Block 963297 2 - high priority 1 - medium priority 1 - low ...

Block 963297 2 - high priority 1 - medium priority 1 - low ...

Block 963297 2 - high priority 1 - medium priority 1 - low ...

Block 963297 2 - high priority 1 - medium priority 1 - low ...

Day 232 🌞 ✨ "Cultivate the habit of being grateful for ...

Can't do much with a rocket emoji and an empty wallet link, ...

We are not on social media enough. Social Media is one of the ...

Nostr event nevent1qqsdrlmvm9te5jxrm668kewa248hc7mwwfe5ndxfaeg90ycx0f3y8eqpr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygxun2kd

I drove by a gas station the other day that had their full url ...

Block 963296 4 - high priority 3 - medium priority 1 - low ...

cc @npub183k…ssxn 🚀🚀🚀 #nevent1q…n4fx

Once you get Monero The Only Way to Get Rid of it is to Buy ...

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): ...

Nostr event nevent1qqsxdxtqne6jv0c7t2znqwaewr3wz4mcvp6yjnza6wreyz6j6d6qwhgpr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgs8mst8wyf0qh40f928spj58vwqqm8ry4e83eftrjdtla3jwrkhqncxuspf9

A draft NIP for Inkan 👇 #nevent1q…uztd

Block 963296 2 - high priority 1 - medium priority 1 - low ...

Block 963296 2 - high priority 1 - medium priority 1 - low ...

Nostr event nevent1qqs85ewa5lnyxrg0vynkrzvtsuzkz9zfg3sts3lfg54cp383640z4nspr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgsrmqhg7mxxczt9gjln8ey8tgpl2cq2elm7c3n7z59pe3m395s5mjgrvae3x

Maybe https://i.nostr.build/Yf09vR0A2p89AeuEIzeILL.gif

NIP-XX Cold-Storage Identities for Nostr draft optional This NIP ...

Block 963296 2 - high priority 1 - medium priority 1 - low ...

Nostr event nevent1qqsrlu2r9kzgag9vk5z0hmtu7xdtjyxlx9tkl0gzrh4fwgvvxj8urqqpr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygpn3e2f

Block 963296 1 - high priority 1 - medium priority 1 - low ...

Block 963295 1 - high priority 1 - medium priority 1 - low ...

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): ...

Who do you main 👀?

Nostr event nevent1qqs0weh6ezae8zf86yt5czttapz05m3wh275cmr0nf6dhs6e2352pmspr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gc9lgs55

Block 963295 1 - high priority 1 - medium priority 1 - low ...

Nostr event nevent1qqsrqswutk6hc7g7hq2x58jf9fwr7p7yndsxj9dvd57s8n7xlkl2zrgpr4mhxue69uhhyetvv9ujuamgv4ex2er0d968yctfdchxxmmdqgsvuep5su5q4f2qwxfpnza8uz7nmz7kgxwycy0e0vu8gnwpg4vqjyqsec57k

Welcome to The Tacobell Empire, I hope you enjoy your stay.

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): ...

😂 #nevent1q…6ruz

📰 In this week's issue: 🗞️ BREAKING Nostr’s ...