U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
Why @arwensecure changed Arwen's Ethereum smart contract to use 'create2'?
Spoiler: there is an inherent performance/security tradeoff with non-create2 smart contract addresses. /1https://medium.com/arwensecure/moving-arwens-ethereum-smart-contract-to-create2-4451e685f7a1 …
![jimmyhomma⚡️[LN adoption]](https://pbs.twimg.com/profile_images/740824062260334592/Y-rAxOFn_normal.jpg)
Core issue: Under some smart contract usercases IF you don't wait for enough confirmations before funding a address a third party can redirect your funding transaction to an attacker controlled address stealing your $$$. Works even when your smart contract is 100% correct, /2
The standard way of solving this is: 1. use create2, 2. OR to wait a sufficient number of confirmations before sending funds to the smart contract. Under some designs, such as Arwen, this doubles the number confirmations a user must wait. We choose to move to create2. /3
None of this impacts Arwen users. While we are getting close Arwen ETH support hasn't launched yet. I choose to publish this because it is technically interesting and may help others. /4
While I wrote this blog entry, Arwen's ETH smart contracts were a team effort. See: https://github.com/cwcrypto/arwen-eth-contracts/graphs/contributors … /5
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
