{"version":1,"id":"zkmoney","title":"zk.money","summary":"zk.money is an open-source, self-custodial wallet built on the Aztec Network that lets users send and receive cryptocurrency privately using readable tags.","content":"**zk.money** is an open-source, self-custodial [cryptocurrency](https://iq.wiki/wiki/cryptocurrency) wallet that lets people send and receive crypto privately, built on the [Aztec](https://iq.wiki/wiki/aztec) Network by Aztec Labs, a United Kingdom-based developer. The wallet holds funds privately on the Aztec Network, a privacy-focused [Layer 2](https://iq.wiki/wiki/layer-2) on top of [Ethereum](https://iq.wiki/wiki/ethereum), so that balances, amounts, senders and recipients of transactions made inside the system are not published to any public chain.[\\[1\\]](#cite-id-fvktqsq2gp)​[\\[2\\]](#cite-id-dousgnm9f3) Users deposit funds from Ethereum, move them privately within zk.money, and withdraw back to Ethereum [mainnet](https://iq.wiki/wiki/mainnet) at any time.[\\[3\\]](#cite-id-6grjopt3vk)​\n\n## Overview\n\nzk.money can be used as a web wallet at its own domain or as a locally run desktop application, and the same passkey gives access to the same wallet across different devices.[\\[1\\]](#cite-id-fvktqsq2gp) Funds flow in from [Ethereum](https://iq.wiki/wiki/ethereum), move privately inside zk.money, and can be withdrawn back to Ethereum whenever the user wants.[\\[4\\]](#cite-id-ayzmyx8crt) Transactions are proven on the user's own device before being sent, so private keys never leave the device.[\\[3\\]](#cite-id-6grjopt3vk)​\n\nThe system is made of several components living on Ethereum and the [Aztec](https://iq.wiki/wiki/aztec) Network: immutable on-chain [smart contracts](https://iq.wiki/wiki/smart-contract), a security and migration protocol named Oxide, and a web interface or desktop app.[\\[4\\]](#cite-id-ayzmyx8crt) The Aztec Network, described as a fully private, fully programmable network on top of Ethereum, is where zk.money's notes and balances ultimately live.[\\[1\\]](#cite-id-fvktqsq2gp) zk.money states it pays no Ethereum gas on payments made inside the system, while deposits sent from Ethereum into zk.money require [Ethereum](https://iq.wiki/wiki/ethereum) gas and are public, because all Ethereum transactions are public.[\\[1\\]](#cite-id-fvktqsq2gp)​\n\n### Self-Custody and Passkeys\n\nThe wallet is non-custodial and powered by immutable [smart contracts](https://iq.wiki/wiki/smart-contract). [Aztec](https://iq.wiki/wiki/aztec) Labs states that any crypto held in zk.money wallets remains entirely under the user's control, that no one can move funds apart from the user, that there is no privileged admin role, and that there is no centralized zk.money server with admin keys to move funds.[\\[1\\]](#cite-id-fvktqsq2gp) Individual operating roles within the system can go down or refuse service, but existing balances can still be withdrawn.[\\[3\\]](#cite-id-6grjopt3vk)​\n\nzk.money uses no [seed phrase](https://iq.wiki/wiki/seed-phrase) and has no separate key to write down; both of a user's keys are derived from a passkey.[\\[3\\]](#cite-id-6grjopt3vk) When a user signs in, the wallet derives the secret key from the passkey and keeps it unencrypted in the browser's storage until sign-out, so a refresh, new tab or closed browser does not prompt again for the passkey.[\\[3\\]](#cite-id-6grjopt3vk) The documentation states that the secret key can show balance and history but cannot move funds.[\\[3\\]](#cite-id-6grjopt3vk) Backing up the account means backing up the passkey through iCloud Keychain, Google Password Manager or 1Password; a passkey stored only on a hardware security key has no backup, and losing that key loses the wallet.[\\[3\\]](#cite-id-6grjopt3vk) zk.money holds no copy of a passkey, there is no escrow, and if the passkey is gone everywhere no one can reconstruct the account.[\\[1\\]](#cite-id-fvktqsq2gp)​\n\n### Oxide\n\nOxide is a separate protocol that runs alongside the [Aztec](https://iq.wiki/wiki/aztec) Network and provides an independent second security layer against vulnerabilities in the network's proving system.[\\[1\\]](#cite-id-fvktqsq2gp) It is built on AWS Nitro Enclaves — a form of Trusted Execution Environment (TEE), a hardware-isolated environment in which code runs sealed from the host — and works by having the user simulate the Aztec Network transaction.[\\[1\\]](#cite-id-fvktqsq2gp) Aztec Labs states that Oxide attests that an operation is valid without learning what the operation contains, so no third party sees transaction details, and that because Oxide's trust assumptions are separate from the [zero-knowledge](https://iq.wiki/wiki/zero-knowledge-proofs-zkps) (ZK) circuits securing the Aztec Network, a fault in one system does not compromise the other.[\\[4\\]](#cite-id-ayzmyx8crt) Its stated purpose is to add another layer of defense against bugs in cryptographic systems.[\\[4\\]](#cite-id-ayzmyx8crt)​\n\nOxide is open source and permissionless in every role. zk.money runs the default enclave and resolver for Oxide, but anyone can run their own enclave and resolver and point a wallet at it.[\\[1\\]](#cite-id-fvktqsq2gp)​[\\[3\\]](#cite-id-6grjopt3vk) In practice, L2BEAT notes, every withdrawal and refund needs both a ZK proof and a signature from a live AWS Nitro enclave running the approved image; the enclave decrypts and reads the operations it handles.[\\[5\\]](#cite-id-ky8jvsxzb3)​\n\n## History\n\nThe original zk.money was a private [decentralized finance (DeFi)](https://iq.wiki/wiki/defi) application running on [Aztec](https://iq.wiki/wiki/aztec) Connect. Aztec Labs states that in its first year the first zk.money reached more than 75,000 unique wallets and over $100 million in volume, which the company presents as early proof of demand for private crypto transfers.[\\[4\\]](#cite-id-ayzmyx8crt) The application stopped accepting deposits in 2023 and shut down in March 2024.[\\[3\\]](#cite-id-6grjopt3vk) Aztec Labs characterizes the 2023 retirement as a consequence not of private transfers failing but of their needing infrastructure that did not yet exist.[\\[4\\]](#cite-id-ayzmyx8crt)​\n\nThat infrastructure was the [Aztec](https://iq.wiki/wiki/aztec) Network itself. Aztec Labs states it spent three years building and launching the network, which it describes as the decentralized privacy layer that lets systems like zk.money scale to mainstream use, and that with the network live it began shipping open-source privacy products on top of it.[\\[4\\]](#cite-id-ayzmyx8crt) The company cites ZKPassport as one such product and presents the revived zk.money as another.[\\[4\\]](#cite-id-ayzmyx8crt) L2BEAT recorded its initial full discovery of zk.money on 1 October 2026.[\\[5\\]](#cite-id-ky8jvsxzb3)​\n\nWhen the wallet returned, priority access was given to early users of the previous zk.money, and immediate access could also be obtained by sharing one's tag with friends.[\\[4\\]](#cite-id-ayzmyx8crt) In the weeks after launch the team said it had fixed deposits that were not being swept so that stuck funds became recoverable, and added a faster-withdrawal option under which a user pays a small tip to skip the proving queue and withdraw in under five minutes.[\\[6\\]](#cite-id-knxfh7awcz) In early October 2026 the project said it was present at token2049 in Singapore, with a representative speaking at the main event and the Privacy Summit.[\\[6\\]](#cite-id-knxfh7awcz)​\n\n## Tags, Payments and Transfers\n\nInstead of copying a long hexadecimal address, each account claims a human-readable tag such as \"yourname.zk.money\" secured by the passkey.[\\[4\\]](#cite-id-ayzmyx8crt) A tag is public by design so that anyone can pay to it, but knowing a tag does not reveal transaction history, and the tag's balance and history are not visible to others.[\\[3\\]](#cite-id-6grjopt3vk) Tags are first-come, first-served, with a small number reserved by the team; a reserved tag can be claimed only by messaging the  account on X from the X account whose handle exactly matches the reserved tag, after which a claim link is sent.[\\[3\\]](#cite-id-6grjopt3vk) On the technical side, tags publicly map to [Aztec](https://iq.wiki/wiki/aztec) addresses and keys and serve two purposes: deriving [Layer 1](https://iq.wiki/wiki/layer-1) (L1) deposit addresses through [Ethereum Name Service (ENS)](https://iq.wiki/wiki/ens) off-chain lookups, and letting wallets read an Aztec address from an on-chain registry to route private [Layer 2](https://iq.wiki/wiki/layer-2) (L2) transfers.[\\[5\\]](#cite-id-ky8jvsxzb3)​\n\nDeposits arrive through single-use [Layer 1](https://iq.wiki/wiki/layer-1) addresses called SIPAs. Anyone can send [DAI](https://iq.wiki/wiki/dai), [USDC](https://iq.wiki/wiki/usdc) or [USDT](https://iq.wiki/wiki/tether) from any wallet or exchange to a recipient's deposit address, and the funds are swept automatically into the recipient's private balance; incoming USDC and USDT are swapped to DAI through the Curve 3pool as they are deposited.[\\[3\\]](#cite-id-6grjopt3vk)​[\\[5\\]](#cite-id-ky8jvsxzb3) Each deposit address is single-use, and users are told to take a fresh one for every payment they receive so that incoming payments cannot be linked, because reusing a SIPA links its deposits.[\\[1\\]](#cite-id-fvktqsq2gp)​[\\[5\\]](#cite-id-ky8jvsxzb3) To avoid handing out an address, a user can send a request link, or, in an [Ethereum](https://iq.wiki/wiki/ethereum) wallet supporting ENS CCIP, a counterparty can type a tag such as bob.zk.money and a resolver derives a fresh deposit address behind it.[\\[3\\]](#cite-id-6grjopt3vk)​\n\nzk.money supports two kinds of shareable links. A payment link holds funds: the sender locks an amount and shares the link, and whoever claims it with their own passkey receives the funds without needing a prior account. Each payment link has a claim window of 1, 7 or 30 days and a refund window that opens immediately, so an unclaimed link can be reclaimed by the sender at any time; a link can never be both claimed and refunded, with the first of the two outcomes being final.[\\[3\\]](#cite-id-6grjopt3vk) A request link is the reverse — it asks someone to pay and gives them a deposit address, holding no funds until someone sends them.[\\[3\\]](#cite-id-6grjopt3vk) Payments inside zk.money are final, and the wallet shows the resolved recipient before confirmation; for a counterparty who is not fully trusted, the documentation recommends sending a payment link, since unclaimed funds return to the sender.[\\[3\\]](#cite-id-6grjopt3vk) Wallets use XMTP, an end-to-end encrypted messaging network, to confirm contacts added by QR code or link and to send payment requests.[\\[5\\]](#cite-id-ky8jvsxzb3)​\n\nAt launch the system supports DAI as its internal asset, and every deposit, payment and withdrawal was initially restricted to below $2,500.[\\[3\\]](#cite-id-6grjopt3vk)​[\\[1\\]](#cite-id-fvktqsq2gp) L2BEAT records those caps as 2,583 DAI each, with deposits sharing a 50,000 [DAI](https://iq.wiki/wiki/dai) capacity that refills over one day.[\\[5\\]](#cite-id-ky8jvsxzb3)​\n\nThe team has outlined further capabilities it says will be possible on Aztec via zk.money, including savings vaults, bank and IBAN payouts, privately funding [Layer 2](https://iq.wiki/wiki/layer-2) accounts, zero-knowledge passport proofs with ZKPassport to unlock larger limits, shared \"pots\" and group bills, and more passkey support.[\\[6\\]](#cite-id-knxfh7awcz) These are plans described by the project rather than released features.\n\n## Fees\n\nA small fee is charged on deposits and withdrawals, taken out of the amount moved. Part of each fee tops up a standalone fee-paying contract that covers network fees for everyone using zk.money, which is why internal activity is free up to a covered amount, and the remainder pays the [Ethereum](https://iq.wiki/wiki/ethereum) [gas](https://iq.wiki/wiki/gas) of moving funds in and out.[\\[3\\]](#cite-id-6grjopt3vk) The project states the free internal cover is currently up to 100 transactions a day with no account data collected, and that this cover is subject to change.[\\[3\\]](#cite-id-6grjopt3vk) A deposit costs $0.35 and a withdrawal costs $0.20.[\\[3\\]](#cite-id-6grjopt3vk)​\n\nClaiming a tag costs $4.90, plus an additional $0.10 to the fee-paying contract, for $5.00 total taken out of the first deposit, which must be at least $15 in [USDC](https://iq.wiki/wiki/usdc), [USDT](https://iq.wiki/wiki/tether) or [DAI](https://iq.wiki/wiki/dai); a $15 DAI deposit leaves roughly $10 after the charge and any swap.[\\[3\\]](#cite-id-6grjopt3vk) The $4.90 portion can be waived in the sign-up flow for users who either prove ownership of a wallet from the prior zk.money system that sunset in 2024 or get one person to claim a tag through their share link; even when waived, a first deposit of at least $5 is required and the user pays $0.60 in fees, leaving $4.40 from a $5 DAI deposit.[\\[3\\]](#cite-id-6grjopt3vk) On L2BEAT's accounting, a sweep pays 0.25 DAI, or 0.5 DAI when claiming a name; registration costs 5 DAI by default including its sweep fee; and the portal takes 0.1 DAI from each deposit and ordinary withdrawal to sponsor [Aztec](https://iq.wiki/wiki/aztec) fees, with sponsorship requiring a registered name or a voucher.[\\[5\\]](#cite-id-ky8jvsxzb3) A dedicated funder contract collects the portal's funding cut, which anyone can swap to AZTEC and bridge as Fee Juice to the L2 fee-paying contract that pays users' Layer-2 fees.[\\[5\\]](#cite-id-ky8jvsxzb3)​\n\n## Privacy and Security Model\n\nzk.money hides senders, amounts and the link between deposits and withdrawals inside its ledger, while names, deposits and withdrawals to [Ethereum](https://iq.wiki/wiki/ethereum) are public by design.[[5]](#cite-id-ky8jvsxzb3)[[4]](#cite-id-ayzmyx8crt) L2BEAT's analysis grades this protection differently for different observers. A public observer sees link privacy preserved, but claiming a name ties it to the funding wallet, the first payment to a new contact reveals that recipient through a handshake, and the first sponsored transaction after registration is tied to the account.[[5]](#cite-id-ky8jvsxzb3) A chain analyst can place the link at risk, since the anonymity set is limited to zk.money's users on [Aztec](https://iq.wiki/wiki/aztec) and the first payment to a name from outside the system is publicly tied to it.[[5]](#cite-id-ky8jvsxzb3)\n\nRisks grow for other adversaries. A network observer — an RPC provider, relayer, indexer or internet service provider — can see web traffic, IP addresses, timing and the [blocks](https://iq.wiki/wiki/block) that deposits and withdrawals land in, and the desktop wallet offers no Tor or proxy setting.[[5]](#cite-id-ky8jvsxzb3) A privileged insider holding protocol keys or plaintext — an upgrade admin, sequencer, view-key holder, TEE vendor, hosted prover or note registry operator — can fully link deposits and recipients, exposing sender, recipient, amount and asset.[[5]](#cite-id-ky8jvsxzb3) A future adversary that archives chain data now and later breaks elliptic-curve cryptography could decrypt historical notes and payment events published to [Ethereum](https://iq.wiki/wiki/ethereum).[[5]](#cite-id-ky8jvsxzb3)\n\nSecurity of escrowed funds rests on a multiproof design: the portal releases funds only after [Aztec](https://iq.wiki/wiki/aztec) proves the withdrawal message and one registered enclave signer co-signs it, so stealing escrowed funds requires both the ZK layer and the enclave layer to fail, while a failure of either breaks privacy.[[5]](#cite-id-ky8jvsxzb3) L2BEAT summarizes that funds can be stolen if Aztec's private execution or refund proof is unsound and the enclave layer also fails, if malicious wallet code obtains a harmful signature or substituted contract lists redirect future payments, or if the controllers of names redirect future payments.[[5]](#cite-id-ky8jvsxzb3) Funds can be lost if a user loses the passkey, if every AWS-attested enclave stops running, or if resolver screening [blocks](https://iq.wiki/wiki/block) an external payment and the recipient lacks tooling to re-derive the deposit address.[[5]](#cite-id-ky8jvsxzb3)\n\nL2BEAT rates the exit window as infinite because the escrow and the approved enclave image are immutable, but notes the protocol does not pass its \"walkaway test\": users cannot fully use it if all centralized participants disappear, since withdrawals and refunds require a live enclave running the approved image on AWS Nitro, and the released wallets also depend on zk.money services.[[5]](#cite-id-ky8jvsxzb3) The project is rated partially reproducible — the contract, desktop wallet, enclave and circuit sources are public and the deployed refund and resolver verifiers match the published circuits, but the approved enclave binary remains unreproduced and the resolver, snapshot and hosted-wallet release sources are unpublished.[[5]](#cite-id-ky8jvsxzb3) Privacy ratings assume zk.money Desktop v0.1.0; the hosted web wallet loads code from zk.money on every visit, which makes its operator an effective insider able to read viewing keys, whereas an independent setup — a modified desktop build pinning verified addresses, serving under its own domain and running the approved enclave on AWS — is possible but untested.[[5]](#cite-id-ky8jvsxzb3)\n\nzk.money relies on the Aztec Ignition trusted setup, a ceremony run by Aztec in 2019 for KZG commitments over the BN254 curve with 176 participants and publicly open participation, which L2BEAT grades at its lowest risk level; the circuits use the UltraHonk (Plonk) proof system.[[5]](#cite-id-ky8jvsxzb3)\n\n### Compliance Screening\n\nScreening is applied in off-chain services rather than on-chain. The wallet sends [Ethereum](https://iq.wiki/wiki/ethereum) addresses to Predicate, through zk.money, for screening, while funding a deposit SIPA directly avoids this; the relayer screens token movements against OFAC sanctions lists and optionally Predicate, and self-submitted sweeps and withdrawals skip relayer screening.[[5]](#cite-id-ky8jvsxzb3) The name resolver separately screens deposit addresses and funders against OFAC before notifying the recipient on L2; a blocked payment leaves funds at an address unknown to the wallet, recoverable only with the recipient's own tooling and L1 authorization.[[5]](#cite-id-ky8jvsxzb3)\n\n## Contracts and Governance\n\nThe core [smart contracts](https://iq.wiki/wiki/smart-contract) of both the [Aztec](https://iq.wiki/wiki/aztec) Network and zk.money are immutable.[\\[5\\]](#cite-id-ky8jvsxzb3) On [Ethereum](https://iq.wiki/wiki/ethereum), the ZkMoneyPortal contract holds the escrow and releases funds only on a proven Aztec L2-to-L1 message co-signed by a registered TEE signer; anyone can register a TEE signer with a fresh AWS Nitro attestation of an approved enclave image, with two signers registered at the time of L2BEAT's discovery.[\\[5\\]](#cite-id-ky8jvsxzb3) Attestations are validated through a NitroValidator and CertManager whose only trust anchor is the hardcoded AWS Nitro root certificate.[\\[5\\]](#cite-id-ky8jvsxzb3) Deposit and registration addresses are deployed as deterministic clones by permissionless factories, and the portal, once Aztec's canonical rollup changes, can be permanently frozen by anyone — a freeze that stops new deposits and enables refunds at the last proven checkpoint without stopping funds already in from coming out.[\\[5\\]](#cite-id-ky8jvsxzb3)​[\\[3\\]](#cite-id-6grjopt3vk)​\n\nDespite immutable escrow logic, naming and service infrastructure remains under Aztec Labs' control. Two Aztec Labs externally owned accounts (EOAs) govern the \\*.zk.money namespace: one owns the NameRegistry and can replace its registration, metadata and resolver contracts and change the domain owner, as well as bless deposit-address implementations; the other authorizes or refuses every name claim and can sign custom registration fees and add permanent fee beneficiaries.[\\[5\\]](#cite-id-ky8jvsxzb3) Because these controllers can reassign names and redirect future payments, and because Aztec Labs owns zk.money in [ENS](https://iq.wiki/wiki/ens) (reclaimable by the DNS holder) and controls the hosted wallet, desktop releases and the two unsigned contract lists both wallets currently use, L2BEAT identifies name governance and wallet distribution as the system's principal centralization points.[\\[5\\]](#cite-id-ky8jvsxzb3) Claims for names require the domain owner's signature from a closed-source server with a name blocklist, and a registered name is required to access an account on a new device.[\\[5\\]](#cite-id-ky8jvsxzb3)​\n\nWithdrawals and refunds are co-signed by two further Aztec Labs EOAs acting as the portal's registered TEE signers; without a signature from a registered TEE signer, no funds can leave the portal.[\\[5\\]](#cite-id-ky8jvsxzb3) Supporting contracts handle the mechanics: a swap-on-withdraw escrow lets a withdrawal pay out in [USDC](https://iq.wiki/wiki/usdc), [USDT](https://iq.wiki/wiki/tether) or [ETH](https://iq.wiki/wiki/ether-eth) by routing [DAI](https://iq.wiki/wiki/dai) through the Curve 3pool or [Uniswap](https://iq.wiki/wiki/uniswap) within fixed [slippage](https://iq.wiki/wiki/slippage) bounds; a default payout executor pays recipients and relayer tips; and a set of UltraHonk verifiers check the refund and resolver circuits against hardcoded verification keys.[\\[5\\]](#cite-id-ky8jvsxzb3) The resolver operator that derives deposit addresses can link a wallet's addresses because they share a secret, but every lookup must carry a ZK proof matching the user's registered keys and L2 address, preventing the operator from redirecting payments, and users may choose a custom resolver operator.[\\[5\\]](#cite-id-ky8jvsxzb3)​","categories":[{"id":"projects-and-protocols","title":"projects-and-protocols"}],"tags":[{"id":"Privacy"},{"id":"Payments"},{"id":"Ethereum"}],"images":[{"id":"QmaXbZhbxVf32853CZt1THzNQiR4xyaZ1xnJJcharRcK9x","type":"image/jpeg, image/png"}],"media":[{"id":"QmaorEuLf2o4tzuRm6bmWEDTQRTGCyR7GFHGiQViAhHpUr","name":"Crypto-Wallet-with-Anonymous-Stablecoins-e1790690117470.webp","source":"IPFS_IMG","thumbnail":"QmaorEuLf2o4tzuRm6bmWEDTQRTGCyR7GFHGiQViAhHpUr","caption":""},{"id":"QmV8P5dywBXjKWrSTUJnPsZ6Eiq8LZ8u4BfcpXaiQvBEDy","name":"HTZX5zHbcAAsJrL.webp","source":"IPFS_IMG","thumbnail":"QmV8P5dywBXjKWrSTUJnPsZ6Eiq8LZ8u4BfcpXaiQvBEDy","caption":""}],"metadata":[{"id":"rootdata_profile","value":"https://www.rootdata.com/Projects/detail/zk.money?k=MjYwNzg="},{"id":"website","value":"https://zk.money"},{"id":"twitter_profile","value":"https://x.com/zk_money"},{"id":"github_profile","value":"https://github.com/aztec-labs-eng/zkmoney-public"},{"id":"references","value":"[{\"id\":\"fvktqsq2gp\",\"url\":\"https://docs.zk.money/\",\"description\":\"zk.money open source self-custodial private wallet\",\"timestamp\":1791507812865},{\"id\":\"dousgnm9f3\",\"url\":\"https://www.rootdata.com/projects/detail/zkmoney?k=MjYwNzg%3D\",\"description\":\"zk.money privacy wallet built by Aztec Labs\",\"timestamp\":1791507812865},{\"id\":\"6grjopt3vk\",\"url\":\"https://docs.zk.money/docs/faq\",\"description\":\"deposit from Ethereum and withdraw at any time\",\"timestamp\":1791507812865},{\"id\":\"ayzmyx8crt\",\"url\":\"https://aztec-labs.com/blog/zk-money-is-back\",\"description\":\"zk.money is back, published 29 September 2026\",\"timestamp\":1791507812865},{\"id\":\"ky8jvsxzb3\",\"url\":\"https://l2beat.com/privacy/projects/zkmoney\",\"description\":\"initial full discovery recorded 1 October 2026\",\"timestamp\":1791507812865},{\"id\":\"knxfh7awcz\",\"url\":\"https://x.com/zk_money\",\"description\":\"post-launch fixes and faster withdrawals, self-reported\",\"timestamp\":1791507812865}]"},{"id":"main-image-origin","value":"{\"imageId\":\"QmaXbZhbxVf32853CZt1THzNQiR4xyaZ1xnJJcharRcK9x\",\"originalId\":\"QmaXbZhbxVf32853CZt1THzNQiR4xyaZ1xnJJcharRcK9x\"}"},{"id":"commit-message","value":"Create zk.money wiki"}],"events":[{"type":"CREATED","title":"Original zk.money launched","date":"2021-01-01","description":"Original zk.money private wallet launched on Aztec Connect.","link":"https://aztec-labs.com/blog/zk-money-is-back","multiDateStart":null,"multiDateEnd":null,"country":"United Kingdom","continent":"Europe","id":"c2d0cbb6-8efc-414e-8ca0-156ea7dcd5d5"},{"title":"Original zk.money stopped accepting deposits","date":"2023-03-01","type":"DEFAULT","description":"Original zk.money application stopped accepting new deposits.","link":"https://aztec-labs.com/blog/zk-money-is-back","country":"United Kingdom","continent":"Europe","multiDateStart":null,"multiDateEnd":null,"id":"31a9f0eb-d2c0-471e-9c08-13cd91ee0f3e"},{"type":"DEFAULT","title":"Original system shut down","date":"2024-03-01","description":"Original system shut down","link":null,"multiDateStart":null,"multiDateEnd":null,"id":"9e6a0f4f-cd26-456f-bec6-2df591bceb8c"},{"type":"DEFAULT","title":"Revival launched (announcement)","date":"2026-09-01","description":"Revival launched (announcement)","link":null,"multiDateStart":null,"multiDateEnd":null,"id":"ca39e157-5926-4f48-8d52-b01a608d7663"},{"title":"zk.money relaunched on Aztec Network","date":"2026-09-01","type":"DEFAULT","description":"zk.money relaunched as a new private wallet on the Aztec Network.","link":"https://aztec-labs.com/blog/zk-money-is-back","country":"United Kingdom","continent":"Europe","multiDateStart":null,"multiDateEnd":null,"id":"aaa22abf-eb39-4883-81e0-a17620155db8"}],"linkedWikis":{"founders":[],"blockchains":["ethereum"],"speakers":[]},"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0xd5893989b9952c6568a99F854795AcC5Ae480D56"},"language":"en","operator":{"id":"0xd5893989b9952c6568a99F854795AcC5Ae480D56"}}