Skip to content

Open Problems

This page tracks open areas where outside help would be especially valuable.

It is not a formal roadmap. It is a list of problems that are either actively relevant now or likely to become relevant soon.

Eternix has protocol specifications, but it still needs a proper public-facing documentation layer.

Open needs:

  • explaining the project clearly to non-experts
  • splitting large protocol concepts into readable pages
  • writing contributor-friendly docs
  • improving conceptual examples and diagrams
  • translating specification language into practical explanations

This is one of the highest-leverage contribution areas right now.

Eternix has been tested with MetaMask-oriented RPC behavior, but one known issue is that a transaction may execute while MetaMask continues to show it as pending.

Potentially relevant areas:

  • receipt behavior
  • transaction lookup RPC methods
  • status fields
  • block inclusion reporting
  • MetaMask assumptions inherited from Ethereum

Help diagnosing this would be immediately useful.

Eternix needs native wallet tooling, especially because some protocol features are not naturally represented by existing Ethereum wallets.

Initial useful scope:

  • generate/import accounts
  • show balances
  • send ETX
  • later, support First-Class Tokens and Eternix-specific transaction fields

A minimal CLI wallet would already be valuable.

The local blockchain foundation needs to become a real networked testnet.

Open work includes:

  • node discovery
  • peer connection strategy
  • block and transaction propagation
  • faulty or malicious peer behavior
  • initial sync behavior

This is a major systems milestone.

Eternix plans an EVM-compatible execution environment called XVM.

The chain is not yet at the point where full VM integration is the immediate blocker, but this will become important after the lower-level testnet foundation is ready.

Relevant areas may include:

  • transaction execution model
  • gas accounting
  • state persistence
  • contract deployment and calls
  • preserving compatibility while supporting Eternix-specific features

The following protocol areas are especially worth attacking:

  • Proof of Ash incentive assumptions
  • burn-offset validator incentives
  • same-slot conflict neutralization
  • protocol-generated block edge cases
  • validator slashing and cooldown rules
  • governance-controlled fee-token pricing

If you believe one of these systems can be exploited, distorted, or simplified, that feedback is useful.