MagicWebb
A Non-Custodial NFT Marketplace for the Flare Network
Version 1.0 — May 2026
Executive summary
MagicWebb is a non-custodial NFT marketplace built natively for the Flare Network. It supports the two dominant token standards — ERC-721 and ERC-1155 — across three trade primitives: instant fixed-price purchase, English auction, and on-chain payable offers with escrowed principal. The platform is engineered for the reality of a sovereign-data network: low fees, transparent settlement, and zero custodial risk. MagicWebb charges a single hardcoded 2% platform fee (1.5% to the platform wallet, 0.5% to the network keeper bot that funds instant settlement), charged only on settlement (a fixed-price buy, auction settlement, or offer acceptance) and deducted from the seller’s proceeds. Listing, auction creation, bidding, and making offers are all free — the fee is never charged on operations that do not result in a sale. The fee rate is a Solidity constant — no admin key, environment variable, or upgrade path can change it.
This document explains what MagicWebb is, who it serves, why it exists, and where it is going. A separate technical whitepaper (WHITEPAPER_TECHNICAL.md) covers the smart-contract design and threat model in depth.
1. The problem
NFT marketplaces today suffer from three structural failures:
- Custodial risk. Many incumbents take custody of NFTs to support delayed-settlement features. When the marketplace fails (insolvency, hack, regulatory seizure), users lose both the asset and any unsettled proceeds.
- Hidden fees. “2.5% platform fee” headlines often hide a 5–10% effective take-rate after sequencer fees, MEV extraction, and floor-price spread games.
- Single-standard assumptions. Most user interfaces are designed around either ERC-721 (one-of-one art) or ERC-1155 (semi-fungible items). Switching standards forks the entire product surface.
MagicWebb addresses all three:
- No custody. Sellers retain the NFT in their wallet until the moment a buyer settles. The contract holds zero NFT inventory at rest.
- Fixed fee. The on-chain
PLATFORM_FEE_BPSconstant is 200 basis points (2%), split 150 bps tofeeRecipientand 50 bps to the keeper. It is aconstant— not a variable, not a mutable slot. No admin can change it post-deploy. - One product, two standards. A single contract surface handles both ERC-721 and ERC-1155 via a one-byte discriminator. Frontends treat them uniformly.
2. The opportunity
The Flare Network is a layer-1 blockchain purpose-built to bring high-integrity data on-chain — price feeds via FTSO, programmatic state attestations, and cross-chain proofs. As Flare’s native asset (FLR) ecosystem matures, demand for an NFT venue that respects Flare’s design principles — open data, decentralised oracles, low cost — has outpaced the available supply.
MagicWebb is positioned as the canonical NFT trade venue on Flare:
- Native FLR settlement. No wrapped-token detour. Buy, sell, and bid in the network’s native unit.
- FTSO-backed pricing (optional). USD-equivalent display can use Flare Time-Series Oracle feeds when the UI wires them in; the marketplace contracts settle in native token only.
- Coston2-first. Full feature parity on Coston2 testnet from day one.
3. How it works (in plain English)
Buying
- Browse listings on the MagicWebb web app.
- Click Buy. Your wallet pops up; confirm the transaction.
- The NFT lands in your wallet. The seller is paid. The platform fee goes to the fee wallet. All in one atomic transaction — either every part succeeds or nothing happens.
Selling
- Connect your wallet. Approve the marketplace once per collection.
- Choose List (fixed price), Auction (English with reserve), or wait for Offers (someone else proposes a price).
- The NFT stays in your wallet until a buyer claims it. Cancel any time.
Offers (the bidder side)
- Make an offer on any NFT — the contract escrows your FLR on-chain. Offering is free.
- You hold one offer per NFT. Offering again on the same NFT replaces it: the new amount becomes your whole offer and the old amount is refunded in the same transaction, so send the full amount you want to offer, not a top-up. An edit does NOT refresh the expiry timer — it continues counting down from the original expiry — and cannot change the number of ERC-1155 units. Bidders can cancel their offer before expiry via
cancelOffer(). - If the owner accepts, the NFT transfers to you and your escrow pays the seller (minus the 2% fee).
- If the offer is rejected, cancelled, or expires, your full principal is refunded. Bidders can cancel their own offer before expiry; the keeper auto-refunds expired offers instantly.
Auctions (the bidder side)
- Place a bid. Your FLR is locked in the auction contract. Bids are cumulative: each bid adds to your running total on that auction, so to retake the lead you send only the top-up that brings your total to the leader’s total + 1 FLR — never the full new amount again.
- If you are outbid, your bid stays escrowed in the auction so you can top up and retake the lead. While you are not leading you can pull all of it back any time with Withdraw my bid; after the auction settles, the keeper refunds every losing bidder in full.
- If you win, the keeper bot settles the auction the moment it ends; you or the seller can also call settle yourselves after the end time (nobody else can). The NFT comes to you; the seller is paid.
4. What makes MagicWebb different
4.1 Single hardcoded fee
The PLATFORM_FEE_BPS constant in MarketplaceCore.sol is 200 (2%: PLATFORM_SHARE_BPS 150 to feeRecipient, KEEPER_SHARE_BPS 50 to the keeper). It is a constant — not a variable, not a mutable storage slot. It is charged only on a successful sale (a fixed-price buy, auction settlement, or offer acceptance) and deducted from the seller’s proceeds; listing, auction creation, bidding, and making offers are free. Changing the rate requires deploying a new contract with a different address, so users can verify it themselves.
Fees are sent directly to the feeRecipient wallet via .call{value: fee}("") — no intermediary contract, no vault, no accumulator step.
This is a structural commitment, not a marketing line.
4.2 No custody
NFTs are never escrowed. The marketplace contract holds an ERC1155Holder interface only so that future workflows can route 1155s through the contract if needed; in normal operation, every transfer goes seller → buyer in a single call inside the same buy/settle/accept transaction.
If MagicWebb’s frontend disappears tomorrow, your NFT stays in your wallet. You can interact with the contracts directly via Etherscan/Flarescan or any ABI-compatible tool.
4.3 Pull-pattern refunds
In a naive auction contract, an outbid bidder is paid back inside the new bidder’s transaction. A malicious contract bidder can refuse the refund — DOS-ing every outbid attempt — and lock the auction at their bid price.
MagicWebb never pays an outbid bidder inside someone else’s bid. Each bidder’s escrow stays in the auction under their own cumulative total: a non-leading bidder pulls it with withdrawLoserFunds() at any time, and after settlement refundLosers() returns every loser’s escrow in batches. Every payment push is gas-capped and copies no return data, and a push the recipient refuses is credited to a per-address balance (pendingReturns) that its owner claims with withdrawRefund(). No one can block anyone else.
4.4 Anti-snipe
Last-second bids would be disheartening for both bidders and sellers. MagicWebb extends the auction by 3 minutes if a winning bid arrives in the last 3 minutes. Each subsequent qualifying bid extends again. The auction ends when bids stop arriving in the window — a fair market clearing rather than a contest of latency.
4.5 Hybrid standards
Whether you are trading a 1-of-1 generative art piece (ERC-721) or 1,000 collectible cards (ERC-1155), the same UI and the same contracts apply. We avoid the common trap of building a “PFP marketplace” and bolting a “gaming items” tab on later.
4.6 Creator royalties (EIP-2981)
At sale time (buy, auction settlement, offer acceptance) the core asks the collection for its EIP-2981 royaltyInfo(tokenId, salePrice) at the real sale price — for ERC-1155, the total price of the sale — and pays the answer to the named receiver. The model is seller-pays: the buyer pays exactly the listed price, winning bid, or offer principal; the 2% platform fee is computed on the full price first, and the seller receives price − fee − royalty. The royalty is capped by the constant MAX_ROYALTY_BPS = 1000 (10%): a larger answer is clamped, never refused. The query is a gas-capped staticcall that reads exactly 64 bytes of return data, so a collection without EIP-2981, a reverting one, or a hostile one simply pays no royalty and cannot block the sale. The payout uses the same capped push as every other payment; a receiver that refuses it is credited in pendingReturns and claims with withdrawRefund(). Each non-zero payment emits RoyaltyPaid(collection, tokenId, receiver, amount) just before the sale event, and previewRoyalty(coll, tokenId, salePrice) lets any client show the figure before signing.
5. Architecture (high-level)
On-chain (Flare Coston2)
├── Marketplace — fixed-price listings
├── AuctionHouse — English auctions
├── OfferBook — on-chain payable offers (escrowed, one per bidder per NFT)
└── MarketplaceCore — shared fee + transfer logic (no admin override on trades, no pause)
Off-chain (single Go binary)
├── Indexer (Go) — listens to events, populates Postgres
├── Server (Go Fiber) — REST API and WebSocket live updates for the site's own pages, SIWE auth
└── UI (Astro + Svelte islands + wagmi/viem) — static build served by the binary; wallet writes go direct to chain
The off-chain layer is a convenience layer for fast browsing. Trading is on-chain; the off-chain layer cannot censor, freeze, or front-run a trade.
6. Security posture
MagicWebb has been:
- Statically analysed with Slither (latest stable). All real findings patched; remaining detector hits are accepted-design (paying authenticated parties, timestamp use for expiry checks).
- Manually reviewed against the standard NFT-marketplace threat list (reentrancy, integer truncation, fee-cap bypass, DOS-by-revert, sniping). Offers carry no signatures, so signature-replay does not apply.
- Tested with 98 forge tests across the 4 contracts, including dedicated regressions for every patched finding, plus static analysis (Slither: 0 high / 0 medium).
MagicWebb has not yet had an independent third-party audit: every review so far is internal or AI-assisted (see contracts/AUDIT_REPORT.md), and on Flare the fee recipient and the admin are still one EOA, not a multisig. There is no bug bounty yet (planned for Phase 4, see §8).
7. Token-economic model
MagicWebb does not have a token. There is no ICO, no airdrop, no governance token. The platform fee is collected in FLR on each settled trade.
This is a deliberate choice:
- A token would create an alignment between the platform and short-term price action that we do not want. We are building infrastructure, not a meme.
- The Flare Network already has FLR; introducing a second token to a niche venue would fragment liquidity.
- There is nothing to govern on-chain. The fee rate is a compile-time constant, and nothing on the protocol is pausable. Every network (Coston2, Songbird, Flare) deploys unsealed under a single per-network admin that can perform instant upgrades, replace the keeper, and rotate its own key (2-step
transferAdmin/acceptAdmin); it can never pause trading, change the fee, or touch escrowed funds. Immutability is a later, explicit per-network step: on the owner’s order the admin callsrenounceAdmin(), after which there is no admin, no upgrade path, no keeper rotation, andfeeRecipientcan never change.
If user feedback ever justifies governance, it will be added via a separate mechanism — not retroactively jammed in by minting a token.
8. Roadmap
| Phase | Quarter | Scope |
|---|---|---|
| Phase 1 | Q2 2026 (shipped) | Coston2 testnet. All trade primitives live. Indexer + frontend feature-complete. |
| Phase 2 | Q3–Q4 2026 | ERC-2981 creator royalties (shipped: seller-pays, 10% cap, on every network with contracts). FTSO USD display (pending). |
| Phase 3 | Q4 2026 | Cross-collection routing. Bundle listings. WFLR/USDC payment adapter for stable-priced offers. |
| Phase 4 | 2027 | Songbird deploy. Cross-network offer relay via Flare FAssets. Bug bounty live. |
9. Risks and mitigations (user-facing)
| Risk | What happens | What we do |
|---|---|---|
| Smart-contract bug | Funds at risk | Hard fee cap, internal reviews, static analysis and invariant tests (no external audit or bug bounty yet — see §6); while a network is unsealed its admin can ship an instant fix, and once the owner orders renounceAdmin() no upgrade can change behavior on that network ever again |
| Deployer key compromised | No effect on a live market | The deployer holds no power after deploy; authority sits with the separate per-network admin wallet (rotatable via 2-step transferAdmin/acceptAdmin, and gone after renounceAdmin()). No function of the current contracts lets an admin pause trading or move user funds. feeRecipient is fixed at deploy |
| Admin key compromised | Funds and approved NFTs at risk on that network | While a network is unsealed, its admin can install new contract code instantly (no upgrade delay), and new code can move escrow and use sellers’ marketplace approvals. The admin key is therefore meant to be held offline, used for nothing else, and different on every network; the current Flare admin does not yet meet that and is scheduled for rotation to a fresh key. renounceAdmin() removes this risk on a network for good |
| Keeper key compromised | Automation only | The keeper can only settle auctions to their recorded winner/seller, push refunds to their owners, and clean expired listings — it cannot move, redirect, or block any user’s funds, and it cannot enroll other keepers |
| Frontend disappears | Inconvenient | Contracts remain callable via Flarescan or any wallet’s “contract interaction” panel |
| Indexer lags | Stale UI | Frontend shows “syncing” badge; on-chain trades still settle in real time |
| Approval phishing | Drained NFTs | Per-collection approvals; user education in app; we never request blanket setApprovalForAll for unknown contracts |
10. Team and origins
MagicWebb is being built by an independent contributor in 2026 as a public-good NFT venue for Flare. The codebase is open source under MIT. Contributions, audit reports, and feedback are welcome via the project repository.
11. Closing
The NFT space spent its first cycle on speculation, the second on infrastructure, and now needs venues that respect both the assets and the people trading them. MagicWebb is one such venue: small in scope, bounded in promises, and verifiable end-to-end.
“Make the simple thing easy and the complex thing possible — and let the user verify everything.”
Find us: github.com/OfficialA1manac/MagicWebb
Read the code: contracts/src/, backend/
Read the technical whitepaper: WHITEPAPER_TECHNICAL.md