Waiting room for message assignments

[t-bast]

Message types (2-bytes id) are only finally assigned when they're included into the spec.
While a new message is being tested, you can announce the temporary id you're going to use here.
This will (hopefully) prevent collision between unassigned ids on the network, while also allowing people to quickly see what experiments are being run on the network.

Id	Name	Description
TBD	your_message	description

[t-bast]

These are the custom messages used by Phoenix:

Id	Name	Description
35001	pay_to_open_request	phoenix
35003	pay_to_open_response	phoenix
35005	swap_in_pending	phoenix
35007	swap_in_request	phoenix
35009	swap_in_response	phoenix
35011	swap_out_request	phoenix
35013	swap_out_response	phoenix
35015	swap_in_confirmed	phoenix

[sputn1ck]

At peerswap we rolled the dice and landed on:

Id	Name	Description
42069	swap_in_request	peerswap
42071	swap_out_request	peerswap
42073	swap_in_agreement	peerswap
42075	fee_response	peerswap
42077	tx_opened_response	peerswap
42079	canceled	peerswap
42081	claimed	peerswap
42083	coop_close	peerswap
42085	poll	peerswap
42087	request_poll	peerswap

The spec and project will be open source soon

[ariard]

Taking the range 37560 - 37590 for staking credentials experimentation.

Code: https://github.com/ariard/lightning-risk-engine
Specification: https://github.com/ariard/lightning-rfc/blob/2022-11-reputation-credentials/60-staking-credentials-archi.md

[JssDWt]

A note for people that want to reserve message numbers for their application:

Consider picking a single even/odd pair for your application and use the fist bytes of the message to identify the message type. Because the space of available numbers is somewhat scarce. This way you only use one or two numbers instead of an entire range.

[ZmnSCPxj-jr]

BitcoinAndLightningLayerSpecs/lsp#23

Id	Name	Description
37913	lsps0_message_id	Message conforming to LSPS0 specification.

Single message, as per principle in #716 (comment)