Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
, , , , , , , ,Used in:
, ,Used in:
This is a transaction that is already accepted in a block. Once we have a mempool, we will define a separate message for BroadcastedTransaction.
Used in:
Used in:
Used in:
Used in:
see https://external.integration.starknet.io/feeder_gateway/get_transaction?transactionHash=0x41d1f5206ef58a443e7d3d1ca073171ec25fa75313394318fc83a074a6631c3
Used in:
Used in:
Used in:
see https://external.integration.starknet.io/feeder_gateway/get_transaction?transactionHash=0x29fd7881f14380842414cdfdd8d6c0b1f2174f8916edcfeb1ede1eb26ac3ef0
Used in:
Used in:
Used in:
see https://external.integration.starknet.io/feeder_gateway/get_transaction?transactionHash=0x41906f1c314cca5f43170ea75d3b1904196a10101190d2b12a41cc61cfd17c
Used in:
Used in:
Used in:
TBD: can support a flag to return tx hashes only, good for standalone mempool to remove them, or any node that keeps track of transaction streaming in the consensus.
Responses are sent ordered by the order given in the request. The order inside each block is according to the execution order.
Fin is sent after the peer sent all the data or when it encountered a block that it doesn't have its transactions.