eloizStart a project
Services / integrated delivery

Engineering for the complete blockchain product.

Eloiz joins contract engineering, backend systems, developer infrastructure, security, and release operations under one accountable technical direction.

Define an engagement
Integrated delivery architectureContract to operations
1Protocol
2Services
3Product
4Assurance
5Operations

One architecture connects state transitions, data movement, user actions, security evidence, and operating ownership.

1Protocol engineering

Smart contracts and protocol systems

We design and implement ledger-facing systems with explicit state, permission, execution, and upgrade behavior.

What we deliver
  • Solana and Anchor programs
  • EVM protocols, hooks, and integrations
  • Soroban contracts and release systems
  • Canton applications and Ledger API integrations
What it must establish
  • Defined invariants
  • Reviewable state transitions
  • Release-ready source
Relevant record

Risk-Neutral Hook · Solana ONFT · Inverter Network modules

Abstract blue glass layers folding around a dark central boundary
Stellar / SorobanOpen-source alpha
Release infrastructure2026
2Network expansion

Protocol ports and new-network delivery

We adapt protocol behavior to a new execution model. We preserve intended economics while we make network-specific assumptions explicit.

What we deliver
  • Source and behavior mapping
  • Contract and program ports
  • SDK and adapter layers
  • Parity evidence and release plans
What it must establish
  • Behavior map
  • Network-native implementation
  • Explicit parity gaps
Relevant record

Soroban Upgrades · Solana ONFT · r55 contribution

A field of crystalline blue forms arranged as a repeating analysis structure
SolanaOpen source
Static analysis2025 to 2026
3Infrastructure

Blockchain backend and infrastructure

We build the services around the protocol. This includes APIs, indexers, event pipelines, automation, data systems, and operating controls.

What we deliver
  • Indexers and event pipelines
  • Transaction and wallet services
  • APIs, automation, and agents
  • Observability, recovery, and operations
What it must establish
  • Stable interfaces
  • Observable operations
  • Recoverable state
Relevant record

DEX Oracle · Paragon systems · Hermes Live Voice

A dark architectural system cut by illuminated cobalt channels
Solana / EVMOpen source
Execution analysis2026
4Developer infrastructure

Products, SDKs, and engineering tools

We turn complex protocol capabilities into usable products, command-line tools, SDKs, APIs, and operational interfaces.

What we deliver
  • Developer platforms and CLIs
  • SDKs and typed API contracts
  • Operational dashboards
  • Documentation and integration guides
What it must establish
  • Shorter integration paths
  • Clear operator actions
  • Durable handover
Relevant record

iLold · Nia · Soroban Upgrades

A continuous blue signal ribbon moving through a black field
AI / distributed systemsPublic release
Agent infrastructure2026
5Security engineering

Assurance systems across the delivery

We integrate static analysis, execution testing, invariant checks, and release evidence into the engineering process.

What we deliver
  • Threat and invariant models
  • Static analyzers and custom detectors
  • Fuzzing and execution-path tooling
  • CI gates and release evidence
What it must establish
  • Traceable assumptions
  • Reproducible findings
  • Visible release risk
Relevant record

Eloizer · Solaris · Radiant · iLold

A deep blue curved surface forming a controlled abstract arch
EVM / Uniswap v4Research prototype
Protocol research2024
Network coverage

Architecture follows the execution model.

We do not transfer assumptions between runtimes. We define state, authorization, privacy, upgrade, and operating behavior for each target network.

1

Solana

Programs, Anchor, SVM infrastructure, and security tooling

2

EVM

Solidity, Foundry, protocol integrations, and analysis

3

Stellar

Soroban, WASM, contract release infrastructure, and SDKs

4

Canton

Daml, Ledger API, and privacy-aware workflows

5

Emerging

Tempo, RISC-V, machine payments, and new runtimes

Engineering lifecycle

Evidence grows with the implementation.

Decisions, tests, operating controls, and release requirements develop with the source. They do not arrive as a final appendix.

  1. 1

    Define

    Map objectives, state, permissions, dependencies, and acceptance evidence.

  2. 2

    Model

    Turn protocol behavior and operating constraints into explicit system boundaries.

  3. 3

    Build

    Implement contracts, services, interfaces, tests, and operational controls together.

  4. 4

    Prove

    Review source, artifacts, scenarios, runtime behavior, and unresolved risk.

  5. 5

    Release

    Ship with a controlled plan, clear ownership, diagnostics, and rollback guidance.

Engagement models

A commercial shape that matches the technical problem.

Every engagement has a written scope, an executive sponsor, a review cadence, and acceptance evidence.

Discuss the right engagement model
Start a project

Bring us the system, the network, and the constraint.

Share the objective, current system, network, and known constraints. We will identify the next technical decision.

Start the brief How we respond