Platform: Focusing on the Rainbow Bridge used for Grail S2.
Tokens: Only transactions involving the supported asset are included (https://docs.google.com/spreadsheets/d/1lhC4pGl0-QozPFJ8T2ORHR1vFeeeBEt7kc6zScbowKo/edit?gid=0#gid=0).
Transactions Direction: Only transactions with 'inbound' identifier are included for Grail calculation.
Destination Chain: Following the previous assumption, the inbound transaction must go to NEAR.
Duplicate Transactions: Per Flipside's dbt docs for near.defi.ez_bridge_activity, 'inbound' could also mean the capital is going into Aurora instead of NEAR. Therefore, this subquery is used to remove the transactions going into Aurora.

```
SELECT 
        tx_hash
    FROM 
        NEAR.DEFI.EZ_BRIDGE_ACTIVITY
    GROUP BY 
        tx_hash
    HAVING 
        COUNT(*) > 1
```

Comparative Analysis:
- Grail S1 Aptos: Analysis for Grail covers from May 7 - June 1
- Bridge Qualification: % of bridges that qualify for NEAR is used as a basis for calculating % of bridges that qualify for Aptos.
- Price Matching: Prices are matched hourly between fact_bridge_activity ~ ez_prices_hourly tables.
- Inclusion: Only transactions where direction = 'inbound' with the destination chain labeled as 'Aptos' or 'aptos' is included.
User/Wallet Activity: Initially, an assumption that multiple non-NEAR wallets linking to a single NEAR wallet (inbound) or vice-versa (outbound). However, this would introduce complexity into the analysis. Therefore, the analysis treats each wallet = 1 user.

gregoriustanley