Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

LeiosFetch

Mini-protocol number: 19

Warning

This protocol is proposed and not yet part of the Cardano mainnet. It is specified as part of Leios (CIP-0164), an extension to the Ouroboros consensus protocol aimed at significantly increasing transaction throughput. Details are subject to change.

LeiosFetch is the mini-protocol responsible for fetching Endorser Blocks (EBs) and their transaction payloads from peers. It is a pull-based protocol: the client explicitly requests either a full EB or a subset of its transactions (identified by a bitmap), and the server streams the response.

EBs are discovered via LeiosNotify; once a node decides it wants a block or its transactions, it uses LeiosFetch to retrieve the data.

State machine

graph LR
   classDef client color:black,fill:PaleGreen,stroke:DarkGreen;
   classDef server color:black,fill:PowderBlue,stroke:DarkBlue;
   linkStyle default stroke:gray

   StDone(((StDone)))

   i(( )) --> StIdle
   StIdle --MsgDone--> StDone
   StIdle --MsgLeiosBlockRequest--> StBlock
   StBlock --MsgLeiosBlock--> StIdle

   StIdle --MsgLeiosBlockTxsRequest--> StBlockTxs
   StBlockTxs --MsgLeiosBlockTxs--> StIdle

   StIdle --MsgLeiosBlockRangeRequest--> StBlockRange
   StBlockRange --MsgLeiosNextBlockAndTxsInRange--> StBlockRange
   StBlockRange --MsgLeiosLastBlockAndTxsInRange--> StIdle

   class StIdle client
   class StBlock,StBlockTxs,StBlockRange server

State agencies

StateAgency
StIdleInitiator
StBlockResponder
StBlockTxsResponder
StBlockRangeResponder

State transitions

From stateMessageParametersTo state
StIdleMsgClientDoneEnd
StIdleMsgLeiosBlockRequestpointStBlock
StIdleMsgLeiosBlockTxsRequestpoint, bitmapsStBlockTxs
StIdleMsgLeiosBlockRangeRequeststart_slot, end_slot, start_hash, end_hashStBlockRange
StBlockMsgLeiosBlockendorser_blockStIdle
StBlockTxsMsgLeiosBlockTxspoint, bitmaps, tx_listStIdle
StBlockRangeMsgLeiosNextBlockAndTxsInRangeendorser_block, tx_listStBlockRange
StBlockRangeMsgLeiosLastBlockAndTxsInRangeendorser_block, tx_listStIdle

Codecs

The messages depicted in the state machine follow this CDDL specification:

;; messages.cddl
leiosBlockFetchMessage
     = msgLeiosBlockRequest
     / msgLeiosBlock
     / msgLeiosBlockTxsRequest
     / msgLeiosBlockTxs
     / msgLeiosBlockRangeRequest
     / msgLeiosNextBlockAndTxsInRange
     / msgLeiosLastBlockAndTxsInRange
     / msgClientDone

msgLeiosBlockRequest = [0, leios.point]
msgLeiosBlock = [1, endorser_block]
msgLeiosBlockTxsRequest = [2, leios.point, bitmaps]
msgLeiosBlockTxs = [3, leios.point, bitmaps, tx_list]
msgClientDone = [4]

endorser_block = any ; TODO
bitmaps = any ; TODO
tx_list = [ *tx.tx ] ; REVIEW: length-definite encoding TBD

;# import base as base 
;# import leios as leios 
;# import tx as tx

Note

The CBOR tags in this specification are provisional (MsgClientDone at [9] in particular). The endorser_block, bitmaps, and tx types remain underspecified (any) pending further protocol design, including the length-definite encoding for txList. Additionally, the protocol is known to be incomplete: catch-up oriented batch request messages are likely to be added, and the bitmap-based transaction request structure (MsgLeiosBlockTxsRequest) may change significantly as the roaring bitmap encoding is still under discussion. See CIP-0164 PR #1167 for the latest design decisions.