Automatic loading of Neon Web3 Proxy, installation of postgresql via docker compose, optimization of server performance and connection to the monitoring dashboard
The Neon EVM is an Ethereum-like environment that makes it possible for Solidity contracts and Ethereum-like transactions to function on Solana. In the case of the Neon EVM, Ethereum-like transactions are wrapped into Solana transactions by an intermediary proxy server and sent to the Neon EVM, which executes them in parallel. To facilitate this parallel execution of smart contracts, the Neon EVM ensures that each contract keeps its data in its own Solana storage, and account balances used to pay for Neon transactions are also separated.
A role performed by a Solana account using a software tool. Within Neon EVM, an operator is provided with software in the form of a proxy in order to fulfill certain functions. The operator can deploy one or more proxies. The operator can also configure one proxy for multiple operators, as well as run several proxies with different settings.
The Ansible scripts that we have created for this purpose are a search for best practices and a call for the community of operators to work together. Please use them, enjoy them and improve them.
An RPC server requires at least the same specs as a Solana validator, but typically has higher requirements. For more information about hardware requirements, please see the Solana docs. In particular they recommend:
- 16 cores
- 256 gb memory
For the EVM proxy, the hardware requirements. NeonEVM recommends:
- 4 cores
- 16 gb memory
In sum, this suggest that a combined node running NeonEVM and the Solana RPC could have the following recommended specs:
- 16-24 cores of a recent processor Zen 2, Zen 3 or latest Cascade Lake Refresh Xeons
- 256 gb memory
A suitable processor might be EPYC 7443P or 7413P.
Considering the bandwidth requirements of Solana we recommend using a bare metal host rather than running on the cloud, as you will otherwise pay high egress fees as well as (potentially) see low performance due to the virtualization layer of cloud providers.
The following software should be installed on your Neon EVM proxy:
OS Ubuntu 20.04 or later
Solana Cluster Requirements (optional)
If you want to use a local Solana cluster, you need to meet the following requirements:
Solana cluster with --enable-rpc-transaction-history enabled. Solana cluster with --enable-rpc-bigtable-ledger-storage enabled.
Networking Internet service should be at least 300 Mbps.
-
Log in to your server
-
If you are not have a key pair file - script create it automatical
-
If you are have the key pair file (you can also upload it via scp if you prefer):
nano ~/validator-keypair.jsonPaste your key pair, save the file (ctrl-O) and exit (ctrl-X).
-
Run this command…
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/ElagabalxNode/neon-manager/main/install/install_operator.sh)"…and follow the wizard’s instructions. If your Solana RPC node is installed locally, select the appropriate menu item or If the RPC node has its own entrypoint, select the menu item and paste the address into the line.
And enter your own:
- (Operator name)
- (Postgres DB name)
- (Postgres DB password)
That's it, you are all set!
- Join our Medium medium/elagabalx
- Join our Discord community discord/elagabalx
- Donate Sol to ElagabalX Validator Identity Account on Solana: 6m5vsg6XfsVUroo1zzZmB4YgFmV6ykLiwEXb6choovpc