Everyone who uses Terra has some sort of tax reporting burden. There is currently no steamlined interface or method to export Terra blockchain transactions in a manner that is consumable for 3rd party crypto tax reporting softwares. There are two solutions that try to meet this need, stake.tax, and beta.trackterra.org . Currently TrackTerra is the only open source solution . Our business case is to provide an interim solution until popular tax softwares (Koinly, cointracker, etc) adopt Terra natively and when they decide to do such they are welcome to use our code base which will greatly reduce their time and effort to implement.
The TrackTerra website generates on average between 100 -200 unique daily hits.
I’ve been paying hosting costs out of pocket since March and would continue to do so if necessary.The maintenance fund will cover our hosting costs for 3-4 years assuming we scale up 4x in the coming months.
We’re building a web interface and api that supports exporting Terra transactions in to a format that is consumable by 3rd party tax reporting softwares. Our MVP is available at beta.trackterra.org
This isnt a lot of money and im putting my reputation on the line.
That’s a horrible take in my opinion. If an agreement is in place that individuals won’t be charged to use the product, TrackTerra becomes a public good that serves the Terra community. It should inherently receive funding from the Terra community.
This is not really about the product itself. It’s about disrespect for validators, from the TrackTerra team, who are trying to spread FUD and are bullying validators who do not align to their view.
If they would have just reached me before spreading lies on Twitter, and tried to explain what are they building, things could have been sorted out differently.
I cannot personally trust people who attack others just because they share a different opinion. It’s not really about the problem. It’s about the attitude towards the problem.
Stake Systems is not a governance puppet. We DO NOT vote on our community’s desires and wishes. We vote only on what WE think it’s best for the ecosystem, long term. That’s it! If stakers do not agree with this approach, they are free to move their stake somewhere else. Pressure from the community is not on our voting agenda.
Would you want pilots to listen to the passenger community in regards to the deployment of the landing gear? I guess not.
I completely agree. If your delegators don’t agree with how you voted, please vote yourself and move your stake if you wish.
If you can’t vote for anyone you don’t like, you’ll find that you’ll quickly begin voting away good projects over emotions.
However, I do thank you for publicly expressing that you’ll vote against the proposal. That is very valuable in governance and helps people shape their own views.
Stop trying to play the ‘Victim’ card. You aren’t being bullied, you are being provided constructive criticism for the way you go about voting without any critical thinking or explanation. You don’t take the feedback from the community, you simply stay stuck in your ways without reason. Also, FUD means Fear, Uncertainty, and Doubt. People feel FUD when it comes to a protocol unknowns or lack of education. People spread FUD when they don’t understand something. Stop invoking FUD just because someone is attempting to provide you with their opinion. There is no Fear about Stake.Systems, what is there to be afraid of? There is no Uncertainty, we know where you stand. There is no Doubt that stake.systems operates in accordance to your own views. All of this is fine.
A true leader listens to their followers and reflects inward. You are showing that you do neither.
The proposal was brand new and i was watching the community votes come in, then suddenly i see 5m No votes, i check agora, nothing. So i posted on twitter kindly asking my frens to provide support and if the 5m whale has concerns to engage me here.
Larry , a super helpful and good intentioned community member correctly pointed out that stake.system voted no, and so i asked why and pointed out that i probably wouldnt get a response from you on twitter as you hadn’t been active since April. It’s fact. It’s not FUD. And it’s not a personal attack.
Thanks to LARRY, I voted YES on this proposal, and re delagated all my LUNA from stake system to him! I think we should. have a way to see how our validators are voting for each proposal on Terra station! We need this.
One recommendation I have is to provide a generic CSV first so that non-koinly (or whatever) users aren’t left stuck waiting. Could be a way to get more feedback/bug reports early on.
Proposal passed! Thanks for all the support fam! We’re aiming to have our first development update mid December. We’ll be posting updates here and on Twitter. If your interested follow TrackTerra on twitter. Stay tuned!
Development efforts are ongoing and proceeding on schedule .This week we are wrapping up the transaction classifier and plan to start on the parser next, we likely spend a few weeks on the parser as it is the most complex component of TrackTerra. Subsequently we will work on the web ui and export features. We are targeting mid January for completion of milestone 1 and the release of our MVP, efforts towards additional milestones will continue thereafter.
We made out favorably with our community grant, where the Luna is worth a bit more than the initial estimate of 41$ . We will be holding our grant funding as luna for the foreseeable future. We will communicate any decisions we make around this.
These additional funds will be used for us to host our own FCD infrastructure. We are currently exploring potenial partnerships with other infrastructure hosts as well as exploring how we can most cost effectively self host our own FCD. TFL recently bootstrapped the FCD postgres database making it a much easier process to get up and running. (Thanks Paul!)
We’re aiming to have an additional update out at the end of the month.
Small update. Development is progressing. Fully extensible classifier and parser are mostly done. We have a few special cases around liquidations that were wrapping up in the coming weeks. We’ve shifted focus to the app front-end side of things so that we can build an UI that makes defining classifier definitions a bit easier. Once we have a functional UI we will be wrapping up the remaining protocol definitions and completing any necessary testing.
We also have fully built an FCD server and are currently using it in our testing/development. This will make parsing wallets much faster than it is in our currentl alpha.
We are aiming to complete milestone 1 and make our MVP available on or before January 25th.
Another update. Unfortunately we are just slightly behind our deadline of the 25th. We’ve decided to push our release date to February 4th. On February 4th we will fully release with the completion of all milestones. As another update we are actively working with cryptotaxcalculator to assist them with integrating TrackTerra natively in to their tax app via our API.
We aim to have a teaser video out within the next week.
Would be very helpful noting the UST value of each transaction.
Let’s say you swap Psi to nLuna. When you upload the cvs to Koinly (or any other Tax software), we rely on them to know the usd value of Psi or nLuna at that point, or we have to manually find it.
I’m sure most software do this, but only if they have the info accessible. Psi wasn’t listed on CMC until the 5th of this year as an example, so if that’s where they pull the info from, you’d have to do the work manually for 2021
An update! It was a bit bumpy but we launched last Friday. We dropped an update yesterday improving our transaction support .
We still have a few actions to bring this project to completion. Over the next 2 weeks we will be shoring up our transaction support. Working with 3rd party tax softwares on an API integration. And also working towards out final release which will include deployment docs and general documentation on how to add classifiers and parsers to trackterra.
