Company

A software engineering company with direct technical ownership.

Eloiz builds protocol, infrastructure, and product software for critical operations. The executives responsible for each engagement stay involved from scope through handover.

Why Eloiz
We treat contract logic, backend services, security controls, and release operations as one system.
Engagement governance

A defined delivery system.

Four controls keep ownership, technical decisions, and acceptance evidence clear from the first review through handover.

Accountability

Executive sponsor

A named executive remains accountable for scope, technical direction, and client communication.

Scope control

Written scope

The written scope defines objectives, boundaries, dependencies, acceptance evidence, and unresolved risks.

Technical control

Evidence reviews

We review architecture, implementation, and release decisions against technical evidence.

Transfer

Controlled handover

We transfer repositories, decisions, operating context, and known gaps with the delivered system.

Executive leadership

Executive accountability.

The executives responsible for an engagement make its commercial and technical decisions. Eloiz adds specialist capacity when the scope requires it.

Chief Executive Officer
Sergio Corrales, Chief Executive Officer of Eloiz

Sergio Corrales

Protocol engineering and security research

Leads protocol engineering and security work across EVM and non-EVM ecosystems. His experience includes smart-contract development, static analysis, fuzzing, formal methods, and private protocol assessments.

Chief Technology Officer
Biel Carpi, Chief Technology Officer of Eloiz

Biel Carpi

Backend blockchain infrastructure and smart contracts

Builds backend and blockchain infrastructure, distributed systems, and smart contracts. His work emphasizes explicit interfaces, recoverable state, operational reliability, and release evidence.

Operating principles

Decision standards.

Evidence

Evidence over posture

We separate facts that source, tests, and runtime behavior prove from inferences and open risks.

Ownership

Defined scope, clear ownership

We define the scope before delivery. The engineers who make architecture decisions remain responsible for them.

Network fit

Network-native design

Execution, storage, privacy, upgrade, and operating models shape the architecture from the start.

Handover

Durable handover

Each delivery includes reproducible evidence, clear boundaries, and the operating context that the next team needs.

Public record

Technical claims with direct evidence.

Our public record includes Soroban release infrastructure, analysis tools for Solana and EVM, protocol research, and agent infrastructure. We describe private client work only when the information is public.

Contact

Start with the system you need to build.

Tell us the objective, target network, and operating constraints. We will propose a scope, delivery plan, and evidence standard.

hello@eloiz.xyz