In consensus/state.go, cs.defaultSetProposal could return a ErrInvalidProposalSignature error, but cs.handleMsg only catches that with a cs.Logger.Error message and it appears the block can still be committed. Where are invalid proposal signatures caught and blocked? Are they not a concern? Thanks!

Note: I'm looking at a downlevel master branch, but it looks like the latest master has the same logic.