add: Deepstate volume and trading fees adapters - #1
Open
0xHawreeth wants to merge 1 commit into
Open
0xHawreeth wants to merge 1 commit into
0xHawreeth wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Deepstate V1 volume and trading fees adapters for Robinhood Chain.
Volume
Fees
0xbfb7b3Ff3D498a559b946B836d26F0E168f273D510(0.1%)Validation
Validated against live Robinhood Chain transactions and on-chain fee configuration.
Example matched fill:
0xc26a80dc3fdc6fc9ac7468f2f8adf4b8ee6d366bd1409275c9c50ddabc0c2b4Gross NVDA output:
2.946942266691035 NVDAProtocol fee:
0.002946942266691035 NVDAExpected at 10 bps:
0.002946942266691035 NVDAContract observability note
The current DeepstateV1 deployment does not expose a dedicated protocol-fee event.
Protocol fees are therefore identified from ERC20 transfers emitted by DeepstateV1 to the configured fee recipient.
A dedicated event such as
ProtocolFeePaid(token, recipient, amount)would make fee indexing more deterministic and auditable, especially for multi-token fees and routed fills.