Brian Flynn
@flynn.eth
If you're a mini app dev that hasn't launched a token yet, would love to hear why you haven't done so yet. Here are the most common answers I hear: A. Operational burden of not knowing what it's for/how it will be used B. Uncomfortable with legal risk C. Not wanting to be distracted from What else?
19 replies
2 recasts
37 reactions
Samuel ツ
@samuellhuber.eth
All of the above + it’s a one way door. Can’t take a token back. Makes it hard to pivot / fail unless you just accept potential financial damage of folks as mental thing to deal with
2 replies
0 recast
16 reactions
Samuel ツ
@samuellhuber.eth
Cc @0xsid we talked about this today
1 reply
0 recast
2 reactions
🎀 sonya (in theory) 🐰
@sonyasupposedly
discussed this with @toadyhawk.eth recently and he talked about the pressures introduced by a token, similar to what you said above: "BETR is the first time I've ever built an app. It's the first time I've ever had a token associated with something I'm building as well. And it's fun and exhilarating, but it can also be really stressful because it's like, oh, what if what if this doesn't work? Like, it's working now, but what if it doesn't work anymore in six months? Are people going to think you're a rugger if you decide that it's not working anymore? It's not something I spend a lot of time thinking about, because you just don't have time to think about that when you're trying to get traction for something. But, it does creep into my mind sometimes. It's tough to be a builder in the space."
1 reply
0 recast
1 reaction
