Twitxy Saved

Taurus

Verified account This account is verified. Learn more

@taurus_hq

The full stack of digital assets solutions: custody, tokenization, trading. Global leading infrastructure provider for financial institutions
Switzerland taurushq.com Joined June 2018
3 Following 5.8K Followers 592 Posts

Latest posts 5

Taurus Verified account @taurus_hq
Binance lost about USD 6.3 billion without losing a single private key.

On 29 October, attackers drained Binance hot wallets on 10 blockchains, most of it within about 20 minutes. Binance reports no evidence that any private key was stolen. Instead, attackers obtained signatures directly from its signing service, outside the normal withdrawal flow and its policy controls.

For banks and other financial institutions running digital asset infrastructure, the incident raises important questions about:
馃敼 How signing policies are enforced
馃敼 Who can authorize transactions
馃敼 How security controls hold up when systems or credentials are compromised

In our latest technical analysis, Taurus' security team and CTO office examine six security principles that financial institutions should review.

We also explain how we approach each in Taurus-PROTECT and share five practical questions to ask your internal teams and technology providers.

馃摉 Read the full analysis: eu1.hubs.ly/H0zYdrF0
Taurus Verified account @taurus_hq
Binance hack explained.

Figure 1. What Binance set-up should be based on our understanding of the events (outside-in) and a transaction lifecycle.

1. Transaction service: creates transactions and waits until right quorum of approvals is made

2. Transaction Policy controls: policy engine that checks transactions authorized and right policy controls / validations made (before signature)

3. Signing infrastructure: where keys are stored and protected; where blockchain transaction signatures (with private keys) actually take place

4. Broadcasting: node infrastructure that broadcasts signed transactions