---
# System prepended metadata

title: Chrysalis RFC Call - 2020-11-16
tags: [meeting-minutes]

---

---
tags: meeting-minutes
---

# Chrysalis RFC Call - 2020-11-16

## Participants

- Wolfgang
- Andrea
- Luca
- Gal
- Thibault

## Topics

### RFC Status

#### Merged

https://iotaledger.github.io/protocol-rfcs/

- Chrysalis Pt 2 Updates:
  - This is a major change to an existing RFC. Therefore, the new PR should be mentioned in the `RFC PR:` tag. 
  - [#30](https://github.com/iotaledger/protocol-rfcs/pull/30) very straightforward no more discussion required.
  - [#31](https://github.com/iotaledger/protocol-rfcs/pull/31) changes also examples and algorithm @all review

#### PR

- [RFC-0017](https://github.com/iotaledger/protocol-rfcs/pull/17) (Message)
  - `Payload Length` remains unchanged at uint32
  - Revisiting last week's `Network ID`:
    - The current (`Version`: uint8, `NetworkID`: uint64) is rather misleading. There seems to be no more reason for `Version` as it is superseded by by the network ID.
    - Remove `Version` Field
    - `Network ID` remains uint64
    - Add add short explanation how this field can be derived, like `hash("human readable network name" || protocol parameters/version)`
  - Maximum length:
    - Compute the largest message size with the largest UTXO payload. Specify this as a maximum.
- [RFC-0018](https://github.com/iotaledger/protocol-rfcs/pull/18) (Tx Payload)
  - Keep the W-OTS part unchanged for now
- [RFC-0019](https://github.com/iotaledger/protocol-rfcs/pull/19) (MS Payload)
  - @wolfgang to change: 
    - Improve intro
    - Remove Ed448 references
    - Clarify set of keys
    - Address comments
