If there was ever a protocol of blockchains that would be anything like Komodo or Verus, it is probably Avalanche at the current time. It is a multi-chain project consisting of a main X-Chain for transactions & creation of tokens as well as the management of the protocol. It is not a blockchain, but a DAG - a different data structure, similar to other behemoths in the crypto space, like Cardano, Nano & IOTA.

avax governance and tokenization dag chain
AVAX X-chain (DAG) for token creation, transactions & governance.

Then there is the C-Chain for smart contracts. It is a copy of the EVM allowing developers to move their projects from Ethereum.

AVAX c-Chain for EVM smart contracts & co-ordination with snowman protocol
AVAX c-Chain for EVM smart contracts and snowman protocol for co-ordination

P-Chain is the third chain in the AVAX network. It is the "platform chain" for enabling organizations to create "subnets". A subnet is a new blockchain that has it's own consensus mechanism, whether it's PoW or PoS. Subnets can also have their own VMs (as in EVM), to run their own set of smart contracts.

AVAX p-Chain for platform subnets
AVAX p-Chain for blockchain subnets

AVAX Subnets

AVAX subnets can be permissionless or permissioned. Sensitive organization data can therefore be shared on the permissioned chain, e.g. payroll or HR info, and the general public data on the permissionless subnets.

AVAX subnets are configurable independently like Komodo Smart Chains.

The information on this page was summarized from the video of AVAX by whiteboard crypto group.

AVAX - what is the avalanche network video on youtube by whiteboard crypto

The transcript of the "what is avax" video is available here on the komodefi github transcripts repo in case the video disappears from youtube and the content is needed for cross reference in the future.

An explorer is a display of the blockchain data structures in somewhat friendly human readable format. The high level cryptography technology employed by Komodo smartchains does require some dissecting to understand what is going on.

This post is the first part of how to read the explorer, and how to understand the technical underpinnings of NFT creation on Tokel's blockchain.

This morning I was clearing out a usb drive and found these two images from cakeshop era awesomeness. What I like about it is the food-ification of it. Cakeshop may become relevant again - cakes are pretty universally like, so it's no wonder to me that a popular crypto is called Pancake Swap with a ticker CAKE.

It's a nice reminder of the work I had done with Komodo & how I could playfully productize them.

Looking at it again during draft of this post, I'll probably look to re-using this format for my chain game project. Following is the roadmap for my notary node candidature back when...

I still think it's cool. :ridgey_didge_hang_loose_emoji:

The full stack atomic swap tutorial only gets better! Here you will have your own web app for exploring the atomicDEX p2p orderbook market. Market pairs not available on centralized exchanges exist on this p2p trading network. Community exotics such as RVN/DGB directly being listed with DEX prices. No intermediary currency (like BTC/ETH/USDT/BUSB/etc.) and certainly no intermediary party. Your keys your coins!

In part 1 of the tutorial, setting up the telegram bot which relayed our wallet passphrase was helpful. If you did not do it, the passphrase is available in plain text in the root of the container at /passphrase.txt - more advanced docker options to share a file on the host to the container are also available which will be covered at the end.

Viewing Market Orders From A Web App

When I wrote part 1, it was designed for the types of automated testing that can be done without a GUI. Fire up 50 docker instances, with some accompanying scripts. This is ideally what the Komodo dev team would want to use for load testing the network from several data centres around the globe. This image has the web GUI enabled. You need docker installed to play along!

Step 1 - Pulling Updated Tutorial Image

docker pull coingateways/atomicdexorderbook:0.8.4

Step 2 - Start AtomicDEX API, Middleware & Web Front End

For this I'm going to only leave instructions for a telegram bot. If you are not going to use a telegram bot, just omit the (-e) environment variables, it will still work without a problem. Please don't send large amounts of funds without properly having the passphrase backed up. It is auto-generated randomly.

If you have run through tutorial 1, you will want to stop the running container (if you haven't) and remove it. Make sure you have the passphrase saved if you did adventurous things on your own accord (like sending real value to the address). You can recover the funds using the Verus Desktop Wallet.

docker run -i -t -p -p -e MMBOT_URL="http://localhost:7780"  -e BOT_TOKEN="XXXXXXXXX" -e BOT_CHATID="XXXXX" -e BOT_USERNAME="XXX" -e ME_PUBLIC="false" -e ME_PRIVATE="true" --name orderbook coingateways/atomicdexorderbook:0.8.4

We have added the web port to open communications for the browser to connect to on port 8001.

We have also added two variables to pass in ME_PUBLIC & ME_PRIVATE. They are simple true/false values. Best results are reached when they are opposite of each other. ME_PRIVATE enables more dangerous operations from a financial risk point of view e.g. making trade orders broadcast on the network with a funded account.

Step 3 - Browse To Application

Wait! The front end app needs to be compiled - nothing from your end needs to be done, but there will be about a 10 second start up whilst the javascript is optimized. The application is written in VueJS with Material Design baked in from Google. The project VuetifyJS is used for this seamless developer experience.

Browse to http://localhost:8001

The browser will redirect to the dashboard and you will likely see 60+ wallets showing zero balance.

So easy!

Step 4 - Browse P2P Crypto Markets

Currently, atomicDEX is in beta, so there are not many users or orders or volume. So we'll have a look at only 3 markets - firstly an exotic community market - KMD / VRSC. Verus is the home of the desktop wallet & Komodo is the original multi-chain blockchain project. Verus is a fork of Komodo, the address format is the same.

Scroll down to the bottom for VRSC
A button to go to the selected button is also half way down the screen - yes some UX / CSS adjustments to make...
The market data!

Step 5 - Update Coin Gecko Fiat Price

For the first integration with the centralized world, an example of the price feed being updated. This is a cyclical update on the middleware server. It fetches an update approximately every minute. From the above screenshot, to update to the latest fetched data, simply click on the banner!

KMD goes up a tiny bit like the good oscillating currency that it is

You will note the "INVERT" button. This will flip the market around. All orders are sellers, they are just selling at the opposite ends of the market! This is the underlying logic in the atomicDEX marketmaker software.

Step 6 - Invert Market

Not many VRSC sellers! This will increase, especially as I've deployed a coin specific interface for the community at https://vrsc.orderbook.live

What's Next

What's next for me is to do some live streaming using this interface. Creating orders with test coins and the community. Automation is a big feature of this orderbook app. It is designed for web communities to watch orders countdown in a reverse auction style contest.

Re-Using Passphrase

Instead of auto-generating a new passphrase on container start up, a plain text file can be mounted from the host to the container. The container has been built in such a way to auto detect the existence of a pre-shared passphrase!

Using the python electrum wallet sources, Komodo developer pbca26 was able to demonstrate to discord user zrtx goal on how to sign a raw transaction. The conversation included zCash protocol expert dukeleto, atomicDEX API & marketmaker developer artem.pikulin.

Electrum wallet is fully capable of signing correct kmd/kmd smartchain transactions and worked so far w/o any major issues. 99% of it's core code is inherited from zcash electrum wallet version. Here is the resulting gist (embedded below) from pbca26 to achieve the goal below:

komodo-cli createrawtransaction -> unsigned tx hash -> transaction lib of electrum-komodo -> signed tx hash

Most multicoin lite wallets can be used to enter a seed phrase (list of words) or a private key for a coin and be used for different coins. Sometimes, a new wallet will come out and offer features that you may want to try out. The wallet supports a private key for one type of coin for example, like bitcoin.

In the discord mining channel, it was asked:

is there a tool to get out of a komodo private key a BTC private key?

Here is the question.

Komodo team member Poly suggested to extract the key from a lite wallet, like what Verus Desktop & Chameleon Pay can do. Proof-of-Stake expert and LABS maintainer Alright from the Komodo team offered a python script for doing the task. It is included in the following gist below.

The requirements are to install base58 python package with pip install base58. Duke Leto from the HUSH private communications project and ZEC expert offered another private key conversion script with a useful tidbit of information:

ZEC/HUSH/etc have 2 prefix bytes, BTC/KMD only have 1

User CHMEX from the dexstats site has an online address converter to verify outputs of scripts, but it is for public addresses only - aka do not enter in private key or WIFs!

Experience Crypto
© 2021 komodefi.com. Powered by Komodefi