FRENT (beta) Building onchain tools

FAQ

Useful answers

Understand what FRENT puts onchain.

Commerce infrastructure, pixel collections, contracts and ownership—without knowledge base maze.

01 Who or what is FRENT?

FRENT builds practical onchain infrastructure for merchants, creators, and developers. Commerce focuses on merchant-owned payment deployments. Builder currently focuses on fully onchain pixel art collections.

02 What can a merchant deploy with FRENT Commerce?

The planned deployment combines a configurable POS, QR generator, wallet-connected payment screen, IPFS-hosted frontend, and a payment smart contract on a chosen EVM chain.

03 What lives on IPFS and what lives onchain?

Merchant interfaces such as POS, QR generator, and payment screen are published to IPFS. Payment rules, routing, split settlement, receipts, and protocol fee execution belong in the smart contract on the selected chain.

04 Does FRENT custody merchant or customer funds?

No. Customers approve payments from their own wallets. The deployed contract routes funds directly to configured receiving wallets. FRENT does not need to hold the payment balance.

05 How do split payments work?

A merchant configures multiple receiving wallets and their percentages. The payment contract applies that split when a payment settles, making distribution rules visible and verifiable onchain.

06 What does FRENT charge for Commerce payments?

Each completed payment includes a transparent 0.1% protocol fee enforced by the payment smart contract.

07 Which chains does FRENT support?

FRENT targets EVM-compatible networks. Each supported network has its own protocol deployment, chain ID, RPC, explorer, and contract addresses. Availability is listed in the protocol chain directory.

08 What makes a FRENT pixel collection fully onchain?

Palettes, pixel data, traits, layer order, collection rules, token seeds, metadata, and SVG rendering are stored or generated through contracts. A minted token does not depend on a hosted PNG folder.

09 Can collection art or mint rules change after launch?

Creators can edit while building. Artwork is locked when its onchain art store is finalized. Published mint phases, supply, wallet limits, allowlists, pricing, and royalties cannot be quietly replaced through the FRENT launch flow.

10 Which mint phases can a pixel collection use?

Collections can configure Allowlist Mint, Early Mint, and Public Mint. Optional phases can use wallet allowances backed by onchain Merkle roots. Public Mint remains open and does not require an allowlist.

11 Why are testnet drops missing from the launchpad?

Testnet drops are hidden from the public overview to avoid confusion with live collections. Their direct pages remain accessible for testing. Admin wallets can also see them in the overview.

12 Can developers read collection and token data without the FRENT website?

Yes. Contracts can be read directly through an EVM RPC. FRENT also provides an API for indexed collection data, decoded token metadata, and SVG delivery when an application prefers a simpler integration.