# Bypassing our number of nullifiers per tx kernel constraint for large number of token transfers **URL:** \ **Category:** Aztec\ **Created:** [April 9, 2024, 3:23pm UTC](https://forum.aztec.network/t/bypassing-our-number-of-nullifiers-per-tx-kernel-constraint-for-large-number-of-token-transfers/5343 "2024-04-09T15:23:59Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![spalladino](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.aztec.network/spalladino/32/32_2.png) [@spalladino](https://forum.aztec.network/u/spalladino)\ **Post date:** [April 9, 2024, 5:30pm UTC](https://forum.aztec.network/t/bypassing-our-number-of-nullifiers-per-tx-kernel-constraint-for-large-number-of-token-transfers/5343/2 "2024-04-09T17:30:19Z")
> [@rahul-kothari](#): > > Commitments become a problem when multiple parties are involved since each has to be individually revealed. It might not work for some applications and it leaks privacy. One idea is to use encryption instead of commit-reveal schemes. Shout-out to the Wonderland team who used LHE a while back to build their betting oracle. They used LHE for accumulating the total number of participants (not the total funds, those were kept in public), but maybe something similar could be done for balances. > [@Homomorphic Encryption Addition](https://forum.aztec.network/t/homomorphic-encryption-addition/2705): > > Public state is great, it allows us to work on a synced global state. If we need to perform operations on a globally available state, to which we don’t have access on private-land, we can just call a public function that for example increases the total\_users counter. doing this in private-land would require a contract to have a “leaked” Note which users would need to orderly nullify and update, forcing them to have reverted transactions if another user already has an in-transit tx that creat… > **[GitHub - defi-wonderland/aztec-coin-toss-pvp](https://github.com/defi-wonderland/aztec-coin-toss-pvp)** > > Contribute to defi-wonderland/aztec-coin-toss-pvp development by creating an account on GitHub. --- _[View the full topic](https://forum.aztec.network/t/bypassing-our-number-of-nullifiers-per-tx-kernel-constraint-for-large-number-of-token-transfers/5343)._