GenesisL1 Media FAQ

No. GenesisL1 has produced blocks since November 2021. The July 21, 2026 release publishes Version 1.0 of the technical whitepaper documenting the operating network, deployed protocols, evidence, limitations and roadmap.

GenesisL1 makes scientific data objects, exact model artifacts, deterministic execution, replayable results, programmable rights, encrypted intellectual property, settlement and governance composable within one public decentralized state.

GenesisL1 is intended to be infrastructure, not an application renting another network's blockspace. A dedicated chain allows its community to govern consensus, execution, state limits, gas policy, security and public-goods funding without depending on a host-chain sequencer, foreign gas asset, proprietary model API or single database operator.

L1 is the network's native infrastructure asset. Transactions and scientific state writes are metered in L1; validators and delegators bond L1 to secure proof-of-stake consensus; bonded voting power participates in governance; and the community pool is denominated in L1. Applications may also use L1 for settlement.

No. The whitepaper publication is not a token offering, private allocation, fundraising round, exchange-listing announcement or invitation to purchase L1.

The operating network, EVM execution, staking and governance; MOLNFT molecular collections and second-generation chain state; GLAST local sequence search; GL1F Model NFTs and deterministic fixed-point inference; a neural-inference proof of concept; and CIPNFT's encrypted-capsule and provenance core. The paper separately identifies proof-of-concept, in-development, planned and unaudited components.

No. GenesisL1 can make an exact object, model, input, execution rule, output, license or transfer independently inspectable. Scientific validity still depends on methods, evidence, experimental validation, replication and review.

No. GenesisL1 applies selective state placement. Compact, high-value and contract-composable artifacts may be stored fully on-chain. Large datasets can be represented by hashes, CIDs or Merkle commitments while their bulk bytes remain off-chain. A rewarded IPFS sidecar is under development and is not yet a deployed service.

Persistent state is metered in L1, creating an admission cost for scarce replicated storage. Fully on-chain storage is reserved for objects whose integrity and composability justify universal replication; bulk scientific data can use compact on-chain commitments. The whitepaper calls for a publication-grade storage-sustainability study to quantify physical database amplification, synchronization and archive costs.

That is not the stated operating model of v1. CIPNFT v1 is an evidence-rich exchange mechanism intended principally for attributable, documented and contractually bound counterparties. It records the transfer chronology but does not provide atomic fair exchange or prevent a recipient from retaining knowledge after disclosure. A hardened successor and independent audit are roadmap requirements.

GenesisL1 does not make that broad claim. CIPNFT includes an optional experimental ML-KEM-768 envelope mode for protecting data-encryption keys. The implementation has not received an independent cryptographic audit, and ordinary chain-account signatures are not post-quantum.

No comprehensive independent audit of the node integration or canonical MOLNFT, GL1F and CIPNFT contract suites has yet been published. The whitepaper identifies independent audits, reproducible builds, formal threat models and public remediation records as priority milestones.

Mikhail Fedorov, a medical doctor working across bioinformatics, data science and in silico biomedical research. He holds a Graduate Certificate in Bioinformatics from Harvard University Extension School.

Protocol state is finalized through bonded validator consensus, while eligible bonded voting power participates in on-chain governance. Network state, proposals, voting records and validator power are publicly inspectable.

Use the explorer, source repositories, deployed applications, contract addresses and verification endpoints linked from the press page and whitepaper.