---
# System prepended metadata

title: Chrysalis RFC Call - 2020-01-06
tags: [meeting-minutes]

---

---
tags: meeting-minutes
---

# Chrysalis RFC Call - 2020-01-06

## Participants

- Andrea
- Gal
- Thibault
- Wolfgang
- Luca

## Topics

### Chrysalis Stage 2

- RFC status and process:
  - Status of RFCs and PRs is unclear for other teams.
  - Each RFC is now classified and labeled according to the following readiness criteria:
    1. RFC still has pending protocol team discussions
    2. RFC has been reviewed by the protocol team and can be implemented in a testnet to get better research and engineering feedback.
    3. RFC is implemented and deployed on testnet, but it might still need feedback/review from other teams based on this.
    4. RFC has passed testnet evaluation and feedback, but it might still depend on other draft RFCs or contain parameters where changes are likely.
    5. Merged: RFC is ready for mainnet and we are not expecting any more changes to it in the near future.
  - We have requested missing outside reviews for every PR, but dust protection.
- Invalid messages in tip-selection and white-flag:
  - [#30](https://github.com/iotaledger/protocol-rfcs/pull/30) and [#26](https://github.com/iotaledger/protocol-rfcs/pull/26) have been adapted to use the correct definitions from [RFC-18](https://github.com/iotaledger/protocol-rfcs/pull/18):
    - _syntactically_ invalid messages can never enter the Tangle
    - _semantic_ validity of transactions is checked "during" white flag. Semantically invalid (but _syntactically_ valid) message can be referenced by milestones, but are _ignored_.
    - Discussion from https://github.com/gohornet/hornet/issues/797 is not fully concluded yet, whether static signature checks could/should be moved to syntax checks. This would reduce the number of "useless" transactions in the Tangle. However, this discussion is independent from the definitions and formulation used in the aforementioned RFCs. 
- [Dust](https://github.com/iotaledger/protocol-rfcs/pull/32)
  - Will be discussed in another call tomorrow.
- [Bech32](https://github.com/iotaledger/protocol-rfcs/pull/20)
  - As wallet DRI, Charlie gets to have the final say on the used HRPs.
