Skip to content

Receipt order in the payload #41

@0xsimulacra

Description

@0xsimulacra

Hello,

I would like to know if the fact that order (or the lack of it) of the receipt in the payload "metadata" is intentional ?

I can provide an example of some receipts in a flashblock, but what I see is that the receipt might have the following structure:

rcpt_tx_idx_1, rcpt_tx_idx_5, rcpt_tx_idx_3...

This make the channel for subscripting to to these receipts to send them not in the same order as they were mined on the block: code_of_channel_flashbot_crate.

This might cause program if your state processing depend on the order of the logs in those receipts.

If the lack of order is intentional, do we have a garantee that the txs in a flashblock will have alll there receipts in the payload metadata ? and that the payload metadata will not contain receipt of a tx that we have not see yet in a flashblock ? so in that case, we can make that channel in the flakblocks crate just send the receipt in the order of the txs in that flashblock.

What made me think it might be not intentional is just the fact that in some programming langages (golang afaik), the order of the map while iterating or saving them in a json is not garanteed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions