Darkblock's Bold Idea - Allowing Third Parties to Attach Content to Any NFT
Darkblock has been making waves in the world of NFTs by allowing creators to attach multimedia content to their tokens, even after minting has occurred. However, the Darkblock team is now considering an even bolder idea: enabling anyone, not just the NFT's creator or owner, to attach content to an NFT.
Let's take a closer look!
Why Allow Third Parties to Attach Content to NFTs?
Enabling third parties to attach content to NFTs opens up a myriad of new possibilities for the NFT space according to Darkblock. For instance:
Profile picture (PFP) owners could attach their character's backstory or lore to their NFT.
Concert attendees could attach personal photos to their NFT tickets.
DJs could attach their remixes to music NFTs.
Darkblock believes that these and other use cases have genuine value for partners. But, since Darkblock is a protocol, it's impossible to limit the functionality to specific users, so certain challenges need to be addressed to ensure a positive experience for creators and NFT holders.
Darkblock's primary goal is to empower creators and ensure that user-generated content (UGC) doesn't negatively impact the NFT experience. To achieve this, the team mentioned on Twitter that they would take the following steps:
Hide UGC by default in any Darkblock viewer delivered via the NPM (i.e., on websites that integrate the Viewer).
Clearly separate/label UGC from creator content within the Darkblock.
Give creators the power to show or hide any content.
Exploring the Possibility and Seeking Feedback
While the Darkblock team is excited about the idea of third-party content attachments, they are also aware of the potential challenges and are seeking feedback from creators, community members, and the wider NFT space.
Darkblock hosted a Twitter Space to talk with the community about the idea. Chris Seline, CEO of Darkblock, also joined in on the discussions.
We shouldn’t disallow anything - Chris Seline
He goes on to say that you could hide anything you wanted though.
Just because it’s attached, doesn’t mean it has to be surfaced in any way - Chris Seline
Members of the community (specifically Cryptoversal Books) talked about the potential of third parties sending malicious content to users’ NFTs, like viruses. Chris Seline's talked about a way around that that could involve only allowing files to be shared that cannot potentially be malicious but recognises that that is a valid point that would need to be addressed adequately.
What are your thoughts? Can this concept be tamed? Or will it bring with it a runaway domino effect of issues later down the line?
Hear the full discussion here, and share your thoughts with the team on Discord.
How to name Darkblock books
On a side note, the team also discussed what they should name NFT Books that use the Darkblock protocol to encrypt content in order to differentiate them from NFT Books that are unprotected or use token-gating to provide access. The options posted on Twitter by Whit (@cryptomachia) were:
Darkblock Book
Tokenbook by Darkblock
dbBook
dBook
(dBook received the most votes)
