Port/No-Port

custom default_max_transaction_cpu_usage

no-port

was lowered to limit the amount of cpu availability a transaction could use. From 150,000 ms to 50,000 ms. Not needed on the new evm given the new multitiered architecture

This was removed from the latest release of FIO core chain already

chain/library/apply_context modfifications

port

action filtering is applied here, the old implementation prior to a certain block height is no longer needed

Keep the new action filtering

chain_plugin

TBD

Custom API getters and push transaction endpoints

Pros:
-Convenient
Cons:
-Tedious to implement and slows down development time
-Potentially unsafe - uncaught exceptions can crash the api node
-Every getter and push transaction endpoint requires updates on a handful of SDKs

Notes:
-Custom API that utilizes the get_table_rows endpoint might be better

http_plugin

TBD

Customizations to support custom FIO Error messages