Halp! :)

EDIT: this is now solved, u/Contrarian__ helped me identify the problem which doesn't seem related to small transactions at all strangely enough.

The chaintip bot is failing to forward two (~$0.15) transactions that the Bitcoin Unlimited node considers 'too small' (txn-undersize error). How can a transaction be too small?

The transaction hexs are given below:

0100000001f3970963de58021c599055c180fa0925d55b8998581a900e9c82c633d1765df50000000000ffffffff013b330000000000001976a9149ff9d8146cc558f5f7d29392a48834d51f519e6f88ac00000000

01000000011d419ae57c0f6256260720bc5e5aeda463f8e383742ef7a9627dd269d5b66e280100000000ffffffff013d3b0200000000001976a9143551aabae0071cc03181475287d63bd18892c03688ac00000000

I've found this tool useful to decode these: https://live.blockcypher.com/btc/decodetx

I found this: "Minimum Transaction Size Transactions that are smaller than 100 bytes shall be considered invalid. This protects against a Merkle tree vulnerability that allows attackers to spoof transactions against SPV wallets" - 2018 November 15 Network Upgrade Specification

and someone suggested that an OP_RETURN is added to bump the transaction over the limit. I'm not sure how to do this using python-bitcoinrpc (the lib I use to communicate with the Bitcoin Unlimited node). I don't see that as an option in the interface. Would adding a locktime in the past in these cases achieve the same end (this is an option)?

I don't really understand why there is a minimum limit... I thought that the smaller transactions are, the better.