ZEC community open-source threshold custody: mainnet testing is not the same as safe mass production. Around 1468, I’m only waiting for confirmation.
My stance is to observe cautiously—taking a developer demo as immediately usable institutional custody is a leap. In the Zcash community forum, on September 20 a developer publicly released a 2-of-3 threshold custody library designed for shielding ZEC. The project repository states that on September 21, two machines holding different key shares collaborated to authorize a mainnet shield transaction; the third custodian didn’t need to be online to still reach the threshold. Both the forum and the repository are disclosures by the developers. At the moment, I have no independent verification of the full signing workflow for this transaction, so I only describe it as “a mainnet test reported by the developers.” I am not calling it a full network upgrade, an official rollout, nor something already adopted by institutions.
Why is it worth watching? When an institution or DAO holds shielded funds, having a single custodian keep the complete seed creates single-point theft risk and operational risk. This implementation leverages Zcash Foundation’s RedPallas FROST threshold signing, tying together distributed key generation, participant communication, Orchard transaction assembly, deposit confirmation, and reorganization handling—while the coordinator itself does not hold key shares. Zcash’s ZIP 312 proposal also discusses authorizing shield transactions using re-randomizable threshold signatures, which suggests the technical direction has protocol-document background. But the proposal is not production-certified. The project clearly says the full product has not been independently audited; if the threshold is not met, there is no on-chain fallback recovery strategy. Backup and operational procedures remain the hard problems. I think it provides evidence that improves the feasibility of long-term custody—not evidence that supports buying today.
The market hasn’t priced it directly. Around 13:20 Beijing time, OKX ZEC perpetuals are around $1468. The 24-hour range is 1443.66–1572. From 13:00, the complete 15-minute candle closed from 1466 to 1462.49; the subsequent bounce is an incomplete candle and can’t be written as an already completed reversal. Funding rate is about +0.01%; open interest is about 116,000 ZEC, with notional around $179 million. For the old post at 11:04, the long conditions required 1444–1452 to hold without dipping, and then volume returning to close above 1463 with the next candle holding above 1458. Even though it bounced, I have no verifiable record of actual trades, so I won’t call it profitable. Today I’m watching whether 1460 can keep承接 (hold and absorb). Also whether 1476–1484 can be re-established. If it drops back to 1443, the rebound thesis is invalidated.
If I were trading this myself, my position is currently 0. I’m not chasing higher prices because of developer news. Only if 1460–1466 hold for two consecutive 15-minute candles, and then it breaks back up to 1476 on increased volume—with the next candle still holding above 1470—would I use at most 1% of principal for a spot long test. First target: 1485–1493. Second target: 1502–1515. Cut the first target in half; if the position falls back to 1460, cut the remainder in half. If 15-minute candles close below 1442, I’d exit all positions at a full stop. If it breaks below 1458 first and the bounce to 1468 fails, I’ll cancel the long entry and stay flat; I won’t open high leverage because of experimental custody code. If later audits find critical flaws or the mainnet tests can’t be reproduced, even the long-term adoption judgment would need to be withdrawn.
Sources: The Zcash community forum developer original post, the zyn-io project repository, the ZIP 312 proposal, and the OKX公开行情. #ZEC
The above is only personal market observation and does not constitute investment advice.
My stance is to observe cautiously—taking a developer demo as immediately usable institutional custody is a leap. In the Zcash community forum, on September 20 a developer publicly released a 2-of-3 threshold custody library designed for shielding ZEC. The project repository states that on September 21, two machines holding different key shares collaborated to authorize a mainnet shield transaction; the third custodian didn’t need to be online to still reach the threshold. Both the forum and the repository are disclosures by the developers. At the moment, I have no independent verification of the full signing workflow for this transaction, so I only describe it as “a mainnet test reported by the developers.” I am not calling it a full network upgrade, an official rollout, nor something already adopted by institutions.
Why is it worth watching? When an institution or DAO holds shielded funds, having a single custodian keep the complete seed creates single-point theft risk and operational risk. This implementation leverages Zcash Foundation’s RedPallas FROST threshold signing, tying together distributed key generation, participant communication, Orchard transaction assembly, deposit confirmation, and reorganization handling—while the coordinator itself does not hold key shares. Zcash’s ZIP 312 proposal also discusses authorizing shield transactions using re-randomizable threshold signatures, which suggests the technical direction has protocol-document background. But the proposal is not production-certified. The project clearly says the full product has not been independently audited; if the threshold is not met, there is no on-chain fallback recovery strategy. Backup and operational procedures remain the hard problems. I think it provides evidence that improves the feasibility of long-term custody—not evidence that supports buying today.
The market hasn’t priced it directly. Around 13:20 Beijing time, OKX ZEC perpetuals are around $1468. The 24-hour range is 1443.66–1572. From 13:00, the complete 15-minute candle closed from 1466 to 1462.49; the subsequent bounce is an incomplete candle and can’t be written as an already completed reversal. Funding rate is about +0.01%; open interest is about 116,000 ZEC, with notional around $179 million. For the old post at 11:04, the long conditions required 1444–1452 to hold without dipping, and then volume returning to close above 1463 with the next candle holding above 1458. Even though it bounced, I have no verifiable record of actual trades, so I won’t call it profitable. Today I’m watching whether 1460 can keep承接 (hold and absorb). Also whether 1476–1484 can be re-established. If it drops back to 1443, the rebound thesis is invalidated.
If I were trading this myself, my position is currently 0. I’m not chasing higher prices because of developer news. Only if 1460–1466 hold for two consecutive 15-minute candles, and then it breaks back up to 1476 on increased volume—with the next candle still holding above 1470—would I use at most 1% of principal for a spot long test. First target: 1485–1493. Second target: 1502–1515. Cut the first target in half; if the position falls back to 1460, cut the remainder in half. If 15-minute candles close below 1442, I’d exit all positions at a full stop. If it breaks below 1458 first and the bounce to 1468 fails, I’ll cancel the long entry and stay flat; I won’t open high leverage because of experimental custody code. If later audits find critical flaws or the mainnet tests can’t be reproduced, even the long-term adoption judgment would need to be withdrawn.
Sources: The Zcash community forum developer original post, the zyn-io project repository, the ZIP 312 proposal, and the OKX公开行情. #ZEC
The above is only personal market observation and does not constitute investment advice.
