# Creator Pulse: Mercado Bitcoin investigations separate stolen funds from frozen assets Creator Pulse, edition 1. Published 2026-11-03. 5 min read. Canonical page: https://www.w3match.com/reports/creators-2026-11-03 Two investigators put Mercado Bitcoin's November 2 losses near $49 million, with different chain coverage and freeze totals. Separately, new SEC staff answers explain how governance participation relates to control. Both stories turn on powers that remain behind an interface. ## In one minute Two investigators put Mercado Bitcoin's November 2 losses near $49 million, with different chain coverage and freeze totals. Separately, new SEC staff answers explain how governance participation relates to control. Both stories turn on powers that remain behind an interface. ## The lead story ### The recovery question depends on which assets can be stopped [Chainalysis's November 2 account](https://www.chainalysis.com/blog/chainalysis-response-mercado-bitcoin/) estimates approximately $49 million stolen from Mercado Bitcoin and nearly $10 million frozen through coordinated intervention. These are the responding firm's reported estimates, not an audited final loss or a customer reimbursement total. [Bitquery's November 2 investigation](https://www.bitquery.io/investigations/mercado-bitcoin-hack) reports $48.5 million across ten blockchains and $7.3 million frozen. Chainalysis describes activity across 17 chains. These reports independently support a substantial incident, while their individual totals retain their own scope and check times. **Why now:** The investigation concerns a new incident, and its immediate consequences extend beyond the first reported transfer. Freezing an asset prevents movement under the relevant token's controls; returning money requires a separate process. A report about frozen funds should therefore keep the customer recovery question open. **An angle worth explaining:** The response illustrates how crypto assets differ in their intervention mechanisms. Investigators can trace transfers and contact organizations able to act, but tracing alone does not confer the ability to reverse a transaction. Stablecoin issuer controls can create an intervention point that native assets do not share in the same way. That difference shapes the response after a custody breach. **What remains uncertain:** The incident's final loss, technical cause and customer recovery outcome remain unresolved here. The two investigations do not supply a reconciled inventory; differing chain coverage and check times prevent treating their freeze totals as interchangeable. The firm's account is evidence of its response and estimate, not independent proof of every attributed wallet. A useful follow-up should identify the steps toward customer restitution. What transactions are included in the incident inventory? Which restrictions are actually recorded for those assets? Who controls the next step toward restitution? An updated statement answering those questions would add substance beyond another changing dollar estimate. It would also make it possible to compare progress over time without silently changing the population being measured. ## More stories worth covering ### SEC staff distinguishes governance participation from coordinated control The [SEC staff FAQ updated November 2](https://www.sec.gov/about/divisions-offices/division-corporation-finance/faqs-crypto-assets) adds answers about broad-based governance, authority over participation and functionality versus decentralization. Unaffiliated governance participants generally are not treated as a coordinated group merely for participating, subject to the stated factual conditions. **Why now:** The new answers give creators a specific document to explain rather than a broad claim that all governance tokens have received regulatory clearance. **An angle worth explaining:** Ask who can change access, voting processes or protocol operation. A governance interface and a dispersed holder list do not answer those operational questions. The staff's framework directs attention to actual authority and coordination. A concrete explanation can separate the right to express a preference from the power to execute it. A holder may vote while another actor retains an implementation gate. An approved proposal can still require a separately authorized actor to implement it. Assessing a project therefore calls for its actual delegation arrangements, administrator permissions and upgrade process, rather than a conclusion based on the existence of a token ballot. This gives creators a practical document comparison: put the governance description beside the implementation rules and identify where authority changes hands. The reader learns who can act, which decision is binding and what remains contingent. That analysis is more useful than applying a blanket label to every project with similar branding. **What remains uncertain:** These are staff views without legal force, not a new Commission rule or a determination about any particular token. Applying them to a project requires its own facts. ### NEAR's issuance proposal makes validator adoption the implementation gate The [HSP-029 proposal document](https://gov.near.org/t/hsp-029-establish-a-24-month-issuance-ramp-to-a-1-6-target-rate-of-near-token-emissions/42644) describes a 24-month path from a 2.5% maximum annual issuance rate to 1.6%. It explicitly requires validator adoption; a House of Stake vote cannot activate the change alone. The proposal is context for current discussion of issuance reform, rather than proof here of a completed protocol change. **Why now:** The November 2 SEC staff update makes the distinction between a governance vote and implementation authority a timely question. NEAR provides a concrete proposal to examine alongside that discussion, without implying a legal classification of its token. The relevant distinction for holders is when the network's actual issuance rules change, not when a headline starts using the proposed endpoint. This edition does not independently establish the final ballot tally or activation date. **An angle worth explaining:** A lower issuance cap affects more than dilution. It changes the tokens available to compensate staking participants, so the debate includes the economics of operating validators. The proposed endpoint is 0.9 percentage points below the starting cap, a 36% relative reduction. That arithmetic describes the rate change; it is neither a prediction of token appreciation nor a promise that every staker's yield falls by exactly that amount. The central editorial question is who bears the adjustment. A holder's exposure to supply growth differs from an operator's need to pay operating expenses. A successful design would have to preserve sufficient participation while changing issuance. Evidence of adoption and subsequent network operation would be more informative than assuming that a supply-policy announcement has already delivered its intended economic result. **What remains uncertain:** Activation, the realized issuance path and the effect on participation require subsequent confirmation. The proposal's economic arguments remain arguments by its authors; its existence does not independently verify their modeled outcomes. ## Sources - [Chainalysis's November 2 account](https://www.chainalysis.com/blog/chainalysis-response-mercado-bitcoin/), www.chainalysis.com, Publication date not specified - [Bitquery's November 2 investigation](https://www.bitquery.io/investigations/mercado-bitcoin-hack), www.bitquery.io, Publication date not specified - [SEC staff FAQ updated November 2](https://www.sec.gov/about/divisions-offices/division-corporation-finance/faqs-crypto-assets), www.sec.gov, Publication date not specified - [HSP-029 proposal document](https://gov.near.org/t/hsp-029-establish-a-24-month-issuance-ramp-to-a-1-6-target-rate-of-near-token-emissions/42644), gov.near.org, Publication date not specified Every number names its provider and date. Not financial advice.