Question 1

Why does the bot tutorial mention StarkWare when the XNOVA token is on Ethereum?

Accepted Answer

XNOVA’s business page and official announcement point to the Ethereum contract 0xdB8ad3c6D7F9F364d59af9A62C3139cF5C6bE88E. StarkWare appears in the bot tutorial’s network-switching step, so the two describe functions at different layers. The November 2023 tutorial described a path for trading on the StarkWare network. It does not mean that XNOVA transfers on Ethereum are gas-free.

Question 2

What order types and trading pairs did the 2023 bot tutorial support?

Accepted Answer

The official tutorial of November 26, 2023 described switching to the StarkWare network and using the MARKET-BUY and MARKET-SELL features. At that time, the announcement listed five pairs: ARB, BTC, ETH, USDT, and MATIC, each against USDC. This is a historical feature scope, not a guarantee that all of those pairs remain available.

Question 3

How was XNOVA initially issued, and how does burn change supply?

Accepted Answer

At construction, the contract mints 10,000,000 XNOVA to the owner, and the token uses 18 decimals. The complete implementation has no public external minting entry point; the initial issuance should also not be treated as the remaining supply after burns. When a holder calls burn(amount), it destroys that holder’s corresponding balance and reduces totalSupply; insufficient balance causes the call to fail. An ordinary transfer between addresses only moves balances and is not a call to this burn function.

Question 4

How should the XNOVA contract’s fee units and adjustment ceiling be understood?

Accepted Answer

The code uses 1,000 to represent 100%, so the initial standardFee value of 300 represents 30%. A nearby 4% comment cannot replace the actual assignment; these values describe code initialization, not the current fee. When the owner uses updateStandardFees, both fee components must be greater than 0 and their total cannot exceed 200, or 20%; disabling fees uses a separate disableFees switch. Fee logic runs only in the main branch for non-exempt transfers involving a registered AMM pair and not an internal swap.

Question 5

Does turning off tradingEnabled block every XNOVA transfer?

Accepted Answer

No. The branch that requires tradingEnabled applies only when the transfer is non-exempt, either side is a registered automated market maker (AMM) pair, and the contract is not performing an internal swap. That branch also checks the enabled time or whitelist condition. The main branch is bypassed if either side is fee-exempt, disableFees is enabled, or the recipient is the router. The trading switch therefore is not a universal pause button for all ordinary transfers.

Question 6

What are the per-trade buy and sell limits, and are they wallet holding limits?

Accepted Answer

The code defaults to a 200,000-token maximum buy and a 50,000-token maximum sell. The owner can set the buy limit from 50,000 to 300,000 and the sell limit from 25,000 to 200,000; these are code parameters and adjustable ranges, not current settings. The limits apply only in the stated main branch for non-exempt transfers involving a registered AMM pair and not an internal swap, and they test the pre-fee transaction amount. They limit an individual buy or sell, not total wallet holdings.

Question 7

How is the trading delay assessed, and does it restrict every transfer by default?

Accepted Answer

The delay switch defaults to off and the duration parameter defaults to 15 minutes; the owner can adjust the switch and duration separately. Therefore, 15 minutes should not be read as an interval that every transfer must always observe. After a transaction enters the restricted AMM main branch, if the delay is enabled and the relevant address is not whitelisted, a buy checks the recipient’s and a sell checks the sender’s last transaction time. A record of 0 or an elapsed interval allows the transaction and updates that address’s record.

Question 8

Does adding an address to the whitelist also change its fee treatment?

Accepted Answer

Yes. When the owner calls whitelist(address, bool), it sets that address’s whitelist flag and fee-exemption flag to the supplied value together; setting it to false removes both flags together. Fee exemption can also be changed through a separate function. Since an exemption at either end makes a transaction bypass the main branch, a whitelist operation can affect both fees and transaction restrictions in that branch; this does not establish that any particular address is currently exempt.

Question 9

Is the blacklist handled the same for positive-value and zero-value transfers?

Accepted Answer

No. For a positive-value transfer, the contract checks both sender and recipient before entering its fee and trading-limit branches; either side being blacklisted causes failure, including for a fee-exempt transfer. The owner can set blacklist entries individually or in batches. A zero-value transfer instead calls the parent transfer and returns before the later blacklist check. Sender and recipient must still meet baseline requirements such as being nonzero addresses.

Question 10

When are fee tokens accumulated by the contract swapped?

Accepted Answer

The code’s default swap threshold is 25,000 tokens, which the owner can adjust. Only after a transaction enters the AMM main branch governed by the fee rules, and the contract’s token balance reaches that threshold, does it continue to test whether a swap can occur. The sender must also not be a registered AMM pair, and the contract must not already be swapping. Reaching the threshold alone is therefore not an independent immediate trigger, nor does every buy cause a swap.

Question 11

Who receives the proceeds of fee swaps, and which balances are handled when fees are disabled?

Accepted Answer

ETH obtained from swapping fee tokens is sent to the code-designated revenuewallet and treasurywallet; no logic is set to distribute it automatically to all XNOVA holders. The two swap amounts use nested integer division, so they cannot be described as precisely proportional at every fee rate. When the owner calls updateDisableFees(true), it first performs balance cleanup, transferring XNOVA and ETH held by this contract to the owner, then sets fees to disabled. This concerns the contract’s balances only; it does not let the owner withdraw assets from every user wallet.

Question 12

Which addresses are recognized as AMM pairs, and can the original pair be deregistered?

Accepted Answer

The constructor creates an XNOVA/WETH pair through the Uniswap V2 factory and registers it as an AMM pair. The owner can set AMM-pair flags for other addresses, but the setter forbids changing the original uniswapV2Pair registration. These flags determine whether a transaction involves an AMM pair; together with fee exemption and internal-swap status, they determine whether the transaction enters the main branch containing the trading switch, limits, and fees.

XNOVA ($XNOVA) Price

Price of XNOVA ($XNOVA) Today in USD

Fear & Greed Index

About XNOVA ($XNOVA)

Use Cases and Features

Supply and Issuance Mechanism

Frequently Asked Questions About XNOVA ($XNOVA)