pairhouse
[ PAIRHOUSE · DEVELOPMENT BUILD ]

Make a pair.
Know the risks.

Pairhouse now has a working local smart-contract application. Public mainnet and testnet deployment are not configured in this package.

Start locally

Start the development launcher supplied with the source package, open the local website, and choose Connect wallet → Local test wallet. That wallet controls disposable local ETH and demo assets only. Restarting the devnet creates a fresh chain; old local balances and addresses will no longer apply.

Create an asset

Choose Launch an asset. Set its name, ticker, fixed supply, pool allocation and ETH seed. Review the opening price, any optional ETH backing, liquidity lock and the fee actually returned by the selected launchpad. The token supply is minted once. Backing and pool liquidity are separate balances.

Trade and provide liquidity

Open a market to preview a swap, add both assets in the pool ratio, or remove your LP position. Amounts use integer base units. The router enforces the minimum output and deadline you approve. Prices can move, transactions can fail, and gas is still charged on a public chain. Never approve unfamiliar spending requests.

Existing tokens and shared routes

The new-pool flow accepts existing standard ERC-20 contract addresses. Already existing pools must use the regular deposit flow. Routes use at most three distinct pool hops. Fee-on-transfer, rebasing, callback-heavy and otherwise nonstandard tokens are not supported; a successful metadata lookup does not establish a token's safety.

Backing and liquidity locks

Optional ETH backing can be redeemed by burning a holder's tokens for a proportional share of vault collateral. A pool position does not itself guarantee backing. Locked LP tokens can be claimed only by their creator after the configured unlock time. Extra backing deposits are not personal savings accounts and cannot be withdrawn independently.

Synthetic assets: local research only

The local synthetic engine supports collateral deposits, minting, repayment, withdrawal and liquidations using explicitly labelled mock prices. These are not shares, real oracle prices or live investments. Public synthetic markets are disabled pending chain-specific oracle/sequencer-outage design, risk parameters, independent security review and applicable legal review.

Public deployment is a separate step

Choose the intended network and owner, review source and dependencies, conduct an independent audit, deploy through an approved signer, verify source on the explorer and publish a matching deployment manifest. No addresses from the reference project are usable as Pairhouse deployments. The app compares chain IDs, contract code hashes and contract wiring; those checks do not constitute an audit.

Updates

This is an unaudited development build with no promised launch date. Consult the included START-HERE and test report for what was actually verified and what remains pending.