Skip to content
View IpastorSan's full-sized avatar

Block or report IpastorSan

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
Ipastorsan/README.md

👨‍💻 Ignacio Pastor

Fullstack engineer. Early-stage products, zero to one. Smart contracts, L1 infra, and increasingly AI

I work best early: the zero-to-one stage, before the architecture is settled and while the requirements are still moving. Most of what I've built has been the first version of something.

What I've built

Somnia — Head of Engineering for an L1 blockchain. Took it from devnet through testnet to mainnet and TGE with a team of five. Built the staking and validator-committee protocol that holds 20%+ of total token supply (Hacken audit), and a Sybil-resistant incentive platform that verified and rewarded 95,000+ contributors.

Charms — the Web3 side of a consumer app where AI companions have their own on-chain economies: per-character token launches on Uniswap V4 (through Clanker), gasless one-tap transactions (Privy, EIP-7702, ERC-7579), and cross-chain swaps across Base, Solana and BNB.

Earlier — I joined crypto in NFT Summer 2021: DAO governance and treasury contracts at Improbable, then Gokaden through the startup incubator program at Station F, and a year freelancing on NFT project contracts.

What I'm working on

AI product engineering: agents that touch real systems, LLM features that have to survive production, and the evaluation work that decides whether either one ships.

Smart contract work turns out to be strange but useful preparation. You learn to assume inputs are adversarial, to scope exactly what a system is authorized to do, to keep simulation separate from execution, and to never let an unreliable component own an invariant. Those questions arrive the moment a model can take actions instead of just generating text.

Stack

Deep — Solidity, Foundry, Hardhat, upgradeable patterns, account abstraction, DeFi, NFTs Daily — TypeScript, Next.js, React, Node, NestJS, Go, Postgres, Docker, AWS/GCP Learning — agent frameworks, evals, LLM tooling

Elsewhere

  • Website Writing on my blog
  • Github
  • Email
  • LinkedIn
  • Twitter

Pinned Loading

  1. ERC721-nft-merkletree-allowlist ERC721-nft-merkletree-allowlist Public

    Solidity 1

  2. ERC1155-semifungible-with-EIP2981-royalties ERC1155-semifungible-with-EIP2981-royalties Public

    Solidity

  3. ERC721A-nft-dutch-auction ERC721A-nft-dutch-auction Public

    JavaScript 1

  4. beacon-proxy-smart-contracts beacon-proxy-smart-contracts Public

    Solidity 1

  5. mtga-linux-exporter mtga-linux-exporter Public

    Extract and enrich your MTG Arena card collection on Linux/Proton — passive memory scan + Scryfall enrichment. Python 3, stdlib only.

    Python

  6. omarchy-plugin-bujo omarchy-plugin-bujo Public

    A bullet journal in the Omarchy bar. Tasks belong to a day; migrate what you didn't finish.

    JavaScript