MétaCan
Menu
Back to cohort
Record W3003524345 · doi:10.1109/mnet.001.1900178

Securing Smart Cities through Blockchain Technology: Architecture, Requirements, and Challenges

2020· article· en· W3003524345 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueIEEE Network · 2020
Typearticle
Languageen
FieldComputer Science
TopicBlockchain Technology Applications and Security
Canadian institutionsUniversity of Northern British Columbia
Fundersnot available
KeywordsBlockchainComputer scienceArchitectureCloud computingSmart cityKey (lock)Computer securityWork (physics)TelecommunicationsInternet of ThingsEngineeringOperating system

Abstract

fetched live from OpenAlex

In recent years, unprecedented work has been done in the area of smart cities. The purpose of developing smart cities is to enhance quality of life factors for people dwelling within them. To achieve that purpose, technologies such as IoT and cloud computing have been utilized. Blockchain technology is also among the promising technologies that can offer countless valuable services to its end users. It is a immutable programmable digital register for the purpose of recording virtual assets having some value and was primarily developed for digital currencies like Bitcoin. To fully utilize the services of blockchain technology within smart cities, characteristics of blockchain technology, and its key requirements and research challenges need to be identified. Hence, in this article, an attempt has been made to identify the characteristics of blockchain technology. Furthermore, indispensable requirements for incorporating blockchain technology within smart cities are enumerated. A conceptual architecture for securing smart city using blockchain technology is proposed and explained using a possible use case study. An overview of a real-world three-blockchain- based smart city case study is also presented. Finally, several imperative research challenges are identified and discussed.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.779
Threshold uncertainty score0.790

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.037
GPT teacher head0.242
Teacher spread0.206 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it