Market Monitoring & Alerting
Read-only monitoring for LP activity, authority changes, whale transfers, wash-like patterns, and oracle deviation. TROPTIONS cannot freeze or pause on-chain state — monitoring is investigative only.
Sudden removal of >20% of pool liquidity
Trigger: Pool balance decreases by >20% in a single block or ledger
Response: Alert partner operator immediately. Display warning to UI users.
Escalation: Compliance Officer if partner cannot be reached in 30 minutes
Pool liquidity drops to near-zero
Trigger: Pool balance below 5% of initial seeded amount
Response: Immediately display rug-risk warning. Alert all committee members. Suspend UI display.
Escalation: Executive Sponsor — immediate
Mint authority wallet changes on a partner token
Trigger: Token metadata or on-chain authority field changes for mint authority
Response: Alert Technical Lead and Compliance Officer. Suspend proof packet.
Escalation: Executive Sponsor within 1 hour
XRPL issuer account flag changes (DefaultRipple, RequireAuth, GlobalFreeze, NoFreeze, DisableMaster)
Trigger: account_info Flags value changes from baseline
Response: Alert immediately. Flag change without disclosure is a proof packet violation.
Escalation: Legal Counsel + Compliance Officer — immediate
Volume pattern consistent with wash trading: same wallets buying and selling, circular flows
Trigger: Circular transfer between ≤3 wallets accounts for >30% of volume in 24h
Response: Alert Compliance Officer. Suspend proof packet 'verified' label. Initiate investigation.
Escalation: Executive Sponsor + Legal Counsel — same day
Any suspected unauthorized access, key compromise, or exploit
Trigger: Security monitoring alert, partner report, or anomalous admin action
Response: Activate incident response runbook immediately. Alert all committee members.
Escalation: Executive Sponsor + Legal Counsel — immediate
Freeze authority changes on a partner token
Response: Alert Technical Lead. Review proof packet accuracy.
Transfer of >5% of token supply in a single transaction
Response: Log event. Alert partner operator. Review for wash-like pattern.
LP wallet transfers tokens or changes position outside of normal protocol actions
Response: Alert partner operator and Technical Lead. Verify LP lock status.
Token price deviates >30% from oracle or reference price in under 5 minutes
Response: Display price warning in UI. Alert partner operator. Check for manipulation.
Volume increases >10x 24h average in under 1 hour
Response: Log event. Alert partner operator. Review for manipulation signals.
Non-Custodial Route Architecture
- TROPTIONS OS never requests or stores private keys.
- TROPTIONS OS never submits unsigned transactions on behalf of users.
- TROPTIONS OS never holds token balances in TROPTIONS-controlled wallets.
- TROPTIONS OS never executes trades without user-initiated wallet signature.
- TROPTIONS OS never routes funds through TROPTIONS treasury wallets.
- All DEX integration is read-only quote and route display until user signs.
User connects their wallet (Phantom, XUMM, Metamask, etc.) to the TROPTIONS OS interface.
TROPTIONS OS never requests private keys. Connection is view-only until user signs.
User specifies trade parameters: token pair, amount, slippage tolerance, and target venue.
No funds move at this step. Intent is read-only.
TROPTIONS OS queries DEX aggregators and/or on-chain pools for current quotes.
Read-only API calls. No transaction submitted. Data is indicative only.
Available routes displayed to user: price, fees, slippage, DEX venue, and estimated output.
TROPTIONS displays options. User selects preferred route.
TROPTIONS OS constructs the transaction object (swap, offer, payment) unsigned.
TROPTIONS never holds a signing key. Transaction is a pure data structure at this point.
User's connected wallet presents the transaction for review: amounts, fees, and counterparty.
User sees full transaction details in their own wallet. TROPTIONS cannot override this.
User approves and signs the transaction with their private key inside their wallet.
Private key never leaves user's wallet. TROPTIONS OS never sees the signature key.
Signed transaction is broadcast to the blockchain (XRPL, Solana, or EVM).
Submission may happen via wallet provider or user-authorized RPC. TROPTIONS may relay if authorized.
Transaction is confirmed in a block/ledger. TROPTIONS OS reads and displays the result.
Confirmation data is pulled from public RPC. No custody occurs at confirmation.
TROPTIONS OS logs an immutable proof event: tx hash, timestamp, venue, route, and wallet addresses.
Proof events are non-custodial audit records. No funds or keys involved.
Post-trade monitoring: liquidity levels, authority changes, whale movement, and price deviation.
All monitoring is read-only from public chain data.
Anomalies trigger alerts to partner operators: LP removal, authority change, wash-like patterns.
Alerts are informational only. TROPTIONS cannot freeze, pause, or modify on-chain state.