The Silvergate Bank crisis unfolding in early March 2023 — with Bitcoin at $22,435 and Ethereum at $1,564 — has highlighted a critical gap in many crypto investors’ toolkits: the ability to independently audit counterparty risk using on-chain data. While traditional finance relies on credit agencies and regulatory filings, crypto offers the unprecedented ability to trace funds and assess risk in real-time. This advanced tutorial walks through the methodologies for conducting your own on-chain risk audits.
The Objective
This tutorial aims to equip experienced crypto users with the tools and techniques needed to evaluate counterparty risk across DeFi protocols, centralized exchanges, and banking infrastructure. By the end, you will understand how to use blockchain explorers, on-chain analytics platforms, and smart contract verification tools to build a comprehensive risk profile of any crypto platform you interact with.
The Silvergate situation provides an excellent case study. The bank’s collapse was foreshadowed by observable on-chain metrics: large stablecoin movements between exchanges, changes in exchange wallet balances, and shifts in DeFi total value locked. These signals were available to anyone with the skills to read them.
Prerequisites
Before beginning this tutorial, you should have the following:
Technical knowledge: Familiarity with Ethereum and Bitcoin blockchain explorers (Etherscan, BTC.com), basic understanding of smart contract interactions, and experience with DeFi protocols. You should understand how ERC-20 token transfers work and be comfortable reading transaction logs.
Tools: Access to Etherscan (free), Dune Analytics (free tier), Nansen or Arkham Intelligence (for institutional-grade analysis), and a spreadsheet application for tracking your findings. A Web3 wallet like MetaMask is needed for direct contract interaction.
Conceptual foundation: Understanding of Total Value Locked (TVL), liquidity pools, smart contract risk categories (oracle risk, governance risk, admin key risk), and the distinction between on-chain and off-chain counterparty risk.
Step-by-Step Walkthrough
Step 1: Map the target entity’s on-chain footprint. Start by identifying the known wallet addresses associated with the platform you are auditing. For exchanges, Etherscan’s “Verified Addresses” feature and Nansen’s entity labeling system can identify hot wallets, cold storage, and treasury addresses. Document every address and its function.
Step 2: Analyze capital flows and concentration. Using Dune Analytics or Nansen, trace the movement of major assets (ETH, USDC, USDT, WBTC) through the entity’s wallets over the past 90 days. Large, sudden outflows — like the $8.1 billion in deposit outflows that preceded Silvergate’s collapse — are critical warning signals. Look for patterns of capital migration to unknown addresses or sudden shifts in wallet balances.
Step 3: Evaluate smart contract dependencies. For DeFi protocols, map every external contract dependency using tools like Solidity Finance or Slither. Identify oracle dependencies (Chainlink, Uniswap TWAPs), governance mechanisms, and admin key configurations. Protocols with single-admin keys or centralized governance structures carry higher counterparty risk than those with distributed governance through DAOs or multi-signature wallets.
Step 4: Cross-reference with off-chain indicators. On-chain data becomes most powerful when combined with off-chain intelligence. Monitor SEC EDGAR filings for banking partners, track stock prices of publicly traded crypto companies, and set up Google Alerts for key entities. The Silvergate crisis demonstrated that a single delayed SEC filing (the 10-K annual report on March 1, 2023) can trigger cascading on-chain effects.
Step 5: Build a risk scorecard. Compile your findings into a structured risk assessment covering liquidity risk, smart contract risk, governance risk, counterparty risk, and regulatory risk. Assign quantitative scores where possible — for example, the percentage of TVL concentrated in a single liquidity pool, or the number of days since the last smart contract audit.
Troubleshooting
Problem: Cannot find wallet addresses for the target entity. Solution: Start with a known transaction (such as a recent withdrawal from the platform) and trace the sending address through its transaction history. Label addresses as you discover them.
Problem: On-chain data is noisy with automated market-making activity. Solution: Filter out known smart contract interactions (Uniswap router, Aave lending pool) and focus on unusual or large transfers. Use Dune Analytics to build custom queries that exclude routine DeFi operations.
Problem: Cross-chain analysis is needed but data is fragmented. Solution: Use multi-chain explorers like Zapper or DeBank that aggregate positions across Ethereum, BNB Chain, Polygon, Arbitrum, and other networks. The total risk picture requires visibility across all chains where the entity operates.
Mastering the Skill
Advanced on-chain risk auditing is an ongoing practice, not a one-time exercise. Set up automated monitoring using Dune Alerts or Nansen Smart Alerts to track significant changes in the entities you have audited. Review and update your risk scorecards quarterly, or immediately following major market events like the Silvergate collapse.
The most skilled on-chain analysts combine technical proficiency with market intuition — understanding not just what the data shows, but what it means in the context of broader market dynamics. As the crypto industry continues to navigate the tension between decentralization and the practical need for fiat on-ramps, the ability to independently assess counterparty risk will become an increasingly valuable skill.
Disclaimer: This article is for educational purposes only and does not constitute financial or investment advice. On-chain analysis has limitations and should be used as one component of a broader due diligence process.
on-chain analytics caught the silvergate outflows way before the 10-k delay. large stablecoin movements between exchanges were the canary in the coal mine
segfault the stablecoin movements between exchange wallets were visible on etherscan for anyone watching. glassnode made it easier but the data was always public
Good tutorial. Would add that checking exchange reserve changes on Glassnode or CryptoQuant gives you a head start on counterparty stress before it hits the news cycle.
cryptoquant net flows plus the exchange reserve ratio on glassnode gave like a 48 hour heads up on the silvergate situation. free tools, people just need to look
Tomasz N. good point on exchange reserves. cryptoquant has a free tier that shows net flows, enough for basic counterparty monitoring
the Silvergate timeline is the best argument for on-chain auditing. their stock was dropping for 3 weeks but stablecoin outflows showed the actual stress 48 hours before the wire halt
checking the Silvergate SEN exposure through stablecoin flows was clever. most people only looked at stock price
the SEN exposure map was public too. silvergate had been publishing their client list for quarters. the data was screaming at anyone who bothered to read it
the SEN client list was basically a counterparty risk map. anyone who actually read it could trace which exchanges would feel the squeeze first. pure public data, zero people acting on it
the SEN client list was public but nobody connected the dots until after the collapse. having data and acting on it are two different things
having the data and acting on it are completely different skills. SEN outflows were visible for weeks. the industry watched Silvergate bleed in slow motion and still got caught holding bags