Chapter 1: Understanding Doxing in Web3

In my previous editorial, I was reminded of a peculiar statement I encountered on Twitter. A developer, who seemed to lean towards a more progressive viewpoint, claimed that doxing was a privilege. This perspective appeared quite strange, suggesting that NFT teams should consider hiring anonymous developers—particularly web3 developers whose identities remain largely unknown, aside from perhaps a Twitter or Discord handle.

While there may be rare scenarios where someone could argue that revealing one's identity is a privilege—such as a developer living in a country where cryptocurrency is illegal and facing jail time for being doxxed—this is an exception rather than the norm. I’m open to hearing different viewpoints, but to me, this stance feels misguided.

At the end of the day, the established principles from web2 and earlier eras should still apply when hiring web3 developers. Picture this: applying for a tech position at a major company like Facebook or Apple. If they request your ID for HR and tax purposes, and you respond, “I prefer to remain anonymous for legitimate reasons, so please pay me in crypto instead,” you can imagine their reaction. In California vernacular, that’s a hard pass.

For web3, I believe hiring standards should be even stricter. The risks and potential liabilities are significantly greater. Doxing isn’t a privilege; it’s a responsibility that every developer should bear. Moreover, web3 developers should receive appropriate compensation—not just for revealing their identities, but also for their exceptional qualifications and the high-stakes nature of their work, often involving significant amounts of cryptocurrency.

I tend to exercise caution when addressing NFT teams that seem oblivious to the importance of doxed web3 developers, often undervaluing them as a result. A quick anecdote: I once interacted with a representative of a Hollywood celebrity who was dissatisfied with my fees. Instead of negotiating, he opted for a cheaper alternative, only to later ask if I could review the work produced by that less expensive developer. Naturally, I declined.

Reflecting on the early days of the web3 space—about a year ago—it was incredibly challenging to find doxed developers willing to work. I often explored tech Discords, encountering anonymous individuals from unknown locations eager to help, on the condition that their identities remained concealed. I found this situation untenable, as my professional background was not in clandestine operations.

Fast forward a year, and the landscape has shifted. Anonymity among developers has become less common, although the initial struggle to find qualified individuals persisted. Gradually, web3 developers are becoming more accessible. For NFT teams, it’s crucial to remember some fundamental truths about the high-stakes environment of this space.

Don’t let anyone mislead you into thinking they have valid reasons for remaining anonymous on your NFT team. While it’s understandable in some cases, the reality is that you need skilled individuals whose identities you can verify. Period. And yes, they should be compensated fairly for their contributions.

Ultimately, this is just my perspective, and you’ll make your own choices.

Jim Dee is a prolific writer, developer, and multimedia creator based in Portland. For more about him, his businesses, and his publications, visit JPD3.com. Thank you for reading!

Chapter 2: The Importance of Transparency