Builder. Crypto systems, infra and security.

Joined April 2026
Eva has never been just a pet to me. She’s my best friend, my most loyal companion, and probably the creature I love most in this world. But over time, she became something else too. A symbol. She somehow represents a lot of things that have always mattered to me. Even her name makes me think of life. But she’s also a predator. Protection, speed, agility, independence, always alert, and that focused stare that seems to notice everything around her. A few years ago, I had a thought: what if one day she became the symbol of the biggest project of my life? Not just a name or a cool mascot. I wanted the idea behind the project itself to stand for those same things. As you can probably tell from the screenshot below, this didn’t start yesterday. Project EVA already existed back in 2024. There were early plans, job openings, people I was looking for, and something that, at the time, mostly existed in my head was slowly starting to take shape. I’ll leave what happened after that out for now. Maybe Project EVA will actually turn into something big and serious. Or maybe there’s nothing serious about it at all. Just some weird idea from a developer who loves his serval way too much and decided to dedicate something to her. Maybe it’s just for fun and one very long story. Or maybe those of you who’ve been reading my posts for a while are starting to wonder about a few things. Who knows. For now, let’s just call it Project EVA. But I’m genuinely curious. When you look at this screenshot, the name Project EVA, and this whole story, what’s the first thing that comes to mind? What do you think something like this could turn into after a few years? Something actually serious, or just one big idea that ends up going nowhere?
I’ll leave the first part of your comment unanswered for now lol😺 You’re right about the fangs, though. I never did explain why she has titanium fangs. I also never told the story of how Eva ended up living with me in the first place. Eva is an African serval, a real predator. I never wanted a serval, and I don’t think people should buy wild cats just because they want something beautiful or unusual at home. A serval isn’t a toy. But things were different with Eva. This was about six years ago. I was on a short trip, and people nearby had been looking for an escaped serval for several days. People from my country have local group chats wherever they move, and the escape was all over ours. We followed the search too, then decided to help and eventually got in touch with the owners. That’s when we found out they were breeding exotic cats to sell. The escaped serval was an adult male, and we later learned he was Eva’s father. His escape brought way too much attention to the breeding operation. Inspections followed, along with questions about how the animals were being kept and bred. I won’t get into every detail. There was plenty of fucked-up shit going on. The breeders ended up in immigration detention because they were foreigners. At the time, they still had an adult female serval and two very young kittens they were planning to sell. One of them was Eva. The kittens had already been separated from their mother and bottle-fed way too early so they’d get used to people and be easier to sell. By then, both were completely dependent on humans. The escaped male was eventually found. People who knew the breeders took him and the adult female, but the kittens were going to be put down. It all came down to a new law. People who already had these animals before the law took effect were allowed to keep them. Acquiring or keeping new ones was banned, and the kittens didn’t qualify for the exception. At that point, I didn’t see much of a choice. The two kittens had already been born. They were alive, they’d done nothing wrong, and now they were going to be put down because of all this bullshit. I took both of them somewhere it was legal to keep servals. I won’t get into exactly how I pulled that off. Let’s just say it took a hell of a lot of time and money. The stress was even worse. I later gave the male kitten to someone who already had experience with animals like him. He couldn’t take both because two adult servals need a lot of space. The boy is still doing great, and Eva stayed with me. The whole thing started with trying to keep them alive, so I named her Eva. I realized pretty quickly that a serval is absolutely fucking nothing like a big house cat. She’s a predator who weighs over 14 kg, runs fast, can jump almost three meters straight up, and has the temperament to match. But you get attached to her almost instantly. And once you do, you’re responsible for an animal that depends on you for everything. Eva also had health problems. Being bottle-fed so early took its toll, and as she grew, we discovered serious issues with her bone development. We spent a long time going from vet to vet and figuring out her diet. She went through exam after exam and slowly got better. Eventually she got stronger and grew up. For a while, everything was fine. Then the dental problems started, especially with her fangs. Most vets suggested simply removing them. She could live a normal life without them, so medically, that was the easiest option. I didn’t like it. Eva is still a serval and a predator. These problems went all the way back to the beginning of her life. Just removing her fangs now and calling it a day felt wrong. So I started looking for another option. Eventually I found a veterinary dentist who takes on difficult cases. I had to wait several weeks because right before Eva, he’d been working on a bear’s teeth. An actual bear. He examined Eva, and we decided to restore her teeth. She got ceramic crowns on the back teeth. The fangs were more complicated. A predator’s fangs have to withstand much more force, so ceramic wasn’t strong enough. We needed something tougher. That’s how Eva ended up with titanium fangs. She uses them without any problems, including when she eats meat. No one replaced healthy teeth with metal ones just for looks. The damage was already there. Her fangs had to be rebuilt, and we went with titanium. The engravings were my idea. When the fangs were being made, they asked if I wanted anything engraved on them. I figured that since they were going to be titanium anyway, I might as well add something personal. One upper fang has a tiny crown engraved on it. The other has E.L. The E comes from her name, and the L from my last name. Her teeth are fine now, and Eva is doing great too.
191
72
74
358
270,756
大家好 😸 Nice seeing more of Chinese CT around here lately. Saw this message this morning and realized there's one thing that could really speed us up right now. We've been building this thing for a while. still a lot to test before launch One of the biggest bottlenecks right now isn't even code. It's getting to the right people. docs, integrations, edge cases we handle that ourselves. But some things are just way faster to sort out with the people actually building the network. Integration quirks. Weird edge cases. upcoming changes. Or just figuring out where we can actually help each other. Sometimes getting to the right person takes longer than solving the technical problem itself. a few direct intros would save us a ton of time right now. Here are a few teams I'd love to talk to: @ethereumfndn @BNBChainDevs @buildonbase @solana_devs @ton_blockchain @trondao @ArbitrumDevs @Optimism @AvaxDevelopers @0xPolygon @suidevelopers @AptosLabs @NEARDevHub @monad_dev @Scroll_ZKP @LineaBuild @HyperliquidX @StarknetFndn @zkSyncDevs @BuildwithSei @berachaindevs @SonicLabs @Mantle_Official @BuildOnStellar @injective @RobinhoodCrypto This is nowhere near the full list. I keep a working list of 200+ ecosystems, but today I'm only tagging the ones where a direct line would be especially useful right now. If you know someone on any of these teams who handles DevRel, developer support, or integrations, intro us. that would save us a lot of time. Not looking for funding, extra devs, or marketing here... What would actually help is direct contact with the teams. And this doesn't stop with chains. Next in the thread: a few more teams I want to talk to, what I like about their products, and what I'd want to integrate. Still keeping the product details quiet for now.
175
19
1
186
179,984
swaps and liquidity The core dex execution layer is already in place. We're working with public API and SDK already Every team below has a reason to be here. there's a specific use case in the product behind every tag. @1inch @0xProject @De1_ai @KyberNetwork @CoWSwap @VeloraDEX @bebop_dex @EnsoBuild @JupiterExchange @AftermathFi @PanoraExchange @avnu_fi @ston_fi @OfficialSUNio @SoroswapFinance @rhea_finance We're already talking directly wwith some of these teams. we've reached out to others about integration terms, limits, and the quirks of working with their infra. Sometimes it's a technical partnership. Sometimes it's API access, integration support, or upcoming changes. All of that is way easier to sort out with the people actually building the product Especially when there's one specific edge case and you just need a straight answer. If you handle integrations, API, DevRel or partnerships on one of these teams, I'd love to talk. And if you know the right person, intro us😺
68
2
56
11,832
Cross-chain😺 Some teams we're already talking to. Some we're working with through public api and sdk. Some we're still trying to reach and get the access we need Doing it the normal way. Requests Terms Integration talks Cross-chain is messy by default. different networks, different routes, different rules. we're stitching it together. And yeah, when the team is actually one message away, things move a lot faster. and it works both ways. We grow, their infra gets used more. Here are a few teams whose approach I'm especially interested in: @lifiprotocol @SocketProtocol @RangoExchange @squidrouter @AcrossProtocol @RelayProtocol @deBridge @near_intents @mayan @THORChain @Chainflip @StargateFinance @Allbridge_io Native assets. Stables. Different chains. Different routes. None of these tags are random. We've got a reason for every one. We're building either way. A direct line just saves a lot of stupid back-and-forth.
115
8
105
8,129
History was happening right in front of us. while people were catching me up on what I'd missed over the past two weeks, one of the biggest thefts of the year was underway. Yeah, I'm still talking about @bitget getting cleaned out for $387.5m CT is still talking about how Bitget will cover the losses. researchers are digging through blockchains hoping for a bounty, and @zachxbt is already naming the middlemen laundering the stolen cash. (btw, I hope he actually gets paid for his work this time) I'm obsessed with wallets, so I went digging into how this attack was even possible and what the team did when they spotted it. Mandiant and slowMist lay out the attack vector in their reports. Links if you want to read them: img.bgstatic.com/multiLang/e… github.com/slowmist/Knowledg… But after reading them, I've got more questionss about the team's response than anything else... Three times in Bitget timeline. september 24, all utc: 19:05: Risk controls spot a discrepancy and block withdrawal requests. 20:40: The team starts moving funds to cold wallets. 21:44: They shut down withdrawals, including the transaction signing service. 2 hours and 39 minutes between blocking requests and shutting down signing. Were you guys asleep or what? And the thief didn't just leave some signed transactions behind and walk away. After 21:22, he was still looking through logs, checking request statuses, still trying to steal BTC. So requests were already being blocked. And the hacker was still in there, working inside the infrastructure. Take the usdc transfers. at 20:41, 2.6m usdc gets moved out of the hot wallet address on ethereum: etherscan.io/tx/0xb9f716952b… On Avalanche, that same address has 8.6m USDc left after a series of transfers around 20:40. at 20:55, 8.2M of it goes to the attacker: snowtrace.io/tx/0x4d2d95dadf… Why the hell was that money still there? Did you forget about it? Couldn't move it in time? I don't like kicking people when they're down. But for an exchange this size, this looks negligent. You're already blocking requests, you're moving funds, and the hacker is still working inside your infrastructure. Why were millions in usdc still sitting in that wallet for him to take later? Okay, a third-party vulnerability explains how he got in. But how far he could get into your systems and how fast you could cut him off, that's on you. I don't know what the team had figured out minute by minute during the hack. But being ready for shit like this should've been part of your product from day one. My feed is full of people talking about money leaving Bitget. Looks like net outflows hit roughly half a billion dollars in the first 24 hours after they started bringing withdrawals back. And I get it. nobody wants a security crew that's already there but holds back the homeowner while the thieves carry their stuff out. I'm a fan of decentralization. This just made me more sure of it. I want to control my own money and take responsibility for my own decisions. And if you take on the job of holding other people's funds, you're responsible for keeping them safe. (Protecting them, not paying them back.)
Replying to @Jhett_Green
$352m? If that number checks out, @bitget just made it into the biggest fuckups we’ve talked about here today This post was supposed to be satire… but seriously, this is awful. Really hope the team gets it sorted fast They have a Protection Fund, so I’m less worried about user funds. Bearish for the market. a reminder for users to be careful with their keys. and for those of us building, warm and hot wallets need more layers of protection
107
34
8
305
45,135
GM CT 😺 What'd I miss these past two weeks? Who got drained this time? Explain it like you're a dev on the project that got drained and your boss just asked what happened👇🏼
90
18
108
11,509
Today @dexscreener showed me a $4B PENIS. lol my community knows I'm obsessed with the idea of a self-custody trading platform. I post about how I think it should work I've talked about people knowing what they're signing and plenty more. Today it's about the numbers that get them to sign in the first place Was going through issues with different screeners with the team today. opened dexscreener. Trending and the top volume list for the past 24h served me the same token. Suggested I check out a penis. Twice. Thanks. Pool isn't even two days old $62.2m volume, $240m liquidity, almost $4b market cap on the chart, traders showing millions in pnl. Did I miss the meta? Everyone's printing. went to look dexscreener.com/solana/AXTq4… Trade history is full of million-dollar buys and sells. Saw a $24.25m buy. Who put that much into penis? Opened the tx, followed the transfers. The buyer spent $5K. Five fucking grand. There's your whale... solscan.io/tx/C6zgq8Rz5ye8SP… Token launched through @LaunchOnSF, pool on @Raydium, buy through @JupiterExchange. The transfers add up. Where did dex get the millions from? Token has a paid profile. Green Audit; No issues. Open it up: mint and freeze checks. Okay. Who's checking the numbers? Checked 20 more similar tokens. Found mismatches there too. Looked at who uses Dex data: several sites showed the same $62.2M volume for that pool. Meanwhile, Telegram bots are firing off alerts nonstop. I reckon that got expensive for flippers and people running bots. You see volume, whales buying, huge PNLs. Think you should get in. And the $24m whale showed up with $5k. @dexscreener, you tell people to use your data to make investment decisions. I reckon you've made hundreds of millions by now. You sell paid profiles on the promise of credibility. With that kind of money, maybe it's time to sort out the numbers? Where did that $24.25m buy come from? How much can we trust your volume, charts and PnL? We can keep making signing safer. People still need decent numbers to decide whether to hit Buy. DEX Screener did a lot for crypto. Thanks for that. But I don't see it lasting much longer like this. The app people trade through needs to take responsibility for the data on its screen. Just pulling someone else's API and asking the user to sign isn't enough anymore. If a screener turns $5K into $24m, what the fuck do we need it for? n.b : don't buy the token in this post. It's obviously a scam.....
295
28
71
452
33,162
I keep saying this; show people what they're signing Tried @phantom new gasless EVM swap on @base today. Fresh burner. normal EOA. 0 eth. 5 used. Zero approvals. Wallet: basescan.org/address/0x5017B… funding: basescan.org/tx/0x823ed96ce8… Enable smart account delegation. Pay gas in USDC. swap 2 usdc for WETH. Worked. No eth needed. basescan.org/tx/0xc0322baff4… Then Remove account delegation Phantom removed it. Wallet is an eoa again. basescan.org/tx/0x276f3ad62f… Opened @RevokeCash 7702 gone. Two USDC approvals from that same swap still there Near-max // Unlimited to @0xProject AllowanceHolder: 0x0000000000001fF3684f28c67538d4D072C22734 Plus paymaster 0x2cc0c7981D846b9F2a16276556f6e8cb52BfB633: leftover 0.006121 usdc. Dust I signed it. That's the point. Neither spender nor amount showed up on enable, swap review, or remove. I had to open an explorer and Revoke.cash to see what the swap had actually approved. Phantom help article covers 7702, alchemy, temporary delegation, and remove. Not the token approvals. Not the amounts Not that they survive remove.. help.phantom.com/articles/un… @0xProject says AllowanceHolder is formally verified. Fine. 0x.org/enterprise/security-b… Phantom still created a near-max approval, didn't show it, and left it after Remove It has no expiry. Future USDC is covered too. Old approvals already get people drained. @RevokeCash tracks more than $495M stolen through approval exploits since 2020 - revoke.cash/exploits ekubo in May 2026; 31 addresses, about $1.43M lost after a router bug met existing approvals. Different contract The bug came later. The approvals were already there. blog.ekubo.org/the-huff-rout… Tried to revoke both through Revoke.cash. It generated approve(0) Phantom: Not enough ETH. No tx Gasless in. Native ETH to clean up after. Nice. Phantom own guide sends EVM users to Revoke.cash to inspect and revoke approvals: help.phantom.com/articles/37… @phantom, the swap worked. The permission UX didn't. Show both approvals before I sign. Say exactly what Remove clears. Let me wipe the leftovers before you flip the wallet back to EOA.....
440
93
66
532
67,970
I've spent the last few years betting that the wallet becomes the whole trading app,, so "Web3 is dead" is where you lose me. @fomo and @Pumpfun nailed the product loop; see it, buy it, never leave the app. that's a product win. It doesn't mean the old distribution playbook is dead. People aren't dpne with Web3. They're done dealing with the plumbing: chains, bridges, gas, dApp hops. Hide that shit. if the wallet connection step disappears from the screen, great. The uX got better. The wallet and protocols didn't die. But a deposit in every app plus Google/X login? We just moved the mess from chains into apps and put a web2 account next to my money. How is that an upgrade? A wallet can be the whole mobile trading app. I keep the keys and can recover if the app vanishes. If something moves on @BNBCHAIN while my money is on @solana , I shouldn't need another app. Same if it's on @ton_blockchain . One place to check it and trade it. spot, perps whatever. Let the app handle routes, bridges and gas. Apple Pay to fund it, Face ID to unlock. Google/X doesn't need to be the door to my wallet. My wallet doesn't need my identity. i don't want the bank back in the middle.
For crypto founders, the biggest lesson from @fomo and @Pumpfun ascendance is that the distribution model of the last 5 years for apps is moot. Web3 is dead, wallet connect is dead, dApps are dead. The new plan is vertically integrated mobile: hide the crypto mechanics entirely. Single balance across chains, integrated onramp (Apple Pay is king), no bridges, no seed phrases or private keys (sign in with Google or X). For wallet apps themselves, this presents an existential crisis. The user demands simplicity & the feeling of safety. In the past, your wallet was a gateway to crypto. Now, I hold a deposit in each app I use and I don't yet care if they talk to each other. As always, we go through bundling and unbundling cycles. If Phantom and Jupiter and Metamask were bundling, we are now seeing a great unbundling.
252
131
123
496
279,552
Solana won my network poll, so I took the hint and spent some time looking through the latest network changes. the obvious headline is SIMD-0525: the 350ms slot target is now live. Faster slots and the shorter blockhash window have already been covered. I wanted to see what this changes higher up the stack, so I went through the proposal, docs and public protocol code. What I hadn't seen discussed much is what happens one layer above it:: the chain clock moved, while some app logic still reads time through the old 400ms assumption The SIMD warns about this directly. anything measured in slots now covers less real time, and programs that treat slot distance as wall-clock time may need an update Static SDK constants also stay unchanged for now. @switchboardxyz's Solana tutorial gave me the cleanest example: `.max_age(30)` rejects data older than 30 slots and describes that as roughly 12 seconds.. At the 350ms target, those 30 slots are nominally 10.5 seconds. At 200ms, 6 seconds. Same code. Same parameter. Different risk policy. Switchboard is doing exactly what it says. If you meant 30 slots, the rule still does exactly what you asked. If you meant roughly 12 seconds, you don't have 12 seconds anymore. I checked @kamino's public kLend code and found the same handoff. The path starts with Switchboard's last update slot, uses DEFAULT_MS_PER_SLOT to manufacture a timestamp, then checks that against a max age in seconds. the SDK constant is still 400ms, so against the 350ms target the nominal age comes out 14.3% higher. At the 200ms target, it would read as 2x older than it really is. A 30-second policy would trip after roughly 15 seconds of wall time, without anyone changing the policy. The deeper problem isn't the number 400. It's that a risk check silently translates between two clocks. And this is why "just use `Clock::unix_timestamp`" isn't the whole fix. the current time is in seconds, but this oracle update starts in slots Both sides of the check still need to speak the same clock No exploit claim here. The bias is conservative: valid data can look stale sooner. This is an availability risk, not a direct value-extraction path. The important part is that the handoff exists in real code. This is exactly why I keep banging on about the full execution path. The network can report the right slot. The oracle can report the right update. The check can run exactly as written. the final behavior still changes at the handoff between protocol time and real time. This actually makes me like @Solana's staged rollout more. A faster clock is good infra, and every gate gives builders a real checkpoint to catch these assumptions before 200ms. Before the next gate, grep for every `max_age`, staleness check, cooldown, retry and timeout expressed in slots. Did you mean slots or seconds? @bw_solana, should apps stop converting between the two entirely: slots for protocol ordering, timestamped data for wall-clock policy? And if so, what should an oracle expose so apps never have to manufacture that timestamp themselves? SIMD-0525: github.com/solana-foundation… Switchboard example: docs.switchboard.xyz/docs-by… SDK constant: github.com/anza-xyz/solana-s… Public code example: github.com/Kamino-Finance/kl… github.com/Kamino-Finance/kl…
Replying to @m477lander
Okay, now vote. Where should I build it? 👇
53%Solana
32%BNB Chain
9%Base
6%Avalanche
222 votes • Final results
511
161
22
425
164,322
x402 processed 75.4M transactions in the last 30 days. Agent wallets are here, and one question bothers me. Caps and allowlists limit what an agent can do. They don’t prove the transaction matches the user’s intent. Where should the final veto live? x402.org
14%Provider backend
25%Onchain smart account
45%Local wallet policy
15%Human every time
194 votes • Final results
165
106
6
210
45,026
Wallets are getting better at capability controls: Coinbase uses per-call/session caps. MetaMask adds allowlists, simulation, threat scanning and 2FA. Useful. But “allowed” still isn’t the same as “intended.” Coinbase: docs.cdp.coinbase.com/agenti… MetaMask: metamask.io/news/introducing…
63
19
2
97
14,849
My answer: the final veto can’t live inside the same LLM or backend that produced the action. An independent policy layer should compare the final transaction with a user-signed intent before signing. Otherwise the agent is grading its own homework with your money.
122
23
114
12,182
GM from Eva😺. Can't tell if she's taking a shower or checking the water for bugs. either way, she's already doing more due diligence than half the builders in crypto lol How's your morning going?
189
96
31
237
27,295
The “theft” that triggered @Maya_Protocol’s anti-theft path never actually happened. Two legitimate Trade Account outbounds had already gone through on L1, but MAYA failed to match them, marked them missing, and triggered compensation. Then it got a bit awkward. The slasher capped the amount against real balances. The subsidy path then picked up the raw amount again and credited 49.45M CACAO to the pool before the Reserve-to-Asgard transfer had succeeded. The Reserve held around 168K CACAO. The transfer failed. The pool still showed 49.45M. So the anti-theft path booked compensation for a theft that never happened using money that wasn’t there. A 100 CACAO + 100 ARB. LINK add then gave the attacker 99.93% of the pool units. That phantom balance was withdrawn as 48.87M CACAO and 98.82 LINK. @CertiKAlert put the exploit at ~$1.7M. Not ideal for the bit of code meant to protect the pool from theft. This is why I keep banging on about the whole execution path, not one check at a time. Every module can pass its own checks while the system as a whole ends up in a state that should be impossible. Credit where it’s due: trading was halted, full recovery was promised publicly, and the v1.133 fix plus a regression test are in an open MR. That’s the right way to respond after a day like this. So after v1.133, will the full compensation path get one final sanity check? If CACAO never reaches Asgard, the pool can’t account for it as if it did. Or will each module still trust the one before it? MR: gitlab.com/mayachain/mayanod…
Sad news 😕 Will work to fix and recover in full. We carry on. @Maya_Protocol
361
117
38
381
190,513
GM, builders and everyone who cares about crypto security 😺 Someone recently asked me why Eva is chewing on a BNB ball in my header lol Well, it’s not there by accident. I’ve been following BNB Chain for years, and it’s always been one of the ecosystems I’ve followed closely. But the closer I get to launching my project, the more I realize that you don’t choose a chain based on technology alone. For me, it matters just as much whether the ecosystem actually listens to builders. How easy it is to reach the right people, talk about your product and simply start a normal conversation. I still haven’t made a final decision on the chain. This isn’t just another token either. It’s a project I’ve been building for several years, so I can’t just pick a chain at random. If you were choosing a blockchain for your project today, whether it’s a product, infrastructure, utility, a token or something else entirely, which one would you choose? My current favorites are: @BNBCHAIN / @cz_binance @solana / @toly @base / @jessepollak @avax / @el33th4xor Let’s vote below. And definitely tell me in the comments which chain you picked and why. Maybe this post will help me decide where the story of my project begins. There’s a reason I picked these four. Each of them already has something my project needs, which makes the choice a lot harder than it probably looks.
168
52
44
355
83,698
Okay, now vote. Where should I build it? 👇
53%Solana
32%BNB Chain
9%Base
6%Avalanche
222 votes • Final results
54
21
2
94
99,313
I’ll leave the first part of your comment unanswered for now lol😺 You’re right about the fangs, though. I never did explain why she has titanium fangs. I also never told the story of how Eva ended up living with me in the first place. Eva is an African serval, a real predator. I never wanted a serval, and I don’t think people should buy wild cats just because they want something beautiful or unusual at home. A serval isn’t a toy. But things were different with Eva. This was about six years ago. I was on a short trip, and people nearby had been looking for an escaped serval for several days. People from my country have local group chats wherever they move, and the escape was all over ours. We followed the search too, then decided to help and eventually got in touch with the owners. That’s when we found out they were breeding exotic cats to sell. The escaped serval was an adult male, and we later learned he was Eva’s father. His escape brought way too much attention to the breeding operation. Inspections followed, along with questions about how the animals were being kept and bred. I won’t get into every detail. There was plenty of fucked-up shit going on. The breeders ended up in immigration detention because they were foreigners. At the time, they still had an adult female serval and two very young kittens they were planning to sell. One of them was Eva. The kittens had already been separated from their mother and bottle-fed way too early so they’d get used to people and be easier to sell. By then, both were completely dependent on humans. The escaped male was eventually found. People who knew the breeders took him and the adult female, but the kittens were going to be put down. It all came down to a new law. People who already had these animals before the law took effect were allowed to keep them. Acquiring or keeping new ones was banned, and the kittens didn’t qualify for the exception. At that point, I didn’t see much of a choice. The two kittens had already been born. They were alive, they’d done nothing wrong, and now they were going to be put down because of all this bullshit. I took both of them somewhere it was legal to keep servals. I won’t get into exactly how I pulled that off. Let’s just say it took a hell of a lot of time and money. The stress was even worse. I later gave the male kitten to someone who already had experience with animals like him. He couldn’t take both because two adult servals need a lot of space. The boy is still doing great, and Eva stayed with me. The whole thing started with trying to keep them alive, so I named her Eva. I realized pretty quickly that a serval is absolutely fucking nothing like a big house cat. She’s a predator who weighs over 14 kg, runs fast, can jump almost three meters straight up, and has the temperament to match. But you get attached to her almost instantly. And once you do, you’re responsible for an animal that depends on you for everything. Eva also had health problems. Being bottle-fed so early took its toll, and as she grew, we discovered serious issues with her bone development. We spent a long time going from vet to vet and figuring out her diet. She went through exam after exam and slowly got better. Eventually she got stronger and grew up. For a while, everything was fine. Then the dental problems started, especially with her fangs. Most vets suggested simply removing them. She could live a normal life without them, so medically, that was the easiest option. I didn’t like it. Eva is still a serval and a predator. These problems went all the way back to the beginning of her life. Just removing her fangs now and calling it a day felt wrong. So I started looking for another option. Eventually I found a veterinary dentist who takes on difficult cases. I had to wait several weeks because right before Eva, he’d been working on a bear’s teeth. An actual bear. He examined Eva, and we decided to restore her teeth. She got ceramic crowns on the back teeth. The fangs were more complicated. A predator’s fangs have to withstand much more force, so ceramic wasn’t strong enough. We needed something tougher. That’s how Eva ended up with titanium fangs. She uses them without any problems, including when she eats meat. No one replaced healthy teeth with metal ones just for looks. The damage was already there. Her fangs had to be rebuilt, and we went with titanium. The engravings were my idea. When the fangs were being made, they asked if I wanted anything engraved on them. I figured that since they were going to be titanium anyway, I might as well add something personal. One upper fang has a tiny crown engraved on it. The other has E.L. The E comes from her name, and the L from my last name. Her teeth are fine now, and Eva is doing great too.
Replying to @m477lander
If this project ends up being about that security thing you were talking about honestly EVAPEX sounds like the best name. EVA and her titanium fangs is a perfect fit for a guardian. Btw you still havent told me why she has steel fangs? lol that’s such a weird and interesting detail
225
49
64
247
433,997