A Few Updates on the LeoVerse
1/ Issues with leo.voter delegation payments is fixed. A few double payments were sent out + the APR was increased temporarily to remediate any missed payouts from September
A Few Updates on the LeoVerse
1/ Issues with leo.voter delegation payments is fixed. A few double payments were sent out + the APR was increased temporarily to remediate any missed payouts from September
5/ If you have any questions, feel free to @ me on Threads. Great times ahead and so much development happening across the board on Creator Subs, LeoAI, LeoAds and many more features & stability improvements 🦁
@khaleelkazi is there anyway Lions can help out?
Just keep rolling in the #feedback in general
Appreciate you 🦁 and all your support
4/ We're rescheduling the growth call today. I'll be working all day with the teams to test, fix and iterate on Creator Subscriptions. I'm trying to get this out to public release as soon as humanely possible. I believe this is a game changing feature for the LEO Token Economy as it drives a whole new economic model for creators + creates a new revenue stream for the autonomous LEO Token buybacks and perma-pooling into the LEO-CACAO Liquidity Pool on Maya Protocol
3/ We added the ability for autopay using recurring subscriptions. So you can subscribe to creators with autopay either enabled or disabled. If enabled, you'll be on autopay to that creator for 1 year and won't have to worry about re-subscribing each month. If disabled, you'd have to manually resubscribe each month. We're also deploying this to INLEO Premium so that you can turn on autopay if you desire it
Autopay is going to be fantastic! Great addition snuck in there for the whole ecosystem, but very exciting for the creative subs.
2/ Creator Subscriptions are being worked on as we speak. There are so many features, new frontend & backend code for this release. I wanted to have it out by Tuesday of this week but I'm holding it back just a bit longer so we can work out known bugs. We're finding a lot of bugs in these early stages so it's better for the team to be testing, fixing and iterating before public release. It's important that these features work well at launch, especially since this deals with money (subscriptions via HBD, claims via dashboard, etc.).
Understandable that you wanna hold it. People gget Anyoed if there are to many bugs.
4.5/ I have also taken over Tech Support personally for the time being to get us down to 0 tickets. If you have an open ticket, I will be in touch very soon. I'm working through all of them as fast as possible. Sorry for all the delays. Since sunsetting CUB/POLYCUB, we've had extreme ticket load and it's been a nightmare for the team to resolve. New tech support staff will be trained and starting after I clear all existing tickets.