-
Notifications
You must be signed in to change notification settings - Fork 0
Merge branch develop
into main
#12
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
Conversation
|
Summary of ChangesHello @Hanssen0, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request integrates recent developments from the Highlights
Ignored Files
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request appears to be a merge from the develop
branch, introducing a significant refactoring of transaction fee handling, along with several bug fixes and documentation updates. A new centralized function adjustVirtualTxForTxFee
has been created to handle fee calculations, improving code consistency and maintainability across different transaction generation functions. Key bug fixes include correct witness placement when using a paymaster cell and properly flagging the need for a paymaster in spore-related transactions. The documentation has also been updated, although one part regarding service access tokens could be clearer. Overall, these changes enhance the robustness and quality of the codebase.
- Signet: [/token/generate](https://api.signet.rgbpp.io/docs/static/index.html#/Token/post_token_generate) | ||
|
||
As to the mainnet service, it's currently limited to verified apps only. When your app development is ready on testnet, and requires a mainnet access token, please email us at `f@cell.studio` to request a mainnet JWT token. In the email, please provide the following information about your app: | ||
The testnet/signet services are currently public to access. As to the mainnet service, it's currently limited to verified apps only. When your app development is ready on testnet, and requires a mainnet access token, please email us at [buidl@rgbpp.com](mailto:buidl@rgbpp.com) to request a mainnet JWT token. In the email, please provide the following information about your app: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The updated documentation is a bit ambiguous. It states that testnet/signet services are "public to access", but removes the instructions on how to get an access token. The example code for initializing the service, which is not part of this change but is in the same file, still uses BtcAssetsApi.fromToken
which requires a token.
To avoid confusion for developers, please clarify if a token is still needed for testnet/signet. If it is, it would be helpful to restore the instructions or a link on how to obtain one. If a token is no longer required for testnet, the example code in this file should be updated accordingly in a future PR.
No description provided.