Subnostr

Based on cursory glance of https://github.com/retrnull/garnet and review of kind 1814 notes and kind 0 profile of common 1814 testers...

In kind 0, adding a field for `cryptocurrency_addresses` where there value is an object whose fields are cryptocurrency types (e.g. `bitcoin`, `monero`, `arrr`) and value is a corresponding address for that type.

nostr:npub1wamvxt2tr50ghu4fdw47ksadnt0p277nv0vfhplmv0n0z3243zyq26u3l2

nostr:npub1j29xk9mnfzcp9twyu0f20zjzk72603a23ax94led2xvxz4sjd99qssssdj

nostr:npub1e6ejh5glnaj4at3l4ggqjs7pp082qj24rklg0uvmmzsly33rqe9s8umxgr

nostr:npub1skkpnkc4vfe586ul425nd7s4a4qqm6nnacr8j52k72tmguyhgltqk8t32y

nostr:npub153pgcxexl4pn0j906t725uj5jkn9hxzemcg635jd60nwzmmysa7q6qgmfn

I would recommend that the cryptocurrency type be the common ticker symbols vs english names to avoid some degree of ambiguity, or even use the coin type numbers from https://github.com/satoshilabs/slips/blob/master/slip-0044.md if restructured into array format.

For example, in kind 0, instead of this for "cryptocurrency_addresses"...

```

{"monero":"55fSXyCcqkdikrxogPb16UKN3SYhkpyH32Ge6ECkAk3PhrBbXEaNcNf3o82q6vEcaR6Hp1YWdDDA6BqUJW1FL3P5Jvo5TyD"}

```

consider...

```

{"XMR": 1"55fSXyCcqkdikrxogPb16UKN3SYhkpyH32Ge6ECkAk3PhrBbXEaNcNf3o82q6vEcaR6Hp1YWdDDA6BqUJW1FL3P5Jvo5TyD"}

```

or...

```

[[128,"55fSXyCcqkdikrxogPb16UKN3SYhkpyH32Ge6ECkAk3PhrBbXEaNcNf3o82q6vEcaR6Hp1YWdDDA6BqUJW1FL3P5Jvo5TyD"]]

```

And maybe the kind 1814 should reference the given ticker or coin type as well for correlation to expedite verification

There's no NIPs referencing kind 1814 as far as I can tell, nor pull requests in the nostr-protocol/nips repo. Strongly encourage writing a specification for this to allow for wider adoption.

🇵🇸 whoever loves Digit 1y ago

Hey nostr:npub1yx6pjypd4r7qh2gysjhvjd9l2km6hnm4amdnjyjw3467fy05rf0qfp7kza

You want to type up a cryptocurrency_addresses NIP? I have no idea how to submit it to the official NIP repository but I'll give you a small 0.25XMR if you write one that meets these criteria:

* Let the user add anything they want as a wallet address in their profile, with any unicode name for the associated cryptocurrency

* Make it optional to include fully integrated tipping with broadcasting to relays

* Optionally let the user easily edit a unicode wordlist for cryptocurrencies that their client will have a non-relay-integrated tip button for (the tip button can't magically have fully integrated tipping with every possible crypto, it can just show associated addresses for the user to copy and paste - maybe QR codes)

* Include a default set of recognized cryptocurrencies based on both their common names and their ticker symbols, make sure dogecoin is included

* Other than that just base it on how Garnet works; tips can optionally be broadcast to nodes, wallet addresses added in kind 0 show up visibly on profiles, etc. (make sure Garnet's existing implementation is considered at least partly compliant by the standard of your NIP)

I'm good at writing or listing bullet points like the above but I think you have more technical knowledge than me. Garnet needs a well-drafted NIP for Monero tipping to be taken more seriously by the nostr oligarchs

Reply to this note

Please Login to reply.

Discussion

No replies yet.