> For the complete documentation index, see [llms.txt](https://docs.ithacaprotocol.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ithacaprotocol.io/docs/ecosystem/airdrops/season-one/trading-points/fills.md). # Fills Points for filled orders are awarded based on volumes submitted. Points earned for fills are based on the volume of each fill divided by the base volume times a points multiplier of 1,000. \ **Fill Points = ( Fill Volume / Base Volume ) \* 1,000** Base volume per product: * Digital Options: 20 USDC * Vanilla Options: 0.2 ETH * Forwards: 0.8 ETH > FILL EXAMPLES > > 1. Filling 1 ETH of a vanilla call option would earn > > 10.2 1,000 = 5,000 points > > 2. An Iron Condor Strategy with 4 legs of 1 ETH each would earn: > > 4 10.2 1,000 = 20,000 points > > 3. An Up-and-In Barrier Strategy “The Sniper” would earn > > Leg 1 - 1 ETH Vanilla call: 10.2 1,000 = 5 > > Leg 2 - 200 USDC Digital Call: 20020 1,000 = 10,000 points > > Total: Leg 1 + Leg 2 = 15,000 points --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ithacaprotocol.io/docs/ecosystem/airdrops/season-one/trading-points/fills.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.