-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2.2.0 Release - IMPORTANT - Breaking Changes (API Auth, Blockscout, Docker) #47
Merged
Conversation
This file contains 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
# 2.1 Release - IMPORTANT BREAKING CHANGES - * TL;DR: New [Environment Variables](.github/workflows/proxy-router.main.env): * Mandatory: * BLOCKSCOUT_API_URL replaces EXPLORER_API_URL for the proxy-router * Optional: * COOKIE_FILE_PATH adds directed location for the .cookie API auth file (auth-n) * AUTH_CONFIG_FILE_PATH adds directed location for the proxy.conf file which holds the fine-grained authorization for admin, users and agents (auth-z) ## Bug Fix - Arbiscan.io * As of the first of the year, Arbiscan.io (which we used for explorer lookups) now require a free API Key even for basic lookups. * This issue broke the display of wallet transactions in the Desktop UI * To mitigate this issue and enable future enhancements with agent activity and to give deeper insight into wallet activity, we are now using Blockscout.com's API for explorer / blockchain lookups. * **THIS WILL REQUIRE A CHANGE TO YOUR .ENV Environment files and variables** by adding `BLOCKSCOUT_API_URL=https://arbitrum.blockscout.com/api/v2` the functionality will now be restored. * This is a mandatory variable for the proxy-router, and it will **not start** without this new variable ## API-Authorization * In order to secure the proxy-router API and enable future agent authorization, the API will now require authentication * Please see [02.5-api-auth](/docs/02.5-api-auth.md) for details on how to examine the .cookie file, authenticate to the proxy-router as `admin` and then manually add agent/users with fine-grained access * Pre-seed .cookie file for Docker builds or other complex environments, you can supply a .cookie file (via echo or other command) into the COOKIE_FILE_PATH location with the format `admin:my_strong_password`. * This will build the .cookie file and the proxy-router will build the proxy.conf file. This allows you to know the admin password for the API prior to build/runtime. ## Docker Package * To reduce friction for deploying the Morpheus-Lumerin proxy-router (core system) via container, we have included Linux/AMD64 and Linux/ARM64 compatible docker image * Please visit [Morpheus-Lumerin-Node Package Site](https://github.com/orgs/Lumerin-protocol/packages/container/package/morpheus-lumerin-node) * Please see [02.1-proxy-router-docker](/docs/02.1-proxy-router-docker.md) for details on how to use the container file and run with command line variables or .env file.
# 2.1 Release - IMPORTANT BREAKING CHANGES - * TL;DR: New [Environment Variables](.github/workflows/proxy-router.main.env): * Mandatory: * BLOCKSCOUT_API_URL replaces EXPLORER_API_URL for the proxy-router * Optional: * COOKIE_FILE_PATH adds directed location for the .cookie API auth file (auth-n) * AUTH_CONFIG_FILE_PATH adds directed location for the proxy.conf file which holds the fine-grained authorization for admin, users and agents (auth-z) ## Bug Fix - Arbiscan.io * As of the first of the year, Arbiscan.io (which we used for explorer lookups) now require a free API Key even for basic lookups. * This issue broke the display of wallet transactions in the Desktop UI * To mitigate this issue and enable future enhancements with agent activity and to give deeper insight into wallet activity, we are now using Blockscout.com's API for explorer / blockchain lookups. * **THIS WILL REQUIRE A CHANGE TO YOUR .ENV Environment files and variables** by adding `BLOCKSCOUT_API_URL=https://arbitrum.blockscout.com/api/v2` the functionality will now be restored. * This is a mandatory variable for the proxy-router, and it will **not start** without this new variable ## API-Authorization * In order to secure the proxy-router API and enable future agent authorization, the API will now require authentication * Please see [02.5-api-auth](/docs/02.5-api-auth.md) for details on how to examine the .cookie file, authenticate to the proxy-router as `admin` and then manually add agent/users with fine-grained access * Pre-seed .cookie file for Docker builds or other complex environments, you can supply a .cookie file (via echo or other command) into the COOKIE_FILE_PATH location with the format `admin:my_strong_password`. * This will build the .cookie file and the proxy-router will build the proxy.conf file. This allows you to know the admin password for the API prior to build/runtime. ## Docker Package * To reduce friction for deploying the Morpheus-Lumerin proxy-router (core system) via container, we have included Linux/AMD64 and Linux/ARM64 compatible docker image * Please visit [Morpheus-Lumerin-Node Package Site](https://github.com/orgs/Lumerin-protocol/packages/container/package/morpheus-lumerin-node) * Please see [02.1-proxy-router-docker](/docs/02.1-proxy-router-docker.md) for details on how to use the container file and run with command line variables or .env file.
# 2.1 Release - IMPORTANT BREAKING CHANGES - * TL;DR: New [Environment Variables](.github/workflows/proxy-router.main.env): * Mandatory: * BLOCKSCOUT_API_URL replaces EXPLORER_API_URL for the proxy-router * Optional: * COOKIE_FILE_PATH adds directed location for the .cookie API auth file (auth-n) * AUTH_CONFIG_FILE_PATH adds directed location for the proxy.conf file which holds the fine-grained authorization for admin, users and agents (auth-z) ## Bug Fix - Arbiscan.io * As of the first of the year, Arbiscan.io (which we used for explorer lookups) now require a free API Key even for basic lookups. * This issue broke the display of wallet transactions in the Desktop UI * To mitigate this issue and enable future enhancements with agent activity and to give deeper insight into wallet activity, we are now using Blockscout.com's API for explorer / blockchain lookups. * **THIS WILL REQUIRE A CHANGE TO YOUR .ENV Environment files and variables** by adding `BLOCKSCOUT_API_URL=https://arbitrum.blockscout.com/api/v2` the functionality will now be restored. * This is a mandatory variable for the proxy-router, and it will **not start** without this new variable ## API-Authorization * In order to secure the proxy-router API and enable future agent authorization, the API will now require authentication * Please see [02.5-api-auth](/docs/02.5-api-auth.md) for details on how to examine the .cookie file, authenticate to the proxy-router as `admin` and then manually add agent/users with fine-grained access * Pre-seed .cookie file for Docker builds or other complex environments, you can supply a .cookie file (via echo or other command) into the COOKIE_FILE_PATH location with the format `admin:my_strong_password`. * This will build the .cookie file and the proxy-router will build the proxy.conf file. This allows you to know the admin password for the API prior to build/runtime. ## Docker Package * To reduce friction for deploying the Morpheus-Lumerin proxy-router (core system) via container, we have included Linux/AMD64 and Linux/ARM64 compatible docker image * Please visit [Morpheus-Lumerin-Node Package Site](https://github.com/orgs/Lumerin-protocol/packages/container/package/morpheus-lumerin-node) * Please see [02.1-proxy-router-docker](/docs/02.1-proxy-router-docker.md) for details on how to use the container file and run with command line variables or .env file.
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.
2.2 Release - IMPORTANT - BREAKING CHANGES
Bug Fix - Arbiscan.io
BLOCKSCOUT_API_URL=https://arbitrum.blockscout.com/api/v2
the functionality will now be restored.API-Authorization
admin
and then manually add agent/users with fine-grained accessadmin:my_strong_password
.Docker Package