human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "what are the actual flaws in important smart contracts and how can we find them"
  Abstract: An important problem in smart contract security is understanding the likelihood and criticality of discovered, or potential, weaknesses in contracts. In this paper we provide a summary of Ethereum smart contract audits performed for 23 professional stakeholders, avoiding the common problem of reporting issues mostly prevalent in low-quality contracts. These audits were performed at a leading company in blockchain security, using both open-source and proprietary tools, as well as human code analysis performed by professional security engineers. We categorize 246 individual defects, making it possible to compare the severity and frequency of different vulnerability types, compare smart contract and non-smart contract flaws, and to estimate the efficacy of automated vulnerability detection approaches.

Connected through hyperedge HE-1 (induced by source paper "smart contract development from the perspective of developers topics and issues discussed on social media"):
  with members:
    - "a survey on ethereum systems security vulnerabilities attacks and defenses"
    - "when energy trading meets blockchain in electrical power system the state of the art"
    - "slither a static analysis framework for smart contracts"
    - "verisolid correct by design smart contracts for ethereum"
    - "manticore a user friendly symbolic execution framework for binaries and smart contracts"
    - "tool demonstration fsolidm for designing secure ethereum smart contracts"
    - "finding the greedy prodigal and suicidal contracts at scale"
    - "empirical vulnerability analysis of automated smart contracts security testing on blockchains"

Connected through hyperedge HE-2 (induced by source paper "smart contract development in practice trends issues and discussions on stack overflow"):
  with members:
    - "a survey on ethereum systems security vulnerabilities attacks and defenses"
    - "when energy trading meets blockchain in electrical power system the state of the art"
    - "slither a static analysis framework for smart contracts"
    - "transax a blockchain based decentralized forward trading energy exchange for transactive microgrids"
    - "verisolid correct by design smart contracts for ethereum"
    - "manticore a user friendly symbolic execution framework for binaries and smart contracts"
    - "tool demonstration fsolidm for designing secure ethereum smart contracts"
    - "finding the greedy prodigal and suicidal contracts at scale"

Question: Please tell me which class the center node belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.SE(Software Engineering)