Blockchain Developer

** READ CAREFULLY * Experts only

Kaizen L1 — Gravity-based MVP (Exploratory Track)

Project Context

We are evaluating Gravity Chain as a potential foundation for Kaizen, a high-performance EVM Layer-1 with a strong focus on parallel execution, sub-second finality, and protocol-level safety for token launches.

This role is not only about implementation.
It is also about technical evaluation, feasibility analysis, and architectural decision-making.

?

JOB OFFER — Senior Blockchain Engineer (Gravity / Parallel EVM / L1)

Title

Senior Blockchain Engineer – Gravity L1 / Parallel EVM (Architecture & MVP)

?

Project Description

We are exploring the development of Kaizen, a next-generation EVM-compatible Layer-1, with performance and safety as first-class citizens.

One of the candidate stacks is Gravity Chain, a high-performance L1 developed by Galxe, featuring:
• parallel EVM execution
• pipelined / BFT-style consensus
• sub-second finality targets
• advanced security and omnichain primitives

Our goal is to assess whether Gravity can serve as a solid, forkable, and maintainable base for Kaizen’s MVP — or whether a more pragmatic stack (e.g. Avalanche Subnet-EVM) is preferable.

?

Responsibilities

1. Architecture Evaluation (Critical)
• Analyze Gravity Chain’s architecture:
• consensus
• execution (parallel EVM / Grevm)
• state model
• validator and networking assumptions
• Assess:
• forkability
• customizability
• long-term maintainability
• Identify technical risks, bottlenecks, and unknowns

2. MVP Feasibility & Design
• Define what a Gravity-based MVP would realistically include
• Evaluate achievable performance targets (latency, block time, finality)
• Propose a minimal but stable configuration (validators, parameters)

3. Safe Launchpad Compatibility

Evaluate how Gravity could support a Safe Launchpad, including:
• mandatory token factory
• enforced vesting (team / insiders)
• liquidity lock
• timelocks on sensitive actions
• on-chain verification / registry

Key question:

What should live at protocol level vs system contracts vs application layer?

4. Comparative Analysis
• Provide a clear technical comparison between:
• Gravity-based L1
• Avalanche Subnet-EVM–based L1
• Focus on:
• risk
• time-to-market
• debugging complexity
• long-term extensibility

?

Required Skills (Must-Have)
• Senior-level blockchain engineer
• Strong EVM internals knowledge
• Experience with high-performance L1s or L2s
• Deep understanding of:
• BFT / PoS consensus
• parallel execution models
• state management & determinism
• Ability to read and reason about large Rust / Go codebases
• Comfortable operating with incomplete documentation

?

Strong Plus
• Experience with:
• parallel execution engines
• custom EVM runtimes
• Aptos / Move / Sui / Solana-style architectures
• Background in:
• protocol security
• performance engineering
• DeFi infra / MEV considerations

?

Expected Deliverables (Consulting Phase)

Within 2–4 weeks:
1. Technical assessment of Gravity as an L1 base
2. Clear list of pros / cons / risks
3. MVP scope proposal (what is realistic, what is not)
4. Recommendation:
• Proceed with Gravity
• Use Gravity later (Phase 2)
• Prefer alternative (e.g. Avalanche)

(Implementation may follow depending on outcome.)