Previously I introduced an option to send transaction via your own RPC endpoint. However, it allows a "bad state" attack: user can request a signature (passing the simulation), then break the conditions for transaction success (for example, by withdrawing all of the tokens), then submit the transaction with no-checks option and previously received signature. The transaction will fail, but the transaction fee would be spent regardless.
Previously I introduced an option to send transaction via your own RPC endpoint. However, it allows a "bad state" attack: user can request a signature (passing the simulation), then break the conditions for transaction success (for example, by withdrawing all of the tokens), then submit the transaction with no-checks option and previously received signature. The transaction will fail, but the transaction fee would be spent regardless.