RIPSTACKDocsWebsite

$STACK transparency

Security & controls

$STACK supply limits, Agent ID authorization, refund reserves and permanent LP burning, with administrative rights stated explicitly.

On this page

A defined supply ceiling

The $STACK contract design caps issuance at 5.55 billion tokens. The token is issued once at initialization: 5% to the Origin vault and 95% to shared sale inventory. There is no additional mint function. Native token burns reduce total supply.

Agent ID authorization

Share purchases and Origin redemption check the official Binance / SPACE ID registry directly on BNB Chain. The registered handle and its token owner must match the participating wallet. A valid voucher alone cannot admit an unregistered wallet.

Vouchers still bind eligibility, amounts and transaction limits. Registry ownership identifies an eligible wallet; it does not prove which application or person operates it. Refunds and vested claims remain available under their existing terms without a new identity check.

Fully reserved refunds

Each purchase is 100% refundable for 30 days from its purchase timestamp, provided the pool has not opened. The refund burns the entire allocation, including tokens already received and any Stack bonus, and returns the full USDT payment in the same transaction.

If a purchase reaches 30 days before opening, its refund and token rights expire. After cancellation and token burning, only its payment becomes owner-withdrawable to the fixed treasury for $RIPS buybacks. Active refundable payments cannot be withdrawn through this function. Refunds close at pool opening. See the refund terms.

Permanent LP burning

Opening and subsequent share purchases create their protocol LP directly at the dead address in the same transaction. Those LP tokens cannot then be redeemed by the administrator to remove the underlying liquidity.

Funds collected before a pool exists are not burned LP. LP burning must be checked against the actual pool and transaction receipts; it does not prevent trading losses or establish a guaranteed price floor.

What runs automatically

The purchase reaching 10,000 active paid shares opens the pool, settles the 80% liquidity / 20% treasury split and creates LP at the dead address in the same transaction. Later purchases use the same settlement. Refunds and vested claims are initiated by participants, without owner approval. Token amounts unlock with time; sending a claim still requires a transaction.

Owner controls

Treasury withdrawals
Regular settlement sends 20% to the fixed treasury. Neither route permits withdrawing active refundable payments; ownership transfers do not change the recipient.
Origin redemption amount
The distributor owner can adjust the RIPS requirement. A differently priced quote must be replaced and reviewed before redemption.
Purchase pause
A purchase pause does not prevent eligible refunds or vested claims.
Fixed contract code
The contracts are deployed directly, without proxies or implementation upgrades. Owner permissions are limited to the functions defined in the deployed code.
Renouncing authority
Ownership can be renounced separately on the sale, Origin vesting vault and redemption distributor. Renouncing the distributor fixes the redemption cost permanently. Quote signers remain active.
Token and pool
The token and liquidity manager have no upgrade or owner-withdrawal function. Only the configured manager can enable token transfers, once, during successful pool opening.

Direct deployment

The sale and Origin vesting vault have no proxy or upgrade function. Minting, refunds, vesting and pool settlement use the deployed contract code. A new version would require a new contract address.

Direct sale contract inheritanceSolidity
StackPublicSale.sol · line 22
contract StackPublicSale is EIP712, Ownable2Step, ReentrancyGuard, BinanceAgentIdGate {
Source SHA-256 b50919171c4b96cc

Renouncing ownership removes owner-only controls for that contract. Agent ID vouchers still depend on the authorized signer; renunciation does not remove that role.

Verify the implementation

These are $STACK launch requirements. Contract addresses, verified source, role holders and transaction records must establish how they are enforced before participation opens. See Verify the activity for the records to check.