feat: Add Custom Blockfrost URL Support#482
Open
adrian1-dot wants to merge 2 commits intogeniusyield:mainfrom
Open
feat: Add Custom Blockfrost URL Support#482adrian1-dot wants to merge 2 commits intogeniusyield:mainfrom
adrian1-dot wants to merge 2 commits intogeniusyield:mainfrom
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
This PR adds support for custom Blockfrost URLs in Atlas, enabling the use of self-hosted or alternative Blockfrost instances. Previously, Atlas only supported the official Blockfrost environments (mainnet, preprod, preview). This change allows users to configure a custom Blockfrost URL and optionally provide an API key for authentication.
Closes #481
Type of Change
Checklist
Testing
Automated tests:
GYBlockfrostCustomvariantManual testing:
maybeBlockfrostKeywith value)Note: Full provider integration tests require API credentials and are excluded from CI. The new
GYBlockfrostCustomprovider shares the same endpoint limitations as standard Blockfrost (governance, mempool operations) and is appropriately filtered from tests requiring those features.Additional Information
Related Issue: #481
Changes made:
GYBlockfrostCustomvariant toGYLayer1ProviderInfodata type with custom URL and optional API keynetworkIdToProjectCustomfunction to construct Blockfrost client with custom URLisBlockfrostpredicate to recognize the new custom variantBlockfrostNotFoundto handle the constructor's argumentcabal.project, latest release.Use case: This enables users to run Atlas against custom Blockfrost deployments, which is useful for private networks, testing environments, or alternative Blockfrost implementations.