Update regarding the Glitch Bridge—. We've identified the root cause of the issue and fixed it via technical countermeasures.
25 Aug 2022, 05:30
Update regarding the Glitch Bridge—
We've identified the root cause of the issue and fixed it via technical countermeasures. We've also re-defined our standard operating procedures for managing the servers with sensitive code. We are currently executing external tests on the newly impacted changes and we plan to deploy the bridge again next week.
— Diego E. Cruces, CTO, Glitch Finance
Twitter:
Same news in other sources
125 Aug 2022, 05:30
Update regarding the Glitch Bridge—
We've identified the root cause of the issue and fixed it via technical countermeasures. We've also re-defined our standard operating procedures for managing the servers with sensitive code. We are currently executing external tests on the newly impacted changes and we plan to deploy the bridge again next week.
— Diego E. Cruces, CTO, Glitch Finance
Twitter:
Update regarding the Glitch Bridge—. We've identified the root cause of the issue and fixed it via technical countermeasures.
Update regarding the Glitch Bridge—
We've identified the root cause of the issue and fixed it via technical countermeasures. We've also re-defined our standard operating procedures for managing the servers with sensitive code. We are currently executing external tests on the newly impacted changes and we plan to deploy the bridge again next week.
— Diego E. Cruces, CTO, Glitch Finance
Twitter: https://twitter.com/GlitchProtocol/status/1562673642957205505