Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
ex. During the recent @TaiyoRobotics FUD (“what has Solport Tom done”), community members were quick to<br />
give their perspective. @SolportTom hosted a space to clarify some info, and it had immediate benefits<br />
seanytsunami.sol<br />
So @SolportTom hops on one twitter spaces and this is what happens? @TaiyoRobotics<br />
Community engagement: the need for engagement doesn’t stop post-mint. It takes consistency to solidify a<br />
project as a big player in the space. Pfp usage, tasteful raiding, and keeping up with news on discord are always<br />
beneficial for spreading the word. ex. @CetsOnCreck/@CetsCommunity made a name for themselves by being<br />
loud af, to the point where you would have to be sleeping under a rock to not know about them. They may even<br />
raid this tweet too.<br />
Matching the market: it is important that a project’s supply and price are reasonable given the context of the<br />
market. It is also an important consideration whether the project either uplifts or intentionally rejects (riskier)<br />
the market meta.<br />
This can understandably be hard to get right, given that the larger market is outside of a team’s control. This<br />
leads me to the next point...<br />
Flexibility. A team/community that can make pivots<br />
based on market conditions, metas, etc. will almost<br />
win over a project with rigidity. Managing expectations<br />
and not making promises too far in advance<br />
are good signs.<br />
Not all of the factors in the first figure are relevant to<br />
every project. However, I would expect a team to at<br />
least have thought about + considered these factors<br />
before launch. Hold upcoming projects accountable<br />
-- we can create a better space by asking tough<br />
questions.<br />
Thanks for reading. I hope you found something in<br />
here helpful. Do you agree? Disagree? Special S/O to<br />
@LitecoinYagami’s content army for the feedback .<br />
42<br />
<strong>SHILL</strong> <strong>Issue</strong> #<strong>64</strong>