Changelog
What changed in ephemeral and in these docs, newest first.
| Date | Change |
|---|---|
| 2026-11-11 | Client 0.2.18: on networks read over RPC (Arbitrum and Elysium in beta), the registrant check (H1) now blocks when the ERC-6538 registry could not be read, and checks each destination and gas sender against the registry directly. ETH that arrives inside the announcement transaction, or shortly before it, is now found as a payment. A zero-value plain transaction from a stealth address now counts as a past destination. Reported through the bug bounty by Rusdi, Akbar and reaper. |
| 2026-11-11 | Site: EPH launches on Ethereum mainnet. ephemeral stays multichain, with Arbitrum, Base and Elysium in beta. The Proof Wall shows the deployed contracts. |
| 2026-11-09 | Docs: ephemeral is multichain. New pages ephemeral on Elysium (status, setup, contracts, privacy on a new chain) and One meta-address, every chain (what carries over between chains, what stays separate, how cross chain moves can link you). Contracts and networks lists Ethereum, Arbitrum, Base and Elysium with chain ids, start blocks and data sources. The home page, the FAQ and the roadmap name the supported networks. |
| 2026-11-09 | Client 0.2.17: Arbitrum One is a beta network (open the app with ?l2). The ERC-5564 Announcer and the ERC-6538 Registry are at the same addresses there as on Ethereum. Scans and checks read over the public Arbitrum RPC, not an explorer, so the history check (H3) warns that past withdrawals could not be read. A scan of everything since the Announcer was deployed on Arbitrum (June 2024) reads many blocks: pick a shorter range for a faster scan. Amounts show in ETH. With Read from set to RPC, the registry lookup behind the key wallet check (H1) now reads your node too, so the app asks Blockscout nothing on any network. |
| 2026-11-09 | Client 0.2.16: Elysium, the HYPE L2 from Kinetiq, is a beta network (open the app with ?l2). The ERC-5564 Announcer and the ERC-6538 Registry are at the same addresses there as on Ethereum. Scans and checks read over Elysium's public RPC, since its explorer is not public yet, so the history check (H3) warns that past withdrawals could not be read. Amounts show in HYPE. |
| 2026-11-08 | Client 0.2.15: the collector check (H3) no longer reads every history as incomplete. An address without code, as the app's node client reports it, counts as no code again, and the code a past destination had at the block of the send is now really read there. The key wallet, payer and gas checks (H1, H2, H5) also catch a destination typed as the OP stack alias of a linked L1 contract, and gas from the real address of a registrant recorded under its alias; H1 also blocks every wallet that published your meta-address in the registry. The timing advice warns when the time the funds arrived cannot be read. On Base a ranged scan covers the days its label says. A sped-up payment keeps its new hash, a cancelled or failed payment or registration is no longer shown as done, and Finish payment is offered only to the account that announced the payment. When this wallet has another meta-address registered, the app warns that payments to it will not show with the keys just made. Reported through the bug bounty. |
| 2026-11-08 | Client 0.2.14: the P256VERIFY precompile (0x...0100) and the system address (0xff...fe) are blocked as destinations like the zero address. The gas check (H5) blocks gas sent by the destination itself, and an OP stack deposit alias counts as the wallet behind it for the key wallet check (H1), the payer check (H2) and H5. A token Transfer of zero or an ERC-1155 move of zero makes no payer and no arrival. The collector check (H3) reads the code of each address an ETH send went to at the block of that send, so a forwarding EIP-7702 delegation that was cleared later still marks the history incomplete, and code that cannot be read counts as code. A shared receipt link always points to ephemeral.money. Reported through the bug bounty. |
| 2026-11-06 | Client 0.2.13: an Unlinked Receipt verifies only when its announcement is an ERC-5564 scheme 1 announcement (secp256k1 with view tags) for that one-time address; an announcement under another scheme id no longer proves it. The Proof Wall reads a node from a ?rpc= link only next to a public node, on Ethereum mainnet only, and shows nothing as checked when the two disagree; a node from a link is never read on its own. The leak study binds a token payment to its own announcement: another announcement's claim, short metadata or token dust no longer changes which asset was paid, and announcements under another scheme id are left out. Reported through the bug bounty. |
| 2026-11-04 | Client 0.2.12: the payer check (H2) no longer calls a destination safe when ETH reached the address through a contract that the sender of the call did not fund: who really paid cannot be read then, and Withdraw stays locked. The gas check (H5) counts ETH sent in the same transaction as a token by anyone who did not send the token, says history incomplete while past withdrawals are not fully read, and takes the reason an asset is unknown, not only a yes or no. A token withdrawal keeps the ETH for gas while any of the same token is left, and lists the tokens on the address again right before the ETH is sent. A token balance that cannot be read counts as unknown, not zero. |
| 2026-11-02 | Client 0.2.11: the viewing key comes from the low form of the signature (min(s, n - s)), so one wallet always gives one meta-address, and a wallet that returned the other form before still finds its payments; both key signatures must come from the connected account. The payer check (H2) on an address that already sent a transaction needs everything that came in to equal its balance plus everything it sent and paid in fees, reads tokens that reached the address before its announcement window, and runs again on fresh chain data right before a withdrawal is signed. A token balance that cannot be read counts as unknown, not zero. A token withdrawal sends on the ETH left over from gas only after the token has left the address, and only after its last token. The collector check (H3) counts plain ETH sent to a contract and a payment address that has code (an EIP-7702 delegation) as incomplete history, and reads the chain head only after the explorer has answered. |
| 2026-10-31 | Client 0.2.10: the collector check (H3) counts an ETH send that carries calldata (a contract call such as a swap) or creates a contract as incomplete history, and reads ERC-1155 transfers out of a payment address. The payer check (H2) reads ERC-1155 senders and operators as payers, and every known payer is now blocked as a destination, with no setting. For a token payment the gas check (H5) also looks at where its ETH for gas came from and blocks when it came from a wallet linked to you. The precompiles and, for a token withdrawal, the token contract itself are blocked as destinations. The timing advice counts from when the funds arrived, not from the announcement. Reads that carry your payment addresses never fall back to your wallet's RPC; when your endpoint refuses one, the app says to set an RPC in Settings. A truncated or malformed meta-address is refused before any payment. Send pays only after the announcement has succeeded on chain for that one-time address: when it was replaced, cancelled or failed, or did not confirm in time, nothing is sent, and Finish payment checks the announcement again and is no longer offered once the payment went out. Reported through the bug bounty. |
| 2026-10-26 | Client 0.2.9: the payer check (H2) now reads who paid from the payment itself on chain: the sender of each transaction or token transfer that funded the address, as well as whoever made the announcement. While any of them cannot be read, Withdraw stays locked. The asset and the amount shown as sent come from the chain, not from the announcement, so payments with a short announcement (most of them on mainnet) show their token and get the gas check (H5) and the unknown token warning; when the asset cannot be read, H5 treats the payment as a possible token payment. A second announcement for the same address no longer replaces the payment: every announcement is kept, the one the chain confirms is used, and the payment shows a warning. Reported through the bug bounty. |
| 2026-10-22 | Client 0.2.8: the collector check (H3) now reads every token transfer a payment address signed from the call itself (transfer and transferFrom), so a withdrawal counts even when the token logs no Transfer or logs it in a non-standard way, and any other call counts as incomplete history. Withdraw for a token needs a contract at the token address; a token whose arrival left no standard Transfer log shows a warning that withdrawing it may link payments, and H3 never calls a destination unused for it. Reported through the bug bounty. |
| 2026-10-22 | Client 0.2.7: the collector check (H3) now needs the on-chain nonce of every payment address it reads. A missing nonce, or one that could not be read, counts as incomplete history instead of being skipped, and nonce keys match in any letter case. The withdrawal policy steps on the Build page say so. |
| 2026-10-22 | Client 0.2.6: on networks with Glamsterdam (Sepolia since 6 October), the collector check (H3) reads ETH withdrawals from the new ETH transfer logs (EIP-7708), including ETH that a contract call moved out, and no longer calls the history incomplete after an ETH withdrawal. New research page Glamsterdam on Sepolia: what these logs make cheaper to read, for wallets and for anyone watching. |
| 2026-10-21 | Treasury policy on the Proof Wall: We don't burn. We hire growth. Two buckets (Privacy Reserve and Integrations), paid per delivered thing, in ETH, one KPI per spend, every payment public. The FAQ answers why to hold EPH. |
| 2026-10-21 | Client 0.2.5: a scan limited to the last 7, 30 or 90 days now counts as incomplete history for the collector check (H3), both for past withdrawals and for your own payment addresses, so H3 says history incomplete instead of calling a destination unused when an older payment could have gone there. The scan now looks back over everything by default; 7, 30 and 90 days stay selectable. Reported through the bug bounty by @0x123van, and fixed before any payment aged past the old 30 day window. Entry in the review log. |
| 2026-10-21 | New page Receipts: what we shipped and fixed, including what failed first, each with its proof (transaction, commit or review log entry). /llms.txt now follows the llms.txt format, and the FAQ starts with the 10 questions people ask most. |
| 2026-10-20 | Bug bounty: rewards are paid in ETH, USDT or EPH, and we choose the asset. Tiers are now set in ETH and paid from the treasury, or the equivalent in USDT or EPH. Researchers who keep testing with us can receive EPH with vesting. |
| 2026-10-20 | The short link ephemeral.money/security now opens the bug bounty page. |
| 2026-10-20 | Client 0.2.4: the collector check (H3) now reads the past withdrawals of every payment address, also one that never sent a transaction itself, so a token moved out by a relayer counts like any other withdrawal. When the history of any payment cannot be read, H3 says it is incomplete instead of calling a destination unused. Reported through the bug bounty. Docs: the gas section now says the relayer is planned, not live. |
| 2026-10-15 | Client 0.2.2: Buy privately shows the expected EPH and the minimum you accept before you buy, read from the pool, with a slippage choice of 1%, 3% or 5%. The buy stays off until launch. |
| 2026-10-15 | Client 0.2.1: a Pay me privately card with a bio line and a share image, and Unlinked Receipts: prove one received payment with a signature from its one-time address, checked by anyone on /receipt, main wallet never shown. A page for projects. Stealth Buy 1.1 (not on mainnet yet): a 0.5% fee in ETH, 20% of it to referrers. |
| 2026-10-12 | Mainnet leak scan rerun to block 26,176,190: 25,688 stealth addresses, 38.92% of withdrawn ones traced (9,751 of 25,057). |
| 2026-10-07 | Stealth Buy router for Uniswap v4 built and tested. Roadmap: new phase, The Hook. Client: token withdrawals, finish a payment whose second step did not go through, payments announced but not yet paid are marked, build stamp in the footer. |
| 2026-10-06 | Client beta built: keys from one signature with a determinism check, send, scan, withdraw with the H1–H5 checks. Tested end to end and cross-checked against the ScopeLift SDK. Opens to partners first. |
| 2026-10-06 | ERC-5564 scheme 1 test vectors published. Privacy score and live stats pages. Docs: 31 pages, with guides for getting started, receiving and sending, client security, networks and building with ERC-5564. |
| 2026-10-06 | Docs preview: 21 pages across start, using, protocol, research, security and reference. Long-term roadmap. |
| 2026-10-05 | Mainnet leak scan completed: 25,645 stealth addresses, 38.97% of withdrawn ones traced. |
Stay unlinked.