Company

Built for accountable technical delivery.

Eloiz develops protocols, infrastructure, and software products for critical operations. The executive team remains accountable from architecture through delivery.

Why Eloiz
Blockchain code is one part of the system. Eloiz also makes its assumptions, controls, and operating requirements clear.
Engagement governance

Control from mandate to handover.

These controls keep ownership and technical decisions clear from the first scope review through handover.

G / 1

Executive sponsor

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

G / 2

Written mandate

The written mandate defines objectives, boundaries, dependencies, acceptance evidence, and unresolved risk.

G / 3

Evidence reviews

The team reviews architecture, implementation, and release decisions against technical evidence.

G / 4

Controlled handover

Repositories, decisions, operational context, and remaining unknowns transfer with the delivered system.

Executive leadership

Named accountability at company level.

The executives who own the mandate make the commercial and technical decisions. Eloiz adds specialist capacity when the scope requires it.

1Chief Executive Officer
Sergio Corrales, Chief Executive Officer of Eloiz

Sergio Corrales

Protocol engineering & security research

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

2Chief Technology Officer
Biel Carpi, Chief Technology Officer of Eloiz

Biel Carpi

Backend blockchain infrastructure & smart contracts

Builds backend and blockchain infrastructure, distributed systems, and smart contracts, with an emphasis on explicit interfaces, recoverable state, operational reliability, and release evidence.

Operating principles

How we make decisions.

1

Evidence over posture

We separate what source, tests, and runtime behavior prove from what remains an inference or an open risk.

2

Defined scope, clear ownership

We keep each scope clear. The engineers who make architecture decisions remain responsible during delivery.

3

Network-native design

Execution, storage, privacy, upgrade, and operating models are primary inputs. They are not adapter details.

4

Durable handover

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

Public record

Direct evidence for our technical record.

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

Contact

Discuss your next engineering mandate.

Tell us the objective, operating environment, and current technical boundary. We will identify a suitable scope and review process.

hello@eloiz.xyz