Repository navigation
docs(readme): add bulk historical data source (Parquet) to Usage Guide - #18
Open
joshavenue wants to merge 2 commits into
Open
joshavenue wants to merge 2 commits into
joshavenue wants to merge 2 commits into
Conversation
Added section on bulk historical data as an alternative source for backtesting.
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.
Description
Adds a short "Bulk Historical Data (Alternative Source)" subsection under the Usage Guide, right after "Data Fetching with Working SDK". It points to Hydromancer Reservoir, a set of Hyperliquid historical datasets in Parquet on S3 (fills, 1-second candles, 20-level order book snapshots, daily position snapshots). It's for anyone who needs more history or finer data than the info API candles provide.
Disclosure: I work at Hydromancer, which builds Reservoir. I've kept the wording factual and noted the limits (requester-pays S3, no funding rates). Happy to reword it, move it, or close this if it doesn't fit the project.
Type of Change
Testing