You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/blockchain/BSC/four-meme-api.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,7 +94,7 @@ Follow the steps here to create one: https://docs.bitquery.io/docs/authorisation
94
94
-[Get liquidity of a Four Meme token ➤](#get-liquidity-of-a-four-meme-token)
95
95
-[Track Liquidity Add Events for All Tokens on Four Meme ➤](#track-liquidity-add-events-for-all-tokens-on-four-meme)
96
96
-[Track Liquidity Add Events for a Token on Four Meme ➤](#track-liquidity-add-events-for-a-token-on-four-meme)
97
-
-[Check if a Token is Phishy ➤](#check-if-a-token-is-phishy)
97
+
-[Check if a Four.meme Token is Phishy ➤](#check-if-a-fourmeme-token-is-phishy)
98
98
99
99
### 3. Trader Insights
100
100
@@ -1799,7 +1799,7 @@ You can run the query [here](https://ide.bitquery.io/Liquidity-Added-to-specific
1799
1799
1800
1800
</details>
1801
1801
1802
-
## Check if a Token is Phishy
1802
+
## Check if a Four.meme Token is Phishy
1803
1803
1804
1804
This elaborative API approach uses two queries to detect if a Four Meme token is potentially phishy by analyzing the relationship between token transfers and trades.
1805
1805
This approach helps identify tokens where recipients received tokens without purchasing them, which is a common pattern in phishing or airdrop scams.
@@ -1823,7 +1823,7 @@ We are taking here example of `0x35a7bb282d8caafe71617c9d52ee30f1adfe4444` token
1823
1823
1824
1824
This query retrieves the first transfer of a token to each address, providing the timestamp when each address first received the token.
Copy file name to clipboardExpand all lines: docs/blockchain/Solana/Pumpfun/Pump-Fun-API.mdx
+147-3Lines changed: 147 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,19 +103,23 @@ import VideoPlayer from "../../../../src/components/videoplayer.js";
103
103
104
104
### 6. Token Holder & Trader Insights
105
105
106
-
-[Get Dev’s Holdings of a Token ➤](#get-devs-holdings-of-a-token)
106
+
-[Get Dev's Holdings of a Token ➤](#get-devs-holdings-of-a-token)
107
107
-[Get Top 10 Token Holders ➤](#get-top-10-token-holders)
108
108
-[Get Top Traders of a Token ➤](#get-top-traders-of-a-token)
109
109
-[Get Top Token Creators ➤](#get-top-token-creators)
110
110
111
-
### 7. Token Rankings & Filters
111
+
### 7. Token Security & Analysis
112
+
113
+
-[Check if a Pump.fun Token is Phishy ➤](#check-if-a-pumpfun-token-is-phishy)
114
+
115
+
### 8. Token Rankings & Filters
112
116
113
117
-[Top Pump.fun Tokens by Market Cap ➤](#top-pumpfun-tokens-by-market-cap)
114
118
-[All Tokens Above 10K Market Cap ➤](#all-tokens-above-10k-market-cap)
115
119
-[Track King of the Hill Tokens ➤](#track-king-of-the-hill-tokens-30k35k-market-cap)
116
120
-[Tokens Between 400K–450K Market Cap ➤](#tokens-between-400k450k-market-cap-with-dev--creation-time)
117
121
118
-
### 8.[ Video Tutorials](#video-tutorials)
122
+
### 9.[ Video Tutorials](#video-tutorials)
119
123
120
124
## Token Creation & Metadata
121
125
@@ -1597,6 +1601,146 @@ query MyQuery {
1597
1601
1598
1602
</details>
1599
1603
1604
+
## Token Security & Analysis
1605
+
1606
+
### Check if a Pump.fun Token is Phishy
1607
+
1608
+
This elaborative API approach uses two queries to detect if a Pump.fun token is potentially phishy by analyzing the relationship between token transfers and trades.
1609
+
This approach helps identify tokens where recipients received tokens without purchasing them, which is a common pattern in phishing or airdrop scams.
1610
+
1611
+
#### How It Works
1612
+
1613
+
The detection method works by:
1614
+
1615
+
1.**First Query**: Get the first transfers of a token to addresses - this provides the timestamp of when each address first received the token.
1616
+
2.**Second Query**: Check if those addresses ever bought the token and when - pass the address list from the first query as a variable to check their purchase history.
1617
+
3.**Analysis**: Compare transfer times and trade times in your code:
1618
+
1619
+
- If an address **never bought** the token, it's suspicious.
1620
+
- If an address's **first buy time is later than the first transfer time**, it indicates the token was received before being purchased, which is a red flag for phishing behavior.
1621
+
1622
+
Above analysis means someone else transferred the token to them which is phishy because devs often send token to famous KOLs or Influential People in crypto space to misguide traders.
1623
+
1624
+
We are taking here example of `3Fymji2JPhhbKuCzNPKEyjdEuF9cyFuQ8HksyjRGpump` token, this may or may not be phishy as we are not running the further comparison between timestamps. Here we are just demonstrating that how you can get data from Bitquery and later run basic analysis on it.
1625
+
1626
+
#### Query 1: Get First Transfers of a Token to Addresses
1627
+
1628
+
This query retrieves the first transfer of a token to each address, providing the timestamp when each address first received the token.
0 commit comments