ACES Completes Integration of ARK Channels for Two-way Transfers for Easy ICOs When Paired With ARK Deployer (Push-Button-Blockchains).

Less then two months ago we commented on how ACES could be levered to support ARK ICOs for Push-Button-Blockchains. Today, we’ve launched the protocol to support this. We’re calling it ARKA-ARKB channel services. Combining this service with the already released ARK Deployer from the ARK team will allow you to connect your independent ARK blockchain to the ARK main chain (or any other ARK network) to exchange between the tokens. For another guide on ARK Deploy see this guide on using Azure for ARK Deployer.

What’s the difference between ARK-A and ARK-B?

These are simply ARK network variables, and they can be any ARK-based chain. For example, the default in our repository sets ARKA to the ARK mainnet and ARKB to the ARK devnet. Simply adding your independent blockchain’s network config to the network config directory and then replacing the arkbNetworkConfigPath with the correct network config location will replace ARKB with your new network, and your new token will be connected and for sale when you boot the ACES application.

Why is this awesome?

Starting an ICO or any other tokenized project and monetizing it through any connected blockchains is super easy now. We are approaching an era where launching an independent blockchain with connections to other blockchain services (like transfer and contract) can be done from start to finish in less than an hour. We’ve already have several interested parties in working with ACES to support their project in some way.

1. You can have your project tokens for sale in less than a few hours of work, as a complete beginner.
2. With a robust ACES marketplace, you could be connected to all sorts of coins and receive funding in any coin that has available capacity only by connecting your service to ARK through this newly released service. This is because ACES channel services can be linked together. A diagram of the flow of a linked-channel-service is shown below. Just replace ETH with ARKB, and you can see how an ARK ICO can accept Bitcoin to sell their new tokens.

3. The ARK ICO concept can succeed without any other ACES service providers, because the project hosts become an ACES service provider with large capacity of their network available for transfer. This means even if there isn’t enough capacity on the ACES platform for external coins like Bitcoin, ARK can be very successful for launching ICOs and independent blockchains.

4. Brand new chains that do not have, and may never have, listing on exchanges will be available through ARK using the chain’s available and liquid ACES service. This makes ARK competitive with easy ICO options like Ethereums ERC20 tokens, but the ARK-based tokens would reside on their own independent blockchain and not produce any bloat for non-users.

5. As a user/investor, you will not need to ever worry about registering ERC20 tokens for eventual transfer to a mainnet, as this can be easily facilitated with custom ACES services and ARK Push-Button-Blockchains, which as mentioned already, can be set up by projects before their first coffee break of the day.

Next steps

We will now return to enhancing the ACES marketplace, with security audits, adding searchable services, easy deployments, and more. The next month will focus primarily on security audits and UI improvements for what we already have released, and then afterwards we will focus on admin tools for easy deployments and service monitoring.

Join the team!

We’re on the look out for more contributors. We welcome any one to contribute to the project. Here are some contributions we’d love to receive some focus:

1. More coin services. Linking external blockchains to ARK and using our existing repos as guides. Our top desired connection is Monero to ARK. If you want to take this one, reach out! You will need to know Java and Spring-boot to work closely with our existing repos, but this is not a requirement if you want to implement in other ways.
2. Marketplace feature build out. We use Angular for the front-end. If you are interested in learning more about Angular or contributing to an Angular project, we’d love help in this area! You do not need to be expert, and all code will be reviewed by the team.
3. Tutorials and guides. Do you not have much technology experience and just want to learn how to use and teach how to launch ACES services and chains? We’d love for some people to put together tutorial blogs, videos, etc, that show how to launch an ARK-based chain alongside an ACES service.
4. Service providers. It would be great to have some people hosting ACES services with some non-zero mainnet capacity. This is a legitimate business opportunity, and you would be able to be a profitable business by using the integrated ACES service fees.