More detailed info on #posh and #gosh

Many have been asking questions regarding #gosh after the announcement, airdrop and starting the distribution of them as can be tracked on @poshthreads. So I figured writing a new post with how things work both in a simple way and a more detailed way for those interested so I can link back to this for future reference.

POSH and GOSH simply explained

POSH

When you post a tweet that includes a link to a Hive front-end and you use the #hive tag, @poshtoken will automatically detect it then place a comment under the post you shared.

If you are registered on hiveposh.com the bot will know who the Twitter account belongs to on Hive which enables the comment aside from POSH to also earn liquid Hive rewards if someone other than the sharer upvotes it.

Depending on your tweet's performance that day, you compete against everyone else to earn a daily issuance of 250 POSH, the Hive rewards if someone upvotes the comment are a bonus.

POSH can however be traded for Hive (or swap.hive) on hive-engine.com.

POSH on Reddit does not require you to use any tags, it will pick up the link in any subreddit and drop a comment under the shared post. We do however block certain subreddits from earning POSH if they are too close to Hive as it defeats the purpose of getting visibility to our ecosystem there. (for instance the r/hivenetwork subreddit)

GOSH

Similar to POSH, you can earn GOSH by sharing Hive links in Leo Threads (and soon other Hive short form content dapps/front-ends).

Here you also compete against other users daily depending on how your thread performs, but here we don't count amount of votes or reblogs (compared to Twitter's likes and retweets) but instead look for engagement and amount of rewards of both LEO and Hive.

You don't have to be registered to link your Hive account on our website for GOSH as it's all onchain within our ecosystem already so we know which your account is.

POSH and GOSH more detailed explanation and thoughts surrounding it

POSH

While we attempt to make it as easy as possible for the user experience there's quite some complexity in the back-end to how POSH operates. I'll try to go through every aspect and explain whatever I can with my non-developer mind.

When you make a tweet that has a Hive front-end link that we've whitelisted in it and the #hive tag, our bot will fetch it and place a comment under the link you shared.

Whether you're registered and have linked your Hive and Twitter account on our website at this point the bot won't care, but it is in your best interest to do so because else it won't know who to send POSH or Hive to which instead get burned or and the Hive respectively sent to the DHF.

The @poshtoken account places a comment notifying the author that his post was shared on Twitter, if the sharer isn't registered it will not mention anyone, if they are it will mention who the sharer is by his Hive @username. If someone else shares the same post and they also are registered it will edit the comment with an embed to the new Twitter link as well and edit in the username of that sharer as well. This is to prevent @poshtoken to spam a post with too many comments.

The rewards of the comments are sent to an account that liquidates the rewards, instead of @poshtoken receiving 50% in Hivepower and 50% in Hive/HBD it will instead receive all of the rewards of the comments as Hive (it posts the comment as 100% power up with beneficiaries to @reward.app). This is to make the process simpler without needing to power down funds and send those out later to sharers earning Hive rewards. This process also takes no fee so the sharers receive all of the rewards, only reward.app takes a small 1% fee of the rewards for liquidating.

For the daily POSH distribution, it is split as followed:
50% go to delegators (250 tokens) and 50% go to sharers (225 to Twitter, 25 to Reddit) the latter can be adjusted based on activity. For the sharers, you can imagine it this way, it calculates all likes, retweets, engagement of all eligible POSH tweets that day, who they belong to and posts them every 24 hours distributing tokens based on those metrics. Say for instance the tweets with the minimum of likes/retweets would get 0.1 POSH while the tweet with the highest number of likes/retweets/engagement can get more, usually 5-6 as there's a lot of eligible POSH tweets that meet the minimum requirement. This of course leaves out a lot of tweets that don't meet the min. requirement meaning that on a daily basis there can be over 600 tweets that @poshtoken comments on posts with.

Then there's also some calculating behind each comment depending on how popular it is. I think this is better explained with an example:

Say user A and user B share my post on Twitter, @poshtoken drops a comment under my post with both tweets embedded. I give the comment a 1 liquid hive upvote after payout for simplicities sake. Now before the liquid hive rewards are sent to the sharers, it will check each tweet's score: likes, retweets, engagement and split the 1 Hive depending on who got more. If user A got 90 likes and user B only 10 likes user A will receive 0.9 Hive while user B gets the remaining 0.1 Hive.

This gets a bit more complicated if there's a self-vote on the comment, in the example above if user B has self-voted the comment as well his 0.1 Hive is instead sent to @hive.fund as we don't want people rewarding themselves with Hive from the reward pool for simply sharing content there, we'd rather see the author be in charge of that or other random curators. It's a bit similar as how constantly upvoting all your comments is frowned upon and we feel like being able to earn POSH should be the main focus rather than attempting to maximize Hive earnings with our service.

To avoid abuse we have a way to ban users from earning POSH & Hive, this means you'll still have your verified Twitter verification badge but won't be able to receive the benefits that come with POSH'ing and your potential rewards will instead be burnt. You can always appeal to be removed from the banlist after a while of course. We also have ways to prevent certain tweets from earning POSH & Hive as payouts of comments happen 7 days later and the POSH rewards are also sent first after 7 days: https://he.dtools.dev/@poshtoken?symbol=POSH this gives us some time to overview the daily reports of earnings to make sure no shadiness has occurred. The addition of being able to ban certain tweets was after bots such as Hey Wallet and Chaintip or whatever it's called became popular as they're infested by bots that bring close to no real value to the links and our ecosystem and users can cheaply fake a lot of Twitter likes/retweets/engagement which meant they'd earn a lot of POSH which only takes away value from the reward-pool and other sharers.

Okay so some thoughts regarding all this now.

Used well, POSH can be quite a powerful tool not just to incentivize sharing of content which in and of itself is quite unique but also makes it transparent. Sharing content from our ecosystem has been something not many have actively indulged in for years on this chain even though for many stakeholders that has felt like one of the few ways the content may deserve the rewards from inflation it is getting. Striving for genuine engagement and banning fake ones also means that the word of Hive is kept in good standings on #web2, as we know crypto is quite full of scams and rugpulls where more normies just like to bundle them all as "just scams". While we can't stop some people from using bots and fake engagement on their Hive link shares, we can at least not reward it.

It can also work as marketing tool for the authors themselves, when holding a significant amount of Hive Power and voting up the @poshtoken comment it generates an mini-reward pool for others to partake in to share the post by that author to earn some of the pending Hive rewards. Authors can this way get potentially more views to their posts while it also gives a further usecase to holding Hive power to be used this way.

Sharers can also share older posts that have already paid out, as long as you haven't shared it before then @poshtoken will work on it.

Another thing many don't think about is that for front-ends with potential adrevenue in the future this could mean that POSH is able to increase it. Take @leofinance for instance which is one of the only ones I know of that uses adrevenue on their main website. POSH activity may lead to it earning more revenue which goes back into buying LEO so which all holders benefit from. In the future we will hopefully have more front-ends do the same and share the adrevenue either with the authors, sharers or HP holders or a mix of them all.

GOSH

For GOSH it's quite similar except that instead of likes/retweets/engagement we focus mostly on engagement of threads and amount of hive and leo rewards they receive. This may be fine-tuned and adjusted over time.

One of the next steps for GOSH will be to also implement @dbuzz to enable #gosh rewards for sharing links in!

---

I wanted to talk a bit more about tokenomics, some changes we'd want to implement in the near future and other plans we have for both POSH and GOSH but I think this post got quite long already so I'll save it for another day.

We'd gladly hear your thoughts surrounding it, since POSH and GOSH is a community-funded project we're open to ideas on how to improve it. Big thanks to @rishi556 and @hivetrending for having more time to spend on the POSH project as devs lately who've done a great job at evolving and maintaining it. Make sure to vote for their witnesses if you value their contributions!

Thanks for reading and the excitement surrounding the project!

Posted Using LeoFinance ^Beta