A Survey of Decentralizing Applications via Blockchain: The 5G and Beyond Perspective
Bibliographic record
Abstract
Trusted third parties (TTPs) are frequently used for serving as an authority to issue and verify transactions in applications. Although the TTP-based paradigm provides customers with convenience, it causes a whole set of inevitable problems such as security threats, privacy vulnerabilities, and censorship. The TTP-based paradigm is not suitable for all modern networks, e.g., 5G and beyond networks, which are been evolving to support ubiquitous, decentralized, and autonomous services. Driven by the vision of blockchain technologies, there has been a paradigm shift in applications, from TTP-based to decentralized-trust-based. Decentralized applications (DApps) with blockchains promise no trust on authorities, tackling the key challenges of security and privacy problems. A main thrust of blockchain research is to explore frameworks and paradigms for decentralizing applications, fostering a number of new designs ranging from network architectures to business models. Therefore, this paper provides a compact and concise survey on the state-of-the-art research of decentralizing applications with blockchain in the 5G and beyond perspective. We provide four burning 5G and beyond challenges and discuss five aspects of motivation for decentralizing applications with blockchain. Then, we define nine fundamental modules of blockchains and explain the potential influence of these modules on decentralization in depth. We also discuss the interrelation between decentralization and some desired blockchain properties. Particularly, we present the capabilities of blockchain for decentralizing applications through reviewing DApps for 5G and beyond. We clearly distinguish three blockchain paradigms and discuss how developers to make right choices for 5G and beyond. Finally, we highlight important learned lessons and open issues in applying blockchain for decentralizing applications. Lessons learned and open issues from this survey will facilitate the transformation of centralized applications to DApps.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.007 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.003 | 0.008 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".