Forward write_version with on program account change notification

[maa105]

Problem

When listening to program account changes sometimes due to network conditions you might get an update x + 1 before you get update x. Now if both updates happens in different slot thats fine you can deduce the order from the slot number. But if the changes are in the same slot you cant tell which happened first. Im not an expert at this repo but I looked a bit and saw that the notifications that are sent on account change does have a variable called write_version specifically for that purpose (check bellow image) However unfortunately this variable is not sent with the notification on the rpc subscription.

~line 106 in geyser-plugin-interface/src/geyser_plugin_interface.rs:

what I get from the RPC call:

{
    "jsonrpc": "2.0",
    "method": "programNotification",
    "params": {
        "result": {
            "context": {
                "slot": 317118392
            },
            "value": {
                "pubkey": "2DJh81MqEuhGBHMAFZSfkMM9DUuCTB58KVaMpkPaEM2x",
                "account": {
                    "lamports": 2039280,
                    "data": [
                        "...",
                        "base64"
                    ],
                    "owner": "TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA",
                    "executable": false,
                    "rentEpoch": 18446744073709551615,
                    "space": 165
                }
            }
        },
        "subscription": 2667
    }
}

NOTE: no write_version

Proposed Solution

Send write_version with the notification