ABI with bytes16 datatype stored as zero padded bytes32

I have sync event based on a bytes16 datatype and the decoded signature in the database seems to be stored as a zero padded bytes32 as a string datatype.

Not a dramatic bug, but maybe still one worth investigating.


can you give an example of how it got to db and what you were expecting?

Moralis server interface: Creating event synchronisation, selecting ABI in the form of


expected the first parameter to be stored as a string with
it is stored as a hex formatted string
So it should look like this in order to be a bytes16

“0x8495b275c87489474bfe75b858bb30f6” (or alternatively like this)

But no problem, already sliced it. Just thought would be useful for you guys to know about the type inconsistency. :+1:

1 Like