Commitments-API spec implementation

[mempirate]

Context

Implement the commitments-API spec as defined below in the Bolt sidecar.

Specifications

bolt_requestInclusion

Description

Requests an inclusion preconfirmation for one or more transactions. If len(txs) > 1, the array will be considered an atomic bundle.

Important

Creating the signature: the signature should come from signing the message digest. The message digest
is the following:

let message_digest = {
     let mut data = Vec::new();
     // First field is the concatenation of all the transaction hashes
     data.extend_from_slice(&transactions.map(|tx| tx.hash().as_slice()).concat());
     // Second field is the little endian encoding of the target slot
     data.extend_from_slice(&target_slot.to_le_bytes());
     keccak256(data)
};

The signature should be stored in the X-Bolt-Signature header as a hex-encoded string. It will be used for authentication purposes.

Parameters

Method	Content-Type	X-Bolt-Signature
POST	application/json	<ecdsa_signature>

Body

{
  "jsonrpc": "2.0",
  "id": "1",
  "method": "bolt_requestInclusion",
  "params": [
    {
      txs,         // Array[String], A list of hex-encoded "raw" transactions. If type 3, must include blobs.
      targetSlot  // String, a hex-encoded string of the target slot. 
    }
  ]
}