Apply 2.5k Wnear for Q1 operating

Currently, to maintain the system running well, we are runing a couple of watchdog tools, price oracle bots. And QA Testing work are also contantly comsumming near, especially when new features keep going in Q1 2024.

So, we need to apply 2.5K wnear for operating usage in Q1 2024.

1 Like

Like Q1, to keep running those backend tools and kinds of bots, as well as QA Testing work, we need to apply 2.5K wnear for operating usage in Q2 2024.

1 Like

Similar to previous quarter, we nee to apply 2.5K wnear for operation usage in Q3 2024. It includes kinds of bots, watchdogs as well as QA Testing cost and etc.

1 Like

Hi Marco,

Could we please get a more detailed breakdown of how the NEAR is spent? Perhaps we can look at the data from last couple of quarters?

I’ve had a dev reach to me and ask what ‘systems’ you are referring to.

I would also be interested in running an analysis on how the fee generation on REF compares to these basic operational expenses.

1 Like

The detailed breakdown could easily be parsed by tracing those wnear token’s distribution flow. We normally keep these wnear token in ref-dev-teller.near and distribute them directly to target accounts once needed.
As described in previous post, those accounts includes kinds of bots, watchdogs, and our AQ testing related accounts, they are linking to all kinds of different components that keep the whole ref system running smoothly.

Similar to previous quarter, we nee to apply 2.5K wnear for operation usage in Q4 2024. It includes kinds of bots, watchdogs as well as QA Testing cost and etc.

1 Like