Planned features, subject to change. Some require licenses or partners VaultChain does not yet have. No dates promised. Nothing on this page is live product.
An optional way to send with a return window: funds sit in escrow until claimed, and an unclaimed send returns to you at expiry. It currently runs as a simulation inside the demo dashboard.
9% of protocol fees is set aside in a planned gold-purchase bucket. Once enough has accrued and a custody partner exists, the protocol plans to purchase physical gold and publish receipts for it.
Any purchased gold would be held as a company treasury asset while the long-term structure is designed. It does not back VLT or deposits, has no value floor, and involves no price claim of any kind.
A way to name a beneficiary for your vault. This is not a will and does not replace estate planning. Naming rules and what happens to a dormant vault are still being designed, including how state unclaimed-property rules apply.
VaultSlices would let a vault owner list fractional interests in a vault position for other users to hold, under legal review before any build. Selling fractional interests like this raises securities and exchange questions that need to be resolved first.
Planned loan products: one against your own vault balance, one against an outside asset you describe. Consumer lending at a stated rate requires state lending licenses VaultChain does not hold today.
A planned protocol-linked card. Issuing an actual payment card requires a bank or card-issuing partner, which does not exist yet.
A planned reserve, funded by 14% of protocol fees, intended to activate only during extreme, coordinated volatility events. The activation mechanism and what it would actually do are still being designed -- it is not a routine price-support tool, and no such mechanism is live today.
A planned fast payment rail between vaults, capped per transaction. Like GhostPay, moving value between different users raises money-transmission questions that need to be resolved before it can be real.