Blockchain-Based Access and Timeliness Control for Administrative Punishment Market Supervision

• Published in: IEEE internet of things journal Vol. 10; no. 12; p. 1
• Main Authors: He, Yajie, Jiang, Renkai, Ni, Xiaoze, Xu, Shubin, Chen, Ting, Feng, Jian
• Format: Journal Article
• Language: English
• Published: Piscataway IEEE 15.06.2023; The Institute of Electrical and Electronics Engineers, Inc. (IEEE)
• Subjects: Access control; Administrative Punishment; Blockchain; Blockchains; Cryptography; Internet of Things; Law; Logic gates; Market Supervision; Personnel; Regulation; Smart Contract; Smart contracts; Supervision
• ISSN: 2327-4662; 2327-4662
• DOI: 10.1109/JIOT.2023.3264805

Administrative punishment is one of the most important ways of enforcing administrative law in the field of market supervision in China. However, at the current stage, the abuse of data access permission and the difficulty in managing timeliness in administrative punishment still remain unresolved, which hinders the legalization and standardization of the administrative punishment system. Inspired by blockchain, which is inherently traceable, tamper-proof, and transparent, we design a system, punishment supervisor (PEATS), which is suitable for administrative punishment and technically overcomes the defects of the traditional administrative punishment procedure. To prevent the abuse of data access permission, we innovatively introduce the ACG (authorization control gateway) to verify the access permission of users based on the records in the MSD (market supervision department) contract. To ensure the timeliness of the administrative punishment procedure, we design a special case contract that has the same status as the general case processing state of administrative punishment to track case progress on the blockchain. We experiment and evaluate PEATS in terms of functionality and performance and find that PEATS provides traceability, transparency, and timeliness assurance. In addition, PEATS has 80.9% of the throughput of a traditional server with no more than an additional 3% latency and at most 60 KB additional storage space per case.