Repository navigation
docs: restructure the README like the bot's - #35
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
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.
The README follows pumpfun-bonkfun-bot's: Chainstack header, a one-paragraph intro with the sibling repos, numbered getting-started steps (prerequisites, install, RPC and wallet with every environment variable, trading, launch), then the command list and a trading reference (venues, quote assets, transfer fees, JSON amounts and errors, curve limits). Adds the throughput and IDL sections, the missing
wallet tokens,wallet close-atasandconfig deletecommands, and a note thattokensis blocked for now (#33). Error docs now match the CLI's JSON output: a message, not a code.