fiatjaf (npub180c…h6w6) Biz (npub1ehh…zjqv) hodlbod (npub1jlr…ynqn) greenart7c3 (npub1w4u…0jr5) I integrated NIP-55 into one of the native apps I'm working on using Biz (npub1ehh…zjqv) capacitorjs plugin and I had some questions about the spec
1. Why are there a mix of "pubkey" and "npub" (bech32) when its been a nostr standard to have all public keys in hex format?
2. The spec says that nip04 and nip44 encrypt and decrypt calls return a "signature" and "id". is that a typeo? I don't see how an encrypt or decrypt call would return a signature
3. What is the use for the "decrypt_zap_event"?
Biz (npub1ehh…zjqv) for the capacitorjs plugin is "app.icon" from "getInstalledSignerApps" always a base64 encoded image/png or could it ever be a URL?
hodlbod (npub1jlr…ynqn) Thanks for making a working example, I used a lot of your code for reference 😀
Also thanks for all the work you guys (and everyone I'm forgetting) put in to this to get this working, its a much better native experience than using NIP-46
hzrd149
npub1ye…pknpr
2024-10-05 16:15:11
Author Public Key
npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknprPublished at
2024-10-05 16:15:11Event JSON
{
"id": "e74b13b56bc786540c5d9110e933bddb110c6537fabf0cd96a629101fc7c02c4",
"pubkey": "266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5",
"created_at": 1728144911,
"kind": 1,
"tags": [
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"",
"mention"
],
[
"p",
"cdee943cbb19c51ab847a66d5d774373aa9f63d287246bb59b0827fa5e637400",
"wss://relay.damus.io/",
"mention"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"",
"mention"
],
[
"p",
"7579076d9aff0a4cfdefa7e2045f2486c7e5d8bc63bfc6b45397233e1bbfcb19",
"",
"mention"
],
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1ehhfg09mr8z34wz85ek46a6rww4f7c7jsujxhdvmpqnl5hnrwsqq2szjqv nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 I integrated NIP-55 into one of the native apps I'm working on using nostr:npub1ehhfg09mr8z34wz85ek46a6rww4f7c7jsujxhdvmpqnl5hnrwsqq2szjqv capacitorjs plugin and I had some questions about the spec\n\n1. Why are there a mix of \"pubkey\" and \"npub\" (bech32) when its been a nostr standard to have all public keys in hex format?\n\n2. The spec says that nip04 and nip44 encrypt and decrypt calls return a \"signature\" and \"id\". is that a typeo? I don't see how an encrypt or decrypt call would return a signature\n\n3. What is the use for the \"decrypt_zap_event\"?\n\nnostr:npub1ehhfg09mr8z34wz85ek46a6rww4f7c7jsujxhdvmpqnl5hnrwsqq2szjqv for the capacitorjs plugin is \"app.icon\" from \"getInstalledSignerApps\" always a base64 encoded image/png or could it ever be a URL?\n\nnostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn Thanks for making a working example, I used a lot of your code for reference 😀 \n\nAlso thanks for all the work you guys (and everyone I'm forgetting) put in to this to get this working, its a much better native experience than using NIP-46",
"sig": "0b5c5a77d9e18c5292d65c0705e01fee20b85c8f28dc2718617c96be87a3cec4847e54cd8f964ab7a67a0a9f3ff305d882a288eeaf994988f5b62125d8dd013a"
}