Sentinel string params always lowercased

When monitoring a function that takes a string parameter it seems that in the notification message the parameter is always lowercased.

:computer: Environment
I am using the Sentinel to monitor a contract on Mainnet

:memo:Details
Looking at https://etherscan.io/tx/0x24b9748173dba1b8d00e49b2e700cabb0277ac1cabf3413332a9ef901034642f the proposalId should be QmWwo3TkBtUybd7wcwix6yuGtApR427FBCxiSGJNwowDoN, but in the email and telegram notification it is qmwwo3tkbtuybd7wcwix6yugtapr427fbcxisgjnwowdon. As this is an ipfs hash, case actually matters and it would be nice to get the correct one in the notification.

Telegram notification:

3 Likes

Hi @rimeissner!

Thanks for reaching out. I’m sorry about the lowercase. We’re looking into this now and will circle back when it’s fixed. This was done as a shortcut to make it easier to compare Hex values more reliably, but we see how this can be an issue given your ipfs example.

Thanks,
Steven

3 Likes

Thanks for the quick reply. Looking forward to it :slight_smile:

2 Likes

Hi @rimeissner!

We deployed a fix for this a few minutes ago. You will now see unmodified parameters in your notifications. Thanks for letting us know and for your detailed explanation.

Please let us know if there’s anything we can help with, if you have any feedback, or if you think of any features that would be useful to you!

Thanks,
Steven

2 Likes

Thanks for the quick support :slight_smile:

1 Like