{"id":"84df0fa7-7f64-4cc2-afef-124ebf504087","arxiv_id":"1908.09058","paper_version":2,"verdict":"CONDITIONAL","confidence":"MODERATE","novelty_score":3.0,"correctness_risk":"medium","formal_verification":"none","parameter_count":0,"one_line_summary":"A comprehensive survey of blockchain-Cloud of Things integration that categorizes architectures, applications, platforms, and open challenges.","lead":"This paper reviews how blockchain can be combined with cloud computing and the Internet of Things, an approach called BCoT. It organizes the field into architectures, applications, platforms, and research challenges for readers entering the area.","discovery_kind":"review","skeptic_critique":{"model":"deepseek-v4-flash","headline":"The survey's central claim that BCoT is a promising enabler rests on primary studies that the paper's own Tables III–IV classify as conceptual or unvalidated; without a selection/validation audit the claim is not supported.","rationale":"I read the paper as a survey whose central claim is that BCoT is widely regarded as promising and that the paper provides a comprehensive state-of-the-art review. The weakest point is not any technical derivation, since there is no quantitative model to check, but the evidential basis for the 'promising' claim. The reader identified this correctly. The paper's own tables provide the sharpest evidence: numerous entries admit no prototype, no simulation, or no implementation. The narrative does not caveat these limitations when drawing conclusions. This is an internal inconsistency between the evidence presented and the strength of the claim, not merely a disagreement with outside consensus. I would not reject the paper; as a survey it can be useful organizationally. But conditional acceptance with a required limitation statement and softened claims is appropriate. If the audit shows most cited works are conceptual, the concern lands; if it shows a majority are implemented or simulated with results, the concern does not. The concrete test is straightforward and uses only the paper's own data, so it can settle the matter without external judgment. Therefore, the reader's CONDITIONAL verdict should stand unchanged.","tokens_in":42022,"tokens_out":3039,"duration_ms":31320,"concrete_test":"Audit every row of Tables III and IV, using only the paper's own Limitations column, to classify each cited study as (a) implemented/prototyped with measured results, (b) simulation-only, or (c) conceptual/unvalidated. Count the fraction in category (c) per application domain and overall. If that fraction is above 50%, or if any domain's feasibility claims rely predominantly on category (c), the abstract and conclusions should be revised to describe BCoT as a proposed paradigm whose benefits remain mostly unvalidated, and the survey should state this as an explicit limitation.","verdict_should_be":"UNCHANGED","load_bearing_attack":"Section IV presents BCoT applications as evidence that the paradigm delivers security, privacy, and efficiency benefits, and the abstract states it is 'widely regarded as a promising enabler.' The load-bearing premise is that the cited primary studies are a trustworthy, representative evidence base. That premise is insecure on two concrete grounds. First, the paper states in §I-A that material was 'collected from respective websites, technical reports, academic articles and newspapers' and gives no systematic search or inclusion protocol, so representativeness is unverifiable. Second, the survey's own Tables III and IV repeatedly list limitations such as 'the real prototype is not implemented' ([84], [87]), 'implementation results on access control efficiency is not investigated' ([88]), 'performance evaluation ... has not been done' ([96], [98]), 'blockchain implementation has not been done' ([106], [109], [111], [114]), 'only conceptual analysis is provided and simulation ... is lacked' ([124]), and 'real implementation results have not been reported' ([137]). These are not isolated cases; they span healthcare, city, transportation, industry, and cloud-service domains. The narrative in Section IV and the abstract nevertheless treat the aggregate literature as demonstrating feasibility. If most evidence is conceptual, the headline conclusion should be weakened to 'proposed but largely unvalidated,' not 'promising enabler.' The concern is not that BCoT is impossible; it is that this survey does not supply evidence sufficient for the strength of its central claim.","agreement_with_reader":"agree"},"referee_report":{"model":"deepseek-v4-flash","summary":"This paper is a survey of the integration of blockchain with Cloud of Things (BCoT). It introduces background on blockchain and CoT, motivates the integration through complementary capabilities, proposes a three-layer conceptual architecture (IoT layer, cloud blockchain layer, application layer), and reviews BCoT applications in smart healthcare, smart city, smart transportation, smart industry, cloud services, resource management, and education. It also surveys decentralized storage platforms and Blockchain-as-a-Service offerings, and it discusses research challenges and future directions including blockchain performance, machine learning, big data, and 5G. The central claim is that BCoT is widely regarded as a promising enabler for a wide range of application scenarios.","tokens_in":42291,"tokens_out":6175,"duration_ms":63725,"significance":"If the survey is accurate as a representation of the literature, it is a useful reference for researchers entering the BCoT area: it consolidates a fragmented literature, organizes it by application domain, and explicitly documents the limitations of each summarized study in Tables III and IV. The platform tables and the challenges/future-directions discussion are practical strengths. The main weakness is that the survey's narrative and abstract present BCoT as more established than the evidence it itself catalogues: many cited works are conceptual or lack implementation, and no selection protocol is documented. Because the value of the survey depends on the trustworthiness and representativeness of its primary sources, this calibration issue is the main point to address.","major_comments":[{"comment":"The survey does not document a search or inclusion protocol; Section I-A only says the material was collected from 'respective websites, technical reports, academic articles and newspapers.' This makes the representativeness of the reviewed literature unverifiable, which matters because the abstract's headline claim that BCoT is a 'promising enabler' is grounded in that literature. The paper's own Tables III and IV repeatedly report that primary studies are conceptual or unvalidated (e.g., [84], [87], [88], [96], [98], [106], [109], [111], [114], [124], [137]), yet the narrative in Section IV and the lessons-learned passages assert that BCoT 'can achieve' security, privacy, and efficiency benefits. The authors should either provide the missing selection/validation audit or explicitly weaken the conclusion to 'proposed but largely unvalidated,' and should ensure that Section IV language matches the evidence tables.","section":"§I-A, §IV, and abstract"},{"comment":"The proposed three-layer architecture is introduced as a 'conceptual BCoT architecture' that 'would be applicable to various scenarios,' but no mapping or validation demonstrates that it covers the application domains surveyed in Section IV. For example, the IoT-layer description assumes gateways and lightweight/full nodes, which may not fit smart-energy or cloud-service scenarios where the IoT layer is less prominent. The authors should either provide a mapping from each application domain to the architecture or soften the generalizability claim.","section":"§III-B, Fig. 6"},{"comment":"The 'Lessons learned' subsections (e.g., §IV-A1.4 and §IV-A4.4) draw general conclusions such as 'BCoT can achieve secure data sharing' and 'BCoT demonstrates its potentials' without hedging for the fact that, as Tables III and IV show, many of the supporting studies are not implemented or evaluated. This creates an internal inconsistency between the narrative and the authors' own limitation statements. Please add qualifying language such as 'in the reviewed proposals' and cite the corresponding limitation table entries when stating benefits.","section":"§IV-A lessons learned"}],"minor_comments":[{"comment":"Citations [206], [209], and [214] appear in §II-B4 and §III-B1, but the reference list in the provided version ends at [204]; these citations need to be matched to entries.","section":"References"},{"comment":"References [7] and [42] appear to be the same paper (Zhou et al., IEEE Communications Magazine, 2017), and [127] and [128] duplicate the same fair-payment work; the duplicate entries should be removed or consolidated.","section":"References"},{"comment":"Table II lists Openchain's operation mode as 'Partionned' (should be 'Partitioned'), and Section II-A1 states Bitcoin processes at most four transactions per second, whereas the commonly cited figure is about seven; please verify the throughput value.","section":"Table II and §II-A1"},{"comment":"Figure 2 reports publication trends 'from Web of Science' but does not specify the query terms or retrieval date, so the trend cannot be reproduced or updated; add that information in the caption or text.","section":"Fig. 2"},{"comment":"In Table IV, the entry for [129] says 'Data delection' in the use-case column; this should be 'data deletion.'","section":"Table IV"},{"comment":"The sentence 'These interesting integrations have the potentials to disrupt both blockchain and cloud computing worlds' is promotional; consider replacing it with a more neutral statement about possible impact.","section":"§IV-B1"}],"recommendation":"major_revision","confidential_remarks":"This is a solid survey for IEEE Communications Surveys & Tutorials. The main issue is calibration of the central claim to the evidence: the authors themselves provide the limitation data in Tables III and IV, but the abstract and narrative do not consistently reflect it. If the authors add a short methodology paragraph, temper the abstract and lessons-learned statements, and fix the reference and typographical issues, I would support acceptance. I do not see grounds for rejection."},"author_rebuttal":null,"desk_editor":{"model":"deepseek-v4-flash","letter":"First thing to know: this is a competent, comprehensive survey of blockchain + Cloud of Things, and the most honest part is the limitation tables. But the abstract's 'promising enabler' framing is not backed by the evidence the survey itself catalogs.\n\nWhat it does well: Section III's conceptual architecture is a reasonable synthesis and clearly explained. Section IV organizes dozens of BCoT applications into healthcare, city, transportation, industry, plus platforms and services. Tables III and IV are genuinely useful: most surveys wave at limitations; this one names specific missing artifacts per cited paper. That's honest and helps readers calibrate.\n\nSoft spots: the stress-test is right. If you actually tally Tables III and IV, a large share of entries say 'prototype not implemented', 'performance not evaluated', 'only conceptual analysis'. The narrative in Section IV and the abstract then treat the aggregate literature as evidence of feasibility. That is a mismatch. The paper would be more accurate saying 'proposed but largely unvalidated.' Second, the material collection in Section I-A mentions websites, technical reports, newspapers, with no search or inclusion protocol, so representativeness is unverifiable. That's a common survey weakness, but it matters more here because the central claim rests on the evidence base. Minor: the conceptual architecture is presented without validation, which is fine for a survey, but it's a synthesis, not a result. Self-citations are present but not a real issue.\n\nWho's this for: a newcomer who wants a map of the BCoT landscape, or someone who needs a citation for the concept. I'd hand it to a student starting in this area. The tables alone make it worth a look.\n\nRecommendation: yes, this deserves serious peer review — it's a solid survey that would benefit from a revision with a search protocol and a softened, evidence-matched conclusion. If I were the editor, I'd send it out and ask for those revisions.","headline":"Useful survey with honest limitation tables, but the abstract overstates BCoT's promise given most cited studies are conceptual or unvalidated.","tokens_in":42799,"tokens_out":2659,"would_cite":true,"duration_ms":27523,"reading_group":"maybe","serious_thinker":"yes","would_accept_peer_review":true},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"deepseek-v4-flash","headline":"BCoT: blockchain and cloud IoT integration is a promising enabler","keywords":["blockchain","Cloud of Things","Internet of Things","BCoT architecture","Blockchain as a Service","IoT security and privacy","smart healthcare","smart city"],"falsifier":"A head-to-head deployment of the same BCoT application against a centralized cloud IoT baseline—measuring end-to-end latency, energy per transaction, storage growth, and security incidents—would settle the claim; if the BCoT version is slower, more expensive, and no more secure under realistic conditions, the survey's central promise would be contradicted.","tokens_in":41804,"feed_emoji":"🔗","tokens_out":6877,"duration_ms":62920,"temperature":0.7,"pith_summary":"Blockchain and Cloud of Things (BCoT) is presented as a promising pairing: blockchain's decentralized, immutable ledger addresses the security, privacy, and single-point-of-failure problems of conventional cloud-based IoT, while cloud computing's elasticity and scalability relieve blockchain's computational and storage burdens. The paper is a wide-ranging review that organizes the case for this pairing across smart healthcare, smart city, smart transportation, smart industry, and cloud services, and it proposes a three-layer conceptual architecture for BCoT. A sympathetic reader would care because the review identifies a concrete route toward decentralized IoT services and catalogs the obstacles that must be overcome for that route to become practical.","feed_headline":"BCoT: blockchain and cloud IoT integration is a promising enabler","feed_subtitle":"The survey maps how decentralized ledgers fix cloud IoT flaws and how clouds make blockchains scalable.","key_machinery":"The central object is the conceptual BCoT architecture with three layers: an IoT layer of devices and gateways, a cloud blockchain layer in which blockchain services (shared ledger, consensus, smart contracts, cryptography, decentralized storage) are hosted as Blockchain-as-a-Service alongside cloud computing services (IaaS/PaaS/SaaS), and an application layer for healthcare, city, transportation, industry, and other domains. This architecture does the argument's work by showing where each technology compensates for the other: lightweight IoT devices delegate transactions and mining to gateways or cloud nodes, while blockchain governs cloud interactions, data provenance, and access control.","core_discovery":"On the paper's own terms, BCoT is an emerging and viable paradigm, not a single system but a family of designs in which blockchain runs as Blockchain-as-a-Service on cloud infrastructure and mediates IoT data sharing, access control, provenance, and resource trading. The central claim is that the two technologies are complementary: blockchain fixes CoT's centralization, privacy, and integrity weaknesses, while CoT fixes blockchain's scalability, energy, and storage limitations. The survey supports this claim by organizing dozens of proposed systems into a three-layer architecture—IoT layer, cloud blockchain layer, and application layer—and by reviewing application-domain evidence, commercial BaaS platforms, and decentralized storage options. It also identifies five open challenges: standardization, security vulnerability, privacy leakage, intelligence, and resource management.","pith_inferences":["The paper's own taxonomy tables show that many reviewed BCoT systems are conceptual or lack experiments, so the fair reading is that BCoT is a promising design space rather than a proven technology.","If BCoT is to win in practice, the decisive tests will likely be consensus overhead and latency on resource-constrained data flows, not architecture alone.","A natural extension of the survey's generic architecture would be to benchmark the same BCoT stack across healthcare, city, transportation, and industry cases, since the cited systems differ widely in consensus, storage, and trust assumptions."],"forward_implications":["BCoT would let resource-constrained IoT devices join blockchain networks through gateways, with cloud nodes carrying the heavy consensus and mining work.","In smart healthcare, storing raw records off-chain and hashes on-chain could make electronic health records tamper-evident and auditable without bloating the ledger.","Commercial Blockchain-as-a-Service offerings could become the standard deployment route, lowering the entry barrier for BCoT applications.","Future BCoT development is expected to lean on machine learning for resource scheduling and security, big-data analytics for blockchain data, and blockchain-based security for 5G network slicing."],"supporting_citations":[{"why":"It supplies the wide-ranging survey of blockchain applications in IoT that frames the BCoT research landscape and the throughput limitations blockchain must overcome.","marker":"[22]"},{"why":"It provides the baseline survey of blockchain for IoT that the paper extends toward the cloud-integrated CoT case.","marker":"[24]"},{"why":"It contributes the analysis of blockchain-based decentralized cloud solutions and the standardization problems BCoT inherits.","marker":"[27]"},{"why":"It offers the adjacent survey of blockchain and edge computing that motivates the cloud-blockchain integration scope.","marker":"[28]"},{"why":"It serves as one of the paper's own concrete BCoT systems, an Ethereum-based mobile cloud e-health data sharing platform used as evidence of BaaS feasibility.","marker":"[50]"},{"why":"It provides the smart-contract-based secure data provenance architecture for cloud-centric IoT that anchors the conceptual BCoT design.","marker":"[58]"},{"why":"It supplies the blockchain cloud manufacturing system that grounds the smart-industry application category.","marker":"[119]"}],"fun_headline_variants":["BCoT: where blockchain and cloud IoT cover each other's gaps","BCoT integration: blockchain fixes cloud IoT, cloud fixes blockchain","BCoT survey: blockchain and cloud IoT integration, applications, challenges","How blockchain and Cloud of Things complement each other in BCoT"],"cache_read_input_tokens":3200,"weakest_assumption_plain":"The survey's conclusion that BCoT is a promising enabler rests on the assumption that the primary studies it reviews accurately represent BCoT's feasibility, even though the paper's own tables note that many of those studies are conceptual and lack experimental validation.","fun_headline_variants_meta":{"raw":{"variants":["BCoT: where blockchain and cloud IoT cover each other's gaps","BCoT integration: blockchain fixes cloud IoT, cloud fixes blockchain","BCoT survey: blockchain and cloud IoT integration, applications, challenges","How blockchain and Cloud of Things complement each other in BCoT"]},"model":"deepseek-v4-flash","effort":"low","cost_usd":0.001062,"raw_usage":{"total_tokens":4441,"prompt_tokens":920,"completion_tokens":3521,"prompt_tokens_details":{"cached_tokens":384},"prompt_cache_hit_tokens":384,"prompt_cache_miss_tokens":536,"completion_tokens_details":{"reasoning_tokens":3447}},"tokens_in":536,"tokens_out":3521,"duration_ms":26413,"temperature":1.0,"reasoning_tokens":3447,"cache_read_input_tokens":384,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-08-14T11:22:31.307975+00:00","model_set":{"reader":"deepseek-v4-flash"},"falsifier":"A head-to-head deployment of the same BCoT application against a centralized cloud IoT baseline—measuring end-to-end latency, energy per transaction, storage growth, and security incidents—would settle the claim; if the BCoT version is slower, more expensive, and no more secure under realistic conditions, the survey's central promise would be contradicted.","supporting_citations":[],"review_version":1}