Five on Nostr: Some steps and considerations 1. Read spec on github carefully 2. Check how ndk wraps ...
Some steps and considerations
1. Read spec on github carefully
2. Check how ndk wraps events eg highlights [like this](https://github.com/nostr-dev-kit/ndk/blob/4351ec435f56b1d97621ed8ed7f1c742f9b0c0b3/ndk/src/events/kinds/highlight.ts#L13)
3. See calle 👁️⚡👁️ (nprofile…h5zr) 's [contribution](https://gist.github.com/callebtc/0ed77c137809c7fc7627fe8fd4e9f163) . It contains most of the logic you need to adapt to ndk nicely:
1. Include related kinds into NDKKind
2. I would put 'nip17.ts' file with logic in src/events folder
3. Also see logic in nip04.ts it shows how params should be passed and handled. Take more pubkeys as recipients like in the spec
4. Estimate the time it would take to do this and worth of your time
5. Create offer on my ticket in SatShoot
6. I assess your price and if I accept let's Rock and Roll!
1. Read spec on github carefully
2. Check how ndk wraps events eg highlights [like this](https://github.com/nostr-dev-kit/ndk/blob/4351ec435f56b1d97621ed8ed7f1c742f9b0c0b3/ndk/src/events/kinds/highlight.ts#L13)
3. See calle 👁️⚡👁️ (nprofile…h5zr) 's [contribution](https://gist.github.com/callebtc/0ed77c137809c7fc7627fe8fd4e9f163) . It contains most of the logic you need to adapt to ndk nicely:
1. Include related kinds into NDKKind
2. I would put 'nip17.ts' file with logic in src/events folder
3. Also see logic in nip04.ts it shows how params should be passed and handled. Take more pubkeys as recipients like in the spec
4. Estimate the time it would take to do this and worth of your time
5. Create offer on my ticket in SatShoot
6. I assess your price and if I accept let's Rock and Roll!