The following will replace the current Leaderboard design. Our goal with the new design is to adopt HAFSQL and build a better database along with a Points system.
This Points system will be a far superior way to rank-ordering users on the Leaderboard. Expect that we'll start to use the Daily/Monthly/All-Time Leaderboard stats to give out grants/delegations/prizes (in a similar manner to how we conduct LPUD).
The Points system can be tweaked over time as we gather data on how people are performing. Generally, this can add a deep-level of gamification to the interface.
I (Khal) have also long-said that I would love to replace the Reputation Score system on the Interface with a completely new "Engagement Score". I imagine that something related to this points system would be possible and would allow us to then use the API for that purpose and many others. Potentially even open-sourcing that API for other Hive UIs to tap into as well.
Generally a clean design with a focus on the top 3 users based on points. The "Today, Monthly, All-Time" categories will be toggled at the top.
Share Button
A share button in the top right will let you share a screenshot of the current standings into a Thread (automatically screenshotting it and then publishing it as a thread where you can add more text).
List
Scrolling down will show you the rest of the leaderboard. Likely showing the top 100 and then a "View All" button to load the rest.
Tap to Expand a User
If you tap on a user's username, then it will expand their "User Card" and show you the subcategories of how they earned their points.
Imagine tapping a user's icon and seeing a breakdown of:
To get people familiar with LeoDex both on the Maya Protocol side and on the Hive/LEO side. We want more users of LeoDex on a regular basis. The Airdrop is like a "opening day sale" at a retail store that is meant to encourage people to look around the aisles and see what we have to offer the world.
Hopefully, they find that we've built an amazing product and decide to use it both for the airdrop and into the future. Learning about the LEO token economy and the flywheel effects of growing LeoDex's Trading Volume
UI will track the logged-in user's trading activity on LeoDex (their total volume of $$ traded on LeoDex.io)
It will have a fixed calculation based on that trading volume - the higher the trading volume, the more LEO they will earn for the airdrop (for example, 1 LEO for every $1 traded on LeoDex) (example calc, the real calc will be some other number)
Example:
So for example, in the address I'm logged in with - I may have traded $12,600 on LeoDex.
So my number would be $12,600 on the UI display.
You can add 10 tiers. To reach the next tier, you have to swap above a certain amount of $$
Tiers:
We can have 10 tiers. To reach the next tier, you have to swap above a certain amount of $$.
$0/$500
$501/$2500
$2501/$5000
$5001/$10000
$10001/$25000
and so on ... up to 10
The higher your tier, the bigger your airdrop. This encourages users to swap more and more to reach the next tier and gamifies the process by displaying their tiers on the frontend in real-time.
Since the goal of this Volume Drop is to spur activity and awareness around LeoDex and the LEO Token Economy, we should also include an element of "LP Requirements" in order to be eligible for this Volume Drop. The target audience is primarily people who have not yet interacted with the LEO Token Economy or her ecosystem of products.
We will likely introduce an LP Requirement to the tiers. I imagine this could be done in either of two ways:
Each tier will have a corresponding Pooling Requirement to reach the next tier (i.e. $100 LP position alongside the $500 in swap volume for Tier 1... $250 LP Requirement + $501-$2500 swapped for Tier 2, etc.)
Alternatively, we could have a blanket LP amount that is simply an eligibility requirement for the entire drop and is not tier-dependent. This would reduce overall complexity (i.e. must have $500 in the LEO-CACAO LP, then reach the tiers based on swap volume alone).
note: we will have some stipulation that the LP must be symmetric LEO:CACAO OR be asym on the CACAO side).
TBD (optional) bonus for creating an account on INLEO - this may require some additional verification, which adds another layer of complexity but would create a lot of value for the overall LEO Ecosystem
Since the amount of LEO for the airdrop will come from the ecosystem, I believe a LEO POWER stakeholder vote should take place. It should be adequately emphasized that the potential value capture of a successful LeoDex product will be incredibly high for the LEO Token Economy.
I also believe the LEO Team could match the airdrop amount by purchasing LEO off the open market. So if the ending airdrop amount determined by a stake-weighted community vote is 100k LEO, then perhaps the LEO team should also buy 100k LEO off the open market and donate it to the Volume-based airdrop to make the total 200k and also negate any negative sentiment around the potential downside of unlocking 100k LEO from the ecosystem and airdropping it to new users of LeoDex.
The frontend for the volume airdrop will show on the Dynamic Island module. It will be a tier based airdrop and show your real-time tiers as you progress through the airdrop.
Example:
To make the Volume Airdrop display module, we need a backend to keep track of who's swapping and how much they are swapping (based on their Arbitrum / Maya Protocol wallet address).
This backend will go live at the same time as the Volume Airdrop display on the LeoDex.io interface.
In the process of building this backend, I realized that there are many other use cases available for it. In the future, we'll be able to expand more layers on top of this backend and it will allow for more features that are data-centric.
The 1st example of such a feature in my mind is trade history - if you are familiar with using popular CEXes (i.e. Binance), then you'll know that they have a Trade History tab. On this tab, you can see all your trades that you've ever made with that account. You can also export that history as a CSV file.
This is incredibly useful for analysis and many other reasons. Users often want to download their data and be able to use it.
Other potential features are a dashboard where users can see global trading metrics on LeoDex/Maya Protocol as well as deep analysis on their own account (wallet) that they are signed in with.
For example, seeing the total $ value of all the trades they've ever made... what assets they trade the most... what assets are traded on LeoDex most frequently...
We also could have features that show real-time swaps happening. I imagine this like a Shopify store - have you ever been to a digital storefront where they have those little message pop-ups in the bottom right? For example "sally bought 1x pair of Nike shorts for $39"... imagine that but for swaps. As other users swap / pool liquidity, you could see global messages.
The goal of this would be to encourage more activity in general. More activity on LeoDex = more Affiliate Revenue = more $LEO getting bought and deployed as permanent liquidity.
The emissions for LEO are 0.208 LEO/block and decrease over the next ~32 years. Block rewards stop when LEO reaches 50M tokens in circulation.
System Income (LeoAds, LeoPremium, LeoDex, LeoBridge Oracles and
LeoSubscriptions) are designed to replace this inflationary pool over time. As of right now, the System Income buys LEO and deploys it as permanent liquidity in various liquidity pools on DEXes (as of April 2024, this is deploying entirely into two pools: LEO-CACAO on Maya Protocol and LEO-HIVE on the Hive Blockchain).
Starting in 2033 (when inflation drops below 4%), the System Income will buy LEO and deploy it into the SIRP (System Income Rewards Pool).
This pool will continually grow in terms of rewards vs. the inflationary rewards pool. Starting in 2033 and until 2056, the LEO Inflationary Rewards pool will continue to drop in signficance as inflation drops and SIRP's share in the rewards allocated to users increases. By 2056, the inflationary pool will be 0% (as all LEO - 50M Tokens - is in circulation) and the rewards from the SIRP will be 100% of what is paid to users and active LEO POWER stakeholders on the platform.
Until 2033 (9 years), all System Income will buy LEO off the market and deploy it as permanent liquidity in DeFi LPs for the LEO Token. Right now (June 2024 as of this writing), this is LEO-CACAO and LEO-HIVE.
Why these two pools? Because of the Hive Aggregation Technology that drives revenue into the LEO Token Economy (more system income through affiliate fees + LeoBridging fees). As these 2 pools grow, the $ volume per month that can be transacted on HAT will increase. More $ volume = more system income = more deployed as permanent liquidity (a flywheel for the LEO Token Economy).
In the year 2033, the LEO Inflation rate will drop to 4% per year. At this time, the SIRP contract will be launched. Once SIRP is launched, the system income will no longer buy LEO off the open market and deploy it as permanent liquidity.
Instead, the SIRP contract will use system income to buy LEO off the open market and deploy it into the SIRP. The SIRP pays content creators and curators on the platform. As described above, from 2033 - 2056, the share of SIRP's payouts relative to the inflationary rewards pool will increase (as the System Income increases overtime and the inflation continues to drop Y-o-Y).
In the meantime (until 2033), the LEO community and team should aim to grow System Income as much as possible. This is a decade-long opportunity to deploy permanent liquidity into DeFi protocols. That liquidity will never leave the designated pools which means that as the LEO Token Economy grows, the $ value depth of those pools will continuously grow up and to the right.
Liquidity is important for any asset but it is even more so important for the LEO Token. Why? Because a large % of current and potential System Income is derived from trading and bridging the LEO Token. As mentioned above - LeoDex Affiliate Fees and Hive Aggregated swaps all run through the LEO Token Economy. Deeper pool depth = more volume = more system income = more permanent liquidity deployed.
Goal: grow the INLEO platform by creating deeply entrenched incentives that turn the existing community into an army of marketers.
Incentives can dramatically shift sentiment. As of this writing, INLEO has
~1,400 Monthly Active Users. If this userbase were able to leverage simple affiliate tracking links/codes to onboard new users and earn clearly defined incentives now and into the future, they would turn into an unstoppable force of marketers.
1,400 people working toward the common goal of onboarding as many new users as possible.
When a user arrives on INLEO Threads, if they are served the Latest feed first, it is a randomized experience. We don't know what time of day the user is coming in at. We don't know the activity of other users at that time. The latest feed is not an efficient way to provide high quality user minutes off the bat.
If users aren't given high quality minutes right away, they are likely to leave and possibly never return. Expecting that Threads / INLEO have low quality content.
What is a high quality user minute? A minute where the user is looking at the feed and finding interesting things that catch their attention and lead to them spending more minutes on the platform.
The current implementation of the For You Feed on Threads uses an algorithm to determine what content to serve to users. The current algorithm is listed below. We'll continue to tweak this algo until it serves better content. In the long-run, LeoAI should serve as a viable replacement or enhancement to the algorithm with the goal of serving users relevant content.
The For You Feed should be the default feed that all users see (unless the user otherwise changes their default feed via the settings page). Existing users are accustomed to the Latest feed. I believe we can change this culture through a superior For You feed. It is undeniable that the majority of X users utilize "For You" along with pretty much every other social media platform. The For You feed is the future, the critical question is how do we create a better content serving environment.
Authors You Follow - Threads created by an author you follow and has 1 comment and 1 vote
Reply Authors - Show Threads from any Authors who have replied to you or you replied to author in the past 12 hours
For example - if I replied to one of @taskmaster4450le's Threads yesterday and then go to my For You feed today, his Threads show up in my For You
Tagged
Show threads where the logged-in user was tagged (I know that these also go to the notifications tab, but I think it'd be nice to see them in the For You feed as well)
Reply Threads
Author is in follow feed AND thread has more than 3 votes or more than 3 comments
Show threads from hashtags that the logged-in user has engaged with in the past 24 hours. For example, if I replied to a thread that had #hive in it, then show me some threads in my feed that contain #hive
(let me know if this is possible @Deniz)
Top 5 most viewed threads in the past 12 hours
Take the top 5 most viewed threads (using our simple analytics API) and mix them into the feed
X recently implemented this - beneath every Tweet that you open, there are now 3-5 "Recommended Tweets". These Tweets are usually quite relevant and are based on the Tweet you're currently reading.
A similar recommendation feature would create more positive user minutes IF it serves the user Threads that they are likely to click and read based on the current thread they clicked and are reading.
I believe we can implement a recommendation engine that works on the following parameters to rank-order a list of 3-5 recommended Threads beneath the current thread you're on:
Threads containing 3 or more of the same keywords as the current thread you're on
INLEO technically has 8 feeds for article content (the 4 above with a toggle to sort from INLEO.io only content and all Hive content).
A For You Feed that is similar to the one used on Threads should be implemented for Blog Posts. The idea is to give users highly relevant long-form content based on their account and their on-chain activities... creating more positive user minutes on long-form the same way we do on Threads.
Recommendations should also be added beneath blog posts. When you get to the end of a blog post, 3-5 more blog posts should be recommended to our user. Again, the same algo that we use for Threads Recommendations can be repurposed here.
As it stands, there is a lack of high quality, fast and accurate news on INLEO Threads.
This is not to say that there is none of this happening, but there is a definite lack of quality news.
For Threads to grow as a high-quality news outlet that spurs engagement around highly relevant topics, we need to feed the feed with more high quality news.
The new feature would move News2Threads off Discord and onto INLEO Directly. This would coincide nicely with some other features we are working on via slash commands (i.e. /command).
We're adding slash commands for Premium INLEO Users. This will allow this group of users to call on various commands that are built into the UI.
For example "/news2threads [insert-article-link]" could be used by premium users who want to share articles on INLEO as summarized threads + the article link.
I believe putting this on the UI in this way will have two major impacts:
New feature that adds value to being Premium
More News2Threads activity out of convenience and ease of use
Suggestion: could news threads get a colour coded edge or box ? That way we can immediately see them (as long as not too many other colour codes are used).
Right now, News2Threads is a Discord bot where a certain group of INLEO Lions have access to share article links and then have them auto-published on
Threads as a 3 thread-summary of the article + a link to the original story.
I believe this is a fantastic way to share high-quality news on Threads. It allows users to get concise summaries of top news stories without even leaving INLEO. If they are interested in diving deeper on any story they've seen, the link is provided in the last thread.
Polymarket has seen incredible success. INLEO is a social platform with built-in monetization features. This means we could also have a prediction market where people can vote using liquid LEO, HIVE or HBD on various public outcomes.
A new form of System Income: a small % fee could be collected by the LEO Pool account.
Engagement - event-driven engagement can create a lot of positive site-time for users (in turn leads to more fun, ad revenue from page views, premium subs, etc.)
Premium use case? We could require premium in order to create a market (but not to vote in one)
How it Would Work
To launch a Prediction Market, you could require users to burn a small amount of LEO or send a small amount of LEO to Leo Pool. This can prevent spam creation of random prediction markets.
To make the decisions of outcomes decentralized, we can use Poll voting for the outcomes. Could do the poll in various ways:
Community Leaders are elected and it takes 3/5+ of them to vote to close a prediction market (results of a market are then closed by majority vote)
No leaders are elected and instead, a community-majority vote is required over a 24 hour period (same way normal Polls work right now)
Example:
~~~ embed:1840779613997347299?s=46&t=f3qY2xxYIegwgxWlYwko8g twitter metadata:MHhwb2x5Z29ufHxodHRwczovL3R3aXR0ZXIuY29tLzB4cG9seWdvbi9zdGF0dXMvMTg0MDc3OTYxMzk5NzM0NzI5OXw= ~~~
Imagine if INLEO had a prediction market for the upcoming U.S. Election. It was created by XYZ user by sending 10 LEO (or HBD/HIVE, etc.) to @leopool as the creation fee.
The creator sets 2 possible outcomes. (Kamala or Trump to win the U.S. election). They then can set the initial voting fee for each. The fee is dynamic to the current winner % (this creates the odds).
The creator also has to choose when the market closes (i.e. 1 day before the end of the election, date when winner is announced).
After the election is over, a poll is initiated by the creator of the market (or autonomously by the prediction contract). That poll is then voted on using 1 of the 2 implementations mentioned above (either community leader-based voting or community-based voting) to vote on the actual outcome of what happened IRL.
Once closed, the voted crypto (HBD, HIVE or LEO) is sent out accordingly based on votes.
#1 Leaderboard
The following will replace the current Leaderboard design. Our goal with the new design is to adopt HAFSQL and build a better database along with a Points system.
This Points system will be a far superior way to rank-ordering users on the Leaderboard. Expect that we'll start to use the Daily/Monthly/All-Time Leaderboard stats to give out grants/delegations/prizes (in a similar manner to how we conduct LPUD).
The Points system can be tweaked over time as we gather data on how people are performing. Generally, this can add a deep-level of gamification to the interface.
I (Khal) have also long-said that I would love to replace the Reputation Score system on the Interface with a completely new "Engagement Score". I imagine that something related to this points system would be possible and would allow us to then use the API for that purpose and many others. Potentially even open-sourcing that API for other Hive UIs to tap into as well.
Ranked Points System
Points are earned through actions on inleo.io:
The ranked points system would have 3 time-sorting categories:
Mobile Design
Example:
Generally a clean design with a focus on the top 3 users based on points. The "Today, Monthly, All-Time" categories will be toggled at the top.
Share Button
A share button in the top right will let you share a screenshot of the current standings into a Thread (automatically screenshotting it and then publishing it as a thread where you can add more text).
List
Scrolling down will show you the rest of the leaderboard. Likely showing the top 100 and then a "View All" button to load the rest.
Tap to Expand a User
If you tap on a user's username, then it will expand their "User Card" and show you the subcategories of how they earned their points.
Imagine tapping a user's icon and seeing a breakdown of:
100 Threads = 100 Points
27 Comments = 27 Points
3 Blog Posts = 30 Points
4 Referrals = 400 points
200 LEO staked = 20 Points
Total = 577 Points
Desktop Design
pending, will likely be similar to mobile but expanded
Comment on This Proposal
You can comment on this issue directly on the INLEO Platform.
#2 LeoDex Feature - Volume Airdrop
Goal of the Airdrop
To get people familiar with LeoDex both on the Maya Protocol side and on the Hive/LEO side. We want more users of LeoDex on a regular basis. The Airdrop is like a "opening day sale" at a retail store that is meant to encourage people to look around the aisles and see what we have to offer the world.
Hopefully, they find that we've built an amazing product and decide to use it both for the airdrop and into the future. Learning about the LEO token economy and the flywheel effects of growing LeoDex's Trading Volume
Details of Airdrop
From a functionality standpoint/overview:
Example:
So for example, in the address I'm logged in with - I may have traded $12,600 on LeoDex.
So my number would be $12,600 on the UI display.
You can add 10 tiers. To reach the next tier, you have to swap above a certain amount of $$
Tiers:
We can have 10 tiers. To reach the next tier, you have to swap above a certain amount of $$.
and so on ... up to 10
The higher your tier, the bigger your airdrop. This encourages users to swap more and more to reach the next tier and gamifies the process by displaying their tiers on the frontend in real-time.
Eligibility
Since the goal of this Volume Drop is to spur activity and awareness around LeoDex and the LEO Token Economy, we should also include an element of "LP Requirements" in order to be eligible for this Volume Drop. The target audience is primarily people who have not yet interacted with the LEO Token Economy or her ecosystem of products.
We will likely introduce an LP Requirement to the tiers. I imagine this could be done in either of two ways:
note: we will have some stipulation that the LP must be symmetric LEO:CACAO OR be asym on the CACAO side).
Other Eligibility Requirements:
TBD (optional) bonus for creating an account on INLEO - this may require some additional verification, which adds another layer of complexity but would create a lot of value for the overall LEO Ecosystem
Amount of the Airdrop
Since the amount of LEO for the airdrop will come from the ecosystem, I believe a LEO POWER stakeholder vote should take place. It should be adequately emphasized that the potential value capture of a successful LeoDex product will be incredibly high for the LEO Token Economy.
I also believe the LEO Team could match the airdrop amount by purchasing LEO off the open market. So if the ending airdrop amount determined by a stake-weighted community vote is 100k LEO, then perhaps the LEO team should also buy 100k LEO off the open market and donate it to the Volume-based airdrop to make the total 200k and also negate any negative sentiment around the potential downside of unlocking 100k LEO from the ecosystem and airdropping it to new users of LeoDex.
Frontend
The frontend for the volume airdrop will show on the Dynamic Island module. It will be a tier based airdrop and show your real-time tiers as you progress through the airdrop.
Example:
Data Backend
To make the Volume Airdrop display module, we need a backend to keep track of who's swapping and how much they are swapping (based on their Arbitrum / Maya Protocol wallet address).
This backend will go live at the same time as the Volume Airdrop display on the LeoDex.io interface.
In the process of building this backend, I realized that there are many other use cases available for it. In the future, we'll be able to expand more layers on top of this backend and it will allow for more features that are data-centric.
The 1st example of such a feature in my mind is trade history - if you are familiar with using popular CEXes (i.e. Binance), then you'll know that they have a Trade History tab. On this tab, you can see all your trades that you've ever made with that account. You can also export that history as a CSV file.
This is incredibly useful for analysis and many other reasons. Users often want to download their data and be able to use it.
Other potential features are a dashboard where users can see global trading metrics on LeoDex/Maya Protocol as well as deep analysis on their own account (wallet) that they are signed in with.
For example, seeing the total $ value of all the trades they've ever made... what assets they trade the most... what assets are traded on LeoDex most frequently...
We also could have features that show real-time swaps happening. I imagine this like a Shopify store - have you ever been to a digital storefront where they have those little message pop-ups in the bottom right? For example "sally bought 1x pair of Nike shorts for $39"... imagine that but for swaps. As other users swap / pool liquidity, you could see global messages.
The goal of this would be to encourage more activity in general. More activity on LeoDex = more Affiliate Revenue = more $LEO getting bought and deployed as permanent liquidity.
Comment on This Proposal
You can comment on this issue directly on the INLEO Platform.
#3 Economy - System Income Rewards Pool (SIRP) and LEO Token Mining
LEO Tokenomics Overview
Emissions
The emissions for LEO are 0.208 LEO/block and decrease over the next ~32 years. Block rewards stop when LEO reaches 50M tokens in circulation.
System Income (LeoAds, LeoPremium, LeoDex, LeoBridge Oracles and
LeoSubscriptions) are designed to replace this inflationary pool over time. As of right now, the System Income buys LEO and deploys it as permanent liquidity in various liquidity pools on DEXes (as of April 2024, this is deploying entirely into two pools: LEO-CACAO on Maya Protocol and LEO-HIVE on the Hive Blockchain).
Starting in 2033 (when inflation drops below 4%), the System Income will buy LEO and deploy it into the SIRP (System Income Rewards Pool).
This pool will continually grow in terms of rewards vs. the inflationary rewards pool. Starting in 2033 and until 2056, the LEO Inflationary Rewards pool will continue to drop in signficance as inflation drops and SIRP's share in the rewards allocated to users increases. By 2056, the inflationary pool will be 0% (as all LEO - 50M Tokens - is in circulation) and the rewards from the SIRP will be 100% of what is paid to users and active LEO POWER stakeholders on the platform.
Flywheel
Until 2033 (9 years), all System Income will buy LEO off the market and deploy it as permanent liquidity in DeFi LPs for the LEO Token. Right now (June 2024 as of this writing), this is LEO-CACAO and LEO-HIVE.
Why these two pools? Because of the Hive Aggregation Technology that drives revenue into the LEO Token Economy (more system income through affiliate fees + LeoBridging fees). As these 2 pools grow, the $ volume per month that can be transacted on HAT will increase. More $ volume = more system income = more deployed as permanent liquidity (a flywheel for the LEO Token Economy).
In the year 2033, the LEO Inflation rate will drop to 4% per year. At this time, the SIRP contract will be launched. Once SIRP is launched, the system income will no longer buy LEO off the open market and deploy it as permanent liquidity.
Instead, the SIRP contract will use system income to buy LEO off the open market and deploy it into the SIRP. The SIRP pays content creators and curators on the platform. As described above, from 2033 - 2056, the share of SIRP's payouts relative to the inflationary rewards pool will increase (as the System Income increases overtime and the inflation continues to drop Y-o-Y).
In the meantime (until 2033), the LEO community and team should aim to grow System Income as much as possible. This is a decade-long opportunity to deploy permanent liquidity into DeFi protocols. That liquidity will never leave the designated pools which means that as the LEO Token Economy grows, the $ value depth of those pools will continuously grow up and to the right.
Liquidity is important for any asset but it is even more so important for the LEO Token. Why? Because a large % of current and potential System Income is derived from trading and bridging the LEO Token. As mentioned above - LeoDex Affiliate Fees and Hive Aggregated swaps all run through the LEO Token Economy. Deeper pool depth = more volume = more system income = more permanent liquidity deployed.
Comment on This Issue
You can comment on this issue directly on the INLEO Platform.
Feature -Affiliate Program
Goal: grow the INLEO platform by creating deeply entrenched incentives that turn the existing community into an army of marketers.
Incentives can dramatically shift sentiment. As of this writing, INLEO has
~1,400 Monthly Active Users. If this userbase were able to leverage simple affiliate tracking links/codes to onboard new users and earn clearly defined incentives now and into the future, they would turn into an unstoppable force of marketers.
1,400 people working toward the common goal of onboarding as many new users as possible.
What Are the Incentives?
The incentives should be both immediate and recurring.
This means that there should be some instant gratification to onboarding new users. An instant payout for your work to onboard someone.
There also should be recurring incentives attached to each onboarded user.
Feature Improvement - Content Serving
Problem
When a user arrives on INLEO Threads, if they are served the Latest feed first, it is a randomized experience. We don't know what time of day the user is coming in at. We don't know the activity of other users at that time. The latest feed is not an efficient way to provide high quality user minutes off the bat.
If users aren't given high quality minutes right away, they are likely to leave and possibly never return. Expecting that Threads / INLEO have low quality content.
What is a high quality user minute? A minute where the user is looking at the feed and finding interesting things that catch their attention and lead to them spending more minutes on the platform.
Solution
If we can create high quality user minutes both for new and existing users, we are likely to see:
I will break down possible solutions for Threads and Blogs separately below.
Threads
For You Feed
The current implementation of the For You Feed on Threads uses an algorithm to determine what content to serve to users. The current algorithm is listed below. We'll continue to tweak this algo until it serves better content. In the long-run, LeoAI should serve as a viable replacement or enhancement to the algorithm with the goal of serving users relevant content.
The For You Feed should be the default feed that all users see (unless the user otherwise changes their default feed via the settings page). Existing users are accustomed to the Latest feed. I believe we can change this culture through a superior For You feed. It is undeniable that the majority of X users utilize "For You" along with pretty much every other social media platform. The For You feed is the future, the critical question is how do we create a better content serving environment.
50% of following feed & 50% of non-following feed
For the 50% of following feed:
Authors You Follow - Threads created by an author you follow and has 1 comment and 1 vote
Reply Authors - Show Threads from any Authors who have replied to you or you replied to author in the past 12 hours
For example - if I replied to one of @taskmaster4450le's Threads yesterday and then go to my For You feed today, his Threads show up in my For You
Show threads where the logged-in user was tagged (I know that these also go to the notifications tab, but I think it'd be nice to see them in the For You feed as well)
Author is in follow feed AND thread has more than 3 votes or more than 3 comments
There are several news2threads accounts like this one (https://labs.leofinance.io/profile/cryptoinsights). Mix in threads from these accounts because they are high-quality news
Show threads from hashtags that the logged-in user has engaged with in the past 24 hours. For example, if I replied to a thread that had #hive in it, then show me some threads in my feed that contain #hive
(let me know if this is possible @Deniz)
Take the top 5 most viewed threads (using our simple analytics API) and mix them into the feed
Recommendations
X recently implemented this - beneath every Tweet that you open, there are now 3-5 "Recommended Tweets". These Tweets are usually quite relevant and are based on the Tweet you're currently reading.
A similar recommendation feature would create more positive user minutes IF it serves the user Threads that they are likely to click and read based on the current thread they clicked and are reading.
I believe we can implement a recommendation engine that works on the following parameters to rank-order a list of 3-5 recommended Threads beneath the current thread you're on:
Blogs
All Hive UIs have long-held the same 4 feed:
INLEO technically has 8 feeds for article content (the 4 above with a toggle to sort from INLEO.io only content and all Hive content).
A For You Feed that is similar to the one used on Threads should be implemented for Blog Posts. The idea is to give users highly relevant long-form content based on their account and their on-chain activities... creating more positive user minutes on long-form the same way we do on Threads.
Recommendations should also be added beneath blog posts. When you get to the end of a blog post, 3-5 more blog posts should be recommended to our user. Again, the same algo that we use for Threads Recommendations can be repurposed here.
Feature - News2Threads V2
Problem
As it stands, there is a lack of high quality, fast and accurate news on INLEO Threads.
This is not to say that there is none of this happening, but there is a definite lack of quality news.
For Threads to grow as a high-quality news outlet that spurs engagement around highly relevant topics, we need to feed the feed with more high quality news.
New Feature
The new feature would move News2Threads off Discord and onto INLEO Directly. This would coincide nicely with some other features we are working on via slash commands (i.e. /command).
We're adding slash commands for Premium INLEO Users. This will allow this group of users to call on various commands that are built into the UI.
For example "/news2threads [insert-article-link]" could be used by premium users who want to share articles on INLEO as summarized threads + the article link.
I believe putting this on the UI in this way will have two major impacts:
Anything that moves conversation off Discord (centralised) and into Hive (decentralised) has to be a good thing !
Suggestion: could news threads get a colour coded edge or box ? That way we can immediately see them (as long as not too many other colour codes are used).
Could we invite some news organisations to post directly. Maybe even with the DHF funding LEO Premium for them for (say) a year ?
Solution
Outside of simply encouraging users to do this (and we should be doing this), we can also improve the News2Threads AI Engine that we've created.
News2Threads
Right now, News2Threads is a Discord bot where a certain group of INLEO Lions have access to share article links and then have them auto-published on
Threads as a 3 thread-summary of the article + a link to the original story.
I believe this is a fantastic way to share high-quality news on Threads. It allows users to get concise summaries of top news stories without even leaving INLEO. If they are interested in diving deeper on any story they've seen, the link is provided in the last thread.
The problem I see here is that we need more News2Threads Activity as well as More scaling for the bot itself.
We should see more content being published by the News2Threads bots and we should also see more engagement beneath that content.
A feature that could do this is adding News2Threads directly as a feature on Inleo.io.
I am just learning about this. It is interesting.
Yes it is. That is why I did a thread storm for it. We are now to the point where we need to share things as threads.
[Feature] Prediction Market
Polymarket has seen incredible success. INLEO is a social platform with built-in monetization features. This means we could also have a prediction market where people can vote using liquid LEO, HIVE or HBD on various public outcomes.
Why Build it?
A new form of System Income: a small % fee could be collected by the LEO Pool account.
Engagement - event-driven engagement can create a lot of positive site-time for users (in turn leads to more fun, ad revenue from page views, premium subs, etc.)
Premium use case? We could require premium in order to create a market (but not to vote in one)
How it Would Work
To launch a Prediction Market, you could require users to burn a small amount of LEO or send a small amount of LEO to Leo Pool. This can prevent spam creation of random prediction markets.
To make the decisions of outcomes decentralized, we can use Poll voting for the outcomes. Could do the poll in various ways:
Community Leaders are elected and it takes 3/5+ of them to vote to close a prediction market (results of a market are then closed by majority vote)
No leaders are elected and instead, a community-majority vote is required over a 24 hour period (same way normal Polls work right now)
Example:
~~~ embed:1840779613997347299?s=46&t=f3qY2xxYIegwgxWlYwko8g twitter metadata:MHhwb2x5Z29ufHxodHRwczovL3R3aXR0ZXIuY29tLzB4cG9seWdvbi9zdGF0dXMvMTg0MDc3OTYxMzk5NzM0NzI5OXw= ~~~
Imagine if INLEO had a prediction market for the upcoming U.S. Election. It was created by XYZ user by sending 10 LEO (or HBD/HIVE, etc.) to @leopool as the creation fee.
The creator sets 2 possible outcomes. (Kamala or Trump to win the U.S. election). They then can set the initial voting fee for each. The fee is dynamic to the current winner % (this creates the odds).
The creator also has to choose when the market closes (i.e. 1 day before the end of the election, date when winner is announced).
After the election is over, a poll is initiated by the creator of the market (or autonomously by the prediction contract). That poll is then voted on using 1 of the 2 implementations mentioned above (either community leader-based voting or community-based voting) to vote on the actual outcome of what happened IRL.
Once closed, the voted crypto (HBD, HIVE or LEO) is sent out accordingly based on votes.