Transaction Sender Guide

Learn how to send high-priority transactions through the Paladin network to ensure they are processed efficiently and protected from sandwiching attacks.

1. Access Requirements

To become a transaction sender on the Paladin network, you need to meet two requirements:

• Have your IP address whitelisted for access to validator ports
• Have $TESTPAL tokens locked up on your behalf for token-gated access

Please reach out to @edgarpavlovsky on Telegram to initiate the whitelisting process and token setup.

2. Getting the Validator List

Once whitelisted, you can retrieve the current list of active Paladin validators through our API:

This endpoint returns an array of active validators. We recommend:

• Polling this endpoint once per day to maintain an up-to-date list
• Pairing the validator list with your leader schedule tracking

3. Understanding Priority Ports

Paladin validators expose two QUIC ports for priority transaction processing:

• 4819: Standard P3 transactions (include on revert)
• 4820: MEV P3 transactions (fail on revert)

4. Sending Transactions

When sending transactions through Paladin ports, keep in mind:

• Only send transactions to a validator when they are the current leader
• Use port 4819 for transactions that should be included even if they revert
• Use port 4820 for transactions that should fail if they would revert

For reference, you can find an example implementation of a Paladin transaction sender in our p3-txn-sender repository. Please note that this implementation is provided for educational purposes and should not be considered production-ready.