EN
All articles
NFTAMA Blog

How NFTAMA Allocates AMA2 Rewards by Safe Weight

How NFTAMA Allocates AMA2 Rewards by Safe Weight

Follow NFTAMA’s documented AMA2 calculation from the cycle pool to an individual allocation, with a worked example and a clear comparison with the separately identified BNB reward flow.

NFTAMA’s published AMA2 model begins with an amount made available for distribution and then uses safe weight to divide that amount. Safe weight determines a user’s proportional share; it does not create or define the pool. The White Paper expresses the AMA2 calculation through S, r, a 9% base deduction and portfolio weight relative to total system-user weight. It does not categorize the economic source of S. Our Quick Start also identifies BNB as a safe reward, but the cited materials do not define a parallel BNB pool or allocation formula, so the two assets should be considered separately.

AMA2 and BNB are separate reward flows

There are two parts to a reward model: the amount made available and the rule used to allocate it. NFTAMA documents the allocation process for AMA2. It defines the available amount as S but does not classify S as safe-sale proceeds, upgrade or minting payments, platform fees or a particular reserve.

For BNB, the Quick Start confirms the reward asset but does not establish that it follows the AMA2 formula. Keeping the assets separate prevents the AMA2 weight calculation from being applied where no equivalent BNB rule has been published.

AssetPool definitionAllocation basisDeductionPublished scopeSource
AMA2The White Paper defines S as the AMA2 available for distribution.Counted portfolio weight divided by total system-user weight.9% base distribution deduction before the user share is applied.The White Paper states a fixed total supply of 141,000,000 AMA2. A fixed total supply does not make the cycle amount fixed.White Paper PDF
BNBThe Quick Start identifies BNB as a safe reward.A separate allocation formula is not defined in the cited materials.No BNB reward deduction is specified in the cited materials.The pool source, cycle settings and settlement rules are not defined by the cited pages. The AMA2 formula should not be extrapolated to BNB.NFTAMA Quick Start

The AMA2 formula, one layer at a time

First, S is multiplied by r to produce Q, the AMA2 assigned to the cycle. The NFTAMA White Paper provides access to the project documentation, while the White Paper PDF contains the formula and variable definitions.

Next, the formula applies the base distribution deduction f = 0.09. The resulting Qnet is the amount used for proportional allocation. This deduction is part of the AMA2 distribution calculation; it is not presented as a safe-purchase, marketplace or blockchain network fee.

The user’s percentage is then calculated from total portfolio weight. Ai represents the user’s counted weight rather than automatically referring to one safe. Asum represents the corresponding total across system users. Multiplying Qnet by this percentage produces Ri.

The formula explains allocation rather than setting a permanent payout. S, r and total system-user weight can change, so the resulting AMA2 amount can change as well.

The documented AMA2 calculation has four layers: 1. Cycle amount: Q = S × r 2. Net distributable amount: Qnet = Q × (1 − 0.09) 3. User weight share: Di = Ai ÷ Asum 4. User allocation: Ri = Qnet × Di S is the AMA2 available for distribution. r is the share of S assigned to the cycle. Ai is the user’s counted portfolio weight, Asum is total counted user weight in the system, and Ri is the resulting AMA2 allocation.

How changing variables affect an allocation

Assume a hypothetical cycle in which S is 100,000 AMA2, r is 10%, a user’s portfolio weight is 500 and total system-user weight is 50,000. These invented values demonstrate the calculation; they are not current NFTAMA parameters or a projection.

If the user remains at 500 but total system-user weight doubles to 100,000, the user’s share falls from 1% to 0.5%. The illustrative allocation falls from 91 to 45.5 AMA2 because the denominator changed.

The pool variables can change the result independently. If the weight share remains 1% but hypothetical S falls to 80,000 AMA2 while r remains 10%, Qnet becomes 7,280 AMA2 and the illustrative allocation becomes 72.8 AMA2. A constant weight share therefore does not imply a constant token amount.

  • Cycle amount: 100,000 × 10% = 10,000 AMA2.
  • After the 9% deduction: 10,000 × 91% = 9,100 AMA2.
  • Portfolio share: 500 ÷ 50,000 = 1%.
  • Illustrative allocation: 9,100 × 1% = 91 AMA2.

What contributes to portfolio weight

NFTAMA’s product documentation identifies class, quality, level, owned-safe age and upgrades as factors that can affect safe or portfolio weight. These factors do not form separate reward pools. They influence AMA2 allocation through Ai, the numerator in the user-share calculation.

The guide to virtual safes and portfolio weight explains these attributes in more detail. Increasing portfolio weight can increase a user’s share if other variables remain unchanged, but it does not set S, r, total system-user weight or AMA2’s external market value.

  • Class and quality can strengthen a safe’s weight.
  • Levels and AMA2-funded upgrades can alter weight.
  • Owned-safe age stages can strengthen weight under the published product rules.
  • The weight of individual safes contributes to Ai, the portfolio-weight term in the formula.

An allocation is not automatically a withdrawn balance

The formula moves from a gross cycle amount to a net distributable amount and then to an individual AMA2 allocation. Accrued, claimable, internal, converted and withdrawn balances are separate operational states and should not be treated as interchangeable.

The formula itself does not define claim timing, conversion terms, withdrawal processing or network costs. Those conditions belong to the applicable account transaction flow. AMA2’s market price and liquidity can also affect its external exchange value without changing the weight-share equation.

What the blockchain shows—and what the platform calculates

The AMA2 address published by NFTAMA points to a BEP-20 contract that BscScan lists with exact-match verified source code. This confirms the contract identity and published-source status. Blockchain records can also confirm specific activity when the relevant address or transaction hash is known.

Contract verification does not reproduce the complete reward calculation. It does not determine the cycle’s S or r value or show how every user’s counted portfolio weight was established.

The White Paper PDF describes an architecture that combines blockchain components with backend processes. Transfers can produce blockchain records, while weights, histories, rules, queues and distribution calculations also involve the platform backend. Check NFTAMA news and updates for dated announcements about current mechanics.

  • BscScan can display the AMA2 contract and transactions involving known addresses.
  • Contract verification does not identify S, select r or calculate portfolio weight.
  • NFTAMA’s backend maintains weights, histories and rules used in the allocation process.
  • S, r, the 9% deduction, portfolio weight and total system-user weight all affect the calculated result.

FAQ

How is an NFTAMA AMA2 reward share calculated?

The White Paper calculates the cycle amount as S × r, applies the 9% base distribution deduction and then multiplies the result by the user’s weight share. That share is Ai ÷ Asum: the user’s counted portfolio weight divided by total counted user weight in the system. The result is an AMA2 allocation, not a guaranteed monetary return. See the published formula.

Why can my AMA2 allocation change when my weight stays the same?

Your percentage depends on both your portfolio weight and total system-user weight. If the system total rises while your weight remains unchanged, your percentage falls. Your token allocation can also change if S or r changes, even when your percentage stays constant. The White Paper defines these variables.

Does NFTAMA use one safe’s weight or my total portfolio weight?

The AMA2 formula uses Ai, the user’s total counted portfolio weight. Individual safe attributes contribute to that total. One safe’s weight equals your portfolio weight only if it is your sole counted safe. The Virtual Safes guide explains the relevant asset attributes.

What is the 9% deduction in the AMA2 formula?

The White Paper defines f as 0.09 and deducts it from the AMA2 cycle amount before applying each user’s weight share. It is a distribution deduction, not a safe-purchase price, marketplace charge or blockchain network fee. The cited document does not assign a recipient or use to that deduction. Review the distribution formula.

Can NFTAMA rewards be verified on BNB Smart Chain?

The published AMA2 contract and transactions involving known addresses or hashes can be inspected on BNB Smart Chain. BscScan identifies the contract as the AMA2 BEP-20 contract and lists its source code as exact-match verified. The White Paper says weight and distribution calculations also involve NFTAMA’s backend, so the complete allocation cannot be reconstructed from the token contract alone.

NFTAMA’s documented AMA2 model is a pool-first, share-second calculation. S and r determine the cycle amount, the 9% base deduction produces the net distributable amount, and portfolio weight divided by total system-user weight determines each user’s share. BNB is separately identified as a safe reward and should not be assumed to use the AMA2 formula. This distinction helps readers interpret safe weight and AMA2 allocation examples without treating them as fixed payouts.

Before acquiring or upgrading a safe, review the NFTAMA Quick Start for the current overview of safes, epochs, acquisition and onboarding.

Sources

Other news

Your first safe is waiting

Sign-up takes a minute, and a demo safe is a gift.