We built the foundation. Now we're scaling the stack.
What comes next is a complete privacy layer: passwordless auth with STARK proofs, visual explorer, Zcash shielded addresses, Privacy Relay, and Archium encryption. A multi-phase plan to make zkTerm the unified interface for zero-knowledge technology.
Privacy infrastructure, not just privacy tools.
Read full: docs.zkterm.io/resources/roa…$ZKTR
One terminal for the entire ZK universe.
Merry Christmas & Happy Weekend from $ZKTR!
Apologies for just getting back to tweeting ,we’ve been busy building behind the scenes.
zkterm.io is being developed as a unified ZK terminal focused on privacy-first identity and seamless on-chain interaction.
Several updates will be published next week.
Enjoy the holiday season, take a moment to read the website, and
stay tuned.
Decentralization isn't just about the blockchain, it's about the code too.
That's why we're making $ZKTR fully open source.
Starting with the Dashboard Widget:
→ github.com/zkTerm/dashboard
Build with us. Verify everything. Trust no one
Gm,
zkTerm is now running its own Zcash RPC node. hoping to integrate and run zcash features on zkterm soon.
zcash-node.zkterm.io/
X-API-Key: working ✅
SSL: working ✅
blocks: 3,169,960
verificationprogress: 99.99%
$ZKTR
GM!
What will we build today?
Vision: Make zkTerm dApp fully decentralized.
We're working on making zkTerm's dashboard or explorer run 100% client-side so it can be hosted on Crust or Filecoin.
First step: Settings page for custom RPC URLs and @resend API configuration.
Why? Some functions like Email OTP still need a server. By letting users configure their own keys, we remove that dependency.
One step closer to a truly unstoppable dApp.
zkAuth 2FA Update
All users now required to set up 2FA:
• TOTP (Authenticator apps)
• Email OTP
100% decentralized — no database, no server secrets.
TOTP secrets encrypted → IPFS on-chain pointer on Solana.
$ZKTR - Your keys, your security.
#ZKAuth#ZeroKnowledge#ZKTR#Solana#Starknet
GM, what $ZKTR'll build today?
Adding Email OTP to zkAuth Layer 2 security - but fully decentralized.
No database. No centralized storage. Just math.
How it works:
- Request OTP → server generates code signed token
- Token contains hash expiry signature
- OTP sent to your second / other email
- Enter code → server verifies token signature, done
The "state" lives in the token itself. Stateless verification. Zero storage dependency.
True decentralized 2FA.
#zkAuth#zkTerm
No seed phrases to lose. No central reset. Just trust.
Testing 2FA with Google Authenticator on zkAuth
Feature just works! Successfully integrated TOTP-based two-factor authentication. However, still not optimal yet.
Next development:
Users will be REQUIRED to set up at least 1 of 3 Layer 2 security options before gaining full access to the Explorer:
- 2FA TOTP
- Hardware Wallet
- Social Recovery
This ensures every zkAuth identity has proper security barriers activated.
#zkAuth#Web3Security#ZeroKnowledge
Just checking the zkTerm page on PumpFun and realized that we have already completed our first month of building zkTerm, Thank you to all our holders for your continued trust and support 🙏
Your commitment means a lot as we work to grow and strengthen this project
The team is currently stress-testing zkAuth across all flows -> registration, login, 2FA, and multi-chain anchoring. Making sure every cryptographic handshake between Google OAuth, Solana, Starknet, and Zcash runs exactly as designed. No shortcuts. No single points of failure. $ZKTR
How zkAuth Works
zkAuth is fully decentralized authentication. No passwords, no databases, no server secrets.
Your master key is split across 3 blockchains. You only need 2 to recover.
Is it custodial? No. The complete master key is NEVER stored anywhere. Not on servers, not in databases, not even on the blockchains. Only encrypted fragments exist on-chain.
Fully non-custodial. $ZKTR