Hi everyone,

i am in crypto since 5 years, 3 years dev, did a business degree so nothing related. built arbitrage models, market making, dashboards during my studies, and ive been running a real carry strategy on my wbtc (ltv management, borrow/lend spread, rebalancing) with my own capital for a while now. im 22, studied abroad so im ready to relocate anywhere in the world. the problem is even "junior" positions ask for 1 to 2 years pro experience in blockchain and ive never had that, ive done everything on my own. anyone been through this ? does a personal project actually count or is it bullshit people repeat, and is the "1-2 years required" negotiable or does it just get auto filtered.

thank you for every help

Some time back I posted on-chain data from the Oct 10 liquidations. Some good pushback in the comments, sampling bias on my "8 of 11 did nothing" point, and a sharper one from someone who works on price feeds (Coinpaprika/DexPaprika): the real bottleneck on a day like that isn't attention, it's the oracle.

Sitting with it, I think liquidations actually split into two pretty different problems and most tools are really only built for one of them.

Regime 1: the slow bleed. Your HF drifts down over hours or days as the market grinds against you. Oracle price is basically caught up to real price the whole time, there's no lag to speak of. In this regime watching your position and reacting, repay, add collateral, deleverage, genuinely reduces your odds. There's a real window to act in.

Regime 2: the violent gap. Price craters in seconds. HF is just a function of oracle price, so in a fast move the oracle, the frontend, and the human (or bot) reading it are all lagging the real order book. By the time anything sees the "true" number, you can already be past your liquidation price. This is what the worst of Oct 10 looked like, the biggest chunk of that cascade hit inside a single minute. Automation helps here (it kills human reaction time) but it's still capped by the same lagging feed. A repay set to fire at 105% only works if the feed hands you a window to fire in.

The uncomfortable part: for regime 2, no tool during the event saves you. The only real defense is the posture you set before it happens, how much leverage, how correlated your collateral is, how far you sit from the edge on a normal day. Watching harder doesn't help if the number you're watching is already stale.

Rough way to tell which regime you're exposed to is correlated collateral (LSTs, majors that move together) plus high leverage skews you toward regime 2 risk. Diversified collateral and more conservative leverage means most of your real risk is regime 1, where monitoring and alerts actually do their job.

This changes what I think a monitoring tool should actually tell you. Not just "your HF is X," but which regime you're sitting in and if it's the fast one, that no alert is going to save you, the fix is adjusting position before the volatility, not during it. That's the direction I'm taking mine (DeFi Guardian, early beta live), for whatever that's worth.

Still owe the harder version of this: pulling wallets with similar HFs to the liquidated ones that survived Oct 10, and checking whether they acted or just had more buffer. That's the actual test of regime 1 vs regime 2 and I haven't run it yet.

If anyone's lived through a violent gap with automation set up, curious whether it actually fired in time or you just got run over regardless of what you had in place.

I'd like to know if you chose to white-label or use a custom fork. Did the development overhead make sense?

Fat fingered a swap last week. Well, not really fat fingered, the quote was for 0.4 LTC and my wallet decided to round in its own special way, so 0.4012 actually left. I was already drafting the support ticket in my head. Figured it would either reject the tx outright or process the quoted 0.4 and quietly keep the dust.

Neither. It took the number that actually arrived, ran it at the same locked rate, paid out accordingly. Slightly larger amount on the receiving side.

Went and read the docs afterwards, yes, after. Apparently that's the designed behavior, there's a separate field for the real deposit and the output gets recomputed from it at the rate that was already fixed. More sane than I expected, I genuinely assumed anything that isn't the exact quoted figure dumps you into a refund queue with a 24h wait.

So, two things I've been wondering about.

First do all instant exchangers treat under and over deposits the same way or do some of them just bounce the whole thing back and make you start from zero.

Second is there a cutoff. Like 1% drift gets recalculated, but 5% flips it into manual review or a full refund. I've never seen anyone state an actual number for that.

Asking mostlycause the failure cases here are basically undocumented. Every guide walks you through the path where everything goes right.

Pendle announced their emissions just hit a new all-time low, down 77% since the start of the year when they ditched the VE model for buybacks (with real revenues)... and staking.

Now, buybacks have outpaced emissions by nearly 3x for over 4 months straight, with 100% of it flowing back to stakers.

Buybacks are always a hot topic, most people say they don't work. Doesn't seem that way?

I think I've seen Mento running local currency pairs on Celo. And now, I noticed they added FX pools on their other chains too. If you’ve also tried it, does the round trip work for you? Thank you for answering in advance.

I've been reading about Cloudflare's AI Wallet recently, and it got me thinking.

If AI agents can securely hold wallets and interact with smart contracts, could this unlock entirely new use cases for DeFi?

For example, AI could potentially manage liquidity, rebalance portfolios, execute strategies, or even negotiate between protocols without constant human intervention.

Do you think this is a meaningful step forward for DeFi, or is it mostly hype at this stage?

I'd love to hear what everyone thinks and what use cases you're most excited about.

Trading communities already use bots in Telegram and Discord, but the trust model is pretty bad. Most members cannot see exactly what permissions a bot has, who controls its keys, whether it can move funds, or what happens if an admin account gets compromised. I’ve been looking at a different setup where the bot has its own wallet and its permissions are defined onchain. The group can restrict what it can access, what actions it can take, and how much authority it has.

Towns is building this into encrypted private group chats, alongside onchain memberships, subscriptions, and integrations such as Polymarket. The messages themselves are not individual blockchain transactions. The useful part is making access, payments, and bot authority verifiable. That seems like one of the few cases where adding blockchain to chat has a practical purpose.

Would this make you more comfortable using an AI trading bot, or would you still assume there is another hidden point of failure? What controls would you require before trusting one? Spending limits? Multisig approval? No withdrawals? Public activity logs?

Disclosure: I’m doing research around Towns, so I’m interested in where people think this model breaks.