It further renames Tendermint KMS to CometBFT KMS because the former is no longer maintained.

Renaming an entire project is something that should be discussed in its own separate issue, not something done as a secondary objective in what is effectively a feature PR.

Can you leave the name as-is for now and open a discussion issue? It will also make the PR and its subsequent followup much more manageable to review.

Re:

thread 'test_buffer_underflow_sign_proposal' panicked at tests/integration.rs:660:28:
called `Result::unwrap()` on an `Err` value: Os { code: 54, kind: ConnectionReset, message: "Connection reset by peer" }

Q: Is there a way to regenerate "tests/support/buffer-underflow-proposal.bin"?

It further renames Tendermint KMS to CometBFT KMS because the former is no longer maintained.

Renaming an entire project is something that should be discussed in its own separate issue, not something done as a secondary objective in what is effectively a feature PR.

Can you leave the name as-is for now and open a discussion issue? It will also make the PR and its subsequent followup much more manageable to review.

Done ✅

@melekes are there any plans to publish a new prerelease of at least cometbft-proto any time soon?

@melekes are there any plans to publish a new prerelease of at least cometbft-proto any time soon?

@tony-iqlusion
Not sure, we are no longer stewards of cometbft-rs so any request would have to go to ICF.

@sryps is there someone specific at the ICF I should ping about that?

In the meantime I will try to get this landed, but vendoring the relevant protos for now.

@sryps is there someone specific at the ICF I should ping about that?

In the meantime I will try to get this landed, but vendoring the relevant protos for now.

Im not sure, Barry with ICL maybe? I dont deal with anything on that end myself.

@tony-iqlusion feel free to ping me on what needs to be done in Comet-rs

We've migrated to a fork of cometbft-rs: #1124, #1129, #1139

Unfortunately we can't support CometBFT V1 yet due to breaking changes to the protocol: #1132

We'll need to have multi-version support: #976