Skip to content
ZYPER Docs Beta

Your first mint

Goal: mint a public ERC-721 on Base from one wallet. Once this works, the multi-wallet / multi-chain pattern is the same flow with more rows.

1. Add a wallet

Open the Wallets page. The page is two tabs: groups on the left, wallets in the selected group on the right.

  1. Click + New Group. Name it test.
  2. With test selected, click Generate (creates a fresh key) or Import (paste a 64-char hex private key).
  3. Fund the wallet with a small amount of ETH on Base.

2. Add an RPC

Open the RPC page.

  1. Pick the base chain in the group list.
  2. Click + Add Endpoint. Paste your RPC URL (Alchemy, QuickNode, or any public Base RPC).
  3. The app auto-probes the endpoint with eth_chainId. If it answers with 8453, you’ll see a green chip + latency reading.

Defaults exist for every supported chain, but the public ones rate-limit fast. Pinning your own RPC is the single biggest reliability win.

3. Build the task

Open the Tasks page.

  1. Click + New Task Group. Pick Onchain, name it first-mint, chain base.
  2. Inside the group, click + Build Task.
  3. Paste the contract address. Sourcify is queried automatically — the ABI appears within ~300ms.
  4. From the Function dropdown, pick mint (or whatever the contract calls it).
  5. Fill in arguments. If the function takes a uint256 id, you can use the literal {id} token to let scavenger search find a mintable ID for you (see Scavenger search).
  6. Pick value (ETH cost per mint) and gas defaults.
  7. Pick the wallet group test.
  8. Mode: Instant for a normal mint. (Simulate = snipe-loop; Spam = unfinished.)
  9. Click Save.

4. Fire

In the group view, your task is now a row in the table. Hit Start.

The status pill cycles through Pending → Running → Completed (green) or Failed (red) with the revert reason inline. Successful runs show a tx hash linking to the chain explorer.

Live progress polls every 1s while any task is running. You can open a per-row log modal for the verbose execution trace.

What just happened

  • The app dialed your Base RPC through its persistent pool.
  • It signed the transaction with the wallet you generated, using EIP-1559 gas defaults from Settings.
  • It broadcast the signed tx, watched the mempool, and stamped the row when the receipt landed.

That’s the loop. Everything else in Zyper AIO — multi-wallet, multi-chain, social tasks, scavenger, spam — is variations on this same wallet → RPC → task → fire pattern.

Next, learn the Wallets page in depth, or jump to Tasks overview for all execution modes.