Started sketching out an NFT-focused client. Prob gonna trigger many people 😂

Reply to this note

Please Login to reply.

Discussion

I think like you say this will be a good step to get some “crypto bros” in the space, once they’re here they will see how nice all us bitcoin people are and hopefully be orange pilled🤣🤣🤣🤣

That’s the plan. Inside every crypto bro is a bitcoiner waiting to wake up.

🙌🏻🙌🏻🙌🏻

#triggered

we don’t need a client fork with nft’s

we need to build a culture where where the #bitcoin tag is filled with substantive posts from people like

#[3]

#[4]

#[5]

#[6]

Instead of just shallow expressions of loving bitcoin when being here and zapping says that better than any proes could

I meant to include #[3]

Disagree.

I do think taking charge, by making a client that is nft friendly but still primarily implement the same nip 57 zaps for interoperability might help on board those who are heavily invested in nft... But been digging through scuttlebutt and It seems as if there is a demographic who doesn't care about nft but just has a diversified portfolio of crypto, who would happily use nostr as is if not as they describe “every 5 posts is just ‘stack sats’.

Accommodate both. Zaps included. Right now my understanding is that nft collectors use other apps to browse things but talk outsider those apps. Nostr is great as it can bridge both functions and introduce payments like zaps.

I dont think going after any audience is a bad idea... And building it from the inside secures zaps and better interoperability. I'm just not sure if the scuttlebutt guys (or just anyone with just a slightly diverse coinbase account) wants to join nft centric relays for the same reason

Make their own relays? 🤷‍♂️

of course. Their influencers/devs will be the last or what they build will be larry levels of hostile, but if we build it their users might come.

Better we grow this network and make it less appealing to switch later as they fork their own.

will you include support for STAMPS the unprunable bitcoin nfts being stored in the UTXO set on every node?