Zyper AIO
Dashboard

OpenSea Module

Create, prepare, run, and troubleshoot OpenSea mint tasks safely.

Use the OpenSea module to create mint tasks directly from an official OpenSea collection link. Zyper fills the collection and sale information into the task form so you can focus on choosing the correct phase, wallets, quantity, price limit, RPCs, gas, and timing.

Build an OpenSea drop task in the isolated Zyper demo and see how the resolved phase, method, quantity, price ceiling, wallets, and RPCs fit together.

This guide covers the user workflow only. Always verify the official collection, chain, phase, price, and wallet selection before creating a live task.

Before you start#

Prepare these items before opening the task builder:

  • An active Zyper license and the latest available app version.
  • The official OpenSea collection URL, normally https://opensea.io/collection/collection-slug.
  • Wallets imported into Zyper and funded on the correct chain.
  • Enough native token for the mint price and gas. A free mint still needs gas.
  • At least one working RPC for the collection chain. A private or reliable RPC is strongly recommended for competitive drops.
  • A proxy group if the selected phase or your OpenSea setup requires one.
  • An OpenSea API key in Settings if you plan to use an OpenSea feature that explicitly says it requires a key, such as listing or accepting an offer.

Never paste a seed phrase or private key into a task field. Wallet secrets belong only in the encrypted wallet import flow.

Create an OpenSea task#

  1. Open Tasks and click Create Task.
  2. Paste the official OpenSea collection URL into Contract Address / Launchpad Link.
  3. Wait for the task form to display Mint Phase. Do not create the task while it still says resolving....
  4. Confirm that the displayed chain and shortened NFT contract match the intended collection.
  5. Select the correct Mint Phase.
  6. Review Method and use the available option that fits the drop. See Choosing a method.
  7. Select a Proxy Group if needed.
  8. Enter NFT Amount for the quantity each selected wallet should attempt to mint.
  9. Confirm Price per NFT. This is the maximum acceptable price for one NFT, not the total for every selected wallet.
  10. Select the wallets and RPC endpoints.
  11. Configure gas, nonce, timestamp, delay, and task mode.
  12. Review every field once more, then create the task.

One selected wallet creates one task row. If you select 20 wallets with an NFT Amount of 2, you are preparing up to 20 separate wallet tasks, each attempting up to 2 NFTs.

Verify the resolved collection#

After pasting the link, check all of the following before continuing:

CheckWhat you should confirm
URLIt is the official OpenSea collection page, not a copied or look-alike domain.
ChainIt is the chain where you expect the mint to happen.
ContractThe shortened address is consistent with the official project information.
Phase countThe phase selector contains the expected public or allowlist sale.
Phase timeThe selected phase is the one that is live now or starts at your intended time.
PriceThe displayed price matches the official announcement.

If any value looks wrong, stop. Recheck the official project link and announcements before funding wallets or creating tasks.

Choose the correct mint phase#

A collection can expose multiple phases. Phases may differ by:

  • Public or allowlist eligibility.
  • Start and end time.
  • Price.
  • Per-wallet mint limit.
  • Required account preparation.

Select the exact phase you are eligible for. If two phases have similar names, use the time, price, and per-wallet limit to distinguish them.

Changing the phase may update Price per NFT. Review the value after every phase change.

Public phase#

Use a public phase when no allowlist entitlement is required. Your wallet still needs sufficient funds and must respect the collection mint limit.

Allowlist or signed phase#

Use an allowlist or signed phase only for eligible wallets. Some drops require wallet-specific preparation before they become ready. If the app shows a preparation or readiness status, wait until the selected wallets show Ready before launch.

A wallet that is not eligible will not become eligible merely because it was added to a task.

Choosing a method#

The Method selector can show these user-facing choices:

MethodWhen to choose it
OpenSea APIUse when the option is available for the drop and your OpenSea setup is configured. This is the preferred choice when available.
NormalUse when OpenSea API is unavailable for that collection or when the task form selects Normal for the phase. Some phases may require wallet preparation and a proxy.

If OpenSea API is disabled, use Normal. Do not force an unavailable method. If one method repeatedly fails to prepare, refresh the collection details and try the available method appropriate for that drop.

Proxy Group#

The proxy field is optional for some OpenSea flows and important for others.

  • Use a healthy proxy group when the phase requires wallet-specific OpenSea preparation.
  • Make sure the proxy group contains enough working proxies for the number of wallets.
  • Avoid changing proxies immediately before launch unless the existing group is failing.
  • If preparation fails for many wallets at once, test the proxy group before recreating every task.

If the OpenSea API method is working normally and the field is marked optional, you can leave it unselected.

NFT Amount and Price per NFT#

NFT Amount#

NFT Amount is the quantity each task wallet attempts to mint. The phase may display a maximum.

  • Enter a whole number of at least 1.
  • Do not exceed the official per-wallet limit.
  • Existing mints from the same wallet may reduce its remaining allowance.

Price per NFT#

Price per NFT is a safety ceiling for one NFT. The selected phase normally fills it for you.

  • Use 0 only when the selected phase is genuinely free.
  • For a paid phase, confirm the full decimal value carefully.
  • If the live mint price is above your ceiling, the task should not continue at the higher price.
  • Changing quantity does not mean you should enter the total purchase cost in this field.

Estimate each wallet’s required balance as:

(Price per NFT × NFT Amount) + gas buffer

Leave extra native token for gas spikes and optional post-mint actions.

Wallet selection#

Select only wallets that are intended for this drop.

  • Use Funded Only to hide wallets without a useful native-token balance.
  • For allowlist phases, confirm every selected wallet is eligible.
  • Check that each wallet has enough funds for its own quantity and gas.
  • Do not reuse a wallet that has already reached the phase limit.

The wallet picker shows balances as a convenience, but you should still confirm important balances before a competitive mint.

RPC Endpoints#

RPCs connect the task to the selected chain.

  • Select reliable RPC endpoints for the resolved chain.
  • Multiple endpoints can improve resilience when one provider is slow or rate limited.
  • Never select an endpoint from a different chain.
  • If no endpoint is selected, Zyper may show No RPC — Public RPC fallback. This can work, but it is not recommended for competitive launches.

If every wallet fails with the same timeout, check the RPC group before changing wallet or phase settings.

Gas settings#

FieldUser guidance
Gas LimitLeave on auto for normal use. A manual value that is too low can make every transaction fail.
Max FeeMaximum fee rate you are willing to pay. It must not be below Priority Fee.
Priority FeeMiner or validator tip used for transaction priority.

For Spam or live one-shot configurations where required fields show an asterisk, enter valid gas values before creating the task.

Gas conditions can change quickly. Values copied from an old drop may be inappropriate for a new one.

Timing and retry fields#

FieldWhat it means
NonceLeave on auto unless you intentionally need a specific wallet nonce.
TimestampStart now when empty, or wait for the entered Unix timestamp.
DelayTime in milliseconds between eligible retries.
Max TxIn Spam mode, the maximum number of transactions the task may send.
Timestamp start-endIn Spam mode, the permitted start and end window.

Double-check time zones before converting an announced launch time to Unix time. A correct phase with the wrong timestamp can still start too early or too late.

Pick a task mode#

Instant#

Use Instant when the mint is already live or when you know exactly when the task should broadcast. Instant does not wait for a closed phase to become mintable.

Simulate#

Use Simulate when you want the task to wait for the mint call to become ready before sending the live transaction. It is useful for launches where the exact opening moment is uncertain.

Spam#

Use Spam only when repeated attempts are appropriate for the chain and you understand its gas and nonce implications. Set a sensible Max Tx, time window, and gas configuration.

For the full comparison, see Task Modes.

Optional post-mint Action#

The Action toggle can add a follow-up action after a successful non-Spam mint.

ActionWhat the user configures
Transfer NFTDestination wallet and transfer gas settings.
List NFTOpenSea list price and listing expiry. Requires an OpenSea API key.
Accept OfferMinimum acceptable WETH offer and gas settings. Requires an OpenSea API key.

Action is unavailable in Spam mode. Always test unfamiliar destination, listing, and offer settings with a low-risk wallet first.

Final pre-launch checklist#

Before starting the task, confirm:

  • Official OpenSea URL.
  • Correct chain and collection contract.
  • Correct public or allowlist phase.
  • Eligible wallets selected.
  • NFT Amount is within the per-wallet limit.
  • Price per NFT is correct.
  • Every wallet has mint funds plus gas.
  • RPC endpoints are healthy and on the correct chain.
  • Gas values are appropriate for the chosen mode.
  • Timestamp and time zone are correct.
  • Max Tx and end time are set for Spam.
  • Optional Action destination and price are correct.

Editing or cloning an OpenSea task#

When editing a saved OpenSea task, the collection link, chain, and phase may be read-only. You can still adjust supported execution fields such as wallets, RPCs, gas, timing, quantity, price ceiling, and proxy group.

Clone a task when you need a new row based on an existing setup. After cloning, recheck the phase, price, time, quantity, and wallet selection. Never assume yesterday’s resolved values are still valid for a later phase.

Statuses you may see#

Status or messageMeaning and next step
resolving...Zyper is loading the collection and phases. Wait before creating the task.
loading phases...Phase information is not ready yet. Keep the dialog open and wait briefly.
ReadyRequired preparation is complete for that wallet.
Priming or PreparingWallet preparation is still in progress. Do not treat it as launch-ready yet.
FailedThe task or preparation attempt failed. Open the error details and use the troubleshooting section below.
SuccessA transaction completed successfully. Use the transaction hash to confirm the result on the chain explorer.
StoppedThe task was manually stopped or reached a configured stop condition.

Troubleshooting#

The OpenSea URL is not detected#

  • Confirm that the link uses opensea.io/collection/ and includes the collection slug.
  • Remove tracking parameters and paste the clean collection URL.
  • Make sure there are no spaces before or after the URL.
  • Open the collection in a browser to confirm it still exists.

The task stays on resolving#

  • Wait a few seconds, then paste the clean URL again.
  • Confirm your internet connection.
  • Test the OpenSea API key in Settings if the selected method depends on it.
  • Change to another working proxy if the selected proxy is failing.
  • Close and reopen the task dialog if the form became stale.

No phases appear#

  • The collection may not have an active or announced mint phase.
  • The creator may have paused or changed the sale.
  • Refresh the collection page and reopen the task builder.
  • Confirm that you pasted the collection page, not an individual NFT item page.

OpenSea API is disabled#

The drop is not currently available through that method, or Zyper could not confirm availability. Select Normal and continue with the requirements shown for that phase.

OpenSea API key is rejected or rate limited#

  • Open Settings and test the key.
  • Remove expired or mistyped keys.
  • Wait before retrying after a rate-limit message.
  • If you have multiple valid keys configured, confirm they are saved correctly.
  • Do not share your API key in screenshots or support tickets.

Wallet preparation is stuck or fails#

  • Confirm the wallet is eligible for the selected phase.
  • Check the selected proxy group and replace dead proxies.
  • Verify the system clock on your computer is correct.
  • Retry only the failed wallets instead of duplicating every ready task.
  • If the phase changed, reopen the task and select the current phase.

Price per NFT is rejected#

  • Enter a decimal ETH value such as 0, 0.05, or 0.125.
  • Do not include ETH, commas, currency symbols, or an equation.
  • Re-select the phase to restore its displayed price, then review it.

Insufficient funds#

  • Add the mint price for the full NFT Amount.
  • Add a separate native-token buffer for gas.
  • Remember that every selected wallet needs its own funds.
  • If using a post-mint action, leave enough gas for that action too.

The wallet is allowlisted but the task says ineligible#

  • Confirm you selected the exact allowlist phase.
  • Confirm the allowlisted address matches the wallet in Zyper.
  • Check whether the wallet already used its allocation.
  • Verify that the project did not replace or update the allowlist.

The phase is not open#

  • Compare the official launch time with the selected phase.
  • Check your Unix timestamp and time-zone conversion.
  • Use Simulate if the exact opening time is uncertain.
  • Confirm the sale was not paused, delayed, or ended by the creator.

RPC timeout or rate-limit error#

  • Switch to a healthy private RPC.
  • Select more than one reliable endpoint if appropriate.
  • Remove endpoints that belong to the wrong chain.
  • Reduce unnecessary parallel tasks if the provider has strict limits.
  • Retry after the provider’s rate-limit window resets.

Transaction reverts#

Common user-correctable causes include:

  • Phase not live or already ended.
  • Wallet not eligible.
  • NFT Amount exceeds the wallet limit.
  • Wallet already minted its allocation.
  • Price changed above the configured ceiling.
  • Insufficient mint value or gas balance.
  • Gas Limit set too low.
  • Stale or conflicting nonce.

Correct the cause before retrying. Repeatedly sending the same invalid task will not make it valid.

Nonce too low or replacement transaction error#

  • Check the wallet for pending transactions.
  • Return Nonce to auto unless you need manual nonce control.
  • Speed up, cancel, or wait for the earlier transaction before reusing its nonce.
  • Avoid running multiple independent tasks from the same wallet without planning nonce order.

Task shows Success but the NFT is not visible#

  • Open the transaction hash in the correct chain explorer.
  • Confirm the receipt succeeded and emitted the expected NFT transfer.
  • Wait for OpenSea and wallet indexers to refresh.
  • Check the wallet’s hidden or uncollected NFT view.
  • Make sure you are viewing the correct wallet and chain.

Listing or Accept Offer fails#

  • Confirm a valid OpenSea API key is configured.
  • Verify the NFT approval and ownership state.
  • Check that the listing expiry is still in the future.
  • For Accept Offer, confirm the offer is still active and meets your minimum WETH setting.
  • Ensure the wallet has enough native token for gas.

What to send support#

If the problem remains, send support:

  • Your Zyper app version.
  • The OpenSea collection URL.
  • The chain and selected phase name.
  • The task name and approximate time of the attempt.
  • The public wallet address that failed.
  • The exact on-screen error.
  • A transaction hash, if one was created.
  • A screenshot with private keys, seed phrases, API keys, and sensitive proxy credentials hidden.

Never send a seed phrase, private key, raw wallet export, license key, or OpenSea API key to support.