Skip to content

Conversation

brainark
Copy link

Summary

This PR adds BrainArk Network (Chain ID 1236) to the chains registry.

Chain Details

Technical Specifications

  • Consensus: IBFT2 (Istanbul Byzantine Fault Tolerance)
  • Block Time: 2 seconds
  • Validators: 4 nodes
  • Genesis Supply: 1,000,000,000 BAK tokens
  • Features: EIP155, EIP1559 compatible

Files Added

  • _data/chains/eip155-1236.json - Chain configuration
  • _data/icons/brainark.json - Chain icon (IPFS: bafybeih44bmgucw5xjeinh5dwbkpvyublma6vbxxdmi4bkopd2ym3sqcqq)

Production Status

Live Production Network

  • Blockchain is actively producing blocks
  • RPC endpoint is operational and responding
  • Explorer is accessible at https://explorer.brainark.online
  • All technical infrastructure is operational

Verification

  • Chain ID 1236 is not currently in use (verified available)
  • IPFS icon is publicly accessible
  • All endpoints are live and functional
  • Follows ethereum-lists/chains format requirements

The BrainArk Network is a production-ready EVM-compatible blockchain designed for decentralized applications with fast 2-second block times and IBFT2 consensus.

Copy link

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.

Add missing networkId field and fix JSON structure
- Standardize JSON formatting with 2-space indentation
- Ensure consistent structure for ethereum-lists validation
- Fix any potential formatting issues causing CI failures
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