In this clip from the latest LeoFinance Roundtable Podcast, we talk about the upcoming LEO Lightning Database project. The tagline of this project is:
The Speed of Web2 Meets the Principles of Web3
As mentioned in the clip, there have been a lot of scotbot and Hive node issues since the latest Hive Hardfork. These issues cause a headache for the end user and are just one example of the hiccups that come along with being a web3 platform.
Most endusers are accustomed to a seamless web experience with no bugs and no delays. As @scaredycatguide mentions in this video, they want everything instantly because that's what they're used to.
They don't want to visit their favorite crypto platform and then have to wait for loading times or pay hefty fees for simple actions.
While Hive has dramatically better scaling, tx speed, etc.. it doesn't (nor can it ever) compete with Web2 when it comes to raw speed.
To solve for this issue, we've decided to go down a path of building out an entire content layer for LeoFinance. We're calling this Leo Lightning DB.
By having this content layer, we're essentially "web2ifying" the experience of LeoFinance.io on the front-end but still making sure to keep the Web3 backend.
In a nutshell, when the Lightning DB is deployed, your actions will run through LeoFinance's Lightning Database before reaching the Hive blockchain.
This means that LeoFinance.io will display your posts, comments and activities instantly while our Lightning layer broadcasts all of those operations directly to the Hive blockchain on the backend.
While many of us (and future end users) want to know that our data is being published to a public, transparent and verifiable blockchain, the vast majority of people don't actually want to sit there and wait for each of those things to reach the blockchain.
Instead, the best blockchain applications will provide a frontend user experience that is fast, seamless and user-friendly. Meanwhile, the backend will handle all of the broadcasting and "slow" stuff.
In other words: the best blockchain apps will bridge the gap.. merging the speed of web2 with the principles of web3.
You may also notice a recurring theme here:
- Seamless UI experience for the end user
- Messy stuff handled on the backend
- Key piece of infrastructure
hint: LeoInfra
hint2: LEO Token on a Standalone Second Layer
Major announcements coming in the 2021 Roadmap
Listen & Subscribe to the LeoFinance Podcast!
LeoFinance is a blockchain-based social media community for Crypto & Finance content creators. Our tokenized app allows users and creators to engage and share content on the blockchain while earning cryptocurrency rewards.
| Track Hive Data | New Interface! | About Us |
|---|---|---|
| Hivestats | LeoFinance Beta | Learn More |
 |  |  |
| Trade Hive Tokens | Wrapped LEO | Hive Witness |
|---|---|---|
| LeoDex | wLEO On Uniswap | Vote |
 |  |  |
▶️ 3Speak
Cross-chain? This is the first time I hear this. Sounds very interesting. And maybe difficult too. For example how do you resolve Resource Credits (RC) problems. Let us say that the project is using the Steem blockchain and the Hive blockchain, and a given user have enough Resource Credits (RC) on the Steem blockchain to post, but not on the Hive blockchain. What would happen in that case?
I think cross-chain is what Polkadot is trying to do.
wLEO is already making Leo cross chain. The token is now available on two chains.
With the ETH, transaction fees, as it stands now, will be required. As for Steem, it will require having RCs on there.
People who are interested in earning multiple tokens will have the necessary currency to make the transactions.
Posted Using LeoFinance Beta
This is seriously awesome. User experience is important. It's crazy how fast you guys are lapping hive in Utility.
Posted Using LeoFinance Beta
I’m really excited about this project in particular.
I did an interview about LEO recently and they asked for some of the motivation/reasoning behind developing the project. For me, it’s just about building something that is awesome to use everyday from a selfish perspective and for the users who come here.
Everything we do is aimed at making the user experience better. I think that’s our fundamental edge. Listening, observing, predicting and building based on the feedback we get. Let’s see where we end up in 2021 with our approach 🦁
Posted Using LeoFinance Beta
That's really important indeed. Especially for the first impression of new users.
People are spoiled nowadays and drop out quickly if services are slow.
Great initiative!
Posted Using LeoFinance Beta
People have been spoiled all-a-days and drop out quick lol
Posted Using LeoFinance Beta
What you've built is pretty astounding. I like it. If I find some UI issues I'll let you know.
Posted Using LeoFinance Beta
Hive and Leo are two totally different animals.
They are not in competition. The development on Hive is taking place at the second layer. This is what is being done by Leo, 3Speak, and some other projects.
Hive is a blockchain that needs to get the base code updated. That is being done. Having hard forks every 6 months makes it tough to upgrade regularly.
This is why it falls to the applications.
Posted Using LeoFinance Beta
It's vital to have speed on the front-end as quick as a twitter. You rightly say, there's no need to wait for the transaction to be broadcasted to the blockchain for it to go through on the front end. I.E no need to wait 3 seconds for a comment to be posted ect. Fast is indeed better.
That last point you mentioned about batching posts to transact to Ethereum, what is the social media dapp on Etheruem for the content to be posted? Could everyone's content be done in one transaction to post to ETH?
Posted Using LeoFinance Beta
That's great news especially for folks who engage a lot and don't want to lose time waiting pagea to load.
Posted Using LeoFinance Beta
Yeah the wait is a major pain in the ass. Need a faster system to get to 1,000 comments in a week.
Posted Using LeoFinance Beta
I have the feeling that a faster speed will get you like 3000 😁
Posted Using LeoFinance Beta
When miroblogging is unveiled, I have a feeling many will be up to that number.
I will not be the only one.
Posted Using LeoFinance Beta
The Lightning DB should bring us some clear view on all the Leo Finance posts and comments and we'll be able to steer the ship into the right direction. I would like to see some statistics put in place when that is ready and get some insights into this Finance ecosystem. The gained knowledge from that should provide the advantage over any other Hive communities as we'll be able to see what provides more value and simply capitalize on that. Great move with this one!
Posted Using LeoFinance Beta
So many things happening. It's great to see this.
Posted Using LeoFinance Beta
75% of traffic for https://leofinance.io is coming from just three countries. There is so much potential left if we can tap into the audience of other countries. Maybe focusing on different languages like Japanese, Korean etc. would be a real help.
Posted Using LeoFinance Beta
Need to really separate the website for that.
Can you imagine the site with posts in many different languages all thrown in together?
Just think of English, Spanish, French, Italian, Korean, and Japanese all on your feed.
Posted Using LeoFinance Beta
We could simply use language settings options to select which languages users want to see. We can also have specific sections for different languages on the top of the website.
Quick Example
There could even be better ways to do this. One thing for sure is it's vital for us to go after these different languages.
Posted Using LeoFinance Beta
That is true. Enabling a language setting will allow for a wider scale of users.
It is a great idea.
Posted Using LeoFinance Beta
You should talk about this in one of your posts. You have far more exposure to your writings than I do.
Posted Using LeoFinance Beta
Awesome guys, they way you take the show. Love it.
THIS. The Hive node issues are annoying AF. Makes me dread all future hard forks. Retention is everything and a good first impression is so important. We can't be trying to explain to normies/newbies about how to change Hive nodes and managing RC credits.
It's not hard to decouple user actions from direct blockchain actions. Cast a vote, UI reports it cast.
The difficulty is stuff like updating the UI to correctly reflect the new state (like the rshares applied).
Ideally, the in-between layer would predict what the new payout will be before voting, then updates the UI with that amount.
Also, ideally, the in-between layer would show a report on the rare case an operation fails to get into a block. So curators and authors can see when their actions didn't make it and need to be re-broadcasted.
Posted Using LeoFinance Beta
Test
Posted Using LeoFinance Beta
Lightning comment
Posted Using LeoFinance Beta
Lightning comment
Posted Using LeoFinance Beta
Lightning comment
Posted Using LeoFinance Beta
Non lightning comment
Posted Using LeoFinance Beta