Skip to content

[BLD-143] Dashboard: Fix distribute funds in split contract#7907

Merged
graphite-app[bot] merged 1 commit intomainfrom
08-26-_bld-143_dashboard_fix_distribute_funds_in_split_contract
Aug 25, 2025
Merged

[BLD-143] Dashboard: Fix distribute funds in split contract#7907
graphite-app[bot] merged 1 commit intomainfrom
08-26-_bld-143_dashboard_fix_distribute_funds_in_split_contract

Conversation

@MananTank
Copy link
Copy Markdown
Contributor

@MananTank MananTank commented Aug 25, 2025


PR-Codex overview

This PR focuses on enhancing the useSplitDistributeFunds hook and its usage in the DistributeButton component. Key improvements include better address comparison and updated mutation handling for distributing funds.

Detailed summary

  • Updated address comparison in useSplitDistributeFunds to use getAddress(currency.tokenAddress).
  • Changed mutation variable name from mutation to distributeFundsMutation in DistributeButton.
  • Updated distributeFunds function to call distributeFundsMutation.mutateAsync().
  • Adjusted isPending prop in TransactionButton to use distributeFundsMutation.isPending.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

  • Bug Fixes

    • Detects native token by address and routes distributions accordingly, including correct transaction counts for single native balances.
    • Waits for each distribution transaction to complete before proceeding, preventing partial/overlapping operations.
  • Refactor

    • Streamlined distribution flow and loading-state handling for a more consistent experience.
    • Removed toast-based error pop-ups; operation status is now reflected via the ongoing operation state.

@vercel vercel Bot temporarily deployed to Preview – nebula August 25, 2025 20:00 Inactive
@vercel
Copy link
Copy Markdown

vercel Bot commented Aug 25, 2025

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

Project Deployment Preview Comments Updated (UTC)
thirdweb-www Ready Ready Preview Comment Aug 25, 2025 8:18pm
4 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
docs-v2 Skipped Skipped Aug 25, 2025 8:18pm
nebula Skipped Skipped Aug 25, 2025 8:18pm
thirdweb_playground Skipped Skipped Aug 25, 2025 8:18pm
wallet-ui Skipped Skipped Aug 25, 2025 8:18pm

@vercel vercel Bot temporarily deployed to Preview – wallet-ui August 25, 2025 20:00 Inactive
@vercel vercel Bot temporarily deployed to Preview – docs-v2 August 25, 2025 20:00 Inactive
@vercel vercel Bot temporarily deployed to Preview – thirdweb_playground August 25, 2025 20:00 Inactive
@linear
Copy link
Copy Markdown

linear Bot commented Aug 25, 2025

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Aug 25, 2025

⚠️ No Changeset found

Latest commit: 27f50a8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Aug 25, 2025

Walkthrough

Detect native token by address and call the appropriate split contract method (distribute vs distributeByToken) per currency, await each distribution promise before resolving. Simplify the distribute button by removing toast error handling, renaming the mutation, and adding a native-token-specific transaction-count branch.

Changes

Cohort / File(s) Summary
Split distribution logic
apps/dashboard/src/@/hooks/useSplit.ts
- Add getAddress import
- Detect native token via address comparison to NATIVE_TOKEN_ADDRESS
- Call distribute({ contract }) for native, distributeByToken({ contract, tokenAddress }) for tokens
- Await each per-currency distribution promise inside the map before Promise.all
- Minor formatting
Distribute button behavior
apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/split/components/distribute-button.tsx
- Replace toast-based error handling with direct distributeFundsMutation.mutateAsync() call
- Rename mutation variable to distributeFundsMutation and use isPending from it
- Add special-case in numTransactions when a single valid balance has name "Native Token"
- Remove toast and parseError imports and callbacks

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant U as User
  participant B as DistributeButton
  participant H as useSplit hook
  participant SDK as thirdweb SDK
  participant N as Network

  U->>B: Click "Distribute"
  B->>H: call distributeFundsMutation.mutateAsync()
  activate H

  loop per selected currency
    alt currency.tokenAddress == NATIVE_TOKEN_ADDRESS
      H->>SDK: distribute({ contract })
    else
      H->>SDK: distributeByToken({ contract, tokenAddress })
    end
    SDK->>N: submit tx
    N-->>SDK: tx receipt
    SDK-->>H: resolve
  end

  H-->>B: all distributions resolved
  deactivate H
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Assessment against linked issues

Objective Addressed Explanation
Fix native token (POL) distribution revert by invoking correct function for native asset and proper detection (BLD-143)
Ensure flow completes without premature Promise.all resolution during multi-currency distributions (BLD-143)
Maintain user-visible error feedback during failure scenarios (BLD-143) Removal of toasts and callbacks leaves unclear whether alternative UX error handling exists.

Assessment against linked issues: Out-of-scope changes

Code Change Explanation
Removed toast-based error handling and parseError usage (apps/.../split/components/distribute-button.tsx) The linked issue focuses on distribution logic; changing UI error handling is not part of that objective.
Added numTransactions special-case based on balance name "Native Token" (apps/.../split/components/distribute-button.tsx) Adjusting UI transaction-count logic is unrelated to fixing the distribution revert described in the issue.

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)
  • TEAM-0000: Entity not found: Issue - Could not find referenced Issue.

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e69fa41 and 27f50a8.

📒 Files selected for processing (2)
  • apps/dashboard/src/@/hooks/useSplit.ts (4 hunks)
  • apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/split/components/distribute-button.tsx (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • apps/dashboard/src/@/hooks/useSplit.ts
  • apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/split/components/distribute-button.tsx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Unit Tests
  • GitHub Check: Size
  • GitHub Check: Analyze (javascript)
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch 08-26-_bld-143_dashboard_fix_distribute_funds_in_split_contract

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@MananTank MananTank marked this pull request as ready for review August 25, 2025 20:01
@github-actions github-actions Bot added the Dashboard Involves changes to the Dashboard. label Aug 25, 2025
@MananTank MananTank requested review from a team as code owners August 25, 2025 20:01
Copy link
Copy Markdown
Contributor Author

MananTank commented Aug 25, 2025


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@codecov
Copy link
Copy Markdown

codecov Bot commented Aug 25, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.53%. Comparing base (157f4b9) to head (27f50a8).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7907   +/-   ##
=======================================
  Coverage   56.53%   56.53%           
=======================================
  Files         904      904           
  Lines       58592    58592           
  Branches     4143     4143           
=======================================
  Hits        33126    33126           
  Misses      25360    25360           
  Partials      106      106           
Flag Coverage Δ
packages 56.53% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Aug 25, 2025

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 64.06 KB (0%) 1.3 s (0%) 391 ms (+76.37% 🔺) 1.7 s
thirdweb (cjs) 357.05 KB (0%) 7.2 s (0%) 1.7 s (+7.64% 🔺) 8.8 s
thirdweb (minimal + tree-shaking) 5.73 KB (0%) 115 ms (0%) 106 ms (+898.58% 🔺) 220 ms
thirdweb/chains (tree-shaking) 526 B (0%) 11 ms (0%) 93 ms (+1325.45% 🔺) 103 ms
thirdweb/react (minimal + tree-shaking) 19.15 KB (0%) 383 ms (0%) 124 ms (+386.07% 🔺) 507 ms

@graphite-app
Copy link
Copy Markdown
Contributor

graphite-app Bot commented Aug 25, 2025

Merge activity

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (5)
apps/dashboard/src/@/hooks/useSplit.ts (3)

98-127: Parallel map still runs all transactions concurrently; consider serializing to avoid wallet prompt contention

Adding await inside the map callback doesn’t serialize the operations; they still start concurrently and then all await. If you want one approval/signature at a time (smoother UX and fewer wallet-edge-case failures), iterate sequentially.

Apply this diff to serialize transactions:

-      const distributions = balances
-        .filter((token) => token.value !== 0n)
-        .map(async (currency) => {
-          const transaction =
-            getAddress(currency.tokenAddress) ===
-            getAddress(NATIVE_TOKEN_ADDRESS)
-              ? distribute({ contract })
-              : distributeByToken({
-                  contract,
-                  tokenAddress: currency.tokenAddress,
-                });
-          const promise = sendAndConfirmTransaction({
-            account,
-            transaction,
-          });
-
-          toast.promise(promise, {
-            error: (err) => ({
-              message: `Error distributing ${currency.name}`,
-              description: parseError(err),
-            }),
-            loading: `Distributing ${currency.name}`,
-            success: `Successfully distributed ${currency.name}`,
-          });
-
-          await promise;
-        });
-
-      return await Promise.all(distributions);
+      for (const currency of balances.filter((t) => t.value !== 0n)) {
+        const transaction =
+          getAddress(currency.tokenAddress) === getAddress(NATIVE_TOKEN_ADDRESS)
+            ? distribute({ contract })
+            : distributeByToken({ contract, tokenAddress: currency.tokenAddress });
+
+        const txPromise = sendAndConfirmTransaction({ account, transaction });
+
+        toast.promise(txPromise, {
+          error: (err) => ({
+            message: `Error distributing ${currency.name}`,
+            description: parseError(err),
+          }),
+          loading: `Distributing ${currency.name}`,
+          success: `Successfully distributed ${currency.name}`,
+        });
+
+        await txPromise; // ensure prompts execute one-by-one
+      }

128-131: Use React Query v5 invalidate signature

Passing the full query options object to invalidateQueries is non-idiomatic and can confuse types. Use { queryKey } to avoid accidental breakage and to align with v5 API.

Apply this diff:

-    onSettled: () => {
-      queryClient.invalidateQueries(getTokenBalancesQuery(params));
-    },
+    onSettled: () => {
+      queryClient.invalidateQueries({
+        queryKey: getTokenBalancesQuery(params).queryKey,
+      });
+    },

93-97: Prefer ensureQueryData for typed cache + fetch

You can avoid the manual cache-or-fetch branching and get better typing by using ensureQueryData.

Apply this diff:

-      const balances =
-        // get the cached data if it exists, otherwise fetch it
-        queryClient.getQueryData(getTokenBalancesQuery(params).queryKey) ||
-        (await queryClient.fetchQuery(getTokenBalancesQuery(params)));
+      const balances = await queryClient.ensureQueryData(
+        getTokenBalancesQuery(params),
+      );
apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/split/components/distribute-button.tsx (2)

28-33: Avoid name-based native detection; use address normalization to match hook logic

Relying on name === "Native Token" is brittle (localization/providers may differ). Align with the hook by comparing addresses.

Apply this diff:

+import { getAddress, NATIVE_TOKEN_ADDRESS } from "thirdweb";
...
   const numTransactions = useMemo(() => {
     if (
       validBalances.length === 1 &&
-      validBalances[0]?.name === "Native Token"
+      getAddress(validBalances[0]!.tokenAddress) ===
+        getAddress(NATIVE_TOKEN_ADDRESS)
     ) {
       return 1;
     }

Nit: since both native and ERC20 paths currently perform a single tx for a single balance, you could simplify to return validBalances.length; unless you plan to show multi-step counts in the future.


42-44: Avoid unhandled rejections: use mutate() or await mutateAsync with try/catch

Calling mutateAsync() without await/.catch() can surface unhandled promise rejections in dev tools. Prefer mutate() for event handlers, or make the handler async and handle errors.

Apply one of these diffs (Option A recommended):

Option A – use mutate():

-  const distributeFunds = () => {
-    distributeFundsMutation.mutateAsync();
-  };
+  const distributeFunds = () => {
+    distributeFundsMutation.mutate();
+  };

Option B – await with try/catch:

-  const distributeFunds = () => {
-    distributeFundsMutation.mutateAsync();
-  };
+  const distributeFunds = async () => {
+    try {
+      await distributeFundsMutation.mutateAsync();
+    } catch {
+      // handled by hook toasts / React Query error state
+    }
+  };
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 157f4b9 and e69fa41.

📒 Files selected for processing (2)
  • apps/dashboard/src/@/hooks/useSplit.ts (4 hunks)
  • apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/split/components/distribute-button.tsx (3 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{ts,tsx}

📄 CodeRabbit inference engine (CLAUDE.md)

**/*.{ts,tsx}: Write idiomatic TypeScript with explicit function declarations and return types
Limit each file to one stateless, single-responsibility function for clarity
Re-use shared types from @/types or local types.ts barrels
Prefer type aliases over interface except for nominal shapes
Avoid any and unknown unless unavoidable; narrow generics when possible
Choose composition over inheritance; leverage utility types (Partial, Pick, etc.)
Comment only ambiguous logic; avoid restating TypeScript in prose

Files:

  • apps/dashboard/src/@/hooks/useSplit.ts
  • apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/split/components/distribute-button.tsx
**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (CLAUDE.md)

Load heavy dependencies inside async paths to keep initial bundle lean (lazy loading)

Files:

  • apps/dashboard/src/@/hooks/useSplit.ts
  • apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/split/components/distribute-button.tsx
apps/{dashboard,playground-web}/**/*.{ts,tsx}

📄 CodeRabbit inference engine (CLAUDE.md)

apps/{dashboard,playground-web}/**/*.{ts,tsx}: Import UI primitives from @/components/ui/* (Button, Input, Select, Tabs, Card, Sidebar, Badge, Separator) in dashboard and playground apps
Use NavLink for internal navigation with automatic active states in dashboard and playground apps
Use Tailwind CSS only – no inline styles or CSS modules
Use cn() from @/lib/utils for conditional class logic
Use design system tokens (e.g., bg-card, border-border, text-muted-foreground)
Server Components (Node edge): Start files with import "server-only";
Client Components (browser): Begin files with 'use client';
Always call getAuthToken() to retrieve JWT from cookies on server side
Use Authorization: Bearer header – never embed tokens in URLs
Return typed results (e.g., Project[], User[]) – avoid any
Wrap client-side data fetching calls in React Query (@tanstack/react-query)
Use descriptive, stable queryKeys for React Query cache hits
Configure staleTime/cacheTime in React Query based on freshness (default ≥ 60s)
Keep tokens secret via internal API routes or server actions
Never import posthog-js in server components

Files:

  • apps/dashboard/src/@/hooks/useSplit.ts
  • apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/split/components/distribute-button.tsx
🧬 Code graph analysis (2)
apps/dashboard/src/@/hooks/useSplit.ts (1)
packages/thirdweb/src/exports/thirdweb.ts (1)
  • NATIVE_TOKEN_ADDRESS (31-31)
apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/split/components/distribute-button.tsx (1)
apps/dashboard/src/@/hooks/useSplit.ts (1)
  • useSplitDistributeFunds (79-132)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: Size
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Lint Packages
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (4)
apps/dashboard/src/@/hooks/useSplit.ts (2)

102-109: Good fix: address-normalized native token detection

Switching from name checks to getAddress(currency.tokenAddress) === getAddress(NATIVE_TOKEN_ADDRESS) is the right move and should prevent false negatives for POL/native across chains and providers.


1-11: Client-only usage confirmed – no changes needed

I’ve verified that useSplit.ts is only imported by modules that start with the "use client"; directive:

• apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/split/ContractSplitPage.tsx
• apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/account/components/account-balance.tsx
• apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/split/components/distribute-button.tsx

Since all consumers are already client components, the hook will never be imported by a server component. No changes are required.

apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/split/components/distribute-button.tsx (2)

51-52: LGTM: pending state is correctly wired to the mutation

Using distributeFundsMutation.isPending for the error state button is consistent with the main button below.


78-79: LGTM: consistent pending state on main action

The TransactionButton reflects the mutation pending state appropriately.

<!--

## title your PR with this format: "[SDK/Dashboard/Portal] Feature/Fix: Concise title for the changes"

If you did not copy the branch name from Linear, paste the issue tag here (format is TEAM-0000):

## Notes for the reviewer

Anything important to call out? Be sure to also clarify these in your comments.

## How to test

Unit tests, playground, etc.

-->

<!-- start pr-codex -->

---

## PR-Codex overview
This PR focuses on improving the `useSplitDistributeFunds` hook and the `DistributeButton` component by refining the distribution logic and enhancing error handling.

### Detailed summary
- Replaced direct comparison of `currency.name` with a check using `getAddress(currency.tokenAddress)` against `getAddress(NATIVE_TOKEN_ADDRESS)`.
- Added `await` for the promise in the `useSplitDistributeFunds` function.
- Renamed the mutation variable in `DistributeButton` from `mutation` to `distributeFundsMutation`.
- Updated the `distributeFunds` function to use `distributeFundsMutation.mutateAsync()`.
- Adjusted the `isPending` prop in `TransactionButton` to reference `distributeFundsMutation.isPending`.

> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`

<!-- end pr-codex -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

## Summary by CodeRabbit

- Bug Fixes
  - Correctly detects and handles the native token during fund distribution, ensuring accurate routing and transaction counts.
  - Ensures each distribution transaction completes before the next begins, reducing partial or overlapping operations.

- Refactor
  - Streamlined distribution flow and loading state handling for a more consistent experience.
  - Removed toast-based error pop-ups during distribution; status is reflected via the ongoing operation state.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@graphite-app graphite-app Bot force-pushed the 08-26-_bld-143_dashboard_fix_distribute_funds_in_split_contract branch from e69fa41 to 27f50a8 Compare August 25, 2025 20:09
@vercel vercel Bot temporarily deployed to Preview – nebula August 25, 2025 20:09 Inactive
@vercel vercel Bot temporarily deployed to Preview – thirdweb_playground August 25, 2025 20:09 Inactive
@vercel vercel Bot temporarily deployed to Preview – docs-v2 August 25, 2025 20:09 Inactive
@vercel vercel Bot temporarily deployed to Preview – wallet-ui August 25, 2025 20:09 Inactive
@graphite-app graphite-app Bot merged commit 27f50a8 into main Aug 25, 2025
25 checks passed
@graphite-app graphite-app Bot deleted the 08-26-_bld-143_dashboard_fix_distribute_funds_in_split_contract branch August 25, 2025 20:18
@vercel vercel Bot temporarily deployed to Production – thirdweb_playground August 25, 2025 20:18 Inactive
@vercel vercel Bot temporarily deployed to Production – wallet-ui August 25, 2025 20:18 Inactive
@vercel vercel Bot temporarily deployed to Production – docs-v2 August 25, 2025 20:18 Inactive
@vercel vercel Bot temporarily deployed to Production – nebula August 25, 2025 20:18 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Dashboard Involves changes to the Dashboard.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants