{
  "fetched_at": "2026-10-20T09:31:34Z",
  "source_url": "https://www.kaggle.com/competitions/diablo-cryptocurrency-price-prediction/data",
  "pages": [
    {
      "name": "rules",
      "content": "There are no specific rules or restrictions. Everything is allowed to increase your score.",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "data-description",
      "content": "<p>This is a very simple format. The target variable is the daily price of the 'Diablo' currency, there are 7 other variables to use for predictions (outside information is accepted).</p>\n<h2>File descriptions</h2>\n<ul>\n<li><strong>train.csv</strong> - the training set</li>\n<li><strong>test.csv</strong> - the test set</li>\n<li><strong>sample_sub.csv</strong> - a sample submission file in the correct format</li>\n</ul>\n<h2>Data fields</h2>\n<ul>\n<li><strong>Id</strong> - Id for each observation</li>\n<li><strong>Expected</strong> - The closing price for Diablo crypto (the target variable)</li>\n<li><strong>number_of_transactions</strong> - Number of transactions that day</li>\n<li><strong>financial_products_stash1</strong> - A combination of financial products</li>\n<li><strong>financial_products_stash2</strong> - A combination of financial products</li>\n<li><strong>financial_products_stash3</strong> - A combination of financial products</li>\n<li><strong>financial_products_stash4</strong> - A combination of financial products</li>\n<li><strong>financial_products_stash5</strong> - A combination of financial products</li>\n<li><strong>financial_products_stash6</strong> - A combination of financial products</li>\n<li><strong>financial_products_stash7</strong> - A combination of financial products</li>\n</ul>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Description",
      "content": "<p>This is a dataset of the historic price (in USD) of '<b>Diablo</b>', a private cryptocurrency used between several Asian hedge funds to distribute risk between them. The target is simple, we provide a <b>train set of 15 months</b> of data and a <b>test set of the following 4 months</b> to predict.</p>\n<p>As this data isn't published anywhere, there are no rules regarding searching for <b>outside information</b> to increase performance.</p>\n\nThe winner(s) might get a follow up call or e-mail (absolutely non official).",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Evaluation",
      "content": "<p>The evaluation pages describes how submissions will be scored and how students should format their submissions. You don't need a sub-title at the top (the page title appears above). For an example of a high quality evaluation page, see the 2013 KDD Cup page, which we have copied here:</p>\r\n<hr />\r\n<p>The evaluation metric for this competition is <a href=\"https://www.kaggle.com/wiki/MeanFScore\"> Mean F1-Score</a>. The F1 score, commonly used in information retrieval, measures accuracy using the statistics precision p and recall r. Precision is the ratio of true positives (tp) to all predicted positives (tp + fp). Recall is the ratio of true positives to all actual positives (tp + fn). The F1 score is given by:</p>\r\n<p>\\[ F1 = 2\\frac{p \\cdot r}{p+r}\\ \\ \\mathrm{where}\\ \\ p = \\frac{tp}{tp+fp},\\ \\ r = \\frac{tp}{tp+fn} \\]</p>\r\n<p>The F1 metric weights recall and precision equally, and a good retrieval algorithm will maximize both precision and recall simultaneously. Thus, moderately good performance on both will be favored over extremely good performance on one and poor performance on the other.</p>\r\n<h2>Submission Format</h2>\r\n<p><strong>For every author in the dataset</strong>, submission files should contain two columns: AuthorId and DuplicateAuthorIds. DuplicateAuthorIds should be a space-delimited list. Every AuthorId counts as his/her own duplicate, and every duplicate should be listed under each of its respective ids. For example, if you suspect author A, B, and C are the same, you should list (A,A B C), (B,B A C), (C,C A B).</p>\r\n<p>The file should contain a header and have the following format:</p>\r\n<pre>AuthorId,DuplicateAuthorIds<br />1,1<br /><span style=\"font-size: 14px; line-height: 1.4em;\">8,8<br />9,9 10<br /></span><span style=\"font-size: 14px; line-height: 1.4em;\">10,10 9<br /></span><span style=\"font-size: 14px; line-height: 1.4em;\">etc.</span></pre>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    }
  ]
}