what did devops199 write after freezing over 500,000 eth in parity's multisig wallets?

After freezing over 500,000 ETH in Parity's multisignature (multisig) wallets, the user "devops199" wrote that they were "an Ethereum newbie... just learning." Devops199's action occurred after they discovered a wallet library contract that had not been initialized, allowing them to become its owner by calling the "initWallet" function. Following this, devops199 called the "kill" function on the wallet contract, which disabled the library and permanently froze the funds in all wallets dependent on that contract, amounting to over $150 million worth of ETH at the time. Devops199 expressed fear and concern afterward, saying "Sorry… I’m really afraid now… can’t talk." This incident was described as accidental, with devops199 seemingly exploring the code and unintentionally triggering the kill command that caused the freeze. Parity's team indicated that the inclusion of the kill function and failure to initialize the wallet library contract were key mistakes that allowed this to happen. This event caused a major loss of access to a significant amount of ETH in multiple wallets and led to discussions about possible hard forks to restore access, which were highly controversial. Devops199's comment reflected their novice status and regret over the incident, highlighting it was not a deliberate attack but an unfortunate consequence of a bug and lack of proper initialization in the Parity multisig wallet code.