Twitxy Saved

taek.eth

Verified account This account is verified. Learn more

@leekt216

대한민국 서울 taek.tech Joined March 2019
776 Following 1.6K Followers 428 Posts

Latest posts 5

taek.eth Verified account @leekt216
Worst thing AI has done to ethereum space is not hack, it's the fact that some sloppy EIP/ERC can be vibe-written to call dibs on the idea and the writer doesn't give a fuck afterwards about the quality of it and I have to read it through anyway

For god sake this should end now
7 replies 5 reposts 47 likes 3.3K views View on X
taek.eth Verified account @leekt216
If you think this is only happening to foreigners in korea, you are wrong
this shit happened to me few times already

When i received payment with usd few years ago, it took me whole 2 weeks to receive the money in "lawful" way

Bank even told me to just forge the document as that's what people were doing usually(but i didnt)

And i had to wire USD for investment, it took me whopping 1 month to sort things out, they simply didnt allowed me to use my money

Welcome to korea 🫡

ps, wise and stripe doesnt work here
Dan Nunn Verified account @danyay Oct 29
Day 3 in the adventures of transfering $20k to my Korean bank (and also reporting it to the government)

I need to send a "Certificate of Bank Balance" to the Korean government. Hana Bank requires you to pay 75 cents and install spyware to print their damn certificate, which locks you into printing to a physical printer (I don't have one, but I used to, so the drivers still exist on my Mac).

I can't even screenshot this app, and it won't start with any screen recording enabled lol, so I had to capture it from iPhone.

Anyway, I sent it to my nonexistent printer's drivers since there was no Save to PDF, paused the job, spun up ChatGPT and had it write a script to snipe the PDF off the print queue.

Worked like a charm, and shows the futility of all these Korean bank restrictive apps.
View quoted post on X
7 replies 3 reposts 50 likes 11K views View on X
taek.eth Verified account @leekt216
"bigname, but small"

someone asked me to connect ens bigname indexer to skim. And it is a good example for skim as it only reads few addresses

it worked, but the full setup was too heavy for my Oracle free-tier VM. the indexer was much bigger than skim itself.

so i made smallname.

skim already keeps state locally and runs eth_call, so maintaining another full current-state projection felt unnecessary for this setup. smallname reads owners, records and expiries directly through skim, with a small SQLite index for discovery and history.

it follows bigname’s /v1 API shape, but trades its broader indexing setup for direct contract reads and fewer features. about 1,700 lines of JS, one SQLite file, one skim node.

in my Sepolia tests after catch-up, cold lookups took around 0.5–1s, dropping to tens of milliseconds once the state was local.

the limits: Sepolia only, no full feature parity, and history starts no earlier than Glamsterdam, depending on what peers still serve. live reads use one block hash per response, but lists can miss names while the index catches up.

try it: smallname.taek.tech

smallname: github.com/leekt/skim/tre…

bigname + skim integration: github.com/leekt/skim/tre…

enjoy!
4 replies 0 reposts 11 likes 755 views View on X
taek.eth Verified account @leekt216
In case anyone curious, i was able to run full status of contract for 200mb of ram compared to ~7.5gb using traditional client's full node

And ~1mb disk space with 2min to sync
taek.eth Verified account @leekt216 Oct 15
I started writing smart contracts in 2018, and one thing always bothered me: why did running my own RPC mean running a full node, or an archive node if I wanted historical state?

My app only cared about my contracts, a few dependencies and some ERC20s. Why did I need to keep up with everything everyone else was doing on Ethereum just to serve those reads?

The annoying part was keeping that smaller set of state up to date. Reading a value at one block was doable, but knowing what changed in the next block meant executing it or asking a node that had. A transaction could reach my contract through several other contracts, so just filtering transactions by their destination wasn’t enough.

I mostly forgot about it. RPC providers got reliable enough for what I needed, and I had other things to build. I still didn’t love the setup, but it stopped being something I spent time thinking about.

Then over the weekend, I was looking through Glamsterdam’s EIPs and realized block-level access lists might make this practical.

BALs include the state changes made during a block, including the new values, and the block commits to that list. So once you have the initial state you care about, you can follow its changes without re-executing every transaction.

So I started vibe coding it. It’s called skim.

You tell it which accounts and storage slots you care about, or let it discover the state your simulations read. It fetches the initial values from Ethereum’s P2P network through SNAP, checks their Merkle proofs, and keeps them updated using BALs. Your eth_calls then run locally. If a call needs something it hasn’t fetched, it gets that from peers too, just with more latency. No upstream RPC provider for those reads.

It can also keep historical versions of the state you’re tracking. That was another thing I wanted: being able to query my app’s past state without keeping everyone else’s history. It exposes a JSON-RPC interface, so existing tools can use it for the methods it supports.

It still receives full payloads and BALs. The state it maintains is selective, not everything it downloads. There’s also a consensus light-client implementation now, but that path isn’t active on Sepolia yet because the required Gloas light-client data isn’t being served by the peers tested so far. For now, the head is still trusted.

It’s still an experiment, and I’m working through correctness bugs and longer-running tests. I’m not presenting it as a production node replacement.

But it’s pretty satisfying to finally build something around a complaint I’ve had since 2018. I wanted a small client that knows the parts of Ethereum my app actually uses, and that’s what I’m trying to make.

github.com/leekt/skim
View quoted post on X
1 replies 0 reposts 27 likes 1.1K views View on X
taek.eth Verified account @leekt216
I started writing smart contracts in 2018, and one thing always bothered me: why did running my own RPC mean running a full node, or an archive node if I wanted historical state?

My app only cared about my contracts, a few dependencies and some ERC20s. Why did I need to keep up with everything everyone else was doing on Ethereum just to serve those reads?

The annoying part was keeping that smaller set of state up to date. Reading a value at one block was doable, but knowing what changed in the next block meant executing it or asking a node that had. A transaction could reach my contract through several other contracts, so just filtering transactions by their destination wasn’t enough.

I mostly forgot about it. RPC providers got reliable enough for what I needed, and I had other things to build. I still didn’t love the setup, but it stopped being something I spent time thinking about.

Then over the weekend, I was looking through Glamsterdam’s EIPs and realized block-level access lists might make this practical.

BALs include the state changes made during a block, including the new values, and the block commits to that list. So once you have the initial state you care about, you can follow its changes without re-executing every transaction.

So I started vibe coding it. It’s called skim.

You tell it which accounts and storage slots you care about, or let it discover the state your simulations read. It fetches the initial values from Ethereum’s P2P network through SNAP, checks their Merkle proofs, and keeps them updated using BALs. Your eth_calls then run locally. If a call needs something it hasn’t fetched, it gets that from peers too, just with more latency. No upstream RPC provider for those reads.

It can also keep historical versions of the state you’re tracking. That was another thing I wanted: being able to query my app’s past state without keeping everyone else’s history. It exposes a JSON-RPC interface, so existing tools can use it for the methods it supports.

It still receives full payloads and BALs. The state it maintains is selective, not everything it downloads. There’s also a consensus light-client implementation now, but that path isn’t active on Sepolia yet because the required Gloas light-client data isn’t being served by the peers tested so far. For now, the head is still trusted.

It’s still an experiment, and I’m working through correctness bugs and longer-running tests. I’m not presenting it as a production node replacement.

But it’s pretty satisfying to finally build something around a complaint I’ve had since 2018. I wanted a small client that knows the parts of Ethereum my app actually uses, and that’s what I’m trying to make.

github.com/leekt/skim
github.com GitHub - leekt/skim: Application-specific Ethereum state client: sync (and archive) only the state... Application-specific Ethereum state client: sync (and archive) only the state your app needs, straight from P2P. BAL-driven, verified, local eth_call in ms. - leekt/skim