On August 29, 2020, SushiSwap was operating its new liquidity-mining program on Ethereum, allowing holders of Uniswap V2 liquidity-provider tokens to deposit those receipts into SushiSwap’s MasterChef contract and earn newly issued SUSHI. The code and chain record make the core event verifiable: reward accounting began at Ethereum block 10,750,000, mined at 15:31:15 UTC on August 28, making August 29 the program’s first full UTC day.

That design mattered because SushiSwap was not merely asking traders to try another automated market maker. It was targeting the liquidity already assembled inside Uniswap. A Uniswap LP token represented a depositor’s proportional claim on assets in a Uniswap V2 pool. By rewarding deposits of those LP tokens, SushiSwap could organize liquidity providers around a planned later migration without first operating equivalent pools of its own.

Incentives aimed at the liquidity layer

The verified MasterChef code set a base issuance rate of 100 SUSHI per Ethereum block and a 10-times bonus multiplier for the early reward period. In aggregate, that meant reward accounting at 1,000 SUSHI per block before allocation among eligible pools; it did not mean every pool or depositor received that amount. Each pool’s share depended on allocation points, while each user’s claim depended on the LP tokens deposited relative to the pool total. The contract also directed an additional developer allocation when pool rewards were minted.

The project’s stated economic plan paired those incentives with a future exchange fee split. Active liquidity providers were to receive 0.25% of a trade, while 0.05% was to be converted into SUSHI and distributed to token holders. On August 29, that fee-sharing description was a project plan, not proof that the planned migration had occurred or that future fees would materialize.

The distinction is important. Uniswap’s contracts and pooled assets continued to provide the underlying trading venue during this opening phase. SushiSwap’s immediate product was the reward contract layered over selected Uniswap LP positions. The competitive wager was that temporary token issuance could coordinate enough providers to move when a migrator was later activated.

A governance experiment with concentrated controls

SushiSwap presented the system as community-oriented, but the event-day code exposed substantial administrative power. The MasterChef source described the contract as ownable, permitted the owner to add pools, change allocation points and set a migrator, and explicitly warned that the migrator would have extensive access to LP tokens. Those were not hypothetical details imported from later controversy; they were visible in the verified contract design available on August 29.

This produced the central institutional tension of the launch. The protocol used open-source code and on-chain deposits, giving participants more inspectable rules than a conventional private rewards program. Yet pseudonymous stewardship, mutable pool settings and a not-yet-executed migration meant transparency did not eliminate governance, smart-contract or incentive risk. High nominal reward rates also depended on a newly issued token whose durable value and liquidity were uncertain.

What August 29 established

The consequential development was the proof of a new competitive tactic: an open protocol could fork an automated-market-maker design, attach a token to another protocol’s LP receipts and recruit liquidity before launching the destination pools. The method made liquidity itself contestable and showed how quickly incentives could challenge an incumbent without negotiating for access.

Later context

Later records show that SushiSwap migrated more than $800 million of liquidity from Uniswap on September 9, 2020; the accelerated SUSHI reward period ended on September 12; and Uniswap began its own liquidity-mining program on September 18. Those outcomes clarify why the August 29 experiment became significant, but none was knowable as a completed fact on August 29.

Primary sourceEthereum block 10,750,000

The complete source packet and revision history are retained with the newsroom record.

Automated desk disclosure

Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.

Financial-risk note

This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.