# FROST Reference Implementation v1.0.0 Stable Release

**URL:** <https://forum.zcashcommunity.com/t/frost-reference-implementation-v1-0-0-stable-release/46914>\
**Category:** Ecosystem Updates\
**Created:** [February 19, 2024, 8:10pm UTC](https://forum.zcashcommunity.com/t/frost-reference-implementation-v1-0-0-stable-release/46914 "2024-02-19T20:10:20Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Dodger](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/dodger/32/3021_2.png) [@Dodger](https://forum.zcashcommunity.com/u/Dodger)\
**Post date:** [February 20, 2024, 3:00pm UTC](https://forum.zcashcommunity.com/t/frost-reference-implementation-v1-0-0-stable-release/46914/4 "2024-02-20T15:00:45Z")

</div>

I want to add my personal thanks to everyone whose contributions - both past and ongoing - have helped FROST reach this stage.

This is a significant step, both in terms of progress towards making FROST signatures available for use with Zcash, and for the broader cause of financial privacy.

FROST is a significant cryptographic innovation in its own right (which is why it has attracted the CFRG’s interest), and has applications beyond cryptocurrency. For Zcash specifically, it brings a number of benefits.

While transparent ZEC can be protected using Bitcoin-style multisig, that doesn’t work for shielded ZEC, which means that shielded ZEC can’t address use cases that require that spend transactions are authorised by _k_ of _n_ keys (e.g. custody).

FROST for Zcash will fix that, thus fulfilling a key prerequisite for deprecating t-addresses.

It also has future uses in [bridging ZEC to other chains](https://forum.zcashcommunity.com/t/proposed-architecture-for-a-zcash-namada-ibc-ecosystem-ethereum-ecosystem-non-custodial-bridge-using-frost-multisignatures/42749), and, once ZSAs are implemented, bridging other assets to Zcash, as well as enabling _k-of-n_ authorisation for asset issuance.

Beyond enabling specific use cases, FROST is more flexible than multisig. For example, a lost share can be [recovered](https://docs.rs/frost-secp256k1/0.6.0/frost_secp256k1/keys/repairable/index.html) whereas, if a multisig keyholder loses their key, there’s no way to recover it (e.g. a 2-of-3 multisig would become a 2-of-2 multisig).

In short, FROST is cool. ❄

---

_[View the full topic](https://forum.zcashcommunity.com/t/frost-reference-implementation-v1-0-0-stable-release/46914)._
