Blog
Notes on building
with digital assets.
Product updates, security deep dives and practical guides from the team that builds Valtu.
product · security
Introducing Valtu: wallet infrastructure you can verify
Wallets for every customer, deposits that are credited only when final, payouts your own team approves, and keys held in hardware enclaves you can check yourself.
custody · security
Choosing wallet infrastructure: 12 questions to ask any provider
Before you trust a provider with customer funds, ask how keys are held, who can move money, what happens on bad days, and what they can prove. Here are the questions, with our own answers.
custody · security
Custodial wallet infrastructure or self-custody: what a fintech actually needs
Running your own keys gives full control and full responsibility. Custodial infrastructure takes the key work off your team. The real question is who can move funds, and how you can check it.
compliance · security
Screening crypto deposits and payouts with your own KYT provider
Connect your own Elliptic, Chainalysis, Blockaid or Webacy account: Valtu screens payout destinations before signing and deposit senders as deposits arrive, and holds risky ones for your team.
security
Verify the code that holds your keys
"Trust us" isn't a security model. How attestation and reproducible builds let anyone check what's running inside Valtu's enclaves, and what is still to come.
security · payouts
How a payout gets signed: policy, approvals, enclave
Every payout on Valtu takes the same path: your policies decide, your team approves with passkeys, and only then does the enclave sign. Here is each step.
Building something with Valtu?
Start with a free test workspace, or talk to the team about your use case.