0xScotch 🥃 (@0xScotch) profile picture

Defi lover. Building @MaltProtocol 🥃 52C0 7058 693C 3A6D 7BAB 9993 0766 5A15 0B5D AB67

Joined December 2020
Photo by 0xScotch 🥃 (@0xScotch)Photo by 0xScotch 🥃 (@0xScotch)Photo by 0xScotch 🥃 (@0xScotch)Photo by 0xScotch 🥃 (@0xScotch)Photo by 0xScotch 🥃 (@0xScotch)Photo by 0xScotch 🥃 (@0xScotch)Photo by 0xScotch 🥃 (@0xScotch)Photo by 0xScotch 🥃 (@0xScotch)Photo by 0xScotch 🥃 (@0xScotch)Photo by 0xScotch 🥃 (@0xScotch)
0xScotch 🥃 retweeted
Anyone dunking on somebody trying to build something is cringe.
177
133
16
1,342
78,046
This is at the core of the thesis behind the new @MaltProtocol system. A dex that that can use the associated stablecoin’s collateral to capture MEV on its own pricing as well as arbitrage against other dexes. Profit goes to increasing collateral and paying LPs Launching soon
Keeping MEV at the app layer is the way we can start seeing profitable apps again and development with sustainable incentives.
4
8
531
Kinda interesting to think about balancing the incentives of companies to make products that sell well against the need for children to engage in challenging things.
This Post is from a suspended account. Learn more
2
1
261
Your focus groups will tell you the kids zone out when its hard. So make it less challenging. Ofc the kids dont revel in the challenge immediately. The whole point of difficulty is you sit with it for a bit. Get bored. Get frustrated. Do smtn amazing because you had the time
95
It would be hysterical if it turned out we reach AGI because developers putting ascii art diagrams in code to explain algorithms ended up giving LLMs enough training tokens to develop spacial reasoning abilities
3
128
I could not agree with this more. We need absolutely cracked gas golfers, but they should be working further down the stack. Expecting every app developer to know all the tricks is a recipe for vulnerabilities
it is embarrassing that we spend time on stack too deep or gas optimizations a la "unchecked ++i" in loops we must focus on writing safe code that can store billions. vulns due to gas optimizations must be treated as a disease and fixed at the tooling layer.
5
205
This is very under appreciated when considering the very long term. There is a balance between needing mutability to allow for iteration and being able to lock in immutability once things are solid. Malt attempts to handle this… 1/4
What's happening with Maker should make DeFi users re-evaluate their assessment of immutability Knowing that a protocol cannot change is immensely valuable: you assess the risk once, you've assessed it forever. Oppositely, mutable protocols require continuous risk assessment
1
2
379
Eventually update roles can be revoked to leave the protocol fully immutable. All without any complexity that comes with upgradable proxies. Hard to overestimate the value of that over decade or century long timelines. 3/4
1
57
Immutability + Lindy is one of the most powerful combos
1
45
This frustration is understandable but misplaced imo. This is the price of open censorship resistance People want to get rich and marketers will sell them that dream The system that stops state level censorship also allows this kind of exploitative grift. Doesn’t make it good…
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
1
2
260
But we have to accept that is part of the deal. Instead of dog complaining about it we should be trying to figure out how to leverage it in our favour. I think this is what @VitalikButerin was talking about in his recent blog
55
I remember…
This quoted post is unavailable.
2
113
We have literally built this. Currently on testnet. Will likely go live next month some time
Discussion on protocol-captured backrunning profit on Uniswap reddit.com/r/UniSwap/comment… Osmosis is already doing this via ProtoRev members.delphidigital.io/lea…
1
12
290
Anecdotally this is true in my experience too. UK just doesn’t pay engineers well so those that can, make the jump into finance. Has been true for decades Many that stay in engineering see consultancy as an end goal for the same reason. Very few decide to start companies
Met a British startup founder today who'd studied engineering at Oxford. He said the majority of his fellow students had since gone into finance or consulting. In effect there is a brain drain *within* the UK, as engineers emigrate to fields where they don't build anything.
1
181
0xScotch 🥃 retweeted
‘Progress is not motivated by money. Progress comes from those who are happy to embark on a course of action without quite knowing where it will lead, without doing a feasibility study, without fear of failure or too much hope of reward.’
41
110
21
1,000
134,487
I started in the hardware world and then got into SV software before entering defi. Can confirm this take is accurate. Move fast and break things results in: 1. Big losses (I learned this the hard way) 2. Cutting corners on immutability mostly defeating the benefit of blockchain
Q: How can I write more secure Smart Contracts? A: By understanding this key principle: Smart Contracts are NOT SOFTWARE. Smart Contracts are HARDWARE. “Alex, WTF are you talking about?”… hear me out… For the past 20 years, writing software has meant iterating quickly: Getting an MVP out there ASAP, moving fast, and breaking things. So, what happens when something goes wrong? UI misalignment? No worries: 10-minute hotfix. 404 error? Release a patch. Impact: Low, Cost to fix: Low. Software Engineers and Product teams approach software this way because it works. When the impact of issues is low, and the cost to fix them is low, the rapid feedback loop of agile development is extremely effective. The benefits outweigh the drawbacks. It’s a no-brainer. Consider Hardware. Developing Hardware is a very different experience. There’s no rapid feedback loop or moving fast and breaking things. When something goes wrong, the impact is NOT low. Phones combust in pockets. Planes go down. Rockets blow up. How do these issues get fixed? Total recall, or sometimes, they just don’t. Impact: High, Cost to fix: High. The process of idea to execution of a new piece of hardware looks nothing like the process of moving fast and breaking things. Every minute detail is mapped out and thought about way ahead of time. The testing/QA process is rigorous and grueling. There is no fallback. It needs to be right the first time. When you think about Smart Contracts, which of these two buckets do they naturally fall into? In Web3, when a Smart Contract has an issue, the impact is not just a disgruntled user, it’s often millions and, in some cases, billions of dollars. Fixing it is not a 10-minute hotfix, it’s a locked protocol, emergency upgrade (lol hello governance/more_bugs/centralization/etc), or no fix at all. Smart Contracts are hardware. Don’t take my word for it, the evidence is already here. Look at any of the major Blue-Chip Defi protocols that have lasted more than a couple of years. It’s clear that the development approach is similar to Hardware manufacturers. Uniswap was a research paper well before any Solidity was written. Chainlink Labs releases research papers for every primitive they create, well before writing the software. AAVE is formally verified! If you approach Smart Contract development with a “Move Fast and Break Things” mindset, you’re already doomed. This is the first mistake engineers make when they come into Web3 IMO. Approach developing Smart Contracts like Intel approaches chip manufacturing. Smart Contracts are Hardware.
2
143
Periodic reiterations of these ideas from people like @VitalikButerin are immensely valuable. It’s easy to forget that not everyone that enters the ecosystem is aware of these ideals we are building upon. Bringing them back into focus from time to time will keep us on course
1
108
This is what it’s all about. Never forget why we are all building. Let’s all play positive sum games over the long term
This quoted post is unavailable.
117