Upload 172 files

.gitattributes

@@ -33,3 +33,7 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
 *.zip filter=lfs diff=lfs merge=lfs -text
 *.zst filter=lfs diff=lfs merge=lfs -text
 *tfevents* filter=lfs diff=lfs merge=lfs -text
+bitcoinforum/2_train_set_creation/inputs.csv filter=lfs diff=lfs merge=lfs -text
+bitcoinforum/3_training/old/bert/validation_samples.html filter=lfs diff=lfs merge=lfs -text
+bitcoinforum/5_processing_extracted_data/hardware_instances_inc_threads.csv filter=lfs diff=lfs merge=lfs -text
+bitcoinforum/5_processing_extracted_data/not_usable_threads.txt filter=lfs diff=lfs merge=lfs -text

bitcoinforum/1_forum_dataset/cleaned-data/groupbuys.pkl.gz

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9aa8033eabcd022d8e50564530e94fab08b567c159247b9cfc3b1fd5a0174951
+size 7561178

bitcoinforum/1_forum_dataset/cleaned-data/hardware.pkl.gz

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0b2932b4b1ae8492cef458ac0b3ad7030cc6bda33061b22b642a9975453570d4
+size 42232442

bitcoinforum/1_forum_dataset/cleaned-data/miners.pkl.gz

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69f583f707ac16e8058d4d8e2f511c671421c306def40ea620c051de429bf6ec
+size 8792683

bitcoinforum/1_forum_dataset/cleaned-data/mining.pkl.gz

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d94c8fde1c5a3b16b9cc38952549821b3190c3d748d08d2f4855e21b8e8b0f39
+size 5428217

bitcoinforum/1_forum_dataset/cleaned-data/mining_speculation.pkl.gz

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6cd17020a451fffadbcad4d2531c1cddd55d4a10ef4fd586ff7b71d832f0450c
+size 8787062

bitcoinforum/1_forum_dataset/cleaned-data/mining_support.pkl.gz

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:14cff87fbce3372a3830a26e1bc502e5688167df29654a06daa0184bf8d61fb0
+size 10946649

bitcoinforum/1_forum_dataset/cleaned-data/pools.pkl.gz

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:804f62c2b470f75442ad5e94627a276a62ba59672c41c45e296c945a1c1f0ea1
+size 22502221

bitcoinforum/1_forum_dataset/cleanup_data.ipynb

@@ -0,0 +1,478 @@
+{
+ "cells": [
+  {
+   "cell_type": "code",
+   "execution_count": 49,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "import pandas as pd\n",
+    "import os\n",
+    "import re\n",
+    "from bs4 import BeautifulSoup\n",
+    "pd.set_option('display.max_rows', 50)\n",
+    "\n",
+    "df = pd.DataFrame()\n",
+    "\n",
+    "# category = \"groupbuys\"\n",
+    "# category = \"hardware\"\n",
+    "# category = \"miners\"\n",
+    "# category = \"mining\"\n",
+    "# category = \"mining_speculation\"\n",
+    "# category = \"mining_support\"\n",
+    "category = \"pools\"\n",
+    "\n",
+    "\n",
+    "folder2 = \"raw-data\"\n",
+    "\n",
+    "#load every csv in the folder and append them\n",
+    "csv = os.listdir(folder2+\"/\"+category)\n",
+    "for file in csv:\n",
+    "    df = pd.concat([df, pd.read_csv(folder2+\"/\"+category+\"/\"+file)], axis=0)\n",
+    "\n",
+    "df[\"original_info\"] = df[\"original_info\"].astype(str)\n",
+    "df = df.reset_index(drop=True)\n",
+    "\n",
+    "#shorten df to test code\n",
+    "# df = df[:300]\n",
+    "\n",
+    "def clean_row(row):\n",
+    "    html = row[\"original_info\"]\n",
+    "    soup = BeautifulSoup(html, 'html.parser')\n",
+    "    #the date is in <div class=\"smalltext\">\n",
+    "    date = soup.find(\"div\", {\"class\": \"smalltext\"}).text\n",
+    "    #if the date contains \"Last edit: \", use that instead\n",
+    "    if \"Last edit:\" in date:\n",
+    "        date = date.split(\"Last edit: \")[1]\n",
+    "    if \" by \" in date:\n",
+    "        date = date.split(\" by \")[0]\n",
+    "    #delete <div class=\"quote\">\n",
+    "    for quote in soup.find_all(\"div\", {\"class\": \"quote\"}):\n",
+    "        quote.decompose()\n",
+    "    for quote in soup.find_all(\"div\", {\"class\": \"quoteheader\"}):\n",
+    "        quote.decompose()\n",
+    "    #post is in <div class=\"post\">\n",
+    "    post = soup.find(\"div\", {\"class\": \"post\"}).text\n",
+    "    #remove all links\n",
+    "    post = re.sub(r'http\\S+', '<link>', post)\n",
+    "    #remove duplicate spaces\n",
+    "    post = re.sub(' +', ' ', post)\n",
+    "    #remove all non-ascii characters\n",
+    "    post = post.encode(\"ascii\", errors=\"ignore\").decode()\n",
+    "    #remove all words that have a length above 20 (most likely a btc address or something useless)\n",
+    "    post = \" \".join([(word if len(word) < 20 else \"<truncated>\") for word in post.split()])\n",
+    "\n",
+    "    return post, date\n"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 50,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "df[\"post\"], df[\"date\"] = zip(*df.apply(clean_row, axis=1))"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 51,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/html": [
+       "<div>\n",
+       "<style scoped>\n",
+       "    .dataframe tbody tr th:only-of-type {\n",
+       "        vertical-align: middle;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe tbody tr th {\n",
+       "        vertical-align: top;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe thead th {\n",
+       "        text-align: right;\n",
+       "    }\n",
+       "</style>\n",
+       "<table border=\"1\" class=\"dataframe\">\n",
+       "  <thead>\n",
+       "    <tr style=\"text-align: right;\">\n",
+       "      <th></th>\n",
+       "      <th>topic</th>\n",
+       "      <th>post</th>\n",
+       "      <th>date</th>\n",
+       "    </tr>\n",
+       "  </thead>\n",
+       "  <tbody>\n",
+       "    <tr>\n",
+       "      <th>47128</th>\n",
+       "      <td>Cooperative mining</td>\n",
+       "      <td>Actually, they are equal. The low-power machin...</td>\n",
+       "      <td>2010-11-27 14:35:56</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>47138</th>\n",
+       "      <td>Cooperative mining</td>\n",
+       "      <td>I will offer a Six-Way AMD Processor to the Co...</td>\n",
+       "      <td>2010-11-27 14:48:03</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>47137</th>\n",
+       "      <td>Cooperative mining</td>\n",
+       "      <td>i always liked the idea of distributed mining,...</td>\n",
+       "      <td>2010-11-27 14:48:49</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>47136</th>\n",
+       "      <td>Cooperative mining</td>\n",
+       "      <td>Sure seems fair its better then waiting 1 year...</td>\n",
+       "      <td>2010-11-27 16:12:24</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>47135</th>\n",
+       "      <td>Cooperative mining</td>\n",
+       "      <td>You are true for long term. But I think many p...</td>\n",
+       "      <td>2010-11-27 16:20:26</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>...</th>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>122306</th>\n",
+       "      <td>[∞ YH] solo.ckpool.org 2% fee solo mining 277...</td>\n",
+       "      <td>I would love to add another 0 to get 20 th. Un...</td>\n",
+       "      <td>2023-10-25 04:39:10</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>122303</th>\n",
+       "      <td>[∞ YH] solo.ckpool.org 2% fee solo mining 277...</td>\n",
+       "      <td>Even if you add a zero go from 2 to 20 th you ...</td>\n",
+       "      <td>2023-10-25 13:25:21</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>122308</th>\n",
+       "      <td>[∞ YH] solo.ckpool.org 2% fee solo mining 277...</td>\n",
+       "      <td>You still mining on that small pool? is it sti...</td>\n",
+       "      <td>2023-10-25 17:50:03</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>122304</th>\n",
+       "      <td>[∞ YH] solo.ckpool.org 2% fee solo mining 277...</td>\n",
+       "      <td>Hello all,The Blockparty 47 is over, no block ...</td>\n",
+       "      <td>2023-10-25 19:33:12</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>122305</th>\n",
+       "      <td>[∞ YH] solo.ckpool.org 2% fee solo mining 277...</td>\n",
+       "      <td>Blockparty 48 is fillig up. looks like we star...</td>\n",
+       "      <td>2023-10-25 19:34:44</td>\n",
+       "    </tr>\n",
+       "  </tbody>\n",
+       "</table>\n",
+       "<p>209797 rows × 3 columns</p>\n",
+       "</div>"
+      ],
+      "text/plain": [
+       "                                                    topic  \\\n",
+       "47128                                  Cooperative mining   \n",
+       "47138                                  Cooperative mining   \n",
+       "47137                                  Cooperative mining   \n",
+       "47136                                  Cooperative mining   \n",
+       "47135                                  Cooperative mining   \n",
+       "...                                                   ...   \n",
+       "122306   [∞ YH] solo.ckpool.org 2% fee solo mining 277...   \n",
+       "122303   [∞ YH] solo.ckpool.org 2% fee solo mining 277...   \n",
+       "122308   [∞ YH] solo.ckpool.org 2% fee solo mining 277...   \n",
+       "122304   [∞ YH] solo.ckpool.org 2% fee solo mining 277...   \n",
+       "122305   [∞ YH] solo.ckpool.org 2% fee solo mining 277...   \n",
+       "\n",
+       "                                                     post                date  \n",
+       "47128   Actually, they are equal. The low-power machin... 2010-11-27 14:35:56  \n",
+       "47138   I will offer a Six-Way AMD Processor to the Co... 2010-11-27 14:48:03  \n",
+       "47137   i always liked the idea of distributed mining,... 2010-11-27 14:48:49  \n",
+       "47136   Sure seems fair its better then waiting 1 year... 2010-11-27 16:12:24  \n",
+       "47135   You are true for long term. But I think many p... 2010-11-27 16:20:26  \n",
+       "...                                                   ...                 ...  \n",
+       "122306  I would love to add another 0 to get 20 th. Un... 2023-10-25 04:39:10  \n",
+       "122303  Even if you add a zero go from 2 to 20 th you ... 2023-10-25 13:25:21  \n",
+       "122308  You still mining on that small pool? is it sti... 2023-10-25 17:50:03  \n",
+       "122304  Hello all,The Blockparty 47 is over, no block ... 2023-10-25 19:33:12  \n",
+       "122305  Blockparty 48 is fillig up. looks like we star... 2023-10-25 19:34:44  \n",
+       "\n",
+       "[209797 rows x 3 columns]"
+      ]
+     },
+     "execution_count": 51,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "df = df[['topic', 'post', 'date']]\n",
+    "# replace \"Today at \" with \"October 1, 2023, \"\n",
+    "df[\"date\"] = df[\"date\"].str.replace(\"Today at \", \"September 21, 2023, \")\n",
+    "df['date'] = pd.to_datetime(df['date'])\n",
+    "df = df.sort_values(by=[\"date\"])\n",
+    "#remove \"Re: \" from topic\n",
+    "df[\"topic\"] = df[\"topic\"].str.replace(\"Re: \", \"\")\n",
+    "df"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 52,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "# group by topic and append all the strings from the post column\n",
+    "df[\"date\"] = df[\"date\"].astype(str)\n",
+    "df = df.groupby('topic').agg({'post': '<sep>'.join, 'date': '<sep>'.join}).reset_index()"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 53,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "df[\"dates\"] = df[\"date\"]\n",
+    "df['date'] = df['date'].apply(lambda x: x.split(\"<sep>\")[-1])\n",
+    "df['date'] = pd.to_datetime(df['date'])\n",
+    "df = df.sort_values(by=[\"date\"])"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 54,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/html": [
+       "<div>\n",
+       "<style scoped>\n",
+       "    .dataframe tbody tr th:only-of-type {\n",
+       "        vertical-align: middle;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe tbody tr th {\n",
+       "        vertical-align: top;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe thead th {\n",
+       "        text-align: right;\n",
+       "    }\n",
+       "</style>\n",
+       "<table border=\"1\" class=\"dataframe\">\n",
+       "  <thead>\n",
+       "    <tr style=\"text-align: right;\">\n",
+       "      <th></th>\n",
+       "      <th>topic</th>\n",
+       "      <th>post</th>\n",
+       "      <th>date</th>\n",
+       "      <th>dates</th>\n",
+       "    </tr>\n",
+       "  </thead>\n",
+       "  <tbody>\n",
+       "    <tr>\n",
+       "      <th>757</th>\n",
+       "      <td>Cooperative mining (&gt;900Mhash/s already, join ...</td>\n",
+       "      <td>You might like to code this feature:When we fi...</td>\n",
+       "      <td>2010-12-16 08:55:56</td>\n",
+       "      <td>2010-12-16 08:11:14&lt;sep&gt;2010-12-16 08:23:31&lt;se...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>748</th>\n",
+       "      <td>Cooperative mining (&gt;1100Mhash/s already, join...</td>\n",
+       "      <td>yay, seems like we already solved our 2nd bloc...</td>\n",
+       "      <td>2010-12-16 18:13:08</td>\n",
+       "      <td>2010-12-16 15:46:03&lt;sep&gt;2010-12-16 16:07:10&lt;se...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>749</th>\n",
+       "      <td>Cooperative mining (&gt;1300Mhash/s already, join...</td>\n",
+       "      <td>It is explained on homepage - by my extremely ...</td>\n",
+       "      <td>2010-12-17 01:55:12</td>\n",
+       "      <td>2010-12-16 18:27:35&lt;sep&gt;2010-12-16 18:35:23&lt;se...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>750</th>\n",
+       "      <td>Cooperative mining (&gt;1500Mhash/s already, join...</td>\n",
+       "      <td>2 transactions received.12.08btc contributing ...</td>\n",
+       "      <td>2010-12-18 02:08:13</td>\n",
+       "      <td>2010-12-17 02:24:00&lt;sep&gt;2010-12-17 03:02:15&lt;se...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>751</th>\n",
+       "      <td>Cooperative mining (&gt;1700Mhash/s, join us!)</td>\n",
+       "      <td>Well done, fifth block is arriving!</td>\n",
+       "      <td>2010-12-18 02:18:39</td>\n",
+       "      <td>2010-12-18 02:18:39</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>...</th>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>5233</th>\n",
+       "      <td>pool.vkbit.com - solo mining pool [stats @ vkb...</td>\n",
+       "      <td>Almost free service, from now on our fee is 0....</td>\n",
+       "      <td>2023-09-11 13:10:05</td>\n",
+       "      <td>2023-09-11 13:01:02&lt;sep&gt;2023-09-11 13:03:03&lt;se...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>5234</th>\n",
+       "      <td>pool.vkbit.com - the ultimate Bitcoin solo min...</td>\n",
+       "      <td>I hope this is useful for low hash rate miners...</td>\n",
+       "      <td>2023-09-15 06:22:09</td>\n",
+       "      <td>2023-09-15 06:22:09</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>5049</th>\n",
+       "      <td>deleted</td>\n",
+       "      <td>Thanks&lt;sep&gt;thanks&lt;sep&gt;deleted&lt;sep&gt;.</td>\n",
+       "      <td>2023-09-19 18:37:58</td>\n",
+       "      <td>2014-03-04 08:53:58&lt;sep&gt;2014-03-04 08:54:42&lt;se...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>1246</th>\n",
+       "      <td>KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fe...</td>\n",
+       "      <td>&lt;link&gt; payout help and information: &lt;link&gt; mos...</td>\n",
+       "      <td>2023-10-18 12:27:23</td>\n",
+       "      <td>2023-08-05 16:20:00&lt;sep&gt;2023-08-05 22:53:30&lt;se...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>69</th>\n",
+       "      <td>[∞ YH] solo.ckpool.org 2% fee solo mining 277...</td>\n",
+       "      <td>Congrats!!!!&lt;sep&gt;Big congrats to the miner! At...</td>\n",
+       "      <td>2023-10-25 19:34:44</td>\n",
+       "      <td>2023-08-19 10:36:28&lt;sep&gt;2023-08-19 13:57:52&lt;se...</td>\n",
+       "    </tr>\n",
+       "  </tbody>\n",
+       "</table>\n",
+       "<p>5325 rows × 4 columns</p>\n",
+       "</div>"
+      ],
+      "text/plain": [
+       "                                                  topic  \\\n",
+       "757   Cooperative mining (>900Mhash/s already, join ...   \n",
+       "748   Cooperative mining (>1100Mhash/s already, join...   \n",
+       "749   Cooperative mining (>1300Mhash/s already, join...   \n",
+       "750   Cooperative mining (>1500Mhash/s already, join...   \n",
+       "751         Cooperative mining (>1700Mhash/s, join us!)   \n",
+       "...                                                 ...   \n",
+       "5233  pool.vkbit.com - solo mining pool [stats @ vkb...   \n",
+       "5234  pool.vkbit.com - the ultimate Bitcoin solo min...   \n",
+       "5049                                            deleted   \n",
+       "1246  KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fe...   \n",
+       "69     [∞ YH] solo.ckpool.org 2% fee solo mining 277...   \n",
+       "\n",
+       "                                                   post                date  \\\n",
+       "757   You might like to code this feature:When we fi... 2010-12-16 08:55:56   \n",
+       "748   yay, seems like we already solved our 2nd bloc... 2010-12-16 18:13:08   \n",
+       "749   It is explained on homepage - by my extremely ... 2010-12-17 01:55:12   \n",
+       "750   2 transactions received.12.08btc contributing ... 2010-12-18 02:08:13   \n",
+       "751                 Well done, fifth block is arriving! 2010-12-18 02:18:39   \n",
+       "...                                                 ...                 ...   \n",
+       "5233  Almost free service, from now on our fee is 0.... 2023-09-11 13:10:05   \n",
+       "5234  I hope this is useful for low hash rate miners... 2023-09-15 06:22:09   \n",
+       "5049                Thanks<sep>thanks<sep>deleted<sep>. 2023-09-19 18:37:58   \n",
+       "1246  <link> payout help and information: <link> mos... 2023-10-18 12:27:23   \n",
+       "69    Congrats!!!!<sep>Big congrats to the miner! At... 2023-10-25 19:34:44   \n",
+       "\n",
+       "                                                  dates  \n",
+       "757   2010-12-16 08:11:14<sep>2010-12-16 08:23:31<se...  \n",
+       "748   2010-12-16 15:46:03<sep>2010-12-16 16:07:10<se...  \n",
+       "749   2010-12-16 18:27:35<sep>2010-12-16 18:35:23<se...  \n",
+       "750   2010-12-17 02:24:00<sep>2010-12-17 03:02:15<se...  \n",
+       "751                                 2010-12-18 02:18:39  \n",
+       "...                                                 ...  \n",
+       "5233  2023-09-11 13:01:02<sep>2023-09-11 13:03:03<se...  \n",
+       "5234                                2023-09-15 06:22:09  \n",
+       "5049  2014-03-04 08:53:58<sep>2014-03-04 08:54:42<se...  \n",
+       "1246  2023-08-05 16:20:00<sep>2023-08-05 22:53:30<se...  \n",
+       "69    2023-08-19 10:36:28<sep>2023-08-19 13:57:52<se...  \n",
+       "\n",
+       "[5325 rows x 4 columns]"
+      ]
+     },
+     "execution_count": 54,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "df"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 55,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "# import matplotlib.pyplot as plt\n",
+    "# plt.hist(df[\"start_edit\"], bins=10, edgecolor='black')\n",
+    "\n",
+    "# # Add labels and title\n",
+    "# plt.xlabel('date')\n",
+    "# plt.ylabel('Value')\n",
+    "# plt.title('Bar Plot of Integers')\n",
+    "\n",
+    "# # Show the plot\n",
+    "# plt.show()\n",
+    "\n",
+    "# print(df[\"start_edit\"].max())\n",
+    "# print(df[\"start_edit\"].min())"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 56,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "import gzip\n",
+    "import pickle\n",
+    "#save to gzip\n",
+    "with gzip.open('cleaned-data/'+category+'.pkl.gz', 'wb') as f:\n",
+    "    pickle.dump(df, f)"
+   ]
+  }
+ ],
+ "metadata": {
+  "kernelspec": {
+   "display_name": "base",
+   "language": "python",
+   "name": "python3"
+  },
+  "language_info": {
+   "codemirror_mode": {
+    "name": "ipython",
+    "version": 3
+   },
+   "file_extension": ".py",
+   "mimetype": "text/x-python",
+   "name": "python",
+   "nbconvert_exporter": "python",
+   "pygments_lexer": "ipython3",
+   "version": "3.9.7"
+  },
+  "orig_nbformat": 4,
+  "vscode": {
+   "interpreter": {
+    "hash": "ad2bdc8ecc057115af97d19610ffacc2b4e99fae6737bb82f5d7fb13d2f2c186"
+   }
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 2
+}

bitcoinforum/1_forum_dataset/raw-data.7z

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d92d73303939843ac61618d54e04c1591aecf2729444c4d4e672a66c9a6e0d8
+size 187100606

bitcoinforum/2_train_set_creation/create_train_set.ipynb

@@ -0,0 +1,2133 @@
+{
+ "cells": [
+  {
+   "cell_type": "code",
+   "execution_count": 1,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "DEMO_MODE = True"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 2,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "import pandas as pd\n",
+    "import os\n",
+    "import gzip\n",
+    "import pickle\n",
+    "from openai import OpenAI\n",
+    "import torch.nn.functional as F\n",
+    "import torch\n",
+    "from tqdm import tqdm\n",
+    "import json\n",
+    "import numpy as np"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "client = OpenAI()"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 4,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "def get_openai_response(prompt):\n",
+    "    tokens = 1000\n",
+    "    model=\"gpt-4-turbo-preview\" if not DEMO_MODE else \"gpt-4o-mini\"\n",
+    "    # model=\"gpt-3.5-turbo-0125\"\n",
+    "    response = client.chat.completions.create(\n",
+    "        model=model,\n",
+    "        messages=[\n",
+    "            {\n",
+    "                \"role\": \"system\",\n",
+    "                \"content\": \"You are a helpful assistant\"\n",
+    "            },\n",
+    "            {\n",
+    "                \"role\": \"user\",\n",
+    "                \"content\": prompt\n",
+    "            }\n",
+    "            ],\n",
+    "        temperature=0,\n",
+    "        max_tokens=tokens,\n",
+    "        top_p=1,\n",
+    "    )\n",
+    "    choice = response.choices[0]\n",
+    "\n",
+    "    text = choice.message.content\n",
+    "\n",
+    "\n",
+    "    return text"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 5,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "def process_thread(row):\n",
+    "    try:\n",
+    "        date = row[\"dates\"].split(\"<sep>\")[-1]\n",
+    "\n",
+    "        thread = \"\"\n",
+    "        thread += \"Date: \" + date[:7] + \"\\n\"\n",
+    "        thread += \"Topic: \" + row[\"topic\"] + \"\\n\"        \n",
+    "        thread += \"### Original post:\\n\"\n",
+    "        i = 1\n",
+    "        for (post, date) in zip(row[\"post\"].split(\"<sep>\"), row[\"dates\"].split(\"<sep>\")):\n",
+    "            if len(post) > 1200:\n",
+    "                thread += post[:1200] + \"<rest of post truncated>\\n\\n\"\n",
+    "                thread += f\"### Reply {i}:\\n\"\n",
+    "                i += 1\n",
+    "            elif len(post) < 5:\n",
+    "                pass\n",
+    "            else:\n",
+    "                thread += post + \"\\n\\n\"\n",
+    "                thread += f\"### Reply {i}:\\n\"\n",
+    "                i += 1\n",
+    "        #remove the last line\n",
+    "        thread = thread[:-len(f\"### Reply {i-1}:\\n\")]\n",
+    "        if len(thread) > 5000:\n",
+    "            thread = thread[:5000] + \"<rest of thread truncated>\\n\"\n",
+    "\n",
+    "        return row[\"index\"], date, thread\n",
+    "\n",
+    "    except:\n",
+    "        print(\"Error processing thread:\" + str(row[\"index\"]))\n",
+    "        return None, None, None\n",
+    "\n"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 6,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "refresh_df = False\n",
+    "# refresh_df = True\n",
+    "\n",
+    "if refresh_df:\n",
+    "    categories = [\n",
+    "        \"groupbuys\",\n",
+    "        \"hardware\",\n",
+    "        \"miners\",\n",
+    "        \"mining\",\n",
+    "        \"mining_support\",\n",
+    "        # \"pools\",\n",
+    "    ]\n",
+    "\n",
+    "    df = pd.DataFrame()\n",
+    "\n",
+    "    #load every csv in the folder and append them\n",
+    "    for cat in categories:\n",
+    "        with gzip.open('../1_forum_dataset/cleaned-data/'+cat+'.pkl.gz', 'rb') as f:\n",
+    "            df_cat = pickle.load(f)\n",
+    "            df_cat['category'] = cat\n",
+    "            df = pd.concat([df, df_cat], ignore_index=True)\n",
+    "\n",
+    "    df[\"index\"] = df.index\n",
+    "    df.to_csv(\"cache.csv\", index=False)\n",
+    "\n",
+    "else:\n",
+    "    df = pd.read_csv(\"cache.csv\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 7,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/html": [
+       "<div>\n",
+       "<style scoped>\n",
+       "    .dataframe tbody tr th:only-of-type {\n",
+       "        vertical-align: middle;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe tbody tr th {\n",
+       "        vertical-align: top;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe thead th {\n",
+       "        text-align: right;\n",
+       "    }\n",
+       "</style>\n",
+       "<table border=\"1\" class=\"dataframe\">\n",
+       "  <thead>\n",
+       "    <tr style=\"text-align: right;\">\n",
+       "      <th></th>\n",
+       "      <th>topic</th>\n",
+       "      <th>post</th>\n",
+       "      <th>date</th>\n",
+       "      <th>dates</th>\n",
+       "      <th>category</th>\n",
+       "      <th>index</th>\n",
+       "    </tr>\n",
+       "  </thead>\n",
+       "  <tbody>\n",
+       "    <tr>\n",
+       "      <th>0</th>\n",
+       "      <td>[Group Buy in China]  Avalon batch #3</td>\n",
+       "      <td>List of &lt;truncated&gt; Forum Name - Bitcoin Addre...</td>\n",
+       "      <td>2013-03-25 11:06:33</td>\n",
+       "      <td>2013-03-25 10:16:23&lt;sep&gt;2013-03-25 10:42:45&lt;se...</td>\n",
+       "      <td>groupbuys</td>\n",
+       "      <td>0</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>1</th>\n",
+       "      <td>Avalon Group buy - Germany</td>\n",
+       "      <td>Hi, I'm in time to invest?&lt;sep&gt;too late, sorry</td>\n",
+       "      <td>2013-03-25 13:13:44</td>\n",
+       "      <td>2013-03-25 12:47:34&lt;sep&gt;2013-03-25 13:13:44</td>\n",
+       "      <td>groupbuys</td>\n",
+       "      <td>1</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>2</th>\n",
+       "      <td>Avalon Group buy - Germany - closed</td>\n",
+       "      <td>I am willing to organize a community purchase ...</td>\n",
+       "      <td>2013-03-25 13:14:29</td>\n",
+       "      <td>2013-03-25 13:14:29</td>\n",
+       "      <td>groupbuys</td>\n",
+       "      <td>2</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>3</th>\n",
+       "      <td>I'm about to buy Avalon asic 85</td>\n",
+       "      <td>it sold out, its gone.&lt;sep&gt;People just order b...</td>\n",
+       "      <td>2013-03-25 14:26:29</td>\n",
+       "      <td>2013-03-25 13:46:12&lt;sep&gt;2013-03-25 14:26:29</td>\n",
+       "      <td>groupbuys</td>\n",
+       "      <td>3</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>4</th>\n",
+       "      <td>CANCELLED [Group Buy in China]  Avalon batch #3</td>\n",
+       "      <td>Do you not have enough BTC to buy a batch 3 Av...</td>\n",
+       "      <td>2013-03-25 16:42:09</td>\n",
+       "      <td>2013-03-25 16:42:09</td>\n",
+       "      <td>groupbuys</td>\n",
+       "      <td>4</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>...</th>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24184</th>\n",
+       "      <td>S19 Amlogic control board brick ?</td>\n",
+       "      <td>Hello everyone, I have an amlogic s19 j pro ca...</td>\n",
+       "      <td>2023-10-23 15:51:19</td>\n",
+       "      <td>2023-08-30 13:53:04&lt;sep&gt;2023-08-30 17:45:01&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>24184</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24185</th>\n",
+       "      <td>S19jPro abnormal network - (Will not connect t...</td>\n",
+       "      <td>Driving me nuts... after changing pool address...</td>\n",
+       "      <td>2023-10-24 14:00:23</td>\n",
+       "      <td>2023-02-24 15:37:21&lt;sep&gt;2023-02-24 15:59:12&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>24185</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24186</th>\n",
+       "      <td>Flashing control Board S9 to R4</td>\n",
+       "      <td>Hello,I recently purchased a control board tha...</td>\n",
+       "      <td>2023-10-25 23:42:40</td>\n",
+       "      <td>2023-10-05 14:14:14&lt;sep&gt;2023-10-09 05:06:58&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>24186</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24187</th>\n",
+       "      <td>AvalonMiner 1166Pro-72</td>\n",
+       "      <td>Hello,can someone help me find the problem wit...</td>\n",
+       "      <td>2023-10-26 08:40:14</td>\n",
+       "      <td>2023-10-09 07:54:00&lt;sep&gt;2023-10-09 11:50:47&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>24187</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24188</th>\n",
+       "      <td>need advice to reduce noise and monitor asic m...</td>\n",
+       "      <td>I think Awesomeminer supports this unit model ...</td>\n",
+       "      <td>2023-10-27 16:39:20</td>\n",
+       "      <td>2023-09-21 11:52:00&lt;sep&gt;2023-10-27 15:31:24&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>24188</td>\n",
+       "    </tr>\n",
+       "  </tbody>\n",
+       "</table>\n",
+       "<p>24189 rows × 6 columns</p>\n",
+       "</div>"
+      ],
+      "text/plain": [
+       "                                                   topic  \\\n",
+       "0                  [Group Buy in China]  Avalon batch #3   \n",
+       "1                             Avalon Group buy - Germany   \n",
+       "2                    Avalon Group buy - Germany - closed   \n",
+       "3                        I'm about to buy Avalon asic 85   \n",
+       "4        CANCELLED [Group Buy in China]  Avalon batch #3   \n",
+       "...                                                  ...   \n",
+       "24184                  S19 Amlogic control board brick ?   \n",
+       "24185  S19jPro abnormal network - (Will not connect t...   \n",
+       "24186                    Flashing control Board S9 to R4   \n",
+       "24187                             AvalonMiner 1166Pro-72   \n",
+       "24188  need advice to reduce noise and monitor asic m...   \n",
+       "\n",
+       "                                                    post                 date  \\\n",
+       "0      List of <truncated> Forum Name - Bitcoin Addre...  2013-03-25 11:06:33   \n",
+       "1         Hi, I'm in time to invest?<sep>too late, sorry  2013-03-25 13:13:44   \n",
+       "2      I am willing to organize a community purchase ...  2013-03-25 13:14:29   \n",
+       "3      it sold out, its gone.<sep>People just order b...  2013-03-25 14:26:29   \n",
+       "4      Do you not have enough BTC to buy a batch 3 Av...  2013-03-25 16:42:09   \n",
+       "...                                                  ...                  ...   \n",
+       "24184  Hello everyone, I have an amlogic s19 j pro ca...  2023-10-23 15:51:19   \n",
+       "24185  Driving me nuts... after changing pool address...  2023-10-24 14:00:23   \n",
+       "24186  Hello,I recently purchased a control board tha...  2023-10-25 23:42:40   \n",
+       "24187  Hello,can someone help me find the problem wit...  2023-10-26 08:40:14   \n",
+       "24188  I think Awesomeminer supports this unit model ...  2023-10-27 16:39:20   \n",
+       "\n",
+       "                                                   dates        category  \\\n",
+       "0      2013-03-25 10:16:23<sep>2013-03-25 10:42:45<se...       groupbuys   \n",
+       "1            2013-03-25 12:47:34<sep>2013-03-25 13:13:44       groupbuys   \n",
+       "2                                    2013-03-25 13:14:29       groupbuys   \n",
+       "3            2013-03-25 13:46:12<sep>2013-03-25 14:26:29       groupbuys   \n",
+       "4                                    2013-03-25 16:42:09       groupbuys   \n",
+       "...                                                  ...             ...   \n",
+       "24184  2023-08-30 13:53:04<sep>2023-08-30 17:45:01<se...  mining_support   \n",
+       "24185  2023-02-24 15:37:21<sep>2023-02-24 15:59:12<se...  mining_support   \n",
+       "24186  2023-10-05 14:14:14<sep>2023-10-09 05:06:58<se...  mining_support   \n",
+       "24187  2023-10-09 07:54:00<sep>2023-10-09 11:50:47<se...  mining_support   \n",
+       "24188  2023-09-21 11:52:00<sep>2023-10-27 15:31:24<se...  mining_support   \n",
+       "\n",
+       "       index  \n",
+       "0          0  \n",
+       "1          1  \n",
+       "2          2  \n",
+       "3          3  \n",
+       "4          4  \n",
+       "...      ...  \n",
+       "24184  24184  \n",
+       "24185  24185  \n",
+       "24186  24186  \n",
+       "24187  24187  \n",
+       "24188  24188  \n",
+       "\n",
+       "[24189 rows x 6 columns]"
+      ]
+     },
+     "execution_count": 7,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "df"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 8,
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "Error processing thread:2967\n",
+      "Error processing thread:13251\n",
+      "Error processing thread:9306\n",
+      "Error processing thread:9152\n",
+      "Error processing thread:6543\n",
+      "Error processing thread:2907\n",
+      "Error processing thread:4609\n",
+      "Error processing thread:6620\n",
+      "Error processing thread:2344\n",
+      "Error processing thread:12206\n",
+      "Error processing thread:7170\n",
+      "Error processing thread:6956\n",
+      "Error processing thread:5493\n",
+      "Error processing thread:14915\n"
+     ]
+    }
+   ],
+   "source": [
+    "\n",
+    "\n",
+    "path = \"./\"\n",
+    "file_name = \"dataset.csv\" if not DEMO_MODE else \"demo_dataset.csv\"\n",
+    "\n",
+    "already_processed_thread_ids = []\n",
+    "\n",
+    "if not os.path.exists(path+file_name):\n",
+    "    dataset = pd.DataFrame(columns=['index','input','output'])    \n",
+    "else:\n",
+    "    dataset = pd.read_csv(path+file_name)\n",
+    "    already_processed_thread_ids = dataset['index'].tolist()\n",
+    "\n",
+    "# for each unique year, sample x threads\n",
+    "x = 230 if not DEMO_MODE else 1\n",
+    "df2 = df.sample(24000,random_state=44)\n",
+    "rows = pd.DataFrame()\n",
+    "unique_years = np.arange(2010, 2023+1)\n",
+    "year_counts = {year: 0 for year in unique_years}\n",
+    "for i in range(len(df2)):\n",
+    "    index, date, thread = process_thread(df2.iloc[i])\n",
+    "    if index is None:\n",
+    "        continue\n",
+    "    year = int(date[:4])\n",
+    "    if year_counts[year] < x:\n",
+    "        rows = pd.concat([rows, pd.DataFrame(df2.iloc[i]).T], ignore_index=True)\n",
+    "        year_counts[year] += 1"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 9,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/html": [
+       "<div>\n",
+       "<style scoped>\n",
+       "    .dataframe tbody tr th:only-of-type {\n",
+       "        vertical-align: middle;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe tbody tr th {\n",
+       "        vertical-align: top;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe thead th {\n",
+       "        text-align: right;\n",
+       "    }\n",
+       "</style>\n",
+       "<table border=\"1\" class=\"dataframe\">\n",
+       "  <thead>\n",
+       "    <tr style=\"text-align: right;\">\n",
+       "      <th></th>\n",
+       "      <th>topic</th>\n",
+       "      <th>post</th>\n",
+       "      <th>date</th>\n",
+       "      <th>dates</th>\n",
+       "      <th>category</th>\n",
+       "      <th>index</th>\n",
+       "    </tr>\n",
+       "  </thead>\n",
+       "  <tbody>\n",
+       "    <tr>\n",
+       "      <th>0</th>\n",
+       "      <td>Selling another batch of 40 ICARUS - sold out</td>\n",
+       "      <td>Those Icarus are batch 3, tested for several w...</td>\n",
+       "      <td>2012-06-15 10:53:37</td>\n",
+       "      <td>2012-06-15 03:19:09&lt;sep&gt;2012-06-15 10:53:12&lt;se...</td>\n",
+       "      <td>hardware</td>\n",
+       "      <td>4109</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>1</th>\n",
+       "      <td>Advice -Adding additional 6 pin PCIE outputs o...</td>\n",
+       "      <td>Hi AllI have a few modular/semi modular PC psu...</td>\n",
+       "      <td>2022-09-22 01:12:31</td>\n",
+       "      <td>2022-09-20 19:44:16&lt;sep&gt;2022-09-21 01:29:09&lt;se...</td>\n",
+       "      <td>hardware</td>\n",
+       "      <td>11208</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>2</th>\n",
+       "      <td>Please Help: Mining with both cores of 5970 wi...</td>\n",
+       "      <td>Hi, I'm having trouble setting up a 5970 and m...</td>\n",
+       "      <td>2013-07-04 15:42:38</td>\n",
+       "      <td>2013-03-27 13:50:47&lt;sep&gt;2013-03-27 20:16:41&lt;se...</td>\n",
+       "      <td>miners</td>\n",
+       "      <td>12483</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>3</th>\n",
+       "      <td>ASIC Not working!!! HELP</td>\n",
+       "      <td>An ASIC is an Application Specific Integrated ...</td>\n",
+       "      <td>2019-09-12 00:27:02</td>\n",
+       "      <td>2019-09-10 15:56:23&lt;sep&gt;2019-09-10 16:04:48&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>23073</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>4</th>\n",
+       "      <td>USB Block Erupter showing up as generic USB De...</td>\n",
+       "      <td>I've been mining with two USB Block Erupter Sa...</td>\n",
+       "      <td>2014-03-19 04:09:42</td>\n",
+       "      <td>2014-03-18 05:11:47&lt;sep&gt;2014-03-19 03:06:55&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>19054</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>5</th>\n",
+       "      <td>A little more proof the Cloudthink miner is fa...</td>\n",
+       "      <td>How is this site still a thing? Has there not ...</td>\n",
+       "      <td>2015-08-05 16:05:47</td>\n",
+       "      <td>2015-08-05 07:06:39&lt;sep&gt;2015-08-05 08:36:31&lt;se...</td>\n",
+       "      <td>hardware</td>\n",
+       "      <td>9265</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>6</th>\n",
+       "      <td>MOVED: [AJUDA] Montar Máquina de Mineração</td>\n",
+       "      <td>This topic has been moved to Trashcan.&lt;link&gt; i...</td>\n",
+       "      <td>2016-05-20 22:38:16</td>\n",
+       "      <td>2016-05-20 22:38:16</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>21036</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>7</th>\n",
+       "      <td>Monitoring of hash rate over short time periods</td>\n",
+       "      <td>HiI'm running cgminer with quite a few gpus. I...</td>\n",
+       "      <td>2011-12-15 11:38:16</td>\n",
+       "      <td>2011-12-15 10:36:13&lt;sep&gt;2011-12-15 10:51:52&lt;se...</td>\n",
+       "      <td>miners</td>\n",
+       "      <td>11702</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>8</th>\n",
+       "      <td>Ledger Nano Ether Wallet</td>\n",
+       "      <td>Hi, first time using Ledger nano s, with MEW w...</td>\n",
+       "      <td>2018-05-16 20:35:32</td>\n",
+       "      <td>2018-05-16 05:40:54&lt;sep&gt;2018-05-16 06:38:50&lt;se...</td>\n",
+       "      <td>hardware</td>\n",
+       "      <td>10730</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>9</th>\n",
+       "      <td>AntMiner R4 Stopped working</td>\n",
+       "      <td>my Antminer R4 (Antminer R4, Batch 5(7.5TH/s))...</td>\n",
+       "      <td>2017-11-25 08:10:50</td>\n",
+       "      <td>2017-11-25 00:57:57&lt;sep&gt;2017-11-25 01:37:10&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>21854</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>10</th>\n",
+       "      <td>BlackArrow Prospero X-3 [Help] (2020)</td>\n",
+       "      <td>Hi,I just bought myself the Black Arrow X3, fo...</td>\n",
+       "      <td>2020-04-25 11:10:31</td>\n",
+       "      <td>2020-04-24 15:34:03&lt;sep&gt;2020-04-24 16:34:22&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>23255</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>11</th>\n",
+       "      <td>Antminer S19 Control Board</td>\n",
+       "      <td>The Antminer S19 Control Board is a powerful a...</td>\n",
+       "      <td>2023-07-12 01:09:01</td>\n",
+       "      <td>2023-07-06 08:22:08&lt;sep&gt;2023-07-06 08:44:39&lt;se...</td>\n",
+       "      <td>hardware</td>\n",
+       "      <td>11328</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>12</th>\n",
+       "      <td>Innosilcon is trying to get rid of heavily use...</td>\n",
+       "      <td>Innosilicon is offering \"manufacturer refurbis...</td>\n",
+       "      <td>2021-09-23 17:20:56</td>\n",
+       "      <td>2021-08-29 12:41:40&lt;sep&gt;2021-08-29 21:47:04&lt;se...</td>\n",
+       "      <td>mining</td>\n",
+       "      <td>16133</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>13</th>\n",
+       "      <td>Buffer overflow</td>\n",
+       "      <td>This has happened to me every time a hash with...</td>\n",
+       "      <td>2010-11-29 17:21:55</td>\n",
+       "      <td>2010-11-29 13:48:54&lt;sep&gt;2010-11-29 17:21:55</td>\n",
+       "      <td>miners</td>\n",
+       "      <td>11378</td>\n",
+       "    </tr>\n",
+       "  </tbody>\n",
+       "</table>\n",
+       "</div>"
+      ],
+      "text/plain": [
+       "                                                topic  \\\n",
+       "0       Selling another batch of 40 ICARUS - sold out   \n",
+       "1   Advice -Adding additional 6 pin PCIE outputs o...   \n",
+       "2   Please Help: Mining with both cores of 5970 wi...   \n",
+       "3                            ASIC Not working!!! HELP   \n",
+       "4   USB Block Erupter showing up as generic USB De...   \n",
+       "5   A little more proof the Cloudthink miner is fa...   \n",
+       "6          MOVED: [AJUDA] Montar Máquina de Mineração   \n",
+       "7     Monitoring of hash rate over short time periods   \n",
+       "8                            Ledger Nano Ether Wallet   \n",
+       "9                         AntMiner R4 Stopped working   \n",
+       "10              BlackArrow Prospero X-3 [Help] (2020)   \n",
+       "11                         Antminer S19 Control Board   \n",
+       "12  Innosilcon is trying to get rid of heavily use...   \n",
+       "13                                    Buffer overflow   \n",
+       "\n",
+       "                                                 post                 date  \\\n",
+       "0   Those Icarus are batch 3, tested for several w...  2012-06-15 10:53:37   \n",
+       "1   Hi AllI have a few modular/semi modular PC psu...  2022-09-22 01:12:31   \n",
+       "2   Hi, I'm having trouble setting up a 5970 and m...  2013-07-04 15:42:38   \n",
+       "3   An ASIC is an Application Specific Integrated ...  2019-09-12 00:27:02   \n",
+       "4   I've been mining with two USB Block Erupter Sa...  2014-03-19 04:09:42   \n",
+       "5   How is this site still a thing? Has there not ...  2015-08-05 16:05:47   \n",
+       "6   This topic has been moved to Trashcan.<link> i...  2016-05-20 22:38:16   \n",
+       "7   HiI'm running cgminer with quite a few gpus. I...  2011-12-15 11:38:16   \n",
+       "8   Hi, first time using Ledger nano s, with MEW w...  2018-05-16 20:35:32   \n",
+       "9   my Antminer R4 (Antminer R4, Batch 5(7.5TH/s))...  2017-11-25 08:10:50   \n",
+       "10  Hi,I just bought myself the Black Arrow X3, fo...  2020-04-25 11:10:31   \n",
+       "11  The Antminer S19 Control Board is a powerful a...  2023-07-12 01:09:01   \n",
+       "12  Innosilicon is offering \"manufacturer refurbis...  2021-09-23 17:20:56   \n",
+       "13  This has happened to me every time a hash with...  2010-11-29 17:21:55   \n",
+       "\n",
+       "                                                dates        category  index  \n",
+       "0   2012-06-15 03:19:09<sep>2012-06-15 10:53:12<se...        hardware   4109  \n",
+       "1   2022-09-20 19:44:16<sep>2022-09-21 01:29:09<se...        hardware  11208  \n",
+       "2   2013-03-27 13:50:47<sep>2013-03-27 20:16:41<se...          miners  12483  \n",
+       "3   2019-09-10 15:56:23<sep>2019-09-10 16:04:48<se...  mining_support  23073  \n",
+       "4   2014-03-18 05:11:47<sep>2014-03-19 03:06:55<se...  mining_support  19054  \n",
+       "5   2015-08-05 07:06:39<sep>2015-08-05 08:36:31<se...        hardware   9265  \n",
+       "6                                 2016-05-20 22:38:16  mining_support  21036  \n",
+       "7   2011-12-15 10:36:13<sep>2011-12-15 10:51:52<se...          miners  11702  \n",
+       "8   2018-05-16 05:40:54<sep>2018-05-16 06:38:50<se...        hardware  10730  \n",
+       "9   2017-11-25 00:57:57<sep>2017-11-25 01:37:10<se...  mining_support  21854  \n",
+       "10  2020-04-24 15:34:03<sep>2020-04-24 16:34:22<se...  mining_support  23255  \n",
+       "11  2023-07-06 08:22:08<sep>2023-07-06 08:44:39<se...        hardware  11328  \n",
+       "12  2021-08-29 12:41:40<sep>2021-08-29 21:47:04<se...          mining  16133  \n",
+       "13        2010-11-29 13:48:54<sep>2010-11-29 17:21:55          miners  11378  "
+      ]
+     },
+     "execution_count": 9,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "rows"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 10,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "# pd.set_option('display.max_rows', None)\n",
+    "# rows.sort_values(by=\"date\", inplace=True)\n",
+    "# rows"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 11,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "prompt = \"\"\"User:\n",
+    "In the given Bitcoin forum thread, pay close attention to the language used when mentioning hardware pieces. Look for explicit statements indicating ownership or hypothetical discussions.\n",
+    "\n",
+    "{}\n",
+    "\n",
+    "\n",
+    "\n",
+    "Reply with a formatted JSON document containing an array of objects. Each object should represent a piece of hardware mentioned in the thread and include the following fields:\n",
+    "- hardware_name: A string containing the name of the hardware.\n",
+    "- hardware_is_owned: A boolean. If the mention suggests concrete ownership by any user, write true. If the hardware is discussed in a hypothetical or speculative way, write false. \n",
+    "\n",
+    "\n",
+    "Assistant:\n",
+    "Sure! Here is the requested JSON file, with the correct ownership status for each piece of hardware:\"\"\""
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 12,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "indices, dates, threads = [], [], []\n",
+    "for j in range(len(rows)):\n",
+    "    row = rows.iloc[j]\n",
+    "    if(len(row[\"post\"]) < 20):\n",
+    "        print(f\"skipping {j} as it is too short\")\n",
+    "        continue\n",
+    "\n",
+    "    id, date, thread = process_thread(row)\n",
+    "\n",
+    "    if id in already_processed_thread_ids:\n",
+    "        print(f\"Skipping thread {id} as it is already processed\")\n",
+    "        continue\n",
+    "\n",
+    "    indices.append(id)\n",
+    "    dates.append(date)\n",
+    "    threads.append(thread)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 13,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "14"
+      ]
+     },
+     "execution_count": 13,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "len(indices)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 14,
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "processing thread id 4109\n",
+      "\n",
+      "Date: 2012-06\n",
+      "Topic: Selling another batch of 40 ICARUS - sold out\n",
+      "### Original post:\n",
+      "Those Icarus are batch 3, tested for several weeks by me. mostly test with cgminer rig development, use OpenWrt router as host.I will take orders from tomorrow, Wednesday, May 23 5:00AM UTC+8 (don't send email before this time) ---- until all 40 are sold.Price: 480USD + shipping cost.Package content: Icarus, usb cable, power adapter or power wireAll package will send by EMS (<link> time we only accept BTC. after I receive order email I will send a new btc address to you. then after i receice the btc, I will ship your package immediately.Orders take by email <truncated> please add [ICARUS] to the subject. there is no confirm email. I will send you one email after I get the EMS track NO.(means packages already sent out, shipping from Beijing/China with EMS). please write those information in email:1. How many Icarus you want.2. You want power adapter or power wire. I advise you using your own ATX power if you order more then 2 Icarus.3. Address detail: name: company(optional): address: city: province: country: ZIP: TEL:More Icarus info please check:<link><link>\n",
+      "\n",
+      "### Reply 1:\n",
+      "wow!Now here is all sold out , anyone interested in ICArus boards should visit this topic:<link> still some ICA available there.\n",
+      "\n",
+      "### Reply 2:\n",
+      "Another 10 Icarus.\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"ICARUS\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"ICARUS boards\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"ICA\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"ICARUS\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"ICARUS boards\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"ICA\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 11208\n",
+      "\n",
+      "Date: 2022-09\n",
+      "Topic: Advice -Adding additional 6 pin PCIE outputs on a PC modular Power Supply?\n",
+      "### Original post:\n",
+      "Hi AllI have a few modular/semi modular PC psu's and was thinking of using the to pwer some S9 miners with 2 cards. Most of what i have are 1000w or higher.They will be worthless selling so might be better put to use on some S9s powered with2 cards, so i would need x7 ouputs all together.I think i could use an existing hard wired PCIE (6 pin or not) to power the control board.Then on the dedicated high amp PCIE modular ouputs could i not solder on connections and 'share' the load so x2 on each output?I have only seen x8 to x2 PCIE cables so could i not just splice in and solder another?If this works i could do a few more miers in thsi set up as it would be low power and quite when set to 700/800w.Anyone done this or got an opinion on it?The PSU's will either go to waste tbh.Pics attached.<link>\n",
+      "\n",
+      "### Reply 1:\n",
+      "@NotFuzzyWarmYes i will be running only 2 boards @ 700w or 800w.Is that why 'common rail' modular PSUs are so expensive?The only PSUs i can see that have enough outputs (X7) are the EVGA ones and they are silly money, i'm surprised that nobody has found a decent PSU and 'modded' them for more outputs tbh.....I just can't find makes that suffice apart from that brand?I think if i open it i can see rails and go from there, 3 on each for the hash boards and an existing 12v ouput for the control board.Thanks for the advice.\n",
+      "\n",
+      "### Reply 2:\n",
+      "Looks like the +12v are seperate rails and GND/-12v shared.I will just add an extra pin to each double 8pin >x2 6pin.So i will have a set of two 8pin >x3 6 pins.Current will be approx 800/12=66.67aIs this correct?<link>\n",
+      "\n",
+      "### Reply 3:\n",
+      "To be honest, modular plug PSU's all have 1 major problem: They are pushing the maximum current rating through the contacts and generally have only 18ga wires between the PSU and PCIe plugs.Ok, that's 2 major problems...That said, since you are talking about running at reduced power it may not be an issue, just periodically check to see how warm the PSU connectors get. Yes, I've had a few rather spectacularly fry over the years from when I used them to power s3's & s5's...Other thing to keep in mind is that particular PSU has 2 independent output rails. DO NOT connect power from the 2 different rails to 1 hash board! They will be shorted together and fight each other.\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"S9 miners\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"PC modular power supply\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"EVGA power supply\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"hash boards\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"PCIe plugs\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"S3 miners\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"S5 miners\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"S9 miners\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"PC modular power supply\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"EVGA power supply\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"hash boards\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"PCIe plugs\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"S3 miners\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"S5 miners\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 12483\n",
+      "\n",
+      "Date: 2013-07\n",
+      "Topic: Please Help: Mining with both cores of 5970 with cgminer?\n",
+      "### Original post:\n",
+      "Hi, I'm having trouble setting up a 5970 and mining with cgminer The rig is running Linux (Xubuntu) and the 5970 is the only card ( I've followed this guide which has always worked with my other setups.)When I run cgminer -n from the terminal emulator on the desktop I get the <truncated> -nCL Platform 0 vendor: Advanced Micro Devices, Inc. CL Platform 0 name: AMD Accelerated Parallel Processing CL Platform 0 version: OpenCL 1.1 AMD-APP-SDK-v2.5 (793.1) Platform 0 devices: 1 0 Cypress ADL found more devices than opencl! There is possibly at least one GPU that doesn't support OpenCL Use the gpu map feature to reliably map OpenCL to ADL WARNING: Number of OpenCL and ADL devices did not match! Hardware monitoring may NOT match up with devices! GPU 0 ATI Radeon HD 5900 Series hardware monitoring enabled 1 GPU devices max detected Seems to me, cgminer is not recognizing both cores of the 5970.(When I mine with cgminer from the terminal emulator on the Desktop, it's mining with only one core of the 5970)Interestingly, when I run the same command from a SSH terminal it gives me:Code:./cgminer -nCL Platform 0 vendor: Advanced Micro Devices, Inc. CL Platform 0 name: AMD Accelerated Parallel <rest of post truncated>\n",
+      "\n",
+      "### Reply 1:\n",
+      "Do you have the newest drivers?\n",
+      "\n",
+      "### Reply 2:\n",
+      "Usual instructions for when people DONT read the readme.Reconfigure xorg for all devices, start x and export the DISPLAY variable before starting cgminer.\n",
+      "\n",
+      "### Reply 3:\n",
+      "I just find it so weird how people dont read something that specifically says \"READ ME!\"\n",
+      "\n",
+      "### Reply 4:\n",
+      "Ahh, thanks guys I actually was exporting the DISPLAY variable in my mining startup script but I'd stupidly disabled this while installing/testing the card. That seems to have solved that problem! Unfortunately this led me on to a new issue: The Xubuntu computer loses power very quickly when I start mining on the 5970 with anything above intensity 1, but it mines fine (intensity 11) when installed in a different windows machine...When the linux comp powers off, it's without warning I have to wait a little and toggle the PSU switch before turning it on again. Both PC's have adequate PSU's (760W) and the 5790 is the only card being used. So it has me puzzled. Why would mining cause the linux machine to quickly shut off? Temps on the fan never get a chance to hit 80 before the power cuts off.I will start a new thread on this if it comes to me getting completely stuck (I can try a 7870 in the linux computer and see if it has the same problem), but I hoped someone may have a good idea why this is happening? ATI drivers are 11.11Thank you very much for ideas on this one and happy hashing!\n",
+      "\n",
+      "### Reply 5:\n",
+      "Last problem now appears fixed after replacing PSU. Thanks again for the help!\n",
+      "\n",
+      "### Reply 6:\n",
+      "Hi ckolivas,I read the readme, but I may be to \"slow\" to understand. I would definitely appreciate your help.I'm getting the same error. I triedsudo aticonfig --adapter=0,1 --initialI also have the following lines in my shell file to start cgminerexport DISPLAY=:0export <truncated> <truncated> I'm missing?\n",
+      "\n",
+      "### Reply 7:\n",
+      "I realize I'm having issues with X server to start. So guess I need to fix that somehow.\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"5970\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"ATI Radeon HD 5900 Series\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"5790\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"7870\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"760W PSU\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"PSU\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"5970\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"ATI Radeon HD 5900 Series\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"5790\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"7870\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"760W PSU\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"PSU\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 23073\n",
+      "\n",
+      "Date: 2019-09\n",
+      "Topic: ASIC Not working!!! HELP\n",
+      "### Original post:\n",
+      "An ASIC is an Application Specific Integrated Circuit, eg the chips used in a miner. I take it your MINER is not working and we are supposed to just check our crystal ball or guess what kind of miner it is? Try giving some useful information about it such <truncated> new or used?\n",
+      "\n",
+      "### Reply 1:\n",
+      "a 17 second video is worthless.how about a guihow about api logshow about make and model?looks like an innosiliconlooks like it needs 2 psu'sis it this miner a6 or a6+\n",
+      "\n",
+      "### Reply 2:\n",
+      "hey guys I bought AladdinMiner T1 and a psu but now the psu is not working, so I bought new \"bitmain APW3++\" and it was working fine the next day I increase the performance of the asic and it switched off now I can't turn it on!!!here is the video:<link> lights are not working.no ip address.fans starts and strops working.HELP\n",
+      "\n",
+      "### Reply 3:\n",
+      "He clearly edited the post after you guys have commented, anyhow , this is the miner he is talking about I guess.<link> it does look like an Inno gear with a bit of modification, in that link they clearly saywhich means phill is right, you need at least two PSUs, each must be 1400w minimum , and according to the video, it does look like he got 2 PSUs connected, the miner's fan do spin for a while and then stop , and you saidWhich means you tried to overclock the miner, you either burned the miner or one of the PSUs, does it show on the network ?? can you access the user interface? please post more details.\n",
+      "\n",
+      "### Reply 4:\n",
+      "Do note that the OP has not made any mention of trying to contact the distributor or manufacturer of this knock-off miner. That of course should be the very first thing the OP should have done...Nor have they posted anything else re what has been said so far.\n",
+      "\n",
+      "### Reply 5:\n",
+      "He needs to know it's a knock-off in the first place, and honestly if the gear does 32th at 2800w as promised-- it does not matter what name they put on it, as for contacting the manufacturer, honestly this is usually the last thing I personally do simply because1-The support at these Chinese websites is terrible, had a ton of issues with my gears, most were solved by trial and error or from information I got online (mostly on this very forum) , while the manufacturer will give only give you the abc of trouble shooting only.2-In many places, the shipping cost for returning the miner back to china is unreasonable, to the extent that some people rather order new hash board/control board or a PSU than having to pay that much for shipping or wait for months to get their replacement.I think if OP provides enough information and kernel log, someone will be able to give him the solution for this problem without the need for a crystal ball.\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"AladdinMiner T1\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"bitmain APW3++\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"Innosilicon\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"PSU\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"knock-off miner\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"AladdinMiner T1\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"bitmain APW3++\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"Innosilicon\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"PSU\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"knock-off miner\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 19054\n",
+      "\n",
+      "Date: 2014-03\n",
+      "Topic: USB Block Erupter showing up as generic USB Device instead of \"Port\", won't mine\n",
+      "### Original post:\n",
+      "I've been mining with two USB Block Erupter Sapphires without issue for at least a week now, properly cooled. Today, I've been messing around with things trying to get my Antminer U2 up and running and must've done something that now causes one of my erupters to show up under Device Manager as a usb device instead of under \"Ports\". When I try to mine with it, it just sits in standby doing nothing. However, if I plug it into my Win 7 machine it comes up normally under \"Ports\" instead of \"Universal Serial Bus Devices\" but I don't have an ethernet to that box to test if it will mine. I'm not sure what exactly is going on with this stick. Is it fried?\n",
+      "\n",
+      "### Reply 1:\n",
+      "Maybe you installed a WinUSB driver?\n",
+      "\n",
+      "### Reply 2:\n",
+      "Is the problem on a windows xp machine? This may be a device identifier issue. I've never seen it with 3 devices, but I suppose it is possible. There is a fix posted in these forums somewhere and if I have time to dig it up for you I will, but if you keep restarting and plugging it back in to different ports it may eventually pick up properly. Windows XP doesn't handle duplicate usb devices very well.\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"USB Block Erupter Sapphire\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"Antminer U2\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"USB Block Erupter Sapphire\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"Antminer U2\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 9265\n",
+      "\n",
+      "Date: 2015-08\n",
+      "Topic: A little more proof the Cloudthink miner is fake... Shilled reddit accounts\n",
+      "### Original post:\n",
+      "How is this site still a thing? Has there not already been extensive proof uncovered that Cloudthink is a scam? I haven't talked to anyone within the Bitcoin community that has regarded as anything other than a scam.\n",
+      "\n",
+      "### Reply 1:\n",
+      "Has anyone from Manchester walked to their supposed office? It wouldn't take much effort to provide verifiable evidence that this is a scam.\n",
+      "\n",
+      "### Reply 2:\n",
+      "All I want to add is shame on any of the upstanding members that took on their Sig campaign and contributed to anyone getting taken advantage of. Betrayed by greed once again. I feel bad for anyone inexperienced that fell for this scam, it may have been obvious to most of us, but it was slightly less poorly planned out than many others.\n",
+      "\n",
+      "### Reply 3:\n",
+      "Yes<link>\n",
+      "\n",
+      "### Reply 4:\n",
+      "What about the dollar a day whores who signed up for the \"free\" packages and incessantly bumped this thread?<link> was plenty to be suspicious about when they signed up in the middle of June.\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "{\n",
+      "  \"hardware_mentions\": []\n",
+      "}\n",
+      "``` \n",
+      "\n",
+      "In the provided forum thread, there are no explicit mentions of any specific hardware pieces, nor are there any statements indicating ownership or hypothetical discussions about hardware. The conversation primarily revolves around the Cloudthink miner and its legitimacy, without referencing any particular hardware.\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "{\n",
+      "  \"hardware_mentions\": []\n",
+      "}\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 21036\n",
+      "\n",
+      "Date: 2016-05\n",
+      "Topic: MOVED: [AJUDA] Montar Máquina de Mineração\n",
+      "### Original post:\n",
+      "This topic has been moved to Trashcan.<link> in English.\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "[\n",
+      "    {\n",
+      "        \"hardware_name\": \"Antminer S9\",\n",
+      "        \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "        \"hardware_name\": \"AvalonMiner 741\",\n",
+      "        \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "        \"hardware_name\": \"Bitmain Antminer L3+\",\n",
+      "        \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "        \"hardware_name\": \"Innosilicon T2T\",\n",
+      "        \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "        \"hardware_name\": \"Dragonmint T1\",\n",
+      "        \"hardware_is_owned\": false\n",
+      "    }\n",
+      "]\n",
+      "``` \n",
+      "\n",
+      "Note: The hardware names and ownership statuses are hypothetical, as the original post does not provide specific mentions of hardware ownership.\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "[\n",
+      "    {\n",
+      "        \"hardware_name\": \"Antminer S9\",\n",
+      "        \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "        \"hardware_name\": \"AvalonMiner 741\",\n",
+      "        \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "        \"hardware_name\": \"Bitmain Antminer L3+\",\n",
+      "        \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "        \"hardware_name\": \"Innosilicon T2T\",\n",
+      "        \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "        \"hardware_name\": \"Dragonmint T1\",\n",
+      "        \"hardware_is_owned\": false\n",
+      "    }\n",
+      "]\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 11702\n",
+      "\n",
+      "Date: 2011-12\n",
+      "Topic: Monitoring of hash rate over short time periods\n",
+      "### Original post:\n",
+      "HiI'm running cgminer with quite a few gpus. I want to tweak and monitor performance of each gpu at a time so I can fine tune them. Cgminer just offers average has hashrate for all. (6 gpus per client)Can I do this or is there another way I shud go about it? The average per gpu jumps around too much for my liking.Thank you.\n",
+      "\n",
+      "### Reply 1:\n",
+      "You sure? Highlighted numbers are average per card AFAIK:\n",
+      "\n",
+      "### Reply 2:\n",
+      "Yes but mine is constantly jumping around with very large variability . Is yours more stable? Upon further research I see a post where someone has mentioned switching to overclock makes the average more stable (6990) - ill test that out tho I wud prefer to keep it at 375W so I can predict electricity usage. In the meantime the average rate per gpu jumps around so much its ikpossible to gauge whether ur getting a small increase in hashing power.\n",
+      "\n",
+      "### Reply 3:\n",
+      "The left figure (458.0) fluctuates a bit, I think its a 5s average; the right one that I highlighted (456.6), doesnt change at all (after running for a while). I think that is the average since starting the app?\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"gpu\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"6990\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"gpu\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"6990\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 10730\n",
+      "\n",
+      "Date: 2018-05\n",
+      "Topic: Ledger Nano Ether Wallet\n",
+      "### Original post:\n",
+      "Hi, first time using Ledger nano s, with MEW wallet, i log in, it shows 5 different MEW address, are those all mine? who created those account, and how come I don't see private key when I log in those accounts? Also, I don't need any password like a normal wallet? little confused here how it works, can anyone explain? thanks\n",
+      "\n",
+      "### Reply 1:\n",
+      "Consider Myetherwallet as an interface to interact with your Ledger nano S. You will still need to enter the PIN to unlock your Ledger or confirm the transactions from the device. The addresses are yours, pre-generated from your seed.\n",
+      "\n",
+      "### Reply 2:\n",
+      "Ledger has its own HowTo for MyEtherWallet, have a look: <link> are also a ton of guides, blog articles and videos available: <link>\n",
+      "\n",
+      "### Reply 3:\n",
+      "These wallets have already been built in you ledger nano s. When I'm bought trezor I got 5 eth addresses for my device. You can check your own cabinet on ledger where you can configure all functions\n",
+      "\n",
+      "### Reply 4:\n",
+      "Thank you, but how come I am not able to see the private key for those pre-built 5 accounts? does it mean, I don't need private keys for those accounts?\n",
+      "\n",
+      "### Reply 5:\n",
+      "Hello imteaz, look here:<link> hope the information will help you. All the best\n",
+      "\n",
+      "### Reply 6:\n",
+      "The private-key is inside your Ledger. Putting in a simple way, MEW uses your public key (address) to see your balance and build the transaction, which its sent to the Ledger device, signed with the private-key and sent back to the computer, where its broadcasted. The private-key never leaves the device (reason why you can't see them, and why hardware wallets are so secure compared to normal desktop wallets).\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "{\n",
+      "  \"hardware_devices\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"Ledger Nano S\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"Trezor\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "{\n",
+      "  \"hardware_devices\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"Ledger Nano S\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"Trezor\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 21854\n",
+      "\n",
+      "Date: 2017-11\n",
+      "Topic: AntMiner R4 Stopped working\n",
+      "### Original post:\n",
+      "my Antminer R4 (Antminer R4, Batch 5(7.5TH/s)) suddenly stopped working after reboot. i tried various options like reset using different methods but i cant get it to workeven the web based admin console was not reachable however afrer several reboots and holding the IP button i was able to connect to web based control panel...however strange problem is that i cant see the miner config screen though i can see other screensi updated firmware using web based console n got success message but still same problem persists...pfa screenshots and kindly advise ...<link>\n",
+      "\n",
+      "### Reply 1:\n",
+      "too late you did firmware upgradei can't help you sorry.if you are usa based maybe bitmain warranty can help<link> r4 breaks alot and you muscled a firmware update on a broken r4.your best shot is bitmainwarranty good luck\n",
+      "\n",
+      "### Reply 2:\n",
+      "is there a way to connect using ssh....\n",
+      "\n",
+      "### Reply 3:\n",
+      "Too late .The r4 is very delicate,They break and break and break.Someone had a link that show how to reset to the original firmware.someone gave it to me it may work if you reset it.I will look for a link to the reset.In I reset it and it still did not work.I sent it in to bitmainwarranty and they did fix it.\n",
+      "\n",
+      "### Reply 4:\n",
+      "You can ssh into it with username root and password admin.I doubt the firmware is causing this, at least, if it was installed correctly. I had an R4 controller fail and I replaced it with an S9 controller, flashing it with the R4 firmware and it works fine. If the image was installed properly, and your controller isn't broken, it should be working. Make sure you don't have anything preventing javascript from running on that page.The \"ant_data=;\" you see in the miner configuration page is there because the header has an inline script that begins with Code:echo \"ant_data = ${ant_result};\" The script is fetching cgi data from the config saved in <truncated> For some reason it is failing at that point.\n",
+      "\n",
+      "### Reply 5:\n",
+      "thanks all for your suggestions ..\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"Antminer R4\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"S9 controller\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"Antminer R4\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"S9 controller\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 23255\n",
+      "\n",
+      "Date: 2020-04\n",
+      "Topic: BlackArrow Prospero X-3 [Help] (2020)\n",
+      "### Original post:\n",
+      "Hi,I just bought myself the Black Arrow X3, for my personal collection of asics. But, I cannot connect to operate the machine. I saw that for the login it is: user = user, passworld = blackarrow but it shows me an error message that something is not valid. I contacted the seller and he said he knew nothing. Is it possible to reset the machine?\n",
+      "\n",
+      "### Reply 1:\n",
+      "He might have sold you an unit which is affected by firmware virus. If he claims that he does not know what is wrong, that is probably because he was in same boat as you. Or he might have changed the password and forgot.But for your sake, try resetting your machine via reset button or recovery SD card.Also, isn't that unit like 5 years old? Why did you even buy it?\n",
+      "\n",
+      "### Reply 2:\n",
+      "I make a collection of asic and I test it to find out how it works.\n",
+      "\n",
+      "### Reply 3:\n",
+      "Check this post before firing them up, they have a history of burning down.<link>\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"Black Arrow X3\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"Black Arrow X3\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 11328\n",
+      "\n",
+      "Date: 2023-07\n",
+      "Topic: Antminer S19 Control Board\n",
+      "### Original post:\n",
+      "The Antminer S19 Control Board is a powerful and essential component of the Antminer S19 mining rig. Designed to optimize performance and efficiency, this control board plays a crucial role in ensuring the smooth operation of your mining equipment.The Antminer S19 Control Board is engineered to deliver exceptional performance, allowing you to maximize the hashing power of your mining rig. With its advanced chipset and optimized firmware, this control board ensures efficient communication between the different components of your Antminer S19, resulting in higher mining productivity and increased profitability.The Antminer S19 Control Board features a user-friendly interface that simplifies the management and monitoring of your mining rig. With its intuitive design and easy-to-navigate settings, you can efficiently control various parameters such as fan speed, voltage, and temperature. To Know More:<link>\n",
+      "\n",
+      "### Reply 1:\n",
+      "I think we all know what a Control Board is.However, what we don't know is why you're writing this, in a way worthy of an AI, and on top of that putting the link of a Whatsminer PSU which is completely off-topic.\n",
+      "\n",
+      "### Reply 2:\n",
+      "I recently purchased Antminer S19 pro 110Th from 570OLLC. Here's the link if you guys are interested: <link>\n",
+      "\n",
+      "### Reply 3:\n",
+      "Are you sure you purchased the s19 unit from that link?When exactly?Or are you just trying to promote it here just like on other forums with some other newbie alt accounts and trying to promote it with fake/sweet words?I'm talking about this forum as you can see all responses came from newbies so it's very risky to buy on this site.\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"Antminer S19 Control Board\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"Antminer S19 pro 110Th\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"Whatsminer PSU\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"Antminer S19 Control Board\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"Antminer S19 pro 110Th\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"Whatsminer PSU\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 16133\n",
+      "\n",
+      "Date: 2021-09\n",
+      "Topic: Innosilcon is trying to get rid of heavily used miners\n",
+      "### Original post:\n",
+      "Innosilicon is offering \"manufacturer refurbished\" T3+ and other miners. I ordered a T3+ 57T Bitcoin miner. I had to wait for 4 weeks after I paid in full in Bitcoin until they shipped it out. When it arrived it was in horrible condition: <link> of dust, with scratches, stains, missing screws, rattling parts, rust...The firmware was locked and I was not able to enter my own pool settings. There was plenty of evidence that this miner was not manufacturer refurbished, not even cleaned. Otherwise at least the firmware would have been reset. Innosilicon has 3 departments: while the support is trying to help to unlock the miner, the sales and order team tells me: \"This is what you get when you order from us. Deal with it!\"\n",
+      "\n",
+      "### Reply 1:\n",
+      "I think other ppl here ordered the refurb T3s. Would be great to have their feedbacks!\n",
+      "\n",
+      "### Reply 2:\n",
+      "Yes, please. Who else bought a refurb T3+ ? What was your experience?\n",
+      "\n",
+      "### Reply 3:\n",
+      "have you ever got to the bottom of the pool settings being pre-completed and not updating ?also, sorry to hear about your experience, I hope it all goes well in the end\n",
+      "\n",
+      "### Reply 4:\n",
+      "Yeah, they use the term refurbished for a miner that was damaged and repaired by them or something returned and they've set it back running. They did warn a bit but you didn't take the warning seriously, usually in those cases light scratches mean run over by an excavator:Sucks and if I were in your place, even if support manages to help you unblock the settings I would play possum and try to get a refund and send it back. I won't be surprised if that thing wouldn't break in a few months, external scratched and missing screws ain't a big deal but you should take a look inside if possible and have a beer nearby when you do\n",
+      "\n",
+      "### Reply 5:\n",
+      "Refurbished miners could be a great bargain if you get a diamond in the rough with no issues but that is playing a dangerous game if there is no warranty attached to them. Depending on the price and time to get to you it may pay itself off quickly but if it breaks it could quickly become a paperweight or something that ends u costing what a new unit would plus the downtime to ship it back for repairs. Would love to hear feedback as well from anyone who bought one.\n",
+      "\n",
+      "### Reply 6:\n",
+      "Those Innosilicon refurbished miners are 6 months garanty\n",
+      "\n",
+      "### Reply 7:\n",
+      "You are right with the firmware lock, but this is a straight-out scam if you ask me, these were supposed to be \"manufacturer refurbished\", the ones in the video don't look anything like it, in fact, REAL refurbished miners are a lot more expensive than clean used miners, a while back used S9js were going for $250 while the refurbished once were going for at least $400, but those looked as good as new, no scratches, no lost screws, everything seemed like brand new, the miner in the video is a Used Miner with C- condition, selling it as a refurbished piece is nothing but scam IMO.\n",
+      "\n",
+      "### Reply 8:\n",
+      "Looks like this is a rare problem that has happened before.There are threads about a T2 miner that had it on here.. also one on the russian mining board:<link> might need to do a translate on it with your browser)Post 11 reads:Maybe worth reaching out. Seems they found someone at Inno that can unlock it remotely for you.\n",
+      "\n",
+      "### Reply 9:\n",
+      "Watching some videos from your YouTube channel and I like the soundproofing you have setup. I'd probably be mining with more hashrate at my home if I had such a setup as well. I should also mention that I thought for a second this was a bodybuilding YouTube channel instead of being about Bitcoin mining. From the look of your biceps I thought you might go hulk and crush that thing when it wasn't working.\n",
+      "\n",
+      "### Reply 10:\n",
+      "Interesting , they do that constantley , I heard that their ceo is a close friend to the founder of ETH\n",
+      "\n",
+      "### Reply 11:\n",
+      "Figured they would carry some sort of limited warranty. That said, considering Inno was made aware of the Fixed Address issue on at least some miners and quickly responded by putting out a fix for it one can't fault them for their response on that part. They also said they were going to issue a mass email to all customers who bought one of the refurbed miners to notify of them of the possible problem and fix for it if they received a miner that was locked. Hopefully the OP just got a miner that had already been shipped just before Inno became aware of the problem and the miner had yet yet been updated to OEM firmwareMy take on things is that the miners are of course from some of the farms in China that got shut down. It makes sense that a farm would use locked firmware to make sure there is (near) zero chance of miners being hijacked either through hacking or actual theft. If stolen, as soon as the miner goes on line Inno will know which miner and what the ip address is.Biggest problem is Inno dropping the ball on making sure the miners are at least cleaned up and along with that definitely reset back<rest of thread truncated>\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"T3+ 57T Bitcoin miner\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"T3+\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"S9j\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"T2 miner\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "{\n",
+      "  \"hardware\": [\n",
+      "    {\n",
+      "      \"hardware_name\": \"T3+ 57T Bitcoin miner\",\n",
+      "      \"hardware_is_owned\": true\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"T3+\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"S9j\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    },\n",
+      "    {\n",
+      "      \"hardware_name\": \"T2 miner\",\n",
+      "      \"hardware_is_owned\": false\n",
+      "    }\n",
+      "  ]\n",
+      "}\n",
+      "\n",
+      "\n",
+      "\n",
+      "processing thread id 11378\n",
+      "\n",
+      "Date: 2010-11\n",
+      "Topic: Buffer overflow\n",
+      "### Original post:\n",
+      "This has happened to me every time a hash with zeros is found on my 64-bit Atom system:Code:DBG: found zeroes in <truncated> 8150287 hashes, 123.22 khash/secPROOF OF WORK FOUND? submitting... *** buffer overflow detected ***: ./minerd terminated======= Backtrace: <truncated> mentioned the problems with -march=atom CFLAGS previously, but this does not go away when changing the -march.\n",
+      "\n",
+      "### Reply 1:\n",
+      "Fixed in git commit <truncated> just pushed to cpuminer.git.\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "model response: \n",
+      "\n",
+      "```json\n",
+      "[\n",
+      "    {\n",
+      "        \"hardware_name\": \"64-bit Atom system\",\n",
+      "        \"hardware_is_owned\": true\n",
+      "    }\n",
+      "]\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "parsed response: \n",
+      "\n",
+      "[\n",
+      "    {\n",
+      "        \"hardware_name\": \"64-bit Atom system\",\n",
+      "        \"hardware_is_owned\": true\n",
+      "    }\n",
+      "]\n",
+      "\n",
+      "\n",
+      "\n"
+     ]
+    }
+   ],
+   "source": [
+    "\n",
+    "\n",
+    "\n",
+    "\n",
+    "# for (date, thread) in tqdm(zip(dates, threads), total=len(dates)):\n",
+    "for (threadid, date, thread) in zip(indices, dates, threads):\n",
+    "\n",
+    "    \n",
+    "    print(f\"processing thread id {threadid}\\n\\n\"+ thread + \"\\n\\n\")\n",
+    "\n",
+    "    prompt2 = prompt.format(thread)\n",
+    "    \n",
+    "\n",
+    "    response = get_openai_response(prompt2)\n",
+    "\n",
+    "    print(\"model response: \\n\\n\"+response+\"\\n\\n\\n\")\n",
+    "\n",
+    "    if not response.__contains__(\"```json\"):\n",
+    "        print(\"ERROR: response does not contain JSON\")\n",
+    "        continue\n",
+    "\n",
+    "    response = response.replace(\"```json\\n\",\"\")\n",
+    "    response = response.split(\"```\")[0].strip()\n",
+    "\n",
+    "    print(\"parsed response: \\n\\n\"+response+\"\\n\\n\\n\")\n",
+    "\n",
+    "    try:\n",
+    "        _ = json.loads(response)\n",
+    "    except:\n",
+    "        print(\"ERROR: could not parse response as JSON\")\n",
+    "        continue\n",
+    "\n",
+    "\n",
+    "\n",
+    "\n",
+    "    # Append the new rows to the dataset\n",
+    "    input = thread\n",
+    "    output = response\n",
+    "    dataset = pd.concat([dataset, pd.DataFrame({'index': [threadid],'input': [input], 'output': [output]})], ignore_index=True)\n",
+    "\n",
+    "\n",
+    "\n",
+    "    dataset.to_csv(path+file_name, index=False)\n",
+    "    threadid+=1\n",
+    "\n",
+    "    # break"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 15,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/html": [
+       "<div>\n",
+       "<style scoped>\n",
+       "    .dataframe tbody tr th:only-of-type {\n",
+       "        vertical-align: middle;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe tbody tr th {\n",
+       "        vertical-align: top;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe thead th {\n",
+       "        text-align: right;\n",
+       "    }\n",
+       "</style>\n",
+       "<table border=\"1\" class=\"dataframe\">\n",
+       "  <thead>\n",
+       "    <tr style=\"text-align: right;\">\n",
+       "      <th></th>\n",
+       "      <th>topic</th>\n",
+       "      <th>post</th>\n",
+       "      <th>date</th>\n",
+       "      <th>dates</th>\n",
+       "      <th>category</th>\n",
+       "      <th>index</th>\n",
+       "    </tr>\n",
+       "  </thead>\n",
+       "  <tbody>\n",
+       "    <tr>\n",
+       "      <th>0</th>\n",
+       "      <td>[Group Buy in China]  Avalon batch #3</td>\n",
+       "      <td>List of &lt;truncated&gt; Forum Name - Bitcoin Addre...</td>\n",
+       "      <td>2013-03-25 11:06:33</td>\n",
+       "      <td>2013-03-25 10:16:23&lt;sep&gt;2013-03-25 10:42:45&lt;se...</td>\n",
+       "      <td>groupbuys</td>\n",
+       "      <td>0</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>1</th>\n",
+       "      <td>Avalon Group buy - Germany</td>\n",
+       "      <td>Hi, I'm in time to invest?&lt;sep&gt;too late, sorry</td>\n",
+       "      <td>2013-03-25 13:13:44</td>\n",
+       "      <td>2013-03-25 12:47:34&lt;sep&gt;2013-03-25 13:13:44</td>\n",
+       "      <td>groupbuys</td>\n",
+       "      <td>1</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>2</th>\n",
+       "      <td>Avalon Group buy - Germany - closed</td>\n",
+       "      <td>I am willing to organize a community purchase ...</td>\n",
+       "      <td>2013-03-25 13:14:29</td>\n",
+       "      <td>2013-03-25 13:14:29</td>\n",
+       "      <td>groupbuys</td>\n",
+       "      <td>2</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>3</th>\n",
+       "      <td>I'm about to buy Avalon asic 85</td>\n",
+       "      <td>it sold out, its gone.&lt;sep&gt;People just order b...</td>\n",
+       "      <td>2013-03-25 14:26:29</td>\n",
+       "      <td>2013-03-25 13:46:12&lt;sep&gt;2013-03-25 14:26:29</td>\n",
+       "      <td>groupbuys</td>\n",
+       "      <td>3</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>4</th>\n",
+       "      <td>CANCELLED [Group Buy in China]  Avalon batch #3</td>\n",
+       "      <td>Do you not have enough BTC to buy a batch 3 Av...</td>\n",
+       "      <td>2013-03-25 16:42:09</td>\n",
+       "      <td>2013-03-25 16:42:09</td>\n",
+       "      <td>groupbuys</td>\n",
+       "      <td>4</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>...</th>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24184</th>\n",
+       "      <td>S19 Amlogic control board brick ?</td>\n",
+       "      <td>Hello everyone, I have an amlogic s19 j pro ca...</td>\n",
+       "      <td>2023-10-23 15:51:19</td>\n",
+       "      <td>2023-08-30 13:53:04&lt;sep&gt;2023-08-30 17:45:01&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>24184</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24185</th>\n",
+       "      <td>S19jPro abnormal network - (Will not connect t...</td>\n",
+       "      <td>Driving me nuts... after changing pool address...</td>\n",
+       "      <td>2023-10-24 14:00:23</td>\n",
+       "      <td>2023-02-24 15:37:21&lt;sep&gt;2023-02-24 15:59:12&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>24185</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24186</th>\n",
+       "      <td>Flashing control Board S9 to R4</td>\n",
+       "      <td>Hello,I recently purchased a control board tha...</td>\n",
+       "      <td>2023-10-25 23:42:40</td>\n",
+       "      <td>2023-10-05 14:14:14&lt;sep&gt;2023-10-09 05:06:58&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>24186</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24187</th>\n",
+       "      <td>AvalonMiner 1166Pro-72</td>\n",
+       "      <td>Hello,can someone help me find the problem wit...</td>\n",
+       "      <td>2023-10-26 08:40:14</td>\n",
+       "      <td>2023-10-09 07:54:00&lt;sep&gt;2023-10-09 11:50:47&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>24187</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24188</th>\n",
+       "      <td>need advice to reduce noise and monitor asic m...</td>\n",
+       "      <td>I think Awesomeminer supports this unit model ...</td>\n",
+       "      <td>2023-10-27 16:39:20</td>\n",
+       "      <td>2023-09-21 11:52:00&lt;sep&gt;2023-10-27 15:31:24&lt;se...</td>\n",
+       "      <td>mining_support</td>\n",
+       "      <td>24188</td>\n",
+       "    </tr>\n",
+       "  </tbody>\n",
+       "</table>\n",
+       "<p>24189 rows × 6 columns</p>\n",
+       "</div>"
+      ],
+      "text/plain": [
+       "                                                   topic  \\\n",
+       "0                  [Group Buy in China]  Avalon batch #3   \n",
+       "1                             Avalon Group buy - Germany   \n",
+       "2                    Avalon Group buy - Germany - closed   \n",
+       "3                        I'm about to buy Avalon asic 85   \n",
+       "4        CANCELLED [Group Buy in China]  Avalon batch #3   \n",
+       "...                                                  ...   \n",
+       "24184                  S19 Amlogic control board brick ?   \n",
+       "24185  S19jPro abnormal network - (Will not connect t...   \n",
+       "24186                    Flashing control Board S9 to R4   \n",
+       "24187                             AvalonMiner 1166Pro-72   \n",
+       "24188  need advice to reduce noise and monitor asic m...   \n",
+       "\n",
+       "                                                    post                 date  \\\n",
+       "0      List of <truncated> Forum Name - Bitcoin Addre...  2013-03-25 11:06:33   \n",
+       "1         Hi, I'm in time to invest?<sep>too late, sorry  2013-03-25 13:13:44   \n",
+       "2      I am willing to organize a community purchase ...  2013-03-25 13:14:29   \n",
+       "3      it sold out, its gone.<sep>People just order b...  2013-03-25 14:26:29   \n",
+       "4      Do you not have enough BTC to buy a batch 3 Av...  2013-03-25 16:42:09   \n",
+       "...                                                  ...                  ...   \n",
+       "24184  Hello everyone, I have an amlogic s19 j pro ca...  2023-10-23 15:51:19   \n",
+       "24185  Driving me nuts... after changing pool address...  2023-10-24 14:00:23   \n",
+       "24186  Hello,I recently purchased a control board tha...  2023-10-25 23:42:40   \n",
+       "24187  Hello,can someone help me find the problem wit...  2023-10-26 08:40:14   \n",
+       "24188  I think Awesomeminer supports this unit model ...  2023-10-27 16:39:20   \n",
+       "\n",
+       "                                                   dates        category  \\\n",
+       "0      2013-03-25 10:16:23<sep>2013-03-25 10:42:45<se...       groupbuys   \n",
+       "1            2013-03-25 12:47:34<sep>2013-03-25 13:13:44       groupbuys   \n",
+       "2                                    2013-03-25 13:14:29       groupbuys   \n",
+       "3            2013-03-25 13:46:12<sep>2013-03-25 14:26:29       groupbuys   \n",
+       "4                                    2013-03-25 16:42:09       groupbuys   \n",
+       "...                                                  ...             ...   \n",
+       "24184  2023-08-30 13:53:04<sep>2023-08-30 17:45:01<se...  mining_support   \n",
+       "24185  2023-02-24 15:37:21<sep>2023-02-24 15:59:12<se...  mining_support   \n",
+       "24186  2023-10-05 14:14:14<sep>2023-10-09 05:06:58<se...  mining_support   \n",
+       "24187  2023-10-09 07:54:00<sep>2023-10-09 11:50:47<se...  mining_support   \n",
+       "24188  2023-09-21 11:52:00<sep>2023-10-27 15:31:24<se...  mining_support   \n",
+       "\n",
+       "       index  \n",
+       "0          0  \n",
+       "1          1  \n",
+       "2          2  \n",
+       "3          3  \n",
+       "4          4  \n",
+       "...      ...  \n",
+       "24184  24184  \n",
+       "24185  24185  \n",
+       "24186  24186  \n",
+       "24187  24187  \n",
+       "24188  24188  \n",
+       "\n",
+       "[24189 rows x 6 columns]"
+      ]
+     },
+     "execution_count": 15,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "import pandas as pd\n",
+    "dataset = pd.read_csv(\"cache.csv\")\n",
+    "dataset"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 16,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "prompt = \"\"\"\n",
+    "User:\n",
+    "In the given Bitcoin forum thread, pay close attention to the language used when mentioning hardware pieces. Look for explicit statements indicating ownership or hypothetical discussions.\n",
+    "\n",
+    "```thread\n",
+    "{}\n",
+    "```\n",
+    "\n",
+    "\n",
+    "\n",
+    "Reply with the hardware names, all in the same line, separated by commas. Then, on a new line, list \"True\" or \"False\" for each piece of hardware to indicate ownership status. True if the mention suggests concrete ownership by any user, and False if the hardware is discussed in a hypothetical or speculative way.\n",
+    "\n",
+    "Assistant:\n",
+    "Sure! Here is the requested output, with the correct ownership status for each piece of hardware:\n",
+    "Hardware names:\n",
+    "\"\"\".strip()"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 17,
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "Error processing thread:2344\n",
+      "Error processing thread:2907\n",
+      "Error processing thread:2967\n",
+      "Error processing thread:4609\n",
+      "Error processing thread:5493\n",
+      "Error processing thread:6543\n",
+      "Error processing thread:6620\n",
+      "Error processing thread:6956\n",
+      "Error processing thread:7170\n",
+      "Error processing thread:9152\n",
+      "Error processing thread:9306\n",
+      "Error processing thread:12206\n",
+      "Error processing thread:13251\n",
+      "Error processing thread:14915\n"
+     ]
+    }
+   ],
+   "source": [
+    "# create inputs that will be given to trained model\n",
+    "inputs = pd.DataFrame()\n",
+    "for i in range(len(df)):\n",
+    "    index, date, thread = process_thread(df.iloc[i])\n",
+    "    prompt2 = prompt.format(thread)\n",
+    "    inputs = pd.concat([inputs, pd.DataFrame({'input': [prompt2]})], ignore_index=True)\n",
+    "\n",
+    "\n",
+    "inputs.to_csv(\"inputs.csv\", index=False)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 18,
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "User:\n",
+      "In the given Bitcoin forum thread, pay close attention to the language used when mentioning hardware pieces. Look for explicit statements indicating ownership or hypothetical discussions.\n",
+      "\n",
+      "```thread\n",
+      "Date: 2013-03\n",
+      "Topic:  [Group Buy in China]  Avalon batch #3\n",
+      "### Original post:\n",
+      "List of <truncated> Forum Name - Bitcoin Address - Amount Invested\n",
+      "\n",
+      "### Reply 1:\n",
+      "Interesting!I am in China too.I will consider this investment.\n",
+      "\n",
+      "### Reply 2:\n",
+      "Thanks for trusting me,225BTC received! <truncated> please PM or QQ me\n",
+      "\n",
+      "\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "Reply with the hardware names, all in the same line, separated by commas. Then, on a new line, list \"True\" or \"False\" for each piece of hardware to indicate ownership status. True if the mention suggests concrete ownership by any user, and False if the hardware is discussed in a hypothetical or speculative way.\n",
+      "\n",
+      "Assistant:\n",
+      "Sure! Here is the requested output, with the correct ownership status for each piece of hardware:\n",
+      "Hardware names:\n"
+     ]
+    }
+   ],
+   "source": [
+    "print(inputs.iloc[0].values[0])"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 19,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/html": [
+       "<div>\n",
+       "<style scoped>\n",
+       "    .dataframe tbody tr th:only-of-type {\n",
+       "        vertical-align: middle;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe tbody tr th {\n",
+       "        vertical-align: top;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe thead th {\n",
+       "        text-align: right;\n",
+       "    }\n",
+       "</style>\n",
+       "<table border=\"1\" class=\"dataframe\">\n",
+       "  <thead>\n",
+       "    <tr style=\"text-align: right;\">\n",
+       "      <th></th>\n",
+       "      <th>input</th>\n",
+       "    </tr>\n",
+       "  </thead>\n",
+       "  <tbody>\n",
+       "    <tr>\n",
+       "      <th>0</th>\n",
+       "      <td>User:\\nIn the given Bitcoin forum thread, pay ...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>1</th>\n",
+       "      <td>User:\\nIn the given Bitcoin forum thread, pay ...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>2</th>\n",
+       "      <td>User:\\nIn the given Bitcoin forum thread, pay ...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>3</th>\n",
+       "      <td>User:\\nIn the given Bitcoin forum thread, pay ...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>4</th>\n",
+       "      <td>User:\\nIn the given Bitcoin forum thread, pay ...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>...</th>\n",
+       "      <td>...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24184</th>\n",
+       "      <td>User:\\nIn the given Bitcoin forum thread, pay ...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24185</th>\n",
+       "      <td>User:\\nIn the given Bitcoin forum thread, pay ...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24186</th>\n",
+       "      <td>User:\\nIn the given Bitcoin forum thread, pay ...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24187</th>\n",
+       "      <td>User:\\nIn the given Bitcoin forum thread, pay ...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>24188</th>\n",
+       "      <td>User:\\nIn the given Bitcoin forum thread, pay ...</td>\n",
+       "    </tr>\n",
+       "  </tbody>\n",
+       "</table>\n",
+       "<p>24189 rows × 1 columns</p>\n",
+       "</div>"
+      ],
+      "text/plain": [
+       "                                                   input\n",
+       "0      User:\\nIn the given Bitcoin forum thread, pay ...\n",
+       "1      User:\\nIn the given Bitcoin forum thread, pay ...\n",
+       "2      User:\\nIn the given Bitcoin forum thread, pay ...\n",
+       "3      User:\\nIn the given Bitcoin forum thread, pay ...\n",
+       "4      User:\\nIn the given Bitcoin forum thread, pay ...\n",
+       "...                                                  ...\n",
+       "24184  User:\\nIn the given Bitcoin forum thread, pay ...\n",
+       "24185  User:\\nIn the given Bitcoin forum thread, pay ...\n",
+       "24186  User:\\nIn the given Bitcoin forum thread, pay ...\n",
+       "24187  User:\\nIn the given Bitcoin forum thread, pay ...\n",
+       "24188  User:\\nIn the given Bitcoin forum thread, pay ...\n",
+       "\n",
+       "[24189 rows x 1 columns]"
+      ]
+     },
+     "execution_count": 19,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "inputs"
+   ]
+  }
+ ],
+ "metadata": {
+  "kernelspec": {
+   "display_name": "base",
+   "language": "python",
+   "name": "python3"
+  },
+  "language_info": {
+   "codemirror_mode": {
+    "name": "ipython",
+    "version": 3
+   },
+   "file_extension": ".py",
+   "mimetype": "text/x-python",
+   "name": "python",
+   "nbconvert_exporter": "python",
+   "pygments_lexer": "ipython3",
+   "version": "3.10.13"
+  },
+  "orig_nbformat": 4,
+  "vscode": {
+   "interpreter": {
+    "hash": "ad2bdc8ecc057115af97d19610ffacc2b4e99fae6737bb82f5d7fb13d2f2c186"
+   }
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 2
+}

bitcoinforum/2_train_set_creation/demo_dataset.csv

@@ -0,0 +1,458 @@
+index,input,output
+4109,"Date: 2012-06
+Topic: Selling another batch of 40 ICARUS - sold out
+### Original post:
+Those Icarus are batch 3, tested for several weeks by me. mostly test with cgminer rig development, use OpenWrt router as host.I will take orders from tomorrow, Wednesday, May 23 5:00AM UTC+8 (don't send email before this time) ---- until all 40 are sold.Price: 480USD + shipping cost.Package content: Icarus, usb cable, power adapter or power wireAll package will send by EMS (<link> time we only accept BTC. after I receive order email I will send a new btc address to you. then after i receice the btc, I will ship your package immediately.Orders take by email <truncated> please add [ICARUS] to the subject. there is no confirm email. I will send you one email after I get the EMS track NO.(means packages already sent out, shipping from Beijing/China with EMS). please write those information in email:1. How many Icarus you want.2. You want power adapter or power wire. I advise you using your own ATX power if you order more then 2 Icarus.3. Address detail: name: company(optional): address: city: province: country: ZIP: TEL:More Icarus info please check:<link><link>
+
+### Reply 1:
+wow!Now here is all sold out , anyone interested in ICArus boards should visit this topic:<link> still some ICA available there.
+
+### Reply 2:
+Another 10 Icarus.
+
+","{
+  ""hardware"": [
+    {
+      ""hardware_name"": ""ICARUS"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""ICARUS boards"",
+      ""hardware_is_owned"": false
+    },
+    {
+      ""hardware_name"": ""ICA"",
+      ""hardware_is_owned"": false
+    }
+  ]
+}"
+11208,"Date: 2022-09
+Topic: Advice -Adding additional 6 pin PCIE outputs on a PC modular Power Supply?
+### Original post:
+Hi AllI have a few modular/semi modular PC psu's and was thinking of using the to pwer some S9 miners with 2 cards. Most of what i have are 1000w or higher.They will be worthless selling so might be better put to use on some S9s powered with2 cards, so i would need x7 ouputs all together.I think i could use an existing hard wired PCIE (6 pin or not) to power the control board.Then on the dedicated high amp PCIE modular ouputs could i not solder on connections and 'share' the load so x2 on each output?I have only seen x8 to x2 PCIE cables so could i not just splice in and solder another?If this works i could do a few more miers in thsi set up as it would be low power and quite when set to 700/800w.Anyone done this or got an opinion on it?The PSU's will either go to waste tbh.Pics attached.<link>
+
+### Reply 1:
+@NotFuzzyWarmYes i will be running only 2 boards @ 700w or 800w.Is that why 'common rail' modular PSUs are so expensive?The only PSUs i can see that have enough outputs (X7) are the EVGA ones and they are silly money, i'm surprised that nobody has found a decent PSU and 'modded' them for more outputs tbh.....I just can't find makes that suffice apart from that brand?I think if i open it i can see rails and go from there, 3 on each for the hash boards and an existing 12v ouput for the control board.Thanks for the advice.
+
+### Reply 2:
+Looks like the +12v are seperate rails and GND/-12v shared.I will just add an extra pin to each double 8pin >x2 6pin.So i will have a set of two 8pin >x3 6 pins.Current will be approx 800/12=66.67aIs this correct?<link>
+
+### Reply 3:
+To be honest, modular plug PSU's all have 1 major problem: They are pushing the maximum current rating through the contacts and generally have only 18ga wires between the PSU and PCIe plugs.Ok, that's 2 major problems...That said, since you are talking about running at reduced power it may not be an issue, just periodically check to see how warm the PSU connectors get. Yes, I've had a few rather spectacularly fry over the years from when I used them to power s3's & s5's...Other thing to keep in mind is that particular PSU has 2 independent output rails. DO NOT connect power from the 2 different rails to 1 hash board! They will be shorted together and fight each other.
+
+","{
+  ""hardware"": [
+    {
+      ""hardware_name"": ""S9 miners"",
+      ""hardware_is_owned"": false
+    },
+    {
+      ""hardware_name"": ""PC modular power supply"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""EVGA power supply"",
+      ""hardware_is_owned"": false
+    },
+    {
+      ""hardware_name"": ""hash boards"",
+      ""hardware_is_owned"": false
+    },
+    {
+      ""hardware_name"": ""PCIe plugs"",
+      ""hardware_is_owned"": false
+    },
+    {
+      ""hardware_name"": ""S3 miners"",
+      ""hardware_is_owned"": false
+    },
+    {
+      ""hardware_name"": ""S5 miners"",
+      ""hardware_is_owned"": false
+    }
+  ]
+}"
+12483,"Date: 2013-07
+Topic: Please Help: Mining with both cores of 5970 with cgminer?
+### Original post:
+Hi, I'm having trouble setting up a 5970 and mining with cgminer The rig is running Linux (Xubuntu) and the 5970 is the only card ( I've followed this guide which has always worked with my other setups.)When I run cgminer -n from the terminal emulator on the desktop I get the <truncated> -nCL Platform 0 vendor: Advanced Micro Devices, Inc. CL Platform 0 name: AMD Accelerated Parallel Processing CL Platform 0 version: OpenCL 1.1 AMD-APP-SDK-v2.5 (793.1) Platform 0 devices: 1 0 Cypress ADL found more devices than opencl! There is possibly at least one GPU that doesn't support OpenCL Use the gpu map feature to reliably map OpenCL to ADL WARNING: Number of OpenCL and ADL devices did not match! Hardware monitoring may NOT match up with devices! GPU 0 ATI Radeon HD 5900 Series hardware monitoring enabled 1 GPU devices max detected Seems to me, cgminer is not recognizing both cores of the 5970.(When I mine with cgminer from the terminal emulator on the Desktop, it's mining with only one core of the 5970)Interestingly, when I run the same command from a SSH terminal it gives me:Code:./cgminer -nCL Platform 0 vendor: Advanced Micro Devices, Inc. CL Platform 0 name: AMD Accelerated Parallel <rest of post truncated>
+
+### Reply 1:
+Do you have the newest drivers?
+
+### Reply 2:
+Usual instructions for when people DONT read the readme.Reconfigure xorg for all devices, start x and export the DISPLAY variable before starting cgminer.
+
+### Reply 3:
+I just find it so weird how people dont read something that specifically says ""READ ME!""
+
+### Reply 4:
+Ahh, thanks guys I actually was exporting the DISPLAY variable in my mining startup script but I'd stupidly disabled this while installing/testing the card. That seems to have solved that problem! Unfortunately this led me on to a new issue: The Xubuntu computer loses power very quickly when I start mining on the 5970 with anything above intensity 1, but it mines fine (intensity 11) when installed in a different windows machine...When the linux comp powers off, it's without warning I have to wait a little and toggle the PSU switch before turning it on again. Both PC's have adequate PSU's (760W) and the 5790 is the only card being used. So it has me puzzled. Why would mining cause the linux machine to quickly shut off? Temps on the fan never get a chance to hit 80 before the power cuts off.I will start a new thread on this if it comes to me getting completely stuck (I can try a 7870 in the linux computer and see if it has the same problem), but I hoped someone may have a good idea why this is happening? ATI drivers are 11.11Thank you very much for ideas on this one and happy hashing!
+
+### Reply 5:
+Last problem now appears fixed after replacing PSU. Thanks again for the help!
+
+### Reply 6:
+Hi ckolivas,I read the readme, but I may be to ""slow"" to understand. I would definitely appreciate your help.I'm getting the same error. I triedsudo aticonfig --adapter=0,1 --initialI also have the following lines in my shell file to start cgminerexport DISPLAY=:0export <truncated> <truncated> I'm missing?
+
+### Reply 7:
+I realize I'm having issues with X server to start. So guess I need to fix that somehow.
+
+","{
+  ""hardware"": [
+    {
+      ""hardware_name"": ""5970"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""ATI Radeon HD 5900 Series"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""5790"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""7870"",
+      ""hardware_is_owned"": false
+    },
+    {
+      ""hardware_name"": ""760W PSU"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""PSU"",
+      ""hardware_is_owned"": false
+    }
+  ]
+}"
+23073,"Date: 2019-09
+Topic: ASIC Not working!!! HELP
+### Original post:
+An ASIC is an Application Specific Integrated Circuit, eg the chips used in a miner. I take it your MINER is not working and we are supposed to just check our crystal ball or guess what kind of miner it is? Try giving some useful information about it such <truncated> new or used?
+
+### Reply 1:
+a 17 second video is worthless.how about a guihow about api logshow about make and model?looks like an innosiliconlooks like it needs 2 psu'sis it this miner a6 or a6+
+
+### Reply 2:
+hey guys I bought AladdinMiner T1 and a psu but now the psu is not working, so I bought new ""bitmain APW3++"" and it was working fine the next day I increase the performance of the asic and it switched off now I can't turn it on!!!here is the video:<link> lights are not working.no ip address.fans starts and strops working.HELP
+
+### Reply 3:
+He clearly edited the post after you guys have commented, anyhow , this is the miner he is talking about I guess.<link> it does look like an Inno gear with a bit of modification, in that link they clearly saywhich means phill is right, you need at least two PSUs, each must be 1400w minimum , and according to the video, it does look like he got 2 PSUs connected, the miner's fan do spin for a while and then stop , and you saidWhich means you tried to overclock the miner, you either burned the miner or one of the PSUs, does it show on the network ?? can you access the user interface? please post more details.
+
+### Reply 4:
+Do note that the OP has not made any mention of trying to contact the distributor or manufacturer of this knock-off miner. That of course should be the very first thing the OP should have done...Nor have they posted anything else re what has been said so far.
+
+### Reply 5:
+He needs to know it's a knock-off in the first place, and honestly if the gear does 32th at 2800w as promised-- it does not matter what name they put on it, as for contacting the manufacturer, honestly this is usually the last thing I personally do simply because1-The support at these Chinese websites is terrible, had a ton of issues with my gears, most were solved by trial and error or from information I got online (mostly on this very forum) , while the manufacturer will give only give you the abc of trouble shooting only.2-In many places, the shipping cost for returning the miner back to china is unreasonable, to the extent that some people rather order new hash board/control board or a PSU than having to pay that much for shipping or wait for months to get their replacement.I think if OP provides enough information and kernel log, someone will be able to give him the solution for this problem without the need for a crystal ball.
+
+","{
+  ""hardware"": [
+    {
+      ""hardware_name"": ""AladdinMiner T1"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""bitmain APW3++"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""Innosilicon"",
+      ""hardware_is_owned"": false
+    },
+    {
+      ""hardware_name"": ""PSU"",
+      ""hardware_is_owned"": false
+    },
+    {
+      ""hardware_name"": ""knock-off miner"",
+      ""hardware_is_owned"": false
+    }
+  ]
+}"
+19054,"Date: 2014-03
+Topic: USB Block Erupter showing up as generic USB Device instead of ""Port"", won't mine
+### Original post:
+I've been mining with two USB Block Erupter Sapphires without issue for at least a week now, properly cooled. Today, I've been messing around with things trying to get my Antminer U2 up and running and must've done something that now causes one of my erupters to show up under Device Manager as a usb device instead of under ""Ports"". When I try to mine with it, it just sits in standby doing nothing. However, if I plug it into my Win 7 machine it comes up normally under ""Ports"" instead of ""Universal Serial Bus Devices"" but I don't have an ethernet to that box to test if it will mine. I'm not sure what exactly is going on with this stick. Is it fried?
+
+### Reply 1:
+Maybe you installed a WinUSB driver?
+
+### Reply 2:
+Is the problem on a windows xp machine? This may be a device identifier issue. I've never seen it with 3 devices, but I suppose it is possible. There is a fix posted in these forums somewhere and if I have time to dig it up for you I will, but if you keep restarting and plugging it back in to different ports it may eventually pick up properly. Windows XP doesn't handle duplicate usb devices very well.
+
+","{
+  ""hardware"": [
+    {
+      ""hardware_name"": ""USB Block Erupter Sapphire"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""Antminer U2"",
+      ""hardware_is_owned"": false
+    }
+  ]
+}"
+9265,"Date: 2015-08
+Topic: A little more proof the Cloudthink miner is fake... Shilled reddit accounts
+### Original post:
+How is this site still a thing? Has there not already been extensive proof uncovered that Cloudthink is a scam? I haven't talked to anyone within the Bitcoin community that has regarded as anything other than a scam.
+
+### Reply 1:
+Has anyone from Manchester walked to their supposed office? It wouldn't take much effort to provide verifiable evidence that this is a scam.
+
+### Reply 2:
+All I want to add is shame on any of the upstanding members that took on their Sig campaign and contributed to anyone getting taken advantage of. Betrayed by greed once again. I feel bad for anyone inexperienced that fell for this scam, it may have been obvious to most of us, but it was slightly less poorly planned out than many others.
+
+### Reply 3:
+Yes<link>
+
+### Reply 4:
+What about the dollar a day whores who signed up for the ""free"" packages and incessantly bumped this thread?<link> was plenty to be suspicious about when they signed up in the middle of June.
+
+","{
+  ""hardware_mentions"": []
+}"
+21036,"Date: 2016-05
+Topic: MOVED: [AJUDA] Montar Máquina de Mineração
+### Original post:
+This topic has been moved to Trashcan.<link> in English.
+
+","[
+    {
+        ""hardware_name"": ""Antminer S9"",
+        ""hardware_is_owned"": false
+    },
+    {
+        ""hardware_name"": ""AvalonMiner 741"",
+        ""hardware_is_owned"": false
+    },
+    {
+        ""hardware_name"": ""Bitmain Antminer L3+"",
+        ""hardware_is_owned"": false
+    },
+    {
+        ""hardware_name"": ""Innosilicon T2T"",
+        ""hardware_is_owned"": false
+    },
+    {
+        ""hardware_name"": ""Dragonmint T1"",
+        ""hardware_is_owned"": false
+    }
+]"
+11702,"Date: 2011-12
+Topic: Monitoring of hash rate over short time periods
+### Original post:
+HiI'm running cgminer with quite a few gpus. I want to tweak and monitor performance of each gpu at a time so I can fine tune them. Cgminer just offers average has hashrate for all. (6 gpus per client)Can I do this or is there another way I shud go about it? The average per gpu jumps around too much for my liking.Thank you.
+
+### Reply 1:
+You sure? Highlighted numbers are average per card AFAIK:
+
+### Reply 2:
+Yes but mine is constantly jumping around with very large variability . Is yours more stable? Upon further research I see a post where someone has mentioned switching to overclock makes the average more stable (6990) - ill test that out tho I wud prefer to keep it at 375W so I can predict electricity usage. In the meantime the average rate per gpu jumps around so much its ikpossible to gauge whether ur getting a small increase in hashing power.
+
+### Reply 3:
+The left figure (458.0) fluctuates a bit, I think its a 5s average; the right one that I highlighted (456.6), doesnt change at all (after running for a while). I think that is the average since starting the app?
+
+","{
+  ""hardware"": [
+    {
+      ""hardware_name"": ""gpu"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""6990"",
+      ""hardware_is_owned"": false
+    }
+  ]
+}"
+10730,"Date: 2018-05
+Topic: Ledger Nano Ether Wallet
+### Original post:
+Hi, first time using Ledger nano s, with MEW wallet, i log in, it shows 5 different MEW address, are those all mine? who created those account, and how come I don't see private key when I log in those accounts? Also, I don't need any password like a normal wallet? little confused here how it works, can anyone explain? thanks
+
+### Reply 1:
+Consider Myetherwallet as an interface to interact with your Ledger nano S. You will still need to enter the PIN to unlock your Ledger or confirm the transactions from the device. The addresses are yours, pre-generated from your seed.
+
+### Reply 2:
+Ledger has its own HowTo for MyEtherWallet, have a look: <link> are also a ton of guides, blog articles and videos available: <link>
+
+### Reply 3:
+These wallets have already been built in you ledger nano s. When I'm bought trezor I got 5 eth addresses for my device. You can check your own cabinet on ledger where you can configure all functions
+
+### Reply 4:
+Thank you, but how come I am not able to see the private key for those pre-built 5 accounts? does it mean, I don't need private keys for those accounts?
+
+### Reply 5:
+Hello imteaz, look here:<link> hope the information will help you. All the best
+
+### Reply 6:
+The private-key is inside your Ledger. Putting in a simple way, MEW uses your public key (address) to see your balance and build the transaction, which its sent to the Ledger device, signed with the private-key and sent back to the computer, where its broadcasted. The private-key never leaves the device (reason why you can't see them, and why hardware wallets are so secure compared to normal desktop wallets).
+
+","{
+  ""hardware_devices"": [
+    {
+      ""hardware_name"": ""Ledger Nano S"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""Trezor"",
+      ""hardware_is_owned"": true
+    }
+  ]
+}"
+21854,"Date: 2017-11
+Topic: AntMiner R4 Stopped working
+### Original post:
+my Antminer R4 (Antminer R4, Batch 5(7.5TH/s)) suddenly stopped working after reboot. i tried various options like reset using different methods but i cant get it to workeven the web based admin console was not reachable however afrer several reboots and holding the IP button i was able to connect to web based control panel...however strange problem is that i cant see the miner config screen though i can see other screensi updated firmware using web based console n got success message but still same problem persists...pfa screenshots and kindly advise ...<link>
+
+### Reply 1:
+too late you did firmware upgradei can't help you sorry.if you are usa based maybe bitmain warranty can help<link> r4 breaks alot and you muscled a firmware update on a broken r4.your best shot is bitmainwarranty good luck
+
+### Reply 2:
+is there a way to connect using ssh....
+
+### Reply 3:
+Too late .The r4 is very delicate,They break and break and break.Someone had a link that show how to reset to the original firmware.someone gave it to me it may work if you reset it.I will look for a link to the reset.In I reset it and it still did not work.I sent it in to bitmainwarranty and they did fix it.
+
+### Reply 4:
+You can ssh into it with username root and password admin.I doubt the firmware is causing this, at least, if it was installed correctly. I had an R4 controller fail and I replaced it with an S9 controller, flashing it with the R4 firmware and it works fine. If the image was installed properly, and your controller isn't broken, it should be working. Make sure you don't have anything preventing javascript from running on that page.The ""ant_data=;"" you see in the miner configuration page is there because the header has an inline script that begins with Code:echo ""ant_data = ${ant_result};"" The script is fetching cgi data from the config saved in <truncated> For some reason it is failing at that point.
+
+### Reply 5:
+thanks all for your suggestions ..
+
+","{
+  ""hardware"": [
+    {
+      ""hardware_name"": ""Antminer R4"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""S9 controller"",
+      ""hardware_is_owned"": false
+    }
+  ]
+}"
+23255,"Date: 2020-04
+Topic: BlackArrow Prospero X-3 [Help] (2020)
+### Original post:
+Hi,I just bought myself the Black Arrow X3, for my personal collection of asics. But, I cannot connect to operate the machine. I saw that for the login it is: user = user, passworld = blackarrow but it shows me an error message that something is not valid. I contacted the seller and he said he knew nothing. Is it possible to reset the machine?
+
+### Reply 1:
+He might have sold you an unit which is affected by firmware virus. If he claims that he does not know what is wrong, that is probably because he was in same boat as you. Or he might have changed the password and forgot.But for your sake, try resetting your machine via reset button or recovery SD card.Also, isn't that unit like 5 years old? Why did you even buy it?
+
+### Reply 2:
+I make a collection of asic and I test it to find out how it works.
+
+### Reply 3:
+Check this post before firing them up, they have a history of burning down.<link>
+
+","{
+  ""hardware"": [
+    {
+      ""hardware_name"": ""Black Arrow X3"",
+      ""hardware_is_owned"": true
+    }
+  ]
+}"
+11328,"Date: 2023-07
+Topic: Antminer S19 Control Board
+### Original post:
+The Antminer S19 Control Board is a powerful and essential component of the Antminer S19 mining rig. Designed to optimize performance and efficiency, this control board plays a crucial role in ensuring the smooth operation of your mining equipment.The Antminer S19 Control Board is engineered to deliver exceptional performance, allowing you to maximize the hashing power of your mining rig. With its advanced chipset and optimized firmware, this control board ensures efficient communication between the different components of your Antminer S19, resulting in higher mining productivity and increased profitability.The Antminer S19 Control Board features a user-friendly interface that simplifies the management and monitoring of your mining rig. With its intuitive design and easy-to-navigate settings, you can efficiently control various parameters such as fan speed, voltage, and temperature. To Know More:<link>
+
+### Reply 1:
+I think we all know what a Control Board is.However, what we don't know is why you're writing this, in a way worthy of an AI, and on top of that putting the link of a Whatsminer PSU which is completely off-topic.
+
+### Reply 2:
+I recently purchased Antminer S19 pro 110Th from 570OLLC. Here's the link if you guys are interested: <link>
+
+### Reply 3:
+Are you sure you purchased the s19 unit from that link?When exactly?Or are you just trying to promote it here just like on other forums with some other newbie alt accounts and trying to promote it with fake/sweet words?I'm talking about this forum as you can see all responses came from newbies so it's very risky to buy on this site.
+
+","{
+  ""hardware"": [
+    {
+      ""hardware_name"": ""Antminer S19 Control Board"",
+      ""hardware_is_owned"": false
+    },
+    {
+      ""hardware_name"": ""Antminer S19 pro 110Th"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""Whatsminer PSU"",
+      ""hardware_is_owned"": false
+    }
+  ]
+}"
+16133,"Date: 2021-09
+Topic: Innosilcon is trying to get rid of heavily used miners
+### Original post:
+Innosilicon is offering ""manufacturer refurbished"" T3+ and other miners. I ordered a T3+ 57T Bitcoin miner. I had to wait for 4 weeks after I paid in full in Bitcoin until they shipped it out. When it arrived it was in horrible condition: <link> of dust, with scratches, stains, missing screws, rattling parts, rust...The firmware was locked and I was not able to enter my own pool settings. There was plenty of evidence that this miner was not manufacturer refurbished, not even cleaned. Otherwise at least the firmware would have been reset. Innosilicon has 3 departments: while the support is trying to help to unlock the miner, the sales and order team tells me: ""This is what you get when you order from us. Deal with it!""
+
+### Reply 1:
+I think other ppl here ordered the refurb T3s. Would be great to have their feedbacks!
+
+### Reply 2:
+Yes, please. Who else bought a refurb T3+ ? What was your experience?
+
+### Reply 3:
+have you ever got to the bottom of the pool settings being pre-completed and not updating ?also, sorry to hear about your experience, I hope it all goes well in the end
+
+### Reply 4:
+Yeah, they use the term refurbished for a miner that was damaged and repaired by them or something returned and they've set it back running. They did warn a bit but you didn't take the warning seriously, usually in those cases light scratches mean run over by an excavator:Sucks and if I were in your place, even if support manages to help you unblock the settings I would play possum and try to get a refund and send it back. I won't be surprised if that thing wouldn't break in a few months, external scratched and missing screws ain't a big deal but you should take a look inside if possible and have a beer nearby when you do
+
+### Reply 5:
+Refurbished miners could be a great bargain if you get a diamond in the rough with no issues but that is playing a dangerous game if there is no warranty attached to them. Depending on the price and time to get to you it may pay itself off quickly but if it breaks it could quickly become a paperweight or something that ends u costing what a new unit would plus the downtime to ship it back for repairs. Would love to hear feedback as well from anyone who bought one.
+
+### Reply 6:
+Those Innosilicon refurbished miners are 6 months garanty
+
+### Reply 7:
+You are right with the firmware lock, but this is a straight-out scam if you ask me, these were supposed to be ""manufacturer refurbished"", the ones in the video don't look anything like it, in fact, REAL refurbished miners are a lot more expensive than clean used miners, a while back used S9js were going for $250 while the refurbished once were going for at least $400, but those looked as good as new, no scratches, no lost screws, everything seemed like brand new, the miner in the video is a Used Miner with C- condition, selling it as a refurbished piece is nothing but scam IMO.
+
+### Reply 8:
+Looks like this is a rare problem that has happened before.There are threads about a T2 miner that had it on here.. also one on the russian mining board:<link> might need to do a translate on it with your browser)Post 11 reads:Maybe worth reaching out. Seems they found someone at Inno that can unlock it remotely for you.
+
+### Reply 9:
+Watching some videos from your YouTube channel and I like the soundproofing you have setup. I'd probably be mining with more hashrate at my home if I had such a setup as well. I should also mention that I thought for a second this was a bodybuilding YouTube channel instead of being about Bitcoin mining. From the look of your biceps I thought you might go hulk and crush that thing when it wasn't working.
+
+### Reply 10:
+Interesting , they do that constantley , I heard that their ceo is a close friend to the founder of ETH
+
+### Reply 11:
+Figured they would carry some sort of limited warranty. That said, considering Inno was made aware of the Fixed Address issue on at least some miners and quickly responded by putting out a fix for it one can't fault them for their response on that part. They also said they were going to issue a mass email to all customers who bought one of the refurbed miners to notify of them of the possible problem and fix for it if they received a miner that was locked. Hopefully the OP just got a miner that had already been shipped just before Inno became aware of the problem and the miner had yet yet been updated to OEM firmwareMy take on things is that the miners are of course from some of the farms in China that got shut down. It makes sense that a farm would use locked firmware to make sure there is (near) zero chance of miners being hijacked either through hacking or actual theft. If stolen, as soon as the miner goes on line Inno will know which miner and what the ip address is.Biggest problem is Inno dropping the ball on making sure the miners are at least cleaned up and along with that definitely reset back<rest of thread truncated>
+","{
+  ""hardware"": [
+    {
+      ""hardware_name"": ""T3+ 57T Bitcoin miner"",
+      ""hardware_is_owned"": true
+    },
+    {
+      ""hardware_name"": ""T3+"",
+      ""hardware_is_owned"": false
+    },
+    {
+      ""hardware_name"": ""S9j"",
+      ""hardware_is_owned"": false
+    },
+    {
+      ""hardware_name"": ""T2 miner"",
+      ""hardware_is_owned"": false
+    }
+  ]
+}"
+11378,"Date: 2010-11
+Topic: Buffer overflow
+### Original post:
+This has happened to me every time a hash with zeros is found on my 64-bit Atom system:Code:DBG: found zeroes in <truncated> 8150287 hashes, 123.22 khash/secPROOF OF WORK FOUND? submitting... *** buffer overflow detected ***: ./minerd terminated======= Backtrace: <truncated> mentioned the problems with -march=atom CFLAGS previously, but this does not go away when changing the -march.
+
+### Reply 1:
+Fixed in git commit <truncated> just pushed to cpuminer.git.
+
+","[
+    {
+        ""hardware_name"": ""64-bit Atom system"",
+        ""hardware_is_owned"": true
+    }
+]"

bitcoinforum/2_train_set_creation/inputs.csv

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b1a1985edebcc58cf9ab32b72b135b3df8a76a176447ca83e472c69a24025e8
+size 71379688

bitcoinforum/3_training/mistral/lora_model/README.md

@@ -0,0 +1,202 @@
+---
+library_name: peft
+base_model: mistralai/Mistral-7B-v0.1
+---
+
+# Model Card for Model ID
+
+<!-- Provide a quick summary of what the model is/does. -->
+
+
+
+## Model Details
+
+### Model Description
+
+<!-- Provide a longer summary of what this model is. -->
+
+
+
+- **Developed by:** [More Information Needed]
+- **Funded by [optional]:** [More Information Needed]
+- **Shared by [optional]:** [More Information Needed]
+- **Model type:** [More Information Needed]
+- **Language(s) (NLP):** [More Information Needed]
+- **License:** [More Information Needed]
+- **Finetuned from model [optional]:** [More Information Needed]
+
+### Model Sources [optional]
+
+<!-- Provide the basic links for the model. -->
+
+- **Repository:** [More Information Needed]
+- **Paper [optional]:** [More Information Needed]
+- **Demo [optional]:** [More Information Needed]
+
+## Uses
+
+<!-- Address questions around how the model is intended to be used, including the foreseeable users of the model and those affected by the model. -->
+
+### Direct Use
+
+<!-- This section is for the model use without fine-tuning or plugging into a larger ecosystem/app. -->
+
+[More Information Needed]
+
+### Downstream Use [optional]
+
+<!-- This section is for the model use when fine-tuned for a task, or when plugged into a larger ecosystem/app -->
+
+[More Information Needed]
+
+### Out-of-Scope Use
+
+<!-- This section addresses misuse, malicious use, and uses that the model will not work well for. -->
+
+[More Information Needed]
+
+## Bias, Risks, and Limitations
+
+<!-- This section is meant to convey both technical and sociotechnical limitations. -->
+
+[More Information Needed]
+
+### Recommendations
+
+<!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
+
+Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations.
+
+## How to Get Started with the Model
+
+Use the code below to get started with the model.
+
+[More Information Needed]
+
+## Training Details
+
+### Training Data
+
+<!-- This should link to a Dataset Card, perhaps with a short stub of information on what the training data is all about as well as documentation related to data pre-processing or additional filtering. -->
+
+[More Information Needed]
+
+### Training Procedure
+
+<!-- This relates heavily to the Technical Specifications. Content here should link to that section when it is relevant to the training procedure. -->
+
+#### Preprocessing [optional]
+
+[More Information Needed]
+
+
+#### Training Hyperparameters
+
+- **Training regime:** [More Information Needed] <!--fp32, fp16 mixed precision, bf16 mixed precision, bf16 non-mixed precision, fp16 non-mixed precision, fp8 mixed precision -->
+
+#### Speeds, Sizes, Times [optional]
+
+<!-- This section provides information about throughput, start/end time, checkpoint size if relevant, etc. -->
+
+[More Information Needed]
+
+## Evaluation
+
+<!-- This section describes the evaluation protocols and provides the results. -->
+
+### Testing Data, Factors & Metrics
+
+#### Testing Data
+
+<!-- This should link to a Dataset Card if possible. -->
+
+[More Information Needed]
+
+#### Factors
+
+<!-- These are the things the evaluation is disaggregating by, e.g., subpopulations or domains. -->
+
+[More Information Needed]
+
+#### Metrics
+
+<!-- These are the evaluation metrics being used, ideally with a description of why. -->
+
+[More Information Needed]
+
+### Results
+
+[More Information Needed]
+
+#### Summary
+
+
+
+## Model Examination [optional]
+
+<!-- Relevant interpretability work for the model goes here -->
+
+[More Information Needed]
+
+## Environmental Impact
+
+<!-- Total emissions (in grams of CO2eq) and additional considerations, such as electricity usage, go here. Edit the suggested text below accordingly -->
+
+Carbon emissions can be estimated using the [Machine Learning Impact calculator](https://mlco2.github.io/impact#compute) presented in [Lacoste et al. (2019)](https://arxiv.org/abs/1910.09700).
+
+- **Hardware Type:** [More Information Needed]
+- **Hours used:** [More Information Needed]
+- **Cloud Provider:** [More Information Needed]
+- **Compute Region:** [More Information Needed]
+- **Carbon Emitted:** [More Information Needed]
+
+## Technical Specifications [optional]
+
+### Model Architecture and Objective
+
+[More Information Needed]
+
+### Compute Infrastructure
+
+[More Information Needed]
+
+#### Hardware
+
+[More Information Needed]
+
+#### Software
+
+[More Information Needed]
+
+## Citation [optional]
+
+<!-- If there is a paper or blog post introducing the model, the APA and Bibtex information for that should go in this section. -->
+
+**BibTeX:**
+
+[More Information Needed]
+
+**APA:**
+
+[More Information Needed]
+
+## Glossary [optional]
+
+<!-- If relevant, include terms and calculations in this section that can help readers understand the model or model card. -->
+
+[More Information Needed]
+
+## More Information [optional]
+
+[More Information Needed]
+
+## Model Card Authors [optional]
+
+[More Information Needed]
+
+## Model Card Contact
+
+[More Information Needed]
+### Framework versions
+
+- PEFT 0.9.0

bitcoinforum/3_training/mistral/lora_model/adapter_config.json

@@ -0,0 +1,33 @@
+{
+  "alpha_pattern": {},
+  "auto_mapping": null,
+  "base_model_name_or_path": "mistralai/Mistral-7B-v0.1",
+  "bias": "none",
+  "fan_in_fan_out": false,
+  "inference_mode": true,
+  "init_lora_weights": true,
+  "layers_pattern": null,
+  "layers_to_transform": null,
+  "loftq_config": {},
+  "lora_alpha": 16,
+  "lora_dropout": 0,
+  "megatron_config": null,
+  "megatron_core": "megatron.core",
+  "modules_to_save": null,
+  "peft_type": "LORA",
+  "r": 16,
+  "rank_pattern": {},
+  "revision": "unsloth",
+  "target_modules": [
+    "gate_proj",
+    "up_proj",
+    "v_proj",
+    "k_proj",
+    "o_proj",
+    "q_proj",
+    "down_proj"
+  ],
+  "task_type": "CAUSAL_LM",
+  "use_dora": false,
+  "use_rslora": true
+}

bitcoinforum/3_training/mistral/lora_model/adapter_model.safetensors

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55cb3888c5e802aaa6e6ec87664ebb1e206e2e7c8716bfb3ebfe4d2ac998de3b
+size 167832240

bitcoinforum/3_training/old/bert/validation_samples.html

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d6e283d6519172f8a04b93a25941cd8fdc157f175a288307fb7a1a07f63bf11
+size 13942017

bitcoinforum/4_inference/inference.ipynb

@@ -0,0 +1,80 @@
+{
+ "cells": [
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "import pandas as pd\n",
+    "import numpy as np\n",
+    "from sglang import function, system, user, assistant, gen, set_default_backend, RuntimeEndpoint\n",
+    "import sglang as sgl\n",
+    "from torch import save\n",
+    "\n",
+    "# run this:\n",
+    "# python -m sglang.launch_server --model-path timothelaborie/extractor --port 30000 --mem-fraction-static 0.7 --enable-flashinfer\n",
+    "set_default_backend(RuntimeEndpoint(\"http://localhost:30000\"))\n",
+    "\n",
+    "@sgl.function\n",
+    "def text_qa(s, question):\n",
+    "    s += question\n",
+    "    s += sgl.gen(\"answer\", stop=None, max_tokens=400,temperature=0)\n",
+    "\n",
+    "# Step 1: Read the inputs.csv file and sample 50 entries\n",
+    "df_inputs = pd.read_csv('../2_train_set_creation/inputs.csv')\n",
+    "df_inputs = df_inputs\n",
+    "\n",
+    "# Function to split DataFrame into chunks\n",
+    "def split_dataframe(df, chunk_size):\n",
+    "    # Use np.array_split to handle uneven sizes automatically\n",
+    "    chunks = np.array_split(df, len(df) // chunk_size + (1 if len(df) % chunk_size else 0))\n",
+    "    return chunks\n",
+    "\n",
+    "# Split the DataFrame into chunks of size 5\n",
+    "df_chunks = split_dataframe(df_inputs, 2000)  # Adjust the chunk size as needed\n",
+    "\n",
+    "for thing in df_chunks:\n",
+    "    print(len(thing))"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "# Process each chunk\n",
+    "for i, df_chunk in enumerate(df_chunks):\n",
+    "    questions = df_chunk['input'].tolist()\n",
+    "    \n",
+    "    # Run batch inference for the current chunk\n",
+    "    states = text_qa.run_batch(\n",
+    "        [{\"question\": question} for question in questions],\n",
+    "        progress_bar=True\n",
+    "    )\n",
+    "    \n",
+    "    texts = []\n",
+    "    for state in states:\n",
+    "        for out in state.text_iter():\n",
+    "            texts.append(out)\n",
+    "    \n",
+    "    # Save the outputs of the current chunk to a separate file\n",
+    "    save(texts, f'../5_processing_extracted_data/outputs_chunk_{i+1}.pt')"
+   ]
+  }
+ ],
+ "metadata": {
+  "kernelspec": {
+   "display_name": "py310",
+   "language": "python",
+   "name": "python3"
+  },
+  "language_info": {
+   "name": "python",
+   "version": "3.10.13"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 2
+}

bitcoinforum/5_processing_extracted_data/3_add_efficiency.ipynb

@@ -0,0 +1,155 @@
+{
+ "cells": [
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "import pandas as pd\n",
+    "import os\n",
+    "import gzip\n",
+    "import pickle\n",
+    "import openai\n",
+    "import torch.nn.functional as F\n",
+    "import torch\n",
+    "import re\n",
+    "import copy\n",
+    "from tqdm import tqdm\n"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from hardware_mapping import map_hardware_to_table\n",
+    "hardware_instances = pd.read_csv('hardware_instances.csv') # columns: date,hardware\n",
+    "hardware_instances = hardware_instances.assign(hardware_mapped = hardware_instances[\"hardware\"].apply(map_hardware_to_table))"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "for index, row in hardware_instances.iterrows():\n",
+    "    if row[\"hardware_mapped\"] == \"bfl single 'sc'\" and row[\"date\"] < \"2013-04-01\":\n",
+    "        hardware_instances.at[index, \"hardware_mapped\"] = \"bitforce sha256 single\""
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "hardware_instances.head(10)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "len(hardware_instances)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "efficiency = pd.read_csv('../../hardwarelist/hardware_merged.csv') # columns: hardware_name,Mhash/J\n",
+    "efficiency = efficiency.rename(columns={\"hardware_name\":\"hardware_mapped\"})\n",
+    "\n",
+    "efficiency.head(2)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "joined = hardware_instances.merge(efficiency, on=\"hardware_mapped\", how=\"left\")\n",
+    "joined = joined.dropna(subset=[\"Mhash/J\"])\n",
+    "joined.head(4)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "print(len(joined))"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "table = joined[[\"date\",\"hardware_mapped\",\"Mhash/J\"]]\n",
+    "table = table.rename(columns={\"hardware_mapped\":\"hardware_name\"})\n",
+    "table[\"Mhash/J\"] = table[\"Mhash/J\"].astype(float).map(lambda x: x/1000000).map(lambda x: f\"{x:.10f}\")\n",
+    "table = table.rename(columns={\"Mhash/J\":\"TH/J\"})\n",
+    "table = table.sort_values([\"date\",\"hardware_name\"])\n",
+    "table = table.reset_index(drop=True)\n",
+    "table.head(8)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "import numpy as np\n",
+    "# all of these are manually verified to be random noobs trying to use a gpu during the asic era\n",
+    "for index, row in table.iterrows():\n",
+    "    eff = float(row[\"TH/J\"])\n",
+    "    if row[\"date\"] > \"2015-07-01\" and np.log10(eff*1000000) < 1.5:\n",
+    "        print(\"a\")\n",
+    "        # delete the row\n",
+    "        table = table.drop(index)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "table.to_csv(\"hardware_instances_with_efficiency.csv\", index=False)"
+   ]
+  }
+ ],
+ "metadata": {
+  "kernelspec": {
+   "display_name": "py310",
+   "language": "python",
+   "name": "python3"
+  },
+  "language_info": {
+   "codemirror_mode": {
+    "name": "ipython",
+    "version": 3
+   },
+   "file_extension": ".py",
+   "mimetype": "text/x-python",
+   "name": "python",
+   "nbconvert_exporter": "python",
+   "pygments_lexer": "ipython3",
+   "version": "3.10.13"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 2
+}

bitcoinforum/5_processing_extracted_data/4_visualizations.ipynb

@@ -0,0 +1,1083 @@
+{
+ "cells": [
+  {
+   "cell_type": "code",
+   "execution_count": 8,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "import pandas as pd\n",
+    "import numpy as np\n",
+    "import os\n",
+    "import gzip\n",
+    "import pickle\n",
+    "import re\n",
+    "import copy\n",
+    "from tqdm import tqdm\n",
+    "import time"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 9,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "hardware_instances = pd.read_csv('hardware_instances.csv') # columns: date,hardware\n",
+    "\n",
+    "# # keep only values near the end of 2021\n",
+    "# hardware_instances = hardware_instances[hardware_instances[\"date\"] > \"2020-07-01\"]\n",
+    "# hardware_instances = hardware_instances[hardware_instances[\"date\"] < \"2020-11-01\"]\n",
+    "\n",
+    "# unique_values = hardware_instances[\"hardware\"].value_counts()\n",
+    "# pairs = []\n",
+    "# for i in range(0, len(unique_values)):\n",
+    "#     # print(unique_values.index[i], unique_values[i])\n",
+    "#     pairs.append((unique_values.index[i], unique_values[i]))\n",
+    "\n",
+    "# pairs = sorted(pairs, key=lambda x: x[0], reverse=False)\n",
+    "# for pair in pairs:\n",
+    "#     # print(pair)\n",
+    "#     print(pair[0])\n",
+    "\n",
+    "pd.set_option('display.max_rows', None)\n",
+    "\n",
+    "# keep only values near the end of 2021\n",
+    "hardware_instances = hardware_instances[hardware_instances[\"date\"] > \"2020-07-01\"]\n",
+    "hardware_instances = hardware_instances[hardware_instances[\"date\"] < \"2020-12-01\"]\n",
+    "hardware_instances[[\"date\", \"hardware\"]].to_csv(\"hardware_instances_2020_all.csv\", index=False)\n",
+    "\n",
+    "from hardware_mapping import map_hardware_to_table\n",
+    "hardware_instances = hardware_instances.assign(hardware_mapped = hardware_instances[\"hardware\"].apply(map_hardware_to_table))\n",
+    "# hardware_instances"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 10,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "hardware\n",
+       "psu                      257\n",
+       "hashboard                132\n",
+       "fan                      109\n",
+       "fans                     101\n",
+       "miner                     92\n",
+       "miners                    83\n",
+       "hashboards                77\n",
+       "sd card                   68\n",
+       "asics                     68\n",
+       "hash boards               59\n",
+       "router                    56\n",
+       "asic                      51\n",
+       "hash board                51\n",
+       "power supply              51\n",
+       "antminer                  46\n",
+       "l3+                       36\n",
+       "antminers                 33\n",
+       "ethernet cable            31\n",
+       "apw3++                    27\n",
+       "raspberry pi              26\n",
+       "pc                        24\n",
+       "cables                    22\n",
+       "asic miners               21\n",
+       "heatsinks                 21\n",
+       "chips                     19\n",
+       "laptop                    19\n",
+       "s15                       18\n",
+       "pcb                       18\n",
+       "boards                    17\n",
+       "asic miner                17\n",
+       "psus                      16\n",
+       "chip                      16\n",
+       "temp sensor               16\n",
+       "cgminer                   16\n",
+       "cable                     16\n",
+       "ribbon cable              15\n",
+       "data cable                15\n",
+       "asic chips                15\n",
+       "avalon                    14\n",
+       "exhaust fan               14\n",
+       "hashing board             14\n",
+       "board                     13\n",
+       "pdu                       13\n",
+       "r4                        13\n",
+       "power supplies            13\n",
+       "gpu                       12\n",
+       "modem                     12\n",
+       "heat sinks                11\n",
+       "multimeter                11\n",
+       "bitmain psu               11\n",
+       "ribbon cables             11\n",
+       "gpus                      10\n",
+       "transformer               10\n",
+       "cpu                       10\n",
+       "avalon 851                10\n",
+       "hashing boards            10\n",
+       "antminer s15               9\n",
+       "t1                         9\n",
+       "heatsink                   8\n",
+       "asic boards                8\n",
+       "l3                         8\n",
+       "t15                        8\n",
+       "cards                      8\n",
+       "exhaust fans               7\n",
+       "power cables               7\n",
+       "d3                         7\n",
+       "capacitors                 7\n",
+       "voltmeter                  6\n",
+       "heat sink                  6\n",
+       "psu's                      6\n",
+       "r606                       6\n",
+       "power cable                6\n",
+       "solar panels               6\n",
+       "pic                        6\n",
+       "gpu rig                    6\n",
+       "network cable              6\n",
+       "cooling fan                6\n",
+       "gpu rigs                   6\n",
+       "bitmain apw3++             5\n",
+       "innosilicon                5\n",
+       "whatsminer                 5\n",
+       "test fixture               5\n",
+       "asic chip                  5\n",
+       "data cables                5\n",
+       "2pac                       5\n",
+       "bfgminer                   5\n",
+       "internet connection        5\n",
+       "intake fan                 5\n",
+       "avalon miners              5\n",
+       "auc3                       5\n",
+       "mining rig                 5\n",
+       "a851                       5\n",
+       "antminer t15               5\n",
+       "rpi3                       5\n",
+       "a10                        5\n",
+       "pdus                       5\n",
+       "micro sd card              5\n",
+       "firmware                   5\n",
+       "gekkoscience compac f      4\n",
+       "ac                         4\n",
+       "Name: count, dtype: int64"
+      ]
+     },
+     "execution_count": 10,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "hardware_instances = pd.read_csv('hardware_instances.csv') # columns: date,hardware\n",
+    "hardware_instances = hardware_instances[hardware_instances[\"date\"] > \"2018-01-01\"]\n",
+    "hardware_instances = hardware_instances.assign(hardware_mapped = hardware_instances[\"hardware\"].apply(map_hardware_to_table))\n",
+    "\n",
+    "# find most common unique values that were mapped to \"unknown\"\n",
+    "unique_values = hardware_instances[hardware_instances[\"hardware_mapped\"] == \"unknown\"][\"hardware\"].value_counts()\n",
+    "unique_values[:100]"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 11,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "hardware\n",
+       "control board       207\n",
+       "computer            194\n",
+       "controller          141\n",
+       "controller board     72\n",
+       "computers            52\n",
+       "controllers          18\n",
+       "control boards       16\n",
+       "vps                  15\n",
+       "antminer s17         14\n",
+       "4gb ram              13\n",
+       "Name: count, dtype: int64"
+      ]
+     },
+     "execution_count": 11,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "hardware_instances = pd.read_csv('hardware_instances.csv') # columns: date,hardware\n",
+    "hardware_instances = hardware_instances.assign(hardware_mapped = hardware_instances[\"hardware\"].apply(lambda x: str(x).strip()).apply(map_hardware_to_table))\n",
+    "\n",
+    "# print things that are \"not found\"\n",
+    "unique_values = hardware_instances[hardware_instances[\"hardware_mapped\"] == \"not found\"][\"hardware\"].value_counts()\n",
+    "unique_values[:10]"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 12,
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "2010-09-09 12:59:39 gtx460 5.630427875025024\n",
+      "User:\n",
+      "In the given Bitcoin forum thread, pay close attention to the language used when mentioning hardware pieces. Look for explicit statements indicating ownership or hypothetical discussions.\n",
+      "\n",
+      "```thread\n",
+      "Date: 2011-01\n",
+      "Topic: A slightly more open approach to bitcoin on the GPU\n",
+      "### Original post:\n",
+      "Honestly, I can't understand all the secrecy on the CUDA / OpenCL / Whatever GPU enabled versions of bitcoin. Sure, it's nice to take advantage of the extra edge you get if you want to build an efficient mining farm, but really, what's up with everyone on this regard?So, not really having the time to do it, I decided to take my first cup of CUDA (as all I have as hw to test is a macbook pro with a nvidia inside), and I'm attaching the initial version here. Yes, the source, for you to do as you please! Just remember the reason you got it in the first place, which was that someone didn't take it and hide! Anyways, it's *really* crude, has static compile instructions on the makefile, only for osx and with the cuda dev sdk in the default place, compiled for x86_64. But I'm sure you can quickly tweak it to compile for your system, though...The code that runs in the GPU is a 1:1 copy of the Cryptopp source, only slightly tweaked. There's a lot of room for improvement, I have some 20 hours total of working with CUDA so I don't have the faintest idea of what optimizations I could achieve, but at least in the memory layout there's a lot to do. I compared the resulting hashes with Cryptopp a<rest of post truncated>\n",
+      "\n",
+      "### Reply 1:\n",
+      "I have a feeling this is going to be very controversial.\n",
+      "\n",
+      "### Reply 2:\n",
+      "I think the big secret thing with cuda or opencl clients is that they give one person a decisive advantage over everyone else running only a cpu. Add that with the fact that most users don't know cuda programing (me included) makes for a situation where a cuda client can be valuable to the author... For example artforz has made his own cuda client that has not been released. It has been rumored that he makes up 25% of the generation power on the network. It give him a huge advantage and one I think artforz would like to keep. The down side to opening up a GPU client to the masses is that it completely kills CPU based generation unless you have a lot of cpus.... On my windows client I went from 4500Khash to 29000khashes.I will give this a try here in a few days or so on my 8800gtx hackintosh and see how it runs. What GPU does your mac have in it? I have no cuda or MAC OS X programming knowledge but, I have done some c in BSD and will have a go at the code to see what I might be able to do. Thank you for your efforts!\n",
+      "\n",
+      "### Reply 3:\n",
+      "I don't think that the bias should be towards the ones with better printers having more money The Bitcoins are a whole ecosystem, and mining for them is a small part of it, I guess. If lots of people start running GPU based mining, then the advantage that was owned by artforz and a handful of others will blend into more hands and pockets, thus making the mining less efficient for everyone. But mining is part statistics, part luck. I recently generated 3 blocks, running a machine that has been mining non stop for over a month. These 3 blocks are the only blocks it ever generated.Of course artforz would like to keep the advantage. Heck, I could use this to my advantage too, but I'd rather take the open source business approach and say \"here, take it, my treat\" but expect you to do the same for me and others (yes, trust is the base for this), and if you like it, I'll take whatever you feel fair. You want me to do something specific? need suport? Well, priority and special attention comes with a cost.I may never get as many coins as artforz created, but I hope I did my share on helping to spread them I've got a GT330M, really basic entry level thing. And you are most welcome.\n",
+      "\n",
+      "### Reply 4:\n",
+      "Nice! I've wanted to get into FPGA's too, and bitcoin seems very fitting, but unfortunately time doesn't stretch that much.BTW, the code I posted is slightly broken If the cuda thread generates a valid block it will die, for where it reads in main.cpp: if (DEBUG || hash <= hashTarget) { pblock->nNonce = keep+i; break; }it shoudl read if (DEBUG || hash <= hashTarget) { pblock->nNonce = tmp.block.nNonce = keep+i; break; }\n",
+      "\n",
+      "### Reply 5:\n",
+      "I am also working on a version of the BitCoin CUDA Client and will do all that I can to help this project. It will be opensourced as well, for the same reasons nelisky stated. I will test this first version out on my GTX 460(borrowing from a friend ) as soon as I can. Also, the pseudocode I've been writing up should be quite a bit faster than this currently is because it is incorporating FPGA styling and CUDA programming.I should have something up of my code up after the weekend.\n",
+      "\n",
+      "### Reply 6:\n",
+      "Nelisky, thank you for your work. I think that it's in the network's best interest that the fastest possible methods of generating blocks are freely available (see tcatm's 4-way SSE2).\n",
+      "\n",
+      "### Reply 7:\n",
+      "I have one question: Do you need to have a good CPU to take full advantage of your GPU when generating bitcoins? I ask because I want to create a bitcoin mining rig with just pure GPU power. I don't want to spen<rest of thread truncated>\n",
+      "\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "Reply with the hardware names, all in the same line, separated by commas. Then, on a new line, list \"True\" or \"False\" for each piece of hardware to indicate ownership status. True if the mention suggests concrete ownership by any user, and False if the hardware is discussed in a hypothetical or speculative way.\n",
+      "\n",
+      "Assistant:\n",
+      "Sure! Here is the requested output, with the correct ownership status for each piece of hardware:\n",
+      "Hardware names: macbook pro, 8800gtx, GT330M, GTX 460\n",
+      "Hardware ownership: True, True, True, True\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "2010-10-06 20:25:17 4350 5.539076098792776\n",
+      "User:\n",
+      "In the given Bitcoin forum thread, pay close attention to the language used when mentioning hardware pieces. Look for explicit statements indicating ownership or hypothetical discussions.\n",
+      "\n",
+      "```thread\n",
+      "Date: 2018-01\n",
+      "Topic: OpenCL miner for the masses\n",
+      "### Original post:\n",
+      "Amazing solution! Not good for the masses (it's better to integrate the miner in the binary) but great for experimentation and multiple machine mining. I'll be sure to have a go at this when I get a sec, kudos for putting this out.\n",
+      "\n",
+      "### Reply 1:\n",
+      "It is interesting to see how you've split mining and wallet+P2P into separate pieces. Nice and modular.I'll be interested to see feedback from people, if they actually generate coins from this.\n",
+      "\n",
+      "### Reply 2:\n",
+      "nelisky: Integrating CUDA/OpenCL seems to have portability issues. Also, my goal is actually to convince satoshi to patch the mainline. The patch must be crystal clear for this to happen.jgarzik: I tested this against vanilla client to be sure blocks are actually accepted. On ATI 4350 it makes ~5800 khash/s.Forgot to mention that original client generation could be used in parallel.\n",
+      "\n",
+      "### Reply 3:\n",
+      "Yes, that is one of my biggest concerns. I don't have enough exposure to assert in multiple platforms / hw. And I have failed to provide a simple click and use distributable, as of yet, but as interest increases and more developers tackle this I'm sure one of us will provide a clean implementation that is production quality for satoshi.\n",
+      "\n",
+      "### Reply 4:\n",
+      "davidonpda: you need1. Some OpenCL capable hardware and driver.2. python 2.6.63. PyOpenCL. This could be tricky, follow the official installation <truncated> -h or --help for some options, by default looks for bitcoin RPC at 127.0.0.1:8332Hope this helps\n",
+      "\n",
+      "### Reply 5:\n",
+      "Will opencl client works on ati hd3850?\n",
+      "\n",
+      "### Reply 6:\n",
+      "ATI HD3850 has no OpenCL support.4xxx and 5xxx have.\n",
+      "\n",
+      "### Reply 7:\n",
+      "Due to popular demand bitcoin PyOpenCL miner is available now at <link> are some minor fixes. Be sure to experiment with globalThreads to achieve better performance/dekstop lag ratio.\n",
+      "\n",
+      "### Reply 8:\n",
+      "Hmm, that's weird. Shouldn't the speed be much bigger, like 10-fold or 100-fold faster at least ?I mean there was this guy somewhere on the BTC forum who claimed that he's getting 983 Mhash/s (983 000 khash/sec) with just 3 radeons 5870 or something.\n",
+      "\n",
+      "### Reply 9:\n",
+      "Yeah, I'm struggling with how OpenCL compiles kernels and the impact of the work size on performance. It is quite counter intuitive coming from CUDA, as the unrolling of loops and functions actually makes performance worse, as the kernel needs more space. I don't have any numbers for that ATI, but the 4350 seems to be a LOT less performant than the 5870, so it might not be that low.Once I have hardware to test this for real, I'll compare my approach to this one, so we can learn from each other.\n",
+      "\n",
+      "### Reply 10:\n",
+      "There is information on wikipedia about the performance of various AMD/ATI and Nvidia chips.4350 is cited at 92 GFLOPS. 5870 has 2720 GFLOPS. tcatm has 3x5870s. Due to it's superior architecture 5870 is capable of more than just the difference in GFLOPS. For example I get 6 Mhash/s on 4350 and 137 Mhash/s on 5770 (ratio of 1/22) even if the ratio of GFLOPS for the relevant cards is 92 to 1360 (1/14).\n",
+      "\n",
+      "### Reply 11:\n",
+      "don't have an ATI card, but even after reading those performance-infos i still can't believe that <truncated> on a hd4350 makes sense to me, i get around 5-6.000 on a 8600gt, both listed around 100GFlops.my gtx260 gets ~40Mhash, 874GFlopsi'd expect a hd5870 makes at least 3times as much, cuz it's listed with 2700GFlops,which would result in around 400Mhash for 3 of those cards, that's what i would expect, so where's those extra 600Mhash coming from? it's superior architecture?if so, my next card will be ati again.\n",
+      "\n",
+      "### Reply 12:\n",
+      "There's a lot more than GFlops to this equation. Memory bandwidth, for one, will be very important.\n",
+      "\n",
+      "### Reply 13:\n",
+      "of course, but stilli'd like to know if that's a usual expectation on ati cards compared to nvidia,no single-hd5870-users around that want to share their hash-count?i'm gonna buy a new card sooner or later anyway and i don't mind if it says ati or nvidia on it,both will surely run my game/s.but if one of them is x times better crunching blocks and besides that, prolly cheaper too,i already know what my next favourite brand is.\n",
+      "\n",
+      "### Reply 14:\n",
+      "Sorry, just realized i broke it with latest changes, please update. (It won't submit to RPC properly)\n",
+      "\n",
+      "### Reply 15:\n",
+      "Added auto adjustment to keep desktop responsive. Also, doing hash rate calculation at user defined interval.\n",
+      "\n",
+      "### Reply 16:\n",
+      "i'm getting <link> when trying to run it\n",
+      "\n",
+      "### Reply 17:\n",
+      "Slightly improved kernel (~10%). Fixed a problem with rotate() and Nvidia OpenCL. I won't upload anymore to the forum, please use the repo.\n",
+      "\n",
+      "### Reply 18:\n",
+      "Do i need to use a special version of graphics drivers to get the OpenCL client working ?\n",
+      "\n",
+      "### Reply 19:\n",
+      "I'm in the same position. All I need is the patch compiled into the client and I should be ready to go :/\n",
+      "\n",
+      "### Reply 20:\n",
+      "Any chance of a 64 bit windows build?\n",
+      "\n",
+      "### Reply 21:\n",
+      "now it segfaults: <link>\n",
+      "\n",
+      "### Reply 22:\n",
+      "Sorry, forgot about that. You should install json-rpc. See at <link> u<rest of thread truncated>\n",
+      "\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "Reply with the hardware names, all in the same line, separated by commas. Then, on a new line, list \"True\" or \"False\" for each piece of hardware to indicate ownership status. True if the mention suggests concrete ownership by any user, and False if the hardware is discussed in a hypothetical or speculative way.\n",
+      "\n",
+      "Assistant:\n",
+      "Sure! Here is the requested output, with the correct ownership status for each piece of hardware:\n",
+      "Hardware names: ATI 4350, ATI HD3850, 4xxx, 5xxx, radeons 5870, 5770, 8600gt, gtx260, hd5870\n",
+      "Hardware ownership: True, False, False, False, True, True, True, True, False\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "2010-10-06 20:25:17 5770 6.287824115666779\n",
+      "User:\n",
+      "In the given Bitcoin forum thread, pay close attention to the language used when mentioning hardware pieces. Look for explicit statements indicating ownership or hypothetical discussions.\n",
+      "\n",
+      "```thread\n",
+      "Date: 2018-01\n",
+      "Topic: OpenCL miner for the masses\n",
+      "### Original post:\n",
+      "Amazing solution! Not good for the masses (it's better to integrate the miner in the binary) but great for experimentation and multiple machine mining. I'll be sure to have a go at this when I get a sec, kudos for putting this out.\n",
+      "\n",
+      "### Reply 1:\n",
+      "It is interesting to see how you've split mining and wallet+P2P into separate pieces. Nice and modular.I'll be interested to see feedback from people, if they actually generate coins from this.\n",
+      "\n",
+      "### Reply 2:\n",
+      "nelisky: Integrating CUDA/OpenCL seems to have portability issues. Also, my goal is actually to convince satoshi to patch the mainline. The patch must be crystal clear for this to happen.jgarzik: I tested this against vanilla client to be sure blocks are actually accepted. On ATI 4350 it makes ~5800 khash/s.Forgot to mention that original client generation could be used in parallel.\n",
+      "\n",
+      "### Reply 3:\n",
+      "Yes, that is one of my biggest concerns. I don't have enough exposure to assert in multiple platforms / hw. And I have failed to provide a simple click and use distributable, as of yet, but as interest increases and more developers tackle this I'm sure one of us will provide a clean implementation that is production quality for satoshi.\n",
+      "\n",
+      "### Reply 4:\n",
+      "davidonpda: you need1. Some OpenCL capable hardware and driver.2. python 2.6.63. PyOpenCL. This could be tricky, follow the official installation <truncated> -h or --help for some options, by default looks for bitcoin RPC at 127.0.0.1:8332Hope this helps\n",
+      "\n",
+      "### Reply 5:\n",
+      "Will opencl client works on ati hd3850?\n",
+      "\n",
+      "### Reply 6:\n",
+      "ATI HD3850 has no OpenCL support.4xxx and 5xxx have.\n",
+      "\n",
+      "### Reply 7:\n",
+      "Due to popular demand bitcoin PyOpenCL miner is available now at <link> are some minor fixes. Be sure to experiment with globalThreads to achieve better performance/dekstop lag ratio.\n",
+      "\n",
+      "### Reply 8:\n",
+      "Hmm, that's weird. Shouldn't the speed be much bigger, like 10-fold or 100-fold faster at least ?I mean there was this guy somewhere on the BTC forum who claimed that he's getting 983 Mhash/s (983 000 khash/sec) with just 3 radeons 5870 or something.\n",
+      "\n",
+      "### Reply 9:\n",
+      "Yeah, I'm struggling with how OpenCL compiles kernels and the impact of the work size on performance. It is quite counter intuitive coming from CUDA, as the unrolling of loops and functions actually makes performance worse, as the kernel needs more space. I don't have any numbers for that ATI, but the 4350 seems to be a LOT less performant than the 5870, so it might not be that low.Once I have hardware to test this for real, I'll compare my approach to this one, so we can learn from each other.\n",
+      "\n",
+      "### Reply 10:\n",
+      "There is information on wikipedia about the performance of various AMD/ATI and Nvidia chips.4350 is cited at 92 GFLOPS. 5870 has 2720 GFLOPS. tcatm has 3x5870s. Due to it's superior architecture 5870 is capable of more than just the difference in GFLOPS. For example I get 6 Mhash/s on 4350 and 137 Mhash/s on 5770 (ratio of 1/22) even if the ratio of GFLOPS for the relevant cards is 92 to 1360 (1/14).\n",
+      "\n",
+      "### Reply 11:\n",
+      "don't have an ATI card, but even after reading those performance-infos i still can't believe that <truncated> on a hd4350 makes sense to me, i get around 5-6.000 on a 8600gt, both listed around 100GFlops.my gtx260 gets ~40Mhash, 874GFlopsi'd expect a hd5870 makes at least 3times as much, cuz it's listed with 2700GFlops,which would result in around 400Mhash for 3 of those cards, that's what i would expect, so where's those extra 600Mhash coming from? it's superior architecture?if so, my next card will be ati again.\n",
+      "\n",
+      "### Reply 12:\n",
+      "There's a lot more than GFlops to this equation. Memory bandwidth, for one, will be very important.\n",
+      "\n",
+      "### Reply 13:\n",
+      "of course, but stilli'd like to know if that's a usual expectation on ati cards compared to nvidia,no single-hd5870-users around that want to share their hash-count?i'm gonna buy a new card sooner or later anyway and i don't mind if it says ati or nvidia on it,both will surely run my game/s.but if one of them is x times better crunching blocks and besides that, prolly cheaper too,i already know what my next favourite brand is.\n",
+      "\n",
+      "### Reply 14:\n",
+      "Sorry, just realized i broke it with latest changes, please update. (It won't submit to RPC properly)\n",
+      "\n",
+      "### Reply 15:\n",
+      "Added auto adjustment to keep desktop responsive. Also, doing hash rate calculation at user defined interval.\n",
+      "\n",
+      "### Reply 16:\n",
+      "i'm getting <link> when trying to run it\n",
+      "\n",
+      "### Reply 17:\n",
+      "Slightly improved kernel (~10%). Fixed a problem with rotate() and Nvidia OpenCL. I won't upload anymore to the forum, please use the repo.\n",
+      "\n",
+      "### Reply 18:\n",
+      "Do i need to use a special version of graphics drivers to get the OpenCL client working ?\n",
+      "\n",
+      "### Reply 19:\n",
+      "I'm in the same position. All I need is the patch compiled into the client and I should be ready to go :/\n",
+      "\n",
+      "### Reply 20:\n",
+      "Any chance of a 64 bit windows build?\n",
+      "\n",
+      "### Reply 21:\n",
+      "now it segfaults: <link>\n",
+      "\n",
+      "### Reply 22:\n",
+      "Sorry, forgot about that. You should install json-rpc. See at <link> u<rest of thread truncated>\n",
+      "\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "Reply with the hardware names, all in the same line, separated by commas. Then, on a new line, list \"True\" or \"False\" for each piece of hardware to indicate ownership status. True if the mention suggests concrete ownership by any user, and False if the hardware is discussed in a hypothetical or speculative way.\n",
+      "\n",
+      "Assistant:\n",
+      "Sure! Here is the requested output, with the correct ownership status for each piece of hardware:\n",
+      "Hardware names: ATI 4350, ATI HD3850, 4xxx, 5xxx, radeons 5870, 5770, 8600gt, gtx260, hd5870\n",
+      "Hardware ownership: True, False, False, False, True, True, True, True, False\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "2010-10-06 20:25:17 5870 6.2801228963023075\n",
+      "User:\n",
+      "In the given Bitcoin forum thread, pay close attention to the language used when mentioning hardware pieces. Look for explicit statements indicating ownership or hypothetical discussions.\n",
+      "\n",
+      "```thread\n",
+      "Date: 2018-01\n",
+      "Topic: OpenCL miner for the masses\n",
+      "### Original post:\n",
+      "Amazing solution! Not good for the masses (it's better to integrate the miner in the binary) but great for experimentation and multiple machine mining. I'll be sure to have a go at this when I get a sec, kudos for putting this out.\n",
+      "\n",
+      "### Reply 1:\n",
+      "It is interesting to see how you've split mining and wallet+P2P into separate pieces. Nice and modular.I'll be interested to see feedback from people, if they actually generate coins from this.\n",
+      "\n",
+      "### Reply 2:\n",
+      "nelisky: Integrating CUDA/OpenCL seems to have portability issues. Also, my goal is actually to convince satoshi to patch the mainline. The patch must be crystal clear for this to happen.jgarzik: I tested this against vanilla client to be sure blocks are actually accepted. On ATI 4350 it makes ~5800 khash/s.Forgot to mention that original client generation could be used in parallel.\n",
+      "\n",
+      "### Reply 3:\n",
+      "Yes, that is one of my biggest concerns. I don't have enough exposure to assert in multiple platforms / hw. And I have failed to provide a simple click and use distributable, as of yet, but as interest increases and more developers tackle this I'm sure one of us will provide a clean implementation that is production quality for satoshi.\n",
+      "\n",
+      "### Reply 4:\n",
+      "davidonpda: you need1. Some OpenCL capable hardware and driver.2. python 2.6.63. PyOpenCL. This could be tricky, follow the official installation <truncated> -h or --help for some options, by default looks for bitcoin RPC at 127.0.0.1:8332Hope this helps\n",
+      "\n",
+      "### Reply 5:\n",
+      "Will opencl client works on ati hd3850?\n",
+      "\n",
+      "### Reply 6:\n",
+      "ATI HD3850 has no OpenCL support.4xxx and 5xxx have.\n",
+      "\n",
+      "### Reply 7:\n",
+      "Due to popular demand bitcoin PyOpenCL miner is available now at <link> are some minor fixes. Be sure to experiment with globalThreads to achieve better performance/dekstop lag ratio.\n",
+      "\n",
+      "### Reply 8:\n",
+      "Hmm, that's weird. Shouldn't the speed be much bigger, like 10-fold or 100-fold faster at least ?I mean there was this guy somewhere on the BTC forum who claimed that he's getting 983 Mhash/s (983 000 khash/sec) with just 3 radeons 5870 or something.\n",
+      "\n",
+      "### Reply 9:\n",
+      "Yeah, I'm struggling with how OpenCL compiles kernels and the impact of the work size on performance. It is quite counter intuitive coming from CUDA, as the unrolling of loops and functions actually makes performance worse, as the kernel needs more space. I don't have any numbers for that ATI, but the 4350 seems to be a LOT less performant than the 5870, so it might not be that low.Once I have hardware to test this for real, I'll compare my approach to this one, so we can learn from each other.\n",
+      "\n",
+      "### Reply 10:\n",
+      "There is information on wikipedia about the performance of various AMD/ATI and Nvidia chips.4350 is cited at 92 GFLOPS. 5870 has 2720 GFLOPS. tcatm has 3x5870s. Due to it's superior architecture 5870 is capable of more than just the difference in GFLOPS. For example I get 6 Mhash/s on 4350 and 137 Mhash/s on 5770 (ratio of 1/22) even if the ratio of GFLOPS for the relevant cards is 92 to 1360 (1/14).\n",
+      "\n",
+      "### Reply 11:\n",
+      "don't have an ATI card, but even after reading those performance-infos i still can't believe that <truncated> on a hd4350 makes sense to me, i get around 5-6.000 on a 8600gt, both listed around 100GFlops.my gtx260 gets ~40Mhash, 874GFlopsi'd expect a hd5870 makes at least 3times as much, cuz it's listed with 2700GFlops,which would result in around 400Mhash for 3 of those cards, that's what i would expect, so where's those extra 600Mhash coming from? it's superior architecture?if so, my next card will be ati again.\n",
+      "\n",
+      "### Reply 12:\n",
+      "There's a lot more than GFlops to this equation. Memory bandwidth, for one, will be very important.\n",
+      "\n",
+      "### Reply 13:\n",
+      "of course, but stilli'd like to know if that's a usual expectation on ati cards compared to nvidia,no single-hd5870-users around that want to share their hash-count?i'm gonna buy a new card sooner or later anyway and i don't mind if it says ati or nvidia on it,both will surely run my game/s.but if one of them is x times better crunching blocks and besides that, prolly cheaper too,i already know what my next favourite brand is.\n",
+      "\n",
+      "### Reply 14:\n",
+      "Sorry, just realized i broke it with latest changes, please update. (It won't submit to RPC properly)\n",
+      "\n",
+      "### Reply 15:\n",
+      "Added auto adjustment to keep desktop responsive. Also, doing hash rate calculation at user defined interval.\n",
+      "\n",
+      "### Reply 16:\n",
+      "i'm getting <link> when trying to run it\n",
+      "\n",
+      "### Reply 17:\n",
+      "Slightly improved kernel (~10%). Fixed a problem with rotate() and Nvidia OpenCL. I won't upload anymore to the forum, please use the repo.\n",
+      "\n",
+      "### Reply 18:\n",
+      "Do i need to use a special version of graphics drivers to get the OpenCL client working ?\n",
+      "\n",
+      "### Reply 19:\n",
+      "I'm in the same position. All I need is the patch compiled into the client and I should be ready to go :/\n",
+      "\n",
+      "### Reply 20:\n",
+      "Any chance of a 64 bit windows build?\n",
+      "\n",
+      "### Reply 21:\n",
+      "now it segfaults: <link>\n",
+      "\n",
+      "### Reply 22:\n",
+      "Sorry, forgot about that. You should install json-rpc. See at <link> u<rest of thread truncated>\n",
+      "\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "Reply with the hardware names, all in the same line, separated by commas. Then, on a new line, list \"True\" or \"False\" for each piece of hardware to indicate ownership status. True if the mention suggests concrete ownership by any user, and False if the hardware is discussed in a hypothetical or speculative way.\n",
+      "\n",
+      "Assistant:\n",
+      "Sure! Here is the requested output, with the correct ownership status for each piece of hardware:\n",
+      "Hardware names: ATI 4350, ATI HD3850, 4xxx, 5xxx, radeons 5870, 5770, 8600gt, gtx260, hd5870\n",
+      "Hardware ownership: True, False, False, False, True, True, True, True, False\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "2010-10-06 20:25:17 gtx260 5.3222192947339195\n",
+      "User:\n",
+      "In the given Bitcoin forum thread, pay close attention to the language used when mentioning hardware pieces. Look for explicit statements indicating ownership or hypothetical discussions.\n",
+      "\n",
+      "```thread\n",
+      "Date: 2018-01\n",
+      "Topic: OpenCL miner for the masses\n",
+      "### Original post:\n",
+      "Amazing solution! Not good for the masses (it's better to integrate the miner in the binary) but great for experimentation and multiple machine mining. I'll be sure to have a go at this when I get a sec, kudos for putting this out.\n",
+      "\n",
+      "### Reply 1:\n",
+      "It is interesting to see how you've split mining and wallet+P2P into separate pieces. Nice and modular.I'll be interested to see feedback from people, if they actually generate coins from this.\n",
+      "\n",
+      "### Reply 2:\n",
+      "nelisky: Integrating CUDA/OpenCL seems to have portability issues. Also, my goal is actually to convince satoshi to patch the mainline. The patch must be crystal clear for this to happen.jgarzik: I tested this against vanilla client to be sure blocks are actually accepted. On ATI 4350 it makes ~5800 khash/s.Forgot to mention that original client generation could be used in parallel.\n",
+      "\n",
+      "### Reply 3:\n",
+      "Yes, that is one of my biggest concerns. I don't have enough exposure to assert in multiple platforms / hw. And I have failed to provide a simple click and use distributable, as of yet, but as interest increases and more developers tackle this I'm sure one of us will provide a clean implementation that is production quality for satoshi.\n",
+      "\n",
+      "### Reply 4:\n",
+      "davidonpda: you need1. Some OpenCL capable hardware and driver.2. python 2.6.63. PyOpenCL. This could be tricky, follow the official installation <truncated> -h or --help for some options, by default looks for bitcoin RPC at 127.0.0.1:8332Hope this helps\n",
+      "\n",
+      "### Reply 5:\n",
+      "Will opencl client works on ati hd3850?\n",
+      "\n",
+      "### Reply 6:\n",
+      "ATI HD3850 has no OpenCL support.4xxx and 5xxx have.\n",
+      "\n",
+      "### Reply 7:\n",
+      "Due to popular demand bitcoin PyOpenCL miner is available now at <link> are some minor fixes. Be sure to experiment with globalThreads to achieve better performance/dekstop lag ratio.\n",
+      "\n",
+      "### Reply 8:\n",
+      "Hmm, that's weird. Shouldn't the speed be much bigger, like 10-fold or 100-fold faster at least ?I mean there was this guy somewhere on the BTC forum who claimed that he's getting 983 Mhash/s (983 000 khash/sec) with just 3 radeons 5870 or something.\n",
+      "\n",
+      "### Reply 9:\n",
+      "Yeah, I'm struggling with how OpenCL compiles kernels and the impact of the work size on performance. It is quite counter intuitive coming from CUDA, as the unrolling of loops and functions actually makes performance worse, as the kernel needs more space. I don't have any numbers for that ATI, but the 4350 seems to be a LOT less performant than the 5870, so it might not be that low.Once I have hardware to test this for real, I'll compare my approach to this one, so we can learn from each other.\n",
+      "\n",
+      "### Reply 10:\n",
+      "There is information on wikipedia about the performance of various AMD/ATI and Nvidia chips.4350 is cited at 92 GFLOPS. 5870 has 2720 GFLOPS. tcatm has 3x5870s. Due to it's superior architecture 5870 is capable of more than just the difference in GFLOPS. For example I get 6 Mhash/s on 4350 and 137 Mhash/s on 5770 (ratio of 1/22) even if the ratio of GFLOPS for the relevant cards is 92 to 1360 (1/14).\n",
+      "\n",
+      "### Reply 11:\n",
+      "don't have an ATI card, but even after reading those performance-infos i still can't believe that <truncated> on a hd4350 makes sense to me, i get around 5-6.000 on a 8600gt, both listed around 100GFlops.my gtx260 gets ~40Mhash, 874GFlopsi'd expect a hd5870 makes at least 3times as much, cuz it's listed with 2700GFlops,which would result in around 400Mhash for 3 of those cards, that's what i would expect, so where's those extra 600Mhash coming from? it's superior architecture?if so, my next card will be ati again.\n",
+      "\n",
+      "### Reply 12:\n",
+      "There's a lot more than GFlops to this equation. Memory bandwidth, for one, will be very important.\n",
+      "\n",
+      "### Reply 13:\n",
+      "of course, but stilli'd like to know if that's a usual expectation on ati cards compared to nvidia,no single-hd5870-users around that want to share their hash-count?i'm gonna buy a new card sooner or later anyway and i don't mind if it says ati or nvidia on it,both will surely run my game/s.but if one of them is x times better crunching blocks and besides that, prolly cheaper too,i already know what my next favourite brand is.\n",
+      "\n",
+      "### Reply 14:\n",
+      "Sorry, just realized i broke it with latest changes, please update. (It won't submit to RPC properly)\n",
+      "\n",
+      "### Reply 15:\n",
+      "Added auto adjustment to keep desktop responsive. Also, doing hash rate calculation at user defined interval.\n",
+      "\n",
+      "### Reply 16:\n",
+      "i'm getting <link> when trying to run it\n",
+      "\n",
+      "### Reply 17:\n",
+      "Slightly improved kernel (~10%). Fixed a problem with rotate() and Nvidia OpenCL. I won't upload anymore to the forum, please use the repo.\n",
+      "\n",
+      "### Reply 18:\n",
+      "Do i need to use a special version of graphics drivers to get the OpenCL client working ?\n",
+      "\n",
+      "### Reply 19:\n",
+      "I'm in the same position. All I need is the patch compiled into the client and I should be ready to go :/\n",
+      "\n",
+      "### Reply 20:\n",
+      "Any chance of a 64 bit windows build?\n",
+      "\n",
+      "### Reply 21:\n",
+      "now it segfaults: <link>\n",
+      "\n",
+      "### Reply 22:\n",
+      "Sorry, forgot about that. You should install json-rpc. See at <link> u<rest of thread truncated>\n",
+      "\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "Reply with the hardware names, all in the same line, separated by commas. Then, on a new line, list \"True\" or \"False\" for each piece of hardware to indicate ownership status. True if the mention suggests concrete ownership by any user, and False if the hardware is discussed in a hypothetical or speculative way.\n",
+      "\n",
+      "Assistant:\n",
+      "Sure! Here is the requested output, with the correct ownership status for each piece of hardware:\n",
+      "Hardware names: ATI 4350, ATI HD3850, 4xxx, 5xxx, radeons 5870, 5770, 8600gt, gtx260, hd5870\n",
+      "Hardware ownership: True, False, False, False, True, True, True, True, False\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "2010-12-23 21:26:33 8800gt 5.426836453803508\n",
+      "User:\n",
+      "In the given Bitcoin forum thread, pay close attention to the language used when mentioning hardware pieces. Look for explicit statements indicating ownership or hypothetical discussions.\n",
+      "\n",
+      "```thread\n",
+      "Date: 2014-02\n",
+      "Topic: python OpenCL bitcoin miner\n",
+      "### Original post:\n",
+      "Moved actual search to separate thread to avoid IO overhead. It wasn't a problem when used with local bitcoin client, but become a problem with slush's mining pool.Davout, check if crossfire is switched off. Or try with lower clock. Xelister reported on #bitcoin-dev similar issues with 5970 and Diablo's miner.\n",
+      "\n",
+      "### Reply 1:\n",
+      "<truncated> --helpTraceback (most recent call last): File \"poclbm.py\", line 3, in <module> File <truncated> line 3, in <module> File \"pyopencl\\_cl.pyc\", line 12, in <module> File \"pyopencl\\_cl.pyc\", line 10, in __loadImportError: DLL load failed: The specified procedure could not be found.Maybe missing a dll?\n",
+      "\n",
+      "### Reply 2:\n",
+      "Elanthius, in previous version I forgot to remove OpenCL.dll from the py2exe distribution. It is not there in current version and you should check that you have Stream SDK 2.2 installed and proper version of OpenCL.dll loadable by miner. Be sure there aren't multiple versions - for example if an nvidia one from previous drivers load first it could give you this error.\n",
+      "\n",
+      "### Reply 3:\n",
+      "Hmm, I have an nvidia card that is OpenCL capable. I tried copying over the OpenCL.dll from system32 but that still crashes. In the end I just copied the dll out of the previous version and that seems fine. I'm getting 20Mh/s on a GeForce 8800 so its definitely using OpenCL appropriately.\n",
+      "\n",
+      "### Reply 4:\n",
+      "I'm getting these too, didn't get them at all before git pulling latest miner version...\n",
+      "\n",
+      "### Reply 5:\n",
+      "Your limit is already over 20 parallel jobs (increased before days). I hope m0mchil's miner is not so hungry .\n",
+      "\n",
+      "### Reply 6:\n",
+      "I was getting the very same messages even before trying pooled mining\n",
+      "\n",
+      "### Reply 7:\n",
+      "its not only the pool, its the same on local getwork-servers, aka mainline-clients.\n",
+      "\n",
+      "### Reply 8:\n",
+      "Oh! Good to know! I didn't realized that. So it should not be related to 'max_jobs' solution in pool.\n",
+      "\n",
+      "### Reply 9:\n",
+      "i guess it is, should have mentioned that earlier.i tried -testnet, cuz i didnt want to wait a day or 2 to let it happen and it's the exact same invalid-floods as soon as the first hash is found (the first one even makes it to the wallet sometimes).\n",
+      "\n",
+      "### Reply 10:\n",
+      "Hello,I downloaded the miner and followed the instructions from the OP. I feel as though I have it set up correctly. When I try to run the miner a new CMD window flashes on my screen too rapidly to read anything, or even see if it says anything. I don't get any errors in the CMD window I'm using to launch the miner but I really don't feel like it's working. I'm also not sure how I'm able to tell if it is working.Any assistance would be appreciated.Thanks.\n",
+      "\n",
+      "### Reply 11:\n",
+      "Looking at the opencl kernel, can the belowOrEquals function not avoid the endian related comparison of seperate bytes, instead moving the switch into the python code when creating targetH and targetG. Then less branches in kernel and perhaps better stream usage?\n",
+      "\n",
+      "### Reply 12:\n",
+      "Finally got my hands on a GTX 275. Reporting stats:CPU: Core2 Extreme QX6700, 2.67 GHzOS: Gentoo Linux 2.6.34Client: Classic 0.3.19 (local build)khash/sec: ~5000GPU: Nvidia GeForce GTX 275Miner: m0mchil's OpenCL <truncated> -r 3 -f 10 -w 256khash/sec: ~49500I have an old motherboard (PCIe 1.0a, etc.) which has a lot of strain on it, so your results with the same CPU or GPU could be better. It seems I should've gone for an ATI radeon though.\n",
+      "\n",
+      "### Reply 13:\n",
+      "Does anyone know what the optimal settings are for a GTX 580?Thanks,DiSTANT\n",
+      "\n",
+      "### Reply 14:\n",
+      "Yeah, I guess the problem lies with Nvidia's OpenCL drivers which are less than optimal. If there was a CUDA miner available, Nvidia users would probably get more comparable results.. So, who's up to the task?\n",
+      "\n",
+      "### Reply 15:\n",
+      "Nvidia hardware sucks for mining at the hardware level. CUDA won't help.\n",
+      "\n",
+      "### Reply 16:\n",
+      "Sell it and buy an ATI card.\n",
+      "\n",
+      "### Reply 17:\n",
+      "Hi,poclbm finally told me that a block was accepted (after 3 days with <truncated> getinfo shows no balance of +50 until now, though.I read somewhere that this might take very long because the new block is checked very intensively. Couldn't find the text again, though.So can you tell me that I can calm down or went something wrong and the 3 days of work are gone for somebody else?\n",
+      "\n",
+      "### Reply 18:\n",
+      "you have to wait 120 blocks before the coins mature,otherwise you might spend coins that were generated on a chain fork\n",
+      "\n",
+      "### Reply 19:\n",
+      "Thanks a lot for quick reply, davout!Is it possible to see this on blockexplorer.com? What do I have to look for?\n",
+      "\n",
+      "### Reply 20:\n",
+      "You can see the block on BBE as soon as it is generated (1-minute delay). If it shows up there, it probably won't be reversed, though from time to time this does happen. It won't appear in your balance until it is 120 blocks deep.The block hash is printed to debug.log by Bitcoin when you find a block. poclbm itself might also do <truncated> found hash: <truncated> can use the hash to search BBE for the block.\n",
+      "\n",
+      "### Reply 21:\n",
+      "Hi, are there any references you can recommend a<rest of thread truncated>\n",
+      "\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "Reply with the hardware names, all in the same line, separated by commas. Then, on a new line, list \"True\" or \"False\" for each piece of hardware to indicate ownership status. True if the mention suggests concrete ownership by any user, and False if the hardware is discussed in a hypothetical or speculative way.\n",
+      "\n",
+      "Assistant:\n",
+      "Sure! Here is the requested output, with the correct ownership status for each piece of hardware:\n",
+      "Hardware names: 5970, Diablo's miner, nvidia card, GeForce 8800, GTX 275, Core2 Extreme QX6700, GTX 580, ATI radeon, ATI card\n",
+      "Hardware ownership: False, False, True, True, True, True, False, False, False\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "2010-12-23 21:26:33 gtx275 5.365487984890899\n",
+      "User:\n",
+      "In the given Bitcoin forum thread, pay close attention to the language used when mentioning hardware pieces. Look for explicit statements indicating ownership or hypothetical discussions.\n",
+      "\n",
+      "```thread\n",
+      "Date: 2014-02\n",
+      "Topic: python OpenCL bitcoin miner\n",
+      "### Original post:\n",
+      "Moved actual search to separate thread to avoid IO overhead. It wasn't a problem when used with local bitcoin client, but become a problem with slush's mining pool.Davout, check if crossfire is switched off. Or try with lower clock. Xelister reported on #bitcoin-dev similar issues with 5970 and Diablo's miner.\n",
+      "\n",
+      "### Reply 1:\n",
+      "<truncated> --helpTraceback (most recent call last): File \"poclbm.py\", line 3, in <module> File <truncated> line 3, in <module> File \"pyopencl\\_cl.pyc\", line 12, in <module> File \"pyopencl\\_cl.pyc\", line 10, in __loadImportError: DLL load failed: The specified procedure could not be found.Maybe missing a dll?\n",
+      "\n",
+      "### Reply 2:\n",
+      "Elanthius, in previous version I forgot to remove OpenCL.dll from the py2exe distribution. It is not there in current version and you should check that you have Stream SDK 2.2 installed and proper version of OpenCL.dll loadable by miner. Be sure there aren't multiple versions - for example if an nvidia one from previous drivers load first it could give you this error.\n",
+      "\n",
+      "### Reply 3:\n",
+      "Hmm, I have an nvidia card that is OpenCL capable. I tried copying over the OpenCL.dll from system32 but that still crashes. In the end I just copied the dll out of the previous version and that seems fine. I'm getting 20Mh/s on a GeForce 8800 so its definitely using OpenCL appropriately.\n",
+      "\n",
+      "### Reply 4:\n",
+      "I'm getting these too, didn't get them at all before git pulling latest miner version...\n",
+      "\n",
+      "### Reply 5:\n",
+      "Your limit is already over 20 parallel jobs (increased before days). I hope m0mchil's miner is not so hungry .\n",
+      "\n",
+      "### Reply 6:\n",
+      "I was getting the very same messages even before trying pooled mining\n",
+      "\n",
+      "### Reply 7:\n",
+      "its not only the pool, its the same on local getwork-servers, aka mainline-clients.\n",
+      "\n",
+      "### Reply 8:\n",
+      "Oh! Good to know! I didn't realized that. So it should not be related to 'max_jobs' solution in pool.\n",
+      "\n",
+      "### Reply 9:\n",
+      "i guess it is, should have mentioned that earlier.i tried -testnet, cuz i didnt want to wait a day or 2 to let it happen and it's the exact same invalid-floods as soon as the first hash is found (the first one even makes it to the wallet sometimes).\n",
+      "\n",
+      "### Reply 10:\n",
+      "Hello,I downloaded the miner and followed the instructions from the OP. I feel as though I have it set up correctly. When I try to run the miner a new CMD window flashes on my screen too rapidly to read anything, or even see if it says anything. I don't get any errors in the CMD window I'm using to launch the miner but I really don't feel like it's working. I'm also not sure how I'm able to tell if it is working.Any assistance would be appreciated.Thanks.\n",
+      "\n",
+      "### Reply 11:\n",
+      "Looking at the opencl kernel, can the belowOrEquals function not avoid the endian related comparison of seperate bytes, instead moving the switch into the python code when creating targetH and targetG. Then less branches in kernel and perhaps better stream usage?\n",
+      "\n",
+      "### Reply 12:\n",
+      "Finally got my hands on a GTX 275. Reporting stats:CPU: Core2 Extreme QX6700, 2.67 GHzOS: Gentoo Linux 2.6.34Client: Classic 0.3.19 (local build)khash/sec: ~5000GPU: Nvidia GeForce GTX 275Miner: m0mchil's OpenCL <truncated> -r 3 -f 10 -w 256khash/sec: ~49500I have an old motherboard (PCIe 1.0a, etc.) which has a lot of strain on it, so your results with the same CPU or GPU could be better. It seems I should've gone for an ATI radeon though.\n",
+      "\n",
+      "### Reply 13:\n",
+      "Does anyone know what the optimal settings are for a GTX 580?Thanks,DiSTANT\n",
+      "\n",
+      "### Reply 14:\n",
+      "Yeah, I guess the problem lies with Nvidia's OpenCL drivers which are less than optimal. If there was a CUDA miner available, Nvidia users would probably get more comparable results.. So, who's up to the task?\n",
+      "\n",
+      "### Reply 15:\n",
+      "Nvidia hardware sucks for mining at the hardware level. CUDA won't help.\n",
+      "\n",
+      "### Reply 16:\n",
+      "Sell it and buy an ATI card.\n",
+      "\n",
+      "### Reply 17:\n",
+      "Hi,poclbm finally told me that a block was accepted (after 3 days with <truncated> getinfo shows no balance of +50 until now, though.I read somewhere that this might take very long because the new block is checked very intensively. Couldn't find the text again, though.So can you tell me that I can calm down or went something wrong and the 3 days of work are gone for somebody else?\n",
+      "\n",
+      "### Reply 18:\n",
+      "you have to wait 120 blocks before the coins mature,otherwise you might spend coins that were generated on a chain fork\n",
+      "\n",
+      "### Reply 19:\n",
+      "Thanks a lot for quick reply, davout!Is it possible to see this on blockexplorer.com? What do I have to look for?\n",
+      "\n",
+      "### Reply 20:\n",
+      "You can see the block on BBE as soon as it is generated (1-minute delay). If it shows up there, it probably won't be reversed, though from time to time this does happen. It won't appear in your balance until it is 120 blocks deep.The block hash is printed to debug.log by Bitcoin when you find a block. poclbm itself might also do <truncated> found hash: <truncated> can use the hash to search BBE for the block.\n",
+      "\n",
+      "### Reply 21:\n",
+      "Hi, are there any references you can recommend a<rest of thread truncated>\n",
+      "\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "Reply with the hardware names, all in the same line, separated by commas. Then, on a new line, list \"True\" or \"False\" for each piece of hardware to indicate ownership status. True if the mention suggests concrete ownership by any user, and False if the hardware is discussed in a hypothetical or speculative way.\n",
+      "\n",
+      "Assistant:\n",
+      "Sure! Here is the requested output, with the correct ownership status for each piece of hardware:\n",
+      "Hardware names: 5970, Diablo's miner, nvidia card, GeForce 8800, GTX 275, Core2 Extreme QX6700, GTX 580, ATI radeon, ATI card\n",
+      "Hardware ownership: False, False, True, True, True, True, False, False, False\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n"
+     ]
+    }
+   ],
+   "source": [
+    "instances = pd.read_csv('hardware_instances_inc_threads.csv') # columns: date,thread\n",
+    "\n",
+    "\n",
+    "efficiency = pd.read_csv('hardware_instances_with_efficiency.csv') # columns: date,hardware_name,TH/J\n",
+    "efficiency[\"ln_efficiency\"] = np.log10(efficiency[\"TH/J\"]*1000000000000)\n",
+    "# efficiency = efficiency[efficiency[\"date\"] > \"2013-01-01\"]\n",
+    "# efficiency = efficiency[efficiency[\"date\"] > \"2015-07-01\"]\n",
+    "efficiency = efficiency[efficiency[\"ln_efficiency\"] < 7.5]\n",
+    "\n",
+    "\n",
+    "\n",
+    "i = 0\n",
+    "for index, row in efficiency.iterrows():\n",
+    "    print(row[\"date\"], row[\"hardware_name\"], row[\"ln_efficiency\"])\n",
+    "    filtered = instances[instances[\"date\"] == row[\"date\"]]\n",
+    "    print(filtered.iloc[0][\"thread\"])\n",
+    "    print(\"\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\")\n",
+    "    if i > 5:\n",
+    "        break\n",
+    "    i += 1"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 16,
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "2011-07-06 16:49:46 ion\n",
+      "User:\n",
+      "In the given Bitcoin forum thread, pay close attention to the language used when mentioning hardware pieces. Look for explicit statements indicating ownership or hypothetical discussions.\n",
+      "\n",
+      "```thread\n",
+      "Date: 2011-07\n",
+      "Topic: Multipool - the pool mining pool (with source code)\n",
+      "### Original post:\n",
+      "Installing all prerequisite modules without being <truncated> a new user account, here \"teensy\".* gcc needs to be installed* Multipool.pl (to test it works)First, we fetch \"cpanm\", best practice Perl module <truncated> curl -L <link> > cpanm <truncated> chmod +x cpanmWe will then install the prerequisites under the current directory's \"lib\" subdirectory. This is done via the parameter \"-l lib\" to <truncated> ./cpanm -l lib <truncated> Working on <truncated> <link> ... OKConfiguring JSON-RPC-0.96 ... OKBuilding and testing JSON-RPC-0.96 ... OKSuccessfully installed JSON-RPC-0.961 distribution <truncated> is a signed package, we need to make sure we have the right signature or it will hang and cause <truncated> gpg --recv-keys --keyserver <truncated> 6A2A7D39gpg: directory <truncated> createdgpg: new configuration file <truncated> createdgpg: WARNING: options in <truncated> are not yet active during this rungpg: keyring <truncated> createdgpg: keyring <truncated> createdgpg: requesting key 6A2A7D39 from hkp server <truncated> <truncated> trustdb createdgpg: key 6A2A7D39: public key \"Toby Inkster <truncated> importedgpg: no ultimately trusted keys foundgpg: Total number processed: 1gp<rest of post truncated>\n",
+      "\n",
+      "### Reply 1:\n",
+      "Nice work, myself! I'm a little more confident of setting up a local multipool now. Cheers!\n",
+      "\n",
+      "### Reply 2:\n",
+      "Incredible post and guide. Very useful to me.If I wanted to set up a server to run multipool on, and have friends connect to it, would I need a powerful computer to run the MultiPool server on? Because I have a NetTop that I can use that has a duel core processor in it with Nvidia ION video card. It's not all powerful, but it runs things just fine. It's my media server for the house.Also, couldn't I just set up a DNS using no-ip to have people connect to it through their mining application? Is there a benefit to me or other people to have people connect to the multipool together?Is there any more info or tips someone can give me for doing anything else?\n",
+      "\n",
+      "### Reply 3:\n",
+      "Worse, I'm seeing over half the shares submitted to bitcoins.lc rejected.\n",
+      "\n",
+      "### Reply 4:\n",
+      "If you want stats, use btc-poolwatch.com Works with any pool that provides an API, all your results in one place. Make a donation to rearwheels if the site helps you.\n",
+      "\n",
+      "### Reply 5:\n",
+      "any idea where the bitcoind files are on deb? Do I need to get the username and password from bitcoind?Thanks man.\n",
+      "\n",
+      "### Reply 6:\n",
+      "You need to create a file named bitcoind.conf *in the same directory as Multipool.pl*, containing *in one single line*, *separated by a space* the username and password you need to use to connect to the local bitcoind instance.Much of the confusion comes from Multipool.pl naming that config file the same name as the one used by bitcoind Your \"real\" bitcoind.conf (the one that controls which username and password bitcoind is to accept) is usually found in <truncated> and the wiki explains how to put info <truncated> ls Multipool.pl #we are in the same directory where Multipool.pl isMultipool.pl$ cat <truncated> <truncated> cat <truncated> mypassword$ as you see above, the \"local\" bitcoind.conf needs to contain the username and password from the \"real\" bitcoind.conf, separated by a space.\n",
+      "\n",
+      "### Reply 7:\n",
+      "Does multipool cashout automatically from the pools it mines from?\n",
+      "\n",
+      "### Reply 8:\n",
+      "No i meant, i set multipool to mine from pool 1,2,3,4,5.How do i get my BTC from the 5 pools to my wallet?This part. Is it automatic?\n",
+      "\n",
+      "### Reply 9:\n",
+      "Thanks for the info and examples - appreciate it\n",
+      "\n",
+      "### Reply 10:\n",
+      "If you are using Multipool.pl alone, you don't need to: just log in on each of the five pools' websites, and have them pay the balance to your wallet.That part is only necessary if you run Multipool.pl as a service for other users, too.\n",
+      "\n",
+      "### Reply 11:\n",
+      "Nope, I see this directly at bitcoins.lc web site stats page. Also see them rejected in multipool's log. All the other pools accept most of the shares. There were so many of them, and bitcoins.lc was being chosen often enough, that I had to remove bitcoins.lc entirely or risk losing a lot of hashing power. I have not yet gotten into the spaghetti code to see what, if anything, might be going on...\n",
+      "\n",
+      "### Reply 12:\n",
+      "I had similar issues; they stem from the fact that Multipool.pl uses the \"local\" bitcoind to know when there is a new block.IIRC, it also does not completely clear up the queue on a new block received (as threads have to pick that up).As such, the following scenarios may develop:- the miner receives the long poll, and the miner does _not_ clear its queue / request more work => nothing to do with Multipool.pl but I think phoenix did that -- you can verify this by seeing if the rejects are clustered after a long poll.- your bitcoind sees the block & notifies the miners at the same time as all the pools you're getting work from also see it; all is well as the new work fetched by Multipool.pl is pristine and ne<rest of thread truncated>\n",
+      "\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "Reply with the hardware names, all in the same line, separated by commas. Then, on a new line, list \"True\" or \"False\" for each piece of hardware to indicate ownership status. True if the mention suggests concrete ownership by any user, and False if the hardware is discussed in a hypothetical or speculative way.\n",
+      "\n",
+      "Assistant:\n",
+      "Sure! Here is the requested output, with the correct ownership status for each piece of hardware:\n",
+      "Hardware names: NetTop, duel core processor, Nvidia ION video card\n",
+      "Hardware ownership: True, True, True\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "2011-09-28 18:26:12 ion\n",
+      "User:\n",
+      "In the given Bitcoin forum thread, pay close attention to the language used when mentioning hardware pieces. Look for explicit statements indicating ownership or hypothetical discussions.\n",
+      "\n",
+      "```thread\n",
+      "Date: 2013-05\n",
+      "Topic: R600 Bitcoin Miner (Warning: Exceedingly impractical)\n",
+      "### Original post:\n",
+      "So the old radeons are slower than current nvidia cards? I sold my radeon a long time ago, so I can't test it.\n",
+      "\n",
+      "### Reply 1:\n",
+      "Question decade. Can you make it work for an IGP? I.e an integrated HD4200(which people say is actually an HD3k igp)\n",
+      "\n",
+      "### Reply 2:\n",
+      "Well...- I have 2 ATI cards in my known technology collection (amongst about 7-10 nVidias, about 6 of which are capable of mining - at 2-5 Mhash/sec).-- One of which is the 6770 that I use for mining 24/7.-- The other is a 3700, if I remember correctly.- I'd really like some freedom to play with other pools.- I've only ever made a grand total of about 0.6 Bitcoin in the entire ~3 weeks of 24/7 mining on the 6770.-- Low, low price of 5 BTC my ass? I think it'd take an eternity to mine that back...If the miner goes faster on the 3700, than the ~20 Mhash/sec that my horrifyingly over-powered (and now blown-out, evidently) 8800GTS produces, I'd love to play around with it... even if it's stupidly inefficient, you'd really just need to step back and look at how bad nVidias are that people still try to mine with\n",
+      "\n",
+      "### Reply 3:\n",
+      "So, for the fun of it, and because I don't have any newer graphics cards, I've modified m0mchil's poclbm into something that works on R600 video cards. These are the Radeon HD 2000 and 3000 series. I never bothered to rename it.64-bit Windows binary <link> code <link> of the hints on how to build the source code are in the comments on the bottom of the C++ files. To use the Python source, you need some current version of Python 2, Numpy, and Boost::Python. To use the Brook+ source, you need ATI Stream SDK 1.4 beta and some C++ compiler, and some common sense.Let's discuss the reasons not to mine on an R600.By now, they are fairly old. Not all of them were that fast, either. I think my HP notebook is thermally throttling the video card.They don't support the gather/scatter I/O operations that the OpenCL miners use to minimize memory and bandwidth use.They don't have the 1-instruction rotate operation, that makes the modern Radeons so much faster than the modern GeForces. Nor do they have the 1-instruction bitselect instruction that AMD strangely doesn't expose to any APIs.Shifting is extremely inefficient, only 1/5 the speed of normal operations. That's because the ATI design has 4 <rest of post truncated>\n",
+      "\n",
+      "### Reply 4:\n",
+      "Oops, I rearranged and forgot to renumber. Fixed.Probably. Bullet points 3 and 4. Bullet point 3 is a reference to the Bitcoin wiki. <link> by the same measure that a modern Radeon has a 1.7x advantage over a modern GeForce, the older Radeon does not have that advantage, and in fact has a sloppily estimated 3.5x disadvantage. And that doesn't account for manufacturing process or runtime differences.I don't know. I don't have a Radeon IGP. AMD's spec thing says the Radeon 4200 has the 40 unified shaders supporting the ATI Stream Technology, so it should already work with 64-bit Windows. For the low, low price of 5 BTC, I might be convinced to try to make it work on other platforms, too. I doubt you could recover even the costs of electricity with that chip.I'm trying to consider the value of my time, here. And while the difficulty of mining increases, the exchange rate decreases, so I think even 5 BTC is only worth it for playing around. Instead, I give you my source code, which is everything you need to try it on your own, except for the links to the SDKs, and however long it takes it learn how to work those <truncated> says the SHA-256 kernel should do 6M threads/sec on a Radeon H<rest of post truncated>\n",
+      "\n",
+      "### Reply 5:\n",
+      "Can you convert 6 mill threads to mh/s?Also, these 5 bitcoins...5 bitcoins per person, or it could be small donations from everyone to make 5 bitcoins?\n",
+      "\n",
+      "### Reply 6:\n",
+      "No. I don't have any of the GPUs in KernelAnalyzer's group of simulated GPUs. I have only this Radeon HD 3410. I assume it's roughly 4 hashes per thread, so 6 Mthreads/s approximates 24 MH/s. Probably less because of runtime overhead.Let's say 5 BTC per platform.\n",
+      "\n",
+      "### Reply 7:\n",
+      "Okay, fine. If you can do it, count me in for 3 BTC. Anyone else want to cough up the missing 2?I could really use this at the office. Best card I've got in my desk PC is an nVidia 8600GT that bakes 83 C crunching out 3-4 Mhash/sec, or an nVidia Ion with an Atom that, if overclocked, crunches 7 Mhash/sec. And I've got a couple cards laying around gathering dust that could be crunching 20? Sheez. It's worth it!\n",
+      "\n",
+      "### Reply 8:\n",
+      "@rTech: I think we just need to wait for the remaining 1.5 BTC to be volunteered\n",
+      "\n",
+      "### Reply 9:\n",
+      "Yep, I'm in for 3, so if you're in for 2, there's our 5 Bitcoin Yo, Decade! edit: Just checked on the GPU I'll be looking at using this on, and it's a Radeon HD 3600. Just FYI.\n",
+      "\n",
+      "### Reply 10:\n",
+      "I actually managed to get 64 version to work with my ASUS EAH 3450 256MB.1.1 Mhash is the neat result, ill post pictures later.\n",
+      "\n",
+      "### Reply 11:\n",
+      "Wait, wait. I don't think you're minin<rest of thread truncated>\n",
+      "\n",
+      "```\n",
+      "\n",
+      "\n",
+      "\n",
+      "Reply with the hardware names, all in the same line, separated by commas. Then, on a new line, list \"True\" or \"False\" for each piece of hardware to indicate ownership status. True if the mention suggests concrete ownership by any user, and False if the hardware is discussed in a hypothetical or speculative way.\n",
+      "\n",
+      "Assistant:\n",
+      "Sure! Here is the requested output, with the correct ownership status for each piece of hardware:\n",
+      "Hardware names: Radeon, HD4200, ATI cards, 6770, 3700, 8800GTS, Radeon HD 2000 and 3000 series, HP notebook, Radeon IGP, Radeon 4200, Radeon HD 3410, nVidia 8600GT, nVidia Ion, Radeon HD 3600, ASUS EAH 3450 256MB\n",
+      "Hardware ownership: False, False, True, True, True, True, True, True, False, False, True, True, True, True, True\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n",
+      "\n"
+     ]
+    }
+   ],
+   "source": [
+    "instances = pd.read_csv('hardware_instances_inc_threads.csv') # columns: date,thread\n",
+    "efficiency = pd.read_csv('hardware_instances_with_efficiency.csv') # columns: date,hardware_name,TH/J\n",
+    "\n",
+    "# find rows where hardware_name = \"ion\"\n",
+    "efficiency = efficiency[efficiency[\"hardware_name\"] == \"ion\"]\n",
+    "\n",
+    "\n",
+    "i = 0\n",
+    "for index, row in efficiency.iterrows():\n",
+    "    print(row[\"date\"], row[\"hardware_name\"])\n",
+    "    filtered = instances[instances[\"date\"] == row[\"date\"]]\n",
+    "    print(filtered.iloc[0][\"thread\"])\n",
+    "    print(\"\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\")\n",
+    "    if i > 5:\n",
+    "        break\n",
+    "    i += 1"
+   ]
+  }
+ ],
+ "metadata": {
+  "kernelspec": {
+   "display_name": "py310",
+   "language": "python",
+   "name": "python3"
+  },
+  "language_info": {
+   "codemirror_mode": {
+    "name": "ipython",
+    "version": 3
+   },
+   "file_extension": ".py",
+   "mimetype": "text/x-python",
+   "name": "python",
+   "nbconvert_exporter": "python",
+   "pygments_lexer": "ipython3",
+   "version": "3.10.13"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 2
+}

bitcoinforum/5_processing_extracted_data/hardware_instances_inc_threads.csv

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f4c2cdc41313ff1b98e36ec7588a2ede1963a970eca220a87ff32557d8e941b
+size 56910639

bitcoinforum/5_processing_extracted_data/hardware_mapping_demo.py

@@ -0,0 +1,61 @@
+mapping0 = {
+    "\"&\"-\" screw terminals": "unknown",
+    "\"oc dual-x\"": "unknown",
+    "#1 computer": "unknown",
+    "#11": "unknown",
+    "#12 2-conductor with ground wire cable": "unknown",
+    "#13": "unknown",
+    "#2": "unknown",
+    "#2 computer": "unknown",
+    "#2 philips bit": "unknown",
+    "#6/#8": "unknown",
+    "#8-32 hex nut": "unknown",
+    "#8-32 x 1-1/4\" machine screws": "unknown",
+    "$1.1k ups/battery bank combo": "unknown",
+    "$150 laptop": "unknown",
+    "$16 holmes personal fans": "unknown",
+    "$1600 laptop": "unknown",
+    "$200 item from china": "unknown",
+    "$200 laptops": "unknown",
+    "$25 fans": "unknown",
+    "$400 gpus": "unknown",
+    "$400 rig": "unknown",
+    "$5 evercool single fan": "unknown",
+    "$500 pc": "unknown",
+    "(+5v)": "unknown",
+    "* .batstart batch:cgminer.exe": "unknown",
+    "+ track": "unknown",
+    "-framework opencl": "unknown",
+    "-l/opt/local/lib": "unknown",
+    "-lcurl": "unknown",
+    "-ldl": "unknown",
+    "-lm lib/libgnu.a": "unknown",
+    "-lncurses": "unknown",
+    "-lpthread": "unknown",
+    "-qt client": "unknown",
+    "-v -w256 -f0": "unknown",
+    ".333 ghs sticks": "unknown",
+    ".336 asicminers": "unknown",
+    ".bat file": "unknown",
+    ".bat or .cmd files": "unknown",
+    ".net": "unknown",
+    ".net 3.5 framework": "unknown",
+    ".net 4 framework": "unknown",
+    ".net framework": "unknown",
+    ".net framework v4.0": "unknown",
+    ".net program widget thingie": "unknown",
+    ".vbs script": "unknown",
+    "/dev/ati/card0": "unknown",
+    "/dev/ati/card1": "unknown",
+    "/dev/sda1": "unknown",
+    "/dev/sdx": "unknown",# All entries in the provided collection do not correspond to any known mining hardware from the list.
+}
+
+
+def map_hardware_to_table(string):
+    res = "not found"
+    for i in range(0, 488):
+        if string in globals()["mapping" + str(i)]:
+            res = globals()["mapping" + str(i)][string]
+            break
+    return res

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_0.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "\"+\"&\"-\" screw terminals": "unknown",
+    "#2": "unknown",
+    "#2 philips bit": "unknown",
+    "#8-32 hex nut": "unknown",
+    "#8-32 x 1-1/4\" machine screws": "unknown",
+    "$1.1k ups/battery bank combo": "unknown",
+    "$150 laptop": "unknown",
+    "$200 item from china": "unknown",
+    "$200 laptops": "unknown",
+    "$25 fans": "unknown",
+    "$5 evercool single fan": "unknown",
+    "(+5v)": "unknown",
+    "+ track": "unknown",
+    "-framework opencl": "unknown",
+    "-l/opt/local/lib": "unknown",
+    "-lcurl": "unknown",
+    "-ldl": "unknown",
+    "-lm lib/libgnu.a": "unknown",
+    "-lncurses": "unknown",
+    "-lpthread": "unknown",
+    ".333 ghs sticks": "unknown",
+    ".336 asicminers": "unknown",
+    ".bat file": "unknown",
+    ".net": "unknown",
+    ".net framework v4.0": "unknown",
+    "/dev/ati/card0": "unknown",
+    "/dev/ati/card1": "unknown",
+    "/dev/sda1": "unknown",
+    "/dev/sdx": "unknown",
+    "/dev/sdxx": "unknown",
+    "/dev/ttyusb0": "unknown",
+    "0-0 radeon 6950 900mhz clock average temp 85 degrees 1408 shaders": "6950",
+    "0-1 radeon 6950 940mhz clock average temp 70 degrees 1408 shaders": "6950",
+    "0-2 radeon 6570 725mhz clock average temp 70 degrees 480 shaders": "6570",
+    "0-3 radeon 5570 680mhz clock average temp 90 degrees 400": "5570",
+    "0.10 coupon miner": "unknown",
+    "0.13btc reward": "unknown",
+    "0.18um standard digital cmos": "unknown",
+    "0.25 share from the first miner": "unknown",
+    "0.75mm2 flex (2/3 sets of plugs)": "unknown",
+    "006c extenders": "unknown",
+    "05 impala": "unknown",
+    "0603 resistor": "unknown",
+    "0805 blue smd": "unknown",
+    "0805 smd 470 ohm resistors": "unknown",
+    "1 2kwatt boards from finksy/j4bberwock": "unknown",
+    "1 4950": "unknown", # No exact match, could be a typo or a specific model not listed
+    "1 4kwatt board from finksy/j4bberwock": "unknown",
+    "1 blade": "unknown", # Could potentially refer to a blade server used for mining, but no exact match
+    "1 broken stick": "unknown",
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_1.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "1 card rig": "unknown",
+    "1 chip usb miner": "unknown",
+    "1 controller": "unknown",
+    "1 controller with v3e firmware": "unknown",
+    "1 diode": "unknown",
+    "1 dps 1600 psu": "unknown",
+    "1 dps 2000 psu dead": "unknown",
+    "1 ghs scrypt": "unknown",
+    "1 hp 750 watt psu": "unknown",
+    "1 hub": "unknown",
+    "1 hub 10 ports": "unknown",
+    "1 miner": "unknown",
+    "1 pac": "unknown",
+    "1 phase transformer": "unknown",
+    "1 s1": "antminer s1",
+    "1 s5": "antminer s5",
+    "1 share": "unknown",
+    "1 th machine": "unknown",
+    "1 th/s coincraft rig": "unknown",
+    "1 th/s dragon miners": "unknown",
+    "1 th/s miners": "unknown",
+    "1 to 4 splitters with 5a brick": "unknown",
+    "1 to 8 splitter": "unknown",
+    "1 unit gridseed full pack": "unknown",
+    "1 usb block erupter": "unknown",
+    "1 usb hub (10 ports)": "unknown",
+    "1 x 100 chip order": "unknown",
+    "1\" high full-copper heat sink": "unknown",
+    "1\" wide off-green 4 port (12v) power adapter": "unknown",
+    "1% grade meter": "unknown",
+    "1-2 packs": "unknown",
+    "1-chip dualminers": "unknown",
+    "1.0 hub": "unknown",
+    "1.09gh v4 agg12": "unknown",
+    "1.15d boards": "unknown",
+    "1.15d card": "unknown",
+    "1.2 th miner": "unknown",
+    "1.2 th/s miner": "unknown",
+    "1.2 ths miners": "unknown",
+    "1.2gh/s miners": "unknown",
+    "1.2th": "unknown",
+    "1.2th machine": "unknown",
+    "1.2th miners": "unknown",
+    "1.2th/s rigs": "unknown",
+    "1.2v regulator": "unknown",
+    "1.3k watt psu": "unknown",
+    "1.3th blade": "unknown",
+    "1.5 controller board": "unknown",
+    "1.5 th/s order": "unknown",
+    "1.5k pull-up resistor": "unknown",
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_10.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "1500w psu": "unknown",
+    "1500w receptacle": "unknown",
+    "15a 110v breakers": "unknown",
+    "15a outlets": "unknown",
+    "15amp circuit 120v": "unknown",
+    "15k cfm fan": "unknown",
+    "15ohm resistors": "unknown",
+    "15y board": "unknown",
+    "16 5970s": "5970",
+    "16 avalon chips": "unknown", # Avalon products are listed, but "avalon chips" is too vague.
+    "16 awg pvc coated wire": "unknown",
+    "16 bfl chip credits": "unknown", # BFL products are listed, but "chip credits" is not a hardware.
+    "16 bit pic usb boot loader": "unknown",
+    "16 bitfury chips": "unknown", # Bitfury products are listed, but "bitfury chips" is too vague.
+    "16 board tower": "unknown",
+    "16 chip board": "unknown",
+    "16 chip credits": "unknown",
+    "16 chips": "unknown",
+    "16 credits": "unknown",
+    "16 gauge (16awg) wire cables": "unknown",
+    "16 gb blank cards": "unknown",
+    "16 gb usd card": "unknown",
+    "16 mh/s rig": "unknown",
+    "16 mhz oszillator": "unknown",
+    "16 pins cables": "unknown",
+    "16 sticks": "unknown",
+    "16-chip boards": "unknown",
+    "160 chips": "unknown",
+    "1600 evga watt psu": "unknown",
+    "1600 w psu": "unknown",
+    "1600 watt evga psu": "unknown",
+    "1600 watt wine cooling unit": "unknown",
+    "1600cfm fans": "unknown",
+    "1600w evga": "unknown",
+    "1600w power supplies": "unknown",
+    "1600w power supply kits": "unknown",
+    "1600w psu": "unknown",
+    "1600w psu (1700w peak)": "unknown",
+    "160mm fan": "unknown",
+    "162 chip s7s": "unknown", # Closest match would be "antminer s7", but "162 chip s7s" is too vague.
+    "16a2 boards": "unknown",
+    "16awg copper wire": "unknown",
+    "16awg pcie leads": "unknown",
+    "16core opteron 8000 server": "unknown",
+    "16gb flash-disk": "unknown",
+    "16gb micro sd": "unknown",
+    "16gb ram": "unknown",
+    "16gb samsung cards": "unknown",
+    "16mm cable": "unknown",
+    "16nm rig": "unknown",
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_100.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "cooler": "unknown",
+    "cooler fans": "unknown",
+    "cooler master": "unknown",
+    "cooler master extreme power plus 500w": "unknown",
+    "cooler master fan": "unknown",
+    "cooler master gx750 psu": "unknown",
+    "cooler master rp-650-pcap psu": "unknown",
+    "cooler master silent pro 1200w gold psu": "unknown",
+    "cooler master thunder 450": "unknown",
+    "cooler master v1000": "unknown",
+    "cooler master v1000 (1000w)": "unknown",
+    "cooler master v1000 / 1000w": "unknown",
+    "cooler master v1000 psu": "unknown",
+    "coolermaster": "unknown",
+    "coolermaster 1050w atx psu": "unknown",
+    "coolermaster 212 4 pipe 120mm fan heatsink": "unknown",
+    "coolermaster 240l": "unknown",
+    "coolermaster 430 case": "unknown",
+    "coolermaster cabinet": "unknown",
+    "coolermaster gx 450": "unknown",
+    "coolermaster hyper212 evo cpu cooler": "unknown",
+    "coolermaster jet-flo fans": "unknown",
+    "coolermaster jetflo": "unknown",
+    "coolermaster jetflo 100cfm fans": "unknown",
+    "coolermaster laptop pad": "unknown",
+    "coolermaster nepton 280l": "unknown",
+    "coolermaster v1000": "unknown",
+    "coolermaster v850": "unknown",
+    "cooling duct": "unknown",
+    "cooling fan": "unknown",
+    "cooling fans": "unknown",
+    "cooling fins": "unknown",
+    "cooling machine": "unknown",
+    "cooling paste": "unknown",
+    "cooling system": "unknown",
+    "coolink fans": "unknown",
+    "coolit pump": "unknown",
+    "coolitsystems water cooler": "unknown",
+    "coolmax 1600": "unknown",
+    "coolmax lcd power supply tester": "unknown",
+    "coolmax zpg-600b 600w atx12v / eps12v sli ready crossfire ready 80 plus gold certified power supply": "unknown",
+    "coolmax zu-900b": "unknown",
+    "cooper joints": "unknown",
+    "copper cylinder": "unknown",
+    "copper heat sinks": "unknown",
+    "copper heats": "unknown",
+    "copper on": "unknown",
+    "copper pcb board": "unknown",
+    "copper piping": "unknown",
+    "copper polygon pours": "unknown",
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_101.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "copper ram heatsinks": "unknown",
+    "copper shims": "unknown",
+    "copper track": "unknown",
+    "cords": "unknown",
+    "core 2 due": "unknown",  # Likely meant "core 2 duo" but exact match required
+    "core 2 duo": "unknown",
+    "core 2 duo t5600 cpu (1.83 ghz)": "unknown",
+    "core 2s": "unknown",
+    "core i3 system": "unknown",
+    "core i5 desktops": "unknown",
+    "core i7": "unknown",
+    "core i7 920": "unknown",
+    "core i7-860": "unknown",
+    "core i7-950": "unknown",
+    "core-i5 750": "unknown",
+    "core2 with a dual pcie slot": "unknown",
+    "core2 with sli motherboard": "unknown",
+    "core2duo e4400": "unknown",
+    "core2duo e7300": "unknown",
+    "cores": "unknown",
+    "corporate datacenter server room": "unknown",
+    "corsair": "unknown",
+    "corsair - hx-1000": "unknown",
+    "corsair 100 water cooling block": "unknown",
+    "corsair 1000 watt": "unknown",
+    "corsair 1000h psu": "unknown",
+    "corsair 1000w psu": "unknown",
+    "corsair 1000w rmx": "unknown",
+    "corsair 100i": "unknown",
+    "corsair 1050hx": "unknown",
+    "corsair 1200": "unknown",
+    "corsair 1200 axi": "unknown",
+    "corsair 1200 psu": "unknown",
+    "corsair 1200i power supply": "unknown",
+    "corsair 1500 watt": "unknown",
+    "corsair 1500 watt titanium": "unknown",
+    "corsair 1kw": "unknown",
+    "corsair 3 pin fans": "unknown",
+    "corsair 500 power supply": "unknown",
+    "corsair 600 watts": "unknown",
+    "corsair 600m (modular)": "unknown",
+    "corsair 600w 80+ power supply": "unknown",
+    "corsair 650": "unknown",
+    "corsair 650w": "unknown",
+    "corsair 650x": "unknown",
+    "corsair 750": "unknown",
+    "corsair 750 gold series psu": "unknown",
+    "corsair 750 power supply": "unknown",
+    "corsair 750 psu": "unknown",
+    "corsair 750 watt": "unknown",
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_102.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "corsair 750cx": "unknown",
+    "corsair 750m psu": "unknown",
+    "corsair 750w": "unknown",
+    "corsair 750w psu": "unknown",
+    "corsair 750watt": "unknown",
+    "corsair 760 plat": "unknown",
+    "corsair 850": "unknown",
+    "corsair 850 psu": "unknown",
+    "corsair 850ax": "unknown",
+    "corsair 850psu": "unknown",
+    "corsair 850rm": "unknown",
+    "corsair 950w": "unknown",
+    "corsair ax 1200 gold power supplies": "unknown",
+    "corsair ax 1200w professional series": "unknown",
+    "corsair ax 860": "unknown",
+    "corsair ax-1200": "unknown",
+    "corsair ax1200": "unknown",
+    "corsair ax1200i": "unknown",
+    "corsair ax1200i platinum psu": "unknown",
+    "corsair ax1200i psus": "unknown",
+    "corsair ax1500i": "unknown",
+    "corsair ax1500i psu": "unknown",
+    "corsair ax760": "unknown",
+    "corsair ax760i": "unknown",
+    "corsair ax850 psu": "unknown",
+    "corsair ax860": "unknown",
+    "corsair ax860 platinum psu": "unknown",
+    "corsair ax860w platinum psu": "unknown",
+    "corsair cm850": "unknown",
+    "corsair cs650m gold psu": "unknown",
+    "corsair cs750m psu": "unknown",
+    "corsair csm 750": "unknown",
+    "corsair cx 430 power supply units": "unknown",
+    "corsair cx 750": "unknown",
+    "corsair cx 750m psu": "unknown",
+    "corsair cx series 750 watt psu": "unknown",
+    "corsair cx series cx600 600w atx12v v2.3 80 plus bronze certified active pfc power supply": "unknown",
+    "corsair cx430": "unknown",
+    "corsair cx430m": "unknown",
+    "corsair cx430m power supply": "unknown",
+    "corsair cx500": "unknown",
+    "corsair cx500m": "unknown",
+    "corsair cx500m psu": "unknown",
+    "corsair cx600": "unknown",
+    "corsair cx600 watt": "unknown",
+    "corsair cx600m": "unknown",
+    "corsair cx750": "unknown",
+    "corsair cx750 80+ bronze certified": "unknown",
+    "corsair cx750 bronze 80+": "unknown",
+    "corsair cx750 psu": "unknown",
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_103.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "corsair cx750m": "unknown",
+    "corsair cx750m 750w psu": "unknown",
+    "corsair cx750m power supplies": "unknown",
+    "corsair cx750m psu": "unknown",
+    "corsair cx850": "unknown",
+    "corsair cx850m": "unknown",
+    "corsair cx850m psu": "unknown",
+    "corsair fans": "unknown",
+    "corsair force": "unknown",
+    "corsair force 120gb ssd": "unknown",
+    "corsair gold 650 watt": "unknown",
+    "corsair gold extra cooling": "unknown",
+    "corsair gold rm850": "unknown",
+    "corsair gs 800": "unknown",
+    "corsair gs 800 psu": "unknown",
+    "corsair gs800": "unknown",
+    "corsair h100i": "unknown",
+    "corsair h80i": "unknown",
+    "corsair high static pressure fans": "unknown",
+    "corsair hx 1050": "unknown",
+    "corsair hx series hx850": "unknown",
+    "corsair hx1050": "unknown",
+    "corsair hx1050 power supply": "unknown",
+    "corsair hx850": "unknown",
+    "corsair hx850 (850watts)": "unknown",
+    "corsair hx850 power supply": "unknown",
+    "corsair ml120 (white led)": "unknown",
+    "corsair modular psu": "unknown",
+    "corsair mx30": "unknown",
+    "corsair pc psu": "unknown",
+    "corsair platinimum digital": "unknown",
+    "corsair power supplies": "unknown",
+    "corsair psu": "unknown",
+    "corsair psu's": "unknown",
+    "corsair rm 1000": "unknown",
+    "corsair rm 650": "unknown",
+    "corsair rm 850": "unknown",
+    "corsair rm 850 psu": "unknown",
+    "corsair rm series rm750 750w atx12v v2.31 and eps 2.92 80 plus gold": "unknown",
+    "corsair rm100": "unknown",
+    "corsair rm1000": "unknown",
+    "corsair rm1000 power supplies": "unknown",
+    "corsair rm1000 ps": "unknown",
+    "corsair rm1000 psu": "unknown",
+    "corsair rm1000x": "unknown",
+    "corsair rm550": "unknown",
+    "corsair rm650": "unknown",
+    "corsair rm750": "unknown",
+    "corsair rm850": "unknown",
+    "corsair rm850 psu": "unknown",
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_104.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "corsair rm850m": "unknown",
+    "corsair sp120": "unknown",
+    "corsair sp120 high static pressure fans": "unknown",
+    "corsair sp120 pwm": "unknown",
+    "corsair tx 750w": "unknown",
+    "corsair tx750": "unknown",
+    "corsair tx750w": "unknown",
+    "corsair tx850": "unknown",
+    "corsair tx850m": "unknown",
+    "corsair tx850w": "unknown",
+    "corsair units": "unknown",
+    "corsair vengeance 2x2gb ddr1600": "unknown",
+    "corsair vs 650": "unknown",
+    "corsair vs450 psu": "unknown",
+    "corsair vs650": "unknown",
+    "corsair vx450w": "unknown",
+    "corsair's psu (1200 w (2 boards+controller) + 1000 w (1 board))": "unknown",
+    "corsaire psu": "unknown",
+    "corsaire rm850": "unknown",
+    "corsairs": "unknown",
+    "cosair ax1500": "unknown",
+    "cotton rounds": "unknown",
+    "couch pillows": "unknown",
+    "cougar 1000w psu": "unknown",
+    "cougar 1050w": "unknown",
+    "cougar cmx 850w power supply": "unknown",
+    "cougar cmx1200 cgr b2-1200cm 1200w": "unknown",
+    "cougar fan": "unknown",
+    "cougar fans": "unknown",
+    "cougar gx 1050": "unknown",
+    "cougar vortex cf-v12hpb": "unknown",
+    "coupon units": "unknown",
+    "covid-19 antibody test": "unknown",
+    "cp2012 boards": "unknown",
+    "cp2102": "unknown",
+    "cp2102 chip": "unknown",
+    "cp2102 module stc download cable usb 2.0 to ttl 6pin serial converter for stc": "unknown",
+    "cp2102 usb to uart bridge controller": "unknown",
+    "cp2102 usb to uart module": "unknown",
+    "cp2102 usb-uart adapter": "unknown",
+    "cp2102 usbtouart bridge controller": "unknown",
+    "cp2102s": "unknown",
+    "cp210x usb to uart bridge driver v6.6.1": "unknown",
+    "cpci board": "unknown",
+    "cpu": "unknown",
+    "cpu cable": "unknown",
+    "cpu connectors": "unknown",
+    "cpu cooler fan": "unknown",
+    "cpu fans": "unknown",
+    "cpu fans (thermaltake)": "unknown",
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_105.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "cpu heatsink": "unknown",
+    "cpu miner": "unknown",
+    "cpu miners": "unknown",
+    "cpu mining": "unknown",
+    "cpu performance monitor": "unknown",
+    "cpu rig": "unknown",
+    "cpu tower cooler": "unknown",
+    "cpu xmr": "unknown",
+    "cpu(s)": "unknown",
+    "cpub": "unknown",
+    "cpuminer": "unknown",
+    "cpuminer-1.0.1": "unknown",
+    "cpuminers": "unknown",
+    "cpus": "unknown",
+    "cr-doped (bi": "unknown",
+    "crashing software": "unknown",
+    "crate rig": "unknown",
+    "crimp press": "unknown",
+    "cron tab": "unknown",
+    "crossfire": "unknown",
+    "crossfire cable": "unknown",
+    "crossfire ribbon cable": "unknown",
+    "crossover cable": "unknown",
+    "crts": "unknown",
+    "crucial nvme": "unknown",
+    "crypto atm llc": "unknown",
+    "crypto miner \"lava-lamp\"": "unknown",
+    "cryptogenicbullion": "unknown",
+    "cryptoswitcher": "unknown",
+    "crystal oscillator": "unknown",
+    "crystal oscillators": "unknown",
+    "crystals": "unknown",
+    "crytoswitcher": "unknown",
+    "cs": "unknown",
+    "cs750m psu": "unknown",
+    "ct units": "unknown",
+    "cta0": "unknown",
+    "cta1": "unknown",
+    "cta1 board": "unknown",
+    "ctr1 light": "unknown",
+    "ctx691ct-nd(16mhz oscillator crystal)": "unknown",
+    "cube": "asicminer be cube",  # Closest match based on the context of mining hardware.
+    "cube 30gh/s - 38gh/s": "asicminer be cube",  # Assuming a specification detail, closest match.
+    "cube 38 gh btc miners": "asicminer be cube",  # Assuming a specification detail, closest match.
+    "cube blade": "asicminer be blade",  # Closest match based on the context of mining hardware.
+    "cube cables": "unknown",
+    "cube with an \"x\" on a chip": "unknown",
+    "cubes": "unknown",
+    "cuda drivers": "unknown",
+    "cuda gpu": "unknown",
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_106.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "cudaminer": "unknown",
+    "curl": "unknown",
+    "current meters": "unknown",
+    "current probe": "unknown",
+    "current probes": "unknown",
+    "current transformer": "unknown",
+    "current transformers": "unknown",
+    "current-sense board": "unknown",
+    "custom 3d printed brackets": "unknown",
+    "custom 4 gig usb flash drives": "unknown",
+    "custom atx cables": "unknown",
+    "custom avalon water blocks": "unknown",
+    "custom bfl-based hardware": "unknown",  # No exact match, but implies Butterfly Labs hardware
+    "custom build frame": "unknown",
+    "custom build watercooled gaming rig": "unknown",
+    "custom cables": "unknown",
+    "custom case": "unknown",
+    "custom cooled cabinet": "unknown",
+    "custom cooling solutions": "unknown",
+    "custom fan bracket": "unknown",
+    "custom homebuilt el cheapo 10port usb 2.0 hub": "unknown",
+    "custom miner": "unknown",
+    "custom plastic bracket": "unknown",
+    "custom power cables": "unknown",
+    "custom power distribution setup": "unknown",
+    "custom power supplies": "unknown",
+    "custom psu": "unknown",
+    "custom water blocks": "unknown",
+    "customized heat sink": "unknown",
+    "cut-to-length heatsinks": "unknown",
+    "cv1835 control boards": "unknown",
+    "cx1000s": "unknown",
+    "cx250m": "unknown",
+    "cx430": "unknown",
+    "cx500": "unknown",
+    "cx500 corsair": "cx500",  # Assuming a typo or shorthand for Corsair CX500 PSU
+    "cx500 power supply": "cx500",
+    "cx500m": "cx500",
+    "cx500m mining psu": "cx500",
+    "cx500s": "cx500",
+    "cx600": "unknown",
+    "cx600m psu": "unknown",
+    "cx750": "unknown",
+    "cx750 psu": "unknown",
+    "cx750m": "unknown",
+    "cx750m psu": "unknown",
+    "cx750ms": "unknown",
+    "cxm750": "unknown",
+    "cyber power cp-h720p": "unknown",
+    "cyber power ones": "unknown"
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_107.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "cyberpower cp-ha420": "unknown",
+    "cyberpower ups": "unknown",
+    "cybertron pc": "unknown",
+    "cyclone 2 ep2c35f484c6n": "unknown",
+    "cyclone iii dev kit": "unknown",
+    "cyclone3": "unknown",
+    "cypress": "unknown",
+    "cypress (#1)": "unknown",
+    "cypress (#2)": "unknown",
+    "cypress (#3)": "unknown",
+    "cypress (#4)": "unknown",
+    "cypress semiconductor corp. cy7c68013 ez-usb fx2 usb 2.0 development kit": "unknown",
+    "cypress usb-serial": "unknown",
+    "d+": "unknown",
+    "d-": "unknown",
+    "d-link 7-port hub": "unknown",
+    "d-link des-1008d 8-port 10/100 switch": "unknown",
+    "d-link dgs-1008d gbit switch": "unknown",
+    "d-link dir-505": "unknown",
+    "d-link dub-h7": "unknown",
+    "d-link dub-h7 (3a) usb hub": "unknown",
+    "d-link dub-h7 hubs": "unknown",
+    "d-link dub-h7 powered hub": "unknown",
+    "d-link h4": "unknown",
+    "d-link h7 powered usb hub": "unknown",
+    "d-link hi-speed usb 2.0 7-port powered hub": "unknown",
+    "d-link hub7": "unknown",
+    "d-link usb 2.0 hubs": "unknown",
+    "d-links": "unknown",
+    "d3": "unknown",
+    "d510 based board": "unknown",
+    "d510 mobos": "unknown",
+    "d510mo": "unknown",
+    "d7 ppc": "unknown",
+    "d7000": "unknown",
+    "d70s": "unknown",
+    "d750 psu": "unknown",
+    "d750 psu kits": "unknown",
+    "daiyo laptop power protector": "unknown",
+    "darkice": "unknown",
+    "darkside radiators": "unknown",
+    "data and power connectors": "unknown",
+    "data cable": "unknown",
+    "data cables": "unknown",
+    "data connector": "unknown",
+    "data leads": "unknown",
+    "data socket and cable": "unknown",
+    "datorhall": "unknown",
+    "daughter board": "unknown",
+    "dawson sp10 firmware": "spondooliestech sp10 dawson",  # Assuming a firmware reference for the hardware
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_108.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "day 1 jupiters": "unknown",
+    "day-1 knc jupiters": "knc jupiter",
+    "db": "unknown",
+    "db meter": "unknown",
+    "dbl. hashrate upgrade": "unknown",
+    "dc 5v 3 amp power adapter": "unknown",
+    "dc barrel to molex adapter 12vdc wall wart": "unknown",
+    "dc fans": "unknown",
+    "dc regulator": "unknown",
+    "dc unit": "unknown",
+    "dc-dc circuit": "unknown",
+    "dc-dc converter": "unknown",
+    "dc/dc converter": "unknown",
+    "dc/dc id on/off status": "unknown",
+    "dc2dc": "unknown",
+    "dcdc heatsinks": "unknown",
+    "dcr": "unknown",
+    "ddwrt router": "unknown",
+    "de-crypter": "unknown",
+    "de0": "unknown",
+    "de0 nano": "unknown",
+    "de0-nano": "unknown",
+    "de0-nano board": "unknown",
+    "de1 board": "unknown",
+    "dead avalon 1066": "canaan avalonminer 1066",  # Assuming "dead" refers to the condition, closest match.
+    "dead gpus": "unknown",
+    "debian": "unknown",
+    "debian computer": "unknown",
+    "debian cpu only system": "unknown",
+    "debian server": "unknown",
+    "debian squeeze": "unknown",
+    "debian squeeze vm": "unknown",
+    "decibel meter": "unknown",
+    "decibelometer": "unknown",
+    "decoupling capacitors": "unknown",
+    "dedicated laptop": "unknown",
+    "dedicated miner": "unknown",
+    "deep cycle battery": "unknown",
+    "dehumidifier": "unknown",
+    "dell": "unknown",
+    "dell 1200 mb a models": "unknown",
+    "dell 2100w psu": "unknown",
+    "dell 2950 psu": "unknown",
+    "dell 2950 psus": "unknown",
+    "dell 2kw server psu": "unknown",
+    "dell 4u dual xeon system": "unknown",
+    "dell 550w server psu": "unknown",
+    "dell 750": "unknown",
+    "dell 750 server powersupply": "unknown",
+    "dell 750 watt server power supply": "unknown",
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_109.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "dell 750w powersupplies": "unknown",
+    "dell 750w psus": "unknown",
+    "dell 750w server power supplies": "unknown",
+    "dell 750w server psu": "unknown",
+    "dell 750w server psus": "unknown",
+    "dell ahf-2dc-2100w psu": "unknown",
+    "dell ahf-2dc-2100w psus": "unknown",
+    "dell computer": "unknown",
+    "dell desktop fans": "unknown",
+    "dell dimension e520": "unknown",
+    "dell inspiron e1505 laptop": "unknown",
+    "dell mini 9 netbook": "unknown",
+    "dell monitor 27 inch": "unknown",
+    "dell monitors": "unknown",
+    "dell n750p": "unknown",
+    "dell n750p psu": "unknown",
+    "dell optiplex pcs": "unknown",
+    "dell perc/4e pcie raid controller": "unknown",
+    "dell power supply": "unknown",
+    "dell poweredge 750w": "unknown",
+    "dell psu": "unknown",
+    "dell server": "unknown",
+    "dell server powersupply": "unknown",
+    "dell server psu": "unknown",
+    "dell server supplies": "unknown",
+    "dell z750 psus": "unknown",
+    "dell z750 server psu": "unknown",
+    "dell z750p / n750p power supply": "unknown",
+    "dell z750s": "unknown",
+    "dell's psu": "unknown",
+    "delta": "unknown",
+    "delta 120 x 25mm extreme high-speed fan": "unknown",
+    "delta 2400 watt": "unknown",
+    "delta 3 pin fan": "unknown",
+    "delta 38mm fans": "unknown",
+    "delta 5200rpm fan": "unknown",
+    "delta abf1212he 3000-rpm 102-cfm 4.2-watts": "unknown",
+    "delta abf1212hhe 3500-rpm 130-cfm 6.2-watts": "unknown",
+    "delta abf1212le 2000-rpm 71-cfm 1.7-watts": "unknown",
+    "delta abf1212me 2500-rpm 92-cfm 3.2-watts": "unknown",
+    "delta abf1212vhe 4000-rpm 148-cfm 8.2-watts": "unknown",
+    "delta afb1212sh-pwm": "unknown",
+    "delta afb1212she replacement fan": "unknown",
+    "delta afc1212de": "unknown",
+    "delta afc1212de 120mm x 38mm": "unknown",
+    "delta dps 2000bb": "unknown",
+    "delta dps-1520ab a": "unknown",
+    "delta dps-2400ab b": "unknown",
+    "delta electronics afb1212she 120x120x38mm cooling fan": "unknown",
+    "delta fan": "unknown"
+}
+```

bitcoinforum/5_processing_extracted_data/mappings/hardware_mapping_11.txt

@@ -0,0 +1,54 @@
+```python
+mapping = {
+    "16x risers": "unknown",
+    "16x55nm chips": "unknown",
+    "175 available for shipment": "unknown",
+    "176 chips": "unknown",
+    "176-264 volt psu's": "unknown",
+    "18 awg per cable": "unknown",
+    "18 card 7970 rig": "7970",
+    "18 chips": "unknown",
+    "18 gauge awg 12v + ins": "unknown",
+    "18 gauge computer cable": "unknown",
+    "18 gauge power cords": "unknown",
+    "18 pin plug": "unknown",
+    "18 pins cables": "unknown",
+    "18\" cables": "unknown",
+    "18-hand mule": "unknown",
+    "18.000 btu/h hvac": "unknown",
+    "180 gh/s antminer": "antminer s1", # Assuming closest match based on hash rate.
+    "1800mh/s": "unknown",
+    "1800rpm quiet fans": "unknown",
+    "1800w power supply": "unknown",
+    "180gh ants": "antminer s1", # Assuming typo and closest match based on hash rate.
+    "1875 watts socket": "unknown",
+    "188 buck sam's club shop workbench": "unknown",
+    "18awg (0.824mm2) cable": "unknown",
+    "18awg cables": "unknown",
+    "18awg pcie y-splitters": "unknown",
+    "18awg standard wire": "unknown",
+    "18awg thermostat wire": "unknown",
+    "18ga wire": "unknown",
+    "18gh board": "unknown",
+    "18gh/s unit": "unknown",
+    "18guage wires": "unknown",
+    "18pin connectors": "unknown",
+    "19 pcie mobo": "unknown",
+    "19 port hub": "unknown",
+    "19\" rack box": "unknown",
+    "19\" rackmount enclosure": "unknown",
+    "19-porter from dipo electronic": "unknown",
+    "192 cfm delta pwm fan": "unknown",
+    "192 ghs miner": "unknown", # No direct match, could be a general reference to a miner's hash rate.
+    "192.168.0.1 router": "unknown",
+    "192.168.1.8": "unknown",
+    "1a adapter": "unknown",
+    "1a mains to usb adapter": "unknown",
+    "1a921": "unknown",
+    "1gb kingston": "unknown",
+    "1gh rig": "unknown",
+    "1gh/s setup": "unknown",
+    "1k ohm resistor": "unknown",
+    "1kw 28nm miner": "unknown", # No direct match, could refer to a miner's power consumption or efficiency.
+}
+```