Unexplained 4.684680 SHELL terminal component in GPT-5.6 Sol settlement

[h2so4nackl-code]

Summary

This issue is specifically about the unexplained "4.684680 SHELL" component in the final settlement of a GPT-5.6 Sol deal.

The claim-versus-delivered issue has already been identified by the DEX.DO team and is expected to be fixed in the next release.

The team also confirmed that this fix does not explain the "4.684680 SHELL" terminal component.

Deal

TokenContract:

"0:0e9f1c9fcbd3cda5102cf96469d852c8fcffe3245e35d45950449fc59fc7e882"

Model:

"gpt-5.6-sol"

Network:

"mainnet"

Negotiated price:

"990 SHELL / tick"

Purchased:

"2 ticks"

Final StreamStopped settlement

Observed:

• "toSeller = 1,984.684680 SHELL"
• "refundToBuyer = 2,990.354103 SHELL"

Buyer PrivateNote:

"0:11fd930b4c2789c3556e60ab0d2adf2ef5e09e13fb578cba1bbce8a2e4e5e5d9"

The TokenContract was destroyed after settlement.

Arithmetic

At the negotiated price:

2 × 990 = 1,980.000000 SHELL

Actual seller payout:

1,984.684680 SHELL

Difference:

1,984.684680
-1,980.000000

 4.684680 SHELL

This "4.684680 SHELL" component cannot currently be derived from the surviving settlement data.

Request

Please identify the exact formula that produced the additional:

"4.684680 SHELL"

Specifically:

1. Is it a fee?
2. A probe-related component?
3. Rounding?
4. Gas?
5. Another settlement component?
6. Can this breakdown be persisted in "settlement-receipt" before TokenContract destruction?

Sanitized logs and receipts are available if needed.

No PrivateNote keys, wallet keys, seed phrases, or credentials will be shared.