Skip to content

BitVault BVM20 (chainId 31338)#8308

Open
bitvault-developers wants to merge 2 commits into
ethereum-lists:masterfrom
bitvault-developers:add-bvm20-chain-31338
Open

BitVault BVM20 (chainId 31338)#8308
bitvault-developers wants to merge 2 commits into
ethereum-lists:masterfrom
bitvault-developers:add-bvm20-chain-31338

Conversation

@bitvault-developers
Copy link
Copy Markdown

Add chain BitVault BVM20 (chainId 31338)

This PR adds BitVault BVM20 to the chains registry.

Network details

About BitVault

BitVault is a multi-tier blockchain ecosystem combining a custom L1 (PoBV — 11-algorithm multi-PoW consensus) with the BVM20 EVM-compatible execution layer. BVM20 hosts the project's DeFi protocols (lending, staking, perps, options, peg, DAO, insurance, fixed-rate lending), payment channels (BVLN), and 177 wrapped-token contracts for cross-chain swap counterparty roles.

Verifications

  • chainId 31338 is unclaimed in the registry
  • JSON validates against existing schema (matches Ethereum mainnet schema, minus optional ens/slip44 fields)
  • Icon pinned on IPFS — CID bafybeie4dm3zj756hgyuv4catimhj5wubgzzgz6y22qsly7nuzbbbgqqee
  • Resolves on ipfs.io, gateway.pinata.cloud, dweb.link
  • Icon is 1080×1080 PNG with transparent background

Note on RPC/Explorer URLs

The RPC and explorer URLs are configured but the underlying public infrastructure (Cloudflare tunnel + Blockscout instance) is being set up as part of the network's pre-launch checklist (target launch: June 15, 2026). The URLs will be live before mainnet activation.

If reviewers prefer to merge after the URLs respond, please let me know and I'll reply on this PR once they're up.

Files added

  • _data/chains/eip155-31338.json — chain definition
  • _data/icons/bitvault.json — icon manifest

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 9, 2026

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.

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.

1 participant