What shows up before the chain gets misnamed
A vendor asks for the chain ID in an Ethereum wallet. A contract is written for the Ethereum virtual machine and someone asks where to deploy it. A bridge is described as the chain itself. A block explorer link is an Etherscan URL. The integration plan starts from the claim that the chain is EVM-compatible.
Those are the signs.
The short answer is the one the company brief states, and it is the answer this page is for. The JIL L1 is not EVM-compatible. It is an original ledger. Ethereum is reached by a bridge, not by running the EVM on this chain. JIL was not produced by forking Bitcoin, Litecoin, Ethereum, or any other chain. The original Layer-1 reading puts the engineering list in one sentence: the ledger, the compliance engine, the currency platform, and the proof layer are original engineering. The current source has no general-purpose virtual machine.
A fork inherits the design it starts from. An anonymity-first ledger is a poor fit for a ministry that must name who settled. A chain whose protocol has no concept of prohibition can only bolt compliance on afterwards, in an application or an off-chain gatekeeper, where it can be bypassed. A global policy set by an anonymous community is not a national rulebook. The original-layer reading gives the reason JIL was written: regulated finance, local monetary autonomy, and cross-border settlement with accountability. You license the core. You govern the domain. The provisioned chain is a sovereign cell. Issuance, policy, and day-to-day operations stay local.
That is why "not Ethereum" is a structural claim, not a slogan about speed or fees. On a public network in the Ethereum pattern, any validly signed transfer between any two addresses can settle, and a regulator cannot obtain from the protocol itself the assurance that a prohibited transfer is impossible. The sovereign domain reading describes that rented path as one of the two choices a sovereign should refuse. On this Layer-1 the rulebook is a condition of finality. ATCE, the Adaptive Trust, Compliance and Execution Engine, sits in the path of regulated actions: issuance, mint and burn, treasury movement, cross-border settlement, redemptions, and emergency controls. It returns a verdict, a reason code, and a SHA-256 commitment over the policy profile, the transaction context, and the outcome. It fails closed, and the current source has no general-purpose virtual machine for a contract to talk around it. Movement across jurisdiction zones is denied by default.
None of that makes this chain a copy of the Ethereum virtual machine with a compliance plugin added. The current source has no general-purpose virtual machine, so a contract written for Ethereum does not deploy here by being pasted across. The bridge is how value can meet Ethereum. It is not a statement that this ledger runs Ethereum's rules, Ethereum's address model, or Ethereum's client software. If a reader arrives from a page that uses a familiar comparison while explaining a cell, the sentence to keep is the company brief: Ethereum is a bridge, not a runtime on this chain.
Consensus is not an import either. ACL, the Attested Consensus Layer, asks two questions in one pass. Do the named validators agree on the order of transactions? And is each act attested, carrying an identity, a policy verdict, and a jurisdiction the network itself evaluated? Measured 2026-11-12, jil-mainnet-2 seals blocks with jil-abci-node under a third-party consensus engine. The image was created 2026-08-21. The signing set is eight, and a tip block sealed with six of those eight. The Attested Consensus Layer rule belongs to a separate binary that is not this process: six of ten with a verified enclave quote and a verified state-transition proof, eight of ten when those proofs are absent, and nine of ten when an inspection fails. Seven does not pass on that rule. A payment request, on that separate rule, still needs a yes from every active validator; one objection fails that request and the chain continues. JIL Sovereign Technologies Incorporated operates every validator. The chain is jil-mainnet-2. Measured 2026-11-12, ten hosts are operated by JIL and eight are in the signing set Sovereign Technologies Incorporated, permissioned, on one hosting provider. A zone name on a validator is a label, not a street address. The named validators reading is the full account. A recorded showcase measurement showed 10 in the set and 9 signing, all operated by JIL. That is not Byzantine fault tolerance. Binding an inter-cell light client to production ACL signatures is on the hardening roadmap, as the federation reading names it.
Attestation seals are hybrid: a classical Ed25519 signature and a post-quantum ML-DSA-65 signature, and both must verify. Validator signing is classical Ed25519 today. Post-quantum validator signing is on the roadmap. The seals and the block signatures use different keys.
Public figures for the authored system, as the original-layer reading states them, are about 2.8 million lines of source and 350 or more services. The count is authored source, not generated output and not vendored dependencies. The company brief also records 177 patent claims filed, patent pending and not granted, 9 trademarks filed and not registered, and 332 platform attestation checks. Those figures are the estate's public canon. They are not a statement that a patent has been granted, and they are not a statement that this chain inherited someone else's client.
The default service key is a 2-of-3 threshold with all three shares held server-side by JIL; there is no user-held shard, and authorizing a signature is not holding a key.
Proof DEX and the Digital Currency Platform sit on this original ledger. A currency object is not a token deployed onto a public chain and hoped to behave. Mint and burn belong to the issuer's keys. Issuance on a demonstration domain stays off. A listing on Proof DEX is not a statement that the instrument is a security, or that it is not. Classification is a local legal question. Nothing on this site is an offer of securities or virtual assets. The Federation Thesis argues the engineering at length, including the roadmap. Use that page when the question is no longer "is this Ethereum" and has become "what is actually built."
Questions
Can I deploy an Ethereum contract on this chain?
No. The JIL L1 is not EVM-compatible. The current source has no general-purpose virtual machine to deploy it to. Ethereum is reached by a bridge, not by running the EVM here.
Was the ledger forked from an existing chain?
No. It is not a fork of Bitcoin, Litecoin, Ethereum, or any other chain. The ledger, compliance engine, currency platform, and proof layer are original.
Does the bridge mean this chain is an Ethereum sidechain?
No. A bridge is how this ledger can meet Ethereum. It does not import Ethereum's consensus, Ethereum's virtual machine, or a rule that any valid signature settles.
What agrees on a block?
Agreement is set per action. Measured 2026-11-12, a tip block sealed with six of the eight validators in the signing set. The process is jil-abci-node under a third-party consensus engine. The six-of-ten and eight-of-ten Attested Consensus Layer rule is a separate binary and is not this process. A payment request, on that separate rule, needs a yes from every active validator; one objection fails that request and the chain continues. A bridge withdrawal needs agreement from every responding validator. Ten validators, all operated by JIL, permissioned. A recorded showcase measurement showed 10 in the set and 9 signing. That is not Byzantine fault tolerance.
Are the seals the same keys that sign blocks?
No. Attestation seals are hybrid Ed25519 and ML-DSA-65. Validator signing keys are Ed25519 software keys. Post-quantum validator signing is on the roadmap.
Read with this
An original Layer-1, What is a Sovereign Domain, ATCE, Post-quantum, The proof standard, Named validators, Three-shard custody, Federation Thesis.
