Atlas FAQ

Open the official Atlas System website (atlas-system.tech (https://atlas-system.global)), connect MetaMask on the BNB Smart Chain network, and confirm the wallet connection. The first wallet connection creates your Web3 profile in the system. Important: use only the official domain and never share your seed phrase.

No. Login and registration happen through a Web3 wallet, without email or password.

In Web3, an account is defined by the wallet address. So the system sees not a login and password, but the public address you connected with and use to sign actions.

Yes, if the participant has MetaMask Mobile.

If you came by invitation, use the referral link before your first connection, because after registration the inviter cannot be changed.

Check that MetaMask is installed, the selected account, the BNB Smart Chain network, the site permissions in the wallet, and pop-ups. Then refresh the page and reconnect.

Reconnect MetaMask, check the selected account, the BNB Smart Chain network, and the site permissions in the wallet.

Check the official domain manually and don’t follow links from private messages. If the link differs from the official one by even a single character, do not connect your wallet.

If the wallet is already registered, changing the inviter is not possible.

Atlas System uses the MetaMask wallet.

You need a wallet on the BNB Smart Chain (BSC) network. If you use USDT, make sure it is USDT on the BEP-20 network.

BNB is needed to pay the BNB Smart Chain network fee when confirming transactions.

A small amount for gas (about $5). The exact fee changes on the network, so check the gas estimate in MetaMask before any action.

Use USDT on BNB Smart Chain (BEP-20) only. Sending through another network may make the assets unavailable to the intended Atlas address and can require specialist recovery steps, if recovery is technically possible at all.

It is the main recovery key for your wallet. It must never be shared with anyone, including support.

No. Atlas does not store private keys and cannot restore access to a wallet. The wallet owner is responsible for keeping the seed phrase safe.

Rely on the blockchain data and the tx hash; the dashboard interface may update with a delay.

In MetaMask, under the account name. The address can be copied and used to verify transactions.

Signing a message usually confirms wallet ownership and login to the dashboard. A transaction with a fee is only needed for blockchain actions: creating a cycle, Claim, and other on-chain operations.

Don’t sign the transaction if you don’t understand what it does. Verify the site address, the contract address, and the instructions, and contact support before confirming.

A cycle is a scenario of interaction with the Atlas smart contract chosen by the participant, with a set amount, term, and calculated delta. It is not a bank deposit and not a guaranteed investment return.

Connect your wallet, go to the cycles tab, choose a cycle and amount, then confirm the transaction in MetaMask.

The current minimum Support Amount is 10 USDT. Check the Personal Dashboard before confirming because product parameters may be updated.

A cycle is considered active only after the transaction is successfully confirmed on the blockchain and the action is reflected in the smart contract/dashboard.

The transaction may still be pending, or the Personal Dashboard may need time to update. First verify the Tx Hash on BscScan and confirm the wallet and BNB Smart Chain network before creating another cycle.

Check your BNB for gas, the network, your USDT balance, and the error on BscScan. Then contact support with the transaction hash. Don’t send private data to support — only the public address and tx hash are needed.

Once the transaction is confirmed on the blockchain, the action cannot be canceled.

Yes, the product rules allow several active or sequential cycles.

An active cycle cannot be topped up. You need to create a new cycle.

Yes, an experienced user can interact with the smart contract directly if the contract address is officially published. This method requires technical understanding and increases the risk of user error.

A blockchain transfer cannot be cancelled after confirmation. Recovery may be impossible and depends on the destination address, so verify the official Contract Address Registry, network and token before confirming.

Daily Flow V2 is the current contract for newly created Daily Flow cycles. Daily Flow V1 is a legacy contract retained for existing cycles and historical on-chain verification. Always verify the complete address in the official Contract Address Registry.

Atlas has short fixed Smart Cycles and the long-term Daily Flow. Each cycle has its own amount, term, calculated delta, and Claim rules.

A 10-minute test cycle with no delta, used to check the mechanics. Contract Test is only for checking the interface/contract and should not be used as an example of returns. Contract Test can be used only once.

A fixed 1-day cycle with a calculated delta of +0.3% (this is a calculation model, not a guarantee).

A fixed 5-day cycle with a calculated delta of +2% (this is a calculation model, not a guarantee).

A fixed 10-day cycle with a calculated delta of +5% (this is a calculation model, not a guarantee).

A fixed 20-day cycle with a calculated delta of +12% (this is a calculation model, not a guarantee).

A fixed 30-day cycle with a calculated delta of +22.5% (this is a calculation model, not a guarantee).

A long-term 200-day cycle with a daily calculated accrual model.

No. Creating a Smart Cycle is not an investment transaction and does not guarantee the return of the Support Amount or any Delta. Availability depends on the smart-contract rules, participant activity and liquidity.

The received aid depends on the rules of the chosen Smart Cycle, the state of the smart contract, available liquidity, network fees, and the user correctly executing the transactions.

Claim is the on-chain action used to request assistance that the smart contract currently shows as available under the selected Smart Cycle rules.

After the chosen cycle’s term ends or when the Daily Flow conditions are met — when the interface shows an available amount to receive.

Claim may send the amount currently available under the selected cycle rules. Claiming the Support Amount or Delta is not guaranteed and depends on the contract conditions and available liquidity.

To the connected wallet of the participant who took part in the cycle.

Yes, to pay the network fee when sending the Claim transaction.

Most often the issue is insufficient BNB for the fee, a network error, or the payout not yet being available.

A repeat Claim is possible when the interface shows an available amount to receive.

Check the transaction on BscScan and wait for confirmation or a failed status.

Yes. After receiving aid, you can immediately create a new cycle.

If the Claim button isn’t showing, check the selected wallet, the BNB Smart Chain network, the cycle status, the completion term, and the dashboard sync. Then check the contract/transaction data on BscScan.

Claim Assistance is a transaction on BNB Smart Chain. To process it, the blockchain charges a small network gas fee. The fee can be paid: • directly in BNB; • in USDT, if the connected wallet supports Gas Station or a similar feature. When paying in USDT, the wallet automatically converts the required amount to cover the gas fee. The payment method and exact fee are displayed in the wallet before the transaction is confirmed. The network fee is not charged by Atlas System and is separate from the Platform Fee, which is calculated independently.

Partner Program access is activated automatically after the first qualifying Smart Cycle with a Support Amount of 10 USDT or more.

After activation, the referral link appears in Personal Dashboard → Partner Program → My Team.

Partner Rewards are calculated from Delta generated within the Partner Structure, subject to Partner Status, qualification and compression rules. They are not guaranteed income and are not calculated from the Support Amount itself.

For Lockup Flow, the applicable Partner Reward is accrued when the invited participant creates a Smart Cycle. An amount above 10 USDT is sent automatically after formation; smaller amounts accumulate in Partner Balance until the transfer threshold is reached. For Daily Flow, 20% of the Partner Reward is credited when the cycle is created, and the remaining 80% is paid in equal parts over the 200-day cycle. Use Accrual History and Partner Wallet to verify actual accruals and transfers.

Compression distributes the applicable percentage difference through the Partner Structure according to Partner Status. If a lower participant has an equal or higher percentage qualification, the upper participant does not receive a Partner Reward from that structure segment.

These are the participants the partner invited directly.

These are the levels of participants below the first line. Atlas declares unlimited structure depth.

Status depends on personal active volume, first-line volume, structure depth, and status requirements.

Matching Reward becomes available from Master status and may be calculated from Partner Rewards of personally invited participants when the current status and qualification conditions are met.

A recorded Partner Reward can be withdrawn when it is available in Partner Program → Partner Wallet under the active dashboard and smart-contract rules.

There is no automatic reinvestment mechanism. After a Partner Reward reaches the connected wallet, the participant may independently use available funds to create a new Smart Cycle.

The result may reflect Partner Status, compression and the 10% Platform Fee applied to Partner Rewards. Daily Flow also contributes to status qualification at a 0.5 coefficient. Compare Accrual History with the current Partner Program rules.

No. Partner Rewards depend on the current program rules, Partner Status, qualification, structure activity and the underlying Delta.

Yes. Atlas may publish changes as the ecosystem develops. Treat a change as active only after it appears in an official notice, the Personal Dashboard or the applicable smart-contract/interface rules.

Daily Flow cycle volume is counted with a coefficient of 0.5, while short-term Smart Cycle volume is counted with a coefficient of 1.0. The coefficient affects qualification volume only; it does not change the Daily Flow daily assistance rate or the Partner Reward percentage.

No. The Unified Partner Structure preserves referral relationships in one base tree, but each partner model applies its own qualification, volume, placement and reward rules. The same volume is not automatically counted in several programs.

No. The official Atlas pages currently mark these models as planned or Concept Stage. Their final mathematics, qualifications, limits, contracts and launch notices must be published before they are treated as active.

There are Start, Builder 1-7, Master 1-7, and the top statuses Strategist, Ambassador, Director, Executive.

Partner Status determines the applicable Partner Reward percentage qualification and, from Master status, the possible Matching Reward percentage under current rules.

You need to meet the requirements for personal active volume and structure according to the status table.

You need to meet higher requirements for personal, first-line, and deep volume.

You need to meet higher requirements for personal, first-line, and deep volume.

Status may be recalculated based on the system’s current data: personal active volume, first line, deep volume, and activity period. If one of the parameters changes, the status may change under the program rules.

Status requires maintaining activity: personal active volume, first line, deep volume, and activity period.

DAO governance is a mechanism through which the community can take part in discussing and voting on important project matters.

The Personal Dashboard displays Voting Balance in the top bar, but this does not by itself mean that live proposals are available. Eligibility and voting weight will be determined by the rules published for an active proposal in the official governance interface.

Voting may concern project parameters, development stages, and certain system rules — if these matters are officially put to the DAO.

Cycle epochs appear in earlier conceptual materials and are not a current Smart Cycle 1 dashboard function. Use the active Personal Dashboard and the current official governance documents as the source of truth.

The public Atlas roadmap lists Governance for Q4 2026, and the official governance website is currently marked as under development. Voting Balance may be displayed in the Personal Dashboard, but it should not be treated as confirmation that live proposals are already available.

No. The correct wording: Atlas is not a full-fledged DAO, but uses DAO-inspired mechanics for certain community governance and voting functions.

No. Voting can only work within officially permitted topics. Security matters, smart contract operation, legal restrictions, and critical parameters may be outside the scope of voting.

Atlas cannot sign transactions for the participant or control the participant’s wallet. A confirmed Support Amount is handled by the applicable smart contract and liquidity mechanics defined by its code.

No. Private keys and seed phrases remain only with the wallet owner.

No. The seed phrase must never be shared with anyone.

The main risks are network errors, smart contract operation, human errors, choosing the wrong network, and the general limitations of Web3 infrastructure.

Don’t connect your wallet, don’t sign transactions, verify the official domain, and contact support.

Atlas should not be described as a classic investment with guaranteed income. It is a Web3 participation mechanic through a smart contract, where the user evaluates the rules, the calculation model, and the risks themselves.

Atlas may operate through a smart contract without a classic legal entity, but this does not remove the need for rules, risk notices, a data policy, disclaimers, and compliance with applicable requirements in different countries.

The user confirms the transaction in their own wallet and must verify the network, address, amount, and action. A blockchain transaction cannot be canceled after confirmation.

The official Atlas website and the documents published on it. Webinars, presentations, posts, translations, and partner materials are supplementary.

To help support assist you faster, send the wallet address, tx hash, network, a screenshot of the error, and a brief description of the problem right away.

Your seed phrase, private key, access codes, and full device data.

A tx hash is the public identifier of a transaction on the blockchain. With it, you can check the operation’s status, addresses, amount, network, and error on BscScan: https://bscscan.com/ (https://bscscan.com/)

The network has not yet confirmed the transaction, or the gas was too low. Pending does not mean lost funds; wait for the final success/failed status.

There may be insufficient gas, the wrong network, an insufficient balance, or a contract condition error.

Switch your wallet to the correct BNB Smart Chain network and refresh the page.

Support can check the tx hash, wallet address, network, transaction status, MetaMask error, and how the action is displayed in the dashboard. Support cannot cancel a confirmed transaction or restore a seed phrase.

Response time depends on the team’s workload and the complexity of the issue.

The webinar schedule is shown in your personal dashboard: language, topic, host, date, time, time zone, and a link to apply/join.

The first MetaMask connection.