Md. Rejwar Rahman Rifat

Rust 🦀 || DSA

[Md. Rejwar Rahman Rifat @rejwar]

@sabinaahmed22 @Change Mam , May I get your linkedin account ?

[Md. Rejwar Rahman Rifat @rejwar]

@Ayussheth in

[Md. Rejwar Rahman Rifat @rejwar]

@SuperteamDE Reserve your spot now: 👉 https://t.co/m4VlV3FIT1

[Md. Rejwar Rahman Rifat @rejwar]

⏰Berlin is about to see the biggest Solana Event in Germany’s 🔥
On June 13, 2026, the event will land at the stunning Spreespeicher on the River Spree.
🤯This event can change your thoughts about the Great AI job market Displacement. may give new Hope
@SuperteamDE

[Md. Rejwar Rahman Rifat @rejwar]

‼️Who should join the event?

🔥Builders & devs shipping on Solana.
🔥Investors & institutions watching the space.
🔥Creators & community members who love web3.
🤯Curious newcomers who want to change their lives and have the courage to grab the opportunity
@SuperteamDE
#Solana

[Md. Rejwar Rahman Rifat @rejwar]

What to expect from the event: 🔥🔥🔥

🤯 Alpha from top speakers on stablecoins, tokenization, AI + German innovation •
🤯 Live trading competition with real stakes & leaderboard •
🤯 Golf on the Spree, arts, sunset terraces & epic networking

[Md. Rejwar Rahman Rifat @rejwar]

@shankstwin @swarnitghule cgpa of bro 📉📉📉📉

[Md. Rejwar Rahman Rifat @rejwar]

@araghougassian BET

[Mitchell Amador @MitchellAmador]

The Future of On-Chain Security Is Human.

Crypto security platforms are abandoning security researchers for AI.

A lot of the platforms that built their name on security researchers are pivoting hard into AI.

It is an understandable move. AI auditing is a real opportunity, the teams pursuing it are serious, and proprietary tooling has a clear commercial story.

We are not against AI. It will play a meaningful role in the future of this industry.

But the shift has come at a cost.

Contests are smaller. Communication is thinner. Researchers who spent years building reputations on these platforms have been deprioritized as the roadmaps point elsewhere.

We are making a different bet.

Independent security researchers have prevented billions of dollars in losses across crypto. Every major class of vulnerability we now consider "standard knowledge" was first surfaced by a person.

The frontier has always been pushed by humans working in the open.

That is not an argument against AI. It is an argument about what AI cannot do alone.

In fact, the best researchers are already using AI as leverage.

Since AI tooling became more accessible, we have seen a clear rise in both the volume and quality of serious submissions. Yes, spam has increased too. But over the past two years, we have seen serious hunters submit stronger work, earn larger payouts, and outperform their own pre-AI baselines.

We have seen new researchers appear almost overnight and climb to the top of leaderboards by using AI to move through codebases faster, ask better questions, and hunt at a scale that was not possible before.

And we have seen already-elite researchers become even more dangerous with it. @Riptide was exceptional before AI. With AI as leverage through @therealgregoAI, he is operating at another level.

Researchers find what nobody has seen yet. The two are complementary, but only one of them scales adversarial creativity.

We think crowdsourced security is still the strongest security foundation crypto has. AI isn’t diminishing crowdsourced security; it’s making it even stronger, more effective, more critical.

Bug bounties. Audit competitions. Shared knowledge. Researchers compensated fairly for the value they create. That is the bet we have always made. That is the bet we are doubling down on now.

We are scaling crowdsourced security in ways this industry has not seen before. The protocols that will survive the next decade are the ones being tested by thousands of adversarial minds in the open. Supercharged by AI, absolutely, but non-negotiably human at their core.

If you are a security researcher and the past year has felt different, you are not imagining it.

Come build with us. We are going somewhere new, and we want you with us when we get there.

[Md. Rejwar Rahman Rifat @rejwar]

@MicrosoftLearn web3 security

[Md. Rejwar Rahman Rifat @rejwar]

@praptichilling tg: @rejwar

[Md. Rejwar Rahman Rifat @rejwar]

@Ysf34A Banned GMO.

[Md. Rejwar Rahman Rifat @rejwar]

we are so cooked !

[Md. Rejwar Rahman Rifat @rejwar]

@_HerDAO @Onallee @Hari_priyoo @HERDAOIndia @herdaobali @HerDao_Mexico @herdaovzla @herdaosg @herdaoghana @HERDAO_Kenya @herdaosa 👍🏻

[Neo Kim @systemdesignone]

If I had to scale a system, I'd try these techniques:

1 Horizontal Scaling
2 Autoscale
3 Retries
4 Orchestration
5 High Availability
6 Lazy Load
7 gRPC
8 Data Archiving
9 Backend for Frontend
10 Priority Queues
11 Edge Computing
12 Delta Sync
13 Brownout Mode
14 Kernel Bypass
15 Vertical Scaling
16 Microservices
17 Rate Limit
18 Service Mesh
19 Graceful Degradation
20 Capacity Planning
21 Pagination
22 Tiered Storage
23 Request Coalescing
24 Dead Letter Queues
25 Edge Authentication
26 Change Data Capture
27 Leaky Bucket Smoothing
28 Async Non-Blocking IO
29 Caching
30 Event Driven
31 Circuit Breaker
32 Diagonal Scale
33 Consistent Hashing
34 Hot Standby
35 Database Connection Pooling
36 TTL Expiration
37 Batch Reads
38 Stream Processing
39 Static Site Generation
40 Storage Partition Pruning
41 Token Bucket Throttling
42 Thread Pool Tuning
43 Load Balance
44 Queueing
45 Backpressure
46 CDN
47 CAP Tradeoff
48 Read Replica
49 Materialized Views
50 Log Compaction
51 Idempotency Keys
52 Micro-Batching
53 Incremental Static Regeneration
54 Client-Side Caching
55 Adaptive Timeouts
56 Load Shedding
57 Sharding
58 Stateless
59 GeoDNS
60 Monitoring
61 Modularity
62 Write Batching
63 Query Result Caching
64 Event Sourcing
65 Asynchronous Workflows
66 Data Locality
67 Server-Side Rendering Cache
68 Columnar Storage for Analytics
69 In-Memory Data Grids
70 Admission Control
71 Replication
72 Indexing
73 Multi Region
74 Tracing
75 Bulkhead
76 Compression
77 Denormalization
78 CQRS
79 Job Scheduling
80 Regional Read Caches
81 Edge Image Transformation
82 Search Offloading
83 Memory-Mapped Files
84 Concurrency Limits
85 Partition
86 Timeouts
87 Container
88 Failover
89 Prefetching
90 HTTP Keep-Alive
91 Read/Write Splitting
92 API Gateway
93 Worker Pools
94 Anycast Routing
95 Optimistic UI with Deferred Sync
96 Specialized Datastores
97 Zero-Copy Networking
98 Hedged Requests

(...and many more techniques)

What else should make this list?

===

👋 PS - Want my System Design Playbook for FREE?

Join my newsletter with 200K+ software engineers now:

→ https://t.co/ByOFTtOihX

===

💾 Save this for later & RT it to help others learn system design.

👤 Follow @systemdesignone + turn on notifications.

[Md. Rejwar Rahman Rifat @rejwar]

Not giving a....

[0xSlowbug 🥷 @0xSlowbug]

Pay per report model just launched. Worse still non refundable even if it’s valid.

Auditor funds get pooled and part of it is used to pay out winners.

They’ll give the AI spam excuse but it’s not it…
They had submission limit to curb that. Unsure if they even removed it for this contest.

If @cantinasecurity did this the whole space would have eaten them up.

It’s a new dispensation SR’s