zkSync Era ERC-1155 Event Ticket Batch Distributor

WHAT IT DOES

This tool mints new ERC-1155 event tickets from an existing ticketing contract and distributes them directly to multiple attendees in a single batched transaction on zkSync Era. ERC-1155 is the multi-token standard ideal for event ticketing, where a single contract can manage multiple events (token IDs) with different ticket quantities per attendee. Instead of minting tickets one by one and paying gas for each transfer, this tool combines all mint-and-distribute operations into one call to a shared bulk-sender contract. The tool reads the contract's ownership, minter role, token total supply, and metadata URI. It checks attendee wallet balances and current gas price before submitting the transaction. You specify the ERC-1155 ticketing contract address, the ticket token ID (event identifier), event name, base metadata URI, a list of attendee addresses with per-person ticket quantities, and the price per ticket (if any). The tool computes the total cost including the sender contract fee, verifies your wallet has sufficient balance, and submits one transaction that mints and pushes all tickets to attendees' wallets.

HOW TO USE

Connect your EVM wallet via the BotGentz wallet bridge. Select zkSync Era (chain ID 324) from the network dropdown. Enter the address of the ERC-1155 ticketing contract you control (or have minter permissions for). Specify the ticket token ID (e.g., 1 for "Music Festival 2025"). Provide an event name and the base metadata URI that will be used for ticket metadata. In the text area, list each attendee on a separate line with their address and the number of tickets to mint for them, separated by a comma. Set the price per ticket in wei (use 0 for free tickets). Click "Review distribution" to see the attendee count, total tickets, itemized cost, sender contract fee, and the total amount payable. The tool also displays the sender contract address and its owner for transparency. If everything looks correct, click "Sign & distribute tickets" — your wallet will ask you to confirm the transaction. Once confirmed, the tool shows progress and the final transaction hash with a link to the zkSync Era block explorer.

TECHNICAL MECHANISM

This tool uses the BotGentz shared bulk-sender contract registry, keyed by chain ID and ERC standard. For zkSync Era (chain 324), the erc1155 sender address is hardcoded from the registry. The tool calls `fee()` and `owner()` on the sender contract live every time — it never caches these values. It computes the total payable as (price per ticket × total ticket count) + sender fee. Before signing, it checks the connected wallet's native balance against this total using `provider.getBalance()`. The batch operation calls `batchMint1155(address nft, uint256 tokenId, address[] recipients, uint256[] amounts, string baseURI, uint256 pricePerToken)` on the sender contract, sending the exact total value as `msg.value`. The sender contract then iterates the attendee list, mints the specified ticket quantity for each using the ERC-1155 contract's mint function, and transfers ownership atomically within the same transaction. All recipient operations are sequential and awaited inside the contract, preventing nonce conflicts. The tool uses `receipt.effectiveGasPrice` to report actual gas cost after EIP-1559, never `tx.gasPrice`. This is a true push distribution — attendees do not need to call any claim function or pay gas to receive their tickets.

WHAT IT CANNOT SEE

This tool cannot verify whether the off-chain metadata URIs you provide are actually accessible or correctly formatted. If the base URI points to a missing IPFS hash or a broken server, the tickets will still mint successfully but will display no metadata. It also cannot confirm that attendee wallets are ready to receive ERC-1155 tokens or that they support the standard. The tool does not check if the contract has minting paused or if your address has the minter role — those are preconditions you must verify externally. Most importantly, this tool cannot validate ticket expiration dates, event dates, or any on-chain or off-chain access control rules. It does not check if an attendee already holds a ticket or if tickets are transferable. It cannot detect front-running or mempool congestion. The batch is only as reliable as the underlying RPC provider; if the provider has strict `eth_getLogs` limits, the tool does not perform historical log scans, so that limitation does not apply here.

PLEASE NOTE

This tool is EVM-only. It works on zkSync Era and other chains where the BotGentz sender registry has an erc1155 entry. It does not support Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. The tool requires an existing ERC-1155 contract that implements a mint function compatible with the sender contract's expected interface. Always test with a small batch and low ticket price before distributing large quantities. zkSync Era transaction finality may differ from other EVM chains; always check the block explorer for confirmation status. This is a push distribution — the sender pays all gas, attendees receive tickets without any action. Event organizers are responsible for verifying ticket validity, expiration, and access control separately.