Greetings my fellow Terraists . It’s long overdue , however i’d like to give you all an update on my plans for Trackterra V2(trackterra.org) . This project has been moving slowly as of late as im currently designing a major rewrite that will improve functionality and supportability moving forward.
Right now the biggest struggle is that trackterra was written as such to rely on mirror graphql for most of its data as parsing transaction logs is quite cumbersome and can take quite a bit to get working right.
However this comes with two major flaws, it doesnt parse or reparse transactions on demand and this can result in some transactions sporadically missing(i think this issue is related to the spam attack in march?), but more importantly the graphql transaction parser doesn’t start “watching” an address until it interacts with the mirror contracts.
So this means if you used terraswap or other terra native functions prior to ever using mirror, trackterra would not know about these transactions as the graphql api doesn’t return them .
So in order to fix this transactions need to be parsed directly by trackterra when processing a report. In order to do this i will be porting the trackterra report generation code to nodejs , and i will be stealing some code from mirror-graph/src/collector at master · Mirror-Protocol/mirror-graph · GitHub in order to implement a transaction parser. I will also be building this out to include anchor and terra native support.
This is currently in the works , and i will actually be bringing on some extra development resources to help get this done. Estimated timeline just now is July/august.
TrackTerra v2 is expected to include
ANC reward claiming
bLuna delegation rewards
Mirror v1 and V2 support
Support for long and short staking positions
CDP minting and burning
More details to come
Proper tracking of shuttle fees
Native swap support Luna/UST minting
Slashing? (anyone have any tx examples of this?)
Delegation rewards (any tips on the best way to track these?)
And for anything missing here i would love to hear from the community as to what you would like to see.
I would like to get some feedback on monetization , i see a few approaches that can be taken here . But in order to keep up with the growth of the terra ecosystem some method of monetization needs to be implemented.
In general upkeep consist of the following
Hosting costs are about 750 - 1500$ per year, includes hosting a full node
Im going to roughly estimate about 60-80 hours of effort to support a new protocol over the course of a year. An additional 20 hours allocated to support and bug fixes over the course of the first year. And after the first year unless there are any major protocol updates need for support should be minimal.
So as far as monetization , id ideally like to recoup some of the development costs , but at minimum i’d like to recoup the yearly hosting costs .
Since v2 on its own is going to support 3 different apps on terra, should my community spend proposal be split up between different platforms?
I expect costs for all three integrations and hosting for the next 3 years will be between 10k - 15k . Would the community support reimbursing these costs via the respective DAOs? In return the codebase will be made opensource and i will host trackterra for 3 years. After 3 years i will ask the DAO to fund another 3 years of hosting.
In order to support additional projects , either the respective project can update the trackterra parser, or they can fund a grant in the 5k - 10k range depending on complexity and we will take on development.
The alternative approach would be to implement an approach similar to astro tools , where you would need to hold a trackterra token in order to use the platform or the full version of the platform. With this approach it’s not in our best interest to be open source. I feel being 100% DAO funded is the way to go. But if you think otherwise, would love to hear your feedback.