Skip to content

Conversation

@0xsergen
Copy link
Contributor

@0xsergen 0xsergen commented Dec 22, 2025

  • Auditing EVM-related and/or Quicknode product-related apps
  • Implementing rebranding
  • New README and CONTRIBUTING files
  • Pre-commit script to keep the project directory in README updated

Note

Rebrand and docs overhaul

  • Renames “QuickNode” to “Quicknode” across READMEs, code comments, titles, and prompts
  • New README.md with badges, usage guidance, and auto-generated project directory; adds comprehensive CONTRIBUTING.md; updates CLAUDE.md

New/updated examples and guides

  • Adds Streams/ai-bot-discord and updates Streams setup docs; multiple minor README fixes across AI, EVM MCP, Solana, Base, Bitcoin, Console API

NFT Collection Explorer improvements

  • Fixes JSON-RPC param shapes, adds loading/error states, controlled inputs, stronger typing, accessibility (alt), and UI styling; updates tsconfig.json to react-jsx

Removals and misc tweaks

  • Removes deprecated enhanced-apis/get-receipts-by-address example
  • Minor code/label changes (e.g., token names, titles, prompts) to align branding

Written by Cursor Bugbot for commit d156d04. This will update automatically on new commits. Configure here.


setBalance(assets)
console.log(assets)
setBalance(result)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incorrect response property access breaks token balance functionality

The response destructuring was changed from extracting assets to extracting result, which breaks the wallet token balance feature. The QuickNode qn_getWalletTokenBalance API returns a response containing an assets array property with the token balances. When using ethers.js provider.send(), the JSON-RPC result is returned directly, so the code should extract assets from data, not result. This change causes balance to be set to undefined, preventing tokens from being displayed.

Fix in Cursor Fix in Web

Copy link
Contributor

@mikejhale mikejhale left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@0xsergen Made a few minor suggestions.

CONTRIBUTING.md Outdated
- **Title** from the first `# Heading` in your README.md
- **Description** from `package.json`'s `description` field

Optional: Install the pre-commit hook to update automatically on each commit:
Copy link
Contributor

@mikejhale mikejhale Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We mention the pre-commit hook earlier in Setup, but here it's mentioned again as optional.

README.md Outdated
cd qn-guide-examples/<example-folder>
# Install dependencies for the chosen runtime (e.g., npm install, yarn, pip, go mod download)
cp .env.example .env # if provided
# Update .env with your Quicknode endpoint keys and any required secrets
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be

Update .env with your Quicknode endpoint URLs and any required secrets

README.md Outdated

## Community & Support

- Join the Quicknode Discord for questions and collaboration: https://discord.gg/quicknode
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make "Quicknode Discord" the link vs a raw URL

README.md Outdated

- Join the Quicknode Discord for questions and collaboration: https://discord.gg/quicknode
- Repo-specific bugs or requests: open a GitHub issue so we can track it.
- Need help with Quicknode products? Reach out via support: https://support.quicknode.com/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here, link "Reach out via support"

const params = [{
wallet: wallet,
}
}]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incorrect API parameter format breaking NFT Explorer

The API calls to Quicknode methods are now passing parameters as an array wrapped around an object instead of passing the object directly. The reference scripts in scripts/getWalletTokenBalance.js and similar files show these methods expect provider.send(method, {...params}) not provider.send(method, [{...params}]). This breaks all three pages since the API will reject the malformed parameters.

Additional Locations (2)

Fix in Cursor Fix in Web

Copy link
Contributor

@mikejhale mikejhale left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants