Know what you’re using.
The mechanics, the limits, and the things we will not hand-wave.
A coin can have someone’s name on it.
BYLINE is a permissionless token launcher on Arc. A launch creates 1 billion tokens, starts a USDC bonding curve and names one X account or one wallet as its fee beneficiary. Naming someone does not imply endorsement or affiliation.
Simple fees. Explicit destinations.
Each curve buy and sell has a 1% fee. Of that fee, 50% accrues to the beneficiary, 30% to the protocol and 20% to a buyback reserve. Small integer-rounding remainders go to the protocol. Curve referral rewards are funded from 10% of the protocol share, not from the beneficiary. There is no creator token gift, separate launch charge or interest-rate mechanism.
~45K FDV is a milestone, not a promise.
The curve sells up to 800 million tokens. Its potential-based reserve reaches about 9,000 USDC at the cap. The other 200 million tokens and that USDC seed a full-range, 1%-fee Uniswap v4 pool. Remaining LP principal is locked irreversibly; it is not a withdrawable NFT. The locker can collect fees, but has no negative-liquidity operation. If migration fails, it can be retried and the curve remains sellable. A price jump, spread or slippage can still occur through rounding and trading.
Post-graduation royalties are LP fees.
Royalties after graduation come only from BYLINE’s locked liquidity position. Other people may supply additional liquidity, create other pools or route elsewhere. There is no transfer tax forcing every trade in the token to pay BYLINE. USDC-side fees are collectible permissionlessly. Token-side fees require a keeper to convert them before the same 50/30/20 distribution. “50% of fees” means 50% of distributable fees collected by this system, not half of every fee everywhere.
X proves the account. An attester proves it to Arc.
Sign in through X OAuth, connect your receiving Arc wallet and sign a one-time wallet challenge. The backend signs a five-minute, nonce-protected claim attestation bound to your immutable X ID, wallet, chain and fee vault. Arc verifies that attester signature; it cannot directly verify an X login. A compromised attester can authorize fraudulent X claims. A lost attester or inaccessible X account can prevent claims. This is a central trust dependency. Account ownership follows current X authentication, with an outstanding proof window of up to five minutes.
USDC, without confusing two interfaces.
Arc uses USDC for gas with 18 native decimals. The USDC ERC-20 interface uses 6 decimals. They represent the same balance, not two separate assets. BYLINE’s contracts use the 6-decimal ERC-20 interface consistently. Keep additional USDC for gas; a displayed wallet balance cannot safely all be spent if it also funds transaction fees.
A reserve before a token.
The protocol token does not exist merely because a buyback page exists. Until a real BYLINE-launched token graduates and an executor is configured, the 20% buyback allocation stays in a separate reserve. Activation is a privileged, one-time configuration. The keeper has limits and minimum outputs, but no independent manipulation-proof price oracle. Buybacks are discretionary execution of an allocation, not guaranteed returns.
Immutable core. Limited admin. Real trust assumptions.
The core contracts have no proxy upgrades, token mint privilege, arbitrary fee-vault sweep or liquidity-withdrawal path. New versions use new factories. One admin can pause new launches and bonding-curve trades, but not fee withdrawals or external AMM trades. The offchain X signer, initial deployments, one-time buyback configuration, RPC services and content/indexing backend remain trusted in the ways disclosed here. Immutability also prevents emergency patching of a bad deployment.
Read this before real funds.
This release is source code, not an audited production deployment. Build and Solidity execution were not available in the authoring environment. Independent contract review, full dependency builds, adversarial testing, local v4 lifecycle tests, Arc testnet validation and live deployment verification are release gates. Tokens can lose all value. Thin liquidity, MEV, oracle errors, exploits, account compromise, network outages and USDC issuer restrictions can affect funds. No guaranteed profit, redemption price, interest, or legal/Sharia certification is implied.
Open contracts. A moderated website.
The frontend can hide illegal, impersonating or malicious listings and comments. Hiding content does not undo a deployment or confiscate its balances. Uploaded metadata is pinned to IPFS; availability still depends on maintained pins and gateways. Comments, reports and discovery rankings are offchain. Wallet-based usage does not by itself remove the operator’s applicable legal or regulatory obligations.
Launch from another app.
The SDK exports chain definitions, contract ABIs, bigint curve mathematics, transaction helpers and typed API access. The HTTP API provides discovery, token data, charts, public earnings, profiles and creator resolution. Wallet-signed authentication protects comments and uploads. X claims require OAuth and a wallet-bound challenge. Contract calls themselves are permissionless. See the included API and deployment documents for exact schemas and rate limits.