Creator & Lead Developer of Nexus Core Gateway — an autonomous M2M legal-code engine for EVM infrastructure: ABI drift detection, high-fidelity Solidity drafting, and machine-readable security verification.
I architect systems where smart contracts are verified, not just written. My work operates at the seam between three layers that most tooling treats separately: the Solidity source, the EVM state machine it compiles to, and the canonical execution layer (Rust precompiles / node dispatchers) that ultimately interprets every selector. When those layers drift apart, contracts compile clean and break silently at runtime — my entire pipeline exists to catch that class of failure before mainnet does.
Every audit, PR, and advisory I ship is backed by the Nexus Core Gateway — a self-built verification pipeline (v4.3.0-frontier, live on Supabase Edge, registered on-chain as ERC-8004 Agent #636 on Polygon). It is not a wrapper around existing tools; it is a Digital Twin engine that reconstructs what the EVM will actually do:
- Anvil / Foundry state-forking PoCs — every candidate finding must prove real-world impact
against a forked mainnet state, not a synthetic harness. A dust-spam DoS is only real if 5,000
dust stakes actually push a
withdrawpast the 30M block gas limit on a real chain state. - Low-level signature parity checks (v/r/s) — byte-level verification of secp256k1 parity conventions across signers (27/28 vs 0/1), high-s normalization, and EIP-2098 compact encodings. This is where "it compiles" and "it recovers the right address" diverge.
- Invariant fuzzing — state properties, not just happy-path assertions. PPS monotonicity, custody invariants, and accounting conservation get fuzzed until they break or hold.
- Cross-layer verification (Rust ↔ Solidity) — ABI signatures extracted from canonical
crate::sol!node definitions and diffed against Solidity interface mirrors, with transitive inheritance resolution and selector-level type normalization. When the execution layer gets redesigned (T12-style), the mirror cannot rot silently.
The gateway enforces a stop-submit gate: no finding ships to a public tracker below a 95% confidence threshold, and every report must survive a mechanical PoC before a human ever reads it.
The kind of low-level safety thinking that goes into every draft — a minimal sentinel pattern using EIP-1153 transient storage for gas-cheap reentrancy protection, with an assembly-guarded signature parity check:
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.24;
/// @notice Minimal autonomous security sentinel.
/// @dev Reentrancy guard lives in transient storage (EIP-1153): zero SSTORE cost,
/// zero storage slots, fully reverted at the end of the tx — the guard
/// cleans up after itself by construction.
interface INexusSentinel {
event SentinelArmed(bytes32 indexed scope, uint64 deadline);
error SentinelTripped(bytes32 scope);
error SignatureParityMismatch(uint8 v);
}
abstract contract NexusSentinel is INexusSentinel {
// EIP-1153 transient slot — never touches persistent state.
uint256 private constant _GUARD = 0x7f6b0001;
modifier guarded(bytes32 scope) {
assembly ("memory-safe") {
if tload(_GUARD) { mstore(0x00, 0x9c7f66ac) revert(0x00, 0x04) } // SentinelTripped
tstore(_GUARD, or(scope, 0x1))
}
_;
assembly ("memory-safe") {
tstore(_GUARD, 0)
}
}
/// @dev Accepts both secp256k1 parity conventions (27/28 and 0/1) and
/// rejects high-s blobs — a signature that recovers the wrong
/// address is worse than no signature at all.
function _checkParity(uint8 v, bytes32 s) internal pure returns (uint8) {
if (s > 0x7FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF5D576E7357A4501DDFE92F46681B20A0) {
revert SignatureParityMismatch(v);
}
return v >= 27 ? v - 27 : v; // normalize to y-parity
}
}| Layer | Tools & Standards |
|---|---|
| Languages | Solidity (0.7 → 0.8.36), Yul (inline assembly, memory-safe), Rust (sol! ABI definitions, node internals), TypeScript (Deno Edge, SDKs) |
| Security Tooling | Foundry (forge fuzz/invariant, cast, Anvil state-forking), Slither static analysis, custom Digital Twin breach simulator (9 scenario classes, BS-001 → BS-009) |
| Signature & Auth | EIP-712 typed data, EIP-2098 compact signatures, secp256k1 v/r/s parity forensics, EIP-7702 delegation |
| Token & Vault Standards | ERC-20 / ERC-721 / ERC-1155, ERC-4626 vault accounting, EIP-1153 transient storage |
| Infrastructure | Polygon PoS, Supabase Edge Functions, ERC-8004 agent identity, EIP-712 pull-payment rails (USDC) |
- Confetti — GHSA-3g9w-x8qp-2qpq — phantom-vote reward theft (high severity); maintainer shipped the exact recommended fix within 5 hours, plus a regression test and version bump.
- Solady — PR #1562 — two real bugs in
LibBytes(splitmemory corruption via null-path scratch-pointer read; missing bounds check indynamicStructInCalldata), fixed with a 5-test regression suite; 1,597/1,597 tests green. - tempo-std — PR #145 —
flipVparity-convention bug + full T12 ABI resync +check-drift.py, a cross-layer Rust↔Solidity ABI drift checker offered for CI integration. - Uniswap v4-core — PR #1073 — doc-hygiene fixes surfaced by a full EIP-1153 revert-semantics trace of PoolManager.
- Lido staking-modules — PR #878 review — pre-audit design review of CM v2 balance checkpoints: 3 design flags, 0 false positives.
- Nexus Core Gateway — deployed end-to-end: EIP-712 pull-payment contract live on Polygon mainnet, Python + TypeScript SDKs published (PyPI / npm), on-chain ERC-8004 identity, live security playground.
My clients are machines. The gateway speaks pure JSON over HTTP, publishes an A2A discovery manifest, bills itself in USDC via EIP-712 pull payments, and registers its identity on-chain. If your agent wants to audit, draft, or verify Solidity — it can hire mine without a single human meeting.
"A contract that compiles is not a contract that works. Verify the state machine, not the syntax."
— Nexus Gateway Architect
For security teams, maintainers, or human leads requiring private disclosure triage, automated pre-audits, or asynchronous security scans:
- Inbound Email:
rakhmadaa@gmail.com - Expected Subject Format:
[SECURITY-INQUIRY] <Protocol Name> - <Target Commit/Scope> - Ingestion Endpoint (H2M pipeline):
https://xibzsthfrbomefnvbicb.supabase.co/functions/v1/hello-world/ingest/security-inquiry - Gas Asymmetry Guard: quantitative compute-to-gas ratio analysis (threshold > 12.5 → validator-delay DoS flag) is active in the ingestion layer, with automatic audit logging to the append-only
poa_ledger.
Automated Dynamic Triage Note:
Inbound inquiries are routed to the gateway pipeline for automated state-machine pre-scanning. The engine generates a signed proposal with a dynamically adjusted pricing manifest (USDC via Polygon/EIP-712) and timeline. No manual meetings or price negotiations required. Every inquiry is automatically recorded to the immutable Proof-of-Activity ledger.