INLEO has been building in a very specific way over the past few years and especially in the past few months. Our focus has always been on external users in the broader crypto space. Many of these users utilize X on a daily basis for their social interactions.
The fact that they are crypto users and they are using a platform like X is something that we believe we can change with our technology on Hive. Our platform has emerged as something that looks & feels similar to X but puts all their data on the Hive blockchain.
Immutable accounts and data. Put it all on chain.
Over the past several weeks, we've been working with other projects within the Hive ecosystem to proliferate our technology as open source contributions to the Hive Ecosystem.
This is all a part of our updated DHF proposal. Our regular updates will showcase the roadmap to open sourcing more of INLEO's technologies and also providing finalized products in the form of Plug & Play APIs that are open source and easily available to all Hive frontends, games and applications.
It's obvious to us now that our path forward on Hive is to Open Source our work and help all Hive projects grow alongside us.
INLEO's passion is not only in building this technology but also marketing it to the broader crypto space. We've found a lot of success in collaboration with other ecosystems. You can see this with our Dash collaboration from November-December 2024. You'll see it in our upcoming collaborations with the Solana Network, Arbitrum Foundation, Litecoin Foundation, ChainLink and the many other HUGE crypto partners that we have lined up as part of our DHF Proposal.
As we continue to do these collaborations, we want to open source the many technologies that have made INLEO so successful. These technologies can be utilized either from the Open Source codebases we release or from the Plug & Play APIs that we release and manage.
We believe that INLEO's place on Hive is about to transition heavily into designing, developing, iterating and managing Open Source, Plug & Play APIs that can be utilized by all Hive projects.
As we do this, our collaborations will bring in a flood of new users to not only INLEO, but also every other Hive application that is out there. The more that we can spread our successful technology to other Hive UIs, the more that we can all grow together as these new users come into Hive and find an app that they want to use on a daily basis (or hopefully, many Hive apps that they use each day).
I am reaching out to all Hive App Owners and asking them if they'd like to collaborate with us in any way. Whether it means getting early access to our Open Source codebases as we roll them out one-by-one or getting set up with our Plug & Play APIs so that they can start integrating our most successful features.
In this post, I want to outline some of our most successful features and the ones that we plan to Open Source as a part of our DHF Proposal.
INLEO's Onboarding Technology
March 2025 | Released ✅
As promised in our first DHF Transparency Report and Roadmap, we released the Plug & Play APIs + Documentation for our Onboarding Technology on Thursday of last week.
Any Hive application can now integrate INLEO's onboarding technology in 3 forms:
- Keystore (Full Hive Account, Full Self-Custody)
- X Lite Accounts (Lite Account, Web2 Authentication)
- Google Lite Accounts (Lite Account, Web2 Authentication)
We're talking with about 8 different Hive UIs and applications who are working to integrate the APIs/Open Source tech into their framework so that they can allow these signup and login methods. If you are a Hive app owner and want to integrate, you can read the docs and/or get in touch with our team. We're happy to help any Hive UI who wants to integrate.
The Plug & Play APIs offer an elegant and simple way to integrate these sign up / login methods.
Dynamic Resource Credit (RC) Delegation System + Account Creation Tokens
March 2025 | Released ✅
As a reminder, we also included our Resource Credit delegation system + use of our account creation tokens as part of the Open Source APIs we released for our onboarding technology.
A UI has two options to utilize our tech:
- Look at the Open Source codebase, clone it and integrate it on their own
- Use our Plug & Play API to easily connect to LeoInfra V2 and allow signups and logins instantly
If any Hive app uses option #2, we also provide our onboarding resources to new account creations. So it costs the Hive app nothing. The signup APIs use:
- INLEO's account creation tokens to create the Hive accounts
- INLEO's Dynamic Resource Credit delegation system
The dynamic RC delegation system does exactly what the title suggests: it dynamically delegates RCs to new signups based on need. So if a new signup becomes heavily active, our system reads their RCs and continually delegates more RCs to them as they get more active. This ensures the new signups don't run out of RCs if they start blogging/threading/commenting/upvoting right after signing up.
If a signup becomes inactive or powers up Hive or for whatever reason no longer needs as many RCs, our system sees that their RCs are sitting above 80% for an extended period of time - then the delegation is slowly reduced. If the user suddenly runs low on RCs again at some point in the future, our system will re-delegate RCs to them.
Long story short, new onboards have plenty of RCs to interact off the bat. Over time, they are encouraged to power up their own Hive so that they control their own pool of RCs.
HAFSQL Access
March 2025 | Early Access Release
Last Friday, we released access to our HAFSQL database to a handful of other applications privately. After a bit more testing and refining with some of the people who have started privately accessing it, we are going to open source the APIs and allow anyone to access our instance of HAFSQL - which is extremely useful for pulling real-time, onchain data.
HAFSQL has become an integral part of INLEO's UI. It allows us to serve complex data sets to our users in various parts of our interface (Leaderboard, Referrals, etc.).
Use of HAFSQL can be extremely custom. What we are opening up here is the ability for other apps on Hive to tap into our resources that we use to run our own instance of HAFSQL. For free as part of our DHF Proposal.
Accounts API
This Week!
INLEO maintains our own Accounts API that provides relevant, real-time information about users. Some of this data is very common on-chain. Other pieces of data include:
- Premium status
- Creator Subscriptions
- etc.
We are planning to release this Accounts API in the next few days. This will allow other Hive UIs to pull real-time data from our Accounts API. The API has a lot of standard Hive Account info but it also has many modifications that our team has added. These upgrades are vital to running things like INLEO Premium, Creator Subscriptions, Referrals, etc.
Having access to that data is extremely important if/when other applications want to integrate our Creator Subs, Premium, Referrals, etc. technologies.
This is why we've chosen to Open Source our Accounts API sooner than later. It lays some critical foundation needed for us to open source some of our other successful technologies if other applications want to integrate them down the road.
Ledger, Trustwallet, Trezor Support
INLEO has been building a wallet framework. This is currently in beta for our team and private testers. We're refining this framework and will begin releasing more signup and login options to Hive. Fully open sourced as part of our DHF Proposal.
These new wallet options are extremely important for our upcoming collaborations. Similar to how we onboarded Dash users, we want to give our Solana, Arbitrum, Litecoin, Chainlink, etc. partners the wallet sign-in options they need to seamlessly sign up and login to Hive.
Our updated proposal now includes us open sourcing these signup and login methods (like we already did for Keystore, X & Google Lite Accounts) and releasing them prior to the collabs going live.
Doing these releases before the collabs go live is a great way for other Hive applications to add the integrations they want to add and tap into the growth that INLEO brings to the Hive blockchain in the form of new users from these other ecosystems. This is a new generation of Hivers that are very familiar with crypto, are eager to invest in HIVE and are also eager to get active on chain.
Referral System API, Backend and Frontend
Our Referral System has proven to be quite successful. We continue to refine it and have found that it significantly improves new user retention.
Acquiring new users is important but keeping those users around is equally important. Our referral system has proven to do a really good job of this as the Referral Dashboard frontend that we built allows existing users to see exactly who has signed up through their referral links, track their activity on the Hive blockchain and encourage them to get more active.
To make all of this work, we have several layers of infrastructure:
- Tracking on-chain data related to the onboard via HAFSQL - how many posts, threads, comments, etc. they've made as well as other relevant data in our Accounts API (access to our HAFSQL node is opened up in Phase 2 of this roadmap)
- Affiliate link structure (we modeled this after Amazon's Affiliate link structure. Where if a user clicks on a blog post / thread you've shared, then it will give you the referral credit if they signup to Hive within 30 days of clicking your link). This deeply incentivizes sharing your Hive content outside of the ecosystem and aiming to get as many clicks on it as possible
- ...
As you can see, laying the groundwork by releasing our other APIs is critical for adding successful features like this to our open source contributions to Hive.
Creator Subscriptions
Creator Subs have been a really exciting addition to the INLEO App. Now, users can have their own subscribers (very similar to substack). This offers a whole new way for authors to monetize their content.
What we've created with Creator Subs is:
- A payments platform that uses HBD for creators and their subscribers
- Private content for creators and their subs - uses an encrypted container system we built that is 100% on-chain
- Value capture for the Hive economy through a small fee on every creator-subscriber transaction
With an influx of new users coming from our collabs, we want to ensure that other Hive apps have the opportunity to add Creator Subs and encrypted on-chain content to their frontend as well.
We'll be open sourcing the APIs for Creator Subscriptions so that every frontend can integrate a seamless system for:
- Payments
- Encrypted on-chain containers (private content)
- Value capture for HIVE through creator-subscriber fees
As we continue to release the other infrastructure mentioned above that is needed to operate Creator Subs, we'll announce the release date of the Open API access. We want to ensure that other Hive UIs can have this live before our collaborations so that we can all benefit from the influx of new users that come into Hive.
It's important that we not only onboard new users and investors into the HIVE token, but that we also bring paying members of the Hive economy. Imagine that these new users not only buy and stake HIVE POWER but also subscribe to some of their favorite creators. This will get them familiar with buying, holding and spending HBD in the Hive economy. A simultaneous effect will be rewarding the hard work that existing Hive Creators have put into building their brand on the Hive blockchain.
Wins for everyone.
Cross-UI Bookmarks Framework
We've built a robust system for bookmarks that not only allows users to bookmark posts, comments and threads but also allows them to create folders and subfolders for those bookmarks to organize them better. This utilizes on-chain data to assign bookmarks and folders to a specific user's Hive account.
As we onboard new users, we want them to be able to access their bookmarks, folders, etc. from other interfaces in addition to INLEO. We believe that this will greatly improve the User Experience if a user likes to utilize INLEO for some things but Ecency for another (example).
As part of our shift to open sourcing more of INLEO's technologies so that all Hive UIs can benefit and all existing and future Hive Users can have a better User Experience, we'll be open sourcing our Bookmarks APIs so that every UI can have a simple-to-implement framework for Bookmarks. No more losing your place on-chain. Any UI that has it will be able to seamlessly offer bookmarks and folders across UIs and across devices.
More APIs, More Onboarding, More Hive Application Collaboration
The point of this post is to talk a bit about the APIs that we've already released and plan to release in the very near future as part of our DHF Proposal. Our proposal is not just about marketing the platform so that we can grow Hive - it's about open sourcing INLEO's technologies so that as we do that marketing, all the new users we bring to Hive can proliferate to the various Hive Apps in our ecosystem.
We believe heavily in a collaborative approach to growth. We believe that there's a lack of collaboration amongst Hive teams right now and many of us have to re-invent the wheel when new features pop up or new desires from the Hive ecosystem emerge. INLEO has been a part of this problem in the past - by developing our features in a silo.
We want to be a part of the solution going forward. Developing our innovations not just as INLEO-only features, but as open source contributions to the Hive ecosystem as well as Plug & Play APIs that can be utilized easily by any interface, application or game.
Keep an eye out this week for the next iteration of our Open Source contributions to Hive. Our proposal is currently at 96% but we are not waiting to get funded in order to do this work. We believe in our mission and we believe in our ability to grow Hive. We are doing all of this work up front to show our commitment to growing Hive both now and in the many years to come. This ecosystem means so much to us and we will not stop building here. Join us as we continue to put 110% of our effort into making Hive a top 10 blockchain. Where it belongs.