OCAP/Foreign Chain settings for ArcBridge Node

Thank you for expressing interest in running an ArcBridge node! I understand that you have gone through a series of challenges to reach this point.

To help you get your node up and running, here are some important parameters to consider:

OCAP_CHAIN_HOST : The API provider for the blockchain node support OCAP (Open Chain Access Protocol), e.g. ArcBlock's Main or Beta, or a test node you run by yourself FOREIGN_CHAIN_HOST: The API provider for the foreign blockchain node. e.g. Ethereum or any Ethereum compatible blockchain's API server, e.g. Infura. FOREIGN_CHAIN_ID: The Chain ID of the foreign blockchain. (See below for Chain ID)

ArcBlock's Main chain:

Block Explorer | ArcBlock

ArcBlock's Test chain:

Block Explorer | ArcBlock

You can easily setup a test OCAP chain with our blocklets:

FS Chain Manager

You can find different Ethereum and compatible Chain ID here:

Chainlist

To help you better, could you please clarify your intentions? Are you looking to set up an experimental environment for testing purposes or are you interested in becoming a validator node for the existing ArcBlock-Ethereum bridge? We are here to assist you further based on your specific requirements.

We highly recommend that you set up a test environment first before making a serious commitment to becoming a production validator. We advise against experimenting with the setup of the production ArcBlock and Ethereum chain without ensuring that everything is properly covered. This is because there is a risk of potential loss of your digital assets.T o avoid any potential problems or losses, we strongly recommend thoroughly understanding and testing the setup process before proceeding with any experimentation. It is always best to take necessary precautions to safeguard your assets.

We apologize for any inconvenience you experienced while setting up the server and joining the bridge. We understand how frustrating it can be to encounter difficulties during this process. As a solution, we have decided to create video tutorials to demonstrate the entire setup process. We will also improve our documentation to ensure that each step is clear and easy to follow. Please bear with us as we work on creating these tutorials and enhancing our documentation. We will notify you once they are available.

Thank you for showing interest in becoming a validator!

However, before you proceed, it is important to familiarize yourself with the various concepts and responsibilities that come with being a validator. Being a validator carries some risks, such as the potential loss of digital assets due to attacks or slashing. It is crucial to fully understand and evaluate these risks before taking on the role.

Risk of becoming an attack target

The validator node includes a "hot-wallet" (the private keys are on the server) with digital assets because it is essential for the validation and signing of transactions. Occasionally, the node may need to send transactions and your wallet must have sufficient assets for the associated gas fee.

Being a validator node means that it will be publicly known, which unfortunately increases the risk of becoming a target for potential attacks. It is crucial for you to take full responsibility for securing your server to prevent any such attacks from occurring.

We highly advise against setting up the node on a self-hosting home server or devices such as Raspberry Pi. Sharing the server with other services, like a website, is also NOT recommended. To ensure optimal performance and security, we recommend using a dedicated cloud server like AWS, Azure, or Google Cloud, or you can use our dedicated Blocklet Server option, the serverless Blocklet will NOT suitable for this scenario.

It is indeed a complex task, but we are more than happy to provide you with some recommendations later.

Risk of slashing

As a validator node, it is important for you to stake a certain amount of tokens. These staked tokens serve as a guarantee for each transaction that your validator signs. In the event that the system determines that the transactions signed from your node are invalid, there is a risk of you losing the staked tokens. The amount of tokens you may lose depends on the extent of the damage caused by the invalid transaction.

There are several reasons why your node may sign invalid transactions. For example, your system could be attacked and the software altered, or your blockchain node could be out of sync or compromised due to an attack or misconfiguration.

The chance of an invalid transaction being passed is very low, as there are different validators cross-verified each time and gatekeepers automatically re-verify. However, even without any damages occurring, any invalid signature will result in a reduction of your staked tokens. If your staked tokens are completely slashed or if your node continuously signs invalid transactions, your node will be removed from the bridge and will not be able to rejoin.

We recommend that you start by setting up a bridge with our test net and Ethereum test net. This will allow you to gain experience and become familiar with the process. Once you feel confident in what you are doing, you can then move on to using the production bridge. Our engineering team will be available to assist you throughout this process.

Thanks again, so with the advice of not using the home built one, I'd like to set up the dedicated blocklet server I had purchased through the store (server + app).

Only main questions so far are:

Will I be able to change the node from test to production after familiarizing with it, or would it require another server/app?

Do I stake once or can I add more later?

I'm sure I'll have other questions later.

Ok great. I'd love to start getting the test node together, which again leads to needing these settings configured. After it's been established that way for a few days or a week and I've looked at everything which is past the configuration, I'd like to switch it to production.

Ideally, familiarized and production ready within a couple weeks from now is what I'm looking to accomplish.

Sounds great, thanks so much. Is that something that would be posted here, or more generally for everyone like on a youtube video/dedicated forum post?

Edit: Sorry just went through the replies again and you had stated video.

Thanks again.

A few other thoughts that might be better explained in the video as well.

I've noticed on the explorer that there is one active bridge and two that appear offline. All three being of the same type. Each with their own node count. My questions regarding this specific are:

A. Aside from joining the existing bridge, is making additional bridges also applicable?

B. Is it more beneficial to the network to have more of the same type of bridge for possible redundancy-sake?

C. Is there a node per bridge limit?

We possess the necessary technical capabilities to seamlessly connect tokens between ArcBlock and Ethereum compatible blockchains.

Please be advised that ArcBridge operates as a fully decentralized solution, allowing individuals to establish bridge(s) for various digital assets without any restrictions.

z1croUysBVjGHD7KtHqZyhxKrCrSB2Z1Daa I am working on a tutorial about joining our test chain bridge, please stay tuned, and a few requirements to proceeding:

Found where to add the testnets for visibility within DID Wallet, requested faucet transaction and have some test eth.

For joining a node to the testnet, can this be done with an already purchased node from the blocklet store or is a new node to be made with test tokens?

The test bridge you linked, is that link what would be entered for the

OCAP chain host: 'https://beta.abtnetwork.io/explorer/bridges/z3KzTUDUepQNKqcWVfRXqtqWf86tgqQjc9uge'?

Foreign chain host: 'https://ethereum-goerli.publicnode.com' or 'https://goerli.infura.io/v3/YOUR-API-KEY' for infura API?

Foreign chain id: '5' or '0x5'?

z1VV21NqNWkiadznN32ALkos5dQqQwnCMty is working on it. Apparently he is more experienced on creating software than create video demos. 😂

We are currently in a quarter review period, which means everyone's schedule is completely booked. Please bear with us for a few days so that we can have the video and tutorials prepared.

It seems you are adding ArcBridge Node as a component to your existing app?

The ArcBridge Node blocklet should be launched in a standalone app because it requires an Ethereum-compatible address (which is required for each node to send transactions to Ethereum blockchain).