---
tags: meeting-minutes
---

# Chrysalis RFC Call - 2020-11-24

## Participants

- Wolfgang
- Andrea
- Luca
- Gal
- Thibault

## Topics

### RFC Status

#### Merged

- Typos and changes proposed by Charles
- Chrysalis Pt 2 Updates:
- [#30](https://github.com/iotaledger/protocol-rfcs/pull/30):
- @all review
- [#31](https://github.com/iotaledger/protocol-rfcs/pull/31):
- @all review

#### PR

- [RFC-0017](https://github.com/iotaledger/protocol-rfcs/pull/17) (Message)
- Indexation: UTF8 between 1 and 64 bytes
- `Network ID`:
- Add explanation how this field can be derived, like `hash("human readable network name" || protocol version string)`
- Add to the RFC the hash function, BLAKE2b-256 first 8 bytes
- Maximum length:
- Message with a max tx payload is 22324 bytes in its serialized form
- 2^15 = 32KB add this to RFC
- [RFC-0019](https://github.com/iotaledger/protocol-rfcs/pull/19) (MS Payload)
- subjecto to change wrt to Wotsicide
- @wolfgang to change:
- Improve intro
- Remove Ed448 references
- Clarify set of keys
- Address comments
- [RFC-0020](https://github.com/iotaledger/protocol-rfcs/pull/20) (Address Format)
- `iot`/`tio` vs `iota`/??? etc
- talk to UX/bisdev/streams
- do we wanna use "regtest"?
- it might be nice to reserve 48 bytes (max 4 HRP), but this is not a showstopper for |HRP| > 4
- @andrea initiate discussion
- @wolfgang
- Remove W-OTS but keep index 0 reserved
- Propose changes to base-32 type
- [RFC-0024](https://github.com/iotaledger/protocol-rfcs/pull/24) (PoW)
- PoW score is a network parameter
- We leave the PoW computation for now, but this somehow needs to be revisited
- [RFC-0028](https://github.com/iotaledger/protocol-rfcs/pull/28) (Ed25519 Validation)
- Follows ZIP-215 exactly

### Chrysalis Stage 2

- Collect network parameters for Docu not RFC:
- POW score
- Network ID (network name, protocol, e.g `mainnet@1-white_flag`, `alphanet1`)
- Coordinator pubkeys (rotation?)
- Peering?
- More?