Panther Protocol Announcements

Panther’s latest DAO proposal, PIP-41, has passed! The Panther DAO voted in favor of restoring the required $ZKP balances for Panther’s V1 Base deployment and the non-$ZKP balances required for testing and withdrawals, and also decided to start Panther’s mainnet build & deployment on Ethereum, plus authorizing compliance DAO funding through DAO grants. Onwards and upwards!

Yesterday, PIP-41 went live and has, as of now, reached ~56% of the votes required to pass. The proposal aims to restore the required $ZKP balances for Panther’s V1 Base deployment and the non-$ZKP balances required for testing and withdrawals. It also proposes starting Panther’s mainnet build & deployment on Ethereum and authorizing compliance DAO funding through DAO grants. If you haven’t already, VOTE on the proposal here: https://snapshot.box/#/s:pantherprotocol.eth/proposal/0x8e7efd14e240faf6755d72af437f392f8200b7a55c903e54dcef8716d5f346f7

PIP-41 is now LIVE for voting! This proposal aims to restore the required $ZKP balances for Panther’s V1 Base deployment and the non-$ZKP balances required for testing and withdrawals. It also proposes starting Panther’s mainnet build & deployment on Ethereum and authorizing compliance DAO funding through DAO grants. Vote here: https://snapshot.box/#/s:pantherprotocol.eth/proposal/0x8e7efd14e240faf6755d72af437f392f8200b7a55c903e54dcef8716d5f346f7

Panther’s next DAO proposal, PIP-41, will likely go live tomorrow! $ZKP holders can vote only with the tokens they hold in their own wallets, not those deposited in Panther’s shielded pool, so be prepared and position yourself before the proposal goes live!

The PIP-41 draft has been shared on the Panther forum! This proposal aims to restore the required $ZKP balances for Panther’s V1 Base deployment and the non-$ZKP balances required for testing and withdrawals. Furthermore, it is proposed to start Panther’s mainnet build & deployment on Ethereum, and to authorize compliance DAO funding to be handled through DAO grants. Check out the complete proposal draft here: https://forum.pantherprotocol.io/t/pip-41-restore-base-v1-deployment-and-initiate-ethereum-deployment/550

Panther x Igra: Exploring Privacy for Kaspa Panther and Igra are exploring bringing Panther’s privacy-preserving infrastructure to the Kaspa ecosystem. A Panther deployment on Igra could bring confidential DeFi, private transfers and zero-knowledge compliance capabilities to Igra’s high-performance EVM-compatible environment. The next step is exploring demand and potential use cases across the Igra ecosystem. Read more: https://blog.pantherprotocol.io/panther-and-igra-explore-privacy-infrastructure-for-the-kaspa-ecosystem/

Dear Panther community, It is time for a new weekly update! We are happy to share that the internal MASP transfers have been successfully enabled on Panther’s Base deployment. All identified bugs have been solved and verified. This excludes the KYT changes and internal MASP transfer daily limits. Furthermore, the following updates are now live in production: ✅ List Views: Improved amount formatting across all lists. ✅ UI Polish: Optimized button widths on some pages for better visual balance. ✅ Voucher Management: Added automated sorting of vouchers by creation date. ✅ Navigation: Fixed page loading behavior to automatically scroll to the top upon opening. Minor tasks and UI fixes have also been successfully deployed to Canary on both Polygon and Base, and the previously shared voucher issue has been resolved. We will keep you posted about the progress. Have a great Friday and weekend ahead!

Yesterday, we learned that the Panther Base deployment was attacked. The Base deployment was not yet in production. No user funds were compromised. The attacker managed to steal approximately 5.12M ZKP and 0.12 ETH by submitting a Reality.eth proposal which was not challenged within the applicable challenge and cooldown period. The dev team has restored the affected proxy implementations. The attack was possible because protections designed to disable the Reality.eth module when there is no active governance proposal had not been enabled on the Base deployment. Panther DAO has taken measures to address the Reality.eth configuration on Base. The relevant teams are also confirming that the equivalent protections are properly enabled across Panther’s other deployments. A fuller incident report will follow once the review of the incident is complete.

Stablecoins have become a cornerstone of DeFi, but almost every transfer is still completely transparent. Our latest blog explains why confidential stablecoin transfers matter and how Panther's Multi-Asset Shielded Pool (MASP) enables programmable privacy—allowing operators to define their own compliance and access requirements while using existing stablecoins within the DeFi ecosystems where liquidity already exists. Read more: https://blog.pantherprotocol.io/confidential-stablecoin-transfers-how-panther-enables-programmable-privacy/

Panther’s latest DAO proposal, PIP-40, has passed! The DAO voted in favor of minting and releasing an additional 4,000,000 $ZKP to the V1 Privacy Rewards contract, while simultaneously reducing the mainnet reward emission rate to ensure that privacy rewards remain available for a substantially longer period and to reduce unnecessary token emissions into the market. Onwards!

PIP-40 is now LIVE for voting! This proposal authorizes the minting and release of an additional 4,000,000 $ZKP to the Privacy Rewards contract and sets the mainnet privacy reward emission rate to approximately 16,000 $ZKP per day. The objective of this proposal is to restore mainnet's privacy reward distributions while aligning ongoing emissions more closely with the protocol's usage. Check out the proposal and VOTE through here: https://snapshot.box/#/s:pantherprotocol.eth/proposal/0x6163da57aa02a4002b83b65f72f222a7110d91e2d03e68c2823d98325b55b854

Panther’s next DAO proposal, PIP-40, will likely go live tomorrow. $ZKP holders can only vote with the tokens they hold in their own wallets, and not with those deposited in Panther’s shielded pool, so be prepared and cast your vote later this week!

The PIP-40 draft has been shared on the Panther forum today! This proposal authorizes the minting and release of an additional 4,000,000 $ZKP to the V1 Privacy Rewards contract while simultaneously reducing the mainnet reward emission rate to better reflect the protocol’s current TVL. The objective of this proposal is to ensure that privacy rewards remain available for a substantially longer period while reducing unnecessary token emissions into the market. Check out the complete proposal draft here: https://forum.pantherprotocol.io/t/pip-40-increase-v1-privacy-reward-allocation-and-adjust-reward-emissions-on-polygon/546

Dear Panther community, Today, we are sharing the latest update on what has been worked on this week. This week’s update mostly focuses on Panther’s Base deployment: ✅ The voucher update has been implemented on Polygon and Base, per PIP-39. ✅ The dev team’s currently working on enabling internal MASP transfers on Base. ✅ The latest dApp fixes on Base are currently being tested and will be refined if needed. Other tasks, such as zAccount UI improvements and AMM refill voucher-related ones, are also being looked into. We will keep you posted as we move forward with getting Panther’s Base deployment ready!

Panther’s latest DAO proposal, PIP-39, has passed! The recharger voucher reserve will be increased to 50,000 PRP, and the account activation voucher to 1,000,000 PRP. The internal MASP transfers will be enabled on Panther’s Base deployment with a $25,000 daily limit. Thanks to everyone who voted! Onwards!

PIP-39 is now LIVE for voting! This proposal introduces a parameter change to vouchers across both the Polygon and Base deployments and re-enables the internal MASP transfers on Base. The voucher parameter changes are intended to make both voucher systems last much longer than before under current usage patterns. Check out the proposal details and VOTE: https://snapshot.org/#/s:pantherprotocol.eth/proposal/0x3b43e87c025b6dacce1849ab7d7bf348073eb5567bf88e46d11a8567a4c1f98d

Panther’s next DAO proposal, PIP-39, will likely go live tomorrow. $ZKP holders can only vote with the tokens they hold in their own wallets, and not with those deposited in Panther’s shielded pool, so be prepared! LFG

The PIP-39 draft has been shared on the Panther forum today! This proposal introduces a parameter change to vouchers across both deployments (Polygon and Base) and re-enables internal MASP transfers on Base. The voucher parameter changes are intended to make both voucher systems last much longer than before under current usage patterns. Check out the complete proposal draft here: https://forum.pantherprotocol.io/t/pip-39-voucher-update-internal-transfer-for-base-deployment-testing/545

Maximal Extractable Value (MEV) costs users hundreds of millions of dollars annually across blockchain networks, often worsening the overall UX in DeFi. On this blog, we explain how Panther mitigates the negative effects of MEV through its privacy-preserving infrastructure. https://blog.pantherprotocol.io/how-panther-protocol-shields-users-from-mev-privacy-as-a-powerful-defense/

We are going live tomorrow at 5:00 pm UTC on Web3 Global with Access Protocol, GVNR, Spark, Alvey, Shido Network, Shift, Kaspa, and multiple speakers from other projects to discuss real-world adoption and payments in crypto. https://x.com/web3globalmedia/status/2072734497070629200?s=20 We hope to see you there!