How does Kaspa prioritize which transactions spread to peers first?

Kaspa gives high-priority transactions — such as those submitted directly through the RPC interface — an immediate broadcast to all connected peers, while routine transaction rebroadcasts are throttled and sent only to random subsets of peers. This two-tier system is managed by something called the TransactionsSpread mechanism, which batches transaction IDs and sends them out at configurable intervals. The throttling on routine rebroadcasts exists specifically to conserve bandwidth, since a high-throughput network like Kaspa generates far more transaction data than a traditional blockchain. For a beginner, this means that when you submit a transaction yourself it travels the network as fast as possible, while background housekeeping traffic is kept lean so the network does not get bogged down.