Veda Opens Vault Service to Stripe's Privy Wallet Infrastructure

iconKuCoinFlash
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy
AI summary iconSummary

expand icon
Veda, a vault infrastructure provider spun off from MetaEra, announced on June 2 (UTC+8) that it is opening its Vault service to teams using Privy, the wallet infrastructure company acquired by Stripe in June 2025. The on-chain announcement was made at the Proof of Talk 2026 event in Paris. Developers on Privy can now integrate vault infrastructure via a standard API call. Previously, Veda’s service required institutional adoption and months of coordination with specialized teams, making it prohibitively expensive for most firms.

ME News reports that on June 2 (UTC+8), Vault infrastructure provider Veda and Stripe announced that Veda will open its Vault service to development teams building on Privy, a wallet infrastructure company acquired by Stripe in June last year. The announcement was made at the Proof of Talk 2026 conference held at the Louvre in Paris. Teams building on Privy can now provide Vault infrastructure to their users. Previously, Veda’s Vault was only accessible through one-off institutional integrations, requiring dedicated engineering teams and months of coordination—investment levels unaffordable for most companies. Privy’s integration simplifies this process into a standard API call. (Source: Foresight News)

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.