> ## Documentation Index
> Fetch the complete documentation index at: https://docs.palliora.org/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](https://docs.palliora.org/defi/reference/status-and-limits.md) and [Network reference](https://docs.palliora.org/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](https://docs.palliora.org/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](https://docs.palliora.org/defi/build/relayer-api.md) and [Fees](https://docs.palliora.org/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](https://docs.palliora.org/defi/reference/security-and-audits.md).

**2026-07-15. ZK ceremony finalised.** The proving keys come from this ceremony. See [ZK ceremony](https://docs.palliora.org/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](https://docs.palliora.org/defi/learn/concepts/accountable-privacy-and-disclosure.md) and [Palliora integration](https://docs.palliora.org/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](https://docs.palliora.org/defi/reference/status-and-limits.md). |
| A withdrawal costs about 5 bps. | The pool's withdrawal fee is 0 bps. See [Fees](https://docs.palliora.org/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](https://docs.palliora.org/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](https://docs.palliora.org/defi/reference/network-reference.md). |

## Next

* [FAQ](https://docs.palliora.org/defi/reference/faq.md)
* [Rename map](https://docs.palliora.org/defi/reference/rename-map.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.