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.
Cheers!
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
FunctionCall(bytes16,address,uint256,uint32,uint256,uint32)
expected the first parameter to be stored as a string with
“Some16CharactersByteSequence”
it is stored as a hex formatted string
“0x8495b275c87489474bfe75b858bb30f600000000000000000000000000000000”
So it should look like this in order to be a bytes16
“8495b275c87489474bfe75b858bb30f6”
“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 Like