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
The current unencrypted logs are practically broken since they can only be used to emit strictly defined data in the form of strings, which are structured with a u8 array. If passing a field directly to the function emit_unencrypted_log only the least significant byte will actually be emitted, so for event emission similarly to evm based chains it has some way to go.
The text was updated successfully, but these errors were encountered:
I was just investigating this and the issue seems to be fairly small. Noir serializes the data correctly but the oracle handler is incorrect because it accepts only one field.
Instead of emitUnencryptedLog: message => {
it should accept all the fields:
emitUnencryptedLog: (...args) => {
and then concatenate them all to 1 buffer and include with the logs.
The current unencrypted logs are practically broken since they can only be used to emit strictly defined data in the form of strings, which are structured with a u8 array. If passing a field directly to the function
emit_unencrypted_log
only the least significant byte will actually be emitted, so for event emission similarly to evm based chains it has some way to go.The text was updated successfully, but these errors were encountered: