Handle celestia upgrade via the signal module

[MattKetmo]

cf https://github.com/celestiaorg/celestia-app/tree/main/x/signal

CELESTIA-APP v3.0.2 - Mainnet Beta upgrade Dear partners and node operators, We are pleased to announce a new version of celestia-app today. Please make sure you read everything in this post before you upgrade. Celestia app: This is a consensus breaking release. Please upgrade and signal asap. Important changes:

Consensus node operators must enable the BBR (Bottleneck Bandwidth and Round-trip propagation time) . To do this, please run make enable-bbr in the celestia-app folder. To verify it worked, do sysctl net.ipv4.tcp_congestion_control | awk '{print $3}' and the expected output should be bbr

Consensus node operators should update several configurations for v3. This can be done by calling: make configure-v3 or alternatively you can do those manually:

update recv_rate and send_rate in your config.toml file to 10MiB (10485760)

update ttl-num-blocks in your config.toml file to 12

Signal upgrade: Upgrades now use the x/signal module to coordinate the network to an upgrade height.

The following command can be used, if you are a validator in the active set, to signal to upgrade to v3: celestia-appd tx signal signal 3 --from (validatorwallet) --chain-id celestia --fees 210000utia .

You can track the tally of signalling by validators using the following query celestia-appd query signal tally 3.

Once 5/6+ of the voting power have signalled, the upgrade will be ready. There is a hard coded delay between confirmation of the upgrade and execution to the new state machine.

To view the upcoming upgrade height use the following query: celestia-appd query signal upgrade

Release notes: https://github.com/celestiaorg/celestia-app/releases/tag/v3.0.2 :warningpng: Reminder: Please upgrade your DA nodes to v0.20.4 as per ⁠📢｜announcements⁠ if you have not done that yet