Whitepaper 2.0, Two Sets of State Forks, the Rise of Clones: What Happened to Sato Overnight?

marsbitPubblicato 2026-05-08Pubblicato ultima volta 2026-05-08

Introduzione

On the night of May 7, 2026, the SATO project released "Whitepaper 2.0" alongside significant front-end changes, shifting from "buy/sell" to "mint/burn" terminology. This update aimed to clarify market confusion regarding trading mechanics, token burns, and price discrepancies between its bonding curve and secondary markets. Key changes included explicitly defining the separate existence of the bonding curve pool (for minting/burning) and the secondary SATO/USDT pool, and detailing the core mathematical formulas governing the curve. Concurrently, SATO's market cap fell sharply from near $40 million to around $14.4 million. A fork project, SAT1, emerged with a similar bonding curve model but a key technical difference: SAT1 uses a single unified state variable (`ethCum`) for all core logic (minting, burning, halt trigger), whereas SATO's mechanism relies on two state variables (`ethCum` and `totalMintedFair`), which can drift apart and cause operational discrepancies. Both projects position themselves as operator-free "issuance machines" with asymptotic supply curves approaching 21 million tokens and charge a 0.3% fee on transactions, which remains in the protocol. The article emphasizes that despite intricate designs, both SATO and SAT1 are in highly volatile, sentiment-driven phases, and warns that mechanism innovation does not replace the need for personal risk management.

Original Author: KarenZ, Foresight News

On the evening of May 7, 2026, amid market skepticism regarding the pricing drift of Sato within the Curve pool and the divergence between its price on the official website and the secondary market, the Sato official website updated its whitepaper entry to "Whitepaper 2.0." Simultaneously, the front-end trading interface changed from "Buy / Sell" to "Mint / Burn."

This was not just a simple wording revision. Comparing versions 1.0 and 2.0 reveals the key points rewritten by the official team overnight: the focus is not on sentiment or narrative, but on clarifying market understanding regarding how Sato is actually traded, under what conditions tokens are burned, and why prices differ between the official website and secondary markets.

Meanwhile, Sato's market capitalization dropped from yesterday's high of nearly $40 million to $14.4 million. On the other hand, the clone project Sat1 also released its own whitepaper and front-end website. Its market cap reached $10 million around noon and has since fallen to approximately $5.2 million.

It is crucial to remind that both Sato and Sat1 are currently in a phase of high volatility and high emotional-driven activity. Their mechanisms may seem intricate, but that does not guarantee the market will operate as designed. No mechanism innovation can replace risk management. Before participating, carefully assess your own risk tolerance and make prudent decisions.

What Changes Did Sato Whitepaper 2.0 Make?

Version 1.0 focused on explaining an exponential issuance curve, the permanent closure of the self-deprecated minting function at 99% of the supply, no pre-mining, no allocation, no admin role, no upgrade path, and the rule that selling triggers burning.

Version 2.0 adopts a different structure, divided into clear sections: Issuance, The Pool is the Reserve, Curve Mathematics & Limitations, Mint Stop, Trading Phases, Routing and Trading Options.

A very important addition in the new version is the inclusion of the three core formulas governing Sato's Curve mechanics:

  • Total minted supply when cumulative ETH is e: q(e) = K · (1 − e^(−e/S)), where K = 21,000,000, S = 500 ETH
  • Price per token at position e: p(e) = (S / K) · e^(e/S)
  • ETH to be refunded when current supply is q and burn amount is b: Δe(q, b) = S · ln((K − q + b) / (K − q))

These three formulas clarify the operational logic of Sato's curve: the first defines how the cumulative supply is generated, the second determines the price during minting, and the third determines how much ETH the curve should refund during a burn. In other words, Sato's issuance, pricing, and exit are not three separate logics, but three facets of the same curve.

The most critical changes also include the following:

First, Version 2.0 explicitly incorporates the existence of the secondary market as a core part of the market structure. The bonding curve is a Uniswap V4 pool with a Hook, while the Sato/USDT secondary market is another independent V4 pool. They share a PoolManager but are not the same pool.

Second, "Sell" is completely rewritten as "Burn." Although the old version mentioned that selling back to the Hook would burn tokens, Version 2.0 clarifies this separately: only when a user exchanges Sato for ETH via the Curve pool will the total supply decrease, i.e., a burn occurs. Conversely, if a user uses the secondary Sato/USDT pool, it's merely an AMM trade with LPs, which does not burn tokens or affect the Curve reserve. This is a crucial point: only selling into the Curve triggers a burn.

Third, Version 2.0 incorporates "Routing" into the whitepaper. The official site now clearly states that minting and burning via this site will directly call the SatoSwapRouter, which is configured to use the Curve pool and will not automatically switch to the secondary pool for a better price. In other words, the official front-end is not a "market best-execution router" but a "directed entry point into the Curve."

Fourth, the new front-end separates three prices: Market, Burn, and Mint. The new front-end visualizes this difference. Based on current official website data, at the time of writing, the market price is approximately $0.7241, the burn price is approximately $0.7066, and the mint price is approximately $1.2. This means that currently, minting via the official Curve entails paying about 65% more than the secondary market price, while the burn price is very close to the secondary market price. This almost openly presents the overnight controversy: the Curve mint price, the Curve burn price, and the secondary pool market price are inherently different things.

Fifth, Version 2.0 revises the description of the "Mint Stop Line." Version 1.0 described it as: 99% of K is the mint stop line, approximately 20.79 million Sato, corresponding to about 2302 ETH. Version 2.0 phrases it more as a "market-accessible boundary," stating "the practically reachable supply size stops near 20.5 million Sato," adding that this reachable supply will slightly decrease as burning occurs. In other words, Version 2.0 downplays the intuition that "users will naturally drive the supply to 20.79 million Sato," emphasizing more that it is a reachable curve influenced by market behavior, not a linear process that will inevitably complete.

What are the Similarities and Differences Between Clone Sat1 and Sato?

Meanwhile, the clone project Sat1 has also launched a similarly structured new whitepaper and front-end website.

Their core concepts are very similar:

  • Both are ERC-20 tokens on Ethereum, issued directly by on-chain contracts, without reliance on team custody, upgrades, governance, or admin keys;
  • Both bind minting, burning, and reserves within the same Curve mechanism;
  • Both employ a similar asymptotic issuance curve: as cumulative ETH grows, minting new tokens becomes increasingly difficult, with prices rising exponentially, approaching but never truly reaching the 21 million limit;
  • Both charge a 0.3% friction fee on both sides, with fees not going to the team but remaining within the Hook/Curve;
  • Both position themselves as "issuance machines without operators," unlike traditional projects with roadmaps, upgrades, and team treasuries.

The biggest difference lies in "how state variables are recorded."

The Sat1 whitepaper points out that Sato's issue stems from using two sets of states to drive the mechanism:

  • ethCum: Cumulative ETH within the Curve.
  • totalMintedFair: Minted supply within the Curve.

The buy path relies more on ethCum, while selling and self-deprecation (99% threshold) rely more on totalMintedFair. Coupled with an early-stage random multiplier, these two quantities no longer strictly maintain the same invariant, leading to "one contract, two curve positions."

This can cause ethCum to progress faster than totalMintedFair, and repeated buying and selling can exacerbate this drift.

In contrast, Sat1's design principle is to keep only one primary state.

  • The contract stores only one curve state: ethCum.
  • Fair supply = Curve.totalMinted(ethCum).
  • Price = Curve.marginalPrice(ethCum).
  • Sell quotes are also derived from this single position.
  • selfDeprecated is also judged directly from this same curve position.

Therefore, the fundamental mechanism difference is:

  • Sato: In practice, "state split" occurs between issuance, exit, and stop-minting judgments.
  • Sat1: Enforces "unified state," deriving all key logic from the same curve position.

Regarding Curve fees, although both charge 0.3%, Sato's whitepaper states that each mint and burn incurs a 0.3% fee, which remains permanently in the Hook. However, Sato also has the two critical states, ethCum and totalMintedFair, which forked after the early random multiplier. Therefore, the observed "reserve thickening" is not solely due to the 0.3% fee but also mixed with additional drift caused by the state split. In other words, the fee itself is unchanged, but it's layered on top of a state discrepancy.

In Sat1:

  • When buying 1.000 ETH, the mint quote is calculated based on 0.997 ETH, but the full 1.000 ETH enters the reserve.
  • When selling, users receive 0.3% less, and the withheld ETH remains in the Hook.

So, Sat1's 0.3% also "keeps fees in the pool," but it's designed to only thicken the reserve without interfering with the main curve state, as all core logic only recognizes the single ethCum state.

Finally, it must be reiterated that any mechanism innovation cannot replace risk management. Before participating, carefully assess your own risk tolerance and make prudent decisions.

Domande pertinenti

QWhat were the key changes introduced in Sato's whitepaper version 2.0?

AKey changes in Sato's whitepaper 2.0 include: explicitly outlining the three core bonding curve formulas (minting, pricing, burning); formally recognizing the secondary market (sato/USDT pool) as a core part of the market structure separate from the bonding curve pool; replacing the 'sell' concept entirely with 'burn' to clarify that only transactions routed through the curve pool reduce total supply; detailing the role of the official website's router, which directs transactions only to the curve pool, not for best execution; and modifying the description of the 'minting termination line' from a fixed target to a 'market-reachable boundary' influenced by burn activity.

QHow does the pricing mechanism work on Sato's updated website frontend?

ASato's updated frontend displays three distinct prices: the Market price (from the secondary sato/USDT pool), the Burn price (the rate received for burning sato back to ETH via the curve pool), and the Mint price (the cost to mint new sato from the curve pool). At the time of writing, these prices diverged significantly, with the Mint price (~$1.2) being approximately 65% higher than the Market price (~$0.7241), while the Burn price (~$0.7066) was close to the Market price. This visually highlights that the curve pool and secondary market operate independently.

QWhat is the core mechanism difference between Sato and its fork, Sat1, according to the article?

AThe core mechanism difference lies in how they manage state variables. Sato uses two key state variables (`ethCum` and `totalMintedFair`), which can diverge, especially after the early-stage random multiplier, leading to a 'state split' or drift. This affects pricing, burning, and the self-deprecation trigger. In contrast, Sat1 is designed with a 'unified state' system, using only a single primary state variable (`ethCum`) to derive all critical logic like fair supply, price, burn quotes, and the self-deprecation check, aiming to prevent such drift.

QWhat potential issue does the article identify with the 0.3% fee in Sato's design?

AThe article identifies that while the 0.3% fee on mints and burns remains in the hook, its effect in Sato is compounded by the state drift between `ethCum` and `totalMintedFair`. This means the observed 'thickening of reserves' is not solely due to the fee accumulation but is also mixed with the additional offset caused by the split between the two state variables. In Sat1, the fee is designed to only thicken reserves without interfering with the core curve state, as all logic references the single `ethCum` variable.

QWhat major market events are described surrounding Sato on the night of May 7, 2026?

AOn the night of May 7, 2026, amid market质疑 over pricing drift between Sato's bonding curve and secondary market prices, the project updated its website with 'Whitepaper 2.0' and changed its frontend trading panel from 'Buy/Sell' to 'Mint/Burn.' Simultaneously, Sato's market capitalization fell sharply from a high near $40 million to about $14.4 million. Furthermore, a fork project named Sat1 launched its own whitepaper and frontend, reaching a market cap of around $10 million at one point before falling to approximately $5.2 million.

Letture associate

Agent Race Ends, Super Workbench Takes Over

The era of fragmented AI agents is ending. Over the past month, China's tech giants—Tencent, Alibaba, and ByteDance—have simultaneously shifted strategy: instead of launching new, standalone AI agents, they are consolidating their various agent projects into unified "super workbenches." Tencent integrated its QClaw teams into WorkBuddy, a strategic product hailed as a potential third flagship after QQ and WeChat. Alibaba is merging its QoderWork, Wukong, and MuleRun agents into a new "Qianwen Office" platform under DingTalk's leadership. ByteDance rebranded its TRAE SOLO coding agent to TRAE Work, signaling a broader focus on workflow collaboration. This convergence marks a pivotal industry consensus. The initial exploration phase, where companies rapidly built numerous overlapping agents for different scenarios, proved costly and inefficient. With open-source tools eroding technical barriers, competition has shifted from agent creation to resource consolidation and cost control. Historically, platform wars are won not by creating more products, but by simplifying them—as seen with browsers unifying web access and super-apps consolidating services. Now, the "super workbench" aims to become the unified AI entry point for work. This reflects a deeper market realization: the primary audience for AI is no longer just programmers (a market in the tens of millions) but all knowledge workers (a market of billions). The real opportunity lies in augmenting everyday tasks—managing emails, documents, data, and meetings—across the entire workday. The core battleground is becoming control over the primary AI entry point that employees use daily. Tencent's WorkBuddy leverages WeChat and Tencent Docs; Alibaba's Qianwen Office taps into DingTalk's organizational data; ByteDance's TRAE Work integrates with Feishu's workflows. Whoever owns this "super workbench" gains strategic control over orchestrating enterprise data and APIs. This shift is redefining enterprise software. Traditional SaaS applications, valued for their user interfaces, will recede into the background. Their core functionalities will be exposed as standardized "Skills" or APIs for the super workbench's agents to invoke. Software value will shift from selling user seats to charging based on API calls and outcomes delivered. The evolution of agents is moving through clear stages: first as novel standalone products, then as consolidated primary work entry points, and finally as pervasive, invisible capabilities embedded into the digital fabric. The recent moves by major tech firms signal the transition from the first stage into the second, accelerating toward the third. In the end, the most successful agent technology may become invisible—like electricity or the HTTP protocol—a fundamental, unnamed infrastructure powering work itself.

marsbit8 min fa

Agent Race Ends, Super Workbench Takes Over

marsbit8 min fa

Michael Saylor: 110 Reasons to Oppose BIP-110

Michael Saylor presents 110 arguments against Bitcoin Improvement Proposal (BIP) 110, a soft fork aimed at restricting certain non-monetary data storage uses (like inscriptions) on the Bitcoin blockchain. He acknowledges the proponents' valid concerns—such as node costs, fee pressure, and preserving Bitcoin's monetary focus—but fundamentally disagrees with the proposed solution. Saylor argues that BIP 110 represents a dangerous precedent of using consensus rules to enforce value judgments on transaction validity, moving away from Bitcoin's core principles of neutrality and permissionless innovation. His key objections are organized into eleven categories: 1) It violates neutrality and hard consensus by banning currently valid transactions. 2) It fails to meet the high burden of proof required for a consensus change, lacking concrete data on the alleged crisis. 3) Its seven bundled technical restrictions are overly broad, targeting generic script functionalities and blocking future upgrade paths. 4) It sacrifices compatibility and future optionality by closing off designed upgrade hooks. 5) Its temporary rules add significant complexity (grandfathering, expiry states) without sufficient justification. 6) The economic and security impacts, particularly on miner revenue and fee markets, are uncertain and unmodeled. 7) Superior, market-based tools (fee markets, relay/mining policies) already exist to manage blockchain load. 8) It stifles innovation by creating a chilling effect for developers. 9) Its modified activation mechanism (55% threshold, forced signaling) is aggressive and risks network splits. 10) The precedent it sets—using consensus to suppress disliked but legal uses—is more dangerous than the problem it aims to solve. 11) A better path exists: improving measurements, refining resource-based policies, and allowing market forces to work. Saylor concludes that Bitcoin's strength lies in its neutral rules, open markets, and hard consensus. Changing these foundational elements to target specific use cases is an unnecessary and risky "iatrogenic" intervention. He advocates for guarding Bitcoin's neutrality rather than acting as its redeemer.

marsbit24 min fa

Michael Saylor: 110 Reasons to Oppose BIP-110

marsbit24 min fa

Trading

Spot
活动图片