DeFi Users: How do you establish trust in a new protocol/platform?

Discussion

Quick background: I'm a dev trying to build and launch a new Ethereum-based decentralized exchange. Think along the lines of Uniswap, Sushi or Bancor. I really believe that the product will offer some truly new technology that will add value to the users. But my conundrum is building enough trust with the DeFi community, where early users will feel confident to trust their hard earned money.

That's why I'd like to hear from you. The subreddit here is filled with a lot of bright, knowledgeable people, who are often on the cutting edge of DeFi. Your perspective would be super valuable for our team. What are the major things you look for in a new DeFi protocol before you trust it with your money? And how do you approach the problem of deciding to trust something new? Are there common red flags that you look out for? Vice versa, are there things a project can do that will get your attention and trust?

Do you care about audits? If so, are there certain auditors that you trust more than others? (This is a big one for us, as we've found certain audit companies are significantly more expensive than other.) Do bug bounty programs matter to you? If so, is there a certain minimum size in the pot that you prefer to see?

How about the dev team personally? Are there things they can do to help build trust? Dox themselves? Have big name investors? Be active on social media?

Are there certain tools or third party evaluation sites that you rely on? I'd like to hear and all that you use. (I know rugdoc.io is often popular, and we're already trying to work with them.)

Is there a certain threshold of TVL that you like to see on the platform first? Will you be more likely to try a new project if there’s say $10 million TVL instead of $100k?

The above are just discussion points. Please respond with anything and everything that you use to establish trust. Even if you think it’s weird, it always amazes how many ingenious off-the-wall solutions exist in this space. (Tangentially, I’d love to hear any general advice anyone has I’m general about building an early user base.)

I genuinely think we’re building a good project that can potentially add a lot of value to the ecosystem. But to do so, we can’t just launch and have no one show up. We’re engineers, not marketers, so any feedback you can offer is super helpful and illuminating. Thanks I’m advance for all the great responses.

Posted Aug 9, 2021, 9:45 PM UTC

1718
AWholeCoin•

Probably the best thing you can do is have a comprehensive white paper that really gets specific about your technology.

11
CPlusPlusDeveloperOP•

Great point about the white paper. Up until now, it's something that we've neglected. We've been so busy building the code, and the engineering team has the mental model in their head. But you are absolutely right, great white paper and docs is critical to communicating trust. Thanks!

3

Network effects, assuming smarter ppl than myself have read the code and there is sufficient funds locked up to join in the fun.

The test net versions help to some degree for users to familiarise themselves with UX.

9
african_gogeta•

Great question. I’m far more cautious than the average degen btw so for me what’s important is:

  • understanding if the project is truly introducing something novel that should be a stand-alone product or just another feature an existing project should add. Your whitepaper can solve this, it should call this out as well.
  • seeing how active the founders are in the community, how they respond to tough questions, etc
  • understanding how much the TVL is spread amongst users, is it just one whale propping the whole thing up or are there a few other users. Integration with something like Dune analytics to see custom metrics is great
  • Fees are a big one, I’m not a whale so is it on an L2 ?.
  • who is behind the team? Are they super smart? Having listened to plenty of interviews of Stani, I felt more trust in Aave.
  • is there a bug bounty program? No idea on size
  • has someone like Chris blec written a piece on the protocol? Seems like a trustworthy guy IMO
  • how long has the projected been on testnet? A short testnet period isn’t great to me
  • if launching a DEX, what’s capital efficiency like? How does it compare to UniSwap v3?
  • is there a treasury or insurance to potentially protect users if it’s hacked

These are just some I could think of off the top of my head. Hope it helps

6
CPlusPlusDeveloperOP•

Great general list. I hope you don't mind if I forward this unedited to the rest of the team tomorrow morning. Also great specific pointers, this is the first time I've heard of Dune analytics. Looks like a great tool.

Won't go too deep into the product, because we don't really have much out there yet. And I just wanted to keep this thread on the overall question, so it can hopefully be a general resource for dev teams in the future...

But I can say that CrocSwap will have a similar concentrated liquidity model to Uniswap V3, but actually deliver better capital efficiency. Plus, unlike Uniswap, we plan to be multi-chain on all the major L2s. Our socials are empty at the moment, but anyone who's interested can follow @CrocSwap or subscribe to r/CrocSwap.

2
african_gogeta•

No worries, please do.

Definitely intrigued, will keep a close eye the project, good luck!

1
neededafilter•

Pretty awesome list. May I ask which protocols you use and trust/ones that passed your smell test?

1
african_gogeta•

I don’t use a lot of DEXs but Aave on polygon, Element finance, Curve on polygon, UniSwap when gwei is low, Yearn, loopring are a few I use which passed the test,

2
neededafilter•

Thanks. I used to use Yearn but they apys have crashed to the point its not worth the risk of playing in defi. I switched over to Convex which has been great but you have to claim and restake or convert to stables on your own and pay your own gas

1
[deleted]•

[removed]

1
Adventure_Mouse•

Team. Who you have as core team + their history of projects / status in community, etc.

Audits, sure.

Your own team's money at risk in the project (as first loss during a hack, etc.) goes a long way also.

As others said, network effect, sure, but the above can be done before masses join you, and allows for early adopters that turn into mass user base.

4
CPlusPlusDeveloperOP•

Your own team's money at risk in the project (as first loss during a hack, etc.) goes a long way also.

Thanks for bringing this up. We never even really thought of this. But I think it's a great idea, and definitely makes sure that incentives are aligned and the team has "skin in the game".

1

Network effects, assuming smarter ppl than myself have read the code and there is sufficient funds locked up to join in the fun.

The test net versions help to some degree for users to familiarise themselves with UX.

3
webs7er•

As someone who recently decided to experiment with a new DeFi protocol, I think some important things that helped gain my trust were (in no particular order):

  • having a really clear and concise description of the product (purpose and structure) and its tokenomics
  • information on where the idea came from and some backstory to the project
  • trustworthy sources that show audits performed
  • links to social profiles of the developers

Additionaly, having some sort of rewards for early participation in the project, ideally with a low entrance barrier (think: liquidity mining), would go a long way to having new people jump onboard.

Edit: Since I'm no expert, the name of the audit company doesn't really tell me much. As long as they look reputable, I'm willing to trust their reports.

3
CPlusPlusDeveloperOP•

Thanks! That paints a really good picture. Up until this point, we've been so focused on the tech, that we've neglected the side of communicating our story. But you're absolutely right. Early on, people don't have the bandwidth to deep dive into all the nuances of the tech. So, you need to create a compelling and honest narrative that communicates all of that in an easy to convey package.

2
spinz808•

Rug Doc

2
Stobie•

Initially before there is a lot of usage audits matter more and everything must be open source/verified on etherscan. Auditor matters a lot, if you use peckshield I'd just forget your project. good bug bounty can be just as good.

2
CPlusPlusDeveloperOP•

Haha, yeah I can see that regarding Peckshield. Out of curiosity, what's your opinion on Certik? We reached out to a lot of the really top-tier names: Trail of Bits, Consensus, OpenZeppelin, etc. Most of them are booked up for six months or more, or not even taking clients.

So I'd be really interested in hearing about which names you trust, since we have to pull the trigger on audit strategy pretty soon. Thanks!

1