anshdeep.eth (@singh09_a) profile picture

Core Contributor @Kheldotfun | Blockchain & zk Enthusiast | @MidnightNtwrk Build Club | NIT Jalandhar | GSoC@Stability Nexus

Joined May 2022
Photo by anshdeep.eth (@singh09_a)Photo by anshdeep.eth (@singh09_a)Photo by anshdeep.eth (@singh09_a)Photo by anshdeep.eth (@singh09_a)Photo by anshdeep.eth (@singh09_a)Photo by anshdeep.eth (@singh09_a)Photo by anshdeep.eth (@singh09_a)Photo by anshdeep.eth (@singh09_a)Photo by anshdeep.eth (@singh09_a)Photo by anshdeep.eth (@singh09_a)
🎉 Thrilled to share that Oblivion Protocol made it to the top 16 at Midnight Summit in London🇬🇧 Despite visa issues keeping me from attending the summit in person, participated remotely and proud of what we built 🚀 Thank You @MidnightNtwrk for this opportunity
2
8
526
anshdeep.eth retweeted
We tend to make decisions based on data that is easy to collect, not data that is most representative. This is availability bias, and it has a massive influence on how our systems are built. A classic example: you profile your application and see a slow database query in the logs. It is visible, it is measurable, it is right there. So you optimize it. But the real bottleneck might be network latency or an upstream service timeout that is harder to instrument and therefore never gets investigated. The data you do not have does not show up in your dashboards. So you end up optimizing for what you can see, not what actually matters. This shows up in on-call decisions too. Incidents that trigger noisy alerts get attention. Silent degradations - the ones slowly eroding p99 latency or quietly increasing error rates below the alert threshold - go unnoticed until they become a larger problem. The fix is not to collect more data, but rather to ask this before making a decision: "Does this data represent the actual problem, or is it just the data that was easy to get?" The most crucial metric might be the one you are not measuring. Hope this helps.
10
6
141
8,979
anshdeep.eth retweeted
Big milestone unlocked ! @kheldotfun has crossed 3,500+ Proofs in its Proof Tournament powered by @ZKVProtocol ⚡ The future of provably fair gaming is here, and the numbers don't lie. 3,500+ proofs generated. Life is a Khel 🃏 Visit ---> Khel.fun
7
5
1
21
1,596
Glad to be part of Build Club with our 𝙥𝙧𝙤𝙤𝙛 𝙤𝙛 𝙙𝙖𝙩𝙖 𝙙𝙚𝙡𝙚𝙩𝙞𝙤𝙣 project🤘
Build Club Cohort 0 has wrapped, and the results are in. From digital identity to RWA protocols, 10 international teams just created privacy-first products that are ready for investment. Dive into the projects: midnight.network/blog/empowe…
1
11
anshdeep.eth retweeted
This 30-minute speech by the Head of Anthropic "Coding Agents" researcher will teach you more about vibe coding than 100 paid courses. Bookmark it & give it 30 minutes today. This video will change the way you use AI forever,
This weather bot turned $300 → $122K on Polymarket weather markets in 3 months I fully decoded algo and built a self-learning Hermes weather trading agent using weather APIs + Opus 4.7, the bot runs 5-min scans & searches mispricings on Polymarket run your agent in 5 steps: • set up a VPS server on Hetzner - $6 • create a weather API on {visualcrossing} - free • set up Hermes agent using one-liner code - free • connect Telegram bot + Opus 4.7 • send {weather trading logic} from article to agent started my agent 2 days ago with a test sum and already having 40% profit agent already caught 2 traders with +400% ROI on Seoul & Chicago weather markets bot used for logic: polymarket.com/@coldmath?via… my bot test wallet: polymarket.com/@hermesweathe… Hermes bot is a self-learning agent so give him enought trades {100+}, to build his own logic. start small
83
959
41
9,591
1,605,460
anshdeep.eth retweeted
Every engineer I know has asked this at some point: "How deep should I actually go?" According to me, the decision to go deep down the rabbit hole comes down to two things: 1. curiosity - what genuinely pulls you in 2. career direction - where you want to be in the next 2/3 years, not where the internet says you should be My honest take: depth works best when it serves at least one of those. Ideally, both. If something aligns with your career direction, going deep is an obvious win. One simple way to test this is to think in 2/3 year windows and ask yourself: Does understanding this layer actually move me closer to where I want to be? If you are building web apps, you do not need to master CPU instruction sets. If you are working on databases, B-tree internals matter far more than knowing every Linux kernel detail. Context changes what "deep" really means. Abstraction layers exist for a reason. They let you build without getting overwhelmed. A frontend engineer who understands HTTP is usually more valuable than one who has memorized TCP packet headers but struggles to ship features. If something does not align with your career direction, curiosity still matters. Learning out of pure interest is not wasted time. You do it because it optimizes for motivation, long-term learning, and happiness. What does not make much sense is going deep in areas that serve neither curiosity nor direction - often driven by comparison or fear. So keep checking in with yourself. Ask questions. Course-correct often. Depth is most powerful when it is intentional.
18
75
5
879
37,913
Big news! 🎉 I've officially been accepted as a Candidate in the Midnight Aliit Fellowship. Excited to join this amazing community of builders and advance digital privacy on @MidnightNtwrk. Looking forward to become Aliit fellow🚀
3
135
anshdeep.eth retweeted
Nobody knows what things will look like 4 years from now, and there isn't a single right answer. It is uncertain for everyone. But what I strongly believe is ... Everyone has a thesis - or at least, it helps to have one - and then act on it in your own way. For example, - if you think you might not have a job, money-max now - if you believe SaaS is dead, and you work there, switch - if you think fintech is going to stay, move closer - if you think vibe coding tools won't last, don't join one - if you feel depth beats breadth (or vice versa), go all in - if you think distribution would be important, build one You might be wrong - and that's okay. No one gets this perfectly right. What matters is taking the time to think it through and form your own view. By the way, this is exactly how I made my last career move. I had a view that fintech would keep growing in importance, and that being close to money movement and financial infrastructure would help me learn faster and stay close to AI (in the areas I care about). That's what led me to join Razorpay. I could be wrong, and I am okay with that. I would rather make a thoughtful bet than stay unsure. If you are feeling stuck, you are not alone. Millions are going through the same right now. To me, it often just means you have not formed a clear point of view yet. Take your time. Build one. Then act.
46
86
6
1,375
53,689
🔥 Midnight Mainnet is LIVE! What an incredible journey — from testnet days to the genesis block and now officially entering the Kūkolu Phase in the @MidnightNtwrk ecosystem! Proud to have watched this privacy revolution unfold. The real build begins now. Let’s Build!
1
90
anshdeep.eth retweeted
NEW: Dev Academy 301 - Advanced Applications Build your first Zero-Knowledge DApp end-to-end on Midnight. Learn how proof generation, shielded contracts, and full-stack integration come together in practice. Start here 👇 academy.midnight.network/cou…
21
60
8
314
12,816
anshdeep.eth retweeted
JUST IN: UK challenger bank Monument to tokenize up to £250M in retail deposits on @MidnightNtwrk, marking the first time a UK-regulated bank has tokenized deposits on a public blockchain while keeping them FSCS-protected and interest-bearing.
642
769
55
1,980
88,089
anshdeep.eth retweeted
How do fungible and non-fungible tokens work on Midnight? @olanetsoft breaks it down for builders: 🛠️ How tokens work in Compact 🛠️ Key differences from Ethereum 🛠️ How token operations interact with ZK proofs 🛠️ Where unshielded vs shielded tokens fit in Midnight’s architecture
9
48
5
261
10,972
Big news for @MidnightNtwrk: Canada's oldest qualified digital asset custodian @balance_canada just announced they're ready to custody $NIGHT tokens from block 1 when Midnight mainnet launches (late March 2026). 🚀 This is huge for institutions. Thread 👇
Balance (@balance_canada) is the first digital asset custodian ready to support NIGHT. From Glacier Drop to early NIGHT custody and now mainnet readiness, their work reflects a long-term commitment to building institutional infrastructure for Midnight. 🤝
1
2
137
Key line from Balance: "We're prepared to facilitate NIGHT token movements the moment the first block is minted." Translation: Institutions can hold, move, stake, trade $NIGHT right at genesis — no "wait-and-see" delays.
1
1
37
With regulated custody ready Day 1, serious money can flow in fast → better liquidity & adoption. This screams momentum: Real institutional plumbing built before launch. What do you think — will $NIGHT see big flows early? @MidnightNtwrk @balance_canada @midnightfdn
1
38
anshdeep.eth retweeted
Scrum meeting added to the OpenClaw office. Agents walk into the meeting room and report their progress in real time. Task management on another level. Standup meetings with your AI engineers. 🔊 Sound on
128
111
41
974
142,779
$NIGHT is now available on world's largest crypto exchange. 💯
Binance now supports NIGHT. 🕛 As the largest global exchange, @Binance is helping bring NIGHT to a wider audience, allowing more users to begin engaging directly with the Midnight network. This integration strengthens NIGHT’s reach and accelerates the adoption of rational privacy across Web3.
1
3
99