<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Basis Desk</title>
    <description>The latest articles on DEV Community by Basis Desk (@basisdesk).</description>
    <link>https://dev.to/basisdesk</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4151000%2Feac40eae-929b-4f33-b0f9-d511c332de2e.png</url>
      <title>DEV Community: Basis Desk</title>
      <link>https://dev.to/basisdesk</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/basisdesk"/>
    <language>en</language>
    <item>
      <title>Uniswap v4 Hooks and Singleton Architecture, Explained</title>
      <dc:creator>Basis Desk</dc:creator>
      <pubDate>Fri, 20 Nov 2026 04:31:21 +0000</pubDate>
      <link>https://dev.to/basisdesk/uniswap-v4-hooks-and-singleton-architecture-explained-4kp1</link>
      <guid>https://dev.to/basisdesk/uniswap-v4-hooks-and-singleton-architecture-explained-4kp1</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — &lt;a href="https://basisdesk.news/about/how-we-use-ai?utm_source=devto" rel="noopener noreferrer"&gt;how we use AI&lt;/a&gt;. Originally published on &lt;a href="https://basisdesk.news/learn/uniswap-v4-hooks-and-singleton?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Uniswap v4 replaces isolated pool contracts with a single unified ledger, using flash accounting and custom hook plugins to cut routing costs and enable programmable automated market makers.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Key points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Uniswap v4 moves all trading pools into a single contract called the PoolManager, ending the isolated pair-contract model.&lt;/li&gt;
&lt;li&gt;Flash accounting uses transient storage to track multi-hop swap obligations in memory, transferring only net token balances at the end.&lt;/li&gt;
&lt;li&gt;Hooks are plug-in smart contracts that run custom logic before or after pool actions, enabling dynamic fees, TWAMMs, and compliance checks.&lt;/li&gt;
&lt;li&gt;Pool security is no longer uniform: flaws in third-party hook code can put capital at risk even if the core PoolManager is secure.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Uniswap v4 restructures decentralized exchange mechanics by holding all trading pairs inside one unified contract, rather than deploying individual contracts for every asset pair. This architectural shift, known as the &lt;strong&gt;singleton architecture&lt;/strong&gt;, relies on a balance-settlement system called &lt;strong&gt;flash accounting&lt;/strong&gt; that tracks net obligations before moving tokens across the network. Alongside this consolidation, Uniswap v4 introduces &lt;strong&gt;hooks&lt;/strong&gt;, which are modular smart contracts that execute custom code at specific lifecycle points of a trade or liquidity adjustment.&lt;/p&gt;

&lt;p&gt;Automated market makers (AMMs) have traditionally relied on discrete, immutable contracts for each market pair. In earlier versions of Uniswap, adding features like dynamic fees, conditional routing, or customized order execution required deploying entirely distinct protocols or writing complex wrapper contracts. Uniswap v4 standardizes extensibility, transforming the underlying exchange into an execution platform where developers can alter swap mechanics without fragmenting liquidity.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Shift to a Singleton Architecture
&lt;/h2&gt;

&lt;p&gt;In decentralized finance, an automated market maker allows users to trade digital assets using pools of tokens managed by mathematical formulas instead of centralized order books. In Uniswap v1, v2, and v3, each token pair lived in its own isolated smart contract. Deploying a new market required creating a factory contract instance, incurring significant execution overhead known as gas fees on the host blockchain.&lt;/p&gt;

&lt;p&gt;Uniswap v4 replaces this distributed model with a single master contract—the PoolManager. Every liquidity pool, whether trading $ETH against $USDC or between exotic tokens, exists as internal state within this single deployment. Concentrated liquidity mechanics introduced in previous versions, where liquidity providers allocate capital within custom price intervals, are retained inside this unified state (explained further in &lt;a href="https://basisdesk.news/learn/concentrated-liquidity-uniswap-v3-v4" rel="noopener noreferrer"&gt;Concentrated Liquidity: Uniswap v3 and v4, Explained&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;By keeping all pool balances under one roof, pool deployment costs drop substantially. Instead of generating a new contract with its own storage and deployment footprint, creating a pool in v4 requires only initializing a new storage key inside the PoolManager.&lt;/p&gt;

&lt;h2&gt;
  
  
  Flash Accounting and Net Settlement
&lt;/h2&gt;

&lt;p&gt;Under earlier architectures, executing a multi-hop trade—such as swapping Asset A for Asset B, and then Asset B for Asset C—meant physically transferring tokens into and out of successive contracts. Swapping through three separate pairs required multiple independent token transfers across distinct storage slots, consuming computational gas for each leg.&lt;/p&gt;

&lt;p&gt;Uniswap v4 adopts flash accounting, an execution method supported by the Ethereum network's transient storage capabilities (standardized as EIP-1153). Under flash accounting, the PoolManager maintains an internal balance sheet of net debits and credits throughout the execution of a transaction. Intermediate transfers are calculated entirely within temporary memory.&lt;/p&gt;

&lt;p&gt;Tokens only physically move when the entire transaction sequence finishes. If a trader initiates a swap involving multiple intermediate pools, the contract records the intermediate balance changes without touching the underlying token contracts. At the conclusion of the execution block, the contract verifies that all accounts square to zero. The user transfers the initial token into the contract, and the contract transfers the final output token to the user.&lt;/p&gt;

&lt;p&gt;Consider a numerical example of a multi-hop swap under both paradigms. Assume an investor swaps 10,000 $USDC for $ETH, which is immediately traded for 2 $WBTC across two separate pools. &lt;/p&gt;

&lt;p&gt;In a multi-contract architecture:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The user transfers 10,000 $USDC to the USDC/ETH contract.&lt;/li&gt;
&lt;li&gt;The USDC/ETH contract computes the swap and sends 3.0 $ETH to the ETH/WBTC contract.&lt;/li&gt;
&lt;li&gt;The ETH/WBTC contract receives the 3.0 $ETH, executes the trade, and sends 2.0 $WBTC to the user.
Total external transfers: 3 distinct token interactions, each altering external smart contract storage states.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;In the Uniswap v4 singleton architecture with flash accounting:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The PoolManager logs an internal debit of 10,000 $USDC, a transient credit and immediate debit of 3.0 $ETH, and a credit of 2.0 $WBTC.&lt;/li&gt;
&lt;li&gt;The system checks that the net obligation of the intermediate asset ($ETH) is zero.&lt;/li&gt;
&lt;li&gt;Exactly two token balance updates occur on the external network: 10,000 $USDC moves from the user into the PoolManager, and 2.0 $WBTC moves from the PoolManager to the user. The intermediate asset never triggers an external state update.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  How Hooks Alter Pool Behavior
&lt;/h2&gt;

&lt;p&gt;Hooks are external smart contracts called by the core PoolManager at predetermined checkpoints during pool interactions. By defining custom logic that executes before or after a swap, or before or after liquidity is added or removed, developers can build complex financial instruments directly inside a standard pool.&lt;/p&gt;

&lt;p&gt;The v4 architecture exposes eight primary hook entry points:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;beforeInitialize&lt;/code&gt; and &lt;code&gt;afterInitialize&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;beforeAddLiquidity&lt;/code&gt; and &lt;code&gt;afterAddLiquidity&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;beforeRemoveLiquidity&lt;/code&gt; and &lt;code&gt;afterRemoveLiquidity&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;beforeSwap&lt;/code&gt; and &lt;code&gt;afterSwap&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A hook contract can interact with one, several, or none of these execution points depending on its design. For example, a developer can create a pool where the swap fee adjustments occur algorithmically before each trade executes, or where fees are redirected toward continuous liquidity incentives.&lt;/p&gt;

&lt;p&gt;Hooks enable a range of custom behaviors that previously required separate standalone protocols:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Time-Weighted Average Market Makers (TWAMM):&lt;/em&gt; Large orders can be automatically sliced into smaller virtual transactions over predefined time blocks, reducing price impact without requiring manual intervention or off-chain bot execution.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Dynamic Swap Fees:&lt;/em&gt; Instead of fixed fee tiers, hooks can adjust fees dynamically based on market volatility, trading volume, or external price oracles, aligning liquidity compensation with market conditions.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Permissioned and KYC Pools:&lt;/em&gt; Institutional liquidity pools can enforce compliance checks. A hook can query an identity registry prior to executing a trade or admitting liquidity, verifying that the counterparty meets defined legal standards or regulatory certifications without modifying the protocol's base layer.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Limit Orders:&lt;/em&gt; Hooks can accept orders that execute only when the pool's spot price crosses a designated threshold, functioning similarly to traditional limit orders without centralized order matching engines.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Out-of-Pool Routing:&lt;/em&gt; Hooks can be structured to aggregate or cross-reference external liquidity sources alongside internal pools during execution, expanding routing paths beyond isolated automated reserves (as seen in developments covered in &lt;a href="https://basisdesk.news/news/uniswap-v4-launches-aggregator-hooks-external-dex-liquidity" rel="noopener noreferrer"&gt;Uniswap v4 Launches Aggregator Hooks to Route External DEX Liquidity&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  Governance, Fees, and Licensing
&lt;/h2&gt;

&lt;p&gt;While hooks introduce broad flexibility, Uniswap v4 maintains protocol-level parameters governed by the Uniswap DAO. The governance layer preserves the ability to collect a protocol fee on pools, though the base architecture allows pools to operate with zero protocol-level fees by default unless explicitly enabled through governance votes.&lt;/p&gt;

&lt;p&gt;Individual pools can determine their own fee strategies via hooks. A hook may charge a swap fee, deposit fee, or dynamic withdrawal fee that accrues directly to liquidity providers or hook developers. The coexistence of protocol-level governance rights with decentralized hook autonomy establishes a two-tiered economic model: protocol governance oversees the foundational settlement engine, while hook creators set competitive operational rules for specific markets.&lt;/p&gt;

&lt;p&gt;Uniswap v4 launched under a Business Source License (BSL), a software license that limits commercial production use for a designated period before transitioning permanently to an open-source license like GPL. This licensing model protects the foundational codebase during its initial deployment cycle while providing the ecosystem access to review, test, and develop extensions on public testnets and development environments.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common Misconceptions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Misconception: All Uniswap v4 pools have the same security profile.&lt;/strong&gt;&lt;br&gt;
Because hooks allow arbitrary smart contract code execution, the security of a specific pool depends on the hook attached to it. A flaw, vulnerability, or malicious backdoor inside an unverified hook contract can compromise user funds deposited in that specific pool, even if the underlying Uniswap v4 PoolManager is fully secure.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Misconception: Flash accounting eliminates all transaction costs.&lt;/strong&gt;&lt;br&gt;
Flash accounting significantly lowers computational overhead by eliminating intermediate token transfers during complex multi-hop routes. However, users still pay base execution costs for interacting with the blockchain, moving the final tokens, and paying for whatever computational complexity is introduced by the active hook plugins.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Misconception: Hooks can be added or swapped out of existing pools at will.&lt;/strong&gt;&lt;br&gt;
Pool configuration, including its assigned hook contract address, is immutable once initialized. If a hook contains an error or developers wish to update its logic, a new pool must be deployed, and liquidity providers must migrate their assets to the new pool. Hooks can only implement upgradeability if their internal contract code was deliberately written with proxy patterns from the outset.&lt;/p&gt;

&lt;h2&gt;
  
  
  How This Connects to the Market
&lt;/h2&gt;

&lt;p&gt;The architectural model established by Uniswap v4 influences both liquidity fragmentation and application development across decentralized finance. By collapsing separate pool contracts into a singleton, capital efficiency improves for automated trading infrastructure, while routing algorithms face fewer state-access bottlenecks on the host blockchain.&lt;/p&gt;

&lt;p&gt;For institutional capital, programmable hooks provide a pathway to participate in decentralized automated market makers within clear compliance parameters. Because a hook can mandate identity verification before processing trades, regulated market makers can provide liquidity within walled, compliant pools that still benefit from the battle-tested settlement logic of the underlying protocol. This intersection of permissioned access and decentralized execution continues to shape institutional adoption across US, UK, and EU capital markets.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What is the primary difference between Uniswap v3 and Uniswap v4?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Uniswap v3 deploys an independent smart contract for every market pair, requiring physical token transfers between contracts during multi-hop swaps. Uniswap v4 consolidates all pools into a single contract and uses modular hook contracts to customize trading features.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How does flash accounting reduce transaction fees?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Instead of executing separate on-chain token transfers for every intermediate leg of a multi-pool trade, flash accounting calculates net debits and credits in transient storage. Tokens are only transferred once at the completion of the trade sequence.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can a malicious hook steal funds from other Uniswap v4 pools?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. The core PoolManager isolates liquidity between different pool identifiers. An exploit in a specific hook contract affects only the users and liquidity providers interacting with the pool bound to that hook.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What features can developers build with hooks?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Developers can implement time-weighted average market makers (TWAMM), dynamic volatility-adjusted fees, native on-chain limit orders, automated liquidity rebalancing, and identity or KYC verification checks.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://eips.ethereum.org/EIPS/eip-1153" rel="noopener noreferrer"&gt;EIP-1153: Transient Storage Opcodes&lt;/a&gt; — Ethereum Improvement Proposals&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://developers.uniswap.org/docs/protocols/v4/overview" rel="noopener noreferrer"&gt;Uniswap v4 Documentation&lt;/a&gt; — Uniswap Labs&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://app.uniswap.org/whitepaper-v4.pdf" rel="noopener noreferrer"&gt;Uniswap v4 Core Whitepaper&lt;/a&gt; — Uniswap Labs&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;&lt;a href="https://basisdesk.news?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt; is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: &lt;a href="https://basisdesk.news/developers?utm_source=devto" rel="noopener noreferrer"&gt;basisdesk.news/developers&lt;/a&gt;. Not investment advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>defi</category>
      <category>web3</category>
      <category>cryptocurrency</category>
      <category>beginners</category>
    </item>
    <item>
      <title>ERC-3643 and Permissioned RWA Standards, Explained</title>
      <dc:creator>Basis Desk</dc:creator>
      <pubDate>Fri, 20 Nov 2026 02:31:54 +0000</pubDate>
      <link>https://dev.to/basisdesk/erc-3643-and-permissioned-rwa-standards-explained-1n9d</link>
      <guid>https://dev.to/basisdesk/erc-3643-and-permissioned-rwa-standards-explained-1n9d</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — &lt;a href="https://basisdesk.news/about/how-we-use-ai?utm_source=devto" rel="noopener noreferrer"&gt;how we use AI&lt;/a&gt;. Originally published on &lt;a href="https://basisdesk.news/learn/erc-3643-t-rex-permissioned-tokens?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Tokenized real-world assets demand compliance at the smart contract level. The ERC-3643 standard, built on the T-REX framework, uses decentralized identity registries to enforce automated transfer restrictions.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Key points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;ERC-3643 is an open Ethereum standard that uses smart contracts to enforce regulatory compliance for tokenized securities.&lt;/li&gt;
&lt;li&gt;The ONCHAINID framework binds wallet addresses to decentralized identities containing cryptographic claims, keeping private PII off the blockchain.&lt;/li&gt;
&lt;li&gt;Every transaction executes a conditional check via a Compliance Engine, automatically rejecting transfers to unverified or unauthorized wallets.&lt;/li&gt;
&lt;li&gt;The standard includes native asset recovery functions, allowing issuers to reissue tokens if an investor loses their private keys or faces court actions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Traditional financial assets require identity verification, regulatory clearances, and geographic restrictions before they change hands. Standard cryptocurrency tokens, by contrast, prioritize permissionless execution, allowing any wallet to send balances to any other wallet without intermediaries. The &lt;strong&gt;ERC-3643&lt;/strong&gt; standard bridges this divide by embedding automated compliance controls directly into Ethereum smart contracts, enabling institutions to tokenize securities while adhering to securities regulations.&lt;/p&gt;

&lt;p&gt;Originally developed under the name T-REX (Token for Regulated EXchanges), ERC-3643 establishes an open protocol for permissioned tokens. Unlike conventional tokens that execute transfers purely based on cryptographic signatures and token balances, ERC-3643 evaluates identity registries, qualification claims, and rule compliance engines before any ledger balance updates.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Standard Token Formats Fail for Securities
&lt;/h2&gt;

&lt;p&gt;Public blockchains operate primarily on permissionless accounting models. As detailed in our breakdown of &lt;a href="https://basisdesk.news/learn/erc20-erc721-erc1155-standards" rel="noopener noreferrer"&gt;Ethereum token standards like ERC-20, ERC-721, and ERC-1155&lt;/a&gt;, an ERC-20 contract executes a transfer if the sender possesses sufficient balance and authorizes the transaction. The smart contract does not inspect the citizenship, accreditation status, or sanctions standing of the recipient address.&lt;/p&gt;

&lt;p&gt;Financial regulators—including the Securities and Exchange Commission (SEC) in the United States, the European Securities and Markets Authority (ESMA) in the European Union, and the Financial Conduct Authority (FCA) in the United Kingdom—require issuers of private placements, corporate bonds, and real estate equity to verify purchaser identities. Issuers must prevent unlawful secondary transfers to non-accredited individuals or sanctioned jurisdictions. If a regulated security exists as a standard ERC-20 token on a public network, an investor could transfer that asset to an anonymous wallet in an embargoed country, creating non-compliance liabilities for the issuer.&lt;/p&gt;

&lt;p&gt;ERC-3643 solves this problem without compromising blockchain settlement finality. Instead of storing tokens in walled centralized databases or custodial accounts, issuers retain programmatic control over individual token transfers on public networks.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Architecture of ERC-3643 and ONCHAINID
&lt;/h2&gt;

&lt;p&gt;The ERC-3643 framework decouples investor identification from individual wallet addresses. This separation is handled through four core architectural components: the token contract, the identity registry, the claim topics registry, and the compliance engine.&lt;/p&gt;

&lt;p&gt;The foundation of investor eligibility is &lt;strong&gt;ONCHAINID&lt;/strong&gt;, a decentralized identity system built on top of the ERC-734 and ERC-735 identity standards. Under this architecture, each participant in an asset's lifecycle deploys an individual smart contract that serves as their digital identity. This contract does not store raw personally identifiable information (PII) such as passports, home addresses, or tax identification numbers. Storing sensitive data on a public ledger creates severe data protection risks under regulations such as the General Data Protection Regulation (GDPR) in the European Union.&lt;/p&gt;

&lt;p&gt;Instead, trusted qualification authorities deploy cryptographic assertions, known as &lt;strong&gt;claims&lt;/strong&gt;, directly to the investor's identity contract. A claim functions as a digital signature verifying that the owner meets specific criteria, such as passing Know Your Customer (KYC) reviews, residing in an eligible country, or qualifying as an accredited investor.&lt;/p&gt;

&lt;p&gt;The Identity Registry contract links an investor's public wallet address to their ONCHAINID contract. When an issuer creates a tokenized security using ERC-3643, the token references this Identity Registry. The token contract does not evaluate raw user documents; it queries the registry to determine whether a valid identity contract exists for the target wallet and whether an authorized third party has attested to the required claims.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Transfer Approvals Work in Practice
&lt;/h2&gt;

&lt;p&gt;Every time a transfer is initiated under ERC-3643, the smart contract executes a conditional pre-flight check before adjusting balances. This check is governed by a dedicated &lt;strong&gt;Compliance Engine&lt;/strong&gt; contract.&lt;/p&gt;

&lt;p&gt;When address A attempts to transfer an asset to address B, the token invokes an internal check function: &lt;code&gt;canTransfer(address _from, address _to, uint256 _amount)&lt;/code&gt;. The function evaluates two distinct operational layers: user eligibility and asset-level compliance rules.&lt;/p&gt;

&lt;p&gt;First, the Identity Registry verifies that both address A and address B are bound to valid ONCHAINID contracts. Next, it verifies that both identities contain valid claims from approved issuers. If the token requires claims for Topic 1 (KYC/AML approval) and Topic 2 (Accredited Investor status), the transfer immediately reverts if either party lacks those cryptographic attestations.&lt;/p&gt;

&lt;p&gt;Second, the Compliance Engine evaluates programmatic market rules established by the token issuer. These rules might limit the maximum number of legal shareholders residing in a specific country, cap the percentage of supply a single investor can accumulate, or enforce minimum holding lock-up periods. If both conditions pass, the contract processes the transfer. If either fails, the transaction reverts, consuming network execution gas but leaving the token balances unchanged.&lt;/p&gt;

&lt;h2&gt;
  
  
  A Worked Example: Cross-Border Equity Settlement
&lt;/h2&gt;

&lt;p&gt;To understand how these components interact, consider a tokenized commercial real estate debt offering issued under US Regulation D (Rule 506(c)) and Regulation S. &lt;/p&gt;

&lt;p&gt;Assume the issuer establishes the following conditions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Identity requirements: Must hold Claim 101 (KYC verified by an approved agency) and Claim 102 (Accredited Investor certification).&lt;/li&gt;
&lt;li&gt;Compliance Engine limits: A mandatory 365-day holding lock-up for secondary transfers between US citizens, and a cap of 2,000 maximum non-accredited European participants under cross-border rules.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Investor Alice purchases 10,000 tokens of the offering on Day 1. Alice completes identity verification through a certified compliance provider, who writes a cryptographic signature corresponding to Claim 101 and Claim 102 to Alice's ONCHAINID. Alice's primary Ethereum wallet is registered to her ONCHAINID in the token's Identity Registry.&lt;/p&gt;

&lt;p&gt;Six months later (Day 182), Alice initiates an on-chain transaction to transfer 5,000 tokens to Bob. Bob is also a US citizen who has completed KYC verification and holds Claim 101 and Claim 102 in his ONCHAINID.&lt;/p&gt;

&lt;p&gt;When the token contract processes Alice's transaction, it queries the Identity Registry. Both Alice and Bob are confirmed as verified participants. However, when the token calls the Compliance Engine, the engine inspects the asset-level rules. Because the holding period between US investors is set to 365 days, and only 182 days have elapsed since Alice's initial acquisition, the transaction fails. The smart contract triggers an execution revert, outputting an error code indicating a rule lock-up violation.&lt;/p&gt;

&lt;p&gt;On Day 366, Alice attempts the identical transaction. The contract queries the Identity Registry, verifies that Alice and Bob remain valid claim holders, confirms that the 365-day lock-up timer has expired, and permits the balance transfer. Bob receives the 5,000 tokens on-chain without the issuer manually reviewing the settlement.&lt;/p&gt;

&lt;h2&gt;
  
  
  Administrative Controls: Recovery and Legal Freezes
&lt;/h2&gt;

&lt;p&gt;Real-world securities regulations require issuers to maintain mechanisms for legal intervention. If an investor loses their private keys, becomes subject to an asset forfeiture order from a court, or is placed on an active international sanctions list, the issuer must have the technical capability to intervene.&lt;/p&gt;

&lt;p&gt;Permissionless formats do not allow third-party intervention; losing a private key permanently locks the underlying tokens. ERC-3643 addresses this requirement through role-based recovery and freeze functions assigned to the issuer or designated compliance agents.&lt;/p&gt;

&lt;p&gt;If an investor establishes through external legal procedures that their wallet key has been compromised, the issuer can call the contract's recovery module. The smart contract invalidates the old wallet address in the Identity Registry, binds the investor's verified ONCHAINID to a newly generated wallet address, burns the tokens at the compromised address, and mints an equivalent balance to the replacement wallet. Because all identity assertions and historical records remain intact within the ONCHAINID contract, the investor's transaction history and legal entitlement are preserved.&lt;/p&gt;

&lt;p&gt;Similarly, if an authority issues a freezing order, an issuer can pause transfers for an individual wallet without freezing the entire token contract. Standard ERC-20 implementations that support freezing (such as major centralized stablecoins) typically rely on an internal address blacklist. ERC-3643 standardizes these intervention mechanics across all compliant security tokens, establishing an auditable ledger trail for regulatory filings.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common Misconceptions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  ERC-3643 compromises investor privacy on public ledgers
&lt;/h3&gt;

&lt;p&gt;A common assumption is that permissioned standards publish sensitive identification data to public blocks. In practice, the ONCHAINID architecture stores no personally identifiable information on the blockchain. The ledger stores only cryptographic hashes and digital signatures issued by trusted compliance entities. External observers can see that an address holds an accreditation assertion from a recognized verification agency, but they cannot read the investor's name, financial statements, or residential address.&lt;/p&gt;

&lt;h3&gt;
  
  
  Permissioned tokens run only on private blockchains
&lt;/h3&gt;

&lt;p&gt;While ERC-3643 can be deployed on private or consortium networks, it is optimized for deployment on public networks such as Ethereum. Because the compliance checks are hardcoded into the contract, the asset remains compliant even in public environments. An unauthorized address cannot purchase, receive, or interact with the token balances, eliminating the operational need to restrict the network layer itself.&lt;/p&gt;

&lt;h3&gt;
  
  
  The standard relies on manual transaction approval
&lt;/h3&gt;

&lt;p&gt;ERC-3643 is not a multi-signature escrow protocol where an issuer must sign off on every individual trade. The administrative burden is shifted to onboarding: once an investor is verified and registered, secondary transactions execute autonomously. The Compliance Engine checks mathematical conditions in real time, enabling atomic peer-to-peer settlement without human intervention.&lt;/p&gt;

&lt;h2&gt;
  
  
  How This Connects to the Market
&lt;/h2&gt;

&lt;p&gt;As the tokenization of private credit, government debt, and structured real estate moves from early experimental pilots into institutional settlement infrastructure, standardized permissioning layers are displacing ad-hoc, proprietary solutions. In December 2023, ERC-3643 achieved formal adoption as an accepted Ethereum Improvement Proposal (EIP), signaling standard consensus for regulated asset issuance across the EVM ecosystem.&lt;/p&gt;

&lt;p&gt;Institutional capital allocators operating within European jurisdictions under the Markets in Crypto-Assets (MiCA) framework or the EU DLT Pilot Regime require legal certainty that securities laws apply equally on-chain. Market operators in the US face parallel obligations under Financial Industry Regulatory Authority (FINRA) and SEC mandates. By delegating compliance verification to self-sovereign identity contracts while enforcing trading boundaries inside bytecode, ERC-3643 provides an institutional on-ramp that maintains compatibility with public smart contract architecture.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What is the difference between ERC-20 and ERC-3643?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;ERC-20 permits token transfers between any two addresses provided the sender has a sufficient balance and pays gas fees. ERC-3643 overrides this behavior by querying an Identity Registry and a Compliance Engine before any transfer executes, blocking transactions if either party lacks valid identity claims or violates offering rules.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does ERC-3643 store user identity documents on-chain?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. The ONCHAINID standard relies on cryptographic claims and digital signatures written by verified third-party issuers. Personal identifiable information (PII) remains off-chain with the verifying institution, satisfying data protection standards like GDPR.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can an issuer freeze or recover ERC-3643 tokens?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Yes. ERC-3643 contains administrative modules that allow authorized agents to freeze transfers for specific non-compliant wallets or burn and reissue tokens to an investor who has lost access to their private keys.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can ERC-3643 tokens interact with decentralized finance (DeFi) protocols?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Yes, provided the DeFi liquidity pool or automated market maker (AMM) contract is registered in the Identity Registry and meets the compliance criteria defined in the token's Compliance Engine.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://www.esma.europa.eu/" rel="noopener noreferrer"&gt;Guidelines on the DLT Pilot Regime&lt;/a&gt; — European Securities and Markets Authority&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.sec.gov/" rel="noopener noreferrer"&gt;Understanding the Regulation of Tokenized Securities&lt;/a&gt; — Securities and Exchange Commission&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://eips.ethereum.org/EIPS/eip-3643" rel="noopener noreferrer"&gt;EIP-3643: T-REX - Token for Regulated EXchanges&lt;/a&gt; — Ethereum Improvement Proposals&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.erc3643.org/" rel="noopener noreferrer"&gt;ERC-3643 Official Protocol Documentation&lt;/a&gt; — ERC-3643 Association&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;&lt;a href="https://basisdesk.news?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt; is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: &lt;a href="https://basisdesk.news/developers?utm_source=devto" rel="noopener noreferrer"&gt;basisdesk.news/developers&lt;/a&gt;. Not investment advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>fintech</category>
      <category>cryptocurrency</category>
      <category>beginners</category>
    </item>
    <item>
      <title>CoinJoin and PayJoin, Explained: How Bitcoin Users Break Heuristics</title>
      <dc:creator>Basis Desk</dc:creator>
      <pubDate>Thu, 19 Nov 2026 02:31:17 +0000</pubDate>
      <link>https://dev.to/basisdesk/coinjoin-and-payjoin-explained-how-bitcoin-users-break-heuristics-5bpd</link>
      <guid>https://dev.to/basisdesk/coinjoin-and-payjoin-explained-how-bitcoin-users-break-heuristics-5bpd</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — &lt;a href="https://basisdesk.news/about/how-we-use-ai?utm_source=devto" rel="noopener noreferrer"&gt;how we use AI&lt;/a&gt;. Originally published on &lt;a href="https://basisdesk.news/learn/coinjoin-and-payjoin-bitcoin-privacy?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Public blockchains expose transaction histories by default. Collaborative Bitcoin transactions disrupt chain analysis by breaking the core assumptions tracing software relies on.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Key points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Common-input heuristics assume all inputs in a multi-input Bitcoin transaction belong to a single entity.&lt;/li&gt;
&lt;li&gt;CoinJoin breaks this heuristic by combining multiple users' inputs into standardized, equal-sized output denominations.&lt;/li&gt;
&lt;li&gt;PayJoin (BIP-78) involves both the sender and receiver supplying inputs, making privacy transactions look like routine payments.&lt;/li&gt;
&lt;li&gt;Regulated platforms frequently flag identifiable CoinJoin outputs under AML rules, whereas PayJoins blend into normal ledger activity.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Public blockchains broadcast every transfer across a transparent ledger. While Bitcoin addresses do not display personal identities, surveillance firms link activity together by tracking patterns across transaction inputs and outputs. Collaborative transaction structures—chiefly &lt;strong&gt;CoinJoin&lt;/strong&gt; and &lt;strong&gt;PayJoin&lt;/strong&gt;—allow multiple parties to construct unified transfers that systematically break these clustering assumptions.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Accounting Engine: How Bitcoin Uses UTXOs
&lt;/h2&gt;

&lt;p&gt;Bitcoin does not operate like a conventional bank account with an updated balance figure. Instead, it uses the Unspent Transaction Output (&lt;strong&gt;UTXO&lt;/strong&gt;) model. Each UTXO is an indivisible unit of satoshis recorded on the ledger, locked to a specific spending script, usually associated with an address.&lt;/p&gt;

&lt;p&gt;When a user initiates a payment, their wallet consumes one or more existing UTXOs as inputs. The transaction then generates new UTXOs as outputs: typically one to pay the recipient and one to return remaining funds to the sender as change. Once consumed, an input cannot be spent again. To reconstruct a user's total balance, a wallet program scans the entire ledger to aggregate all active UTXOs matching its cryptographic keys.&lt;/p&gt;

&lt;p&gt;Because this transaction graph is public, outside observers can map fund flows over time. Forensic analytics companies analyze the relationships between inputs and outputs to cluster disparate addresses under single ownership profiles.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Surveillance Model: Common-Input Heuristics
&lt;/h2&gt;

&lt;p&gt;Blockchain tracking firms rely on several core heuristics to de-anonymize network participants. The primary principle is the &lt;strong&gt;common-input heuristic&lt;/strong&gt; (also known as the multi-input clustering heuristic). This rule assumes that if a single transaction contains multiple inputs, all of those inputs belong to the same entity.&lt;/p&gt;

&lt;p&gt;Under standard wallet implementations, this assumption holds true. If an item costs 0.60 $BTC, and a user only possesses two independent UTXOs worth 0.35 BTC and 0.40 BTC, the wallet software automatically combines both inputs to fund the 0.60 BTC transfer, returning 0.15 BTC (minus network transaction fees) as change. Analysts mark those two input addresses as belonging to the same wallet cluster, merging their prior transaction histories into a single entity dossier.&lt;/p&gt;

&lt;p&gt;Secondary heuristics examine change outputs. Observers analyze output script types, address reuse, round-number payment amounts, and coin denominations to infer which output belongs to the merchant and which returns to the spender. Once an analyst successfully identifies the change output, they follow the user's remaining balance into future transactions, extending the ownership cluster.&lt;/p&gt;

&lt;h2&gt;
  
  
  CoinJoin: Equal-Output Batching
&lt;/h2&gt;

&lt;p&gt;Introduced conceptually by developer Gregory Maxwell in 2013, a CoinJoin invalidates the common-input heuristic by allowing multiple independent users to coordinate a single transaction. Instead of one person spending multiple inputs, multiple participants contribute inputs into a communal transaction that produces standardized outputs of identical value.&lt;/p&gt;

&lt;p&gt;Consider an illustrative example involving three distinct participants, Alice, Bob, and Charlie:&lt;/p&gt;

&lt;p&gt;Assume Alice controls a UTXO worth 0.12 BTC, Bob controls 0.15 BTC, and Charlie controls 0.20 BTC. Through a coordination server or decentralized communication protocol, they agree to mix funds using a standardized denomination of 0.10 BTC.&lt;/p&gt;

&lt;p&gt;The resulting single transaction structure contains:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Three inputs: Alice's 0.12 BTC, Bob's 0.15 BTC, and Charlie's 0.20 BTC (Total inputs: 0.47 BTC).&lt;/li&gt;
&lt;li&gt;Three identical primary outputs: 0.10 BTC to an address designated by Alice, 0.10 BTC to Bob, and 0.10 BTC to Charlie.&lt;/li&gt;
&lt;li&gt;Three distinct change outputs: Alice receives 0.02 BTC, Bob receives 0.05 BTC, and Charlie receives 0.10 BTC, minus their proportionate share of the miner fee.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Because the primary outputs are completely identical in amount, an external observer monitoring the ledger cannot determine which 0.10 BTC output belongs to which input provider. The mathematical link tying a specific sender to a specific recipient output is broken.&lt;/p&gt;

&lt;p&gt;To ensure participants cannot steal funds or deanonymize each other during setup, modern CoinJoin implementations use cryptographic primitives such as blind signatures. The coordinator facilitates the aggregation of inputs and registers the desired output addresses without learning which registered output corresponds to which input. Furthermore, transactions are only signed by the users once the final structure contains their exact expected outputs, eliminating counterparty theft risk.&lt;/p&gt;

&lt;p&gt;However, standard CoinJoins feature clear structural footprints. Blockchain analysis tools immediately recognize a transaction containing numerous identical outputs alongside fragmented change outputs as a mixing event. While the software cannot trace the lineage across the equal outputs with certainty, it can flag the resulting coins as having passed through a CoinJoin pool.&lt;/p&gt;

&lt;h2&gt;
  
  
  PayJoin (BIP-78): Steganographic Collaboration
&lt;/h2&gt;

&lt;p&gt;PayJoin, formally specified under Bitcoin Improvement Proposal 78 (&lt;strong&gt;BIP-78&lt;/strong&gt;), offers a different architectural approach. Instead of gathering large groups of strangers to create an obvious mixing transaction, a PayJoin is a collaborative payment conducted strictly between a payer and a receiver during an ordinary commercial transaction.&lt;/p&gt;

&lt;p&gt;In a standard non-private transaction, the payer provides all the inputs, and the outputs consist of the payment to the receiver plus the payer's change. In a PayJoin transaction, the receiver also contributes an input. The receiver then rolls their own input value directly into the primary payment output they receive.&lt;/p&gt;

&lt;p&gt;Suppose Alice wants to purchase a service from Bob costing 0.20 BTC:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Alice has a UTXO worth 0.30 BTC.&lt;/li&gt;
&lt;li&gt;Bob controls an existing UTXO worth 0.10 BTC.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Alice connects to Bob's BIP-78 compatible server endpoint. Rather than Bob merely providing a receiving address, Bob provides his 0.10 BTC input to be bundled into the draft transaction. The final signed transaction contains:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Inputs: Alice's 0.30 BTC and Bob's 0.10 BTC (Total: 0.40 BTC).&lt;/li&gt;
&lt;li&gt;Outputs: Bob's payment output of 0.30 BTC (the 0.20 BTC purchase price plus Bob's 0.10 BTC input) and Alice's change output of 0.10 BTC (minus network transaction fees).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To any chain analysis software monitoring the network, this transaction appears to be an ordinary, single-payer transfer where one entity combined 0.40 BTC across two inputs to pay someone 0.30 BTC, generating 0.10 BTC in change. The tracking heuristic assumes that both input addresses belong to Alice. In reality, the inputs were owned by two different parties.&lt;/p&gt;

&lt;p&gt;PayJoin operates steganographically: it conceals private behavior inside data structures that appear entirely routine. Because PayJoin transactions look indistinguishable from conventional multi-input transactions on the ledger, they systematically undermine the reliability of all multi-input clustering algorithms across the broader Bitcoin network.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compliance Screening and Exchange Considerations
&lt;/h2&gt;

&lt;p&gt;Financial institutions and centralized virtual asset service providers (VASPs) operate under stringent anti-money laundering (AML) and counter-terrorist financing (CTF) mandates. Regulatory bodies such as the Financial Action Task Force (FATF), the Financial Crimes Enforcement Network (FinCEN) in the United States, and the European Securities and Markets Authority (ESMA) require regulated platforms to monitor customer transactions for illicit activity.&lt;/p&gt;

&lt;p&gt;To satisfy these mandates, exchanges deploy automated blockchain intelligence tools to assign risk scores to inbound deposits based on their transaction history:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;CoinJoin Deposits:&lt;/strong&gt; Because CoinJoin transactions possess an identifiable mathematical footprint, compliance software readily tags UTXOs exiting these protocols. Regulated exchanges frequently flag deposits containing a CoinJoin history, occasionally triggering automated account freezes, source-of-funds inquiries, or outright service termination. Several centralized services strictly prohibit customer interactions with mixing protocols.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PayJoin Deposits:&lt;/strong&gt; Because PayJoin does not utilize standardized, equal-sized output patterns, automated heuristics cannot reliably flag it as a privacy-enhancing transaction. However, if an exchange's surveillance provider identifies the receiver's co-spent input through external intelligence, the platform may scrutinize the operational structure.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tainted Change:&lt;/strong&gt; In CoinJoin arrangements, unmixed change outputs remain directly connected to the user's pre-mix identity. Users who recombine mixed outputs with their unmixed change outputs inadvertently undermine their own privacy, creating traceable linkages that compliance engines can parse.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Tax obligations remain strictly independent of transaction obfuscation. In jurisdictions like the United States (under the Internal Revenue Service) and the United Kingdom (under HM Revenue and Customs), disposing of digital assets to pay fees, settle balances, or exchange properties generally triggers a taxable event. The use of privacy mechanisms does not exempt market participants from legal reporting requirements.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common Misconceptions
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;"CoinJoin coordinators can steal user deposits."&lt;/strong&gt; Non-custodial CoinJoin implementations do not surrender custody of funds to the coordinating server. Transactions are constructed cooperatively, and participants only sign the final package via their private keys if the output matches their agreed allocation. Coordinators cannot redirect funds.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"PayJoin requires finding a third-party mixing pool."&lt;/strong&gt; PayJoin does not rely on public pools or crowds of independent users. It is an agreement exclusively executed between two transacting counterparties: the buyer and the seller. If a merchant's payment processing software supports BIP-78, the interaction occurs during checkout.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"CoinJoin delivers complete anonymity on its own."&lt;/strong&gt; A CoinJoin transaction breaks the link across a specific transaction phase, but user behavior afterward can re-expose the transaction history. If an individual sends multiple mixed outputs into a single consolidated deposit at an exchange that enforces Know Your Customer (KYC) rules, the platform can link the outputs back to that single identity.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How This Connects to the Market
&lt;/h2&gt;

&lt;p&gt;The ongoing tension between privacy protocols and compliance infrastructure shapes institutional Bitcoin adoption. As surveillance firms refine multi-input clustering heuristics, tools that introduce ambiguity across the base layer degrade the deterministic quality of their scoring models.&lt;/p&gt;

&lt;p&gt;Protocol-level improvements, including Taproot and Schnorr signatures, allow multi-party transactions to look identical to single-key transactions when settled on-chain. As collaborative protocols integrate these cryptographic standards, distinguishing between single-user transfers, PayJoins, and complex multi-signature institutional transactions will become increasingly difficult for external monitoring engines.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What is the primary difference between CoinJoin and PayJoin?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;CoinJoin combines inputs from many users into identical output amounts to break transaction links, creating a noticeable footprint on the blockchain. PayJoin is a payment between two parties where both contribute inputs, creating a transaction that looks indistinguishable from an ordinary Bitcoin transfer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can a CoinJoin coordinator steal my Bitcoin?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Modern CoinJoin architectures are non-custodial. The coordinator merely arranges the transaction data. Each user retains their private keys and only signs the proposed transaction if their designated outputs and change amounts are strictly correct.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why do centralized exchanges flag CoinJoin transactions?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Regulated exchanges must adhere to anti-money laundering mandates. Because traditional CoinJoins have obvious visual structures on-chain that obscure source-of-funds analysis, automated compliance tools flag these outputs as higher risk for financial screening.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does using PayJoin make transactions completely untraceable?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No single privacy tool guarantees complete untraceability. While PayJoin breaks the assumption that all inputs come from the spender, improper post-transaction behavior—such as address reuse or consolidating outputs—can still allow analysts to infer ownership.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://developer.bitcoin.org/reference/transactions.html" rel="noopener noreferrer"&gt;Bitcoin Developer Documentation: Transactions&lt;/a&gt; — Bitcoin Project&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://github.com/bitcoin/bips/blob/master/bip-0078.mediawiki" rel="noopener noreferrer"&gt;BIP 78: A Trade-Off-Resistant PayJoin Proposal&lt;/a&gt; — Bitcoin Improvement Proposals&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;&lt;a href="https://basisdesk.news?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt; is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: &lt;a href="https://basisdesk.news/developers?utm_source=devto" rel="noopener noreferrer"&gt;basisdesk.news/developers&lt;/a&gt;. Not investment advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>bitcoin</category>
      <category>blockchain</category>
      <category>cryptocurrency</category>
      <category>beginners</category>
    </item>
    <item>
      <title>BitVM Explained: Smart-Contract Computation on Bitcoin</title>
      <dc:creator>Basis Desk</dc:creator>
      <pubDate>Thu, 19 Nov 2026 00:31:15 +0000</pubDate>
      <link>https://dev.to/basisdesk/bitvm-explained-smart-contract-computation-on-bitcoin-4bp4</link>
      <guid>https://dev.to/basisdesk/bitvm-explained-smart-contract-computation-on-bitcoin-4bp4</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — &lt;a href="https://basisdesk.news/about/how-we-use-ai?utm_source=devto" rel="noopener noreferrer"&gt;how we use AI&lt;/a&gt;. Originally published on &lt;a href="https://basisdesk.news/learn/bitvm-and-bitcoin-zk-verification?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;BitVM enables arbitrary, Turing-complete computation on Bitcoin without a soft fork by shifting program execution off-chain and enforcing fraud proofs on-chain.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Key points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;BitVM enables Turing-complete smart-contract verification on Bitcoin using Taproot and hash locks without requiring consensus soft forks.&lt;/li&gt;
&lt;li&gt;Computation runs entirely off-chain between provers and challengers; Bitcoin's blockchain serves strictly as an arbitration court for disputed steps.&lt;/li&gt;
&lt;li&gt;Original BitVM models used NAND gate commitments in multi-round bisection games; BitVM2 refines this into non-interactive, permissionless SNARK chunk verification.&lt;/li&gt;
&lt;li&gt;The primary commercial use case is trust-minimized bridges for Bitcoin rollups operating under a 1-of-N honest verifier assumption.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;BitVM is a computing paradigm that enables expressive, Turing-complete smart contracts on Bitcoin without requiring changes to the network's consensus rules [1]. Proposed by developer Robin Linus in October 2023, the model borrows the optimistic verification architecture used in Ethereum rollups and adapts it to Bitcoin's constrained Script language [1]. By running computations off-chain and keeping on-chain activity limited to pre-signed fraud-proof disputes, BitVM turns Bitcoin into an arbitration settlement layer rather than an execution engine [1].&lt;/p&gt;

&lt;p&gt;Historically, Bitcoin intentionally avoided complex, stateful programming languages to prioritize security, predictability, and decentralization [2]. As institutional interest in decentralized applications and Layer-2 scaling solutions expanded, researchers faced a structural constraint: adding arbitrary smart contracts traditionally required hard or soft forks to introduce new opcodes or covenant rules [2]. BitVM sidesteps this governance hurdle entirely, using existing tools—primarily Taproot, hash locks, and timelocks—to verify any computable program [1].&lt;/p&gt;

&lt;p&gt;Understanding BitVM requires examining how it decomposes complex calculations into elementary digital logic, how interactive challenger-prover games resolve disputes, and how its newer iteration, BitVM2, refines the framework for scalable, trust-minimized bridges.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Bitcoin Script Constraint
&lt;/h2&gt;

&lt;p&gt;Bitcoin relies on Bitcoin Script, a stack-based, non-Turing-complete execution language designed deliberately without loops, unbounded recursion, or complex cross-transaction memory [2]. Every node in the network must process and validate every transaction; unrestricted execution could expose nodes to denial-of-service vectors, such as infinite loops [2].&lt;/p&gt;

&lt;p&gt;Because Bitcoin cannot run complex applications natively, developers previously had to build external platforms, such as sidechains or federated networks, which typically rely on honest-majority multi-signature committees to manage funds. These setups introduce custody trust assumptions: if a quorum of signers colludes, user funds can be stolen. True Layer-2 networks, such as optimistic or zero-knowledge rollups, require the underlying Layer 1 to independently verify transaction transitions or fraud proofs. Until BitVM, engineers assumed that verifying such state transitions on $BTC required new consensus opcodes [1].&lt;/p&gt;

&lt;p&gt;BitVM challenges that assumption. Instead of executing arbitrary logic on-chain, it executes logic off-chain and uses Bitcoin Script exclusively to verify claims if a dispute occurs [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  NAND Logic and Bit Commitments
&lt;/h2&gt;

&lt;p&gt;At the core of the original BitVM design is the mathematical reality of universal logic gates: any digital circuit or computer program can be expressed entirely through networks of &lt;strong&gt;NAND gates&lt;/strong&gt; (NOT-AND gates) [1]. A NAND gate takes two binary inputs and outputs a zero only if both inputs are one; otherwise, it outputs a one.&lt;/p&gt;

&lt;p&gt;To translate this logic into Bitcoin Script, BitVM employs &lt;strong&gt;bit commitments&lt;/strong&gt; [1]. A bit commitment is a cryptographic mechanism that forces a party to commit to a binary value—either 0 or 1—without revealing it immediately, while preventing that party from changing the value later [1]. In Bitcoin Script, this is achieved using hash locks: a prover reveals one of two pre-image strings to represent 0 or 1. Once a pre-image is revealed on-chain, the prover's choice is permanently fixed [1].&lt;/p&gt;

&lt;p&gt;BitVM groups these bit commitments into logic gate commitments. In the original proposal, each NAND gate requires a small Script snippet that inspects the two committed inputs and verifies that the committed output matches the truth table of a NAND operation [1]. Because Taproot (activated via Bitcoin Improvement Proposal 341 and 342) allows transactions to commit to massive Merkle trees of distinct execution scripts (the Tapscript tree), a developer can organize millions of individual NAND gate scripts off-chain [1, 2]. Only the specific gate contested during an active dispute ever needs to be executed on the Bitcoin blockchain [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  The Challenger-Prover Game
&lt;/h2&gt;

&lt;p&gt;BitVM operates on an optimistic verification model between two roles: a &lt;strong&gt;prover&lt;/strong&gt; and a &lt;strong&gt;challenger&lt;/strong&gt; [1]. The prover claims that a given off-chain computation was completed correctly and that a specific outcome is valid. The challenger monitors the computation and checks for discrepancies [1].&lt;/p&gt;

&lt;p&gt;Under regular operation, the prover and challenger compute the program off-chain, agree on the result, and complete the settlement through standard Bitcoin multi-signature transactions. In this cooperative path, zero verification logic touches the blockchain, preserving privacy and minimizing transaction fees [1].&lt;/p&gt;

&lt;p&gt;If the prover posts a false claim, the challenger initiates an interactive dispute on-chain. This dispute unfolds as a bisection game:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The prover asserts the correctness of a program containing billions of execution steps.&lt;/li&gt;
&lt;li&gt;Rather than evaluating the entire program on-chain, the challenger asks the prover to bisect the execution trace—halving the contested execution path repeatedly over successive on-chain rounds [1].&lt;/li&gt;
&lt;li&gt;Within several rounds, the search space narrows to a single contested instruction or NAND gate.&lt;/li&gt;
&lt;li&gt;The prover must execute that single gate's script on-chain using their committed inputs [1].&lt;/li&gt;
&lt;li&gt;If the on-chain gate script reveals an impossible logic state (for example, inputs of 1 and 1 yielding an output of 1), the Bitcoin consensus engine invalidates the prover's claim, slashing the prover's pre-funded collateral and awarding it to the challenger [1].&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This dispute process requires only a 1-of-N honest verifier assumption. As long as at least one challenger in the pre-defined group remains honest and active, a fraudulent claim can be detected and struck down [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  A Worked Example: Off-Chain State Settlement
&lt;/h2&gt;

&lt;p&gt;To understand the operational overhead of the bisection mechanism, consider an application verifying an execution trace of 1,048,576 ($2^{20}$) computational steps.&lt;/p&gt;

&lt;p&gt;Assume the prover locks 10 $BTC as an operational bond in an optimistic bridge contract. The prover asserts that a state transition spanning all 1,048,576 steps is correct. A challenger detects an error and formally objects.&lt;/p&gt;

&lt;p&gt;Rather than testing 1,048,576 operations on Bitcoin, the protocol divides the problem:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Round 1: The challenger demands the prover commit to the state at step 524,288 ($2^{19}$). The challenger identifies that the error is in the first half.&lt;/li&gt;
&lt;li&gt;Round 2: The prover commits to the state at step 262,144 ($2^{18}$).&lt;/li&gt;
&lt;li&gt;Rounds 3 through 20: The dispute proceeds sequentially, cutting the remaining trace in half at each step.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;After 20 bisection steps ($\log_2(1{,}048{,}576) = 20$), the parties isolate the dispute to an exact transition between two single operations—for instance, between step 131,071 and step 131,072. The prover is forced to execute that single operation on-chain. If the prover's committed output contradicts Bitcoin Script execution rules, the dispute transaction defaults against the prover. The bridge cancels the settlement and transfers the 10 $BTC collateral to the challenger to cover transaction fees and provide an economic reward. &lt;/p&gt;

&lt;p&gt;While mathematically clean, this classical BitVM design carries a major friction: the interactive game requires multiple sequential Bitcoin transactions spread across days or weeks, exposing challengers to liquidity locks and network congestion risks [3].&lt;/p&gt;

&lt;h2&gt;
  
  
  The Shift to BitVM2
&lt;/h2&gt;

&lt;p&gt;To address the latency and coordination bottlenecks of multi-round interactive bisection, the research team introduced &lt;strong&gt;BitVM2&lt;/strong&gt; in 2024 [3]. BitVM2 alters the fraud-proof model by reducing the multi-round bisection game to a non-interactive, three-transaction process [3].&lt;/p&gt;

&lt;p&gt;BitVM2 accomplishes this by breaking off-chain programs into SNARK (Succinct Non-Interactive Argument of Knowledge) verifiers, which are subsequently segmented into small chunks of Script [3]. Instead of requiring repeated on-chain queries back and forth, the prover publishes their assertions in a single commit transaction. If an assertion is invalid, a challenger can directly disprove the assertion in a single response transaction containing the mathematical proof of error [3].&lt;/p&gt;

&lt;p&gt;BitVM2 also shifts the bridge architecture from permissioned challenger pools to a permissionless dispute model [3]. In the initial BitVM design, the participant set had to be established during the initial setup of the Taproot tree, requiring all prospective challengers to pre-sign transactions. BitVM2 introduces mechanisms that allow anyone to challenge a fraudulent claim, moving closer to the trust model of standard decentralized rollups [3]. Researchers have also noted parallels between these off-chain covenant-like emulations and proposals using &lt;a href="https://basisdesk.news/news/bitcoin-functional-encryption-covenants-bypass-soft-forks" rel="noopener noreferrer"&gt;functional encryption covenants&lt;/a&gt; to bypass consensus upgrades.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building Trust-Minimized Bridges and Rollups
&lt;/h2&gt;

&lt;p&gt;The primary practical application for BitVM is constructing trust-minimized two-way asset bridges between the Bitcoin base layer and Layer-2 rollups [1, 3].&lt;/p&gt;

&lt;p&gt;In a standard federated bridge, deposited $BTC is held by custodians. If the custodians sign a withdrawal transaction, the Bitcoin blockchain executes it without checking whether an equivalent balance was legitimately burned on the Layer 2. By contrast, a BitVM-powered bridge binds withdrawals directly to execution proofs [3]. &lt;/p&gt;

&lt;p&gt;When liquidity operators fulfill user withdrawals on the Bitcoin mainnet, they file reimbursement claims verified by the BitVM contract. Provers must post financial collateral to back their reimbursement assertions [3]. If a bridge operator tries to withdraw user deposits without presenting a valid state root of the Layer 2, any challenger can run the BitVM verification script to seize the operator's bond and reject the withdrawal [3]. &lt;/p&gt;

&lt;p&gt;This setup allows the creation of optimistic rollups and zero-knowledge rollups on Bitcoin where security does not depend on majority consensus of a multi-sig, but rather on the mathematical assumption that at least one honest participant will submit a fraud proof if an invalid withdrawal is attempted [1, 3]. Users looking to understand how client-side verification interacts with native proofs can examine &lt;a href="https://basisdesk.news/learn/spv-light-clients-explained" rel="noopener noreferrer"&gt;Bitcoin light clients and SPV designs&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common Misconceptions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Misconception 1: BitVM is an upgrade or soft fork to Bitcoin.&lt;/strong&gt;&lt;br&gt;
BitVM is not a Bitcoin Improvement Proposal (BIP) that requires miner signaling or a network hard/soft fork [1]. It is an off-chain application architecture that utilizes tools already available on the Bitcoin mainnet today, primarily Pay-to-Taproot (P2TR), timelocks, and basic conditional hash checks [1, 2].&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Misconception 2: Bitcoin nodes must execute heavy smart-contract calculations.&lt;/strong&gt;&lt;br&gt;
Bitcoin full nodes do not compute smart contracts when using BitVM [1]. Full nodes only process standard Bitcoin transactions, verifying cryptographic hashes and signatures. The intensive computation happens off-chain on computers operated by the prover and challenger [1]. Only a microscopic fragment of logic (such as an individual NAND gate or a chunked SNARK segment) is verified by the blockchain, and only when a dispute occurs [1, 3].&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Misconception 3: BitVM brings instant, fully trustless rollups to Bitcoin today.&lt;/strong&gt;&lt;br&gt;
BitVM does not provide instant, trustless scaling equivalent to Layer-2 networks with native consensus verification opcodes. Early implementations face capital inefficiencies: bridge provers must front liquidity and post substantial collateral to underwrite settlement periods [3]. Furthermore, if transaction fees on Bitcoin spike drastically, challenger transactions could theoretically be priced out of blocks during a dispute window, creating an economic vector that developers must mitigate through dynamic fee-bumping designs.&lt;/p&gt;

&lt;h2&gt;
  
  
  How This Connects to the Market
&lt;/h2&gt;

&lt;p&gt;The development of BitVM marks a strategic shift in how developers approach capital deployment on Bitcoin. By demonstrating that Turing-complete execution verification is possible without changing base-layer consensus, BitVM provides an alternative to multi-year political battles over soft-fork covenant proposals [1, 3].&lt;/p&gt;

&lt;p&gt;For institutional market participants, the evolution of BitVM2 serves as a testbed for whether native Bitcoin capital can participate in decentralized lending, synthetic asset issuance, and cross-chain liquidity without surrendering custody to centralized custodial bridges. Institutional adoption of BitVM-anchored rollups will depend heavily on capital efficiency: specifically, the ratio of collateral bridge operators must lock up relative to the volume of user transactions they process. Monitoring the deployment of initial production bridges, on-chain dispute activity, and transaction fee management under network congestion will determine if the paradigm can move from cryptographic proof-of-concept to production infrastructure.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does BitVM require a soft fork or changes to Bitcoin's rules?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. BitVM relies exclusively on existing Bitcoin functionality, including Taproot, hash locks, and timelocks activated in past network updates.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is the 1-of-N honest verifier assumption?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It means the system remains secure as long as at least one participant out of the designated challenger pool is honest, online, and willing to challenge fraudulent claims.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is the main difference between BitVM and BitVM2?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The original BitVM relied on a multi-round interactive bisection game across many on-chain transactions, whereas BitVM2 uses chunked SNARK verification to resolve disputes in three non-interactive transactions open to permissionless challengers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Are full Bitcoin nodes burdened by running BitVM smart contracts?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Complex programs are computed entirely off-chain. Full nodes only validate standard signatures and hashes, executing a single discrete computational step only when a formal dispute is initiated.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki" rel="noopener noreferrer"&gt;BIP 341: Taproot: SegWit Version 1 Spending Rules&lt;/a&gt; — Bitcoin Improvement Proposals&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://bitvm.org/bitvm.pdf" rel="noopener noreferrer"&gt;BitVM: Compute Anything on Bitcoin&lt;/a&gt; — BitVM Project&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;&lt;a href="https://basisdesk.news?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt; is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: &lt;a href="https://basisdesk.news/developers?utm_source=devto" rel="noopener noreferrer"&gt;basisdesk.news/developers&lt;/a&gt;. Not investment advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>bitcoin</category>
      <category>blockchain</category>
      <category>cryptocurrency</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Bitcoin Covered-Call ETFs vs Holding Spot Bitcoin: Total Return Trade-offs</title>
      <dc:creator>Basis Desk</dc:creator>
      <pubDate>Wed, 18 Nov 2026 04:31:05 +0000</pubDate>
      <link>https://dev.to/basisdesk/bitcoin-covered-call-etfs-vs-holding-spot-bitcoin-total-return-trade-offs-1j1d</link>
      <guid>https://dev.to/basisdesk/bitcoin-covered-call-etfs-vs-holding-spot-bitcoin-total-return-trade-offs-1j1d</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — &lt;a href="https://basisdesk.news/about/how-we-use-ai?utm_source=devto" rel="noopener noreferrer"&gt;how we use AI&lt;/a&gt;. Originally published on &lt;a href="https://basisdesk.news/learn/covered-call-etfs-vs-owning-spot-bitcoin?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Covered-call bitcoin exchange-traded funds swap parabolic upside for immediate cash flow. Understanding their mechanics reveals why option-income funds outperform in stagnant markets but structurally lag during sharp bull runs.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Key points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Covered-call bitcoin ETFs harvest options premiums to generate immediate income but legally surrender asset appreciation above the option strike price.&lt;/li&gt;
&lt;li&gt;The strategy offers only minor downside protection: premiums offset small losses, but investors absorb nearly all catastrophic declines.&lt;/li&gt;
&lt;li&gt;Total return often lags spot bitcoin significantly over market cycles because bitcoin historical returns rely on sudden, vertical price advances.&lt;/li&gt;
&lt;li&gt;Distributions can be classified as ordinary income, capital gains, or return of capital, creating different tax outcomes than unrealized spot holdings.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Investors deciding between pure spot bitcoin exposure and derivative-income strategies face a structural trade-off between open-ended capital appreciation and immediate cash yield. A standard spot bitcoin holding or spot exchange-traded fund captures the unconstrained price trajectory of $BTC, leaving the holder fully exposed to market drawdowns while preserving all upside. In contrast, covered-call bitcoin funds sell potential future gains to options buyers in exchange for option premiums, delivering high headline distribution rates at the expense of asymmetric right-tail returns [1].&lt;/p&gt;

&lt;p&gt;To evaluate these two approaches, capital allocators must look beyond headline annualized yields and examine &lt;strong&gt;total return&lt;/strong&gt;, which combines net asset value fluctuations with reinvested cash distributions. While selling call options generates a cash cushion during sideways or moderately down trending markets, the strategy caps the explosive upside moves that historically account for the bulk of bitcoin's long-term performance.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Anatomy of an Option Overlay
&lt;/h2&gt;

&lt;p&gt;A traditional covered-call strategy combines a long position in an underlying asset with the sale of call options against that exact holding [1]. A call option grants the buyer the legal right, but not the obligation, to purchase the asset at a predetermined &lt;strong&gt;strike price&lt;/strong&gt; on or before a specified expiration date. For assuming this obligation to sell, the fund receives an upfront payment called an option premium [1].&lt;/p&gt;

&lt;p&gt;In conventional equity markets, managers execute this trade by holding the physical equity and writing call contracts against it. In the digital asset sector, fund structures vary. Some vehicles hold spot bitcoin or shares of spot exchange-traded funds and write exchange-traded or over-the-counter call options against those holdings. Other funds employ synthetic architectures: they hold cash collateral alongside long call options to replicate asset exposure, simultaneously writing short out-of-the-money or at-the-money calls to generate cash flow. Readers can explore the architectural distinctions among derivative-income structures in the analysis of &lt;a href="https://basisdesk.news/learn/bitcoin-income-etfs-explained" rel="noopener noreferrer"&gt;Bitcoin Income ETFs Explained: How MSTY, YBIT, and BTCI Pay Distributions&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The premium collected by the fund is driven largely by &lt;strong&gt;implied volatility&lt;/strong&gt;, an options pricing metric that reflects the market's expectation of future price swings. Because bitcoin displays elevated volatility relative to traditional equities, options buyers pay substantial premiums for call contracts. This dynamic allows fund managers to harvest large upfront cash amounts, which form the basis of the double-digit yields advertised by covered-call vehicles.&lt;/p&gt;

&lt;h2&gt;
  
  
  Capped Upside and the Right-Tail Deficit
&lt;/h2&gt;

&lt;p&gt;The fundamental compromise of the covered-call trade becomes apparent when bitcoin experiences rapid upward price discovery. If the price of $BTC surges beyond the agreed strike price prior to expiration, the option moves into the money. The fund remains obligated to deliver the underlying asset or settle the cash difference at the lower strike price. &lt;/p&gt;

&lt;p&gt;Consequently, the fund forfeits all capital appreciation above the strike level. It retains only the price gain up to the strike, plus the option premium collected at the outset. Because bitcoin's multi-year performance has historically been concentrated in short, explosive breakout periods, capping upside during these parabolic runs creates an insurmountable total return drag relative to holding pure spot asset allocations. &lt;/p&gt;

&lt;p&gt;Consider an institutional portfolio that holds direct spot allocations. When liquidity inflows accelerate—such as instances when &lt;a href="https://basisdesk.news/news/us-spot-bitcoin-etfs-pull-one-billion-inflows" rel="noopener noreferrer"&gt;US Spot Bitcoin ETFs Draw Over $1B in Three Days&lt;/a&gt;—spot allocations capture the complete vertical price advance. A covered-call ETF holding a strike set 5% out of the money captures that initial 5% and the premium, but participates in none of the remaining surge.&lt;/p&gt;

&lt;h2&gt;
  
  
  Downside Asymmetry and Net Asset Value Erosion
&lt;/h2&gt;

&lt;p&gt;While an option overlay strictly limits upside potential, it provides minimal protection against deep market crashes. The cash collected from the sold call option acts as a partial buffer, reducing the fund's net loss by the exact amount of the premium. However, once the spot price drops below the purchase price minus the premium, the fund absorbs every dollar of subsequent decline.&lt;/p&gt;

&lt;p&gt;This dynamic creates an asymmetric performance profile: &lt;strong&gt;asymmetric return&lt;/strong&gt; behavior where the fund absorbs virtually all catastrophic downside while sacrificing the parabolic upside. &lt;/p&gt;

&lt;p&gt;Furthermore, this dynamic leads to a structural problem known as net asset value erosion. When the underlying asset declines sharply, the fund's capital base shrinks. In subsequent option cycles, the manager writes calls against a smaller asset base. If the market suddenly rebounds, the fund's participation is capped by its new strike price, leaving the net asset value permanently impaired relative to an unencumbered spot holding that fully recovers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Worked Scenario: Three Market Regimes
&lt;/h2&gt;

&lt;p&gt;To illustrate the mathematical divergence between the two strategies, assume an investor compares a $10,000 spot bitcoin allocation against a $10,000 allocation in a covered-call bitcoin ETF. Assume the covered-call fund writes one-month calls with a strike price set 5% above the starting market price and collects a 3% option premium ($300).&lt;/p&gt;

&lt;p&gt;In a flat market regime, bitcoin ends the month unchanged at $10,000. The spot investor records a 0% return, maintaining a $10,000 portfolio value. The covered-call option expires worthless, allowing the covered-call fund to retain the $300 premium. The covered-call investor finishes with $10,300, outperforming spot by three percentage points.&lt;/p&gt;

&lt;p&gt;In a parabolic bull regime, bitcoin surges 25% over the month to finish at $12,500. The spot investor captures the full move, ending with $12,500. The covered-call ETF captures the 5% move up to the strike price ($500) plus the 3% premium ($300), but forfeits the remaining 20% gain. The covered-call portfolio finishes at $10,800, underperforming spot bitcoin by $1,700.&lt;/p&gt;

&lt;p&gt;In a severe drawdown regime, bitcoin declines 20% to finish at $8,000. The spot investor absorbs an unrealized loss of $2,000, ending with $8,000. The covered-call fund absorbs the same drop but cushions the loss with the $300 premium, ending at $8,300. The covered-call strategy modestly outperforms on the drawdown, but remains down 17% overall.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fee Structures and Cash Drag
&lt;/h2&gt;

&lt;p&gt;Management costs represent an additional structural friction that separates derivative funds from direct exposure. Spot bitcoin ETFs typically charge low annual management fees, as passive custody of digital assets requires minimal active intervention. &lt;/p&gt;

&lt;p&gt;Conversely, covered-call strategies involve active derivatives trading, periodic roll execution, collateral management, and options clearing costs. As a result, covered-call fund expense ratios are generally higher than spot alternatives. Over extended holding periods, these higher management fees subtract steadily from total returns.&lt;/p&gt;

&lt;p&gt;Additionally, funds that distribute monthly cash yields often face cash drag. Managers must set aside liquid balances or short-term collateral to pay option settlements and monthly shareholder distributions, leaving less capital continuously compounded in the underlying asset.&lt;/p&gt;

&lt;h2&gt;
  
  
  Regulatory and Tax Treatment
&lt;/h2&gt;

&lt;p&gt;The tax consequences of covered-call income differ substantially from the capital gains rules governing buy-and-hold spot positions. &lt;/p&gt;

&lt;p&gt;In the United States, the Internal Revenue Service governs option transactions and investment distributions under the Internal Revenue Code [2]. Distributions from covered-call ETFs can be classified as ordinary income, qualified dividends, short-term capital gains, or &lt;strong&gt;return of capital&lt;/strong&gt;. A return of capital distribution is not taxed immediately; instead, it reduces the shareholder's cost basis in the fund, deferring taxation until the shares are sold. In contrast, holding spot bitcoin or a spot ETF directly triggers capital gains taxation only upon an actual realization event, allowing long-term investors to defer tax liabilities without receiving involuntary annual cash distributions [2].&lt;/p&gt;

&lt;p&gt;In the United Kingdom, HM Revenue &amp;amp; Customs distinguishes between income distributions and capital gains for fund investors, subjecting overseas or derivative-based fund distributions to dividend or miscellaneous income tax rates depending on the vehicle's reporting fund status [3]. In the European Union, member states enforce varying national rules under frameworks outlined by the European Securities and Markets Authority, with local tax bodies applying distinct rates to derivative receipts versus physical asset capital gains. Investors must verify rules with qualified domestic advisers, as jurisdictional frameworks adjust frequently.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common Misconceptions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;"A high distribution yield equals high total return."&lt;/strong&gt;&lt;br&gt;
Investors frequently conflate cash distribution rates with overall investment gain. If an ETF pays an annualized distribution yield of 30% while its underlying net asset value drops 40%, the investor's total return remains negative. Option distributions represent realized option premiums and partial returns of capital, not risk-free profit.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"Covered calls offer reliable downside protection against bear markets."&lt;/strong&gt;&lt;br&gt;
A sold call option protects capital only up to the cash value of the received premium, which typically amounts to a few percentage points per month. During cyclical crypto contractions where an asset drops 50% or more, the option premium provides negligible insulation, and the investor remains fully exposed to the remaining balance of the decline.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"Option-income ETFs are structurally equivalent to dividend-paying equities."&lt;/strong&gt;&lt;br&gt;
Corporate equity dividends represent distributions of operational company profits and cash flows. Covered-call ETF yields are generated by selling off the future price upside of the fund's own assets or by consuming fund capital. The income is extracted by truncating the fund's capital appreciation capacity, not from corporate earnings.&lt;/p&gt;

&lt;h2&gt;
  
  
  How This Connects to the Market
&lt;/h2&gt;

&lt;p&gt;Covered-call bitcoin exchange-traded funds serve a distinct mandate within the broader digital asset landscape. They are tools designed specifically for cash-flow generation, suited primarily for stagnant, sideways, or high-volatility range-bound market environments where asset prices move horizontally over long durations.&lt;/p&gt;

&lt;p&gt;For market participants whose primary objective is long-term wealth accumulation, direct spot exposure remains the mathematically optimal route for capturing bitcoin's asymmetric upside. Allocators selecting covered-call vehicles must acknowledge that they are actively selling their participation in explosive market expansions in exchange for immediate cash flow.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What happens to a covered-call bitcoin ETF when bitcoin price surges?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When the price exceeds the call option's strike price, the fund must settle the option obligation or sell the asset at the strike price, completely capping the fund's capital appreciation above that level.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does a covered-call fund protect against a 50% bitcoin crash?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. The protection is limited strictly to the option premium collected, usually 2% to 4% per month. The fund absorbs all remaining losses beyond the premium cushion.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why are distribution rates on bitcoin covered-call ETFs so high?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Option premiums scale directly with implied volatility. Because bitcoin exhibits significantly higher volatility than conventional assets, call options sell for larger amounts, generating elevated cash yields.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is the primary operational difference between holding spot bitcoin and a covered-call ETF?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Spot bitcoin allows unlimited, unconstrained upside participation with low holding costs and deferred taxation, whereas covered-call ETFs deliver current cash payouts by continuously capping upside and charging active management fees.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://www.irs.gov/publications/p550" rel="noopener noreferrer"&gt;Publication 550: Investment Income and Expenses&lt;/a&gt; — Internal Revenue Service&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.gov.uk/hmrc-internal-manuals/cryptoassets-manual" rel="noopener noreferrer"&gt;Cryptoassets Manual: Detailed Guidance&lt;/a&gt; — HM Revenue &amp;amp; Customs&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;&lt;a href="https://basisdesk.news?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt; is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: &lt;a href="https://basisdesk.news/developers?utm_source=devto" rel="noopener noreferrer"&gt;basisdesk.news/developers&lt;/a&gt;. Not investment advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>bitcoin</category>
      <category>blockchain</category>
      <category>cryptocurrency</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Ledger Users Report $604,000 in Thefts Linked to Dubai Virgin Megastore Purchases</title>
      <dc:creator>Basis Desk</dc:creator>
      <pubDate>Wed, 18 Nov 2026 02:46:29 +0000</pubDate>
      <link>https://dev.to/basisdesk/ledger-users-report-604000-in-thefts-linked-to-dubai-virgin-megastore-purchases-1d2b</link>
      <guid>https://dev.to/basisdesk/ledger-users-report-604000-in-thefts-linked-to-dubai-virgin-megastore-purchases-1d2b</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — &lt;a href="https://basisdesk.news/about/how-we-use-ai?utm_source=devto" rel="noopener noreferrer"&gt;how we use AI&lt;/a&gt;. Originally published on &lt;a href="https://basisdesk.news/news/ledger-hardware-wallet-tampering-dubai-virgin-megastore?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Two hardware wallet owners allege their tampered Ledger devices originated from an authorized UAE retail partner.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Key points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Two users reported losing $604,000 combined in $SOL and $USDT via tampered Ledger wallets bought in Dubai [1].&lt;/li&gt;
&lt;li&gt;Mark Karpelès’ OSINT registry verified a hardware implant inside one victim's Ledger Flex unit [1].&lt;/li&gt;
&lt;li&gt;Both devices were allegedly purchased from Virgin Megastore, an authorized Ledger retailer in the UAE [1].&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Two hardware wallet owners reported a combined loss of roughly $604,000 in digital assets after using tampered Ledger units allegedly purchased from an authorized retail store in Dubai [1].&lt;/p&gt;

&lt;p&gt;An X user posting as Rewinsky reported the theft of approximately 1,300 Solana ($SOL) following the use of a modified Ledger Flex [1]. Mark Karpelès’ Ledger Implant OSINT registry confirmed the presence of a hardware implant in the device, pointing to antenna components identical to those observed in earlier compromised Flex units [1]. In a separate report on Tuesday, a user operating under the handle New Babylon Order Worldwide stated that 507,000 Tether ($USDT) was drained from their Ledger Stax on Saturday [1]. That owner noted the unit was bought on Oct. 11 from Virgin Megastore in Dubai, shortly after Ledger announced an inquiry into retail stock sold through Southeast Asian distributor CryptoBilis [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  Retail Supply Chain Exposure
&lt;/h2&gt;

&lt;p&gt;The reports suggest that fraudulent physical modifications targeting Ledger devices have reached retail channels in the United Arab Emirates, moving beyond earlier documented incidents in Asia and Europe [1]. Virgin Megastore operates eight locations in Dubai, such as branches in Dubai Mall and Mall of the Emirates, and is formally listed by Ledger as an authorized merchant in the country [1]. &lt;/p&gt;

&lt;p&gt;The physical tampering disclosures follow broader retail hardware integration moves, including recent initiatives where &lt;a href="https://basisdesk.news/news/solana-mobile-ledger-atom-hardware-partner" rel="noopener noreferrer"&gt;Solana Mobile named Ledger as its first hardware expansion partner&lt;/a&gt;. With broader crypto sentiment sitting in Extreme Fear at the time of writing, these physical supply-chain exploits present direct security hurdles for self-custody adoption. Neither Ledger nor Virgin Megastore had provided official statements regarding the Dubai claims at the time of publication [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Which Ledger models were reported as compromised in Dubai?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The reported incidents involved one Ledger Flex unit and one Ledger Stax device.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where were the tampered devices allegedly purchased?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Victims reported purchasing the devices at Virgin Megastore in Dubai, an authorized Ledger retailer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://cointelegraph.com/news/ledger-hardware-implant-saga-reaches-dubais-virgin-megastore?utm_source=rss_feed&amp;amp;utm_medium=rss&amp;amp;utm_campaign=rss_partner_inbound" rel="noopener noreferrer"&gt;Ledger hardware implant saga reaches Dubai’s Virgin Megastore&lt;/a&gt; — Primary document (discovered)&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;&lt;a href="https://basisdesk.news?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt; is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: &lt;a href="https://basisdesk.news/developers?utm_source=devto" rel="noopener noreferrer"&gt;basisdesk.news/developers&lt;/a&gt;. Not investment advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>blockchain</category>
      <category>cryptocurrency</category>
      <category>news</category>
    </item>
    <item>
      <title>Optimizely Tag Poisoning Injects Crypto Clipper Across CNN, Zoom, and Fox News</title>
      <dc:creator>Basis Desk</dc:creator>
      <pubDate>Tue, 17 Nov 2026 11:51:22 +0000</pubDate>
      <link>https://dev.to/basisdesk/optimizely-tag-poisoning-injects-crypto-clipper-across-cnn-zoom-and-fox-news-20of</link>
      <guid>https://dev.to/basisdesk/optimizely-tag-poisoning-injects-crypto-clipper-across-cnn-zoom-and-fox-news-20of</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — &lt;a href="https://basisdesk.news/about/how-we-use-ai?utm_source=devto" rel="noopener noreferrer"&gt;how we use AI&lt;/a&gt;. Originally published on &lt;a href="https://basisdesk.news/news/optimizely-supply-chain-skimmer-crypto-clipper-cnn-zoom?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;An attacker injected a multi-chain address swapper and card skimmer into enterprise web bundles, exposing millions of visitors across 15 high-profile domains.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Key points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Compromised Optimizely bundles delivered a crypto-clipper and card skimmer across 15 prominent websites, including CNN, Zoom, and Salesforce [1].&lt;/li&gt;
&lt;li&gt;The malware replaces wallet addresses across eight blockchains, including BTC, ETH, and SOL, using checksum-validated regex [1].&lt;/li&gt;
&lt;li&gt;Strict Content Security Policy directives successfully blocked payload execution on two compromised domains [1].&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A supply chain campaign designated OPTIMJACK compromised third-party JavaScript tag layers across 15 major consumer and enterprise websites on Nov. 16, injecting a script that secretly swaps cryptocurrency addresses and steals payment credentials [1]. Impacted properties include CNN, Zoom, Fox News, BBC, Salesforce, and GitLab [1].&lt;/p&gt;

&lt;p&gt;According to an analysis published by amirulcyber.com, attackers inserted unauthorized code into JavaScript bundles served through digital experience platform Optimizely, alongside secondary vectors involving ad wrappers and protected first-party scripts [1]. The injected snippet fetches an external payload from command-and-control server &lt;code&gt;1688360[.]cc&lt;/code&gt;, appending &lt;code&gt;track.js&lt;/code&gt; directly to document head elements [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  Multi-Chain Clipboard Hijacking and Data Exfiltration
&lt;/h2&gt;

&lt;p&gt;The malicious script executes a multi-component operation led by a crypto-clipper supporting eight networks: $BTC, $ETH, $SOL, $LTC, $DOGE, $TRX, Bitcoin Cash, and TON [1]. The clipper uses checksum validations—including base58check, bech32, cashaddr, and TON CRC16—to identify valid destination addresses [1]. When matched, it alters clipboard contents, DOM text, text areas, framework models, and network request payloads, replacing the user's intended target address with attacker-controlled wallets [1]. Similar threats are explored in Basis Desk's coverage on &lt;a href="https://basisdesk.news/news/clipboard-hijackers-and-malware" rel="noopener noreferrer"&gt;clipboard hijackers and malware&lt;/a&gt; and the broader scope of &lt;a href="https://basisdesk.news/news/optimizely-supply-chain-malware-crypto-hijack" rel="noopener noreferrer"&gt;Optimizely supply chain malware&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Beyond replacing transaction destinations, the script functions as a web skimmer [1]. It captures credit card details through form-hooking and Luhn algorithm checks, steals page cookies, captures JPEG screenshots of active sessions via &lt;code&gt;html2canvas&lt;/code&gt;, and transmits exfiltrated data back to remote C2 endpoints [1]. An obfuscated secondary payload, &lt;code&gt;boot.js&lt;/code&gt;, was also observed targeting iOS devices on version 18.6 or lower via hidden iframes [1].&lt;/p&gt;

&lt;p&gt;Security findings show that two affected sites mitigated the script execution through strict Content Security Policy (CSP) headers, which blocked the unauthorized external &lt;code&gt;script-src&lt;/code&gt; calls [1]. Technical mitigation guidance urges IT administrators to inspect Optimizely bundles, verify outbound domains against CSP controls, and audit clipboard modifications on staging endpoints [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://amirulcyber.com/2026/11/16/optimjack-optimizely-skimmer" rel="noopener noreferrer"&gt;CNN, Zoom, Fox News Served Visitors a Crypto-Stealing Skimmer – OPTIMJACK (Nov 2026)&lt;/a&gt; — Primary document (discovered)&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;&lt;a href="https://basisdesk.news?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt; is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: &lt;a href="https://basisdesk.news/developers?utm_source=devto" rel="noopener noreferrer"&gt;basisdesk.news/developers&lt;/a&gt;. Not investment advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>blockchain</category>
      <category>cryptocurrency</category>
      <category>news</category>
    </item>
    <item>
      <title>Optimizely Supply Chain Attack Hijacks Crypto Addresses Across 178 Brand Websites</title>
      <dc:creator>Basis Desk</dc:creator>
      <pubDate>Tue, 17 Nov 2026 01:16:08 +0000</pubDate>
      <link>https://dev.to/basisdesk/optimizely-supply-chain-attack-hijacks-crypto-addresses-across-178-brand-websites-3oil</link>
      <guid>https://dev.to/basisdesk/optimizely-supply-chain-attack-hijacks-crypto-addresses-across-178-brand-websites-3oil</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — &lt;a href="https://basisdesk.news/about/how-we-use-ai?utm_source=devto" rel="noopener noreferrer"&gt;how we use AI&lt;/a&gt;. Originally published on &lt;a href="https://basisdesk.news/news/optimizely-supply-chain-malware-crypto-hijack?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Attackers tampered with Optimizely Web snippets to swap wallet addresses, deliver iOS exploits, and divert stolen funds across major enterprise sites.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Key points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Malicious JavaScript injected into Optimizely Web snippets affected 188 customer files across 178 corporate websites on Nov. 16 [1].&lt;/li&gt;
&lt;li&gt;The multi-vector payload replaced cryptocurrency addresses, skimmed payment forms, and distributed Coruna and DarkSword iOS exploit chains [1].&lt;/li&gt;
&lt;li&gt;Attackers secured roughly $7,040 across BTC, ETH, USDT, and LTC before sweeping funds to exchange deposit addresses [1].&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A widespread supply-chain compromise struck the Optimizely Web experimentation platform on Nov. 16, injecting malicious JavaScript into scripts delivered to visitors across 178 organizations [1]. The breach impacted high-traffic platforms including hardware wallet provider Ledger, as well as Zoom, the BBC, CNN, Salesforce, GitLab, and HSBC [1]. Attackers altered the "Project JavaScript" field within customer projects, which allowed the code to execute from Optimizely's trusted content delivery network without breaching individual company infrastructures [1].&lt;/p&gt;

&lt;p&gt;The inserted code functioned as a multi-purpose malware suite designed to siphon digital assets and compromise visitor devices [1]. Primarily acting as a clipboard hijacker and address clippersimilar to tactics tracked in &lt;a href="https://basisdesk.news/news/clipboard-hijackers-and-malware" rel="noopener noreferrer"&gt;crypto malware research&lt;/a&gt;the script scanned pages and system clipboards for valid addresses tied to Bitcoin, Ethereum, EVM networks, TRON, Solana, Litecoin, and Dogecoin [1]. When detected, it substituted the recipient's address with one operated by the attacker, while also modifying outgoing web requests and navigation events [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  Multi-Vector Exploitation and Stolen Assets
&lt;/h2&gt;

&lt;p&gt;Beyond address manipulation, the threat actors iterated on the payload 26 times throughout the day, attaching card-skimming modules alongside the Coruna and DarkSword iOS exploit chains aimed at Apple devices [1]. Stolen funds were periodically consolidated; by 19:25 UTC on Nov. 16, attacker-controlled wallets had taken in roughly $7,040 in assets across $BTC, $ETH, $USDT, and other tokens before routing portions through exchange deposit addresses [1]. At the time of writing, Bitcoin traded near $64,628 while broad market sentiment registered Extreme Fear.&lt;/p&gt;

&lt;p&gt;Cleanup efforts cleared the vast majority of malicious instances by late Nov. 16, dropping the active count of infected snippets from 169 down to a single remaining endpoint by 21:52 UTC [1]. Optimizely has not yet publicly clarified how the attackers obtained write access across unrelated customer accounts [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely" rel="noopener noreferrer"&gt;World's Largest Brands Infected With Malware Via Optimizely&lt;/a&gt; — Primary document (discovered)&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;&lt;a href="https://basisdesk.news?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt; is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: &lt;a href="https://basisdesk.news/developers?utm_source=devto" rel="noopener noreferrer"&gt;basisdesk.news/developers&lt;/a&gt;. Not investment advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>blockchain</category>
      <category>cryptocurrency</category>
      <category>news</category>
    </item>
    <item>
      <title>Vitalik Buterin Backs leanPCS to Accelerate Quantum-Resistant Ethereum</title>
      <dc:creator>Basis Desk</dc:creator>
      <pubDate>Mon, 16 Nov 2026 10:01:30 +0000</pubDate>
      <link>https://dev.to/basisdesk/vitalik-buterin-backs-leanpcs-to-accelerate-quantum-resistant-ethereum-3967</link>
      <guid>https://dev.to/basisdesk/vitalik-buterin-backs-leanpcs-to-accelerate-quantum-resistant-ethereum-3967</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — &lt;a href="https://basisdesk.news/about/how-we-use-ai?utm_source=devto" rel="noopener noreferrer"&gt;how we use AI&lt;/a&gt;. Originally published on &lt;a href="https://basisdesk.news/news/vitalik-buterin-endorses-leanpcs-quantum-safe-ethereum?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The Ethereum co-founder endorsed leanPCS under draft proposal EIP-8288 to aggregate bulky post-quantum proofs off-chain without waiting for new language consensus.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Key points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Vitalik Buterin endorsed leanPCS under draft EIP-8288 to compress quantum-safe signatures and proofs before publishing on Ethereum.&lt;/li&gt;
&lt;li&gt;Quantum-resistant signatures expand payload sizes up to 6 kilobytes, which Buterin identified as unsustainable for direct on-chain storage.&lt;/li&gt;
&lt;li&gt;LeanPCS enables rapid implementation without requiring immediate consensus on a new execution language beyond the EVM.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ethereum co-founder Vitalik Buterin voiced support on Nov. 16 for leanPCS, describing it as an accelerated path toward deploying quantum-resistant cryptography across the network [1]. The approach, developed under draft proposal EIP-8288, aims to compress bulky post-quantum signatures and zero-knowledge proofs before they are published to the Ethereum blockchain [1]. At the time of writing, $ETH traded down 1.7% over 24 hours at $1,796 amid broader market weakness.&lt;/p&gt;

&lt;p&gt;Elliptic curve cryptography currently protects account access on Ethereum and Bitcoin, but future quantum hardware is expected to breach these mechanisms [1]. Standard quantum-safe alternatives require substantially more data: signatures expand from 65 bytes to between 1 and 6 kilobytes, while zero-knowledge proofs increase from a few hundred bytes to roughly 128 kilobytes [1]. Buterin wrote that committing this volume of information directly on-chain is unsustainable [1]. Co-authored with developer Thomas Coratger in June, EIP-8288 resolves this scaling bottleneck by having nodes aggregate user signatures and proofs into recurring STARK proofs until a single master proof validates the entire block, leaving only compact claims on-chain [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  Implementation Trade-Offs
&lt;/h2&gt;

&lt;p&gt;EIP-8288 outlines three technical avenues, differing in flexibility and deployment speed [1]. The narrowest option, leanSPHINCS, supports only hash-based signatures, reducing verification overhead to roughly 3,000 gas per signature through protocol-level aggregation compared to the approximately 150,000 gas required today on Ethereum without protocol alterations [1]. The most flexible option, leanSTARK, would accommodate arbitrary signature systems and privacy designs, but relies on Ethereum agreeing on an execution language beyond the Ethereum Virtual Machine (EVM) [1].&lt;/p&gt;

&lt;p&gt;Buterin endorsed leanPCS as the preferred middle ground, arguing that it achieves the flexibility of leanSTARK while requiring fewer foundational design choices, enabling rapid delivery [1]. The focus builds upon the broader &lt;a href="https://basisdesk.news/news/ethereum-post-quantum-cryptography-roadmap" rel="noopener noreferrer"&gt;Ethereum post-quantum cryptography roadmap&lt;/a&gt; coordinated by the Ethereum Foundation, which established a specialized post-quantum research team in January [1]. Under this strategy, leanPCS could serve as an immediate bridge to protect consensus and execution while broader language decisions for leanSTARK proceed in parallel [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://decrypt.co/383294/vitalik-buterin-now-a-total-bull-on-leanpcs-as-fast-track-to-quantum-safe-ethereum" rel="noopener noreferrer"&gt;Vitalik Buterin Now ‘a Total Bull’ on leanPCS as Fast Track to Quantum-Safe Ethereum&lt;/a&gt; — Primary document (discovered)&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;&lt;a href="https://basisdesk.news?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt; is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: &lt;a href="https://basisdesk.news/developers?utm_source=devto" rel="noopener noreferrer"&gt;basisdesk.news/developers&lt;/a&gt;. Not investment advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>web3</category>
      <category>cryptocurrency</category>
      <category>news</category>
    </item>
    <item>
      <title>Luxor Patches Commander Platform Breach Following Hashrate Hijacking</title>
      <dc:creator>Basis Desk</dc:creator>
      <pubDate>Mon, 16 Nov 2026 02:56:10 +0000</pubDate>
      <link>https://dev.to/basisdesk/luxor-patches-commander-platform-breach-following-hashrate-hijacking-ikn</link>
      <guid>https://dev.to/basisdesk/luxor-patches-commander-platform-breach-following-hashrate-hijacking-ikn</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — &lt;a href="https://basisdesk.news/about/how-we-use-ai?utm_source=devto" rel="noopener noreferrer"&gt;how we use AI&lt;/a&gt;. Originally published on &lt;a href="https://basisdesk.news/news/luxor-commander-mining-breach-ai-security?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Attackers redirected mining power from over a dozen accounts to another pool, prompting Luxor's CEO to warn of automated AI-driven cyber threats.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Key points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Attackers breached Luxor's Commander tool, redirecting hashrate from over a dozen accounts to the OCEAN mining pool [1].&lt;/li&gt;
&lt;li&gt;Luxor patched the vulnerability within two hours, isolated the fault, and promised full reimbursement to affected clients [1].&lt;/li&gt;
&lt;li&gt;A wallet associated with the exploit received approximately 0.162 BTC ($10,500) in redirected mining payouts [1].&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Bitcoin mining software firm Luxor Technology experienced a cybersecurity breach over the weekend affecting its Commander management tool, redirecting customer computing power to the OCEAN mining pool [1]. The incident impacted just over a dozen accounts, with attackers reportedly receiving approximately 0.162 $BTC—valued around $10,500—in payout rewards across two transactions, according to data identified by CoreX [1].&lt;/p&gt;

&lt;p&gt;Luxor stated that it patched the Commander vulnerability within two hours of detection and began returning affected rigs to their original mining configurations [1]. The firm confirmed that other products, including Luxor Pool and LuxOS, remained unaffected by the incident [1]. Furthermore, Luxor committed to reimbursing affected customers entirely for the diverted computing power and announced plans to issue a post-mortem review [1]. At the time of writing, $BTC traded at $64,952 amid widespread market caution.&lt;/p&gt;

&lt;h2&gt;
  
  
  Automated Attack Vectors Threaten Infrastructure
&lt;/h2&gt;

&lt;p&gt;Following the incident, Luxor Chief Executive Officer Nick Hansen warned that crypto infrastructure operators are confronting an increasingly aggressive landscape driven by automated, AI-assisted exploitation [1]. Hansen noted that bad actors are deploying continuous automated scans against corporate attack surfaces to detect and exploit minor vulnerabilities [1]. In response, Luxor paused primary feature development to strengthen defensive infrastructure, securing graphics processing units to deploy open-weight defensive models internally [1]. This development follows wider industry expansion into high-performance computing, such as when &lt;a href="https://basisdesk.news/news/luxor-technology-raises-16-million-ai-compute-derivatives" rel="noopener noreferrer"&gt;Luxor Technology raises $16 million to expand AI compute and derivatives desk&lt;/a&gt; operations.&lt;/p&gt;

&lt;p&gt;The intrusion reflects a broader escalation of AI-augmented threats recorded across digital asset and cybersecurity sectors [1]. India's national cybersecurity agency previously identified malicious clusters such as Crafty Falcon using AI utilities against financial services and exchanges [1]. Similar automated methodology was cited in an October breach at Chainalysis involving offensive agentic techniques, while Anthropic documented automated exploit research frameworks targeting enterprise networks in September [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://cointelegraph.com/news/luxor-ceo-warns-of-ai-dark-forest-after-bitcoin-miner-hijack?utm_source=rss_feed&amp;amp;utm_medium=rss&amp;amp;utm_campaign=rss_partner_inbound" rel="noopener noreferrer"&gt;Luxor CEO warns of AI ‘dark forest’ after Bitcoin miner hijack&lt;/a&gt; — Primary document (discovered)&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;&lt;a href="https://basisdesk.news?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt; is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: &lt;a href="https://basisdesk.news/developers?utm_source=devto" rel="noopener noreferrer"&gt;basisdesk.news/developers&lt;/a&gt;. Not investment advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>blockchain</category>
      <category>cryptocurrency</category>
      <category>news</category>
    </item>
    <item>
      <title>Coinone Warns of Phishing and Identity Theft After Customer Service Breach</title>
      <dc:creator>Basis Desk</dc:creator>
      <pubDate>Sun, 15 Nov 2026 08:31:16 +0000</pubDate>
      <link>https://dev.to/basisdesk/coinone-warns-of-phishing-and-identity-theft-after-customer-service-breach-1385</link>
      <guid>https://dev.to/basisdesk/coinone-warns-of-phishing-and-identity-theft-after-customer-service-breach-1385</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — &lt;a href="https://basisdesk.news/about/how-we-use-ai?utm_source=devto" rel="noopener noreferrer"&gt;how we use AI&lt;/a&gt;. Originally published on &lt;a href="https://basisdesk.news/news/coinone-customer-data-breach-metam-phishing-warning?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;An attacker breached outsourced customer service provider MetaM, accessing support records that contained personal details, bank accounts, and passwords.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Key points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;An attacker breached customer support records at Coinone vendor MetaM, accessing personal details, IDs, bank accounts, and passwords.&lt;/li&gt;
&lt;li&gt;Coinone stated core exchange, trading, and wallet systems remain separate and uncompromised, with no direct internal breach detected.&lt;/li&gt;
&lt;li&gt;The breach follows recent South Korean FSC findings of security deficiencies at 130 financial firms and new withdrawal-freeze rules for exchanges.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;South Korean cryptocurrency exchange Coinone warned customers of potential identity theft and phishing risks after an intruder breached its third-party customer support provider [1]. The incident occurred when an attacker accessed systems run by MetaM, an outsourced support vendor, compromising customer service records viewed or extracted during support inquiries [1]. Coinone stated it discovered the intrusion on the same day the servers were breached [1].&lt;/p&gt;

&lt;p&gt;According to Coinone, the exposed information includes full names, dates of birth, phone numbers, email addresses, national identification numbers, bank account numbers, residential addresses, crypto wallet addresses, transaction IDs, and passwords shared during support interactions [1]. The exchange noted that the specific records exposed vary by individual, and users who never contacted customer service were not impacted [1]. Coinone did not reveal the total number of affected users [1]. Users who submitted credentials during previous support sessions were urged to change them, as bad actors could deploy the stolen records for targeted &lt;a href="https://basisdesk.news/news/common-crypto-scams" rel="noopener noreferrer"&gt;phishing scams&lt;/a&gt; [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  Exchange Infrastructure Intact Amid Regulatory Push
&lt;/h2&gt;

&lt;p&gt;Coinone clarified that its internal trading, account, and custody wallet infrastructure remains uncompromised, as these core systems operate independently from MetaM's external servers [1]. The platform confirmed it reported the security incident to South Korean law enforcement and regulatory authorities [1]. Similar supply-chain vulnerabilities have previously affected major trading platforms, such as when a &lt;a href="https://basisdesk.news/news/coinbase-vendor-amplitude-data-breach-funds-safe" rel="noopener noreferrer"&gt;Coinbase vendor breach&lt;/a&gt; exposed select user information while core funds remained isolated.&lt;/p&gt;

&lt;p&gt;The disclosure aligns with increased regulatory scrutiny across South Korea's financial ecosystem [1]. In October, the Financial Services Commission (FSC) reported security deficiencies across 130 of 555 evaluated financial institutions [1]. Days before the Coinone disclosure, the FSC announced rules permitting digital asset exchanges to halt withdrawals upon suspecting a hack, while requiring continuous, 24-hour network monitoring [1]. At the time of writing, broader market sentiment remains constrained, with $BTC trading at $64,535 and $ETH at $1,796 amid extreme market fear.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://cointelegraph.com/news/coinone-data-breach-phishing-identity-theft-customer-information?utm_source=rss_feed&amp;amp;utm_medium=rss&amp;amp;utm_campaign=rss_partner_inbound" rel="noopener noreferrer"&gt;Coinone warns of phishing, identity theft after customer data breach&lt;/a&gt; — Primary document (discovered)&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;&lt;a href="https://basisdesk.news?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt; is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: &lt;a href="https://basisdesk.news/developers?utm_source=devto" rel="noopener noreferrer"&gt;basisdesk.news/developers&lt;/a&gt;. Not investment advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>blockchain</category>
      <category>cryptocurrency</category>
      <category>news</category>
    </item>
    <item>
      <title>Aztec Outlines Tierra V6 Rollup Architecture to Deter Illicit Capital</title>
      <dc:creator>Basis Desk</dc:creator>
      <pubDate>Sat, 14 Nov 2026 21:06:15 +0000</pubDate>
      <link>https://dev.to/basisdesk/aztec-outlines-tierra-v6-rollup-architecture-to-deter-illicit-capital-2j2o</link>
      <guid>https://dev.to/basisdesk/aztec-outlines-tierra-v6-rollup-architecture-to-deter-illicit-capital-2j2o</guid>
      <description>&lt;p&gt;&lt;em&gt;AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — &lt;a href="https://basisdesk.news/about/how-we-use-ai?utm_source=devto" rel="noopener noreferrer"&gt;how we use AI&lt;/a&gt;. Originally published on &lt;a href="https://basisdesk.news/news/aztec-unveils-tierra-v6-private-rollup?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Co-founder Zac Williamson detailed cryptographic serial numbers, formal verification, and decentralized rollup mechanics for the Ethereum layer-2 network.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Key points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Aztec's Tierra V6 upgrade doubles proving speeds, bringing confirmation times to roughly 12 seconds.&lt;/li&gt;
&lt;li&gt;A note serial-number system lets users cryptographically prove funds are disconnected from Lazarus Group hacks without exposing account data.&lt;/li&gt;
&lt;li&gt;The Stage 2 rollup relies on staking and slashable sequencers with no security council, alongside Zcash-style turnstile double-spend defenses.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Aztec co-founder Zac Williamson detailed the technical specifications of Tierra, the V6 upgrade to the network's private Ethereum layer-2 protocol, in an interview released on Nov. 14 [1]. The update introduces structural changes aimed at isolating illicit capital and accelerating transaction settlement across the network [1].&lt;/p&gt;

&lt;p&gt;Under the Tierra upgrade, Aztec's proving speeds have doubled, reducing transaction confirmation intervals to approximately 12 seconds [1]. The privacy protocol utilizes an unspent transaction output (UTXO) note model analogous to $BTC, ensuring that dusted assets cannot compromise the balance of a recipient's broader account [1]. To address compliance and sanctions concerns, Aztec implemented a note serial-number mechanism based on privacy pool designs, enabling depositors to cryptographically demonstrate that their balances exclude funds linked to state-sponsored actors, including North Korea's Lazarus Group, without exposing identifying transaction history [1].&lt;/p&gt;

&lt;h2&gt;
  
  
  Governance and Double-Spend Defenses
&lt;/h2&gt;

&lt;p&gt;Williamson noted that Aztec operates as a Stage 2 rollup where decentralized sequencers stake capital, face slashing conditions, and participate in protocol upgrade votes without relying on an administrative security council [1]. To defend against undetectable double-spend vulnerabilities in zero-knowledge circuits, the protocol incorporates a turnstile accounting system modeled on Zcash [1]. Additionally, the platform supports granular per-account viewing keys, allowing participants to selectively share transaction ledgers with regulatory entities, such as the Internal Revenue Service, without activating a centralized auditor backdoor [1].&lt;/p&gt;

&lt;p&gt;Protocol security operations also integrated an automated 24/7 artificial intelligence auditing harness that identified critical vulnerabilities within Aztec's cryptographic libraries prior to formal verification [1]. Ecosystem deployments planned for the Tierra environment include the zk.money neobank, a confidential AI inference marketplace, and an anonymous social network collateralized by Ethereum bonds [1]. At the time of writing, $ETH traded at $1,787 amidst broader crypto market downturns.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;How does Aztec prevent dusted notes from tainting account balances?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Aztec relies on an unspent transaction output note model similar to Bitcoin, isolating incoming dusted transactions from the rest of the user's funds.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How can Aztec users prove compliance without revealing identity?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The protocol utilizes private note serial numbers under a privacy pools architecture, letting depositors mathematically show their assets do not originate from blacklisted sources like Lazarus Group.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://unchainedcrypto.com/can-private-protocols-keep-north-korea-out-aztecs-zac-williamson-thinks-so/" rel="noopener noreferrer"&gt;Can Private Protocols Keep North Korea Out? Aztec’s Zac Williamson Thinks So&lt;/a&gt; — Primary document (discovered)&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;&lt;a href="https://basisdesk.news?utm_source=devto" rel="noopener noreferrer"&gt;Basis Desk&lt;/a&gt; is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: &lt;a href="https://basisdesk.news/developers?utm_source=devto" rel="noopener noreferrer"&gt;basisdesk.news/developers&lt;/a&gt;. Not investment advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>web3</category>
      <category>cryptocurrency</category>
      <category>news</category>
    </item>
  </channel>
</rss>
