# Private shared state in Aztec smart contracts, using Taceo

**URL:** <https://forum.aztec.network/t/private-shared-state-in-aztec-smart-contracts-using-taceo/7768>\
**Category:** Aztec\
**Tags:** apps, smart-contracts\
**Created:** [April 29, 2025, 7:39pm UTC](https://forum.aztec.network/t/private-shared-state-in-aztec-smart-contracts-using-taceo/7768 "2025-04-29T19:39:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.aztec.network/mike/32/7_2.png) [@Mike](https://forum.aztec.network/u/Mike)\
**Post date:** [April 29, 2025, 7:39pm UTC](https://forum.aztec.network/t/private-shared-state-in-aztec-smart-contracts-using-taceo/7768/1 "2025-04-29T19:39:04Z")

</div>

The guys from Taceo visited the Aztec offices a while back, and built a PoC of an Aztec smart contract with private shared state (that is, state that no one in the world knows, but which you can perform computations over). Here’s a write up of the PoC.

Hopefully this explains a useful pattern which people can adopt, to build Aztec smart contracts with private shared state.

> **[Private shared state on Aztec, with Taceo's co-SNARKs - HackMD](https://hackmd.io/@aztec-network/ByZ6tymhyl)**
>
> Taceo enables a network of MPC nodes M1, M2, M3 (currently 3) to perform computations over secret-shared data. We spent time thinking about how this can enable private shared state on Aztec.