Deploying a Trusted Forwarder

Trusted Forwarders MUST be deployed through the Limit Break Trusted Forwarder Factory to be considered a trusted forwarder for Payment Processor.

To deploy a trusted forwarder call the cloneTrustedForwarder function the the Trusted Forwarder Factory.

• admin: The initial owner of the trusted forwarder. The owner may update the forwarder's signer address, transfer and renounce ownership.
• appSigner: For a permissioned forwarder this will be the signer address. For an open forwarder this must be set to address(0).
• salt: A 32-byte hex value that can only be used once per deployer address to create a deterministic deployment address for the trusted forwarder. Note: Users that are mining a salt value for vanity/optimized addresses should be aware that the provided salt is hashed with their deployer address to determine the salt passed to the CREATE2 instruction.

function cloneTrustedForwarder(
    address admin, 
    address appSigner, 
    bytes32 salt
) external returns (address trustedForwarder)

After a trusted forwarder is deployed, creators may set the trusted forwarder as an allowed channel with add trusted channel and block unauthorized channels by setting the blockTradesFromUntrustedChannels flag to true in set collection payment settings.