Conversation
…ransaction fee: the connector fills cum_fees_quote with what the open and close cost on-chain and puts the fee income in custom_info.fees_earned_quote, so the one number that says whether a band is worth keeping read three orders of magnitude low — a live DJT-USDC band showed $0.000023 against $0.074624 actually earned; the formatter now prefers fees_earned_quote when the executor carries it and falls back to cum_fees_quote for executors that have no custom_info twin
|
…e direction An LP executor without custom_info.fees_earned_quote fell back to cum_fees_quote, which for an LP is the on-chain transaction cost — so the detail view could still show a cost as fee income, the confusion this branch exists to fix. LP now reads fees_earned_quote only; when the field is absent the income is unknown and no fee line is printed. Non-LP executors keep their cum_fees_quote, labelled "Fees Paid" so a client cannot read a paid fee as income against the LP's "Fees Earned".
| executor_type = get_field(executor, "type", "executor_type", default="unknown") | ||
| if executor_type == "lp_executor": |
There was a problem hiding this comment.
If an LP executor stores its type in config.type, this check reads only top-level fields and treats it as a non-LP executor. The detail view then hides its earned fees and shows its on-chain transaction cost as “Fees Paid.” Resolve the type from the config too, and test that payload shape.
Show an LP executor's earned fees in its detail view instead of the transaction fee fee: the connector fills cum_fees_quote with what the open and close cost on-chain and puts the fee income in custom_info.fees_earned_quote, so the one number that says whether a band is worth keeping read three orders of magnitude low — a live DJT-USDC band showed $0.000023 against $0.074624 actually earned; the formatter now prefers fees_earned_quote when the executor carries it and falls back to cum_fees_quote for executors that have no custom_info twin