Proof Engine and API limitation
A valid receipt from the browser engine or Receipt API beta proves internal consistency under the listed engine version and, when present, control of a signing wallet. It does not prove honest measurements, completeness, trusted time, service delivery or legal identity. The unaudited off-chain software and hosted API may contain implementation, interface, availability or infrastructure defects.
Synthetic simulation limitation
The default $25,000,000 shown by the deterministic simulator is synthetic nominal volume: 250,000 model agreements at $100 each with 1,000,000 checks. It is not historical activity, total value locked, revenue, customer funds, adoption, settlement capacity, audited performance or assets secured. The simulator moves no assets, and service and escrow volume remains $0.
Technology risk
The current browser software, API, hosting, wallets and interfaces can contain bugs or vulnerabilities or become unavailable. If future smart contracts, evidence adapters, verification workers or integrations are deployed, they would add further risk. Blockchain transactions may be irreversible, and admin, treasury or signing keys may be lost or compromised.
Verification and slashing risk
Evidence may be incorrect, incomplete, delayed, unavailable, unlicensed or manipulated. Any future verifiers may fail, collude or disagree. Objective criteria can still be specified badly. If settlement or slashing is later deployed, those failures could produce a false decision, and an appeal might be unavailable, delayed or unsuccessful.
Collateral and refund risk
“Assurance” does not mean insurance or a guarantee. No collateral or refund system is live. If one is deployed, any refund would be limited by the transaction terms and available assets. Stablecoins can depeg, be frozen or blacklisted by an issuer, provider collateral can be insufficient, and a token price can move sharply.
Identity, reputation and privacy risk
Submitted receipts can contain identifying or confidential information, and API submissions transit hosting infrastructure. Future public wallet activity and any on-chain outcome records may be linkable across applications. Records can be incomplete, misinterpreted or attached to compromised identities.
Solana and third-party risk
No PactVerity settlement program is deployed. If Solana functionality later launches, network congestion, interruption, program changes, RPC failures, wallet vulnerabilities, exchanges, aggregators and other third parties may affect access or settlement. PactVerity does not control those systems.
Token, SOL and market risk
PVTY may have no value, sustainable buyer demand or lasting resale market. Independent liquidity can be shallow, volatile, manipulated, paused or removed. There is no guarantee of adoption, listing, price appreciation, revenue, yield, redemption or continued market access.
DEX trading risk
Jupiter and Raydium are independent third parties. Quotes can change before execution; price impact, slippage, pool fees, network fees, routing errors, malicious copied tokens or liquidity removal can cause loss. A route-detection result is not a guarantee that a later transaction will execute at the same price.
Governance and control risk
Early systems may rely on a development team, multisignature permissions or upgrade authorities. Token ownership and voting can become concentrated. Emergency actions may be delayed, ineffective or misused.
Legal and tax uncertainty
Rules differ by country and can change. Future access may be restricted. Users are responsible for obtaining professional advice appropriate to their own jurisdiction.
No advice or offer
This website is general information, not financial, investment, legal or tax advice and not an offer or solicitation to purchase an asset.