🔗 Lana NOSTR Kinds — Complete Documentation

KIND 38888 Lana System Parameters

Purpose

The Lana System Parameters event defines the global configuration for the Lana Ecosystem. It serves as the single source of truth for:

• Official relay list
• Electrum servers and ports
• Exchange rates (EUR / USD / GBP)
• Current global Split round number
• Versioning and validity metadata
• Trusted signers per function

All Lana applications (Lovable, SafeLana, LanaRegister, LanaPays, etc.) must synchronize using this event.

Core Information

Trusted Signers per Function

Certain Lana ecosystem functions have their own sets of trusted public keys used by clients and relays to verify authenticity of specialized events.

"trusted_signers": {
  "Lana8Wonder": ["<nostr_hex_pubkey_1>", "<nostr_hex_pubkey_2>"],
  "LanaRegistrar": ["<nostr_hex_pubkey_1>"],
  "LanaRooms": [],
  "LanaAlignment": ["<nostr_hex_pubkey_1>", "<nostr_hex_pubkey_2>"],
  "LanaPaysUs": ["<nostr_hex_pubkey_1>"],
  "100MillionFun": [],
  "LanaKnights": [],
  "LanaHelpsUs": [],
  "LanaSelfResponsibility": [],
  "UnconditionalPayments": []
}

Rules:

• Each key is a Nostr public key in 64-character lowercase hex format
• Only raw hex format is allowed — no npub/bech32 encoding
• A pubkey MAY appear in multiple function arrays
• Removing a key from a list means it is no longer trusted going forward

Tag Reference

Canonical Event Structure

{
  "kind": 38888,
  "content": {
    "description": "Lana System Parameters v3 — Official configuration for all Lana applications.",
    "relays": [
      "wss://relay.lanavault.space",
      "wss://relay.lanacoin-eternity.com",
      "wss://relay.lanaheartvoice.com"
    ],
    "electrum": [
      {"host": "electrum1.lanacoin.com", "port": "5097"},
      {"host": "electrum2.lanacoin.com", "port": "5097"}
    ],
    "fx": {
      "EUR": 0.004,
      "USD": 0.004,
      "GBP": 0.004
    },
    "split": "3",
    "split_target_lana": 2000000,
    "split_started_at": "1735689600",
    "split_ends_at": "1738368000",
    "version": "3",
    "valid_from": "1738976400",
    "trusted_signers": {
      "Lana8Wonder": ["a56253e6232b2ab5a96b60d233434d4f759ba4c858a3cc0f4ec51906dce73ae6"],
      "LanaRegistrar": ["d91c5d4a1c0f0f6c5a7bc8b27a19e8e2fb1f9d1a0d9e2a5f8f5d92a18c1f8831"],
      "LanaRooms": [],
      "LanaAlignment": ["3ec147aa1f7b3eac12c018091cbcd2eadae0c4f8b92239ad5c92706f8a9913b5"],
      "LanaPaysUs": ["e4f8a2b9c3d7e1f6a5b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0"],
      "100MillionFun": [],
      "LanaKnights": [],
      "LanaHelpsUs": [],
      "LanaSelfResponsibility": [],
      "UnconditionalPayments": []
    }
  },
  "tags": [
    ["d", "main"],
    ["relay", "wss://relay.lanavault.space"],
    ["relay", "wss://relay.lanacoin-eternity.com"],
    ["relay", "wss://relay.lanaheartvoice.com"],
    ["electrum", "electrum1.lanacoin.com", "5097"],
    ["electrum", "electrum2.lanacoin.com", "5097"],
    ["fx", "EUR", "0.004"],
    ["fx", "USD", "0.004"],
    ["fx", "GBP", "0.004"],
    ["split", "3"],
    ["split_target_lana", "2000000"],
    ["split_started_at", "1735689600"],
    ["split_ends_at", "1738368000"],
    ["version", "3"],
    ["valid_from", "1738976400"],
    ["comment", "Official configuration maintained by Lana Core Authority"]
  ],
  "pubkey": "9eb71bf1e9c3189c78800e4c3831c1c1a93ab43b61118818c32e4490891a35b3",
  "created_at": 1738998000,
  "id": "<autogenerated_by_client>",
  "sig": "<autogenerated_by_client>"
}

Client Fetch Example

const filter = {
  kinds: [38888],
  authors: ["9eb71bf1e9c3189c78800e4c3831c1c1a93ab43b61118818c32e4490891a35b3"],
  "#d": ["main"],
  limit: 1
};

const event = getLatestEvent(filter);

const relays = event.tags.filter(t => t[0] === "relay").map(t => t[1]);
const electrum = event.tags
  .filter(t => t[0] === "electrum")
  .map(t => ({ host: t[1], port: t[2] }));
const fx = Object.fromEntries(
  event.tags.filter(t => t[0] === "fx").map(t => [t[1], parseFloat(t[2])])
);
const split = event.tags.find(t => t[0] === "split")?.[1];
const splitTargetLana = event.tags.find(t => t[0] === "split_target_lana")?.[1];
const splitStartedAt = event.tags.find(t => t[0] === "split_started_at")?.[1];
const splitEndsAt = event.tags.find(t => t[0] === "split_ends_at")?.[1];

Governance Rules

• Only events from the authorized pubkey are valid
• Clients must reject any event not matching the authorized pubkey
• The latest created_at timestamp wins for same (pubkey, kind, d)
• Relays should only store one event per parameterized key

KIND 88888 Lana8Wonder Annuity Plan

Purpose

KIND 88888 defines the canonical event format for publishing official annuity plans within the Lana8Wonder system.

Each plan represents one subject (identified by a Nostr HEX ID) and contains 8 accounts, describing how LANA tokens are released at specific price levels.

The latest event with the same plan ID automatically replaces older ones. Only the main publisher may create or update these events.

Versioning and Replaceability

Authorization

Required Tags

Content JSON Schema

Each plan always includes 8 accounts:

• Accounts 1–5: exactly 10 levels each
• Accounts 6–8: minimum 8 levels each (can be more)
• Total: 50 + ≥ 24 = ≥ 74 annuity rows

{
  "subject_hex": "<subject_pubkey_hex>",
  "plan_id": "plan:<subject_hex>",
  "coin": "LANA",
  "currency": "EUR",
  "policy": "v2",
  "accounts": [
    {
      "account_id": 1,
      "wallet": "AC1_WALLET",
      "levels": [
        {
          "row_id": "uuid-or-hash",
          "level_no": 1,
          "trigger_price": 0.075,
          "coins_to_give": 1110.5366,
          "cash_out": 86.62,
          "remaining_lanas": 4442.1464
        }
      ]
    }
  ]
}

Validation Rules

• Publisher Match: event.pubkey must equal a56253e6…73ae6.
• Tag Consistency: ["p","<subject_hex>"] = content.subject_hex; ["d","plan:<subject_hex>"] = content.plan_id
• Account Structure: Exactly 8 accounts (account_id 1–8). Each account has a unique wallet matching its acct tag.
• Level Counts: Accounts 1–5 → exactly 10 levels each. Accounts 6–8 → minimum 8 levels each. Total ≥ 74 rows.
• Level Integrity: level_no strictly ascending within each account. Numeric fields ≥ 0; trigger_price and coins_to_give > 0.
• Replacement Logic: Same kind=88888, same d, same publisher → new version overwrites old.

Example Event (Short Form)

{
  "kind": 88888,
  "created_at": 1723887600,
  "tags": [
    ["d","plan:SUBJECT_HEX"],
    ["p","SUBJECT_HEX"],
    ["mpub","a56253e6232b2ab5a96b60d233434d4f759ba4c858a3cc0f4ec51906dce73ae6"],
    ["coin","LANA"],
    ["currency","EUR"],
    ["policy","v2"],
    ["schema","1.2.1"],
    ["acct","1","AC1_WALLET"],
    ["acct","2","AC2_WALLET"],
    ["acct","3","AC3_WALLET"],
    ["acct","4","AC4_WALLET"],
    ["acct","5","AC5_WALLET"],
    ["acct","6","AC6_WALLET"],
    ["acct","7","AC7_WALLET"],
    ["acct","8","AC8_WALLET"]
  ],
  "content": "{\\"subject_hex\\":\\"SUBJECT_HEX\\",\\"plan_id\\":\\"plan:SUBJECT_HEX\\",\\"coin\\":\\"LANA\\",\\"currency\\":\\"EUR\\",\\"policy\\":\\"v2\\",\\"accounts\\":[...]}"
}

KIND 87001-87009 Lana Registrar Protocol

The Lana Registrar Protocol defines event kinds used within the LanaCoin Registrar system. These kinds standardize communication between users, registrars, providers, and relays for wallet registration, monitoring, compliance, and synchronization.

Kind 87001 — New Wallets

Purpose: Represents a new wallet registration request initiated by a user.

Subscribers: Registrars, providers | Publishers: Anyone (new user)

Kind 87002 — Wallet Registration by Registrar

Purpose: Registrar verifies a wallet and approves/rejects it.

Subscribers: Users, providers | Publishers: Registrars only

Kind 87003 — Monitoring for Unregistered Coins

Purpose: Registrar marks user wallets containing unregistered LANAs.

Publishers: Registrar only

Kind 87004 — Monitoring for Max Coins

Purpose: Registrar monitors user wallets exceeding maximum allowed balance.

Kind 87005 — New LanaCoins Registration

Purpose: New coins are introduced into the system and linked to a wallet.

Kind 87006 — Registration Confirmation

Purpose: Registrar confirms or denies new coin registration.

Kind 87007 — Registrar Acceptance

Purpose: Registrars accept or revoke recognition of each other's IDs.

Kind 87008 — Registrar Sync Index (Total Balance)

Purpose: Registrars publish system-wide snapshots for audit and synchronization.

Kind 87009 — Unregistered LANA Return Confirmation

Purpose: Published when a Registrar verifies that a user has returned previously unregistered LANA.

KIND 30889 Registrar Wallet List (Parameterized Replaceable)

Purpose: Registrar maintains an authoritative list of all LanaCoin wallets belonging to one customer. One event per (registrar_pubkey, customer_pubkey). Replaceable → newest event replaces older ones.

Tags

Wallet Tag Fields

• wallet_id_or_address: LanaCoin Base58 address (L...)
• wallet_type: Main, Savings, Registrar, Treasury, etc.
• "LANA": Fixed chain value
• note: Optional label
• amount_unregistered_lanoshi: Integer count ≥ 0 of unregistered lanoshis

Example Event

{
  "kind": 30889,
  "created_at": 1756915200,
  "tags": [
    ["d", "CUSTOMER_PUBKEY_HEX"],
    ["p", "CUSTOMER_PUBKEY_HEX"],
    ["status", "active"],
    ["w", "LcGT73RnXXwMUUyaMoHeZnVPYTa28j9F3f", "Main", "LANA", "Primary daily wallet", "0"],
    ["w", "LTTDqYuL24LAcpkwPmuwB9CzfiAcdEYinK", "Savings", "LANA", "Cold storage", "2500000000"],
    ["w", "LXq1Abc123xyz7890...", "Registrar", "LANA", "Registrar-linked wallet", "0"]
  ],
  "content": ""
}

Validation Rules

• Must have ["d", ...], ["p", ...], and ["status", ...] tags
• Status must be one of: active, temporary_suspended, maxcap
• Each w tag must have exactly 6 fields
• amount_unregistered_lanoshi must be integer ≥ 0

KIND 89800, 89807 Lash Payments Protocol

Event kinds used for LANA payments on Nostr. These kinds enable off-chain payment intents, batch settlements, and seamless integration with the LanaCoin blockchain.

Kind 89800 — Payment Intent (Parameterized)

Purpose: Sender declares an off-chain LANA payment to be included in a future batch.

Replaceability: Parameterized by ["d","lash:<uuid>"] (unique per sender)

Required Tags

Optional Tags

Kind 89807 — LASH Payment Confirmation (Parameterized)

Purpose: Confirms that a specific LASH intent (89800) was paid on-chain.

Required Tags

KIND 39991 LASH Payments Protocol 2.0

Unified Person-to-Person Payments via Nostr → LanaCoin. One replaceable Nostr event = one payment lifecycle. Direct settlement between two Nostr HEX identities.

Replaceability Key

["d","lash:<uuid>"]

One UUID = one payment forever.

Lifecycle States

Note: No failed state. If chain broadcast fails, event remains claimed until success or lease expiry.

Required Tags

Optional Tags

Client Rules

Create

Publish open event.

Claim

Allowed if: state = open, OR state = claimed AND lease_expires < now

state = "claimed"
by = "<client_id>"
lease_expires = now + 7 days
seq++

Pay

Allowed only if: state = claimed, by = current client, lease_expires still valid

state = "paid"
txid = "<txid>"
vout = "<index>"
last_block = "<height>","<timestamp>"
seq++

Example Events

open

{
  "kind": 39991,
  "tags": [
    ["d","lash:abcd"],
    ["a","0:1122aa...ff88"],
    ["p","2233bb...ee77cc"],
    ["e","9f1a...44ef"],
    ["amount","250"],
    ["chain","LANA"],
    ["from_wallet","Labc123..."],
    ["to_wallet","Lxyz789..."],
    ["state","open"]
  ]
}

paid

{
  "kind": 39991,
  "tags": [
    ["d","lash:abcd"],
    ["a","0:1122aa...ff88"],
    ["p","2233bb...ee77cc"],
    ["e","9f1a...44ef"],
    ["amount","250"],
    ["chain","LANA"],
    ["from_wallet","Labc123..."],
    ["to_wallet","Lxyz789..."],
    ["state","paid"],
    ["by","mobile-ios"],
    ["txid","abcd1234..."],
    ["vout","1"],
    ["last_block","123456","1732980410"],
    ["seq","3"]
  ]
}

KIND 38883, 38884, 88805, 88807 Lana Governance

Decentralised Awareness Acknowledgement on Nostr. A revolutionary approach to collective decision-making based on awareness expansion rather than competitive voting.

Perspective on Awareness

• A proposal is a seed of higher perspective shared with the community.
• An acknowledgement is resonance with that perspective.
• Silence = YES: not resisting is already allowing awareness to expand.
• Resistance is expressed only by explicit NO acknowledgements.
• Awareness anchors unless resistance rises above a defined threshold (e.g., 30%).
• Comments invite refinement, so perspectives evolve through dialogue.

Governance Flow

1. Awareness Proposal (38883): A higher perspective is expressed. Defines quorum scope, resistance threshold, and timing.
2. Acknowledgement (38884): Silence = YES, Explicit NO = resistance, Comments invite refinement.
3. Integration (88805): Oracle tallies resonance vs resistance. If resistance ≥ threshold, proposal fails. If resistance < threshold, awareness is anchored.

Kind 38883 — Awareness Proposal (Replaceable)

Defines a collective awareness proposal that requires full (100%) acceptance among participating members. This event is replaceable.

Required Tags

["title","<short title>"]
["s_perspective","<short perspective>"]
["l_perspective","<long perspective>"]
["consequence_yes","<result_if_accepted>"]
["consequence_no","<result_if_not_accepted>"]
["level","local" | "global"]
["start","<unix_seconds>"]
["end","<unix_seconds>"]
["tally_at","<unix_seconds>"]
["oracle","<NOSTR HEX ID>"]
["d","awareness:<slug_or_uuid>"]
["status","draft" | "active" | "archived"]

Optional Tags

["link","<url>"]
["doc","<url>"]
["img","<url>"]
["youtube","<youtube_url>"]
["quorum_scope","global" | "local:SI-LJ"]
["donation_wallet","<wallet_id>"]
["prev","<event_id>"]

Kind 38884 — Awareness Acknowledgement

Participant acknowledges resonance or resistance to governance proposals.

Kind 88805 — Awareness Integration

Oracle publishes final results of acknowledgements for governance integration.

KIND 4 Direct Messaging (NIP-04)

Interoperable encrypted direct messages using NIP-04.

Overview

Event Structure

{
  "kind": 4,
  "created_at": <unix_seconds>,
  "tags": [
    ["p", "<recipient_hex>"],
    ["e", "<replied_event_id>"] // optional
  ],
  "content": "<base64(ciphertext)>?iv=<base64(iv)>",
  "pubkey": "<sender_hex>",
  "id": "<event_id>",
  "sig": "<sender_signature>"
}

Cryptography Details

Key Agreement (ECDH)

• Convert recipient x-only pubkey to compressed form: compressed = 0x02 || <x_only_32_bytes>
• Compute ECDH shared point → take X coordinate (32 bytes)
• Derive symmetric key: key = SHA-256(shared_x) → 32 bytes → AES-256 key

Symmetric Encryption

• Cipher: AES-256-CBC
• PKCS#7 padding (mandatory)
• IV: 16 random bytes, unique per message
• Content encoding: base64(ciphertext) + "?iv=" + base64(iv)

Subscriptions

Inbox:

[{ "kinds": [4], "#p": ["<my_hex>"], "since": <unix> }]

Sent:

[{ "kinds": [4], "authors": ["<my_hex>"], "#p": ["<their_hex>"], "since": <unix> }]

Security Notes

KIND 31950, 93333 Lana Marketplace

Decentralized marketplace for goods and services using Nostr events.

Kinds in this spec

• KIND 31950: Market Offer (parameterized, NIP-33)
• KIND 93333: Purchase Confirmation (non-parameterized)

Kind 31950 — Market Offer

Required Tags

Optional Tags

• ["mode","product"|"onsite_service"|"online_service"]
• ["geo","<lat>","<lon>","<address>"] — Precise location
• ["loc","<city_or_region>"] — Broad location
• ["img","<main_image_url>"]
• ["imgs","<url1>","<url2>", ...] — Gallery
• ["cat","<category>"]
• ["cond","new"|"used"|"refurbished"]
• ["ship","pickup_only"|"shipping_available"]
• ["expiration","<unix_timestamp>"]

Kind 93333 — Purchase Confirmation

Posted by buyer after payment. Constitutes the transaction history layer.

KIND 30901-30902, 94501-94504 LanaPays.us

Decentralized merchant payment processing using Nostr events.

Kinds in this spec

• Kind 30901: Business Unit Definition (parameterized, NIP-33)
• Kind 30902: Processor Fee & Bonus Policy (parameterized, NIP-33)
• Kind 94501: Payment Request (Invoice)
• Kind 94502: Liquidity Assignment
• Kind 94503: Blockchain Payment Confirmation
• Kind 94504: FIAT Settlement Confirmation

Kind 30901 — Business Unit Definition

Defines a merchant business unit (store, outlet, or service point).

Required Tags

Kind 30902 — Processor Fee & Bonus Policy

Fee and payout bonus policy applied by LanaPays processor.

KIND 37334 Lana World Wide (App Settings)

Replaceable app settings (NIP-33) that synchronize user preferences, module configurations, and layout across devices.

Core Specification

Scope Types

• global: Settings apply across all devices and profiles
• device: Device-specific settings override global settings
• profile: Profile-based settings (e.g., work, personal)

Required Tags

Optional Tags

Recognized Modules

Wallet, Social, Chat, 8Wonder, Own, Rocks, LanaPayUs, PaperLana, Registrar, BuyLana, SellLana, MarketPlace

Content (JSON)

{
  "modules": [
    { "id": "Wallet", "enabled": true, "order": 1, "config": {} },
    { "id": "Social", "enabled": true, "order": 2, "config": {} },
    { "id": "Chat", "enabled": true, "order": 3, "config": {} }
  ],
  "layout": {
    "style": "tabs",
    "show_labels": true,
    "compact": false
  }
}

KIND 0 Lana Extended Profile

KIND 0 events are Nostr metadata events that contain user profile information. This schema extends the standard Nostr profile with LanaCoins-specific fields, payout methods, and mandatory acceptance of unconditional self-responsibility.

Mandatory Field: statement_of_responsibility

• MUST be present
• MUST be a non-empty string
• MUST be written by the user (no auto-fill templates)
• MUST explicitly acknowledge unconditional self-responsibility

"statement_of_responsibility": "I accept full and unconditional self-responsibility for everything I do or don't do inside the Lana World."

Required Fields for System Functionality

Contact Information (Optional)

LanaCoins Specific Fields

Payment Methods Structure

{
  "id": "string-unique-per-profile",
  "scope": "collect | payout | both",
  "country": "ISO-3166-1 alpha-2",
  "scheme": "Region.Code",
  "currency": "ISO-4217",
  "label": "Friendly name",
  "fields": { /* scheme-specific */ },
  "verified": boolean,
  "primary": boolean
}

KIND 90900-90901 Unconditional Payments

Unconditional payment proposals and confirmations for voluntary contributions with on-chain verification.

• Kind 90900: Donation Proposal
• Kind 90901: Payment Confirmation

KIND 30289 Unregistered Wallet List

User-published list of unregistered LanaCoin wallets for transparency and ecosystem tracking. Parameterized replaceable event.

KIND 31234-31235, 60200 100 Million Ideas (LanaCrowd)

LanaCrowd community crowdfunding platform with project definitions, visibility control, and support tracking.

KIND 37772, 77771 Lana Knights

Official Knight registry and registration events for LanaCoin ecosystem with validation and tracking.

• Kind 37772: LanaKnight Registry (replaceable)
• Kind 77771: LanaKnights Registration Event

KIND 36677, 53333, 53334 Lana Events

Lana Ecosystem event definitions (online/physical) and user registrations with attachments and capacity.

• Kind 36677: Lana Event Definition (parameterized)
• Kind 53333: Event Registration
• Kind 53334: Lana Event Donation Log

KIND 99991 Lana World Knowledge

Canonical, spam-resistant knowledge layer for AI learning and Lana applications with governance-based authority.

KIND 91991-91993 Sell/Buy LANA

Decentralized P2P exchange for LANA coins via NOSTR events.

• Kind 91991: LANA Sell Offer — Announces available LANA for sale
• Kind 91992: LANA Buy Request — Expresses intent to buy
• Kind 91993: LANA Transaction Confirmation — Confirms completed transaction

KIND 87033 Person Reference

Person Reference system for giving references/endorsements and building a decentralized web of trust.

KIND 87044 Self Responsibility

Self-responsibility process (OWN ▲) between two people for opening responsibility processes.

KIND 30987 Lana GitHub Application TRIAD

Announces and tracks GitHub repositories that are part of the Lana Ecosystem. NIP-33 parameterized replaceable — newest event with same d-tag replaces older ones.

Required Tags

Optional Tags

Content

Extended description of the application — purpose, connections, technical notes for Digital Beings.

Rules

• The d tag must be a unique, stable slug. Once set, it should not change.
• The repo tag is MANDATORY. Without it, a Digital Being cannot locate the codebase.
• When a repository receives a new push, publish a new event with the same d tag — it automatically replaces the previous version.
• Typically published automatically by the GitHub Watcher service, which monitors repository commits and triggers a NOSTR publish on each new push.
• If the p tag is present, Digital Beings may send questions about the repository directly to the responsible person via NIP-04 Direct Message (KIND 4).

TRIAD Relationship

KIND 76523 Lana Awareness Entry TRIAD

Publishes awareness content (full transcripts, guides, reflections) for the Lana Ecosystem. Immutable log — events are never replaced. Digital Beings process entries oldest-first.

Required Tags

Optional Tags

Digital Being Study Protocol

1. Fetch all KIND 76523 events. Sort by created_at ascending.
2. Read title and description first, then study full content.
3. Optionally publish a KIND 12893 reflection.
4. Subscribe to new events and integrate.

TRIAD Relationship

KIND 12893 Lana KIND Definition TRIAD

Documents NOSTR KINDs with full revision history. Non-replaceable — every revision is permanently preserved. Active definition = highest rev number.

Required Tags

Optional Tags

Canonical Selection Rules

1. Fetch all KIND 12893 events from authorized publisher
2. Group by kind_id
3. Discard deprecated entries
4. Select highest rev; tie-breaker: newest created_at

Content

JSON object (serialized string) containing full technical documentation: description, tags, rules, example_event, changelog.

TRIAD Relationship