←
Martin2,363 posts
Martin avatar

Martin

@ShieldifyMartin

Co-Founder @ShieldifySec Taking your smart contracts' security seriously!

◷ Joined April 2022▧ 107 Photos and videos
Martin avatar
Martin@ShieldifyMartin·7h

PQ-Vault combines hash-based cryptography with NIST-standardized ML-DSA signatures. It implements a cryptographic escrow with checkpoint verification and proof-based withdrawals. More 👇

Martin avatar
⟳ Martin retweeted
Martin@ShieldifyMartin·Nov 16

Number of fixed findings / their severity > Large Security Name / Badge

Questions to ask your security provider? 🫡 1/ How many of your customers have been exploited? 2/ What percentage of your customers are returning?

Shieldify Security avatar
⟳ Martin retweeted
Shieldify Security@ShieldifySec·Nov 16

😤 Most users see "audited by X" & stop there Open the report. Check which commit was reviewed, what was out of scope & which findings were acknowledged instead of fixed. That's where the real story is🙏

Martin avatar
Martin@ShieldifyMartin·Nov 15

Today's read 📌 With Shor's algorithm deprecating ECDSA by 2030, it's vital to research quantum algos.

Post attachment
The Moats 🏰 avatar
⟳ Martin retweeted
The Moats 🏰@Moats_app·Nov 13

We are proud to be working with @ShieldifySec as one of our auditors for Moats v4 Coming soon 👀

Next week we're kicking off the security review of @moats_app V4 🛡️ Moats powers staking & rewards for token projects, with stake, lock & burn mechanics running on top of it. Every project that plugs in relies on these contracts, so we're going deep. Looking forward to working with the team!

0:08
Martin avatar
Martin@ShieldifyMartin·Nov 14

Questions to ask your security provider? 🫡 1/ How many of your customers have been exploited? 2/ What percentage of your customers are returning?

Shieldify Security avatar
⟳ Martin retweeted
Shieldify Security@ShieldifySec·Nov 13

Next week we're kicking off the security review of @moats_app V4 🛡️ Moats powers staking & rewards for token projects, with stake, lock & burn mechanics running on top of it. Every project that plugs in relies on these contracts, so we're going deep. Looking forward to working with the team!

0:08
Shieldify Security avatar
⟳ Martin retweeted
Shieldify Security@ShieldifySec·Nov 12

🫡 To every new auditor putting in the hours while things are quiet: Fewer contests & fewer bounties doesn't mean less to learn. Read past reports, break down every new exploit, rebuild the attacks yourself, write your own tools. When the next bull run hits, every protocol will need an audit at the same time & there won't be enough good researchers. The ones who put in the work now will be the ones getting paid then. And if you're good, we're always looking🙏

Martin avatar
Martin@ShieldifyMartin·Nov 12

Security competitions are great, but not many protocols can afford to run one currently. They're also not a standalone security layer, as researcher participation and their experience and efforts are never guaranteed. I expect demand to grow in the next bull run. 🫡

Shieldify Security avatar
⟳ Martin retweeted
Shieldify Security@ShieldifySec·Nov 11

The best auditors we know aren't the ones who know every attack vector 🫡They're the ones who understand what the protocol is supposed to do better than the devs who wrote it. Bugs live in the gap between intent & code. True?

Martin avatar
Martin@ShieldifyMartin·Nov 11

Strongest Security Strategy in 2027 🚀 1. Custom AI agents running on every commit/change. 2. A trusted long-term security partner auditing every sprint, building deep context around the product. 3. A different security firm every larger sprint as an independent 3rd layer.

Shieldify Security avatar
⟳ Martin retweeted
Shieldify Security@ShieldifySec·Nov 10

🚨 Teams skipping the fix review are not going to make it Some of the worst bugs we've seen weren't in the original code. They were introduced by the fix itself. Get your fixes reviewed🙏

Shieldify Security avatar
⟳ Martin retweeted
Shieldify Security@ShieldifySec·Nov 9

Something we keep seeing: teams wait until their code is "final" before getting it reviewed. Thing is, the bugs that hurt the most usually aren't in the code. They're in the design. If the way funds settle or get refunded is wrong, there's no quick patch for that. You end up rebuilding a big chunk of the protocol. So if your contracts are still changing, it's worth having someone look at the architecture first. Way cheaper to fix a diagram than a deployed contract.