Skip to content

Update ACiD (1714): chain is now live with public RPC + faucet#8262

Open
NoBanks wants to merge 6 commits intoethereum-lists:masterfrom
NoBanks:add-acid-1714
Open

Update ACiD (1714): chain is now live with public RPC + faucet#8262
NoBanks wants to merge 6 commits intoethereum-lists:masterfrom
NoBanks:add-acid-1714

Conversation

@NoBanks
Copy link
Copy Markdown
Contributor

@NoBanks NoBanks commented Apr 25, 2026

ACiD L2 (chain ID 1714) is now live and reachable.

  • L1 contracts on Sepolia, deployed 2026-01-06 (op-contracts/v5.0.0 via op-deployer v0.5.2)
  • L2 sequencing began 2026-04-24, currently producing blocks every ~2s
  • L1 batches landing on Sepolia (BatchInbox 0x0056f135b647ee0107935f102ea36da530ed084f)

Updates in this PR:

  • name: "ACiD" -> "ACiD Testnet" (it's a testnet chain settling to Sepolia)
  • rpc: added https://rpc-acid.livingagentic.me (Cloudflare-fronted, public)
  • faucets: added https://faucet-acid.livingagentic.me (0.001 ACiD ETH per address per 24h)
  • infoURL: github -> https://acid.livingagentic.me (project landing page)
  • explorers: added https://explorer-acid.livingagentic.me (Blockscout, indexing)
  • parent: added L2 metadata (Sepolia parent + bridge URL)
  • status: "incubating" -> "active"

Verification:
```
curl -X POST -H "Content-Type: application/json"
--data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
https://rpc-acid.livingagentic.me

returns {"result":"0x6b2"} = 1714

```

NoBanks and others added 6 commits January 3, 2026 16:48
Updated the chain name and native currency details.
ACiD L2 went live 2026-04-24. L1 contracts on Sepolia (deployed 2026-01-06).
Adding live RPC, faucet, explorer URLs and bridge metadata.
Status: incubating -> active.
@github-actions
Copy link
Copy Markdown

You successfully submitted a PR! Due to the amount of PRs coming in: we will only look at PRs that the CI is happy with. We can also not hold your hand getting the CI green - just look how others that where merged did it and RTFM. So as long as there is any CI check that reports an error - no human will look at this. You might be able to ask for some support after supporting the project - e.g. by sending funds to lists.eth. When you fixed things after a requested change - then you also need to (re-)request a review.

Copy link
Copy Markdown
Member

@ligi ligi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolve conflicts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants