"They want magic."

inkan
npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l
hex
4e652919d95f5142cec5818b5c8eeeb38392e418bd6e238872b5d523a2731c11nevent
nevent1qqsyueffr8v4752zemzcrz6u3mht8qujusvt6m3r3pett4fr5fe3cygprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcu5ttqxKind-1 (TextNote)
↳ 回复 事件不存在
000000fee3d2783821ef3938519069765be10633dc648d7787ef1ddafc721ba5...
"They want magic."
I've been using this system every single day for months now. It's functional and non-magical. And it doesn't disrupt the regular Nostr protocol. The post I am making right now is fully compatible with both regular Nostr clients and with Inkan.
Inkan uses exactly the same kind-0 profile for the pubkey that signed this post as all other Nostr clients do.
Inkan merely recognizes that the signing key is making the post on behalf of a master identity, and attributes the post to that master identity.
原始 JSON
{
"kind": 1,
"id": "4e652919d95f5142cec5818b5c8eeeb38392e418bd6e238872b5d523a2731c11",
"pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
"created_at": 1788805517,
"tags": [
[
"e",
"0bb4daf107c109410d85a15391dd4961e47fa97cfc7d35f83c1a1df0bb44d531",
"wss://nostr.mom/",
"root",
"50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
],
[
"e",
"000000fee3d2783821ef3938519069765be10633dc648d7787ef1ddafc721ba5",
"wss://relay.snort.social/",
"reply",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"4a38463c2a75e68c24416e7720a3b3befbb0ea6872d5a04692c39e18e8f2dcac"
],
[
"p",
"576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9"
],
[
"p",
"036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58"
],
[
"p",
"50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
]
],
"content": "\"They want magic.\"\n\nI've been using this system every single day for months now. It's functional and non-magical. And it doesn't disrupt the regular Nostr protocol. The post I am making right now is fully compatible with both regular Nostr clients and with Inkan.\n\nInkan uses exactly the same kind-0 profile for the pubkey that signed this post as all other Nostr clients do. \n\nInkan merely recognizes that the signing key is making the post on behalf of a master identity, and attributes the post to that master identity.",
"sig": "3f25fc29781d59964c58d7b291d04b63f8872c0adcfb0f5f5c1b8cfdf2a8900bafff63303427d23345348fb8de457534357e1078446c0f89caf29dfbe4e62046"
}