Yes it requires the blockchain. Nostr "simply" needs a relay...

ChipTuner

npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7

hex

01e1af5826ace8f797a9b1de926c6b5c81c1812531e0dbbb5727919c61fcec8f

nevent

nevent1qqsqrcd0tqn2e68hj75mrh5jd344eqwpsyjnrcxmhdtj0yvuv87wercprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsqxefne258ydmfgm2wfl02fsdqgs0d5wx29kweg9amxcqxew4t7kq9pw4jv

Kind-1 (TextNote)

2026-06-09T17:05:03Z

↳ 回复 inkan (npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l)

I would not have been able to implement Inkan without the use of blockchains. Is there anything objectionable about using them?

Yes it requires the blockchain. Nostr "simply" needs a relay and an equipped client to function currently, in all types of topologies. Bringing in another dependency chain creates additional complexity and requires different topological arrangements. Presumably relays and/or clients would need to operate a node (or trust a node) somewhere in order to provide the feature. Right now nostr is fully independent, requiring no chain.

It's just a different model I don't think many would want to opt-in to.

As a part business owner in this space. That just added another server I have to maintain alongside my relay and client (distribution/api) servers.

原始 JSON

{
  "kind": 1,
  "id": "01e1af5826ace8f797a9b1de926c6b5c81c1812531e0dbbb5727919c61fcec8f",
  "pubkey": "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
  "created_at": 1781024703,
  "tags": [
    [
      "e",
      "f9901260bc194e772513aa63bc4c5e4696eaaad9168d08f4d547c18e46eae264",
      "wss://cyberspace.nostr1.com/",
      "root",
      "577de06dce160a0379163a4bb7b680be3e0a0e1c68de6e6ba8c01134b44064dd"
    ],
    [
      "e",
      "7da7b4a3c147a807c56f7c739507098ae15b04da334d37128f3412751340edc7",
      "wss://nos.lol/",
      "reply",
      "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
    ],
    [
      "p",
      "577de06dce160a0379163a4bb7b680be3e0a0e1c68de6e6ba8c01134b44064dd"
    ],
    [
      "p",
      "32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
    ],
    [
      "p",
      "930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9"
    ],
    [
      "p",
      "a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
    ],
    [
      "p",
      "576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9"
    ],
    [
      "p",
      "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58"
    ],
    [
      "p",
      "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
    ]
  ],
  "content": "Yes it requires the blockchain. Nostr \"simply\" needs a relay and an equipped client to function currently, in all types of topologies. Bringing in another dependency chain creates additional complexity and requires different topological arrangements. Presumably relays and/or clients would need to operate a node (or trust a node) somewhere in order to provide the feature. Right now nostr is fully independent, requiring no chain. \n\nIt's just a different model I don't think many would want to opt-in to. \n\nAs a part business owner in this space. That just added another server I have to maintain alongside my relay and client (distribution/api) servers. ",
  "sig": "67e08607e08ee13b86d98ceb5280b314db6649507b2e1b7ea6826f2e9a882d5eb3699a871aec5797dad2af20cb07b507e30a3de3a3b91947a58b37470f1c147a"
}