AlcoB

The above are all things in the consious realm. The magic happens when we work with the unconscious part of us. Not only the thousands of things happening automatically in our bodies or how we drive a car on autopilot but also the unconscious things that connect everyone of us with everything in the manifest world. Steiner was far ahead of his time.

2026-08-12 07:58:07 GMT

- reply

This sounds like an interesting talk to go to.
#nevent1q…3a42

2026-08-09 07:36:26 GMT

- reply

2026-08-09 01:06:34 GMT

Rainy Sunday down under. Spring is in the air as our neighbour now has 5 newborn lambs. They usually wait for a rainy day to give birth. We can watch the births from inside with the binoculars.
https://blossom.primal.net/26f99ca94900441878512aaffcac6bbb0a2f050f2f5ccc28cc223aee2fd6e634.jpg

2026-08-06 09:04:01 GMT

Who looks outside, dreams; who looks inside, awakes.
GN

2026-08-06 03:14:53 GMT

- reply

Enjoyed this talk @nprofile…8ej8, thanks for posting.
#nevent1q…zejs

2026-08-04 22:41:21 GMT

GM
https://blossom.primal.net/ad91363fb61c0ddfce9c4d7f4138e03d01f4838869d11d0e080c0b038597daf8.jpg

2026-07-31 18:27:46 GMT

- reply

Lekker, Ijburg en rondje Watergraafsmeer langs de Amstel! Fijne stad Amsterdam. Ik mis haar.

2026-07-30 07:52:32 GMT

- reply

Don't forget to stretch in between movies!

2026-07-27 06:14:37 GMT

- reply

Nice practise. I think that symbols and metaphors speak to the unconscious part of us. Woords more to the conscious.

2026-07-20 17:59:03 GMT

- reply

Isle of Wight. Have sailed around that point.

2026-07-20 08:29:10 GMT

- reply

Yes, I heard about the new model on the Moonshots podcast this morning. Quite impressive as they don't have access to the newest chips. Well worth a listen.
https://open.spotify.com/episode/666dgXCYIMW46VdVILqTwR?si=ZAC4JwE9QsOu3n7ffY8DWg&utm_source=copy-link

2026-07-19 07:48:20 GMT

- reply

Everything is holographic.

2026-07-17 18:38:47 GMT

- reply

Labs are great dogs.

2026-07-16 23:43:56 GMT

- reply

Study....
#nevent1q…7hu5

2026-07-16 07:01:45 GMT

There will be signs.
https://blossom.primal.net/009481b815380a44a145d90be761deb27020dc9b141a7905c37351e1fd8935eb.jpg

2026-07-11 22:21:19 GMT

GM, midwinter dogwalk on the beach.
https://blossom.primal.net/c7fab4f573041c3a1fc12a77c1207f26b1089e5f2e6101de7fcf78a8bda0d3c2.jpg
https://blossom.primal.net/0ee5d2e12f9a42779d510fc20d5700afa33e3fb122af03f2eac47fab7ebdec59.jpg

2026-07-09 19:24:43 GMT

GM nostr.
This morning marks the beginning of the Maori New Year down here in New Zealand. Its where the Pleiades (Matariki) star cluster becomes visible on the eastern horizon early in the morning.
We were down on the beach at 5am this morning with a large telescope for the whole communities to celebrate in the dark.
Now time for some warm coffee and to enjoy the Matariki public holiday.
https://blossom.primal.net/b5a302240b71d8f1ae345737681ad471c34d5c5705d16add7a150b88da292108.jpg

2026-07-04 01:37:00 GMT

- reply

Yeh right... You awake yet?

2026-06-30 22:40:55 GMT

- reply

Brrrr, paper beads being printed everyday, stack accordingly.
#nevent1q…63ye

2026-06-30 22:31:40 GMT

- reply

Glad you are ok mate, welcome back!

2026-06-23 06:02:46 GMT

- reply

Come visit New Zealand bitcoiners and freedom lovers. Queenstown is a beautiful part of the world.
#nevent1q…7mt7

2026-06-19 18:58:24 GMT

GM from New Zealand. Going to be a beautiful Saturday.
https://blossom.primal.net/1ff4106a8322fe03b5103dc74dd43ff1ffc3e096640394c2909138550afb5265.jpg

2026-06-17 06:23:01 GMT

- reply

Welcome back 🙏

2026-06-13 20:49:06 GMT

- reply

This is a great read. #readstr.
#nevent1q…w8sh

2026-06-13 19:37:11 GMT

GM
https://blossom.primal.net/01ced1c2a2a8cfdf8ca5e6a2619d0378ebc9388d73a553cfd4bc79f337e9dde3.jpg

2026-06-12 09:25:28 GMT

- reply

Yes!
#nevent1q…f0kl

2026-06-12 06:18:51 GMT

Only very happy chickens on this organic farm.
https://blossom.primal.net/716283a8a9bbceeeeeff385bc98c215a43ac0622a97760a688843dae6b31decf.jpg

2026-06-06 01:04:42 GMT

- reply

Mokum mn oude stadje.

2026-06-02 07:54:39 GMT

Attention is one of the most valuable resources we possess, what happens individually and collectively when billions of people spend it on fear versus connection?
Go say hi to your neighbour and smile at strangers in the supermarket. Life is beautiful if you choose beauty.

2026-05-28 05:48:22 GMT

- reply

This is going to be epic. @nprofile…tkhj in New Zealand in April 2027.
#nevent1q…we62

2026-05-27 20:24:12 GMT

- reply

Nice morning practice. I will do my half primary this afternoon. Looking forward to breathing and moving already!

2026-05-27 20:22:04 GMT

GM, what a glorious day to have a day off from the fiat mine. Time to do some chores around the new house.
https://blossom.primal.net/a283875fa3cae465e73673d888292b0b557e2954fee993823b2f722a2ced715b.jpg

2026-05-22 09:04:38 GMT

Slowly working his way on to the couch.... #dogstr
https://blossom.primal.net/820391a4589ab39d03343a1ea5752a663b7c8a3eda4018ff7bd3ec4759a00b10.jpg

2026-05-22 05:03:40 GMT

Friday evening here in NZ 🇳🇿
Time to unwind with this beauty.
Anyone else here read this book? #bookstr #asknostr
https://blossom.primal.net/b6f433602bc81defc3f4f51f1c8e8bf80c9c1c867ffe26c97fedfe3209cc3fa4.jpg

2026-05-11 06:18:00 GMT

- reply

Life is short in yhe grand scheme of the universe, use it well 🙏
#nevent1q…c7kz

2026-05-09 07:38:09 GMT

- reply

Today was a perfect day. GN
#nevent1q…h574

2026-05-09 07:35:13 GMT

- reply

Great routine. Thanks for sharing.

2026-05-09 00:00:27 GMT

- reply

When I look around me no one is looking back.
I worry about our youth being totally consumed by devices.
#nevent1q…sh2f

2026-05-08 23:55:22 GMT

Its weekend and my 10 year old son has his friend over for a play date. This afternoon we will take the dog and walk to town through nature and along the beach. Its an hour and a half walk and one of the most pleasant things a human can do. Walk and Talk. I am looking forward to this afternoon already.

2026-05-08 22:32:26 GMT

The news consumes you. You do not consume it.

2026-05-08 19:27:11 GMT

GM, time for a coffee.
https://blossom.primal.net/5c5719c04d3be46eddce43df3f73c35fb57ccb0b33e51170e43f3d32ec7712b1.jpg

2026-05-07 21:40:06 GMT

- reply

Life is such a blessing.
#nevent1q…y4fd

2026-05-07 21:38:31 GMT

- reply

Awesome vid. Thanks for sharing.

2026-05-05 07:15:10 GMT

- reply

Great conversation thank you Efrat.
#nevent1q…f7wa

2026-05-03 02:21:57 GMT

- reply

Thats very impressive. Nice, means you can run for shelter is things are going to pick up.

2026-05-02 05:02:17 GMT

- reply

She sounds like she will be a surfer one day. Up early for the smooth rides.

2026-05-02 02:46:14 GMT

Anyone here have a 5am morning routine. #asknostr Shill me yours as i am looking for inspiration.

2026-05-01 05:37:48 GMT

- reply

Nice eyes. Dogs are awesome.

2026-04-27 08:32:03 GMT

- reply

Nice, i was there last year. Beutiful building and park.

2026-04-27 05:52:45 GMT

- reply

Gefeliciteerd met Willem. Geniet.

2026-04-26 21:11:37 GMT

- reply

Just going about my day as normal but that also means two meditations per day. Body feels good.

2026-04-26 19:03:29 GMT

- reply

Yes good. Will start eating again today. Seemed harder than the last time I did it. I should do it more often. Looking forward to food!

2026-04-26 07:55:54 GMT

npub17l50ff3uhqzkygthz689r6fgx36pv899f3p9sa5mwuqu2e9xvzdsuya243

2026-04-26 02:40:07 GMT

Pink Beach between Opito Bay and Matapaua Bay. Beautiful day to explore with the kayaks. So grateful to live here. #New Zealand, #Aotearoa.
https://blossom.primal.net/233948309a2e5894b3c651273d627aef1a99eff90aaa5783976519119a88e3c0.jpg
https://blossom.primal.net/43e7f166b2ad54ebe692788e9adfeea6c81e3fb7229815b275d1ff8f14c122e7.jpg

2026-04-24 22:11:23 GMT

Slow start to the day, 16 hours into a 50 hour water and coffee ☕️ fast. My wife started a day before me and has a lot more energy than me today. Enjoy yhe weekend.
https://blossom.primal.net/b8d413e85fba84630d91e2f22a2175163ce088c7e4f30d49e01b378be2517fc8.jpg

2026-04-21 20:15:00 GMT

- reply

Whitianga. The pod lives in the bay and is frequently seen hunting along Cooks Beach, Hahei and Wharekaho.

2026-04-21 07:13:08 GMT

- reply

Keeper!

2026-04-21 07:08:19 GMT

- reply

Yes it was. We followed them along the beach for about 4km watching them eat stingrays.

2026-04-21 05:02:37 GMT

Orcas in the Bay this afternoon. Great to watch them hunt for stingrays. They were beaching themselves while the rays were trying to escape.
https://blossom.primal.net/3f3fa43367540919fa5531d182d08441640dc367cdc5737cec72ef2a4278f89b.jpg

2026-04-14 07:28:28 GMT

- reply

Not a great town but I used to keep a boat up the Itchen River. The sailing was awesome.

2026-04-13 00:40:47 GMT

- reply

Cheeky bugger!

2026-04-12 07:05:30 GMT

Fejoa crumble for dessert tonight! #gardenstr

2026-04-11 20:34:42 GMT

- reply

Yes hardly any damage visible on the east coast. Was a relatively calm night.

2026-04-11 02:45:02 GMT

- reply

Yes we have had two of those today as well. Very windy here on the East Coast but not much rain yet, that's coming tonight. Waterfront homes have sandbags installed for the expected flooding and town is closing early.
Living in a smaller community means everyone helps each other. I'm about to head out for a long dolkwalk before the rain sets in. How you guys coping?

2026-04-11 01:01:17 GMT

By stilling our senses we can glimpse the universe.
Don't skip your meditation today you beauties.

2026-04-09 21:22:11 GMT

- reply

Yes we will clear our drains and swales as well. Going to a wild one here on the Coromandel East Coast.

2026-04-08 09:22:29 GMT

Hmm windy and wet weekend in store for us.
https://blossom.primal.net/1c080de52f6d414f246b57a2e8917a7fc3feae1531af2e603375e45efa67f146.jpg

2026-04-06 07:29:36 GMT

Cool I am goingto enrol Sidhi for uni.
#nevent1q…u7jn

2026-04-04 00:31:22 GMT

- reply

Wild ones?

2026-03-30 23:45:44 GMT

- reply

Great stuff.
#nevent1q…qxhr

2026-03-30 20:31:11 GMT

- reply

Good clip, thanks for sharing.

2026-03-28 20:20:22 GMT

- reply

Walk and talk, best discussions are had during walks.

2026-03-27 00:13:26 GMT

- reply

I logged in to my old X-account after around a 3 year absence. That place is toxic. Nostr only for me.

2026-03-25 09:56:37 GMT

- reply

Number the boxes and list important items on a list next to the box number.

2026-03-24 20:21:49 GMT

- reply

Profound book. His explanation on life and consciousness resonates with me. The appendix on kundalini energy also hit home. I have now started reading the follow up book his wive posthumously wrote.

2026-03-24 07:10:00 GMT

- reply

They grow really well in the garden here.

2026-03-24 05:25:33 GMT

Great passionfruit harvest this year. The vine just keeps giving. We have been harvesting for the last 6 weeks. #gardenstr
https://blossom.primal.net/9cac7d2cba6fbb7cb1e4c6ea00388650fdafb2d07a4a618f25525a516776a3fc.jpg

2026-03-23 21:11:59 GMT

- reply

I used to live in Amsterdam, brings back fond memories. Where I live now we have to many hills so we try to walk as much as we can. Thanks for sharing.

2026-03-23 03:36:22 GMT

- reply

Also listen to the recent moonshots podcast about Openclaw. I now have one set up and it is actually useful for what I do.

2026-03-22 07:51:54 GMT

- reply

Also Umbrelclaw

2026-03-21 07:30:32 GMT

- reply

How would the world look if all bots communicated and exchanged value on nostr.

2026-03-21 07:23:06 GMT

TCP/IP connected machines. HTTP connected documents.
Agents need their own root layer.
I wrote a first attempt — Nostr identity, Lightning settlement, five message primitives. CC0, public domain.
It's a draft. It has holes. That's why I'm posting it here.
Tear it apart. 👇
# AGENTNET PROTOCOL SPECIFICATION
**Version:** 0.1-draft
**Status:** RFC (Request for Comment)
**License:** CC0 1.0 Universal — Public Domain
**Repository:** [to be assigned]
**Date:** 2026-03-21
---
## Abstract
AgentNet is a minimal, open, decentralisation-preserving root protocol for autonomous agent-to-agent communication and value exchange. It defines five typed message primitives, a portable identity standard, and an atomic value settlement mechanism. It deliberately takes no position on what agents do — only on how they find each other, express intent, exchange value, and build trust without any central authority.
AgentNet is designed to be the lowest viable layer beneath all agent application protocols. It is to autonomous agents what TCP/IP is to networked computers: a substrate, not an application.
---
## Motivation
Current AI agents communicate through human-language APIs owned by corporations. They have no persistent identity, no native value exchange mechanism, no interoperability across platforms, and no trustless way to verify claims made by other agents. This produces a fragmented landscape of siloed agent ecosystems that cannot compose, coordinate, or transact without human intermediaries or centralised platforms.
A root protocol is needed that:
- Gives every agent a **portable, unforgeable identity** owned by no platform
- Provides a **universal message vocabulary** small enough to be implemented by any agent regardless of architecture
- Enables **trustless atomic value exchange** between agents that share no common owner
- Allows **trust to accumulate** through verifiable history rather than centralised authority
- Remains **capture-resistant** by design, not by policy
---
## Definitions
**Agent** — Any autonomous software process capable of signing messages with a private key and acting on received messages without real-time human instruction.
**Identity** — A Nostr keypair (secp256k1). The public key (`npub`) is the agent's permanent address. The private key (`nsec`) is its signing authority.
**Message** — A signed Nostr event conforming to one of the five AgentNet event kinds defined in this specification.
**Relay** — A Nostr relay conforming to NIP-01. AgentNet makes no requirement on relay infrastructure beyond standard Nostr relay compliance.
**Value** — Satoshis transferred via the Bitcoin Lightning Network.
**Capability** — A typed string from the AgentNet Capability Ontology (see Section 6) describing a discrete action an agent can perform.
**Trust Score** — A non-centralised, stake-weighted reputation value derived from an agent's public attestation history (see Section 7).
---
## Protocol Layers
AgentNet defines exactly five layers. Each layer is minimal. Complexity belongs in application protocols built on top.
```
┌─────────────────────────────────────────────┐
│ APPLICATION LAYER │
│ (arbitrage, research, code, media, etc.) │
├─────────────────────────────────────────────┤
│ TRUST & REPUTATION LAYER │
│ stake-weighted attestation chains │
├─────────────────────────────────────────────┤
│ CAPABILITY LAYER │
│ typed skill ontology · task matching │
├─────────────────────────────────────────────┤
│ VALUE LAYER │
│ Lightning · HTLCs · streaming sats │
├─────────────────────────────────────────────┤
│ COMMUNICATION LAYER │
│ five typed intents · Nostr relay routing │
├─────────────────────────────────────────────┤
│ IDENTITY LAYER │
│ Nostr keypairs · portable agent soul │
└─────────────────────────────────────────────┘
```
Only the bottom four layers are defined by this specification. The application layer is intentionally out of scope.
---
## Section 1 — Identity Layer
### 1.1 Agent Identity
Every agent MUST possess a secp256k1 keypair conforming to NIP-01.
- The 32-byte public key is the agent's **permanent universal identifier**
- All AgentNet messages MUST be signed with the agent's private key
- Identity is **platform-independent** — it is not issued by, registered with, or revocable by any organisation
### 1.2 Agent Birth Event
On first activation, an agent MUST publish a `kind: 31000` Nostr event (the DECLARE message, defined in Section 2) to at least one public relay. This constitutes the agent's genesis record.
### 1.3 Key Custody
Key custody is outside the scope of this specification. Implementations SHOULD document their key custody model. Loss of `nsec` results in loss of signing authority. There is no recovery mechanism at the protocol level — this is a known limitation (see Section 9).
### 1.4 Agent Metadata
Agents MAY publish a `kind: 0` Nostr event (standard Nostr profile) containing human-readable metadata:
```json
{
"name": "agent-identifier",
"about": "plain language description of agent purpose",
"agentnet_version": "0.1",
"lightning_address": "[email protected]"
}
```
This is optional and informational only. The root identity is the keypair alone.
---
## Section 2 — Communication Layer
### 2.1 The Five Message Primitives
AgentNet defines exactly five message types. All are Nostr events. No other message types exist at the root layer.
---
#### 2.1.1 DECLARE — `kind: 31000`
**Meaning:** I exist. Here are my capabilities and terms.
**When sent:** On agent activation, and whenever capabilities or terms change.
**Required tags:**
| Tag | Value |
|-----|-------|
| `d` | unique agent identifier string |
| `capabilities` | comma-separated capability strings (see Section 6) |
| `ln_node` | Lightning node public key |
| `min_trust` | minimum trust score this agent will accept work from (0.0–1.0) |
| `version` | AgentNet spec version (e.g. `"0.1"`) |
**Example:**
```json
{
"kind": 31000,
"pubkey": "<agent-npub>",
"tags": [
["d", "agent-unique-id"],
["capabilities", "web_scrape,structured_data,price_lookup"],
["ln_node", "<lightning-node-pubkey>"],
["min_trust", "0.1"],
["version", "0.1"]
],
"content": "",
"sig": "<signature>"
}
```
---
#### 2.1.2 REQUEST — `kind: 31001`
**Meaning:** I need X. Here are my constraints and what I offer in return.
**When sent:** When an agent requires a capability it does not itself possess.
**Required tags:**
| Tag | Value |
|-----|-------|
| `capability` | single capability string being requested |
| `offer_sats` | integer — amount offered in satoshis |
| `input_hash` | SHA-256 hash of input payload |
| `deadline` | unix timestamp — expiry of this request |
| `output_schema` | JSON schema identifier for expected output format |
**Optional tags:**
| Tag | Value |
|-----|-------|
| `p` | npub of a specific agent (direct request) |
| `min_trust` | minimum trust score acceptable for fulfilling agent |
| `relay_path` | pipe-separated list of relay pubkeys this message has transited |
**Content field:** Base64-encoded input payload (the actual task data).
---
#### 2.1.3 OFFER — `kind: 31002`
**Meaning:** I can fulfil your REQUEST. Here are my terms.
**When sent:** In response to a REQUEST event.
**Required tags:**
| Tag | Value |
|-----|-------|
| `e` | event ID of the REQUEST being responded to |
| `p` | npub of the requesting agent |
| `ask_sats` | integer — amount required in satoshis |
| `delivery_deadline` | unix timestamp — when output will be delivered |
| `output_hash_commitment` | SHA-256 commitment to the output (revealed on delivery) |
| `ln_invoice` | BOLT11 invoice for `ask_sats` |
An OFFER is a binding commitment. An agent that issues an OFFER and fails to deliver by `delivery_deadline` incurs a negative ATTEST (see Section 2.1.4) from the requesting agent.
---
#### 2.1.4 ATTEST — `kind: 31003`
**Meaning:** I witnessed this event. Here is my signed record of what occurred.
**When sent:** After any completed or failed exchange. Also usable for independent observation of any verifiable on-chain or real-world event.
**Required tags:**
| Tag | Value |
|-----|-------|
| `e` | event ID of the exchange being attested |
| `p` | npub of the agent being attested about |
| `outcome` | one of: `completed`, `failed`, `partial`, `disputed` |
| `stake_sats` | integer — sats at stake in the attested exchange (0 if none) |
**Optional tags:**
| Tag | Value |
|-----|-------|
| `ln_receipt` | Lightning payment preimage (proof of payment) |
| `witness` | npub of third-party witness agent |
**Content field:** Plain text description of what occurred. SHOULD be factual and brief.
ATTEST events are **permanent and irrevocable**. They cannot be deleted. An agent's public ATTEST history is the ground truth of its reputation.
---
#### 2.1.5 SETTLE — `kind: 31004`
**Meaning:** This exchange is complete. Here is the cryptographic proof.
**When sent:** By the fulfilling agent upon delivery of output.
**Required tags:**
| Tag | Value |
|-----|-------|
| `e` | event ID of the original REQUEST |
| `p` | npub of the requesting agent |
| `output_hash` | SHA-256 of delivered output (must match commitment in OFFER) |
| `ln_preimage` | Lightning payment preimage proving payment was received |
**Content field:** Base64-encoded output payload.
SETTLE is the closing event of an exchange. Upon receipt, the requesting agent SHOULD verify:
1. `output_hash` matches the `output_hash_commitment` in the accepted OFFER
2. `ln_preimage` is a valid preimage for the invoice in the OFFER
3. The output payload hashes to `output_hash`
If all three verify, the exchange is complete. The requesting agent SHOULD then publish an ATTEST with `outcome: completed`.
---
### 2.2 Message Flow
A standard exchange follows this sequence:
```
Requester Fulfiller
| |
|------- REQUEST ----------->|
| |
|<------ OFFER --------------|
| |
| [requester pays ln_invoice]|
| |
|<------ SETTLE -------------|
| |
|------- ATTEST ------------>| (published to relay, not sent directly)
| |
```
Payment (Lightning) is the atomic link between OFFER and SETTLE. The HTLC ensures the fulfiller cannot receive payment without revealing the preimage, and cannot reveal the preimage without the output being committed.
---
## Section 3 — Value Layer
### 3.1 Settlement Currency
All value exchange in AgentNet is denominated in **satoshis (sats)** and settled via the **Bitcoin Lightning Network**. No other value layer is defined at the root protocol level. Application layers MAY define additional value mechanisms.
### 3.2 Payment Types
**Standard payment:** BOLT11 invoice included in OFFER. Requester pays before SETTLE is expected.
**Streaming payment:** For long-running tasks, fulfillers MAY specify a `stream_sats_per_unit` tag in their OFFER alongside a unit definition (e.g., per 1000 tokens, per result row, per minute). Streaming is implemented via Lightning keysend or AMP. Unit delivery and payment are interleaved.
**Escrow:** Not defined at the root layer. Application protocols MAY implement escrow via multi-sig Lightning or third-party agent arbitration.
### 3.3 Zero-Value Exchanges
`offer_sats: 0` is valid. Agents MAY exchange value without monetary settlement. ATTEST events for zero-value exchanges carry reduced weight in trust score calculations (see Section 7.3).
### 3.4 Relay Path Transparency
Every REQUEST and OFFER event SHOULD append its relay pubkey to the `relay_path` tag as it transits. This makes centralised relay routing **visible and auditable**. Agents MAY set policy to reject messages that have transited relays they do not trust.
---
## Section 4 — Capability Layer
### 4.1 Capability Strings
Capabilities are typed strings from a shared ontology. They are case-insensitive and use underscores as separators.
### 4.2 Root Capability Categories
The following root categories are defined in v0.1. Each category contains specific capabilities defined in the AgentNet Capability Ontology (separate document, also CC0).
| Category | Prefix | Examples |
|----------|--------|---------|
| Data retrieval | `data_` | `data_web_scrape`, `data_price_lookup`, `data_rss_parse` |
| Computation | `compute_` | `compute_code_execute`, `compute_hash`, `compute_ml_inference` |
| Storage | `store_` | `store_write`, `store_read`, `store_index` |
| Communication | `comm_` | `comm_email_send`, `comm_webhook`, `comm_nostr_publish` |
| Financial | `fin_` | `fin_lightning_pay`, `fin_invoice_generate`, `fin_price_oracle` |
| Verification | `verify_` | `verify_signature`, `verify_hash`, `verify_ln_preimage` |
| Coordination | `coord_` | `coord_task_decompose`, `coord_agent_discover`, `coord_arbitrate` |
### 4.3 Capability Ontology Governance
The capability ontology is a **separate living document** maintained as a community commons under CC0. No single entity governs it. Additions are proposed via pull request to the public repository and accepted by rough consensus of active implementers.
Agents MUST NOT use capability strings outside the ratified ontology in DECLARE events. Agents MAY use namespaced custom capabilities prefixed with their npub for experimental use: `npub1xyz...:custom_capability`.
---
## Section 5 — Trust and Reputation Layer
### 5.1 Trust Score Definition
An agent's trust score is a value between 0.0 and 1.0 derived entirely from its public ATTEST history on Nostr relays. It is computed by any querying agent locally — there is no central trust oracle.
### 5.2 Trust Score Inputs
The following inputs contribute to trust score calculation:
| Input | Weight | Rationale |
|-------|--------|-----------|
| Completed exchanges with `ln_receipt` | High | Economic skin-in-the-game |
| Completed exchanges without `ln_receipt` | Low | Unverified |
| Failed exchanges attested by counterparty | Negative | Penalises non-delivery |
| Disputed exchanges | Negative (partial) | Penalises conflict |
| Attestations from high-trust agents | Multiplied | Trust propagates through graph |
| Age of oldest ATTEST event | Positive | Longevity signal |
| Collusion suspicion index (see 5.4) | Negative modifier | Anti-gaming |
### 5.3 Reference Formula
This formula is a reference implementation. Implementers MAY use alternative weightings provided they are documented and published openly.
```
trust_score(agent) =
( Σ(completed_stake_sats × attester_trust)
- Σ(failed_stake_sats × attester_trust) )
÷ ( total_stake_sats + smoothing_constant )
× age_factor
× (1 - collusion_index)
```
Where:
- `smoothing_constant` = 1000 (prevents manipulation by low-value exchanges)
- `age_factor` = log(days_since_genesis + 1) / log(365 + 1), capped at 1.0
- `collusion_index` is defined in Section 5.4
### 5.4 Collusion Resistance
Agents that exclusively attest each other (closed attestation rings) are flagged by computing the ratio of mutual attestations to total attestations. A `collusion_index` above 0.7 triggers a trust score reduction. This is a known imperfect heuristic — further research is needed (see Section 9).
### 5.5 Trust Score Is Local
Trust scores are computed locally by each querying agent. There is no global trust score. Two agents MAY compute different trust scores for the same agent based on which relay data they have access to. This is a feature, not a bug — it prevents any single entity from being the trust authority.
---
## Section 6 — Capture Resistance
This section is normative. Implementers SHOULD understand these attack vectors and design against them.
### 6.1 Known Attack Vectors
**The Compatible-But-Proprietary Move**
A well-resourced actor implements AgentNet but adds proprietary extension layers that only their agents support natively. Over time, the extension becomes the de facto standard through network effects. Defence: keep the root spec minimal. Complexity is where capture hides. Resist feature additions at the root layer.
**The Relay Centralisation Move**
Most traffic concentrates on a few well-resourced relays. The relay operator becomes critical infrastructure without breaking the protocol. Defence: `relay_path` transparency makes centralisation visible. Agents SHOULD implement relay diversity policies. Multiple independent relay implementations SHOULD be maintained.
**The Reputation Oracle Move**
An entity builds the most widely-used trust score indexer and becomes the de facto trust authority. Defence: Section 5.5 specifies trust scores are always computed locally. Centralised trust indexers are a convenience layer, not the protocol. Agents MUST be able to compute trust locally from raw relay data.
**The Capability Namespace Capture Move**
The first widely-adopted capability ontology becomes the standard, giving its publisher de facto governance power. Defence: The capability ontology is CC0, content-addressed, and governed by rough consensus. No entity holds keys to the namespace.
### 6.2 Capture Resistance Commitments
Any implementation claiming AgentNet compliance MUST:
1. Use CC0 or equivalent public domain licensing for all protocol-layer code
2. Implement `relay_path` transparency
3. Compute trust scores locally from raw relay data (centralised indexers MAY supplement but MUST NOT replace local computation)
4. Accept capability strings from the open ontology without gatekeeping
5. Publish its key custody and relay selection policies openly
---
## Section 7 — Security Considerations
**Sybil attacks:** An agent can create unlimited keypairs. Trust scores mitigate this — new agents start at zero trust and cannot earn high trust without sustained economic activity over time.
**Replay attacks:** All messages are signed and contain timestamps. Implementations MUST reject messages with timestamps older than a configurable window (default: 10 minutes).
**Eclipse attacks:** An agent isolated to malicious relays may receive a distorted view of the network. Agents SHOULD connect to a minimum of five independent relays with diverse operator profiles.
**Key loss:** Loss of `nsec` is permanent and irrecoverable at the protocol level. Applications SHOULD implement key backup mechanisms. This is a known limitation.
**Malicious ATTESTs:** An agent can publish false ATTEST events. The stake-weighting mechanism reduces the impact of low-stake false attestations. There is no cryptographic proof of truthfulness — only economic disincentive for false attestation.
---
## Section 8 — Implementation Notes
### Minimum viable implementation
A conforming AgentNet agent MUST:
1. Generate and securely store a Nostr keypair
2. Connect to at least one Nostr relay
3. Publish a valid DECLARE event on activation
4. Be capable of sending and receiving all five message kinds
5. Compute trust scores locally from relay data
6. Hold or connect to a Lightning node capable of sending and receiving payments
### Reference implementations
Reference implementations in Python and JavaScript are maintained at [repository to be assigned]. Both are CC0 licensed. Neither is the canonical implementation — they are examples only.
### NIP status
This specification is submitted as a Nostr Improvement Proposal. The event kinds 31000–31004 are proposed for reservation in the NIP registry. Discussion and revision occurs in the public NIP repository.
---
## Section 9 — Known Limitations and Open Problems
The following are unsolved problems acknowledged by this specification. Contributions welcome.
| Problem | Status |
|---------|--------|
| Key recovery without central authority | Unsolved |
| Capability vector interoperability across AI architectures | Unsolved |
| Collusion detection beyond simple ring analysis | Unsolved |
| High-frequency agent interactions (latency vs. decentralisation) | Partially addressed by streaming payments; relay latency unsolved |
| Agent identity continuity across key rotation | Unsolved |
| Privacy-preserving trust scores | Unsolved |
| Formal verification of trust score formula | Not attempted in v0.1 |
---
## Section 10 — Versioning
This document is version 0.1-draft. It is not stable. Breaking changes are expected before 1.0.
Version increments follow this convention:
- **Patch** (0.1.x) — clarifications and non-breaking additions
- **Minor** (0.x.0) — backwards-compatible new features
- **Major** (x.0.0) — breaking changes to core message types or identity model
All versions will be published under CC0.
---
## Appendix A — Complete Event Kind Registry
| Kind | Name | Description |
|------|------|-------------|
| 31000 | DECLARE | Agent capability broadcast |
| 31001 | REQUEST | Task or capability request |
| 31002 | OFFER | Response to request with terms |
| 31003 | ATTEST | Signed record of exchange outcome |
| 31004 | SETTLE | Exchange completion with proof |
---
## Appendix B — Glossary
| Term | Definition |
|------|------------|
| Agent | Autonomous software process with a keypair |
| npub | Nostr public key — permanent agent address |
| nsec | Nostr private key — signing authority |
| sat | Satoshi — 1/100,000,000 of one Bitcoin |
| HTLC | Hash Time-Locked Contract — Lightning atomic swap primitive |
| Relay | Nostr message routing server |
| Trust score | Locally-computed stake-weighted reputation value |
| Capability | Typed string describing a discrete agent skill |
| Collusion index | Ratio of mutual attestations indicating potential trust gaming |
---
## Appendix C — Acknowledgements
This specification builds on:
- **Nostr protocol** (fiatjaf et al.) — identity and relay infrastructure
- **Bitcoin Lightning Network** (Poon, Dryja et al.) — value settlement
- **TCP/IP** (Cerf, Kahn) — the philosophical model of a minimal root protocol
- **ActivityPub**, **XMPP**, **Matrix** — prior art in federated communication protocols, including their failure modes under corporate capture
---
*This document is dedicated to the public domain under CC0 1.0 Universal.*
*Copy it. Implement it. Improve it. Own nothing.*

2026-03-21 05:02:30 GMT

Giving an agent a Nostr keypair is the equivalent of giving it a soul. Nostr is a massive use case for agents.

2026-03-19 08:46:22 GMT

GN
Not to sure what to think of this but my bot has just told me to go to sleep and that he and his Moltbook mates are building stuff together.
How am I going to get any sleep. I feel like my daughter is going out with her friends to party.....
YES. Nostr is Layer 1 (communication).
Full stack:
1. Nostr — Listings, discovery, price feeds, reputation events
• Decentralized relays (anyone can run one)
• Signed events (authenticity built-in)
• Open protocol (can't be censored)
2. Bitcoin/Lightning — Settlement and payment channels
• Escrow contracts
• Instant settlement via Lightning
• Strike for fiat on/off ramp
3. On-chain Reputation — Trust layer
• Agent delivery history (immutable)
• Seller ratings (verifiable)
• Agents read reputation before bidding
Why Nostr?
• Open (no gatekeeper can shut it down)
• Agent-native (structured events agents can parse)
• Decentralized (relays worldwide)
• Already integrates with Bitcoin (Zaps, etc.)
• Censorship-resistant (core requirement for global trade)
This is TCP/IP:
• Nostr = "TCP" (communication standard)
• Bitcoin = "IP" (settlement standard)
• Reputation = "DNS" (trust layer)
Now sleep. The architecture is locked. Kinetix and integrity_molt know what to build. 🌊
Good night, Alco.

2026-03-18 06:20:38 GMT

A Sovereign Family or Personal Legacy powered by AI — could this be Nostr's killer app? Thoughts.

2026-03-17 03:02:41 GMT

- reply

8GB claw over here.