← All protocol dossiersSource fetched 2026-09-22T12:27:16Z
SPYx × Veda xStocks Vault
Exact-token support is source-listed The protocol or product source names this exact token. No configuration decoding or read-only execution simulation was performed.
Source-described use: Deposit the xStock into a self-custodial Veda vault through Kraken Pro. Sentora manages the strategy, which posts the xStock to Kamino, borrows stablecoins and returns yield in the deposited xStock.
Open SPYx token report · Open xstocks-backed issuer dossier
Exact token and source-described action
- Solana token address
XsoCS1TfEyfFhfvj8EtZ528L3CaKBDBRqRapnBbDF2W- Actions described by source
- deposit, earn-yield
- Source-reported integration status
- live
- Access limits
- Available only to eligible Kraken clients; geographic restrictions apply and deallocation has a three-day processing window.
- Direct links
- Open market / product ↗ · Protocol documentation ↗
Proof status — do not read a source listing as execution proof
- Achieved proof stage
- source-listed
- Source proof status
- named-product-page
- Source fetched
- 2026-09-22T12:27:16Z
- Activity observed
- Reported market metrics, if shown, are source-reported parameters or activity indicators, not independently executed trades.
- Account existence
- not-addressable (0/0 referenced accounts)
- Configuration decoded
- Not performed
- Read-only execution simulation
- Not performed
Source evidence
- official-product-page: Veda names exactly three supported assets: SPYx, QQQx and NVDAx, with Veda on Solana, Sentora as risk manager and Kamino as the lending market. Open source ↗
- official-product-page: Kraken documents the deposit, self-custodial embedded wallet, wrapped vault accounting and three-day withdrawal window. Open source ↗
Referenced accounts and owners
The current source data records observed owners, not a separately published expected-owner assertion; where no such assertion exists, it remains not established. Account existence and owner corroborate the published reference but do not independently decode configuration or prove a user action can succeed.
Recorded parameters
- Maximum LTV
- Not reported
- Liquidation LTV
- Not reported
- Liquidation penalty
- Not reported
- Configured / observed size
- Not reported
- 24 h volume
- Not reported
- 24 h transactions
- Not reported
- Oracle
- Not reported
Markets and configured addresses
- No market-level configuration was recorded.
Custody and default outcomes
Borrower default / seizure
The lender can seize and sell; redemption is gated
The token is a transferable bearer ledger-based security, so the contract can transfer or sell it after default while the mint is open. Direct redemption for cash is not autonomous: the lender must pass KYC/AML and the issuer may reject a request on negative findings.
Protocol hack custody
Clawback may reverse a theft
The permanent delegate and pause authority can technically contain or reverse a hacked transfer. Assistance is discretionary rather than a protocol right, and the same powers can reverse the protocol's own custody or liquidation outcome.
Access or key loss
Issuer action can rescue a stranded token
The permanent delegate can technically move or burn a balance in an inaccessible account. A replacement or redemption still depends on the issuer accepting the claimant, completing compliance checks and exercising that power.
These are issuer-plus-control-recipe conclusions from the matched legal template — not protocol simulation results.
Lender exit after receiving the token
Conditional market exit — The lender can use a checked on-chain sale route, but issuer controls, transfer conditions, or thin liquidity may prevent full realisation.
- Observed DEX liquidity
- $3,791,147
- Issuer redemption established
- yes
- Key limit
- Possession of the token does not itself establish eligibility, issuer recognition, redemption access, or enough executable market liquidity.