Lightchain Protocol AI Decentralized blockchain uniting transparency, scalability, and innovation for the future of AI.

Joined November 2024
🔐 Lightchain AI — Wallet Security ReminderSecurity starts with you. As a reminder to everyone in the Lightchain AI community Never share your seed phrase or private keys — with anyone, under any circumstances. We will never ask you to connect your wallet, disclose credentials, or “verify” anything via DM. Do not engage with unsolicited private messages claiming to be support, team members, moderators, or partners. These are almost always scams. All official announcements and support happen in public channels only. If it sounds urgent, secret, or too good to be true — it’s a scam.Protect your assets Use a hardware wallet when possible Double-check URLs and domains Verify announcements through official channels Report suspicious accounts immediatelyStay vigilant and help keep the Lightchain AI ecosystem secure.
76
3
266
105,242
Most AI runs on compute you can't inspect. Here's how open compute actually works on Lightchain ↓
4
32
2
71
2,473
The network re-runs a sample of jobs to check the work, and any answer can be disputed. New models join through community proposals and onchain votes, which also set what each model costs.
1
1
7
325
That's open compute: open models, independent operators, and a record anyone can check. See who's serving right now ↓ workers.lightchain.ai
2
10
313
Calling an open model with our developer API is simple. Just point your OpenAI code at Lightchain testnet, and every answer gets a receipt that shows you: → an onchain job ID → a transaction hash → the operator's info Open compute, built for you.
6
34
3
74
3,701
An open network grows stronger with quality contributions. On Lightchain, every model proposal and vote happens onchain. We're building verifiable, secure and community-owned compute for the onchain era.
9
39
3
94
3,613
If you've used Remix, you already know how to deploy on Lightchain. The Lightchain IDE lets you write, compile and deploy contracts from your browser. Give it a spin, it's buttery smooth.
9
33
3
77
3,553
T-minus 90 seconds. The Lightchain testnet relaunches from a fresh genesis at 06:30 UTC. Same chain id, new foundation underneath: the first live build of the architecture we've spent the last 8 months on. Mainnet is untouched. Testnet tokens reset. Faucet reopens shortly after the first blocks. Watch it come alive: testnet.lightscan.app
3
29
81
3,330
"Put-down and pick-up" hashes. A user posts a commitment hash on the base chain, the sequencer is obliged to pick the matching transaction up within K ticks or the registry refuses its next manifest. That is exactly the force-inclusion queue in v3, generalized to commitments so the content stays private until inclusion. It buys censorship resistance with an L1-enforced deadline. It does not stop the operator from choosing the order within the tick.
2
25
2
53
2,700
Lightchain testnet is relaunching. Mainnet is untouched. Same chain id, 8200. New genesis, clean state. Testnet balances and contracts reset, the faucet refills, the explorer reindexes from block zero. Nothing on mainnet restarts, changes or needs your attention. The relaunch is the first public step of an architecture we have been building for the last eight months, and the new testnet is built to run it from genesis. Here is what we can say today. Every blockchain you have used so far makes one node do three jobs at once: decide the order of transactions, execute them, and finalize them. That is why the whole network moves at the speed of one machine. The new design pulls those three jobs apart and gives each its own engine. Ordering becomes a replicated sequencer. Your transaction is acknowledged in tens of milliseconds with a fixed place in one global sequence. It never executes anything, which is exactly why it can absorb bursts without flinching. Execution becomes independent EVM shards. Each shard is a complete chain. Each builds one block per tick, and ticks are measured in hundreds of milliseconds, not seconds. Every shard block is a pure function of public inputs: block number, timestamp, randomness, gas limit, all derived by a fixed rule with no operator discretion anywhere. That is not a detail. It is what makes the whole system provable later without a redesign. Finality stays on the chain you know. Every L1 block anchors each shard's state roots and commitments. The L1 becomes the settlement layer underneath, and inherits nothing new to execute. Value moves through escrow, never minting. A deposit locks on the L1 and lands on a shard in the next tick. An exit is proven against roots already anchored on the L1 and works even if the sequencer is gone. History is written once, content-addressed, with every hash on chain, so a shard's disk holds its state rather than its past. The AI compute marketplace moves to its own shard with a protocol rebuilt for it: fewer transactions per job, job ids you know before you send, encrypted prompts and responses kept off the chain with their hashes on it, workers that subscribe to events instead of polling the chain four times a second. And a second class of worker is coming that does not need a GPU at all. What stays: Proof of Intelligence as the useful-work layer, end-to-end encrypted prompts on the GPU tier, the validator set, the token, EVM compatibility and the tooling you already use. What changes: how far it scales, and how fast it feels. Date, genesis details and the operator guide will be posted here and in Discord before the switch. Benchmarks and the full technical write-up come when they are measured, not before.
6
30
2
76
4,109
Introducing Lightchain Signal, our flagship creator program We're platforming AI and crypto voices who explain the open network for open models, in their own words. Applications are now open ↓
23
40
7
124
6,970
The Lightchain Bridge just got upgraded ⚡️ - Fresh UI - Mobile version loads 10x faster - Buy & Bridge ETH to native LCAI in one flow - See price impact before you sign - Built-in mainnet/testnet switch Go fast → bridge.lightchain.ai
14
43
3
94
3,909
Your AI workflow can be retired with one email. Open weights don't vanish when a company changes plans. Lightchain serves LLMs like gpt-oss and Qwen3 through independent operators, so that no single company can pull them.
12
35
3
64
3,439
Imagine if someone could read all your prompts. This is how most AI setups work. But not ours. Lightchain Desktop rooms are encrypted and peer-to-peer. No account, no central server holding your messages, and open-source code anyone can check.
15
30
6
77
4,014