Does signMessage follow RFC 6979 to make signature deterministic for FireblocksWeb3Provider?

Developer Discussion
1

Want to use the FireblocksWeb3Provider to signMessage, is the signature deterministic?

2

Hi @peter

If I understand correctly, RFC 6979 specifies how to generate deterministic k values for ECDSA signatures using HMAC. To preven k from ever being reused or predicted.

Fireblocks does not expose the private key to the client. Instead, it signs messages using their MPC platform, where the signature generation happens securely and off-device.
Fireblock still generate secure and unique nonces to protect against ECDSA vulnerabilities, even if the method isn’t RFC 6979.

I do not see a signMessage method in the Web3Provider GitHub - fireblocks/fireblocks-web3-provider: Fireblocks EIP-1193 Compatible Ethereum JavaScript Provider, is this a smart contract method?