Gold tops $4,050, up 3.5%: check the XAU orders still open

What the two quotations establish

Odaily's report is a short market observation: Gate, XAUUSD, $4,051.26 per ounce, and a 3.5% increase over the reported 24-hour period. Keep those labels together. Describing the same number as Bitget's last price would change the claim. Calling the later Bitget observation proof of a decline from Gate's quotation would also combine different instruments and times into a price sequence the evidence does not contain.

The independently retrieved Bitget ticker confirms an XAUUSDT perpetual quotation above 4,000 in the same evening. It reports a last price of 4,044.94 USDT, a 24-hour opening reference of 3,926.17, and a change field of 0.03025, or 3.025%. This supports the direction of the gold-linked contract's move. It does not independently reproduce the Gate instrument's exact 3.5% increase.

Using the displayed Bitget prices, the arithmetic is (4,044.94 ÷ 3,926.17 − 1) × 100, approximately 3.025%. The absolute difference is 118.77 USDT per XAU unit. Both calculations describe the captured contract and opening reference. A reader comparing a different chart window needs that chart's own starting price.

ChainCatcher also carried a same-evening article saying gold had returned above $4,000 during broader market swings. That gives context for the level, but does not establish why this particular gold quotation advanced by 3.5%. Its broader political interpretation is not needed to calculate an existing position's exposure. The ChainCatcher article is a separate account of the market session.

The contract fields worth putting beside your order

Bitget's official XAUUSDT contract response identified the product as a perpetual, with XAU as the base asset and USDT as the quote and supported margin asset. Its status field read normal. Those are useful identifiers when comparing the news with a position screen. They do not establish a reader's regional eligibility or what their account currently permits.

The same response specified a minimum trade quantity of 0.01, a quantity increment of 0.01 and a minimum trade value of 5 USDT. Read these fields together. Multiplying the snapshot last price by 0.01 gives approximately 40.4494 USDT of notional. A minimum value of 5 USDT therefore does not mean that a 5 USDT notional order also meets the captured minimum quantity.

The contract specifications and ticker are official Bitget public market responses captured at 20:46 SGT. Source: Bitget XAUUSDT contract specifications and ticker, api.bitget.com. For a reader comparing their existing product identifiers, the Bitget exchange profile provides the site's venue reference.

A position quantity and an amount of margin are different entries to read on the account screen. The arithmetic here multiplies the XAU quantity by a quoted price. It does not calculate required margin, liquidation price or an account's available balance. Those figures need the actual account settings and records, which the public market response does not provide.

SponsoredBitget

Partner rebate share60%Up to

Check regional eligibility and account terms

→Enter the code when you sign up: nexu888

Sign up on Bitget →Codenexu888Copied

A 0.1 XAU example keeps the units visible

Assume an existing position represents 0.1 XAU. At the captured last price of 4,044.94 USDT, its quoted notional would be 0.1 × 4,044.94 = 404.494 USDT. At the 24-hour opening reference of 3,926.17, the same quantity corresponds to 392.617 USDT. The difference is 11.877 USDT before any costs, using those two prices solely as an example.

That 11.877 USDT is not a report of anyone's profit. To calculate the price movement of a real position, substitute its actual entry price and quantity. A position entered late in the advance has a different starting point from the 24-hour reference. A position that has been partly closed also needs its remaining quantity checked before the next calculation.

For a second size check, 1 XAU at the captured last price represents 4,044.94 USDT, ten times the notional of the 0.1 XAU example. Copying a price into a calculator while overlooking the quantity changes the amount being evaluated. Read the quantity unit before typing the number, particularly when comparing an XAUUSD news quote with an XAUUSDT position.

The same method can test an outstanding order without choosing a new trade. Write down its own limit price and requested XAU quantity, then multiply them. Compare that result with the remaining position's quantity and the original purpose of the instruction. Keep the filled amount separate from the amount still waiting to execute.

Last, mark and index are separate observations

The Bitget snapshot contained more than a last trade. Alongside 4,044.94 USDT last, it showed a mark price of 4,044.68 and an index price of approximately 4,042.474. These fields are explicitly named in the market response. The fact that all are near 4,045 does not make the values interchangeable when checking a saved order condition.

The arithmetic gaps at the snapshot are small in price units: last minus mark equals 0.26 USDT, and mark minus index is approximately 2.206 USDT. For the hypothetical 0.1 XAU quantity, multiplying those gaps gives 0.026 USDT and approximately 0.221 USDT respectively. These examples show the effect of selecting a different field; they do not establish how an account's order is configured.

Open the order detail and read its stated trigger basis if one is present. Record the basis beside the trigger value, rather than comparing the trigger with whichever large price appears first on the market screen. If the condition's wording is unclear, keep the existing instruction and its record available while checking the product's order information.

The response also showed bid 4,044.63 and ask 4,044.64, an arithmetic difference of 0.01 USDT. Those quotations are a captured pair of fields. They do not demonstrate the execution price available for a particular order quantity, and this article does not infer an execution history from the fact that the last-price field differs from them.

Read the funding interval before extending a rate

The captured contract specification listed a funding interval of 4 hours. The ticker's funding-rate field was 0.000044, equivalent to 0.0044% when expressed as a percentage. Keep the rate and interval visible as separate inputs when checking an existing position's next funding record.

For illustration, applying that decimal rate to the hypothetical 404.494 USDT notional gives 404.494 × 0.000044 = approximately 0.0178 USDT. This is an arithmetic illustration using the captured rate and last-price notional. It does not identify an actual debit, credit, settlement value or payment direction for a reader's account.

Do not multiply this observation into a daily or annual income claim. The opened response contains one captured rate, while an account's funding record is the place to verify an actual settled amount. The funding-rates board is a separate reader tool; the calculation above remains tied to the named XAUUSDT observation and its 20:46 SGT capture.

Review orders left at earlier price levels

1. Open the existing Bitget XAUUSDT position and copy its remaining XAU quantity and entry price into your notes.
2. Open the related outstanding orders and compare each remaining order quantity with that position; read any trigger basis before comparing prices.

Start with the existing position record. Confirm XAUUSDT or the actual symbol held, the venue, direction and remaining XAU quantity. Put the real entry price beside the current quotation for that same instrument. Use the 24-hour reference only when your question is the contract's reported daily change.

Then read every outstanding instruction associated with the position. Note whether it opens exposure or closes some of the position, its quantity, its price and its current status. An order submitted while reading the earlier $3,950 story still needs its own record checked; the new $4,050 headline cannot tell you whether it filled.

If an order has a trigger, compare its trigger basis with the matching price field. If the position has been reduced, compare the order's remaining size with the current position size. Save the existing order details before changing an instruction whose original purpose you can no longer reconstruct.

Quick answers about the gold report

Is the 3.5% move Bitget's reported change?

No. Odaily attributed 3.5% and $4,051.26 to Gate's XAUUSD. The independently opened Bitget XAUUSDT response reported 3.025% and 4,044.94 USDT at a later capture. Cite the venue, instrument and time with each number.

Does the public contract response confirm my account can use it?

The response confirms the public XAUUSDT product fields captured in this run, including perpetual type, USDT margin support and normal status. It contains no personal account eligibility result. Check the product shown in your existing account before interpreting its position or order records.

What remains unconfirmed about the rally?

The opened sources do not establish a specific cause for the reported 3.5% advance, a continuous path between the two venue observations, or how long the new level will hold. The next useful evidence for an existing position is its own current quotation, order status and settled account record.