Implement Soroban Refund Flow For Contributors#61
Merged
ritik4ever merged 2 commits intoritik4ever:mainfrom Mar 30, 2026
Merged
Implement Soroban Refund Flow For Contributors#61ritik4ever merged 2 commits intoritik4ever:mainfrom
ritik4ever merged 2 commits intoritik4ever:mainfrom
Conversation
|
@RemmyAcee is attempting to deploy a commit to the ritik4ever's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@RemmyAcee Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
Author
|
Done, Close: #61 |
Owner
|
@RemmyAcee please resolve the conflicts |
Contributor
Author
Done |
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
2 participants
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.
Close: #31
Implemented the refund flow end to end so it now goes through Soroban first, then reconciles local state after a confirmed on-chain success. The main pieces are in [soroban.ts], [App.tsx], and the backend refund verification path in [index.ts] plus [sorobanRpc.ts].
On success, the backend now records richer refund metadata into campaign history from [campaignStore.ts], and the timeline renders that context in [CampaignTimeline.tsx]. I also exposed contract/network config for the frontend from [index.ts], and updated the refund payload/types in [schemas.ts] and [campaign.ts].
Verification: frontend typecheck passed with npx tsc --noEmit. I couldn’t fully verify the backend build because better-sqlite3 failed to install on this machine under Node 24 without the required Visual Studio C++ toolchain, and the full frontend Vite build is currently blocked by a broken Rollup native optional dependency in node_modules.