# One-byte message type allocations

This table lists additional message type IDs that various BIPs have
assigned or proposed for assignment.

Type | Message      | Proposal
---- | ------------ | --------
  29 | uproof       | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923)
  30 | getuproof    | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923)
  31 | uttls        | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923)
  32 | getuttls     | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923)
  33 | usummary     | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923)
  34 | utreexotx    | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923)
  35 | uroot        | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923)
  36 | geturoot     | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923)
  37 | feature      | [BIP 434](https://github.com/bitcoin/bips/blob/master/bip-0434.md)

Note that this table is not authoritative but instead is reflective
of the BIPs proposing the changes. If multiple BIPs make conflicting
assignments for message type IDs, that may lead to multiple entries for
the same message type ID in this table. BIPs that are in Draft status
may be included in the table, and as a result, the IDs and messages they
define may be changed in future.