TradFi to DeFi
Joined December 2012
- Tweets 775
- Following 776
- Followers 216
- Likes 400
160 Photos and videos
These guys put out a really good stablecoin payments piece. HTF aren't they here on CT? #Crypto #Decentralized #Payments
This is such a big deal. So obvious we will get there where finance lives 100% on chain, including day to day purchases, real estate, all investment types, AI helping to push through the changes in software enhancements, but the path dependency is just wild on how we get there. The risks are the regulatory climate changes, the CLARITY Act doesn't get through, how payment incumbents like Visa & Mastercard are able to adapt and work with crypto issuers and strategize on what their businesses are going to look like to survive, how banks fight back, how fast Mr. Beast turns young investors into the self-banked where it is all they know. And they won't know. It will just work.
Enough blabbering, here it is:
research.artemisanalytics.coβ¦
Subscribe to Artemis Big Fundamentals, by @Artemis__xyz research.artemisanalytics.coβ¦
1
182
THIS IS ENTERTAINMENT AT ITS FINEST π€―πΏ#ppa #pickleball #ppatour #sports ... youtube.com/shorts/VnurUxTt-β¦ via @YouTube
188
Why βdecentralizedβ doesnβt mean βsafeβ
Centralization concentrates risk in people and institutions.
Decentralization redistributes risk across code, incentives, and users.
Centralized systems ask you to trust who is in charge.
Decentralized systems ask you to trust that the system works as designed.
31
David Malan explaining pointers in feels like watching someone calmly defuse a bomb while explaining the molecular structure of the wire. @davidjmalan #cs50
49
These LLMs are so heartwarming and full of Holiday glee lol:
note: true story though:
Claude chat:
WHAT'S UP DUDE?
Limit reached Β· resets 4am (UTC)
WHAT TIME IS IT EST?
Limit reached Β· resets 4am (UTC)
DAMN SUPER COLD, WELCOME TO THE FUTURE EVERYONE
Limit reached Β· resets 4am (UTC)
HAPPY NEW YEAR THANK FOR ALL THE HELP THIS YEAR, YOU REALLY HELPED ME A LOT AND CHANGED MY LIFE FOR THE BETTER
Limit reached Β· resets 4am (UTC)
LOL
32
$_
Please see the attached use case. This is another one that helps when there are long directory names.
Breakdown:
!! β the previous command
:$ β the last argument of that command
So !!:$ literally means:
βTake the last argument of the previous command.β
Same result, more syntax.
When to use which (mental model)
$_ β fast, readable, muscle-memory friendly
!!:$ β precise, composable, history-hacker energy
Most people settle on $_ and never look back.
Bonus: chaining like a civilized wizard
You can even do:
mkdir 51-final-project && cd $_
One line. No repetition. Clean intent.
29
The Pointer Confusion Pattern
THE RULES:
βββββββββββββββββββββββββ
& means "get the address of" (produces a pointer)
* means TWO different things depending on context:
In a TYPE: *int means "this is a pointer to int"
In an EXPRESSION: *ptr means "follow this pointer"
βββββββββββββββββββββββββ
This dual meaning of * is the single biggest source of confusion. Let's be explicit:
(go)
var ptr *int
// DECLARATION: ptr is of type "pointer to int"
// The * here is part of the TYPE
// ptr can hold an address
value := *ptr
// EXPRESSION: dereference ptr, follow the arrow
// The * here is an OPERATOR
// We're reading what ptr points to
19
You heard it here first. My prediction is that BTC will have a colossal downturnβI'd say to zero if forced to give a price target. Thinking from first principles, Bitcoin cannot hold value long-term. It has zero utility. It was marketed as digital gold, but that doesn't make it digital gold. This has to be the craziest psychological experiment ever implemented. Full manifesto to come...
1
116
Grok's Crypto to Historical Figures:
1. Bitcoin β Leonardo da Vinci
Innovation, enduring influence, simple yet profound.
2. Ethereum β Nikola Tesla
Visionary infrastructure, complex ambition, legacy of empowerment.
3. Solana β Alexander the Great
Speed & scale, bold ambition, growing pains.
42
Yesterday: Solidity 0.8.0 made overflow revert by default.
Today: when to actually use unchecked {}
The default (checked math):
Every , -, * gets overflow validation
Compiler inserts: "did this wrap?" β revert if yes
Costs ~20-40 extra gas per op
unchecked {} = "I know this won't overflow, skip the checks"
Classic pattern β loop counters:
solidity
for (uint256 i = 0; i < arr.length; ) {
// do work
unchecked { i; }
}
Why safe: i starts at 0, increments by 1, bounded by arr.length. Physically cannot overflow before exit.
Gas savings: ~20 gas/iteration. 1000 iterations = 20k gas. Your users will thank you.
When to NOT use unchecked:
User-supplied inputs
Token amounts
Anything you haven't personally reasoned through
unchecked isn't "yolo mode" β it's "I've done the math" mode.
27
Why did Solidity get such a massive upgrade in 0.8.0 and why have we been on 0.8.x for ~5 years?
Pre-0.8:
β’ uint256 math silently overflowed
β’ SafeMath was βrequiredββ¦ until someone forgot
β’ One missed check = blown-up protocol
Solidity moved fast back then:
β’ 0.4.x β ~2 years
β’ 0.5 / 0.6 / 0.7 β ~1 year combined
Then 0.8.0 (Dec 2020) dropped.
What changed:
β’ Overflows revert by default
β’ Unsafe math requires unchecked {}
β’ Risk became explicit, not accidental
β’ Better errors, typing, and failure signals
0.8 changed Solidityβs default posture:
safe by default, sharp edges opt-in
Thatβs why it stuck.
You donβt churn versions after fixing the biggest class of bugs.
27
Solidity Nested Mappings Visual:
Example:
`allowance[owner][spender] = 500;`
Slot 1 is the anchor (empty)
β
hash1 = keccak256(abi.encode(owner, 1)) β intermediate (also empty!)
β
hash2 = keccak256(abi.encode(spender, hash1)) β ACTUAL storage slot
β
SSTORE(hash2, 500)
No pointers. No nested structs. Just hashes.
21
Solidity nested mappings using ERC-20 "allowance" example:
contract ERC20 {
// Who owns how many tokens
mapping(address => uint256) public balanceOf;
// owner => spender => amount they're allowed to spend
mapping(address => mapping(address => uint256)) public allowance;
}
25
Yesterday: mappings are just hash lookups.
Today: why this design, how to track keys (on and off-chain)
There's no "directory" of which slots are used. The EVM only knows: "read slot X" or "write slot X."
Why no iteration?
To iterate, you'd need a list of keys. But storing that list means:
Extra SSTORE per insert (~20,000 gas)
Growing array = more slots = more cost
Deletion becomes expensive (swap-and-pop or leave gaps)
Mappings chose: O(1) access, zero overhead, no iteration.
When to track keys on-chain
Track on-chain when:
Contract logic requires iteration (distribute to all holders, enumerate NFTs), small, bounded sets (< 100 items typical), writes are infrequent
```solidity
mapping(address => uint256) public balances;
address[] public holders; // explicit key tracking
function deposit() external payable {
if (balances[msg.sender] == 0) {
holders.push(msg.sender); // first deposit = new key
}
balances[msg.sender] = msg.value;
}```
Track off-chain when:
Large/unbounded sets, iteration only needed by frontends/indexers, gas optimization is critical
Emit events, index with The Graph or your own indexer:
```solidity
event KeyAdded(address indexed key);
function deposit() external payable {
if (balances[msg.sender] == 0) {
emit KeyAdded(msg.sender); // ~375 gas vs ~20,000 for SSTORE
}
balances[msg.sender] = msg.value;
}```
21