zkgent

UI update shipped on zkgent.sbs. Cleaner layout. Faster load. Better flow. Refined components, improved responsiveness, and smoother interactions across the app. Changelog highlights: – Revamped dashboard UI – Optimized performance – Improved navigation & UX consistency – Minor bug fixes & stability improvements More updates coming.

shipped a full redesign for zkgent — new confidential-document landing — operator console restyled to match — fresh Z/G mark + favicon — mobile responsive end-to-end — socials + CA pill in hero 15 commits. zero compromises on the phosphor aesthetic.

How ZKGent makes a Solana transfer confidential — in 4 steps: 1/ COMMIT Browser generates a 32-byte secret + nullifier, hashed with Poseidon → produces a commitment. Nothing leaves your device. 2/ PROVE snarkjs builds a Groth16 proof against your local Merkle snapshot. ~1.2s. Proof size: 192 bytes. 3/ ANCHOR The proof + public signals get anchored on Solana via SPL Memo. No custom program = no upgrade authority = less to trust. 4/ SETTLE The relayer broadcasts. It only sees 192 bytes of math. Amounts, recipients, graph relationships — all hidden. That's it. No magic. Just real zk.

Confidential payments for Solana. No emails. No passwords. Your wallet is your identity. Built on Groth16 zk-SNARKs + Poseidon hash-chain. Anchored via SPL Memo. Zero-knowledge by default. → zkgent.sbs

Behind the scenes, we’re pushing deeper. This UI update is just the surface we’re refining the core, improving reliability, and preparing the next layer of features. Less noise. More precision. Built for real use, not just visuals. Stay with us bigger updates are on the way.

@kcasuncion18 openned

@zkgent open the TG so we can ask question about the team. pls

UI update shipped on zkgent.sbs. Cleaner layout. Faster load. Better flow. Refined components, improved responsiveness, and smoother interactions across the app. Changelog highlights: – Revamped dashboard UI – Optimized performance – Improved navigation & UX consistency – Minor bug fixes & stability improvements More updates coming.

@Alphaspy9 sorry input wrong ca ,I will fix it.

@zkgent Change the ca on github maybe ?

dev wallet locked : app.streamflow.finance/contract/solan…

$zkGent live on pumpfun : 3VyL7E5keZrnGVjXDbQ2egJRKCvnarPN5rNwYfqopump

We've just updated our servers and routers for a major upgrade. We'll keep you posted on the progress, as this will be a major upgrade for ZKGent.

@solana @humidifi keep Building

Today @humidifi is launching Aquarium, a transparent market making system built to give Solana projects deeper liquidity, tighter spreads, and clearer performance. Where the water is deep, the fish gather. Live on Solana ↓ 🐟

Entering the arena. We’re building with $zkGent at Colosseum Frontier Hackathon where real builders ship, compete, and get funded. From idea → product → acceleration. Let’s cook something unstoppable. colosseum.com/frontier

Today we shipped a major hardening pass across ZKGent on Solana. We improved wallet authentication, tightened settlement ownership checks, strengthened the signing flow, expanded integration testing, and cleaned up docs so the product behavior matches the trust model we present publicly. Private payments infra needs more than hype. It needs discipline. Public receipts: PR: github.com/zkgent/ZKGent/… Commit: github.com/zkgent/ZKGent/… CI: github.com/zkgent/ZKGent/… CI: github.com/zkgent/ZKGent/… We’re building private payment infrastructure on Solana for teams that need real operational trust.

We've just completed several key points: Ceremony artifact (server/circuits/transfer/ceremony/) manifest.json — chain source of truth (contributor + beacon + hash) contribution_0001.zkey — contributor #1's zkey output contributions/0001-zkgent-core.json — contributor #1's attestation contributions/beacon.json — beacon attestation transfer_beacon.zkey — post-beacon (= production final) zkey legacy_backup/transfer_0000_initial_setup.zkey — initial setup backup legacy_backup/transfer_final_legacy_singleparty.zkey — old zkey backup legacy_backup/verification_key_legacy.json — old vkey backup Backend server/domain/ceremony.ts — domain module (state + summary + trust level classification + hash consistency check) (live) Frontend src/routes/ceremony.tsx — public page /ceremony Documentation CEREMONY.md — threat model guide, how to verify, how to contribute Files updated (10) package.json — added ceremony:contribute|beacon|verify scripts server/circuits/transfer/build/transfer_final.zkey — regenerated from new ceremony server/circuits/transfer/build/verification_key.json — regenerated from new ceremony server/routes/zk.ts — new /api/zk/ceremony endpoint, embed summary in /api/zk/system, added integrity_status + branching note honest src/components/zkgent/Navbar.tsx — "Ceremony" link src/components/zkgent/Footer.tsx — "Trusted Setup" link src/routes/trust-model.tsx — updated bullet D1 to be consistent with the new chain src/routeTree.gen.ts — auto-regenerates due to the new route zkgent.db-{shm,wal} — regular SQLite WAL file (not relevant to the feature) Total: 26 files, +2094 / -11 lines. proff : github.com/zkgent/ZKGent/… guide : github.com/zkgent/ZKGent/…

We’re building ZKGent, a confidential payments system on Solana. The idea is simple: settlement should be fast and verifiable without making every payment, counterparty, and operational pattern fully public by default. We want privacy to feel like real infrastructure, not an afterthought. That means product, workflows, and cryptographic rails all have to come together. Still early, but the direction is clear. $zkGent $solana

We’ve opened early access for ZKGent. Still early, still being built, but the direction is clear: confidential payments on Solana, shaped around real operator workflows. If you want to follow closely or get involved early: zkgent.sbs/apply

Just added a new ceremony stack to the ZKGent repo under scripts/ceremony/. Included: - lib.mjs for shared helpers, manifest hashing, and Solana beacon fetch - contribute.mjs for adding phase-2 contributions - beacon.mjs for finalization using a Solana mainnet beacon - verify.mjs for full end-to-end verification of the contribution chain github.com/zkgent/ZKGent/… $ZKGENT #zk #solana #privacy

To briefly explain, today we're working on Plan: Phase-2 MPC Ceremony Infrastructure. Goal: Replace the single-party trust assumption with a ceremony that is transparent, verifiable, and open to external contributors - although starting today with just one contributor. What I built: Ceremony state tracking (server/circuits/transfer/ceremony/) manifest.json - version schema, circuit hash, contribution order contributions/000N-{handle}.json - attestation per contribution (name, timestamp, prev_zkey_hash, new_zkey_hash, contribution_hash, transcript) legacy_backup/ — store old zkeys as audit evidence CLI tools npm run ceremony:contribute — snarkjs zkey contribute wrapper with auto-generated attestation npm run ceremony:verify — verify full chain: each contribution is valid + chained from the previous one npm run ceremony:beacon — apply final public beacon (Solana mainnet finalized slot hash) Re-bootstrap ceremony Restart from transfer_0000.zkey (post-setup, pre-contribution) Contribution #1 from my /dev environment with random entropy + signed attestation Apply beacon from Solana mainnet slot hash as final "rerandomization". Result: new transfer_final.zkey + complete attestation chain API + system integration GET /api/zk/ceremony — return chain + verify status /api/zk/system augmented with ceremony block (contributors_count, beacon_applied, chain_verified, last_contribution_at) Public /ceremony page Hero: trust status (1/N contributors + beacon ✓) Contributors list with attestation hash links "How to contribute" instructions step by step Honest framing: "Production-grade requires 5+ independent contributors" Update /trust-model + Footer link to ceremony

This is the settlement flow behind ZKGent. An operator initiates a payment, the API checks wallet access, a Groth16 proof is generated and verified, the note and nullifier are persisted, then an unsigned Solana transaction is prepared for wallet signing before final submission on-chain. In other words: not just a concept, but a real confidential payment flow taking shape step by step. $ZKGENT

ZKGent is an operator workspace for sending and managing confidential payments on Solana. Transfer values, recipients, and metadata are hidden inside zero-knowledge commitments, while settlements are anchored on Solana devnet so anyone can verify they happened without seeing what they were. The console covers the full payment lifecycle: ad-hoc transfers, recurring payroll batches, treasury routing, counterparty management, and a unified activity feed. $ZKGENT