How LastcoinVision is built
A Cosmos SDK chain with a fixed-supply, decaying-emission economy, dual smart-contract environments, and a privacy-first identity layer.
Consensus
CometBFT (Tendermint-lineage) BFT consensus with a delegated validator set. Staking rewards come from a genesis-funded pool on a 10-year exponential decay curve, not open-ended inflation.
Fee market
An EIP-1559-style dynamic base fee, with a governance-tunable split — a portion burned, the remainder to validators and treasury.
Interchain
IBC-enabled (transfer and interchain accounts) — LCV is a Cosmos SDK chain first, so it inherits the IBC ecosystem rather than requiring a bespoke bridge.
Smart contracts
Two environments, one chain: CosmWasm (governance-gated code upload, permissionless instantiate) and an Ethereum-JSON-RPC-compatible EVM with a native two-way ulcv bridge. Standard tooling works unmodified — Hardhat, Foundry, wagmi, CosmJS.
Identity & privacy
W3C-style DIDs (did:lcv:<address>) and credential-hash anchoring by governance-authorized issuers. Personal data never touches the chain — only hashes and revocation status, plus a queryable account tier derived from them.
What this doesn't do yet
Every module ships a SPEC.md with its own limitations section. The ones that matter most if you're evaluating this for a real deployment:
Voting is commit-reveal, not ballot-secret
x/voting's commit-reveal scheme lets anyone recompute a tally from public data, but a vote's contents become visible at reveal time to anyone watching the chain during that window. Ballot secrecy in the sense a real election needs — where no one, including validators, can link a revealed vote back to a voter — requires threshold encryption and ZK nullifiers, neither of which is implemented. Do not use this for a real election.
Credential verification is signature-based, not zero-knowledge
MsgPresentCredential checks a signature against the credential registry today. There's a defined ZKVerifier interface for selective-disclosure proofs, but its current implementation is an explicitly marked stub — no ZK proof system is wired in yet.
MetaMask and CLI-generated keys aren't portable by mnemonic
The chain's BIP44 coin type is Cosmos's standard 118, unchanged for compatibility with existing Cosmos tooling. An eth_secp256k1 key from lcvd keys add and a MetaMask account don't derive the same address from the same seed phrase — each wallet is its own independent key, not two views of one account.
This is testnet/devnet software
No independent security audit has been performed. No production mainnet exists. Nothing on this site is an offer or solicitation — see the token page's disclaimer.