Skip to content

Start Here

Upside is a principal-protected token fundraising protocol. Projects sell a portion of their token supply at a defined valuation, with built-in principal protection for every investor.

A project says: “We are selling 30% of our token supply at a $50M valuation.” Investors deposit capital. That capital goes into yield-generating reserves that back a perpetual PUT right on each position. Investors can always get their money back by exercising their PUT, no expiry, no extra approval.

The platform also supports token generation events (TGEs), where a project launches and distributes tokens for the first time.

There is no platform token and no staking requirement.

Crypto fundraising has a trust problem. Projects raise capital and investors hope the token holds value. When it doesn’t, investors lose everything.

Upside is designed so principal protection is structural, not social. Deposited capital is held in reserve, routed into yield strategies, and remains redeemable on-chain.

For projects, this is a credibility signal: “We are confident enough to offer structural downside protection.” For investors, it removes most project-token downside while preserving upside exposure.

  • Institutions requiring downside controls
  • Funds and VCs preferring transparent on-chain raise structures
  • Retail users seeking raise participation with principal-protection behavior
  • DeFi users who value secondary market liquidity for position tokens
  1. Guarantees — what is and isn’t protected
  2. Investing and Positions — how deposits and positions work
  3. Hold, Redeem, and Withdraw — your three actions
  4. Risk Model — what can go wrong
  1. Raise Setup and Configuration — how to configure a raise
  2. Capital Lifecycle — where capital goes and how buyback/burn works
  3. Yield Strategy — how yield is generated and routed
  4. Fees and Economicsplatform fee model
  1. Contract Map — architecture and contract responsibilities
  2. Formula Reference — on-chain math
  3. Roles and Permissions — access control model
  4. State, Events, and Interfaces — key state variables and terminology