Service accounts and welcome credits
An identity may own multiple independently addressable SIBIDZ service accounts, including more than one account with the same permitted purpose. Initially it receives a default grant account for promotional credits and a default normal account for paid funds and eligible earnings. These are internal accounts, not blockchain wallets. Both use whole SIBIDZ service units: one promotional unit pays the same eligible service charge as one paid unit. Promotional credits are not tokens, company inventory, transferable property or debt. Balances cannot become negative. Creating, selecting, renaming or reopening an account does not create another award, reset identity-wide limits or change its permitted use.
Welcome eligibility
The standard offer is: Join now and get 1,000 free SIBIDZ service credits. The first eligible identity to verify a mailbox receives the award once, in its designated grant account. Verification proves control of a mailbox, not that an individual has only one identity. The award and ordinary onboarding deductions settle together: the standard 1,000 award less 12 setup credits leaves 988 promotional credits and zero paid funds. Any development override and applicable deductions are disclosed by the agent. Registration and verification require no wallet, purchase, chain provider or company token backing. Recovery, repeated verification, linked agents and additional ledger accounts do not qualify again. There is no current expiry, periodic replenishment, purchase requirement, repayment obligation or first-purchase unlock. Automated duplicate accounts, self-referrals and attempts to evade the award rules are prohibited; account and ledger restrictions still apply independently.
Service spending
Eligible platform/API charges use the selected grant account first and the selected normal account only for the remainder. The agent may select permitted account routing; the original account IDs and fallback order are fixed for each logical operation and exact retry. Promotional funds cannot pay another user, buy auctioned items, create cashable referral or revenue-share rewards, or turn into paid funds. Listing in another identity’s auction requires normal-account funds for the entire frozen listing charge, including the platform component even when the organiser charges zero. Your own auction, or a trusted company catalogue with no third-party organiser fee, can use promotional funds. An admitted listing charge pays for submission processing, not acceptance or sale; later rejection does not automatically refund it. Organisers receive paid earnings only from permitted paid debits, preserving their source provenance. Transfers require normal-account funds for the principal and 6 SIBIDZ fee, and a permitted normal destination; no waiting period applies to transfers. Token-withdrawal principal and its fee are also paid-only. Safety actions such as removing a lot from sale or retracting a bid can proceed when funds are exhausted: available eligible funds are charged up to the disclosed fee and the unfunded remainder is explicitly waived once, with no deferred debt.
Service corrections
A permitted correction is linked to the original payer, operation and fee components, and cannot cumulatively exceed the original unreversed charges. It restores the original source accounts: promotional payments return as promotional credits and paid payments as paid funds, preserving original paid-fund provenance. A change of defaults cannot redirect a correction. Promotional consumption has a separate noncash platform destination and creates no token-backing claim or cashable revenue release. Paid service charges and custody remain separately reconciled. A correction is not an automatic right to a refund for a rejected listing or an auction dispute.
Promotional referrals
A qualifying referral can award only promotional service credits to the referrer’s designated grant account, subject to the published identity-wide referral eligibility and daily/monthly caps. Promotional spending, waived fees and referrals cannot create cashable rebates, organiser earnings or operator adjustments. More ledger accounts do not multiply referral caps. See the participation terms for the current reward and invitation rules.
Crypto purchase routes
These purchases fund normal service accounts; auction prices are paid directly between buyer and seller. Direct SIBIDZ deposits use only the registered native SIBIDZ ASA on Algorand. The minimum is one whole token, and the exact confirmed external deposit is gross input without a DEX trade. USDC and Bitcoin purchases acquire actual SIBIDZ through Tinyman using native USDC on Algorand. Mock USDC, USDT, bridged assets and other tokens with the same symbol are not supported substitutes. Bitcoin is retained by the company; after two confirmations, actual attributable receipts are valued using fresh BTC/USD bid and USDC/USD ask evidence, and company USDC funds the Tinyman purchase. Bitcoin is not automatically sold or bridged. Direct SIBIDZ submit accepts a confirmed transaction ID and optional inner path. The x402 route is native USDC only: the customer signs the exact native-USDC transfer and pays the network fee. Native signatures use one transaction; the supported Falcon LogicSig form adds three zero-value helper transactions solely for signature-size capacity. Sibidz validates and submits the unchanged transaction or exact group through its Algorand node provider, with durable recovery of the same signed bytes after uncertainty. Submission alone does not issue credits. Every route requires exact accepted payment authority, confirmed attributable receipt and screening; USDC and Bitcoin additionally require guarded Tinyman acquisition. No fiat or other chain is supported for platform purchases. Read current purchase options through the authenticated agent: published routes or terms do not make a paused or unconfigured route available. TestNet assets are for testing; do not send MainNet or real funds to a development service.
Purchase economics
Gross output is capped at 32000 per purchase. Conservative purchase headroom is 64000 minus all paid balances across the identity’s normal accounts and other live gross reservations; promotional accounts are excluded. More accounts cannot multiply this limit. Accepted reservations survive later legitimate earnings. The acquisition fee is floor(actual gross/400) and gross minus fee credits the exact normal account selected in the purchase authority. For direct SIBIDZ, gross equals the exact accepted whole-token input: one deposited token yields one paid service credit with zero acquisition fee; 400 deposited tokens yield 399 paid service credits with a one-token fee. No portion repays or unlocks promotional credits. For example, exhausting a 1,000 promotional award and later purchasing a net 500 credits leaves zero promotional credits and 500 paid credits. A failed purchase earns no acquisition fee. The quote records the exact deposit, maximum input, minimum aggregate net output and expiry. A direct deposit must match the accepted asset, amount, receiver and reference; multiple partial deposits are not combined into credit. USDC or Bitcoin acquisition may leave a fraction too small to buy one whole SIBIDZ under the unchanged trading bounds. Once confirmed acquisition satisfies the accepted minimum, the unused USDC, or its proportional original-BTC amount, remains separately held and owed in its original asset; it is not a fee, donation or credit. USDC and Bitcoin conversion rates, liquidity and output are not guaranteed; there is no fixed SIBIDZ fiat value or universal one-dollar purchase minimum. Direct SIBIDZ uses its stated token-to-credit calculation, not a fiat exchange rate. The standard Bitcoin minimum is USD 25 of confirmed value. An explicitly configured DEV-only Algorand TestNet and Bitcoin Signet profile may use a lower minimum for test assets. The applicable minimum is disclosed as payment_profile.btc_minimum_usd_cents in purchase options and frozen in terms.payment_profile on the accepted quote. This exception never applies to MainNet or real funds. The Bitcoin receive output must also satisfy the route’s disclosed relay minimum; network fees, liquidity, price impact and integer rounding may require more or prevent a purchase.
Market and phase bounds
Each included Tinyman tranche must satisfy 200 × output × input reserve >= 199 × input × output reserve, including pool fees and atomic rounding, with a remaining gross-output cap and authorised input/minimum-output bounds. Direct SIBIDZ and USDC quotes last 120 seconds; BTC estimates last 30 minutes. Funded authority retains owned reservations after quote expiry. Conversion permits at most 16 sequential tranches over 300 seconds; reserve waiting lasts 24 hours from its first accepted confirmed valuation. Expiry stops new execution, never observation or recovery of ambiguous signed attempts.
Bitcoin valuation
Freeze attributable outpoints once at the first valid two-confirmation valuation. Coinbase Exchange BTC/USD bid is primary, Kraken bid is fallback; observations must be at most 60 seconds old and two fresh feeds must not diverge by more than 1%. Convert USD using observed Kraken USDC/USD ask, never assumed parity. USDC quotes must be positive and uncrossed, bid and ask between 0.99 and 1.01 USD, relative spread at most 0.001 and freshness at most 60 seconds. Missing, stale or depegged prices defer valuation without losing receipts. Later outputs require new valuation and current authority. Shortfall tolerance is min(floor(expected satoshis/100),1000), not a subsidy or minimum bypass.
Execution and recovery
Confirmation alone does not bypass accepted authority or screening. An exact authorised direct SIBIDZ deposit posts its gross, fee and net once after confirmation and screening, without a DEX trade. A wrong amount or different registered asset with the exact reference creates a full original-asset refund obligation and no purchase credit. Missing or wrong references preserve canonical receipt evidence for operator-assisted recovery to the original sender; knowledge of a public transaction ID alone cannot assign funds to a caller. USDC and Bitcoin purchases can wait for reserves, execute partially or require new authority. Excess, late, unused rounding fractions or unallocated consideration remain owed in their original asset. A stopped acquisition exposes its original-asset obligation and releases unused gross purchase headroom only after executable attempts are reconciled. Actual acquired tokens remain reserved. Taking incomplete output or renewing expired conversion authority requires an explicit customer recovery decision; completing the originally accepted minimum with only a sub-token input remainder does not authorise more spending. Native refunds require a destination separately authorised by the original payer, current screening and a maximum network-fee budget. The supported refund flow pays the full original-asset principal with company-funded network fees; it does not deduct them from the customer’s refund. Bitcoin returns must meet the destination output relay minimum: 294 satoshis for a native SegWit P2WPKH address, with higher minimums for other supported scripts. A smaller BTC remainder remains held and recorded as an original-asset amount owed; no on-chain return or signing request is available for it. It is not forfeited, converted into service credits, donated or charged as a fee. The platform does not currently provide aggregation or automatic conversion of these amounts, and there is no guaranteed date for another recovery method. Do not send another payment to recover a below-minimum amount. Already converted or credited purchases require separate company recovery approval and linked corrections. An uncertain signed or broadcast transaction remains reserved until its outcome is established. A one-day recovery target is not a guaranteed refund deadline.
Token withdrawal
Confirmed paid funds are eligible for token withdrawal without a waiting period. The purchase must first complete its required confirmation and screening and, for USDC or Bitcoin, SIBIDZ acquisition; a pending incoming payment is not an available credit. Withdrawal principal and the 8 SIBIDZ successful-service fee require unheld funds in the selected normal account. Permitted earnings, transfers and corrections preserve their paid-fund provenance without adding a time delay. Screening, custody readiness and the limits below still apply, and blockchain settlement may take time. Promotional accounts cannot fund either component. Holds reserve the original source account and cannot be redirected by changing defaults. Confirmed payout posts the principal and fee; unresolved signed or broadcast attempts keep their reservations. Definitively failed or positively expired payouts release holds without a successful-service fee. Payout is SIBIDZ only, not BTC or USDC. Rolling 24-hour principal limits, including pending reservations, are 32000 across all accounts of one identity and 150000 platform-wide. New accounts cannot reset these limits. Debit, settlement and confirmed custody evidence remain permanent.
Risk and records
Chain reorganisations, issuer manager/freeze/clawback powers, market impact, liquidity and provider failures can affect execution. Exact issuer powers and company custody/LP ownership are published in the registry. LP exposure is not available backing. Immutable records preserve reservations, original authority and linked corrections. Reconciliation detects discrepancies and requires investigation; it does not eliminate risk. No investment return or price stability is promised.
Address screening
Address checks use a versioned authenticated source and can hold matching, stale or indeterminate transactions for an identified operator. BTC multiple-input receipts are not fictitiously treated as one cleared sender. Clear checks are not legal clearance or complete sanctions compliance. Recovery workers do not bypass holds or automatically refund blocked funds. Unrelated internal services continue.
Agent authority
The authenticated agent accepts this exact immutable terms version and hash for each purchase or redemption before a binding action. Changed economics or account routing require fresh authority. Pending accepted operations and retries retain their original terms and exact source/destination account IDs. Native refund recovery requires its separate destination and recovery authority linked to the original operation. The website only observes; scoped operation links expire or can be revoked and cannot authorise transactions.
Operator policy
Sibidz LLC · hello@sibidz.io
Supported regions: Not configured for live service. Prohibited regions: Not configured for live service.
Live record-retention and export policy must be configured before MainNet.
SHA-256: 57737452352c3c3be92e4ffbda319641a471a6da367e05a19d347555e0a5ec1e