Is there already an SWC entry for the keeping secret vulnerability [1][2]? The issue occurs when a contracts, e.g., a multi-player game needs to store secret information, e.g., for the next move of a player, and it just stores this information in a private field. However, for writing the field there needs to be a transaction, which makes the value public and a player might get an advantage because of this.
If there is no related entry may I just write one?
[1] Atzei, Nicola, Massimo Bartoletti, and Tiziana Cimoli. "A survey of attacks on Ethereum smart contracts." IACR Cryptology ePrint Archive 2016 (2016): 1007.
[2] https://medium.com/solidified/keeping-secrets-on-ethereum-5b556c3bb1ee
Is there already an SWC entry for the keeping secret vulnerability [1][2]? The issue occurs when a contracts, e.g., a multi-player game needs to store secret information, e.g., for the next move of a player, and it just stores this information in a private field. However, for writing the field there needs to be a transaction, which makes the value public and a player might get an advantage because of this.
If there is no related entry may I just write one?
[1] Atzei, Nicola, Massimo Bartoletti, and Tiziana Cimoli. "A survey of attacks on Ethereum smart contracts." IACR Cryptology ePrint Archive 2016 (2016): 1007.
[2] https://medium.com/solidified/keeping-secrets-on-ethereum-5b556c3bb1ee