feat(squeeze): launchpad deployments, trades, labels (Base, Robinhood, Solana) - #9904
feat(squeeze): launchpad deployments, trades, labels (Base, Robinhood, Solana)#9904flockain wants to merge 1 commit into
Conversation
Identify Squeeze launches on Base/Robinhood via Doppler Airlock integrator and on Solana via Raydium LaunchLab platform_config. Co-authored-by: Cursor <cursoragent@cursor.com>
github-actions
Bot
added
WIP
|
CLA Assistant Lite bot: I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 3 potential issues.
Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.
Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit b83fbe4. Configure here.
| AND ( | ||
| t.token_bought_address = d.token | ||
| OR t.token_sold_address = d.token | ||
| ) |
There was a problem hiding this comment.
OR-join on dex.trades
High Severity
The join to dex.trades uses OR across token_bought_address and token_sold_address, which forces a Trino NestedLoopJoin on a very large fact table. If both sides of a trade are Squeeze tokens, the join also emits duplicate merge keys and can fail MERGE.
Additional Locations (1)
Triggered by learned rule: Flag OR-join conditions forcing Trino NestedLoopJoin — split into UNION ALL of equi-joins
Reviewed by Cursor Bugbot for commit b83fbe4. Configure here.
| {% else %} | ||
| AND b.block_time >= TIMESTAMP '{{ project_start_date }}' | ||
| {% endif %} | ||
| GROUP BY b.pool_id, b.base_token_mint, b.quote_token_mint, b.platform_config |
There was a problem hiding this comment.
Launch time drifts on merge
High Severity
squeeze_solana_launches MERGEs on pool_id while computing MIN(block_time) only over the incremental window. Later trades for an existing pool overwrite the stored launch time with a later minimum, corrupting launch timestamps.
Reviewed by Cursor Bugbot for commit b83fbe4. Configure here.
| - block_month | ||
| - blockchain | ||
| - tx_hash | ||
| - evt_index |
There was a problem hiding this comment.
Missing unique-key null tests
Medium Severity
New incremental MERGE models have unique_combination_of_columns aligned with unique_key, but lack not_null tests on each unique-key column. That violates the merge-key schema test rule and leaves NULL key collisions unchecked.
Additional Locations (2)
Triggered by learned rule: Flag new incremental MERGE models missing schema tests on unique_key columns
Reviewed by Cursor Bugbot for commit b83fbe4. Configure here.
1 participant
Summary
Adds Squeeze launchpad abstractions (deployments + trades + address labels).
Methodology
createfiltered by integrator0x6C61feE73584670AbEd65101946734006DAB12d6; assets from decodedcreateoutputsraydium_launchlabfiltered byplatform_config = FpKUW9…AW3hdex.trades/ LaunchLab trades (attribution table; may double-count vs Uniswap/Raydium)Notes for reviewers
source('doppler_*', 'Airlock_call_create')). Namespaces/column names will be updated once decode lands (createtakes acreateDatastruct containingintegrator).Test plan
dbt slim cigreen (may need decoded Airlock sources first)blockchain = 'robinhood')labels_squeezeappears inlabels.addressesunionMade with Cursor