Skip to content

Conversation

@rickyrombo
Copy link
Contributor

  • Adds support for the Meteora Locker program (using the IDL and anchor-go initially, but then ejecting)
  • Add sol_locker_vesting_escrows table to track vestings
  • Index escrows based on token mints matching artist coins

Technically, this isn't fully sufficient as there could be multiple escrows with the same mint, with the canonical one for the DBC pool only linked by being deterministically derived, but I think this is "good enough" for now - a future PR might change this to have the subscription code do the derivation and listen to those addresses instead of doing the memcmp

@gitguardian
Copy link

gitguardian bot commented Oct 24, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
21836782 Triggered Generic High Entropy Secret 9d9e00c solana/indexer/dbc/indexer_test.go View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@rickyrombo
Copy link
Contributor Author

Technically, this isn't fully sufficient as there could be multiple escrows with the same mint, with the canonical one for the DBC pool only linked by being deterministically derived, but I think this is "good enough" for now - a future PR might change this to have the subscription code do the derivation and listen to those addresses instead of doing the memcmp

Done in #497

@rickyrombo rickyrombo closed this Oct 24, 2025
rickyrombo added a commit that referenced this pull request Oct 24, 2025
Moves Meteora Locker indexing to its own indexer that watches the DBC
pools table, so that it can derive explicit addresses for the lockers
rather than relying on the token mints inside.

Supersedes #496
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.

2 participants