Peg

Peg is an onchain application built around tokenized stocks and the liquidity surrounding them. It brings market access, liquidity management, community-created pools, PEG principal staking and token launches into one connected workspace.

The idea is practical: a tokenized asset becomes more useful when people can trade it, supply liquidity around it and build new projects connected to its market. Peg provides those entry points through a wallet interface, with the underlying assets and transaction results kept visible.

For liquidity providers, Peg offers market and position controls. For communities, it offers a way to create a token / USDG pool. For creators, PegPad connects a new token to an approved stock-token pair and routes creator-fee proceeds into payouts, Peg liquidity and PEG buybacks.

Network: Robinhood Chain · Chain ID: 4663 · Application: usepeg.trade

Contract address · Robinhood Chain

0x7f362d5ef8b02cedf2b5c5f76b9d7aaa667085c8

View PEG on the explorer ↗

PegAsset is a fixed-unit custody wrapper. It receives an underlying stock token and issues wrapped units against that asset. New v8 market plans configure zero wrap and unwrap fees; the underlying constructor supports bounded immutable fee settings for other versions.

Unwrapping burns wrapped units and returns the underlying token according to the configured contract. The backing is denominated in token units. It does not depend on the interface inventing a price, and it does not turn the wrapper into a cash-redemption service or direct legal equity ownership.

A Peg stock market pairs its wrapped stock token with USDG. Liquidity providers supply the pool assets and receive LP shares. Those shares represent a proportional claim on the pool's reserves. When liquidity is removed, the position returns its share of both assets under the pool's rules.

The constant-product pool family retains a 0.30% swap fee in its reserves. Liquidity providers participate through their LP share of those reserves. Fees, the changing mix of assets and market prices all affect a position's value; a fee rate alone is not an APR or a profit forecast.

Peg's native-entry routing can combine supported ETH or USDG entry steps into one planned operation. Its contract binds the supported markets and venues, spends the current call's balance deltas and returns applicable leftovers. Availability depends on the registered route and current liquidity.

Trading starts with a specific asset, amount and route. The wallet flow separates required token approvals from the actual swap, simulates the planned operation and checks its receipt before treating it as complete. Minimum output and deadline constraints are part of the transaction, so a displayed quote is not an unlimited authorization to trade.

Bring a token address. Create a market around it.

Community Pools extends pool creation beyond Peg's curated stock markets. A creator supplies an ERC-20 contract address on Robinhood Chain. Peg reads the token identity, prepares its direct pairing with USDG and requests the necessary wallet confirmation.

1. Identify the asset. Read the token contract, metadata and decimals from the selected chain.
2. Create the pool. Review and confirm the deployment transaction from the connected wallet.
3. Establish liquidity. Supply both assets; the first two-sided deposit sets the pool's initial ratio.
4. Manage the position. Use the Community view in Pools to access deposit and withdrawal controls.

A confirmed deployment establishes that the pool contract exists. Liquidity is a separate step: an empty contract is not yet a funded market. Likewise, a token name, avatar or RWA category is descriptive metadata, not an endorsement of the issuer.

Community assets do not automatically join the curated stock catalog, native-entry allowlist or operator execution routes. Each part of the system has its own registration and asset requirements.

The staking interface supports depositing PEG into PegStakingVault and withdrawing the balance recorded for the caller. The vault permanently binds its token and expected chain at construction.

Its responsibility is deliberately narrow: hold principal, account for each depositor and return that principal when a valid withdrawal is requested. It has no owner withdrawal, upgrade switch, lock period, deposit fee, principal investment or donation sweep. Reward processing does not receive authority over the vault.

The withdrawal entry point below is taken directly from the published contract:

function withdraw(uint256 amount) external nonReentrant {
    _checkChain();
    if (amount == 0) revert InvalidAmount();
    if (amount > stakedBalance[msg.sender]) revert InsufficientStake();
    _requireBacking();
    stakedBalance[msg.sender] -= amount;
    totalStaked -= amount;
    _sendExact(msg.sender, amount);
    emit Withdrawn(msg.sender, amount, stakedBalance[msg.sender]);
}

OpenZeppelin reentrancy protection and exact sender/recipient balance checks protect the accounting assumptions. Unsupported transfers revert instead of silently crediting a different amount. Underlying-token freezes or changed transfer rules can still prevent a transfer.

The interface's configured 12% external-reward rate belongs to a separate reward module. It is not yield generated or guaranteed by the principal vault. Staked and Withdrawn events provide position changes that an external indexer can consume.

Read PegStakingVault.sol ↗

PegPad is the launchpad inside Peg. It connects to Pons so a creator can launch a token paired with an approved tokenized stock on Robinhood Chain.

The creation flow starts with a token name, symbol, avatar and stock selection. Uploaded avatars become validated public images so token metadata can resolve beyond the creator's browser. Wallet-confirmed creation is followed by a Your launches card containing the confirmed token identity and a copyable contract address.

PegPad's V2 fee router connects available creator-fee proceeds to three destinations:

The allocation applies to the available net creator proceeds after Pons' protocol share, rather than total trading volume. PegPad adds no additional creator tax; Pons' trading fees and opening protections still apply.

Fee processing is an explicit Creator fees transaction. The router binds its creator, executor, market and runtime commitments; price-sensitive steps use protected outputs and deadlines. Accumulated fees are not automatically distributed after every trade. Post-graduation conversion can depend on Pons operator execution.

The PegPad Test / PPTEST / NVDA lifecycle produced real transaction receipts:

These receipts document completed historical operations. They do not predict future trading volume, fee income or execution conditions.

Build with public state, exact amounts and explicit contract versions.

peg-sdk ↗ provides a read-only TypeScript client for PEG and funded staking v2 on Robinhood Chain. Read wallet balances, legacy positions, current stake, earned rewards and the reward reserve in one typed snapshot. The client checks network identity, block freshness, canonical state and the expected staking and reserve runtimes.

The source package includes installation instructions and runnable examples. It uses no signer and submits no transactions. Reward projections remain estimates; a reserve snapshot does not guarantee future funding. Runtime attestation is provided by the TypeScript client, not the Python example.

The public peg-contracts repository contains five selected source contracts, a pinned build and the staking custody test suite.

Source snapshots and deployed versions are distinct. The published PegPool.sol is the foundational pool source; current app registries use separately frozen pool artifacts, including the PegRevenuePool variant exposed as PegPool. Integrations must match the actual market's artifact and constructor bindings.

The configured staking deployment is 0x431d61b1a57F8d4fd1C0406dc424d5beEEc07A8F. The repository includes its frozen staking artifact and independent reproduction script.

git clone https://github.com/use-peg/peg-contracts.git
cd peg-contracts
npm ci
npm run build
npm test

The package uses Node.js 22+, Solidity 0.8.36, OpenZeppelin 5.6.1, optimizer 200 runs and Shanghai EVM. The aggregate build uses IR; the staking reproduction script preserves its separate artifact settings. Local tests require no funded wallet or external RPC.

The 30-test staking suite covers constructor validation, artifact reproduction, multiple depositors, partial and immediate withdrawals, transfer taxes, rebasing, issuer restrictions, donations, deficit repair, reentrancy and conservation of principal. It is a staking suite, not a complete test suite for every published component.

Peg's frontend uses Next.js, React and TypeScript, with Three.js and spring-based motion for its monitor-led studio. Chain interactions use ethers; same-origin server APIs validate inputs with Zod.

The transaction lifecycle connects those layers:

Saved display data keeps the interface responsive while background reads refresh it. Transaction-critical checks still need current chain state. Recorded fees, external volume, pool liquidity and position value are separate measurements; missing observations should remain explicit.

• Liquidity providers: explore a supported market, inspect its assets and manage your LP position.
• Communities: bring an ERC-20 address and create a USDG pool, then establish liquidity.
• Token creators: open PegPad, choose a stock pair and inspect the creator-fee route.
• Developers: read the Solidity, reproduce the staking artifact and follow the contract boundaries.

Source publication, successful compilation and historical transaction proofs are not an independent security audit. Market conditions, underlying-token restrictions and external venue dependencies remain relevant. Peg is built on Robinhood Chain and is independent of Robinhood.