4 ms·
> It would take weeks to figure out precisely what had happened, but it appeared that the platform had been fooled into severely undervaluing tokens that belong
by tzs 4y ago
> It would take weeks to figure out precisely what had happened, but it appeared that the platform had been fooled into severely undervaluing tokens that belonged to its users and selling them to the attacker at an extreme discount.
Q: is the programming language these things are written in powerful enough and have sufficient data access for the developers to include sanity checks that would halt trading automatically if something is happening too far out of the norm such as an unusually high volume of attempted night discount sales? Or maybe that would just block extreme discount sales if there have been too many of those recently?
- meetups323 4y agoThe language could represent that, but you pay per operation so checks tend to get thrown out the window.
- isolli 4y agoThis part seems relevant: > It also saved on costs by limiting the number of interactions between the platform and outside entities. For example, when Indexed needed to calculate the total value held within a pool, instead of checking token prices on an exchange such as Uniswap, it sometimes extrapolated from the value and weight of the largest token within the pool, called the “benchmark” token. > This way, it reduced the fees it paid for transactions on the Ethereum blockchain. This cost-saving mechanism ultimately allowed the hack to take place.
- hiq 4y agoSee this very good comment about Solidity, the main language used to write software on Ethereum: https://news.ycombinator.com/item?id=14691212 https://news.ycombinator.com/item?id=14691212 More to your point, you can always have more logging, slow things down to make them safer and allow communities to react in a timely manner, but it's far from trivial. The real problem is that any mistake can be fatal from the defender's point of view.