Question 1

How was BRETT's initial issuance accounted for, and is there scheduled unlocking or minting?

Accepted Answer

The contract fixes the supply at 69,420,000 BRETT with 9 decimal places and credits the entire amount to the deployer at deployment. The complete implementation has no interface for scheduled unlocking or later minting; this fixed supply is not the same as real-time circulating supply.

Question 2

What is the difference between an allowance and the amount of BRETT actually received?

Accepted Answer

approve sets the amount a spender may use; it does not immediately transfer BRETT. When the spender calls transferFrom, the allowance is reduced by the full requested transfer amount, and the transaction reverts if the allowance is insufficient. The recipient's actual amount also depends on whether that transfer triggers the contract's token charge, so an approved amount cannot be treated as the received amount.

Question 3

When do the source-code buy and sell charges switch from the initial tier?

Accepted Answer

The code sets both initial buy and sell charge parameters to 13% and both final parameters to 1%; the final parameters are selected only when the buy count is strictly greater than 13. This describes code rules, not a current rate. The count rises only in the specified buy branch where both parties are not the owner, tokens come from the designated pair, the recipient is not the router, and the recipient is not excluded. The charge is calculated before the count is increased, so reaching 13 does not immediately trigger the lower tier.

Question 4

Can a direct BRETT transfer between wallets also have tokens deducted?

Accepted Answer

Under this contract's transfer logic, if neither sender nor recipient is the owner, a charge is first calculated using the buy tier; an ordinary wallet-to-wallet transfer can therefore be covered. The recipient receives the requested amount less the charge, and the deducted BRETT goes to the token contract balance. The name of an exclusion-list variable alone does not establish that every transfer is exempt.

Question 5

Which purchases are subject to the initial 1,388,400 BRETT transaction limit?

Accepted Answer

These are historical source-code rules. The code initially sets the transaction limit to 1,388,400 BRETT. It checks whether a requested purchase exceeds that limit when neither party is the owner, tokens are sent from the designated pair, and the recipient is neither the router nor excluded; an excess reverts. This is not a permanent limit applied uniformly to all transfers, and the owner can raise it to the fixed total supply through removeLimits. These administrative calls require owner authority before ownership is renounced; this does not establish the current owner state or that the calls remain available.

Question 6

Why can receiving BRETT fail even when the post-charge balance appears within the limit?

Accepted Answer

These are historical source-code rules. The wallet-limit check uses the recipient's previous balance plus the full requested amount, rather than the net amount received after the charge. The initial wallet limit is 1,388,400 BRETT. Where neither party is the owner, it is checked in the relevant purchase branch and in the transfer branch where the recipient is not the pair and is not excluded. A transfer can therefore revert even if the net received amount appears within the limit; removeLimits can also change that limit. These administrative calls require owner authority before ownership is renounced; this does not establish the current owner state or that the calls remain available.

Question 7

Does removeLimits also remove charges and list restrictions?

Accepted Answer

No. This owner-only function sets both the transaction and wallet limits to the total supply. It does not alter charge parameters, clear the bots list, or mint tokens; the function's presence does not show that it has been executed.

Question 8

What special restriction applies to contract addresses receiving BRETT just after trading opens?

Accepted Answer

openTrading records the opening block. In the specified purchase branch—tokens sent from the designated pair, recipient not the router or excluded, and neither party the owner—the recipient address must have zero code size if the current block number is less than the opening block plus 3. This applies to the opening block and the next two blocks, not as a permanent ban on contract addresses receiving BRETT.

Question 9

How does the bots list affect BRETT transfers?

Accepted Answer

These are historical source-code rules. When neither sender nor recipient is the owner, the contract requires that neither address be marked in the bots list; otherwise the transfer reverts. The code lets the owner add markings in batches through addBots or remove them through delBots, and exposes isBot for checking. These authority rules do not establish that any particular address has been listed. These administrative calls require owner authority before ownership is renounced; this does not establish the current owner state or that the calls remain available.

Question 10

Under what conditions are accumulated charged tokens automatically swapped for ETH?

Accepted Answer

In a transfer path where neither party is the owner, all of these must hold: no swap is in progress, the recipient is the designated pair, swapping is enabled, the contract's BRETT balance is strictly above the code threshold of 694,200, and the buy count is strictly above 30. The swap amount is the smallest of the current transfer amount, the contract token balance, and the per-swap cap of 694,200 BRETT. Reaching the threshold alone does not guarantee an immediate swap.

Question 11

Is ETH obtained through automatic swapping distributed to BRETT holders?

Accepted Answer

This implementation does not distribute that ETH by token holdings. The automatic swap follows a BRETT-to-WETH route to obtain ETH, which first enters the token contract. If the contract then has an ETH balance, its entire ETH balance is sent to the fee wallet, which is set to the deployer at deployment. The transferred asset is all ETH in the contract, not only ETH newly produced by one swap.

Question 12

How does openTrading establish BRETT liquidity, and who initially receives the LP tokens?

Accepted Answer

Only the owner can call openTrading, and trading must not already be marked open. The function creates a BRETT/WETH pair through the specified Uniswap V2 router, adds liquidity using BRETT and ETH held by the token contract, and sets the LP recipient to the owner. It then enables swapping and trading flags and records the opening block. This initial allocation rule alone does not prove that LP tokens were later locked or burned.

Brett (ETH) (BRETT) Price

Price of Brett (ETH) (BRETT) Today in USD