Skip to documentation
Resources/Docs
Start hereSinjoh v2

The Sinjoh docs

Understand the markets. Follow the money. Build on the protocol.

3 min read·
On this page
BUILD WITH SINJOHDeveloper quickstart

From a contract address to your first quote.

UNDERSTAND THE PROTOCOLExplore the architecture

Markets, reserves, revenue and services.

A market system, from launch onward

Sinjoh combines token creation, managed liquidity, optional funded floors, creator revenue routes and holder rewards on Robinhood Chain. A new launch opens directly into its canonical Uniswap v4 market. It does not begin on a separate bonding curve and wait to graduate.

Each market has one token, one backing asset, its own vault and its own accounting. Shared contracts route revenue, convert assets and administer rewards without pooling one market’s obligations with another’s.

  1. 01Create or migrate
  2. 02Trade against backing
  3. 03Build market reserves
  4. 04Route creator revenue
  5. 05Distribute holder rewards

Find your starting point

You want to…Start with
Use an account or understand your balanceAccounts & profiles and Portfolio
Create a token or manage a marketLaunch a token and Creator controls
Understand prices, fills and chargesTrading, Fees & taxes and Backing & pricing
Bring an existing token to SinjohMigration and Allocation stage
Integrate a wallet, bot or applicationDeveloper quickstart, SDK, API and Contracts

Three distinctions that matter

  • A Portfolio holding is an asset with a readable balance, USD valuation and usable price history. Showing it in Portfolio does not make it a Sinjoh market.
  • A backing asset denominates a specific market’s trades, fees and reserves. Eligibility depends on the configured pricing rules.
  • An automated conversion needs an enabled path that can execute for the actual amount. An asset listing, an initialized pool or a nonzero quote alone does not prove sufficient liquidity.

A complete view of the stack

The guides cover market construction, the four trade types, all tax models, floor funding, treasury and yield, creator controls, revenue routing, sweeps, airdrops, raffles, migration, accounts, public reads and the services that operate them. Developer references provide the active application manifest, downloadable ABIs and worked read/quote/transaction examples.

Start with Architecture for contract boundaries, or use search to jump directly to a mechanic, function name or error. The Glossary keeps terms such as backing, floor cash, treasury and pending credits distinct.