Skip to content

Conversation

@gsteenkamp89
Copy link
Contributor

@gsteenkamp89 gsteenkamp89 commented Dec 19, 2025

closes FE-217

Work done

  • Resolves output amount and fill timestamp from tx signature received from the indexer
  • Does NOT implement RPC fallback. There is no reliable way of tying a CCTP MintAndWithdraw event to a particular deposit ID.

CCTP (Sponsored)

Screenshot 2026-01-06 at 12 27 44

CCTP (NOT Sponsored)

Screenshot 2026-01-06 at 12 27 38

Signed-off-by: Gerhard Steenkamp <gerhard@umaproject.org>
@linear
Copy link

linear bot commented Dec 19, 2025

@vercel
Copy link

vercel bot commented Dec 19, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
app-frontend-v3 Ready Ready Preview, Comment Jan 6, 2026 2:03pm
sepolia-frontend-v3 Ready Ready Preview, Comment Jan 6, 2026 2:03pm

@gsteenkamp89 gsteenkamp89 marked this pull request as ready for review January 6, 2026 10:28
@0xjorgen 0xjorgen changed the title feat(deposti-tracking): parse mint and burn event on solana feat(deposit-tracking): parse mint and burn event on solana Jan 6, 2026
Copy link
Contributor

@0xjorgen 0xjorgen left a comment

Choose a reason for hiding this comment

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

A few questions


async queryMintAndWithdrawEvents(fromSlot?: bigint, toSlot?: bigint) {
return await this.queryEvents(
"MintAndWithdraw" as any, // Maybe override queryEvents method
Copy link
Contributor

Choose a reason for hiding this comment

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

Would the correct thing here be to add MintAndWithdraw to SVMEventNames in the SDK?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This class is actually built for the SVM spoke contract. I am really just repurposing it's methods here since the event querying and unwrapping logic is the same as long as you initialize this with the correct program id and idl.

The best solution is probably to make changes to the original client in the sdk to infer event names based on the idl passed into its constructor

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is removed anyway so no longer relevant f8e775f

return events.filter((event) => event.name === "DepositForBurn");
}

async queryMintAndWithdrawEvents(fromSlot?: bigint, toSlot?: bigint) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Are you using this method anywhere?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, I will remove it along with queryDepositForBurnEvents since those are not really viable options

Copy link
Contributor Author

Choose a reason for hiding this comment

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

remove f8e775f

let fillEventTxRef = "";

if (!fillEvent) {
if (bridgeProvider === "cctp") {
Copy link
Contributor

Choose a reason for hiding this comment

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

I dont uderstand why this is //todo?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Signed-off-by: Gerhard Steenkamp <gerhard@umaproject.org>
@vercel
Copy link

vercel bot commented Jan 6, 2026

Deployment failed with the following error:

Hobby accounts are limited to daily cron jobs. This cron expression (* * * * *) would run more than once per day. Upgrade to the Pro plan to unlock all Cron Jobs features on Vercel.

Learn More: https://vercel.link/3Fpeeb1

Signed-off-by: Gerhard Steenkamp <gerhard@umaproject.org>
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