Eliezer Suite

Eliezer Suite is an AI-powered blockchain freight logistics platform built on Arbitrum, purpose-designed for the US–Nigeria shipping corridor.

The problems it addresses:

International freight between the US and Africa is broken at three layers:

1. Trust and payment risk. Shippers pay carriers before goods arrive, or carriers move cargo without payment guarantees. There is no neutral escrow that automatically releases upon verified delivery. Disputes take weeks and require lawyers.

2. Regulatory opacity. Sanctions screening, HS code classification, customs clearance, and document verification all happen manually and off-chain. There is no tamper-proof record that a shipment was compliance-checked before departure. Customs disputes are expensive and opaque.

3. Paper-based title documents. The Bill of Lading is the legal document proving ownership of cargo in transit, is still largely paper-based. It cannot be used as on-chain collateral, sold to a trade finance buyer mid-voyage, or programmatically verified by a bank or customs authority.

How Eliezer Suite solves them:

- FreightEscrow: USDC locked on-chain at booking, auto-released to the carrier 48 hours after confirmed delivery. Either party can escalate a dispute; an AI arbitration agent reviews the evidence and submits a split ruling on-chain. No lawyers, no banks.

- ComplianceRecord: The AI agent runs OFAC/UN/EU sanctions screening, HS code verification, document completeness checks, and customs clearance confirmation before departure. Every result, whether pass or fail, along with the corresponding evidence hash, is written permanently on Arbitrum. Customs authorities and auditors get a tamper-proof compliance trail.

- BillOfLading (eBL): A negotiable ERC-721 NFT issued per shipment. Whoever holds the token has legal title to the cargo. Negotiable eBLs can be sold or pledged as collateral while the ship is at sea, enabling trade finance. Non-negotiable straight B/Ls are transfer-locked. The eBL is burned on delivery, extinguishing the title.

- ShipmentRegistry: Every status transition (Created → In Transit → At Customs → Delivered) is written on-chain by the AI agent after polling the Maersk Ocean API, port systems, and IoT sensors. Immutable custody chain, no data can be retroactively altered.

 - CargoClassifier (Arbitrum Stylus/Rust): A WASM smart contract that classifies cargo descriptions into HS codes, assigns a risk level, and determines license requirements, entirely on-chain, with no oracle dependency for the classification logic itself.

The result is a complete freight lifecycle managed by a single AI agent wallet with every critical decision, payment release, compliance approval, title transfer, dispute resolution, anchored on Arbitrum as an irrevocable on-chain record.

Phase 1                                     
Designed and built four production-grade Solidity contracts from scratch: ShipmentRegistry (full custody chain with 9-state FSM), FreightEscrow (USDC escrow with 48-hour dispute window and AI arbitration splits), BillOfLading (negotiable/non-negotiable eBL as ERC-721 NFT), and ComplianceRecord (on-chain sanctions, HS code, customs, and insurance checks). All contracts use OpenZeppelin v5.3 with AccessControl, ReentrancyGuard, SafeERC20, and custom errors throughout. Deployed to Arbitrum Sepolia.

Phase 2
Built a deterministic CargoClassifier contract in Rust using Arbitrum Stylus SDK 0.10.7 — the first version of the SDK with a completely rewritten host API. Overcame multiple undocumented breaking changes (new self.vm() host pattern, export-abi WASM poisoning, hyphen vs underscore WASM discovery bug, alloy version conflicts) by reading SDK source code directly. Deployed and activated on Arbitrum Sepolia (20.2 KB WASM, verified on Arbiscan).

Phase 3
Built a Next.js 14 frontend with Privy wallet authentication and an AI agent (OpenRouter/Qwen) that polls the Maersk Ocean API and drives all on-chain state transitions autonomously, registering shipments, recording compliance checks, marking deliveries, and resolving disputes, integrated real US-Nigeria shipping route data with live container tracking.                                                                           

Phase 4
Conducted two full security audit passes. First pass identified 2 Medium and 3 Low vulnerabilities. The second pass uncovered three additional Low findings. All 5 code-level vulnerabilities fixed: resolveDispute state machine gap (MEDIUM-01), missing pause guard on ERC-721 transfers (MEDIUM-02), missing zero-address validation across all constructors, markDelivered dispute window manipulation (LOW-04), raiseDispute terminal state bypass (LOW-05), and zero-address payee in createEscrow (LOW-06). Final test suite: 166 tests, 166 passing, 0 failing. Full audit report published in AUDIT.md. 

Bootstrapped.