Instruct: Identify the main and secondary category of Arxiv papers based on the titles and abstracts
Query: Solidity 0.5: when typed does not mean type safe   The recent release of Solidity 0.5 introduced a new type to prevent Ether
transfers to smart contracts that are not supposed to receive money.
Unfortunately, the compiler fails in enforcing the guarantees this type
intended to convey, hence the type soundness of Solidity 0.5 is no better than
that of Solidity 0.4. In this paper we discuss a paradigmatic example showing
that vulnerable Solidity patterns based on potentially unsafe callback
expressions are still unchecked. We also point out a solution that strongly
relies on formal methods to support a type-safer smart contracts programming
discipline, while being retro-compatible with legacy Solidity code.

17
The categories of this paper are: q-fin
24
The categories of this paper are: dg-ga
15
The categories of this paper are: nucl-ex
13
The categories of this paper are: quant-ph
5
The categories of this paper are: gr-qc
20
The categories of this paper are: acc-phys
32
The categories of this paper are: atom-ph
27
The categories of this paper are: comp-gas
21
The categories of this paper are: adap-org
8
The categories of this paper are: hep-ex
6
The categories of this paper are: astro-ph
22
The categories of this paper are: chao-dyn
0
The categories of this paper are: hep-ph
3
The categories of this paper are: physics
34
The categories of this paper are: chem-ph
29
The categories of this paper are: funct-an