Web3 venture studio · On-chain engineering lab

The trenches aren’t chaos. They’re broken design.

Pleco Ventures finds the structural flaws in the small-cap ecosystem — the ones that quietly drain users and builders — and engineers proprietary infrastructure to remove them.

  • 01On-chain intelligence
  • 02Wallet clustering & forensics
  • 03Security infrastructure
  • 04Execution systems

Thesis

Most people see the trenches as inevitable. We read them as a spec with bugs in it.

Status quo

  • Bundled launches that look organic until the chart is already dead.
  • Linked wallets hiding behind fresh addresses funded from the same source.
  • Fake volume treated as a signal because nobody checks who’s on both sides.
  • Execution that loses to the mempool before the user has finished clicking.
  • Security that is a Discord warning after the drain, not a control before it.

What we do with it

  • Measure the behaviour at the transaction level, not the narrative level.
  • Cluster funding paths, timing and counterparties until the actors have names.
  • Separate real flow from circular flow, and show the difference as data.
  • Build execution paths that assume adversaries are already in the block.
  • Ship controls that act before the exploit, because a post-mortem is not a product.

Every one of these is a design failure with a technical fix. We don’t write checks and wait. We write the fix.

Studio focus

Four verticals. One standard: it has to hold under adversarial load.

01

On-chain intelligence

Indexing and interpreting raw chain state faster than the narrative forms. Launch detection, deployer history, holder composition, liquidity events — decoded as they land, not after.

  • Real-time indexing
  • Deployer lineage
  • Holder composition
  • Liquidity telemetry
02

Wallet clustering & forensics

Fresh addresses are not fresh identities. We cluster wallets by funding paths, timing signatures and shared counterparties, then follow the money through hops and bridges.

  • Funding-graph analysis
  • Temporal correlation
  • Cross-chain tracing
03

Security infrastructure

Controls that sit in the path of the transaction. Pre-trade risk checks, contract and authority inspection, and monitoring that pages before the drain, not after.

  • Pre-trade risk
  • Authority inspection
  • Live monitoring
04

Execution systems

Routing, timing and inclusion built on the assumption that someone is already competing for the same block. Low-latency pipelines, private submission, and failure modes that are explicit rather than silent.

  • Low-latency routing
  • Private submission
  • Deterministic failure handling

Philosophy & craft

Small, obsessed teams build the infrastructure that lasts.

  1. I

    Understand the mechanics at the atomic level.

    Accounts, instructions, ordering, fees. If you can’t explain what happens inside the block, you're guessing about what happens on the chart.

  2. II

    Build the thing. Then prove it under fire.

    No decks for systems that don’t run. Everything we ship is used against live, adversarial markets before anyone else touches it.

  3. III

    Headcount is not leverage. Focus is.

    A handful of engineers who own the whole problem outperform a department that owns a slice of it. We stay small on purpose.

  4. IV

    Say the uncomfortable thing.

    Most tooling in the trenches is optimised to look like it works. We’d rather be correct than comfortable — in our analysis, and in our code.

Contact

Building in the trenches and tired of the defaults?

We work with a small number of teams and operators who need infrastructure that holds. Tell us what’s broken.