Naim Ashhab
Smart Contract Developer
5+ years exp
Management: Under a year
Solidity
TypeScript
Yul
Python
JavaScript
Node JS
Rust
Smart Contract Development: 5/10
Security & Audit: 5/10
Blockchain Protocol Understanding: 5/10
Active 2 days ago
Invite to interview
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Senior protocol engineer specializing in on-chain peer-to-peer loans and vault management with strong protocol-level design. The strongest proven skill is designing secure, invariant-tested lending flows as demonstrated by pwn/loan/terms/simple/loan/PWNSimpleLoan.sol together with the comprehensive unit and fuzz tests in PWNDAO/pwn_protocol/test/unit/PWNSimpleLoan.t.sol. There is limited public evidence of frontend wallet UX, custom subgraph mappings, or large-scale RPC/indexer infrastructure work.
Technical skills
Languages
7
Solidity
TypeScript
Yul
Python
JavaScript
Node JS
Rust
DevOps
3
GitHub
Git
CI/CD
Web3
9
Ethereum
Chainlink
Foundry
Aragon
Slither
NFT
Aave
OpenZeppelin
DAO
Frontend
3
React.js
Next.js
Tailwind CSS
Other
9
Foundry Cheatcodes
Claude
Smart Contracts
GitHub Actions
Vercel
Tenderly
Hardhat
Token Standards
DeFi
Timeline
Protocol Architect & Lead Smart Contract Developer
•
Lead
Generic Money
•
Full-Time
Led end-to-end R&D, architecture, implementation, deployment, and maintenance of a fully collateralized USD stablecoin with native yield bridging capabilities. Built supporting systems handling significant transaction volume. Owned the project across research, engineering, and ongoing operations.
Solidity
Foundry
Tenderly
Morpho
Ethereum
LayerZero
Senior Blockchain Developer
•
Senior
PWN
•
Full-Time
Owned the full lifecycle of a permissionless peer-to-peer fixed/variable-rate lending protocol, from protocol R&D and architecture through deployment, monitoring, upgrades, and maintenance. Designed lending financial state machines covering proposals, collateral, issuance, repayment, defaults, and fixed-rate settlement. Implemented security-critical smart contracts using Foundry fuzzing/invariant/fork testing and Slither, and built governance and Safe{Wallet} periphery components.
Solidity
Foundry
Slither
Aragon
DAO
Ethereum
ERC-5646: Token State Fingerprint
Publications
České vysoké učení technické v Praze (ČVUT)
Master's Degree •
Computer Science
České vysoké učení technické v Praze (ČVUT)
Bachelor's Degree •
Computer Science
Senior Blockchain Developer
Confidence: High Protocol Engineer
Senior protocol engineer specializing in on-chain peer-to-peer loans and vault management with strong protocol-level design. The strongest proven skill is designing secure, invariant-tested lending flows as demonstrated by pwn/loan/terms/simple/loan/PWNSimpleLoan.sol together with the comprehensive unit and fuzz tests in PWNDAO/pwn_protocol/test/unit/PWNSimpleLoan.t.sol. There is limited public evidence of frontend wallet UX, custom subgraph mappings, or large-scale RPC/indexer infrastructure work.
Smart Contract Development
5/10
Writing smart contracts
Strong, production-grade smart contract engineering for a lending protocol: clear domain-specific types, EIP-712 extension handling, packed storage layout, custom errors, and many unit/fuzz tests demonstrating deliberate design and edge-case handling.
Evidence
pwn/loan/terms/simple/loan/PWNSimpleLoan.sol: _createLoan, _settleLoanRefinance, getLOAN and loan storage layout
PWNDAO/pwn_protocol/test/unit/PWNSimpleLoan.t.sol: comprehensive unit and fuzz tests covering create/repay/claim/refinance/extend flows
PWNDAO/MultiToken/src/MultiToken.sol: unified MultiToken Asset handling used across the protocol
Security & Audit
5/10
Checking contracts for flaws
Clear security awareness and applied mitigations: use of ReentrancyGuard, CEI pattern, nonce revocation, try/catch fallback for external transfers, invariant and fuzz tests, and dedicated security research notes in the repo.
Evidence
pwn/loan/terms/simple/loan/PWNSimpleLoan.sol: ReentrancyGuard usage, revokedNonce interactions, tryClaimRepaidLOAN try/catch patterns
PWNDAO/pwn_protocol/test/helper/ReentrancySpy.sol and tests referencing reentrancy scenarios
generic-money/generic-protocol/reports/security/vault-reentrancy-security.md: documented reentrancy considerations and tests
Blockchain Protocol Understanding
5/10
Knowing how blockchains work
Good blockchain-protocol knowledge: explicit handling of pool adapters, source-of-funds model, EIP-712 domain/seal for extensions, and repayment/supply flows showing awareness of onchain/offchain integration and reentrancy/atomicity tradeoffs.
Evidence
pwn/loan/terms/simple/loan/PWNSimpleLoan.sol: pool adapter interactions, sourceOfFunds logic and bridge-ready loan lifecycle
pwn/loan/lib/Chainlink.sol: chainlink feed handling and sequencer uptime checks referenced in loan proposals and tests
PWNDAO/pwn_protocol/script/PWNTimelock.s.sol: timelock deployment utilities and governance-aware deployment flows
DApp & Web3 Integration
3/10
Connecting apps to blockchain
Some periphery and deployment automation exists (Foundry scripts and Gnosis timelock/safe helpers) but there is no evidence of frontend wallet UX, transaction-retry UX, or custom subgraph mappings.
Tokenomics & DeFi Logic
5/10
Token and finance logic
Strong DeFi and tokenomics reasoning in loan flows: explicit fee calculation, handling surplus/shortage in refinancings, preservation of invariants, and many tests for repayment math and rounding behavior.
Evidence
pwn/loan/terms/simple/loan/PWNSimpleLoan.sol: fee handling, surplus/shortage logic and repayment math
pwn/loan/lib/PWNFeeCalculator.sol: fee calculation helper used in settle flows
PWNDAO/pwn_protocol/test/unit/PWNSimpleLoan_LoanRepaymentAmount.t.sol: tests and fuzz coverage for accrued interest and rounding
Decentralization & Trust Model
3/10
Designing trust without middlemen
Some governance and trust-model primitives are present (timelocks, Gnosis Safe helpers, explicit config contract and owner checks) but the codebase still relies on admin roles and there is limited evidence of a fully decentralized upgrade/governance lifecycle described in-code.
Evidence
PWNDAO/pwn_protocol/script/PWNTimelock.s.sol: timelock deployment functions and min delay updates
pwn/config/PWNConfig.sol: admin-settable config, fee collector and pool adapter registry
PWNDAO/pwn_protocol/script/lib/GnosisSafeUtils.sol: Gnosis Safe execution helper
Verified artifacts
Expertise
DeFi & Decentralized Finance• Senior
Ethereum & EVM Development• Senior
Web3 Security & Smart Contract Audits• Senior
Industries
Blockchain & Crypto• Senior
Financial Services• Senior
Technologies
Rust
Yul• Senior
Solidity• since 2021 • Senior
Foundry• since 2021
Hardhat
Chainlink• since 2023
Slither• since 2021
OpenZeppelin
Tenderly
Smart Contracts
Ethereum• since 2021
Foundry Cheatcodes
DeFi
DAO• since 2021
Token Standards
Aragon• since 2021
Recommendations
- Design and implement core DeFi primitives and lending/vault lifecycle features (loans, refinancing, extension, claim flows).
- Own protocol-level integrations with pools and bridges, including pool adapters and safe repay/supply logic shown in _withdrawCreditFromPool and tryClaimRepaidLOAN.
- Lead security- and invariant-focused work such as invariant tests, fuzzing attacker scenarios, and audit fixes for lending/product logic.
- Implement cross-chain adapters and governance/timelock integration for coordinated upgrades and multi-chain canonical supply flows.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Frontend Developer
Confidence: Medium App Engineer
Frontend app engineer (middle) focused on building documentation and analytics tooling for blockchain protocols. The strongest proven skill is producing detailed protocol docs and ABI-driven developer tooling as shown by the bridging and withdrawal guides plus exported ABIs (generic-docs/docs/pages/guides/withdrawals/citrea.mdx and generic-analytics/public/abi/BridgeCoordinatorL1.abi.ts). There is little public evidence of custom React component architecture, interactive SPA implementations, performance instrumentation, or automated accessibility testing.
UI Component Architecture
1/10
How interface parts are built
Little evidence of bespoke component architecture or a custom component library; mostly docs, ABIs and config files rather than React component design.
Responsive & Cross-browser
1/10
Works on all screens and browsers
No explicit responsive strategy or cross-browser feature-detection patterns shown; styles focus on font assets for docs rather than responsive UI architecture.
Performance Optimization
1/10
Speed of the interface
No measurable performance artifacts, bundle analysis, virtualization, or explicit code-splitting strategy present in the analyzed human-authored files.
Accessibility & Semantics
1/10
Usable for everyone
Documentation pages are well formed but there is no clear evidence of a11y engineering such as ARIA on custom widgets, automated a11y checks, or focus-management code.
State Management & Data Flow
2/10
Managing data in the app
There are many RPC/data-fetch action signatures indicating server-state and analytics integrations, but implementations and advanced state discipline (cancellation, optimistic updates, state machines) are not exposed in the reviewed human-authored files.
UX & Visual Polish
3/10
Look and feel quality
Strong, polished protocol documentation and user guides with clear UX-oriented steps and error-resolution guidance demonstrates attention to UX and instructional polish more than interactive UI polish.
Expertise
React• Middle
Industries
Blockchain & Crypto• Senior
Financial Services• Middle
Technologies
JavaScript
TypeScript• since 2025 • Middle
Node JS
Tailwind CSS• since 2025
Next.js• since 2025
GitHub Actions
React.js• since 2025
Recommendations
- Develop documentation-driven developer portals and onchain analytics dashboards that combine the existing ABIs and RPC fetchers into interactive charts and query pages.
- Build analytics UI pages (Next.js + React) that wire the app/actions RPC helpers to visualizations (nivo) with clear loading/error/empty states and request cancellation.
- Package a small design-system subset (tokens, a11y patterns, and a few shared components) extracted from the docs site so future frontends stop reusing doc templates as UI components.
- Implement end-to-end examples that show server-state handling (fetching, caching, cancellation, optimistic UI with rollback) for common flows like bridge estimation and submit.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: