You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to use aws ksm for my validator node, and I don't want to use a socket provider due to I have to have a independent process to use it.
islishude
changed the title
sdk should be able to provide PrivValidator for cometbft
[Feature]: sdk should be able to provide PrivValidator for cometbft
Jul 25, 2024
sdk can only provide fixed filepv to cometbft, it can not be updated by apps.
cosmos-sdk/server/start.go
Lines 375 to 378 in 826d4d3
cometbft checks if the socket provider configuration is not empty, and use the socket provider then
https://github.com/cometbft/cometbft/blob/24b39c5ae75f6cec77fedd9c3a27a305aa711fcc/node/node.go#L335-L341
I think we can give application access to provide their own PrivValidator.
I propose a change to add a method
ValidatorKeyProvider() cmttypes.PrivValidator
to the Application interface.
sdk can have a built-in filepv provider in the baseapp
if apps want to have their own provider, they can overwrite the NodeKeyProvider func.
so sdk doesn't have visible breaking changes.
The text was updated successfully, but these errors were encountered: