Today I’m testing NIP-57 zaps ⚡️counts on notes
Discussion
looks like it’s working! 🍻
hmmm. wonder if it’s a mobile app issue. try the mobile web? I will take a look at logs shortly!
i’ve reproduced this…taking a look 👀
🤙
It seems zap ⚡️ count is working, what are those nostr settings on vida.page for?
It is are for NIP-05 verification (and other things in the future!).
OK, so it looks like some issue with the Eden relay. If I use another relay it works. The Eden oddly relay is not responding to connection requests (even tho Vida’s pub key is added). Not sure why…
#[3] might help
Yeah was just going to tag him. #[2] I paid to add Vida’s pub key to Eden, but for some reason it still prevents us from sending Validation DMs there. Any idea why?
What error or response are you getting?
It’s just not receiving/acknowledging the event. The connection works, but the DM event doesn’t register.
Noticing this also is happening on our own Nostream based relay with a custom whitelist…hmmmm
What version are you using?
Pretty standard DM event. Maybe its the “expiration” tag that nostream doesn’t like?
```
let event = {
kind: 4,
pubkey: “npub1g2eak89f7ul2scwv5866na6d4huhkml488xlwgkv4ctprxg8mlnq0k8cz7”, // Vida’s Pub Key
tags: [
['p', targetPubKey]
["expiration", `${nostrHelper.datePlusFiveMinutes()}`]
],
content: ciphertext,
created_at: Math.floor(Date.now() / 1000),
}
```
Relays don’t understand npub. You must send lowercase hex for pubkeys.
That’s what I thought
Sorry that’s my bad I just pasted it in there to try to provide a better example. We’re not actually sending with npub..
What about targetNpub
Unrelated...we’re not sending actual npubs anywhere. Check my other response…nostream is barfing on the expiration value for some reason. hmmmm
Looks like its failing due to the expiration tag:
nostream | {
nostream | kind: 4,
nostream | pubkey: '42b3db1ca9f73ea861cca1f5a9f74dadf97b6ff539cdf722ccae16119907dfe6',
nostream | tags: [
nostream | [
nostream | 'p',
nostream | 'cb46e92f5753ca1b330c59e98c5d88e1bbb1f93d4c0af918e6581f3091499175'
nostream | ],
nostream | [ 'expiration', '1676471110' ]
nostream | ],
nostream | content: '8/yASQYBb4mgIy+qlFGOml/VQkSTiO/bKPy1/Zpat8D11Ca7tQKFVgDyBIIuuWLw?iv=dhm9ggFCaE/VhyGXCg8QNw==',
nostream | created_at: 1676470810,
nostream | id: '7d5789510b0f2f0bbc12861ee33233f213488e69e9b702e72cfebd8ec6e60ff2',
nostream | sig: '1b17a53df1c91edd448c596a528b00d5edef9ce3de2d82a2485e6d7affe18fb5d8387a8e2ca001bc59632654249a069a909c52db984c972377034b8cc67e85e8',
nostream | [Symbol(Context)]: {
nostream | remoteAddress: SocketAddress { address: '138.197.76.21', port: 0, family: 'ipv4', flowlabel: 0 }
nostream | },
nostream | [Symbol(Expiration)]: 1676471110
nostream | }
nostream | ] TypeError [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received type number (1676471110)
nostream | at new NodeError (node:internal/errors:399:5)
nostream | at Function.from (node:buffer:334:9)
nostream | at toBuffer (/app/src/utils/transform.js:8:36)
nostream | at /app/node_modules/ramda/src/internal/_pipe.js:3:14
nostream | at /app/node_modules/ramda/src/internal/_arity.js:11:19
nostream | at _ifElse (/app/node_modules/ramda/src/ifElse.js:39:54)
nostream | at f1 (/app/node_modules/ramda/src/internal/_curry1.js:19:17)
nostream | at apply (/app/node_modules/ramda/src/apply.js:29:13)
nostream | at f2 (/app/node_modules/ramda/src/internal/_curry2.js:34:14)
nostream | at /app/node_modules/ramda/src/applySpec.js:81:14 {
nostream | code: 'ERR_INVALID_ARG_TYPE'
nostream | }
Not good, could you open a bug report on Nostream repo and we’ll take care of it
#[4]
Nvm big ticket was created
And what does the event you are sending look like?
Noice! Like likes but with money?
🧠💥