# Establishment of the CCC Operational Multisig **URL:** \ **Category:** Projects\ **Created:** [July 29, 2026, 2:23pm UTC](https://research.lido.fi/t/establishment-of-the-ccc-operational-multisig/11765 "2026-07-29T14:23:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Elena\_S](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/elena_s/32/4918_2.png) [@Elena\_S](https://research.lido.fi/u/Elena_S)\ **Post date:** [July 29, 2026, 2:23pm UTC](https://research.lido.fi/t/establishment-of-the-ccc-operational-multisig/11765/1 "2026-07-29T14:23:13Z")
The Confidential Crab Computing (CCC) intends to establish a new Gnosis Safe multisig wallet (_ **`0x08Af22D13CeA3c7812eF42623F9Ba87Dd1A2C54f`** _) to manage its operational payments. CCC is a subsidiary entity of the Alliance Borg, established to support Wisp, a privacy-first agent system built around local controls and attested TEE execution. The CCC multisig has been established across multiple networks: _ **`Ethereum Mainnet, Base, and Polygon.`** _ The proposed signatories for the new multisig are listed below, together with confirmation of their willingness to serve as signatories. The multisig will use a **`3-of-5`** signing threshold for transaction execution. Proposed signatories and their signing addresses: - Nemo 0xFC08588a828e425Ac7A8E7559CaeBf678A8C03B5 - Sergey Kolesnikov 0x6B6Cc958614E0b124a9E5Aee6276f57Ccf15425b - Sergey Avdyakov 0xCB437a8a5ff8946D1D12CBF9585636a4Bb2D8a62 - Elena\_S 0xB95fdA03A90290Bd5853C79796a768E37130d193 - Angelina 0xBd7561D644b7fE312aB190761bC2a4eB4285CC0f ---
**Author:** ![Elena\_S](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/elena_s/32/4918_2.png) [@Elena\_S](https://research.lido.fi/u/Elena_S)\ **Post date:** [July 30, 2026, 11:57am UTC](https://research.lido.fi/t/establishment-of-the-ccc-operational-multisig/11765/2 "2026-07-30T11:57:43Z")
Hi there! I’m looking to join the CCC multisig with address: 0xb95fda03a90290bd5853c79796a768e37130d193. My address verification: [Ethereum Verified Signed Message](https://etherscan.io/verifySig/320643) ---
**Author:** ![kolsolv](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/kolsolv/32/5685_2.png) [@kolsolv](https://research.lido.fi/u/kolsolv)\ **Post date:** [July 31, 2026, 9:22am UTC](https://research.lido.fi/t/establishment-of-the-ccc-operational-multisig/11765/3 "2026-07-31T09:22:53Z")
Hi there! I’m looking to join the CCC multisig with address: 0x6B6Cc958614E0b124a9E5Aee6276f57Ccf15425b. My address verification: [Ethereum Verified Signed Message](https://etherscan.io/verifySig/320677) ---
**Author:** ![Nemo](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/nemo/32/5143_2.png) [@Nemo](https://research.lido.fi/u/Nemo)\ **Post date:** [July 31, 2026, 9:23am UTC](https://research.lido.fi/t/establishment-of-the-ccc-operational-multisig/11765/4 "2026-07-31T09:23:24Z")
Hi there! I’m looking to join the CCC multisig with address: 0xFC08588a828e425Ac7A8E7559CaeBf678A8C03B5. My address verification: [Verified Signed Message](https://etherscan.io/verifySig/320666) ---
**Author:** ![Sergey\_A](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/sergey_a/32/6641_2.png) [@Sergey\_A](https://research.lido.fi/u/Sergey_A)\ **Post date:** [July 31, 2026, 10:14am UTC](https://research.lido.fi/t/establishment-of-the-ccc-operational-multisig/11765/5 "2026-07-31T10:14:28Z")
Hi there! I’m looking to join the CCC multisig with address: 0xcb437a8a5ff8946d1d12cbf9585636a4bb2d8a62. My address verification: [Ethereum Verified Signed Message](https://etherscan.io/verifySig/320667) ---
**Author:** ![Angelina\_L](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/angelina_l/32/4105_2.png) [@Angelina\_L](https://research.lido.fi/u/Angelina_L)\ **Post date:** [July 31, 2026, 11:34am UTC](https://research.lido.fi/t/establishment-of-the-ccc-operational-multisig/11765/6 "2026-07-31T11:34:49Z")
Hi! I’m looking to join the CCC multisig with address: 0xBd7561D644b7fE312aB190761bC2a4eB4285CC0f. My address verification: [Ethereum Verified Signed Message](https://etherscan.io/verifySig/320674) ---
**Author:** ![cedricbrown](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/cedricbrown/32/7031_2.png) [@cedricbrown](https://research.lido.fi/u/cedricbrown)\ **Post date:** [August 10, 2026, 4:15pm UTC](https://research.lido.fi/t/establishment-of-the-ccc-operational-multisig/11765/7 "2026-08-10T16:15:14Z")
The signer verification flow is underway, but the proposal as written specifies who signs and at what threshold without saying what the multisig may spend. When the Labs BORG operational multisig was established, it came with Easy Track factories for operational expenses, which gave the DAO per period limits and a legible trail instead of open ended discretion. Three setups seem possible here. A plain 3 of 5 Safe with discretionary payments, which is what the text currently describes and asks the DAO for the most trust. Easy Track factories with defined limits, matching the Labs BORG precedent, which costs setup time but makes every payment stream pre bounded. Or an allowance module plus a fixed reporting cadence as a lighter middle ground. Given CCC is a new subsidiary running payments across three networks, matching the existing precedent seems like the path of least surprise for delegates.