10.11.2021
Hyperinflation in the Weimar Republic # Finally, a brief word on a favorite example of advocates of private control over money issuance, the German hyperinflation of 1923, which was supposedly caused by excessive government money printing. The Reichsbank president at the time, Hjalmar Schacht, putthe record straight on the real causes of that episode in Schacht (1967). Specifically, in May 1922 the Allies insisted on granting total private control over the Reichsbank.
...
10.11.2021
DAO Corollary, For Teams # F.K.A. Amdahl’s Corollary
The most efficient way to implement a piece of software is to do it all yourself.
No time is wasted communicating (or arguing); everything that needs to be done is done by the same person, which increases their ability to maintain the software; and the code is by default way more consistent.
Turns out “more efficient” doesn’t mean “faster”. When there are more people working on the same problem, we can parallelized more at once.
...
10.11.2021
All Problems Are Hard # Aren’t all problems hard?
Say a customer reports a bug, and you’ve got to fix it. You can fix it. You know you can fix it. Maybe it’ll take an hour, maybe it’ll take a day, maybe a week. But you’ll narrow it down, figure out the smallest possible increment of work you can do to remedy the problem, and then you’ll do it.
...
14.10.2021
Uniswap V3
10.10.2021
Solidity is an object-oriented, high-level language for implementing smart contracts. Smart contracts are programs which govern the behavior of accounts within the Ethereum state.
10.10.2021
MEV and 1559
02.10.2021
Data Representation in Solidity # For writers of line debuggers and other debugging-related utilities.
#
Purpose of this document # The point of this document is to explain representation of data in Solidity for the purposes of locating and decoding it; more specifically, for writing a line debugger that does such. As such, other information about the type system or data layout that aren’t necessary for that may be skipped; and where location is not entirely predictable but may be determined by other systems of the debugger, we may rely on that.
...
2021.10.25 - Community update # New Developer and Community Hub https://manifoldfinance.github.io/hub/ Starting point and organizational checkpoint for providing updates and engaging with each other Reduce the effort to get updates and find historical updates Reduce the ‘mission creep’ that was happening (multiple different repos for documentation, hard to keep up if casual end user) Reduce effort of formulating and providing updates Mitigating Security Issues # In the course of working with the sushi team, we caught a ‘supply chain attack’ npm package (this was actually apart of an unclaimed bug bounty) A repository is produced here: https://github.
...
DAOsclarosis # on the persistence of faulty models in governance # “Demosclerosis isn’t a problem you solve It’s a problem you manage.”
Jonathan Rauch, DEMOSCLEROSIS
The Silent Killer of American Government, 1994
The DAO Corollary # F.K.A. Amdahl’s Corollary
The most efficient way to implement a piece of software is to do it all yourself.
No time is wasted communicating (or arguing); everything that needs to be done is done by the same person, which increases their ability to maintain the software; and the code is by default way more consistent.
...
async/await is just the do-notation of the Promise monad # source gist
CertSimple just wrote a blog post arguing ES2017’s async/await was the best thing to happen with JavaScript. I wholeheartedly agree.
In short, one of the (few?) good things about JavaScript used to be how well it handled asynchronous requests. This was mostly thanks to its Scheme-inherited implementation of functions and closures. That, though, was also one of its worst faults, because it led to the “callback hell”, an seemingly unavoidable pattern that made highly asynchronous JS code almost unreadable.
...