---
tags: meeting-minutes
---

# Chrysalis RFC Call - 2020-12-01

## Participants

## Topics

### RFC Status

#### PR

- [RFC-0017](https://github.com/iotaledger/protocol-rfcs/pull/17) (Message)
- Gal has integrated last week's "breaking" changes
- Questions, Updates?
- Check API RFC (in info response? NetworkID as a string before hashing, and the hash?)
- [RFC-0019](https://github.com/iotaledger/protocol-rfcs/pull/19) (Milestones)
- [minor updates](https://github.com/iotaledger/protocol-rfcs/pull/19/commits/325d6f1ef7d62e16c23f1d4a190658993a9ec9a8?short_path=44b334f#diff-44b334f76a0f414830c28af0ed930ac3df5857381275a13ba744daf6d75c0514):
- Clarify description as mentioned
- Motivate reattachments (as discussed in [Slack](https://iotafoundation.slack.com/archives/C01CECL6QHZ/p1603125771428000))
- [RFC-0020](https://github.com/iotaledger/protocol-rfcs/pull/20) (Address Format)
- Let's go with `iota`, `atoi`
- [RFC-0025](https://github.com/iotaledger/protocol-rfcs/pull/25) (Local Snapshot)
- Full vs diff
- New RFC bootstrapping
- @all think about having outputs in the PoI, include previous root? Also Snapshot validation/verification

### Chrysalis Stage 2

- Multisig
- We have Shamir's Secret Sharing out of the box with [SLIP-0039](https://github.com/satoshilabs/slips/blob/master/slip-0039.md) etc
- Poor man's Ed25519 multisig, is very easy to do (but introduces a new signature scheme we can never get rid of)
- Is it needed at release? How can we figure this out?
- Options:
- [Tree-like](https://github.com/mgudemann/implementation-decisions/blob/rfc/multi-sig_terms/text/0000-multi-sig-term.md)
- [Simple](https://docs.avax.network/build/references/avm-transaction-serialization/#proto-secp-256-k1-transfer-output-specification)
- New Signature Scheme: like BLS, sr25519
- Discussion about NetworkID/Protocol and breaking changes