We’ve made some progress…
Feel free to click around the demo and let us know your feedback. Once the user experience is easy enough for folks to follow + understand, then we can look at connecting it up with what’s on Tron Blockchain.
This looks awesome now
All the best
This looks great 
I love it
Interesting, very nice:clap: 
Buen trabajo, te felicito
Hey all,
Important Advisory.
For transparency, this is to inform everyone that the private key of our Protocols’ main deployer was recently discovered to be compromised. As a result we no longer have access/control over the contracts deployed. The permissions on the account was switched to an unknown inactive address:
As there were no live users of the protocols on mainnet - for both goStables and Sorrel (beside myself) fortunately, no external users were affected by this incident.
We have since made some of our Github repositories private for now, as we want to ensure that our UI isn’t used with ill intent.
The next steps are to be decided whether we redeploy everything under a new multisig based account, renouncing ownership of key contracts upon redeployment or consider this project to be at its end.
This message report was submitted to Tronscan:
The private key for our project address TCiJCtTBhGSw8mMYYts67vCXUjdoFLLuYw has been compromised. On June 23rd I discovered (after a failed transfer attempt) an address TTirJPviQxVmEzPJG3yM84NnAGxeJSx4rU took over the permissions of our projects’ deployer account. Upon checking further it was found that the transaction to change permissions took place on the 20th and was switched to this inactivated account. I no longer have access to the account, its tokens/funds and deployed contracts. Apologies for posting a screen from tronscan as you’ve mentioned not to, but this is the only proof I have of and its a mandatory field to submit.
So you lost over 4000 usd in value 
. So you have any idea what might cause the overtake?
Yes we do.
Upon further investigation I determined that this was a case of human error on my part and also a hard lesson learned. While working on the new Sorrel Wallet within this past week, a private key was accidentally pushed to a then public repo on Github. This resulted in the incident.
I understand this diminishes trust and confidence in what we’ve been building. We can discontinue our work based on this or we can keep building forward with more stringent checks and practices in place…
I did the same mistake my luck let’s say it was that the value and the importance of the wallet was minuscule(still lost some funds)! Starting from that time I keep my repos private(as much as possible) and use the imports from env files.
Really appreciate the transparency not many people have the strength to admit that they did a mistake. I know it’s frustrating! But this shows real professionalism and I appreciate that!
Only those who do not build do not know about these mistakes don’t worry the work you did so far is outstanding and that could not be taken from you in any way at all.
Stay strong and keep building!
I checked all projects before season 5. And easily I can say that your description video is great by far than other teams. Will you join to season 5 also?
Thanks for the feedback! I am considering joining S5 also. What will be submitted is to be decided. After the incident in my last post, I took a break from the code to chill, clear my mind and explore next steps. Will provide further updates soon. Thanks for the support all 
That will be great, cant wait for what you have to offer. Wishing you all the best.
Hey all,
Sorrel’s primary depository contract has been redeployed to mainnet and accessible via the dapp.
The comptrollers that enable energy free transactions will be deployed in the future when there’s available shared resources to support them.
Development of Sorrel continues…
Thanks for the support!
This is quite impressive and very glad you keep building.
Keep up the good work brother. Sorrel to the world
Congratulations for reaching this great milestone,… keep on building, the future is bright 
