FAQ
This FAQ explains how AlphaPing operates mandate-driven, non-custodial on-chain credit vaults under explicit, mechanically enforced risk boundaries. It is intended for institutional allocators, funds, family offices, platforms, and ecosystem participants evaluating structured on-chain credit exposure.
Core Concepts
Q: What is AlphaPing?
A: AlphaPing is an operator-grade risk curator that designs and operates mandate-driven, non-custodial on-chain credit vaults with explicit, mechanically enforced risk boundaries. It is not a discretionary manager, hedge fund, or yield optimizer.
Q: What is an AlphaPing vault?
A: A vault is a self-contained risk container defined by a clear credit mandate. Positions, risk constraints, and behavior are public and enforced on-chain. Capital is non-custodial; users retain control via smart contracts.
Institutional Value Proposition
Q: Why would an institutional allocator use AlphaPing vaults?
A: For defined, verifiable credit exposure under explicit risk boundaries, mechanical enforcement, liquidity discipline, and continuity across stress regimes. Risk is defined upfront — not optimized after deployment.
Q: How do these vaults compare to discretionary credit strategies?
A: AlphaPing vaults do not rely on discretionary intervention, opportunistic rebalancing, or subjective risk decisions. They operate within a pre-specified mandate that governs permitted actions and prohibited behaviors — all verifiable on-chain.
Mandate and Risk Mechanics
Q: What is a mandate?
A: A mandate is a defined risk framework that specifies eligible markets, collateral types, maximum loan-to-value ratios, utilization limits, oracle dependencies, liquidation mechanics, liquidity constraints, and exit paths — enforced mechanically by smart contracts.
Q: How are risk boundaries enforced on-chain?
A: Vault parameters and constraints are encoded in smart contracts. Any action that would violate a mandate is prevented at the protocol level. There is no discretionary override.
Q: What happens under stress conditions?
A: Vaults continue to operate within the mandate, process withdrawals subject to liquidity availability, and realize losses where defined. Outcomes are mechanical and observable: there is no discretionary delay or hidden intervention.
Non-Custodial and Transparent Operation
Q: Does AlphaPing custody assets?
A: No. Vaults are fully on-chain and non-custodial. Users retain control through smart contracts, and all positions and parameters are transparent and verifiable.
Q: Is there discretionary trading or rebalancing?
A: No. Vault behavior is mechanically enforced; risk parameters are fixed and monitored. AlphaPing does not chase yield or make subjective allocations.
Performance and Liquidity
Q: How are returns generated?
A: Returns emerge from defined credit exposures — supply to borrowing markets within mandate constraints — and are a structural outcome of risk-bounded utilization, collateral quality, and market conditions. They are not targeted or guaranteed.
Q: What are liquidity expectations?
A: Liquidity targets (including T+0 considerations) and constraints are defined in the mandate. Withdrawals are processed on-chain subject to actual available liquidity.
Risk Disclosure
Q: What risks should allocators understand?
A: Principal risks include credit risk, liquidity risk, oracle behavior risk, smart contract risk, and market stress conditions. Losses can occur and are reflected mechanically in share price and on-chain accounting.
Q: Can AlphaPing override risk limits to protect capital?
A: No. Risk constraints are explicit, public, and mechanically enforced. There is no discretionary intervention to mitigate losses or make exceptions.
Partner and Integration Questions
Q: How can platforms and distributors integrate AlphaPing vaults?
A: Through defined partner models (independent wrappers or joint vaults) where risk boundaries remain intact, and AlphaPing operates the vault under mandate discipline. Partners may layer distribution fees, but risk parameters remain unchanged.
Q: Can a fund launch its own mandate-specific vault with AlphaPing?
A: Yes. AlphaPing supports co-designed mandates with explicit boundaries. Capital deployment begins only after mandates are fixed, public, and mechanically enforceable.
Q: How does a fund-of-funds verify execution and isolation?
A: All positions, parameters, and state transitions are public on-chain; there is no cross-vault subsidy or implicit pooling. A fund-of-funds can independently audit exposures and constraints on-chain.
Family Office and Allocator-Specific
Q: How does a family office ensure risk boundaries are explicit?
A: Family offices receive the publicly documented mandate, including detailed risk parameters, liquidity constraints, stress behavior, and exit mechanics — all enforceable on-chain without subjective interpretation.
Q: Can risk profiles be tailored to institutional limits?
A: Yes. Mandates define exact risk boundaries. If a risk cannot be bounded with clear mechanical constraints, it is not included in the mandate.
Technical and Governance
Q: How is on-chain accounting verified?
A: Vault states, positions, constraints, and transitions are visible on-chain. Independent verification comes from observing smart contract storage and event logs.
Q: Are mandates adjustable after launch?
A: Changes require deliberate, explicit action with clear documentation. There is no silent parameter drift or opportunistic adjustment.
Not Within Scope
Q: What does AlphaPing explicitly not do?
A: AlphaPing does not act as a discretionary credit manager or trader, does not custody user funds, does not provide legal or tax advice, does not guarantee returns or principal preservation, and does not dynamically optimize risk post-deployment.