An attempted fork of the scroll Layer 2 for Ethereum Classic.

We tried to deploy scroll L2 on Ethereum Classic. As part of this journey we compiled our own custom blockchains using geth. If you read the README linked below you will see the command `make dev_docker` which compiles these geth client. We had to update these genisis.json files so that we had actual assets on the blockchain.

We had a problem with the ZK VM where we we were unable to run the prover on transactions actually completed. We were able to compile the ZKVM prover and get the zk smart contracts deployed.

https://github.com/nero-layer/scroll-docker-stuff/blob/paul/docker-stuff/README.md

We have tried to create an evm compatible bridge on mantle. Even though we haven’t been able to compile it fully, we did come quite far

GitHub.com/anuragbejju/BlockHack-evm

Blocklance Mainnet: EVM-Compatible Chain Built Using Avalanche's Subnets

Project Name: Blocklance Mainnet

Purpose: To create a decentralized, EVM-compatible chain leveraging Avalanche's subnets to offer enhanced scalability, interoperability, and robustness tailored for modern decentralized applications.

Technology Used: Avalanche CLI, AVAX Subnets, EVM (Ethereum Virtual Machine).

Chain Setup and Development Process:

1. Local Setup Using Avalanche CLI:
   • Initialized a new local subnet using the Avalanche CLI.
   • Configured the subnet settings to facilitate the creation of the new Blocklance Mainnet.
   • Created a new blockchain instance within this subnet, ensuring it's EVM compatible.
   • Started the subnet and successfully interacted with the local instance of the Blocklance Mainnet.
2. Attempt to Deploy on Fuji Testnet:
   • Initialized a subnet on the Fuji testnet using Avalanche CLI.
   • Attempted to sync the subnet with the testnet. However, the synchronization process was lengthy and wasn't completed within the expected time frame. This is possibly due to network congestion or other network-specific intricacies.

Running Subnets:

• On localhost: The subnet was successfully initialized and run using Avalanche CLI. The local instance of the Blocklance Mainnet was accessible, and interactions were seamless.
• On Fuji Testnet: The subnet was initialized, but due to prolonged syncing times, it couldn't be fully operationalized.

Transactions:

• Local transactions were successfully executed on the localhost setup of the Blocklance Mainnet. The EVM compatibility ensured seamless interactions similar to Ethereum-based transactions.

Conclusion and Future Steps: The project successfully established the Blocklance Mainnet using Avalanche's subnets on a local setup. The next steps would involve:

• Troubleshooting the syncing issues on the Fuji testnet.
• Enhancing the Mainnet's features, security, and scalability aspects.
• Engaging with the community for testing, feedback, and further development.

Blocklance Mainnet: EVM-Compatible Chain Built Using Avalanche's Subnets

Project Name: Blocklance Mainnet

Purpose: To create a decentralized, EVM-compatible chain leveraging Avalanche's subnets to offer enhanced scalability, interoperability, and robustness tailored for modern decentralized applications.

Technology Used: Avalanche CLI, AVAX Subnets, EVM (Ethereum Virtual Machine).

Chain Setup and Development Process:

1. Local Setup Using Avalanche CLI:
   • Initialized a new local subnet using the Avalanche CLI.
   • Configured the subnet settings to facilitate the creation of the new Blocklance Mainnet.
   • Created a new blockchain instance within this subnet, ensuring it's EVM compatible.
   • Started the subnet and successfully interacted with the local instance of the Blocklance Mainnet.
2. Attempt to Deploy on Fuji Testnet:
   • Initialized a subnet on the Fuji testnet using Avalanche CLI.
   • Attempted to sync the subnet with the testnet. However, the synchronization process was lengthy and wasn't completed within the expected time frame. This is possibly due to network congestion or other network-specific intricacies.

Running Subnets:

• On localhost: The subnet was successfully initialized and run using Avalanche CLI. The local instance of the Blocklance Mainnet was accessible, and interactions were seamless.
• On Fuji Testnet: The subnet was initialized, but due to prolonged syncing times, it couldn't be fully operationalized.

Transactions:

• Local transactions were successfully executed on the localhost setup of the Blocklance Mainnet. The EVM compatibility ensured seamless interactions similar to Ethereum-based transactions.

Conclusion and Future Steps: The project successfully established the Blocklance Mainnet using Avalanche's subnets on a local setup. The next steps would involve:

• Troubleshooting the syncing issues on the Fuji testnet.
• Enhancing the Mainnet's features, security, and scalability aspects.
• Engaging with the community for testing, feedback, and further development.

Building your own EVM-compatible Layer 1 chain can be a complex undertaking, but I can provide you with an overview of the general process involved. Here are the high-level steps you would typically follow:

1. Define the network's goals and requirements: Before diving into implementation, it's crucial to outline the objectives of your network. Determine the consensus mechanism (e.g., Proof of Authority, Proof of Stake, etc.), block time, transaction throughput, token economics, and any unique features or improvements you want to introduce.
2. Select a consensus mechanism: Choose a consensus mechanism that aligns with your network's goals. Proof of Authority (PoA), Delegated Proof of Stake (DPoS), and Proof of Stake (PoS) are commonly used in EVM-compatible chains. Research each consensus mechanism to understand their implications and select the one that suits your requirements best.
3. Design the architecture: Plan the network's architecture, including the protocol design, block structure, transaction format, gas model, virtual machine configuration, and other technical aspects. Consider scalability, security, and interoperability with other networks.
4. Set up the development environment: Install the necessary tools and dependencies to create and deploy your network. This typically includes setting up a local development environment with tools like Ganache or Hardhat for testing and Truffle for smart contract development.
5. Develop and deploy the network: Implement the network's codebase using a programming language that supports EVM compatibility, such as Solidity or Vyper. Create the genesis block, smart contracts, transaction validation rules, and the consensus mechanism. Test and debug your code thoroughly to ensure its reliability and security. Then, deploy your network to a testnet or mainnet environment.
6. Build infrastructure and tooling: Develop or configure the necessary infrastructure components to support your network. This includes setting up nodes, creating APIs for interacting with the network, implementing an explorer to view blocks and transactions, and ensuring the overall network's stability and uptime.
7. Security and auditing: Perform comprehensive security audits to identify vulnerabilities and ensure the network's robustness. Collaborate with external auditors and conduct thorough testing to ensure the safety of user funds and smart contracts.