Skip to content

[#1299] Document T2.4b hybrid SQL helper pattern #1313

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
realproject7 merged 1 commit into from
May 26, 2026
Merged

[#1299] Document T2.4b hybrid SQL helper pattern #1313

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/airdrop-contracts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,16 @@ forge script contracts/script/DeployMerkleClaim.s.sol \
--private-key $DEPLOYER_PRIVATE_KEY
```

## Weighted Spend SQL Helper (T2.4b hybrid pattern)

The weighted spend computation uses a hybrid of T0.1's option A (TS config) and option B (DB function):

- **`lib/airdrop/sql.ts`** — TS wrapper `weightedSpendQuery(config)` returns `{sql, params}`. Config values (campaign dates, thresholds, multiplier params) flow from `getAirdropConfig()` at call time, supporting test-fast/test-full/prod modes.
- **`supabase/migrations/00041_weighted_spend_function.sql`** — Postgres function `weighted_spend(...)` is the single canonical SQL definition. All consumers (finalize script, /projection, /leaderboard) call this function.
- **`lib/airdrop/sql.ts:weightedSpendQuery()`** returns `SELECT * FROM weighted_spend($1, $2, $3, $4, $5)` — the TS wrapper delegates to the DB function.

This avoids both option A's risk (SQL string drift across consumers) and option B's downside (DB-resident config table).

## Settlement (finalize)

```bash
Expand Down
Loading