Your keys never leave your phone.
We reviewed the entire AseVault wallet, line by line: how keys are made, how the vault locks them away, how every transaction gets your approval first. Here is what it means for you, in plain words.
Reviewed against the real app source · v1.1.0
Keys stay yours
Created on your device with 256 bits of randomness. There is no server that could ever see or send them.
You approve everything
Every spend, signature, and secret reveal asks for your fingerprint or passcode first. Nothing signs silently.
Post-quantum by design
Signed with ML-DSA-65, the NIST standard built to resist even future quantum computers.
What we verified
Six layers that keep the vault shut
Keys are born on your device
A 24-word phrase built from 256 bits of operating-system randomness becomes your post-quantum keypair. The same phrase restores the same wallet in any official Asentum app, and it is shown to you exactly once.
The vault is hardware-locked
Everything sits under AES-256-GCM encryption, and the key that opens it lives inside your phone's secure hardware (Android Keystore / iOS Keychain). Copying the app data gives an attacker unreadable ciphertext.
Every action needs you
Sends, signatures, exports, and dApp connections all pass a biometric or passcode gate. Approval screens show the real origin, amounts, and full payload before anything signs.
Guessing is shut down
Wrong passcodes trigger escalating lockouts that climb to 10 hours and survive restarts. The answer is verified by actual decryption, not a stored check, so there is nothing to shortcut.
dApps see approval screens, not keys
The in-app browser and deep-link connector validate origins, cap payloads, and route every request through the same human approval. A malicious site can ask; it cannot sign.
Quiet by default
Notifications never show amounts, stay hidden on the lock screen, and the app blocks screenshots on every sensitive surface.
The scorecard
How each area rated
Twelve areas, reviewed against the shipped code. Most landed at the top mark.
Overall: Strong
Nine of twelve areas earned the top mark. The rest reflect the honest limits of any mobile hot wallet and previews, not code flaws.
Key generation
256-bit entropy, 24-word phrase, post-quantum ML-DSA-65
Encryption at rest
AES-256-GCM behind a hardware-gated vault key
Secret handling
Keys live in memory only, wiped the moment you lock
Spending authorization
Biometric or passcode gate on every send and reveal
Brute-force protection
Escalating lockouts up to 10 hours, saved across restarts
Backup & recovery
Masked phrase entry, 6-word confirmation, clipboard scrub
dApp connections
Every request needs your approval; nothing signs silently
Transaction safety
Exact-amount approvals, real fee estimates, replay protection
On-screen privacy
Screenshot blocking, hidden lock-screen alerts, masked entry
Network layer
Everything over TLS; a bad server can mislead reads, never spend
Device health checks
Warns on emulators and custom ROMs; deeper checks need native modules
Rooted phones
No software wallet can survive a fully compromised OS
Straight talk
Good to know
A trustworthy report says where the edges are. None of these can take your funds on a healthy phone, but you deserve to know them.
Your phone + PIN is your wallet
Whoever holds both can spend. Set a strong passcode, turn on biometrics, and keep your phrase written down somewhere offline.
Rooted phones weaken the walls
A jailbroken or rooted OS can bypass the hardware protections every wallet relies on. AseVault warns when it detects a modified device.
Web builds are previews only
Browsers have no secure hardware, so the web version is for testing, not for real funds. Production is iOS and Android.
A bad network can lie about numbers
A hostile server could show wrong balances or quotes, but it can never move your funds. Every transaction still needs your local signature.
While unlocked, keys live in memory
True of every software wallet. Auto-lock shrinks that window to minutes.
Keep installs official
Only download the APK from asepad.fun. The team is moving release signing to fully managed credentials so updates stay verifiably ours.
The roadmap
What the AsePad team is doing next
Managed release signing
Moving app signing to EAS-managed credentials so no build machine ever holds them directly.
Deeper device checks
A native module for stronger root and jailbreak detection beyond today's heuristics.
Independent third-party review
An external cryptography and mobile-security audit is planned before wider rollout.
Continuous hardening
Each release tightens something. Findings from this review feed straight into the roadmap.
Questions
Frequently asked
Why should I use AseVault?
It is the first wallet built natively for Asentum's post-quantum signatures. It holds your ASE and ARC-20 tokens, connects to AsePad, AseDex, AURAS and other apps, and asks for your approval before anything signs. No account, no email, no custodian: the wallet lives on your device.
How secure is it, really?
Keys are generated with 256 bits of randomness, sealed under AES-256-GCM, and anchored to your phone's secure hardware. Every spend needs your fingerprint or passcode, and wrong guesses trigger lockouts that climb to ten hours. Nine of the twelve areas we reviewed rated Strong; the rest are the honest limits every mobile hot wallet shares.
Can AsePad or AseVault see my keys or phrase?
No. Keys are created and stored only on your device. Nothing, including us, ever receives them. The app has no accounts, no analytics of secrets, and no backend holding user data.
What does post-quantum actually mean for me?
Signatures use ML-DSA-65 (Dilithium3), a NIST-standard scheme designed to stay unforgeable even against future quantum computers. It is the same scheme the Asentum chain itself runs on, so your wallet is as future-proof as the network.
What happens if I lose my phone?
Your 24-word recovery phrase restores the same wallet on a new device, because key generation is fully deterministic. Write it down, keep it offline, and never store it in screenshots or cloud notes.
What if someone steals my phone?
They still cannot open the vault without your biometric or passcode, and passcode guesses are throttled hard. The encryption key sits in hardware the OS guards. If they somehow have your passcode too, restore your phrase on a new device and move funds.
Is the web or desktop version safe to use?
It is a development preview. Browsers have no secure hardware, so use it to explore, not to hold funds. The real security model applies to the iOS and Android apps.
How does the team keep improving security?
Each review turns findings into fixes. Recent passes added masked phrase entry, clipboard auto-clearing, stricter connection validation, and escalating lockouts. Next up: managed release signing, deeper device checks, and an independent third-party audit.
Independent review welcome
This report reflects the audited app source. A formal third-party review is encouraged before large-value use.