SlothBuzz - A TWO YEAR journey so far! What's next? Have you say!

in SlothBuzz6 days ago

Good evening my buzzing beauties! What a buzz it's been! We've already been on HIVE for 2 whole years! It's crazy to think the little sloth community started in September 2022 and continues to buzz until now!

image.png

We had a bumpy start, to say the least, we joined Hive with high expectations. Upon launching our outpost/community/token we discovered we were releasing tokens far too quickly! We're sloths, the buzz shouldn't control us! After reining that in, we started working on building our community proper. Slothly but surely we grew in size and onboarded a few users who have helped support us over the years.

As it stands, we currently have over 2800 unique wallets holding some SLOTHBUZZ tokens! I'd say that is a success, considering our very low liquidity and minting rate! As it stands the token is holding a price of 0.75 Hive on Tribaldex. We're considering adding a liquidity pool in the near future also! However, the token price is not the main concern for us. We want to empower the users to maximise their time on Hive. Creating community and supporting small creators to flourish.


We had big plans, bringing the sloth community together in one place on Hive. Our dev had visions of creating a new platform, linking the best of Hive with our previous adventures. CryptoRadio.fm, streaming, merch stores and more! Things on this side took more of a sloth than buzz. As it turns out we've ended up going back to the 'basic' outpost provided by Hive-engine. This allows us to focus more on what matters, building a community of like-minded sloths!


Token info:

image.png
image.png

Circulating tokens: 14331

Tokens currently 'active': 13669 Burnt tokens (@null account): 662

Holders: 2811
Holders with at least 1 Slothbuzz STAKED (Allows use of !SLOTH tipbot): 320

82 Community subscribers

Current token use case:
Curation of 'SlothBuzz' tagged content.
Ability to use !SLOTH tipbot
Delegate to @lolz.sloth to earn LOLZ Defi tokens (lolz token holders can then earn via their defi platform)


The future?
image.png

We're again asking for your opinions!
Where should sloth.buzz go from here?

We have several options in mind and are always open to more suggestions from the community. Our current ideas include:

Add Hive-engine token drips on a daily/weekly basis for Token holders and/or Delegators.
Create Beeswap liquidity pool (Swap.Hive-Slothbuzz) with rewards.
Create a 'curation team' utilising Discord for ease of use and payment for curators.

Your opinions can help shape the future of Slothbuzz and hopefully your overall Hive experience!

Should we allow ALL holders to earn rewards or limit to the top 10/50/100/1000? If we reward users for delegating how much of the earning should we return? 10%/50%/100%? What other ways could we support users on Hive and build a strong token and community? Would you like to see slothbuzz collab with another project or token?

We're always looking for support from anyone who can share some buzz with the sloths! We'd love to hear from you, let's make slothbuzz work for you on Hive!

What would make you hodl or buy a token?
Why do you support other tokens on Hive?

Sort:  

Congratulations @slothbuzz! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)

<table><tr><td><img src="https://images.hive.blog/60x70/https://hivebuzz.me/@slothbuzz/upvotes.png?202411111934" /><td>You distributed more than 46000 upvotes.<br />Your next target is to reach 47000 upvotes. <p dir="auto"><sub><em>You can view your badges on <a href="https://hivebuzz.me/@slothbuzz" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">your board and compare yourself to others in the <a href="https://hivebuzz.me/ranking" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Ranking<br /> <sub><em>If you no longer want to receive notifications, reply to this comment with the word <code>STOP