diff --git a/public/images/tip20/virtual-addresses-dark.png b/public/images/tip20/virtual-addresses-dark.png new file mode 100644 index 00000000..e07754c3 Binary files /dev/null and b/public/images/tip20/virtual-addresses-dark.png differ diff --git a/public/images/tip20/virtual-addresses-light.png b/public/images/tip20/virtual-addresses-light.png new file mode 100644 index 00000000..dbf3f21b Binary files /dev/null and b/public/images/tip20/virtual-addresses-light.png differ diff --git a/src/pages/protocol/tip20/virtual-addresses.mdx b/src/pages/protocol/tip20/virtual-addresses.mdx index 870c9841..2a4b3d06 100644 --- a/src/pages/protocol/tip20/virtual-addresses.mdx +++ b/src/pages/protocol/tip20/virtual-addresses.mdx @@ -18,18 +18,8 @@ Without virtual addresses, per-customer deposit addresses are operationally expe With virtual addresses, the customer-facing address is still unique, but it behaves like a routing alias. The protocol resolves it to the registered master wallet during the TIP-20 transfer itself. - B1[Separate onchain balance] - B1 --> S1[Sweep transaction] - S1 --> M1[Master wallet] - end - - subgraph B[With virtual addresses] - D2[Customer virtual address] --> F2[TIP-20 forwarding] - F2 --> M2[Master wallet] - end -`} /> +Without virtual addresses, each customer deposit address holds a separate onchain balance that must be swept to the master wallet. With virtual addresses, TIP-20 forwarding routes deposits directly to the master wallet. +Without virtual addresses, each customer deposit address holds a separate onchain balance that must be swept to the master wallet. With virtual addresses, TIP-20 forwarding routes deposits directly to the master wallet. This means: