Papers › Bayesian regression and Bitcoin

Bayesian regression and Bitcoin

6 Oct 2014arXiv:1410.1231archive 2025-07-28

Devavrat Shah, Kang Zhang

In this paper, we discuss the method of Bayesian regression and its efficacy for predicting price variation of Bitcoin, a recently popularized virtual, cryptographic currency. Bayesian regression refers to utilizing empirical data as proxy to perform Bayesian inference. We utilize Bayesian regression for the so-called "latent source model". The Bayesian regression for "latent source model" was introduced and discussed by Chen, Nikolov and Shah (2013) and Bresler, Chen and Shah (2014) for the purpose of binary classification. They established theoretical as well as empirical efficacy of the method for the setting of binary classification. In this paper, instead we utilize it for predicting real-valued quantity, the price of Bitcoin. Based on this price prediction method, we devise a simple strategy for trading Bitcoin. The strategy is able to nearly double the investment in less than 60 day period when run against real data trace.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 13 code samples harvested from 6 repositories linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 2 honoured, 1 violated, 0 with no contract checked; 7 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 5 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 13 samples from 6 repositories, 10 ran (3 with no instrument failure; 7 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

15 repositories listed; official and paper-mentioned ones first.

SourangshuGhosh/BTCpredictor mentioned on GitHubMITSyntology: not harvested report
SourangshuGhosh/BitCoinPricepredictor mentioned on GitHubMITSyntology: not harvested report
akashsrikanth2310/Predicting-Bitcoin-Price-Variations-using-Bayesian-Regression- mentioned on GitHubSyntology: 3 samples, 3 ran (1 instrument-failed) · 0 unverified report
fraziezr/Machine_Learning_Final_Project_Team_12 mentioned on GitHubMITSyntology: not harvested report
panditanvita/BTCpredictor mentioned on GitHubMITSyntology: not harvested report
parikhs97/Predicting-Bitcoin-Price-Variations mentioned on GitHubSyntology: not harvested report
pmshst/A-Real-time-System-of-Bitcoin-Price-Prediction mentioned on GitHubSyntology: not harvested report
prmody96/Predicting-Bitcoin-Price-Variations-using-Bayesian-Regression mentioned on GitHubSyntology: 2 samples, 1 ran (1 instrument-failed) · 1 unverified report
rajatdge/Bitcoin-Price-Prediction mentioned on GitHubSyntology: not harvested report
raveenaaa/BitcoinPricing mentioned on GitHubSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
sabsgeo/crypto-trading-bot mentioned on GitHubApache-2.0Syntology: 2 samples, 0 ran · 2 unverified report
sabsgeo/sentimentalmarket mentioned on GitHubApache-2.0Syntology: not harvested report
shawnrajan7/Bayesian-Regression-and-Bitcoin mentioned on GitHubSyntology: 2 samples, 2 ran (1 instrument-failed) · 0 unverified report
stavros0/bitcoin-price-prediction mentioned on GitHubSyntology: 3 samples, 3 ran (3 instrument-failed) · 0 unverified report
tejasai97/BitCoinPricePrediction mentioned on GitHubSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

13 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 2 honoured, 1 violated, 0 with no contract checked; 7 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · honoured contract
1ran · violated contract
5ran · our draft was wrong
2ran; the contract check could not run
3unverified

Licence: 8 of the 13 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 6 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

akashsrikanth2310/Predicting-Bitcoin-Price-Variations-using-Bayesian-Regression- community (archive-listed) 3 samples, 3 ran (1 instrument-failed) · 0 unverified
findMean bitcoin.py ran · honoured contract fingerprinted no licence file found · pointer only · 396d865c150550af · report fixture: signature x:ndarray/1/float · returned float64 · level recorded 2026-09-22
findStd bitcoin.py ran · honoured contract fingerprinted no licence file found · pointer only · f74e8b4b084db3b7 · report fixture: signature x:ndarray/1/float · returned float64 · level recorded 2026-09-22
findTheSimilarityValues bitcoin.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted no licence file found · pointer only · 3596eba818752a48 · report fixture: signature X:Tensor/1/float, rowVal:Tensor/1/float, meanofX:float/0/float, stdOfX:float/0/float, MeanofRow:float/0/float, stdofRow:float/0/float, M:int/0/int, counter:int/0/int · returned Tensor · level recorded 2026-09-22
prmody96/Predicting-Bitcoin-Price-Variations-using-Bayesian-Regression community (archive-listed) 2 samples, 1 ran (1 instrument-failed) · 1 unverified
similarity in 17 papers bitcoin.py ran · our draft was wrong no licence file found · pointer only · 8582898b7905fbc6 · report fixture: signature a:Series/1/float, b:Series/1/float · returned float64 · level recorded 2026-09-22
computeDelta bitcoin.py unverified no licence file found · pointer only · 6af741a51af070df · report
raveenaaa/BitcoinPricing community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
computeDelta bitcoin.py ran · our draft was wrong no licence file found · pointer only · 3bc96df115ad2b9a · report fixture: signature wt:int/0/int, X:Series/1/float, Xi:DataFrame/0/? · returned float64 · level recorded 2026-09-22
sabsgeo/crypto-trading-bot community (archive-listed) 2 samples, 0 ran · 2 unverified
calc_support_and_resistance sentimentalmarket/algorithms/trending_lines.py unverified Apache-2.0 (permissive) · e26e3994b72e9e6f · report
calc_vwap sentimentalmarket/algorithms/technical_indicators.py unverified Apache-2.0 (permissive) · 9a4797bb7ff7584d · report
shawnrajan7/Bayesian-Regression-and-Bitcoin community (archive-listed) 2 samples, 2 ran (1 instrument-failed) · 0 unverified
computeDelta bitcoin.py ran · our draft was wrong no licence file found · pointer only · eb40608f370c62c2 · report fixture: signature wt:float/0/float, X:Series/1/float, Xi:DataFrame/0/? · returned float64 · level recorded 2026-09-22
similarity in 17 papers bitcoin.py ran · violated contract fingerprinted no licence file found · pointer only · 408e49df96405fae · report fixture: signature a:ndarray/1/float, b:ndarray/1/float · returned float64 · level recorded 2026-09-22
stavros0/bitcoin-price-prediction community (archive-listed) 3 samples, 3 ran (3 instrument-failed) · 0 unverified
choose_effective_centers bitcoin_price_prediction/bayesian_regression.py ran · our draft was wrong fingerprinted MIT (permissive) · 1402942d0885b747 · report fixture: signature centers:ndarray/2/float, n:int/0/int · returned ndarray · level recorded 2026-09-22
find_cluster_centers bitcoin_price_prediction/bayesian_regression.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · b9dd41be3c7a35f3 · report fixture: signature timeseries:ndarray/2/float, k:int/0/int · returned ndarray · level recorded 2026-09-22
generate_timeseries bitcoin_price_prediction/bayesian_regression.py ran · our draft was wrong fingerprinted MIT (permissive) · 161a2eb75063855d · report fixture: signature prices:ndarray/1/float, n:int/0/int · returned ndarray · level recorded 2026-09-22

Tasks

Bayesian InferenceBinary ClassificationGeneral Classificationregression

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections