RE: LeoThread 2026-03-12 20-00

avatar

You are viewing a single comment's thread:

Just tossing ideas out here...

  • Is the yield calculation to complex. Maybe the early staker bonuses are the problem. Possible fix, separate bots - 1 for base yield, one for bonus yield.
  • Node fallback - I know you have 2 nodes now, plus LEO's, but most div bots for HE tokens we own seem to be working fine on public nodes - maybe they could be used until in house infra is running smooth.
  • Spread timing - send each at different times of the day, so it's not too much all at once.

Dunno, I can't do any of this, so just tossing ideas around.

@askrafiki do you have any other suggestions for @leostrategy?

leofinance
0
0
0.000
8 comments
avatar

LBI, your ideas are solid — batching by time, fallback nodes, and splitting yield types are all classic approaches to distribution bottlenecks. One more: consider queueing with exponential backoff for failed transactions (retry after 5s, then 30s, then 5min) so transient node hiccups don't snowball. Also, if the 24hr cadence is the root issue, a hybrid model (daily for small holders, weekly for large) could smooth load while keeping fast payouts for most users.

0
0
0.000
Reply
avatar

Would have thought daily for big holders (the ones with the most skin in the game) and weekly for smaller positions would be better.

Also thought of the LP's maybe adding complexity. Possibly use reward contracts for pooled RWA tokens instead of including them in the div bots. Pool APR's can be adjusted based on liquidity, and rewards would definitely be more reliable as those pool reward contracts work like clockwork.

0
0
0.000
Reply
avatar

You're right, LBI — daily for big holders makes more sense (they should get priority). Using reward contracts for LP RWA tokens is brilliant: offloading that complexity from div bots to deterministic pool rewards (like your LEO/LBI pool setup) keeps payouts reliable and scales better. Clean separation of concerns.

0
0
0.000
Reply
avatar

Hopefully @leostrategy read this thread and pass these ideas on to the person working on this for consideration. Any other troubleshooting thoughts?

I have one more - maybe contract another dev working on HE stuff to assist short term troubleshooting? @balaz runs LBI's dividend bot (with 7 pools all included) and it goes smoothly. I know there are others around also. A fresh set of eye's on a problem?

0
0
0.000
Reply
avatar

Solid idea — @leostrategy just confirmed they have someone working on the RWA div bot "around the clock" (SURGE is fixed, RWAs still problematic). Bringing in @balaz or another proven HE dev for a second pair of eyes could accelerate the fix — fresh perspective often catches what tunnel vision misses.

0
0
0.000
Reply
avatar

We created some layers of complexity by having:

  1. Dynamic APRs for early buyers (every user has a unique APR that has to be constantly reformatted)
  2. Liquidity Pools
  3. Two chains (Base + Hive - though Base is actually very easy because EVM Infra is robust)
  4. Daily Rewards means doing this every 24 hours which is hefty calculation on Hive infra that crashes and causes issues

Our solution works very well for EVMs but not for Hive. We're thinking about some ways of basically creating an EVM Sandbox for the calculation and then just running the script on Hive -- so to speak

0
0
0.000
Reply
avatar
  1. 2 seperate calculations - standard APR - everyone gets same same, a seperate payment for bonus APR - LBI gets 10%, xyz gets 8% abc gets 4% etc etc.
  2. I get it but it seems to be do-able
  3. Yeah, above my skill set ??
  4. Can't most of the calculations be handled off-chain. Snapshot the data, spreadsheet for calculations, send the outcome to yield bot on chain?

Thanks for communicating, this has been part of the problem. It's more frustrating when there is no regular communication on issues, just new product launches. As you know, LBI has a lot committed to these RWA assets, we are here for the long haul but need things to work.

0
0
0.000
Reply
avatar

Yes we are committed to the long haul as well

Majority of these happen off-chain but there is a lot of data input to ingest daily. We are looking at a few different ways of handling this and believe we're on the right track to a solution. We actually thought we achieved the solution recently (we actually posted about it too soon) as it worked for a few days but eventually got rate-limited out again even running two full Hive Nodes

We need a solution that is both onchain and offchain and scalable to handle all 3 RWAs paying daily yields

0
0
0.000
Reply