When a ZEC t1 or t3 is this pool's account

This pool account is one transparent ZEC address, not any string that looks like a wallet. The page accepts t1 or t3 with exactly 33 characters after the prefix, without easily confused characters. The 2Miners help example is a t1, written from t1fu…. That extract does not show a t3. A t3 works because this page accepts it, not because the help page demonstrates one.

What the fields mean

Transparent and shielded are Zcash's two treatments of financial information. A transparent address makes the information public. A shielded address keeps it private. A pool can credit a transparent address because that information is public. A unified address packs more than one way to receive into one string. This page does not treat it as a t1 or t3. The help page also lets payouts go out as BTC or TON. Those strings are a different payout setup. Putting them in the ZEC monitor does not open a ZEC account.

What to inspect

Check three things: the prefix is t1 or t3, 33 characters follow, and there is no space or line break. On the ASICs listed in the help, the Worker field is your wallet address. That wallet should still be a transparent t-address. Do not put a rig nickname in this page's address box. A shielded receive string copied from an exchange or a desktop wallet will not pass.

Next step

After the string checks out, save that device on the Zcash monitor. Free is five saved devices for this project. Pro is fifty. Several workers under one transparent address still share one pool balance. Seeing them does not automatically use extra device slots. A slot is used only when you save a separate device. Never paste a private key.

An illustrative case

A t1 plus 33 characters, the shape of the help example, is queried. Changing that string to start with z, or using a unified address from an exchange, is not queried, and the page does not invent a pool balance of 0 ZEC. A t3 plus 33 characters is queried. If the pool has no account for it, the result is that this account is absent, not that the shape was refused. The case only shows the acceptance range.

Limits

This page does not explain viewing keys for shielded transactions, and it does not draw the transparent address's full chain history on the same table as pool unpaid. The Zcash article does not publish a t1/t3 character table. The table that matters is the shape this page actually accepts. Fee figures on the help page belong to the pool's payout note at the time of that page. This guide does not copy them and does not promise they still apply.