@dystopiabreaker Either way I suspect that the issue was more related to overall system complexity, development velocity, and testing / verification procedures than it was to missing language features.
@dystopiabreaker Not sure optionals would have helped here. Maybe proper ADTs and compiler warnings for non exhaustive matches, at least based on the analysis here:
6/ We know that the exploit only uses process(), not update() or prove(). This must mean that the problem lies in that critical check. Looking at this function, there are actually two parts: main functionality, and backwards-compatbility code introduced later on in an update.
@0xfbifemboy Taxing income at a higher rate than capital gains disproportionately punishes those who do not have enough capital to invest. It is much more equitable to tax capital gains and wealth at a higher rate than income.
@gakonst definitely v cute, but loops should be treated with quite some caution in the smart contract context. not sure if hiding them away in utility functions is a good idea.
@MonetSupply also I would hardly call maker governance radically transparent. It’s a big mess of impenetrable jargon and hard to understand forum posts, and still most of the real governance happens behind the scenes and is controlled by a few whales.
@MonetSupply all token weighted governance voting is inherently plutocratic and will devolve to the same broken structures that we have with existing corporate entities.
@MonetSupply maker gov is fundamentally flawed. it is a replication of existing corporate shareholder gov structures and as such can never be a true public good.
@dystopiabreaker but degrowth isn’t about population growth, it’s about the way that current economic systems demand a constant increase in consumption.