Weekly Dev Update #54
THORChain Weekly Dev Update for Week 29 Jul–03 Aug 2020; Testnet4.2 live chain upgrades, Ethereum Support, Explorer
Chain Upgrades
A total of five chain upgrades were pushed in the week, demonstrating both to the team, node operators and community that THORChain’s ability to upgrade its stack, address TSS issues and recover stuck funds without chain halts is extremely versatile:
- KVStore (core data schema)
- Core logic
- Bifrost — Observer logic && Signer logic
- Midgard
- Chain clients
- Stuck funds
Although THORChain can support a chain-halt coordinate upgrade, it was reassuring to see in the vast majority of cases it is not required.
UPDATE 0.2.0
A Mini-token bug caused a mini-token pool to be created, but due to mini-token transfer limits, it could not be moved. The fix was to prevent observing any further mini-tokens and purge the mini-token from the KVstore. This upgraded Midgard, Bifrost and THORChain.
UPDATE 0.2.1
A TSS-related fix to improve reliability. This upgraded Bifrost.
UPDATE 0.3.0
This fixed a Node Bonding Bug (fail to zero out bond on LEAVE), causing nodes to be incorrectly credited funds. This required changes to core logic and the KVStore.
UPDATE 0.3.1
This deployed a new BinanceChain image, as well as fixing TSS syncing issues. This required changes to Binance and Bifrost.
UPDATE 0.4.0
This added BinanceChain Memo Validation and fixed a Vault Migration Bug, recovering stuck funds. Interestingly, most of the nodes that were present in a retired vault had churned out AND back in, before the update was pushed, demonstrating how churned nodes can reconvene to sign TSS transactions.
THORNode
Fixes, upgrades and work for multi-chain.
- Resolve “Test TSS new changes”
- Merge branch ‘565-issue’ into ‘testnet’
- Resolve “[FIX] Bond has not been correctly deduct from the node account after they leave”
- [bugfix] Bond has not been correctly deduct from the node account after they leave
- [feature] chain contracts
- Fix stream reset
- Merge branch ‘fix-stream-reset’ into ‘master’
- Resolve “[ADD] handle account that set memo check flag”
- Merge branch ‘566-issue’ into ‘testnet’
- check 2/3 signer still in the network
- Merge branch ‘574-issue’ into ‘testnet’
- Resolve “[FIX] Retry churn logic is not accurate”

TSS
Some fixes to improve reliability.
Midgard
Fixes, as well as a new history endpoint.
- Resolve “Fix: Pool share factor when totalstaked is greater than totalbond”
- Update testnet V4.1 (Fix poolsharefactor)
- Resolve “Implement continuous aggregation for “pools_history” table”
- Resolve “Implement continuous aggregation for total volume changes”
- Resolve “Reimplement “/v1/history/total_changes” as total_volume”
Infra
Quality of life improvements and stability, as well as support for Digital Ocean.
- Fix AWS cross zone
- Fix helmfiles deployments
- Fix metrics server DigitalOcean
- Add Provider DigitalOcean
- update image
Clients
BEPSwap Client
Numerous UI/UX tweaks based on community feedback
ASGARDEX Client
Work continues to prepare the client for Chaosnet.
Community Work
A dashboard and explorer have been funded and MVPs demoed. They will be unveiled soon.


Audits
A final infrastructure audit is planned post-Chaosnet.
Next Milestones
Testnet 4.2 has been deployed and under-going stress-testing.
Chaosnet is expected once testnet has been fully-validated.
Community
To keep up to date, please monitor community channels, particularly Telegram and Twitter:
- Twitter: https://twitter.com/thorchain_org
- Telegram Community: https://t.me/thorchain_org
- Telegram Announcements: https://t.me/thorchain
- Reddit: https://reddit.com/r/thorchain
- Github: https://github.com/thorchain
- Medium: https://medium.com/thorchain