This guide covers the ZECUSDT perpetual on BloFin. It is a linear perpetual futures contract, settled in USDT, sized in contracts worth 0.1 ZEC each, with leverage you can set as high as 75x. You never receive the coin, and no Zcash address is created at any point.
This guide covers the contract's published parameters, what to set up first, the order path itself, what funding costs an open position, the size limits the venue enforces, and the errors that cost money here. It does not cover directional views. It also does not cover buying the coin to hold, which is a separate job with separate risks.
Every contract figure below was read from BloFin's public API on August 22, 2026, and each endpoint is named inline so you can repeat the reading yourself.
What the ZECUSDT contract actually is
A perpetual future tracks an underlying asset continuously and has no settlement date. A position runs until you close it. What you own is a claim priced in the quote currency rather than any amount of the coin.
The perpetuals feed returns one ZEC market, typed SWAP. Spot instruments sit on a separate endpoint, where ZEC/USDT has been listed since August 29, 2024 (source: BloFin spot instruments endpoint).
| Parameter | Published value | What it means for your order |
|---|---|---|
| Instrument ID | ZEC-USDT |
The market you select in the interface |
| Contract type | Linear, settled in USDT | Gains and losses land in the quote currency |
| Contract value | 0.1 ZEC | One contract is one tenth of a coin |
| Minimum order size | 0.1 contracts | The smallest order is 0.01 ZEC |
| Lot size | 0.1 contracts | Sizes must be multiples of 0.1 |
| Tick size | 0.01 | Limit prices must be multiples of 0.01 |
| Maximum leverage | 75x | A published ceiling, not a recommendation |
| Listing date | October 18, 2023 | The market has run for nearly three years |
| State | live |
Trading, not suspended or delisted |
Two of those rows cause most beginner errors. The contract multiplier of 0.1 ZEC is the one traders misread most often. An order size of 10 is one coin, not ten. The lot and tick constraints are the other, because an order that breaks either is rejected outright, not rounded to fit.
The expiry field carries a timestamp in the twenty-second century, which is how a perpetual is written in a schema that needs the field filled. The contract does not lack an expiry. It carries one set so far out that it never matters.
Zcash itself is a separate subject with its own mechanics, documented by the project directly (source: Zcash project documentation). None of it reaches a contract position, which is why the two choices are separate.
What you need before your first order
Four things to have ready, and traders skip the fourth far more often than the other three combined.
A funded balance in the quote currency comes first. The instruments feed reports settleCurrency as USDT, so margin, realized gains and realized losses all move in that currency, and depositing the coin itself does not capitalize this market in any way.
Account security comes second, and it belongs before the first order rather than after the first incident. Two-factor authentication is the baseline, and our guide to account security fundamentals covers the configuration in detail.
A deliberately chosen leverage setting comes third. The published ceiling of 75x is a system limit. It is not a default worth inheriting from whatever the interface last used. The arithmetic later in this guide shows why that difference is expensive.
A position size determined before the order form opens comes fourth. Choosing exposure while watching a moving quote is how traders end up holding something they would have rejected an hour earlier, and our treatment of sizing a crypto position is the right preparation. If perpetual contracts are unfamiliar, the comparison between spot and perpetual markets is worth reading first, since this guide assumes the mechanism and covers only what is specific to this contract.
Before submitting anything, run the four items above as a written checklist, not from memory:
- Quote-currency balance funded and visible in the futures wallet
- Two-factor authentication active on the account
- Leverage configured to a value you selected consciously
- Position size written down before the order form opens
A trader who can point at all four has removed the four most common avoidable failures on this contract. Our broader security checklist for crypto accounts covers the account layer in more depth than a trading guide reasonably can.
How to trade ZEC on BloFin: step by step
Nine steps, in the order the interface presents them. Each one corresponds to a decision rather than a keystroke, and the sequence matters because several of the decisions constrain the ones that follow.
Step 1: Fund the account in the quote currency
Deposit or internally transfer USDT into the futures balance. Because the contract settles in USDT, no other asset funds a position here. A balance held in the coin itself stays unavailable to this market, however large it is.
Step 2: Select the ZECUSDT market
Search the futures market list for ZEC and select ZECUSDT. The futures feed contains a single ZEC perpetual, so there is no ambiguity about which instrument you are opening and no need to compare variants.
Step 3: Set leverage deliberately
Configure leverage before deciding quantity, because the setting determines how much margin a given exposure consumes and how far the quote can move against the position before the margin behind it is exhausted. Treat the published ceiling as information about system limits rather than as guidance.
Step 4: Choose between a market order and a limit order
A market order executes immediately against resting liquidity, which means accepting the prevailing spread and whatever slippage the order's own size produces. A limit order executes only at your nominated level or better, which means retaining price control at the cost of execution certainty.
The choice is not purely stylistic, because the two order types interact with this contract's liquidity profile very differently. On a thin market, the gap between the quoted level and the level a market order actually gets widens with order size. That gap is hard to estimate up front. A limit order caps it by design, at the cost of maybe not filling at all.
For a first position, a limit order is the better choice to learn on, because it isolates the mechanics from the volatility. Our explanation of market, limit and stop orders covers the full comparison, and the related distinction between maker and taker execution determines which fee schedule applies.
Step 5: Enter a quantity that respects the lot constraint
Quantity is counted in contracts and must be an integer multiple of 0.1 contracts. Since one contract represents 0.1 ZEC, the conversion is straightforward once stated explicitly:
- 0.1 contracts equals 0.01 ZEC, which is the minimum permissible order
- 1 contract equals 0.1 ZEC
- 10 contracts equal 1 ZEC
- 100 contracts equal 10 ZEC
Any quantity that is not a multiple of 0.1 contracts is refused at submission. The venue declines to guess your intent, which is preferable to a silent adjustment you would discover only afterward.
Step 6: Place limit prices on the tick
Limit prices must be multiples of 0.01, the tick size the instruments feed publishes for this contract. A price carrying three decimal places is rejected rather than rounded, and the rejection message describes a constraint violation rather than a system fault.
Step 7: Submit a deliberately undersized first order
Open a position much smaller than the one you eventually intend to hold, then examine what the position panel reports before committing real size. The contract multiplier is the parameter most likely to surprise a newcomer, and a single small execution resolves the question faster and more convincingly than any documentation, this page included.
Check three numbers on that first fill. The contract quantity should match what you sent. The exposure in coin terms should match the multiplier. The margin used should match the leverage you set. If any of them is off, close the position and find out why before you scale.
Step 8: Note when the position crosses a funding settlement
Once open, the position participates in the funding mechanism at fixed intervals. The next section quantifies the cost. What matters in practice is that funding applies to whatever position exists at each settlement timestamp, so an intraday position opened and closed between settlements incurs none of it.
Step 9: Define the exit before it becomes urgent
Decide the levels at which you close, in both directions. Then decide whether a resting protective order should enforce that for you. Our guide to placing protective orders on BloFin covers the mechanics. A position without a planned exit is a position whose exit gets chosen for you.
Reading the position panel after your first fill
The panel that appears once a position exists reports several quantities, and confirming that they agree with your intent is a two-minute discipline that prevents most sizing errors from compounding.
Contract quantity is what you submitted, expressed in contracts rather than coins. Multiply it by 0.1 to recover exposure in coin terms, and compare that against what you meant to open. A gap here is almost always the multiplier rather than an execution error.
Notional value is the exposure in the quote currency, and it is the figure that funding and profit calculations both reference. It should equal your contract quantity multiplied by 0.1 and then by the entry level, which makes it a useful independent check on the previous line.
Margin is the capital the position consumes, and it should approximate notional divided by the leverage you configured. If margin looks larger than that arithmetic predicts, the leverage setting did not apply as you expected. The position is more cautious than you meant. If it looks smaller, the setting is more aggressive than intended, which is the direction that costs money.
Unrealized profit and loss updates continuously against the reference the venue uses for valuation, which is not necessarily the last traded level. Small divergences between the two are ordinary rather than erroneous.
Forced closure is not the only way exposure ends. The panel shows the alternatives too. Closing by hand, cutting the size, or flipping direction all appear as ordinary position changes. Knowing which one you intend before you open removes a decision from the moment it is hardest to make well.
Check all four before adding to the position. A discrepancy discovered at minimal size is a lesson; the same discrepancy discovered at intended size is a loss.
What funding costs a position that stays open
Two distinct costs attach to a perpetual position, and mixing them up leads to wrong expectations about which one matters.
Trading fees apply at execution, on entry and on exit. They follow the venue's standard maker and taker schedule rather than anything specific to this contract. Our overview of what trading actually costs covers that schedule.
Funding is the mechanism specific to perpetuals, and it is not a fee collected by the venue. It is a regular transfer between the long and short sides of the same contract, set to keep the perpetual's quote tethered to the underlying spot reference. A positive rate transfers value from longs to shorts; a negative rate reverses the direction.
The funding endpoint publishes the parameters governing this contract directly (source: BloFin funding rate endpoint):
| Funding parameter | Published value |
|---|---|
| Settlement interval | 8 hours, therefore three settlements daily |
| Rate observed on August 22, 2026 | 0.0447% per settlement |
| Rate ceiling | 5% per settlement |
| Rate floor | -5% per settlement |
At that reading, a long position accrued about 0.13% of its notional value per day across three settlements. That figure is genuinely small relative to the price variation the same position is exposed to, and understanding why is more useful than memorizing the number.
Two properties of the rate matter more than its size. It changes sign regularly, which means a holder can be compensated for holding rather than charged for it, so funding is not a one-way cost the way a trading fee is. And the permitted band is more than a hundred times wider than the observed rate, because the ceiling exists for conditions in which positioning has become severely one-sided and cannot unwind cheaply. Our explanation of how funding rates work covers the general mechanism, and the pillar's dedicated treatment of perpetual mechanics on this contract goes further into the specifics.
How leverage changes the arithmetic
This is the section that determines outcomes, and it is arithmetic rather than judgment, which makes it unusually easy to get right.
Leverage determines the proportional adverse movement that exhausts the margin supporting a position. At leverage of L, an adverse move of one divided by L consumes that margin entirely. The relationship is mechanical and identical on every contract.
| Configured leverage | Adverse move that exhausts margin |
|---|---|
| 75x | 1.33% |
| 25x | 4.00% |
| 10x | 10.00% |
| 5x | 20.00% |
In practice the position is closed by the venue before margin reaches zero, because a maintenance requirement sits above that threshold. The percentages above are therefore outer bounds rather than trigger levels, and the difference between the two is covered in our guide to leverage and forced closure.
Now compare that against the funding figure. At that reading, an entire day of funding costs about 0.13% of notional. A single adverse move of 1.33% therefore costs roughly ten times what a full day of funding does, at the highest leverage the contract permits.
The point holds beyond this contract. Funding is the visible, published cost, and it is almost never the one that decides the outcome. Price variation is, and leverage is the multiplier applied to it.
Volatility on this specific contract deserves emphasis. In the twenty-four hours preceding the reading on August 22, 2026, the tickers endpoint reported a high roughly 1.50 times the matching low (source: BloFin tickers endpoint). A fifty percent intraday range is many multiples of the 1.33% that exhausts margin at maximum leverage, and it occurred on an ordinary trading day rather than during an exceptional event. Our treatment of volatility in crypto markets covers the general phenomenon, and the pillar's analysis of what moves this asset covers the specific drivers.
A worked example, in plain numbers
The arithmetic on this contract is easier to trust once you have run it once. Here it is, with no prices involved.
Say you open 20 contracts. One contract is 0.1 ZEC, so 20 contracts is 2 ZEC of exposure. That is the first number to confirm on the panel.
Say you set leverage to 25x. The margin behind the position is one twenty-fifth of its notional value, so it is 4% of it. A move of 4% against you uses that margin up.
Now hold it for a day. At the rate observed on August 22, 2026, funding costs about 0.13% of notional. That is one thirtieth of the 4% move that ends the position.
Read those two numbers side by side. The daily carry is small. The move is not. Sizing decisions should follow the second number, not the first.
Run the same arithmetic at 75x and the picture sharpens. Margin drops to 1.33% of notional. The move that ends the position drops with it. Funding stays where it was. Higher leverage does not make holding cheaper; it makes being wrong faster.
Order size ceilings and why they differ
The instruments feed publishes two distinct maxima for this contract, and the gap between them reflects a real market constraint rather than an arbitrary policy.
| Constraint | Contracts | Equivalent exposure |
|---|---|---|
| Maximum limit order | 15,000 | 1,500 ZEC |
| Maximum market order | 10,000 | 1,000 ZEC |
The market-order ceiling sits a third below the limit-order ceiling because a market order consumes resting liquidity progressively, filling at worse and worse levels as it works through the book. On a contract of this size, a sufficiently large market order would produce an execution price far off from the quote that prompted it, and the lower ceiling constrains that outcome directly. Our explanation of how an order book fills covers the mechanism.
The distinction also explains a behavior that surprises traders scaling into a position for the first time. An order above the market-order ceiling is not filled up to the limit and then cut off. It is refused whole, so the exposure you wanted simply does not exist. Split the intent into several smaller orders instead. Working them as limit orders raises the ceiling that applies and cuts the execution cost of the size.
For most readers these ceilings sit far above any exposure they will take, and the constraint never becomes operative. They matter to anyone sizing in the hundreds of coins. At that scale, work a limit order patiently rather than send a market order near the published maximum.
Seven mistakes that reliably cost money here
These are ordered by how frequently they occur rather than by how much they cost, though the two line up more closely than you might expect.
- Interpreting contract quantity as coin quantity. An order of 10 contracts represents 1 ZEC of exposure. Confirm the notional on a small first execution rather than reasoning about it.
- Inheriting whatever leverage the interface last used. The published ceiling describes what the system permits, and nothing about it is a default worth accepting.
- Submitting quantities or prices that violate the lot and tick constraints. Both produce rejection rather than adjustment, and both account for a large share of unexplained submission failures.
- Treating funding as the dominant cost. It accrued at about 0.13% daily at that reading, while a single 1.33% adverse move at maximum leverage costs roughly ten times that.
- Reading a positive funding rate as directional information. It establishes that longs are paying shorts at that moment. It establishes nothing about which side proves correct.
- Sizing a thin, headline-driven contract as though it were a major pair. This asset moves on discrete announcements without the preceding drift that would let a position be reduced gradually.
- Confusing contract exposure with ownership. A perpetual position confers price exposure and nothing else. If the objective is the asset itself, acquiring and holding the coin is the applicable procedure.
Troubleshooting the common failures
Most problems on this contract fall into four categories, and three of them are constraint violations rather than faults.
An order rejected without an evident cause is usually a lot or tick violation. Check the quantity against the 0.1 contract multiple and the limit price against the 0.01 tick before investigating anything else, because these two account for most rejections on this market.
A position that appears smaller or larger than intended is almost always the multiplier. Multiply the contract quantity by 0.1 to obtain exposure in coin terms, so a panel reporting 50 contracts describes 5 ZEC of exposure.
Funding charged when none was anticipated means the position was open across a settlement timestamp. Funding attaches to whatever exists at that moment, and holding across a settlement incurs it regardless of how briefly the position existed on either side of it.
Funding credited rather than charged means the rate had turned negative, transferring value from shorts to longs. This is ordinary behavior of the mechanism rather than an accounting error, and it can persist for extended periods.
A rejection citing insufficient margin usually reflects leverage rather than balance. The margin a position consumes scales inversely with the configured leverage, so a quantity that is affordable at a higher setting becomes unaffordable at a lower one without any change to the balance itself. Confirm the setting before adding funds.
An execution level much worse than the quote at submission indicates that a market order consumed more of the resting book than the visible depth suggested. This is a property of the market rather than a fault, and the response is a limit order at a nominated level rather than a larger market order.
The operator-desk view
BloFin lists this contract because there is real demand for it. The venue is better served by traders who understand the instrument than by traders who learn its properties during a bad session.
Two observations are worth stating plainly from this side of the interface. The first is that this is a thin, headline-driven market. The tickers endpoint reported roughly 89,350 coins of turnover in the twenty-four hours to the reading. A contract that size moves much further on the same order flow than a major pair does. The second is that the maximum leverage figure is a published system limit rather than an endorsed configuration, which is precisely why the arithmetic section above appears on a page the venue wrote itself.
A venue earns from trading activity no matter the direction. That structural fact is the reason a page published here should supply contract parameters and margin arithmetic rather than a view on where the quote is headed.
What this contract leaves out
A perpetual position does not deliver the coin. A contract position gives you no wallet, no address, and no access to Zcash's shielded transactions. If your interest in the asset is its privacy features, you need the custody route instead, covered in storing the coin securely.
Holding a position through a venue also concentrates a category of risk that holding the coin does not, and the pillar's treatment of custody and venue risk covers what that concentration involves.
Frequently asked questions
How many ZEC does one ZECUSDT contract represent?
One contract represents 0.1 ZEC, set by the contractValue field on the instruments endpoint. Sizes must be submitted in multiples of 0.1 contracts. That makes the minimum order 0.01 ZEC of exposure and makes a quantity of 10 contracts equal to 1 ZEC rather than 10. Limit prices must also fall on a 0.01 tick. Both constraints are enforced by rejection rather than rounding, which is why an order that looks entirely reasonable can still be refused at submission.
What is the maximum leverage available on ZECUSDT?
The instruments feed publishes a maximum of 75x for this contract. Treat that as a system limit, not as guidance. The arithmetic is harsh at that setting. A move of about 1.33% against you uses up the margin behind the position, and the venue closes it a little before that point, because a maintenance requirement sits above zero equity. At 10x the equivalent figure is 10%, which is a very different exposure to the same underlying volatility.
How often does funding settle on this contract?
Every eight hours, producing three settlements per day. At the reading taken on August 22, 2026 the rate stood at 0.0447% per settlement, equivalent to roughly 0.13% of notional per day for a long position. The rate is bounded at 5% and -5% per settlement, and it changes sign frequently enough that a holder can be compensated for holding rather than charged. Funding applies only to positions open at a settlement timestamp.
Can I buy spot ZEC on BloFin?
Yes. BloFin lists ZEC/USDT on spot, live since August 29, 2024, with a minimum order of 0.001 ZEC (source: BloFin spot instruments endpoint). Spot gives you the coin itself, which you can withdraw to a Zcash address and shield if you choose. The ZECUSDT perpetual is a separate instrument that tracks the price without ever delivering a coin, so it cannot be withdrawn or shielded. If you want to own ZEC, spot is the market you want.
Is holding this contract the same as owning Zcash?
No, and the difference is more than technical. A perpetual position provides exposure to the quoted price and nothing further: no coin, no wallet, no address, and no access to shielded transactions. Owning the asset means holding it directly, which carries the custody duties and the privacy features that come with it. The two activities answer different objectives and carry different risks, so the choice between them should follow from what you actually want rather than from which interface is closer to hand.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Contract parameters, funding figures and market data were read from BloFin's public API endpoints, named inline, on August 22, 2026. All facts independently verified against those endpoints and current as of August 2026. Contract parameters can change; re-read the instruments feed before relying on any figure published here.