Magiceden is a Fixed-Price NFT Checkout With SOL Reserved for Fees
Magiceden is a fixed-price Solana NFT checkout where the buyer selects a listed asset, reviews the SOL debit and royalty choice, approves one wallet transaction, and receives the NFT after confirmation. The wallet must hold the displayed total plus enough SOL for Solana's base fee and any priority fee.
Insufficient fee reserve stops the ownership change
An insufficient SOL reserve is the checkout failure that matters most because Magiceden cannot settle the listing price, royalties, and required network debit together.
The reserve is separate from the seller's price and remains in the wallet unless the transaction consumes it. Magiceden recommends keeping at least 0.01 SOL in the main wallet for transaction costs. That buffer exceeds Solana's base charge for one ordinary signature: 5,000 lamports, or 0.000005 SOL, because 1 SOL contains 1,000,000,000 lamports. A checkout may also request a priority fee or create an account needed to receive the asset. If the available balance covers only the displayed purchase total, wallet simulation or chain execution rejects the sale before ownership changes, while a submitted failed transaction still consumes its network fee. A sibling page deals with Magiceden limits in depth requirements.
Fixed-price checkout versus offers and sweeps
Magiceden's fixed-price Buy Now path commits to one seller's displayed price, while offers await acceptance and sweeps combine several listings into a broader purchase.
Buy Now is the relevant path when the buyer accepts the listed SOL amount for one specific NFT. It does not introduce an offer amount, acceptance period, or automated replacement rule. The listing remains available to other buyers until Solana executes a valid sale, so opening checkout does not reserve the item. If another transaction fills or cancels the listing first, the buyer's sale instructions fail together. Returning to the item page then reveals the updated state. This distinction keeps the decision centered on the exact asset, current listing, and wallet debit shown before approval.
What must the wallet hold before checkout?
The connected Magiceden wallet must hold the displayed buyer total, Solana network fees, and any account-creation amount included by the constructed transaction.
Use the same active address for balance review, transaction approval, and post-purchase verification. Common Solana signers include Phantom, Solflare, and Backpack, while a Ledger account connects through compatible wallet software. The item price belongs in the main wallet rather than an offer escrow account. Leave the fee reserve untouched when calculating the highest affordable listing. If the receiving asset standard needs a new associated token account, that account's funding appears within the transaction's balance changes. Any unused reserve stays under the buyer's control after settlement.
The checkout review separates three kinds of value
The Magiceden checkout review separates the amount the buyer pays from deductions applied to seller proceeds and from Solana's independent network charge.
Listing price and marketplace fee
The fixed listing price is the SOL amount accepted by the seller. Magiceden deducts a 2% marketplace fee from the seller's listed amount rather than adding that fee to the buyer's fixed SOL price. Creating the listing carries a 0% listing fee. Those seller-side terms matter when reading checkout because the buyer's principal debit still begins with the displayed list price.
Royalty selection
Collections with optional royalties present three buyer choices: full at 100%, half at 50%, or none at 0%. Full royalty is the default selection. The chosen percentage applies to the creator royalty rate stored for that collection, not to Magiceden's marketplace fee. Collections that enforce royalties, including relevant MIP-1 configurations, do not present the same discretion. The review panel therefore decides whether the buyer pays the listing alone or the listing plus some or all of the stated royalty.
Worked checkout arithmetic
For one worked calculation, treat every following input as hypothetical: a 2 SOL listing, a 5% creator royalty, a 100% royalty choice, one required signature, a 20,000-lamport priority fee, and zero account-creation debit. The royalty adds 0.10 SOL. The base fee adds 0.000005 SOL, and the priority fee adds 0.000020 SOL. The buyer therefore needs 2.100025 SOL for execution. From the 2 SOL listing, the 2% marketplace fee equals 0.04 SOL, leaving 1.96 SOL in seller proceeds, while the creator receives 0.10 SOL.
Wallet approval is the final decision boundary
A wallet approval for Magiceden is the final decision boundary because the signature authorizes one exact Solana message rather than a general purchase.
Before the signature
Confirm the active public key, Solana network, requested SOL outflow, and any decoded account changes. A Solana public key represents 32 bytes, although wallets display it in base-58 form. Connecting an account only exposes the address and permitted account information; it does not approve the sale. The later transaction prompt carries the executable message. If its account or debit differs from the checkout review, reject it and rebuild the purchase from the item page.
After the signature
Each Solana signer contributes one 64-byte Ed25519 signature. That signature binds the signer to the recent blockhash, account list, and compiled instructions in the message. The first signature also serves as the transaction identifier. Changing the royalty preference, active wallet, or listing state requires a newly constructed message and a new approval. Once submitted, the wallet waits for network status rather than editing the signed purchase.
How does Solana execute the sale atomically?
Solana executes a Magiceden sale atomically: listing payment, asset transfer, royalty instructions, and account creation either succeed together or roll back together.
Solana charges a base fee of 5,000 lamports for every required signature, and it charges that fee even when transaction execution fails. An optional priority fee equals the requested compute-unit price multiplied by the compute-unit limit, divided by 1,000,000 and rounded upward to a whole lamport. One lamport contains 1,000,000 micro-lamports, and the default compute-unit price is 0 micro-lamports. The requested limit, rather than actual usage, determines that additional fee.
Without an explicit compute limit, Solana allocates 200,000 compute units per non-builtin instruction and 3,000 per builtin instruction, subject to a 1,400,000-unit transaction maximum. A serialized transaction fits within 1,232 bytes. Those limits explain why the checkout builds a compact message and why the wallet signs a prepared instruction set rather than a loose description of the intended purchase.
Ownership records differ across Solana NFT standards
A completed Magiceden purchase changes the asset's recognized owner, although the precise account update follows the NFT standard used by that collection.
Metaplex Token Metadata assets
Under Metaplex Token Metadata, a conventional NFT mint has a supply of 1 and 0 decimals. The SPL Token transfer moves that single unit from the seller's token account into an associated token account controlled by the buyer. The mint address and metadata account remain the same, so the asset identity survives the sale. A programmable NFT under MIP-1 routes the transfer through Token Metadata and its authorization rules rather than a bare token move. When the destination account does not exist, the checkout transaction may create it. Successful verification shows one unit under the buyer's authority and none in the seller's former holding account.
MPL Core assets
MPL Core stores an asset and its owner in one principal asset account, without an associated token account for each wallet. Settlement updates that account's owner field to the buyer's public key. The asset address, collection relationship, name, and update authority remain separate from the ownership change. A successful Core transfer also revokes existing Transfer, Burn, and Freeze Delegates, giving the new owner a clean post-transfer authority state.
Bubblegum compressed NFTs
Bubblegum represents a compressed NFT as a leaf in a state-compression Merkle tree. Its sale changes the leaf's ownership data and advances the tree state rather than moving one token between ordinary SPL Token accounts. Wallet galleries and Magiceden rely on indexed Digital Asset Standard API data to present that ownership. The asset identifier and buyer address provide stronger verification than waiting for the thumbnail alone.
Confirmation and verification use independent records
After that point, Magiceden's success message confirms the interface outcome, while the Solana transaction signature and resulting owner record confirm the executed state independently on-chain.
Solana exposes three commitment labels: processed, confirmed, and finalized. A processed status means a validator included the transaction, confirmed adds cluster voting, and finalized records the strongest completed state. Copy the transaction signature from the wallet activity and inspect it in Solscan. Check for successful execution, the buyer's SOL debit, and the asset transfer. Then compare the asset's owner with the same 32-byte public key used at checkout. A wallet gallery may refresh after the chain record because its indexer follows separately, so the signature and owner field settle the question first.
What should you do when the wallet shows insufficient SOL?
An insufficient-SOL error on Magiceden is fixed by funding the same active wallet, rebuilding the checkout, and signing only after the refreshed balance appears.
Close the stale approval first; its recent blockhash does not remain valid indefinitely.
Phantom error 32003 can accompany a rejected transaction when the wallet lacks the necessary SOL. Add enough SOL to cover the displayed buyer total and the fee reserve, then confirm that the funded address matches the account connected to Magiceden. Reload the item page before pressing Buy Now again. A recent Solana blockhash remains valid for 150 slots, so the earlier message can expire even after the balance changes. A refreshed checkout supplies the current listing state, updated balance inputs, and a new blockhash.
Inspect any existing transaction signature before retrying. A confirmed owner change means the first checkout finished, even if the interface message arrived late.
The complete state path from item page to owned asset
The fixed-price Magiceden path moves through five observable states: active listing, funded wallet, reviewed message, submitted signature, and verified ownership on Solana.
Start with the item page and confirm that the intended NFT still carries the accepted fixed SOL price. Connect the funded address, choose the available royalty setting, and read the buyer total before opening the wallet. Compare the wallet's account and outflow with that review, then approve the prepared message. Retain the resulting transaction signature while confirmation advances. Finally, verify that the same asset identifier now resolves to the buyer's address. The signature connects the interface decision, network execution, and recorded ownership change.
Things people ask
When does a fixed-price Magiceden listing stop being available during checkout?
A fixed-price listing stays available only until a valid purchase fills it or the seller changes or cancels it. Opening the item page or wallet prompt does not reserve the NFT. If the listing state changes before your signed transaction executes, Solana rolls back the sale instructions. The network fee for a submitted attempt remains charged, and Magiceden must construct a fresh transaction from the new listing state.
Does rejecting the Magiceden wallet request deduct any SOL?
Rejecting the wallet request deducts no SOL when the transaction never leaves the wallet. A denial produces no on-chain signature and gives Solana nothing to execute. The listing remains governed by its seller and can still be filled elsewhere. If you approved first and then saw an error, check the transaction signature before retrying, because a submitted transaction can consume its network fee even when its sale instructions fail. The wallet activity record distinguishes a local rejection from chain execution.
Where does unused fee-reserve SOL remain after a successful purchase?
Unused fee-reserve SOL stays in the same connected wallet after settlement. Magiceden does not sweep the recommended buffer into a separate account. Solana deducts the actual base fee, any requested priority fee, and account funding included in the transaction; the remainder is untouched. Compare the wallet's post-sale SOL balance with the transaction's fee and balance changes, not with the maximum reserve that you chose to keep.
Does the NFT's metadata change when Magiceden transfers ownership?
Ownership transfer does not, by itself, rewrite the NFT's name, artwork reference, attributes, or collection membership. Metaplex Token Metadata keeps those fields associated with the mint, while MPL Core keeps them in the asset account as its owner field changes. Update authority is separate from ownership. A later metadata update remains possible only under the asset's existing standard and authority settings, so the buyer should record the asset identifier rather than rely only on a gallery image.
Will a hardware wallet change the fee for the same SOL purchase?
A hardware wallet does not add a Magiceden surcharge to the same constructed transaction. Solana calculates fees from required signatures and the requested compute budget, not from whether a Ledger or software wallet holds the key. The Ledger device still needs its Solana app and a compatible connection path. A rebuilt transaction deserves a separate review because its compute settings can differ.
What information identifies one completed Magiceden checkout for support?
One completed checkout is identified most precisely by its Solana transaction signature. Pair that signature with the connected public key, the NFT mint or Core asset address, and the approximate action sequence shown in the wallet activity. Those fields let support distinguish an executed sale from a display delay without relying on screenshots alone. Never provide a private key or recovery phrase; neither value is needed to inspect public transaction state accurately.