> For the complete documentation index, see [llms.txt](https://docs.palliora.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.palliora.org/defi/reference/changelog.md). # Changelog Changes to the Palliora DeFi protocol and product that matter to users and integrators, newest first. For what is true now, use [Status and limits](/defi/reference/status-and-limits.md) and [Network reference](/defi/reference/network-reference.md). ## 2026 ### October **2026-10-06. Ethereum pool upgrade (contract revision 2).** The Ethereum pool runs a new implementation. The pool address did not change. This upgrade changes what a client must do. * A deposit must carry a fee of 0. * Nullifiers, commitments and memo words must be below the field size. * A tree update of size zero reverts. * The pool screens the transaction origin and the registration signer against the sanctions list, as well as the sender. * The Ethereum Paymaster was replaced. The two earlier Paymasters are retired. The Paymaster address is part of the fee data and the proof binds it, so a client must use the current one. See [Network reference](/defi/reference/network-reference.md). ### September **2026-09-30. HyperEVM mainnet pool deployed.** The pool was deployed from the same code as the Ethereum implementation above. HyperEVM has no ERC-4337 bundler, so a relayer submits transactions. Fees are a flat amount in USDC. See [Relayer API](/defi/build/relayer-api.md) and [Fees](/defi/reference/fees.md). ### July **2026-07-30. Ethereum pool and request manager deployed.** The Ethereum pool went live in block 25,647,575. The disclosure request manager was deployed in block 25,648,509. **2026-07-17. ABDK report 1.2.** The final version of the audit report. See [Security and audits](/defi/reference/security-and-audits.md). **2026-07-15. ZK ceremony finalised.** The proving keys come from this ceremony. See [ZK ceremony](/defi/reference/zk-ceremony.md). ## Before mainnet * **Disclosure.** A step where guardians approved a request in a transaction was removed before mainnet. A guardian now answers a request directly, with a permit sent to the revoker, so partial decryptions are never published. The setup of the guardians' key is a verifiable DKG with no leader. The revoker keeps its report of what it de-anonymized on Palliora DA. See [Accountable privacy and disclosure](/defi/learn/concepts/accountable-privacy-and-disclosure.md) and [Palliora integration](/defi/learn/concepts/palliora-integration.md). ## Compared with older documentation Older Veilnyx pages say some things that are no longer true. This table lists them. | Older pages said | Today | | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- | | Palliora DeFi is in private beta before mainnet. | It is live on Ethereum and on HyperEVM. See [Status and limits](/defi/reference/status-and-limits.md). | | A withdrawal costs about 5 bps. | The pool's withdrawal fee is 0 bps. See [Fees](/defi/reference/fees.md). | | Guardians vote and click "Give Permission" in a transaction. | There is no such step. A guardian answers the revoker directly. | | It runs on OP Sepolia and Sepolia. | The test networks are Sepolia and HyperEVM testnet. OP Sepolia is not deployed. | | Transfers are 100% anonymous. | Privacy depends on how many people use the pool. Deposits and withdrawals are public. See [Privacy model](/defi/learn/concepts/privacy-model.md). | | Shield Score rewards and Privacy Makers and Takers. | They are not part of the product. | | Uniswap is live. Lido and Aave are coming. | On Ethereum, Uniswap, Aave, Lido and Morpho are live. See [Network reference](/defi/reference/network-reference.md). | ## Next * [FAQ](/defi/reference/faq.md) * [Rename map](/defi/reference/rename-map.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.palliora.org/defi/reference/changelog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.