Security for those who cannot afford a mistake.

Joined September 2021
306 Photos and videos
Pinned Tweet
Apr 24
It's never been harder to build or raise in crypto. And the teams that need audits the most are the ones just starting out. Hexens Builder Support: real security engagement built around where early-stage protocols actually are. Who qualifies: — Under $1M raised — First security audit (no prior professional audit) — Live or near-launch product (not just an idea) Too many good protocols die before their first audit or ship without one and get exploited. That's why we built Builder Support. To catch the ones worth catching, before anyone else does. Apply: hexens.io/?request-a-quote=t…
9
10
49
5,491
Jun 12
Before you take a position in a tokenized security, check how it restricts transfers. Your ability to exit depends on it. ERC-3643, one of the most common standards, enforces restrictions through an on-chain identity system: ONCHAINID-linked wallets, claim registries, and trusted issuers who attest credentials like KYC. Transferring your position isn't a wallet-to-wallet transaction. The buyer needs valid claims from an approved issuer, and the transfer must clear a compliance contract. No credential, no transfer. ERC-3643 appears most often on institutional-grade tokenized securities: regulated equity, real estate funds, private credit. The compliance structure is the feature. The liquidity constraint is the tradeoff and it isn't unique to this standard. The right question isn't "is it ERC-3643," it's "what does it take to get out." Try the query below to see if your token complies with ERC-3643: glide.r.xyz/query/22a803fb-7…
2
10
391
Jun 11
Hexens Builder Support × @obsdntrade Happy to have supported @obsdntrade through our Builder Support program, backing early-stage teams building thoughtful protocols in Web3. Our audit focused on account delegation (ERC-1271), order and balance modules (EIP-712), and vault accounting across spot and perp positions. Wishing the OBSDN team the best as they head into launch. Full report below:
2
4
24
1,126
Jun 10
Hexens Builder Support × @0xPolygon We’ve partnered with @0xPolygon to allocate dedicated Builder Support slots exclusively for Polygon builders. Builders get a full Hexens audit, Hexens products, and partner ecosystem access. Eligibility: under $1M raised, pre-first-audit. Apply: hexens.io/pages/builder-supp…
2
7
34
10,496
Jun 9
New partner on Builder Support: @MatchSystems, covering compliance and incident response for accepted teams. Glad to have them on board. Apply: hexens.io/pages/builder-supp…
The teams that need compliance and security the most are the ones just starting out. @hexens Builder Support Program fixes that — top-tier tooling for early-stage protocols, at builder-stage prices. Time to show what we bring to this partnership. For teams accepted into the program — Match Systems perks: ▸ AML/KYT — risk scoring built on real investigative experience: we don't just flag risks, we trace fund origins, transaction links, and full operation context ▸ KYB — counterparty verification before you trust anyone with your infrastructure ▸ Incident Response — funds stolen or wallets compromised? We launch immediately: on-chain tracing, blockchain investigations, recovery support Special rates on all services for Builder Support participants. Apply: hexens.io/pages/builder-supp…
4
16
853
Jun 8
Stripping names from a dataset doesn't make it anonymous. Differential privacy is what replaced ad-hoc anonymization, and it's the only privacy guarantee with formal math behind it. Part 1 of our technical guide: definitions, mechanisms and accounting. hexens.io/blog/dp-part1
4
19
1,889
Jun 5
Builder Support keeps adding to what accepted teams get. @CoinStats joining with API access to crypto prices, wallet balances, PnL and DeFi positions across 120 chains. Apply: hexens.io/pages/builder-supp…
Top-tier security for teams building from 0 Most "builder programs" hand out credits. @hexens is handing out something rarer: a real audit at a price pre-seed teams can actually pay. We're joining in. $6,000 in CoinStats API credits, free for accepted teams👇
3
13
910
hexens retweeted
Time to show what we bring to this partnership. For qualified residents of @hexens Builder Support Program - a set of exclusive perks from GetBlock: > Starter Shared subscription, free > Dedicated or Limitless Node on a 2 1 offer (pay for two, get three, terms apply) Share promo code HEXENS26 with us through the Contact form once you're in. Builder Support details and application: hexens.io/pages/builder-supp…
Strong news from our security partner @hexens Applications are open for their Builder Support Program. What's on the table for qualifying protocols: ᐉ Full Hexens audit at 1/3 the standard rate ᐉ Same senior auditors, same scope, same deliverable ᐉ Eligibility: pre-seed or under $1M raised, first audit, live or near-launch product ᐉ Perks include investor intros, co-marketing, Glider monitoring access, and more Hexens already fuels GetBlock's Token Risks API: a real-time risk scoring for tokens, contracts, ownership patterns, and liquidity behavior, all through a single endpoint. Apply for Builder Support: hexens.io/pages/builder-supp… Explore the Token Risks API: getblock.io/token-risks-api
1
3
9
688
hexens retweeted
The Glider Query Contest has officially wrapped | our $50K prize pool has been fully depleted! What started as an experiment turned into something way bigger than we expected. A huge thank you to everyone who contributed and to @ethereumfndn for funding the entire $50K prize pool. Big thanks also to @autopools for contributing an additional $3K to the pool. Contributions are always open and everyone is welcome to keep submitting queries as we will still review existing and new queries. New contributions won't be paid for now. Every query makes Glider smarter and more useful for the whole ecosystem. We will post the database after all the triaging is finished. Also, we know you loved the contribution visuals, so we're not stopping there. We'll keep posting the remaining contribution announcements here. And yes, stay tuned. This might not be the last pool
2
5
38
2,576
Jun 3
Glad to have been on the security side of @Cybro_io. Looking forward to working together again.
Automation you can trust 🛡 Cybro’s new Auto-Close and Auto-Rebalance features have been audited by @hexens The full audit report is now available here ⬇️ hexens.io/audit-reports/cybr… Built for safer, smarter LP management — so you can automate with confidence. Live now on Arbitrum ⚡️ 🔗 cybro.io
2
12
1,193
Jun 1
As TradFi integrates with the DeFi ecosystem and adopts ERC-20 tokens, institutions must ensure tokens meet compliance standards including adherence to the official OFAC SDN list. Many tokens support blacklisting, but it's difficult for analysts to verify whether a given token is actually up to date with the latest sanctions list. With Glider, we can analyze any token and instantly surface whether it maintains the latest OFAC SDN list. The query below identifies ERC 20 tokens that support blacklisting but don’t utilize the latest SDN list.
1
3
16
1,241
May 28
Glad to have @getblockio join the Builder Support Program as an infrastructure partner. More partners being announced soon: hexens.io/pages/builder-supp…
Strong news from our security partner @hexens Applications are open for their Builder Support Program. What's on the table for qualifying protocols: ᐉ Full Hexens audit at 1/3 the standard rate ᐉ Same senior auditors, same scope, same deliverable ᐉ Eligibility: pre-seed or under $1M raised, first audit, live or near-launch product ᐉ Perks include investor intros, co-marketing, Glider monitoring access, and more Hexens already fuels GetBlock's Token Risks API: a real-time risk scoring for tokens, contracts, ownership patterns, and liquidity behavior, all through a single endpoint. Apply for Builder Support: hexens.io/pages/builder-supp… Explore the Token Risks API: getblock.io/token-risks-api
1
1
16
852
May 27
Replying to @_nd_koo
@_nd_koo recently broke down six security issues that recur across Hexens wallet audits. Not bugs. Architectural defaults that survive design review because nobody pushes back.
2
6
29
1,065
May 27
5. Token UI Wallet UIs often abstract transactions into simplified asset actions. Critical execution details may be hidden or poorly visualized, making malicious behavior appear indistinguishable from legitimate user flows.
1
4
244
May 27
6. KDF and entropy Wallet security still regularly fails at key generation and password hardening. Weak entropy sources, insufficient randomness, and fast hashing primitives continue to turn local wallet compromise into practical key recovery.
4
213