Open an encrypted vault
Select Stellar testnet, public network or a custom network, then reconstruct the encrypted account chain with the database secret.
Encrypted vault that uses the Stellar network
boot>
Secure the secret. Review the operation.
SVAULT is a credential vault by Badje. It encrypts sensitive records in the browser, shows the ledger impact before signing, and preserves a verifiable history of operations through the Stellar network.
Every record stays encrypted, reviewable and under your control until you approve the final operation.
✓Local browser encryption
✓Explicit approval before signing
✓Traceable transaction history
NetworkStellar
✓
FlowOpen • Add • Approve
Encrypted records
Approval before signing
Traceable commits
LOCAL ENCRYPTION✦
APPROVAL BEFORE SIGNING✦
USES THE STELLAR NETWORK✦
PWA READY✦
BUILT BY BADJE✦
LOCAL ENCRYPTION✦
APPROVAL BEFORE SIGNING✦
USES THE STELLAR NETWORK✦
What SVAULT can do
A focused vault for encrypted credentials and verifiable operations.
SVAULT is designed around clear user actions: choosing a network, opening the encrypted database, adding or editing records, reviewing the ledger cost, approving the action, and keeping a result you can track later.
Store credential records
Save title, username, URL, secret, notes and tags inside a structured record model that is easier to manage than scattered files or messages.
Encrypt before submission
Record content is encrypted in the browser before chunks are prepared for the selected Stellar environment.
Review ledger impact first
A dedicated approval screen shows fee, reserve change, operations, chunks and record delta before anything is signed.
Track the final result
After a successful commit, SVAULT shows the transaction hash and commit state so the action can be referenced and, where applicable, independently inspected.
Run like an app
The interface is responsive, installable as a progressive web app, and intentionally shaped to feel stable across desktop and mobile devices.
Capability summarysecurity workflow
Networks: testnet, public, custom
Record types: credential-style structured records
Core actions: open, browse, add, update, approve, commit
Security flow: encrypt → estimate → approve → sign
Verification: transaction hash and ledger-backed operation trail
Platform: browser-based PWA by Badje
Blockchain in plain language
A shared ledger makes silent history changes harder.
You can think of a blockchain as a continuously ordered ledger kept by multiple computers. The network agrees on valid signed operations, so the transaction history is not locked inside only one private server or one browser session.
One history across many nodes
Multiple nodes keep aligned copies of the ledger. That means the transaction history does not exist only inside one product interface.
Every change is signed
Recorded operations are signed by an account key. From the ledger, it is possible to inspect which account authorized the transaction.
Hidden tampering becomes visible
Transactions are ordered through network agreement. Replacing earlier history without leaving evidence becomes far more difficult.
Short answer
A blockchain does not automatically make information private. SVAULT uses local encryption for confidentiality and uses a distributed ledger for signed, traceable history.
How SVAULT works
Every critical step stays visible to the user.
The flow is simple: choose the Stellar environment, manage encrypted records, inspect the operation details and approve only when you are confident.
Choose a network and open the vault
Connect to Stellar testnet, public or a custom network, then use the database secret to reconstruct the encrypted chain.
Network + database secretCreate or update a record
Enter the required fields. Encryption, chunk preparation and transaction building happen inside the app flow.
Local encryptionReview the fee and approve the action
Before commit, you can review reserve changes, operations, chunk count and record impact; only then is the action signed and submitted.
Explicit approval
How SVAULT uses Stellar
Stellar is the ledger infrastructure, not the brand behind the product.
SVAULT is designed and developed by Badje. The app uses Stellar accounts, signed transactions, fees and ledger entries to store and reconstruct encrypted record chunks, and it can connect to testnet, the public network or a custom network.
Read the official Stellar introduction ↗Development and testing
Stellar public network
Private or self-hosted network
Why this vault can be trusted
Confidentiality comes from encryption; confidence comes from signed and reviewable operations.
SVAULT combines local browser encryption, session-only database-secret handling, chunked ledger storage and a final approval screen. Security still depends on protecting the database secret, the device, the browser and the chosen network.
✓
AES-256-GCM local encryption
Record content is encrypted in the browser before it is turned into ledger chunks or sent to the selected network.
Database secret stays in the active session
SVAULT uses the database secret in browser memory and does not present it as permanently saved app data.
Nothing is signed without your approval
The app shows fee, reserve change, operation count, chunk count and record delta in a dedicated review interface before submission.
History that can be tracked later
Signed Stellar transactions create an inspectable trail, and the transaction hash becomes an independent reference for the final action.
Security note: SVAULT cannot recover a lost database secret and cannot fully protect against a compromised device, a malicious browser extension or an unsafe custom network. Keep backups offline and verify the selected network before approval.
Important questions
Before trust comes clarity.
What does the blockchain do, what does SVAULT encrypt, and what should the user still protect?
A blockchain is a shared, ordered ledger maintained by multiple participants. Signed transactions become part of a history that can be checked independently of the app.
No. SVAULT encrypts record content before ledger chunks are prepared. The network receives encrypted data and transaction information, not the readable secret or note that was typed into the form.
SVAULT is a Badje product. It uses Stellar as the account, transaction and ledger layer and supports testnet, the public network and custom network connections.
You should protect the database secret, the device, the browser session, backups and any signing keys used for transaction approval. Losing the database secret can make encrypted records impossible to reconstruct.
Yes. After a successful commit, SVAULT shows the transaction hash. On supported public environments, that identifier can be checked with an independent Stellar explorer.
Badje is building SVAULT. The project is open to investor conversations, strategic partnerships, technical collaboration, security review and voluntary financial support.
BADJEThe brand behind SVAULT
Built by Badje
SVAULT is looking for investors, strategic allies, technical collaborators and supporters.
Badje is the product brand and development team behind SVAULT. We welcome conversations with investors, organizations interested in pilots, security specialists, members of the Stellar ecosystem and people who want to help the product move faster.
Visit badje.ir ↗01
Investment & partnership
If you want to discuss investment, a pilot deployment, product partnership or ecosystem collaboration, contact the founder directly.
Discuss collaboration02
Donation & project support
Voluntary support can help cover infrastructure, design, security review, documentation and continued development. Email us to receive the current support options.
Support the projectProject contactTooraj Valaeetooraj.valaee@live.com
Open SVAULT
Encrypt locally, inspect the action and commit only when you are ready.
Open SVAULT in a modern browser and choose the Stellar environment that matches your use case.
Open app.svault.ir