Update method/Readme.md
Browse files- method/Readme.md +1 -1
method/Readme.md
CHANGED
|
@@ -108,7 +108,7 @@ We utilize Google BigQuery to extract Ethereum's blockchain data, including time
|
|
| 108 |
<p>For varying periods <code>$k$</code>, the regressor variable for the preceding <code>$k$</code> data points is collected into a list, forming the feature set <code>$X$</code>. The variable <code>$Y$</code> corresponds precisely to the prediction variable for the data point at time <code>$t$</code>.</p>
|
| 109 |
|
| 110 |
#### Off-chain data
|
| 111 |
-
|
| 112 |
<table>
|
| 113 |
<thead>
|
| 114 |
<tr>
|
|
|
|
| 108 |
<p>For varying periods <code>$k$</code>, the regressor variable for the preceding <code>$k$</code> data points is collected into a list, forming the feature set <code>$X$</code>. The variable <code>$Y$</code> corresponds precisely to the prediction variable for the data point at time <code>$t$</code>.</p>
|
| 109 |
|
| 110 |
#### Off-chain data
|
| 111 |
+
We focused our analysis on key communities within the blockchain ecosystem, specifically targeting the Binance, Uniswap, and Ethereum Dev channels on Discord. These communities represent major segments of the industry: Binance as the largest centralized exchange, Uniswap as a leading decentralized exchange, and Ethereum Dev as a hub for Ethereum developers. Our data collection involved querying the discussion text from the "general" channels of these three communities.We query all the discussion data of the selected channels, starting from the establish date of each channel until April 2, 2024. After aggregating the text data, we compiled a total of 728863 individual discussion entries.
|
| 112 |
<table>
|
| 113 |
<thead>
|
| 114 |
<tr>
|