Look at it like building a house, the foundation is the most important part then it’s step by step after that, eg-: you don’t gyprock the house before the roof goes on. Be patient, hope the foundation is rock solid and you may reap many rewards later on. Chill 
1 Like
I really want this network to stay in place. I’ve been on this project almost from the very beginning. It just makes me angry that some greedy people decided to throw us all and grab our money, that’s why it hurts me when they do this !! Where is this fair justice? They must revive this network and prove that we are strong and no one will stop us, and the sooner they do it, the better, because people are slowly running away from the project and they are not to blame.
Why is the information flow so slow that people want to learn something and are waiting for news from you. Don’t you need to speed up the work and start 1.2% tax as soon as possible? Why can’t we get information anywhere?
2 Likes
Starting to bore me with your cry baby scenario. You speculated. You lost. That’s what happens when you speculate. Take responsibility. Move on, do something useful.
2 Likes
Can see some impatient folks… but changes take time… Sharing #LUNCPenguins Huddle Tracker hope it helps to ease anxiety of these folks by sharing some information.
1 Like
Thank you, that’s a great resource!
1 Like
Just a question
The ten working days TFL have to respond - given they are doing all the changes and embedding the changes now - does it effectively mean they have to finish the changes in this 10 working day period ?
I have seen same question at the terra rebels discord channel. I want to ask here. also so what will happen after 10 days now? TFL will not cordinate the code i think.
Hi @Bond_Man ,
I am going to state this more as an update (since this situation will continue to develop in the next few days).
10 Business Days:
First, on further review, the date that I originally mentioned as the deadline date for 10 business days was not correct.
Since TFL is in Singapore, to be on the safe side, it should use their definition:
-
“‘business day’ means any calendar day other than a Saturday, Sunday, public holiday or bank holiday”
- To be honest, I calculated it from UTC (which would have captured 8/3, since it would have ended at 8:36am before the 9 am cut off), but in all actuality if it is calculated from Singapore time zone, their business day was almost over on 8/3 (4:36pm SST). So, in reality, I was wrong as well, it does not count 8/3, and 8/9 is a holiday in Singapore, so it would be Aug 18th at 5pm SST, which would be Aug 18th at 9am UTC (to be on the safe side, it should be Aug 18th at 4pm UTC [which would begin the following day in Singapore]) .
Update:
So far TFL has merged classic-core PR 784, and cosmos-sdk PR 96 and did pull the classic-core code into a tag for v0.5.21. However, upon review there was a request made, by one of TFL’s developers, in PR 96 for a change, which was submitted in PR 104 (and which is still open). If PR 104 is merged, it would require a rebuild of the classic-core code that is in the tag for v0.5.21 (to capture the change in cosmos-sdk dependency). If that happens, it means that any validators that have installed from that source prior to merge of PR 104 will need to update again after the merge of PR 104 and rebuild. It is not entirely clear if this developer was intending the change request to be part of v0.5.21 or possibly a later release, however they did go ahead and merge the code while waiting for the further PR (104). Personally, I am hopeful that TFL will be able to do this, and distribute before the 10 business days (It is my hope at least). If they do not, and there is a sense that no real options exist for further action on their part, being as gracious as possible, but still being mindful of the block height for delegation stake to existing validators to become available (which also allows for consensus catch-up) and caution around security and people’s money, then the question will be addressed if PR 104 is a necessity (or if it could be a change that has a minimal impact and can be incorporated in a future release). If PR 104 is an absolute necessity, then we would want to keep the options open that the proposal affords to make sure that a smooth and secure distribution happens.
I hope that helps a little better, and of course @ek826 has been closely working on this issue and may have further insights.
3 Likes
I got it now thanks for ur clear respond
2 Likes
Just an update.
It appears that TFL has met their commitment mentioned in this proposal since they have merged, built, and provided a tag for distribution.
Here is the link to a support document for validators that outlines the update process for the code associated with this proposal (now v0.5.22):
I hope you are each doing well today 
7 Likes
Excuse me, We need validators to install the new build and their combined voting power needs to equal 66% or greater. but what would happen otherwise?
A personal update (and Thank You to each of you):
Wow, that felt really good to be able to have governance be completely restored again, and to stake.
Thank you to all the validators, to those who collaborated, for those who worked behind the scenes, and to all who took part in moving this to become a reality again 
Thank you also to TerraForm Labs and to those who contributed in helping to make this a reality.
11 Likes
Thank you.
1 Like
Hello everyone, when can IBC be opened?
Time to bring some balance to the force!
1 Like
Thanks all that helped carry the torch, and to those that had the persistence to see this endeavor cross the finish line.
1 Like
@aeuser999 Hello, could you explain to us BURN TAX activation process?
Blockquote
// TaxPowerUpgradeHeight is when taxes are allowed to go into effect
// This will still need a parameter change proposal, but can be activated
// anytime after this height
const TaxPowerUpgradeHeight = 9346889
The community needs to specify the exact block height at which the 1.2% burn will be implemented
1 Like
With the upgrade done enabling staking the code is in place for the burn tax.
12th September the tax function will be enabled. Once it works at 0.0% Terra Rebels will put a Parameter Change proposal through governance vote and once passed the burn commences at 1.2%
3 Likes
Please I need support with my terra station wallet after delegation was re-enabled I tried to delegate but I was receiving “invalid hex string” error message so I uninstalled terra station and reinstalled it but now I can’t connect my wallet anymore. What I have is private key and the said error message above is what I keep getting when I submit my private key.