komodoplatform / developer-docs

Archived

Latest version at https://github.com/KomodoPlatform/komodo-docs-mdx

Komodo documentation uses Vuepress.

Setup:

Prerequisites:

• nodejs
• yarn

---

Tip:

If you prefer using Docker, installation of nodejs and yarn is not required. See below for Docker instructions.

• Fork the repository
• Clone the repository
• cd into the directory cd developer-docs/

Install packages & dependencies

yarn install

Start Editing

yarn docs:dev

HTML output is displayed at http://localhost:8080

Edit the markdown files in the directory docs and save the file.

If the changes are not reflected at http://localhost:8080 right away, refresh the page.

Exit the dev mode by using CTRL + C in the same terminal yarn docs:dev has been run.

Issuing the build command while the above dev command is active might cause the build to fail with errors.

Build

yarn docs:build

The html files are available in developer-docs/docs/.vuepress/dist/

Deploy

To deploy to gh-pages at https://<USERNAME>.github.io/developer-docs

./deploy.sh

The above script uses your git <USERNAME> from the global git configuration of your system.

Using Docker:

You can use Docker to reliably produce a developer environment that won't conflict with any of your existing projects.

Prerequisites: Install Docker and Docker Compose on your system

• Clone the repository

• cd into the directory cd developer-docs/

• To start developing, simply issue docker-compose up in a terminal to launch the container

• Then do docker exec -ti komodo_docs /bin/sh in another terminal to access a terminal inside the container. Now simply follow the instructions detailed in the above Start Editing and Build sections.

• To exit from the terminal from the container use the exit command.

• Use CTRL + C in the terminal docker-compose up has been done to stop the container.

• To deploy using docker, use the command ./deploy_docker.sh. This script deploys to your own fork; the webpages are now located at the following address: https://<USERNAME>.github.io/developer-docs

• When used for the first time, Docker might take some time to download the required data and build an image. Subsequent usage will be faster.

developer-docs's Issues

Windows-incompatibe file names?

I've a problem checking out the repository on Windows:

error: unable to create file docs/.vuepress/public/KMD_Brand_Assets/Horizontal/Black/Icon?: Invalid argument
error: unable to create file docs/.vuepress/public/KMD_Brand_Assets/Horizontal/Dark/Icon?: Invalid argument

Looks like a carriage return (%0D) sneaked into the file names (https://github.com/KomodoPlatform/developer-docs/blob/master/docs/.vuepress/public/KMD_Brand_Assets/Horizontal/Black/Icon%0D).

I suspect it's a bug, and it prevents me and possibly other developers from working normally with the docs.

Missing curl commands

z_listunspent and z_listreceivedbyaddress

Add info that RPC password can't contain following chars: "<", ">", "&"

Document paid_from_trading_volume field of the trade_preimage fees response.

It indicates whether the fee will be deducted from the trading volume during the swap. For example, it is deducted from the payment amount to spend/refund UTXO HTLC (paid_from_trading_volume: true), but ETH users require ETH on their balance upfront for the same actions (paid_from_trading_volume: false).

Dead link

At the tutorial page:
https://developers.komodoplatform.com/basic-docs/antara/antara-tutorials/beginner-series-part-1.html

clicking at the end on the "Link to the next tutorial in this series" takes to:
https://developers.komodoplatform.com/basic-docs/antara/antara-tutorials/overview-of-development-on-komodo-part-2.html

that is a dead link btw, I suppose it should instead take to:
https://developers.komodoplatform.com/basic-docs/antara/antara-tutorials/beginner-series-part-2.html

Messy link in docs/README.md

On dev-theme branch I got rid of the landing page. Saves a click and gets newcomers into docs faster. This came at request of management.

However, this meant that we needed a default page. I was not able to find a way to make plain https://developers.komodoplatform.com/ forward directly to our introduction, https://developers.komodoplatform.com/basic-docs/start-here/introduction.html.

I found a temporary workaround.

The default for the / directory is the README.md file in the docs/ directory.

I moved all content from docs/basic-docs/introduction.md to the README.md file, for this reason.

This works fine, except that we need a call to action at the bottom, or a link leading onwards, since the README.md files do not natively have the normal links at the bottom to the next page.

I inserted a CTA button, and set it as an html a link, so that I could style it. (Wouldn't want to style markdown elements.)

The issue with this is that the href value of the a link does not naturally become a part of the single-page application framework. When you click it, the whole browser blinks, and there's a delay.

We can just remove the button, I suppose, but before we do that, I'm putting an issue here to see if anyone has any other ideas.

Add t --> t to z_sendmany

yes, but check the first example 😛
https://developers.komodoplatform.com/basic-docs/komodo-api/wallet.html#examples-53

@siddhartha-crypto Please add t --> t tx is also available using z_sendmany ^^

Add atomicdex desktop guides

• build instructions for all OS
• add custom coins
• customising theme
• simple ops (swap, transaction etc)

Gateways Bind section is missing from current Gateways CC docs

Mihailo pointed this out:

https://docs.komodoplatform.com/cc/contracts/gateways/scenarios/tutorial.html#bind-the-tokens-and-oracle-as-a-gateway

corrections required to `-ac-script`

8:10 AM] gcharang: Alright here: https://developers.komodoplatform.com/basic-docs/installations/asset-chain-parameters.html#ac-script
it says This parameter requires that ac_founders also be active. but rogue chain seems to work without having ac_founders in it?(edited)
Custom Asset Chain Parameters | Komodo Documentation
Documentation for developers building on Komodo
[8:12 AM] Alright: ac_perc ac_script combo will result in a founder's reward paid to the script hash specified in ac_script
[8:12 AM] Alright: so uhh
[8:12 AM] Alright: it requires ac_perc
[8:12 AM] Alright: although it has a default value of "35%" if ac_perc is not set
NEW MESSAGES
[8:13 AM] Alright: I had the misconception that ac_script was not compatible with ac_perc tax model, but it is
[8:13 AM] Alright: that's likely how that got there

Document MM2.db database

-gen -genproclimit=$(nproc) is not recommended

Alright informed me that various kinds of bugs can happen when using these params, as recommended by:

https://docs.komodoplatform.com/basic-docs/installations/creating-asset-chains.html#creating-a-new-asset-chain

It's much safer to recommend people to use setgenerate RPC after the daemon has started.

if you try to bootstrap a node by running ./komodod -ac_name=NAME -addnode=<IP> -gen -genproclimit=n
it might mine it's own block 1
and if you aren't bootstrapping
it might fork at the point where you were synced up until

yarn docs:dev will fail if until algolia-key.sh is run.

algolia-key.sh creates ./docs/.vuepress/algolia-secret.js file, I get Error: Cannot find module './algolia-secret.js' since it's required by config.js. This part is not mentioned in Readme.
@gcharang could you please advice on this since it seems that you added the algolia in c08e8a4

dice.html not showing up on the Antara Modules list

New RPC available in the Komodo daemon

Need to add them to the api docs

Fix `electrum` rpc request example for QTUM

Reopening issue: KomodoPlatform/Documentation#159 here

https://developers.komodoplatform.com/basic-docs/atomicdex-api-legacy/coin_activation.html#electrum

Looks like 0xba8b71f3544b93e2f681f996da519a98ace0107a swap contract address is actually a testnet address, while QTUM coin is the mainnet asset.

curl --url "http://127.0.0.1:7783" --data "{
	\"coin\": \"QTUM\",
	\"method\": \"electrum\",
	\"servers\": [
		{\"url\": \"electrum1.cipig.net:10050\"},
		{\"url\": \"electrum2.cipig.net:10050\"},
		{\"url\": \"electrum3.cipig.net:10050\"}
	],
	\"swap_contract_address\":\"0xba8b71f3544b93e2f681f996da519a98ace0107a\",
	\"userpass\": \"$userpass\"
}"

cc: @yurii-khi

Document unban_pubkeys RPC.

https://github.com/KomodoPlatform/atomicDEX-API/blob/dbacb816c3ece306628ca7517ef57c29036e0b1e/mm2src/rpc/dispatcher/dispatcher_legacy.rs#L131

Add Postman collection for all API methods.

As discussed in the call and Discord, this repo seems the best place for such a collection.

Add CTA for third-party service providers

even the documentation refers to additional costs that are handled through service providers: https://developers.komodoplatform.com/basic-docs/installations/creating-asset-chains.html#secure-this-asset-chain-with-delayed-proof-of-work

Ssiddhartha_crypto maybe we could add more info about the pricing at the very end, so it becomes even more black&white. Something like "for full pricing information please get in touch with a Komodo service provider" and maybe even something like "Komodo Security Service uses an annual subscription based pricing model to cover infrastructure and maintenance costs. In addition external blockchains are required to go through a third party security audit."

Probably a lot of these projects rely on the documentation to get all the info rather than the website itself
4+A
like a CTA type of thing, so it cannot be missed

User Request: Examples as drop down menus

Request to make the examples an unexpanded drop down, to make reading and scanning the docs faster.

Tables with arguments and responses, remove "structure

Convert CD from travis-ci to gh-actions

context: https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works

Negative confirmations of tx and KMD didn't deliver

Hello. I have an issue. I sent 1000 KMD to my Ledger wallet address and seems my tx is stuck.
by listtransactions got such result:

{ "account": "", "address": "RMn6xtRV1zutpKeiT5jsSFcRKCCZXcpi1s", "category": "send", "amount": -1000.00000000, "vout": 1, "fee": 4.27883438, "rawconfirmations": -1, "confirmations": -1, "txid": "6227a0eac12c1fc2608b1abded6729e8af869d63538441223ce3df036437d209", "walletconflicts": [ ], "time": 1656625651, "timereceived": 1656625651, "vjoinsplit": [ ], "size": 244 }

Any KMD explorer don't see this TX and KMD on my Ledger wallet is zero.
Also KMD didn't return back to my sending wallet balance.

It's first time when I'm facing such situation.
Can anybody help me with it?
How to return KMD back to my balance?
Or resend this tx somehow?

Better landing page

Re: Removal of landing page in the dev-theme branch
My suggestion is to keep the landing page and add various CTA to it, like: Getstarted as it existed previously, create assetchain, explore cc modules
I remember before we removed the extra text in the previous landing page, there was a readymade format for that.

Now, even though we have removed the need for one click, but still the other starting points are many clicks away, even if users know where to navigate.

But if all these CTA are in the previous landing page, then the users can choose where they want to go

zcash params required for using komodod and komodo-cli binaries

[6:41 PM] krtk6160: I tried running komodod & from terminal, but it fails with an error related to Zcash
Error: Cannot find the Zcash network parameters in the following directory:
/home//.zcash-params
[6:42 PM] krtk6160: Do I need to install Zcash before I'll be able to run komodod?
[6:43 PM] CHMEX: run
./zcutil/fetch-params.sh
That will download the params files ( a few gigs of data )
[6:48 PM] krtk6160: @CHMEX But there's no zcutil directory. The docs say I just need 2 files, komodod and komodo-cli
[6:51 PM] CHMEX: hmm ok which docs?
you need it to run a local node
github.com/jl777/komodo/blob/master/zcutil/fetch-params.sh

Maybe download above chmod +x fetch-params.sh and run it
[6:59 PM] krtk6160: @CHMEX https://developers.komodoplatform.com/basic-docs/installations/basic-instructions.html#installing-basic-komodo-software These docs say no installation is required, just those two files.
Anyway, I'll try to download the script and run it.
Basic Instructions | Komodo Documentation
Documentation for developers building on Komodo
[7:00 PM] SHossain: @siddhartha-crypto ^^ please add that devs/users need to download zcash params before they can use komodod if they prefer to download pre-built binaries.

Feature request: Define path to MM2.json as runtime param

It would be handy to be able to reference an MM2.json file located in a specific folder, or by a different name to allow quick changing of the wallet seed used at launch.

E.g.

./mm2 conf=/home/user/folder/mm2_primary.json
./mm2 conf=/home/user/folder/mm2_secondary.json

Long dev docs title in nav bar on mobile needs css override for default theme

@media (max-width: 419px){ 

//nav bar, default is 3.6rem
  .navbar {
    height: 5.0rem;
  }

//side bar top heading loses spacing, default is 0.5rem on first co-ordinate
  .sidebar .nav-links .nav-item {
    padding: 1.5rem 0 0.5rem 1.5rem;
  }

// top heading of main page loses spacing, default is -1.5rem
  .content:not(.custom) > h1:first-child, .content:not(.custom) > h2:first-child, .content:not(.custom) > h3:first-child, .content:not(.custom) > h4:first-child, .content:not(.custom) > h5:first-child, .content:not(.custom) > h6:first-child {
margin-top: -0.5rem;
  }
}

Link key features of kmd that have blog posts

Eg MoMoM has a blog post
https://komodoplatform.com/komodo-platforms-new-scalability-tech/

dPoW now has a lot of info on the subject

Sapling soon

docker yarn docs:dev requires yarn add -D vuepress

For some reason, the docker image required me to yarn add -D vuepress to get it to work.

Size limits of arguments across all rpc calls

Plz don't take any action on this at this stage.

There is a size limit of token names and their description. Names can be 8 characters and description 4096 chars and they are limits placed at RPC call, not on the data structure (char[8], char[4096]).

https://github.com/jl777/komodo/blob/6ef61a1aa9de6902245f8a030e6fc5d09c15de3c/src/wallet/rpcwallet.cpp#L7291 checks if name.size() is 8 or under.

https://github.com/jl777/komodo/blob/6ef61a1aa9de6902245f8a030e6fc5d09c15de3c/src/wallet/rpcwallet.cpp#L7304 checks description.size() 4096 or under.

Have to find out from the developers of the CCs, each CC at a time with a questionnaire so it's easy to gather the data, where it is in the code, etc.

2 main reasons are:

• devs calling these rpc commands will suffer rage when they find out there are (currently) undocumented limits
• devs making CCs will want to know how to add limits to their CC arguments

Add "Improve this page" link to the bottom of every page

See strapi documentation for example:

https://strapi.io/documentation/3.x.x/getting-started/introduction.html#strapi-documentation

component with tabs for displaying linux and windows commands

ref: https://github.com/KomodoPlatform/developer-docs/pull/293/files#r743135578

Add rpc_password policy and allow_weak_password field to API docs.

We're currently applying stricter rules to the rpc_password set by users, which might be turned off using the allow_weak_password flag. Related PR in the API (not merged yet): https://github.com/KomodoPlatform/atomicDEX-API/pull/1144/files

Create guide on asset adding into desktop GUI

@smk762 when you'll have a chance please make a guide/instruction on how to add assets into desktop GUI: coins repo part + files which needs to be changed, logo and etc

Document new RPC 2.0 methods for BCH and SLP protocols activation and tx history.

Creating a separate issue here because it's related to a few in the API repo:
KomodoPlatform/komodo-defi-framework#1006
KomodoPlatform/komodo-defi-framework#701

Please mark them as unstable/in development because we can change them for HD wallets support.

enable_bch_with_tokens

Request (Electrum mode)

curl --url "http://127.0.0.1:7783" --data '{
  "userpass":"'$userpass'",
  "method":"enable_bch_with_tokens",
  "mmrpc":"2.0",
  "params":{
    "ticker":"tBCH",
    "allow_slp_unsafe_conf":false,
    "bchd_urls":[
      "https://bchd-testnet.greyh.at:18335"
    ],
    "mode":{
      "rpc":"Electrum",
      "rpc_data":{
        "servers":[
          {
            "url":"electroncash.de:50003"
          },
          {
            "url":"tbch.loping.net:60001"
          },
          {
            "url":"blackie.c3-soft.com:60001"
          },
          {
            "url":"bch0.kister.net:51001"
          },
          {
            "url":"testnet.imaginary.cash:50001"
          }
        ]
      }
    },
    "tx_history":true,
    "slp_tokens_requests":[
      {
        "ticker":"USDF",
        "required_confirmations": 4
      }
    ],
    "required_confirmations":5,
    "requires_notarization":false,
    "address_format":{
      "format":"cashaddress",
      "network":"bchtest"
    },
    "utxo_merge_params":{
      "merge_at":50,
      "check_every":10,
      "max_merge_at_once":25
    }
  }
}'

Where:

1. ticker - string, mandatory. Ticker of the platform BCH protocol coin.
2. allow_slp_unsafe_conf - bool, optional. If "true", allows bchd_urls to be empty. Please mark that it is highly unsafe to do so as it may lead to invalid SLP transactions generation and following tokens burn. Defaults to "false".
3. bchd_urls - an array of strings, mandatory. URLs of BCHD gRPC API servers that are used for SLP tokens transactions validation. It's recommended to add as many servers as possible. The URLs list can be found at https://bchd.fountainhead.cash/
4. mode - Utxo RPC mode, mandatory. Value for native: { "rpc":"Native" }
5. tx_history - bool, optional. Whether to enable tx history - if "true", spawns a background loop to store the local cache of address(es) transactions. Defaults to "false".
6. slp_tokens_requests - array of SLP activation requests, mandatory. SLP activation requests contain mandatory ticker and optional required_confirmations fields. If required_confirmations is not set for a token, then MM2 will use the confirmations setting from its coins config or platform coin.
7. required_confirmations - number (unsigned integer), optional. The value from the coins file will be used if not set.
8. requires_notarization - bool, optional. Has no effect on BCH. Defaults to "false".
9. address_format - address format, optional. Overwrites the address format from coins file, if set. Value to use legacy/standard address format: { "format":"standard" }.
10. utxo_merge_params - utxo merge params, optional. If set spawns a background loop that checks the number of UTXOs every check_every seconds and merges max_merge_at_once to one if the total exceeds merge_at. Useful for active traders as every swap leads to a new UTXO to occur on the address.

Response

{
  "mmrpc":"2.0",
  "result":{
    "current_block":1480481,
    "bch_addresses_infos":{
      "bchtest:qzx0llpyp8gxxsmad25twksqnwd62xm3lsnnczzt66":{
        "derivation_method":{
          "type":"Iguana"
        },
        "pubkey":"036879df230663db4cd083c8eeb0f293f46abc460ad3c299b0089b72e6d472202c",
        "balances":{
          "spendable":"0.11398301",
          "unspendable":"0.00001"
        }
      }
    },
    "slp_addresses_infos":{
      "slptest:qzx0llpyp8gxxsmad25twksqnwd62xm3lsg8lecug8":{
        "derivation_method":{
          "type":"Iguana"
        },
        "pubkey":"036879df230663db4cd083c8eeb0f293f46abc460ad3c299b0089b72e6d472202c",
        "balances":{
          "USDF":{
            "spendable":"5.2974",
            "unspendable":"0"
          }
        }
      }
    }
  },
  "id":null
}

Errors (stack traces may change)

{
  "mmrpc":"2.0",
  "error":"tBCH",
  "error_path":"platform_coin_with_tokens",
  "error_trace":"platform_coin_with_tokens:281]",
  "error_type":"PlatformIsAlreadyActivated",
  "error_data":"tBCH",
  "id":null
}

{
  "mmrpc":"2.0",
  "error":"Platform tBCH-wrong config is not found",
  "error_path":"platform_coin_with_tokens.prelude",
  "error_trace":"platform_coin_with_tokens:286] prelude:56]",
  "error_type":"PlatformConfigIsNotFound",
  "error_data":"tBCH-wrong",
  "id":null
}

{
  "mmrpc":"2.0",
  "error":"Unexpected platform protocol UTXO for BTC",
  "error_path":"platform_coin_with_tokens.prelude.bch_with_tokens_activation",
  "error_trace":"platform_coin_with_tokens:286] prelude:67] bch_with_tokens_activation:127]",
  "error_type":"UnexpectedPlatformProtocol",
  "error_data":{
    "ticker":"BTC",
    "protocol":{
      "type":"UTXO"
    }
  },
  "id":null
}

{
  "mmrpc":"2.0",
  "error":"Unexpected token protocol ERC20 { platform: \"ETH\", contract_address: \"0xdAC17F958D2ee523a2206206994597C13D831ec7\" } for USDT-ERC20",
  "error_path":"platform_coin_with_tokens.prelude.slp_token_activation",
  "error_trace":"platform_coin_with_tokens:301] platform_coin_with_tokens:114] prelude:67] slp_token_activation:47]",
  "error_type":"UnexpectedTokenProtocol",
  "error_data":{
    "ticker":"USDT-ERC20",
    "protocol":{
      "type":"ERC20",
      "protocol_data":{
        "platform":"ETH",
        "contract_address":"0xdAC17F958D2ee523a2206206994597C13D831ec7"
      }
    }
  },
  "id":null
}

{
  "mmrpc":"2.0",
  "error":"Error Using empty bchd_urls is unsafe for SLP users! on platform coin tBCH creation",
  "error_path":"platform_coin_with_tokens.bch_with_tokens_activation",
  "error_trace":"platform_coin_with_tokens:290] bch_with_tokens_activation:212]",
  "error_type":"PlatformCoinCreationError",
  "error_data":{
    "ticker":"tBCH",
    "error":"Using empty bchd_urls is unsafe for SLP users!"
  },
  "id":null
}

{
  "mmrpc":"2.0",
  "error":"Error bch:633] utxo:1704] utxo:995] Error parsing the native wallet configuration '/home/user/.Bitcoin Cash Testnet/Bitcoin Cash Testnet.conf': No such file or directory (os error 2) on platform coin tBCH creation",
  "error_path":"platform_coin_with_tokens.bch_with_tokens_activation",
  "error_trace":"platform_coin_with_tokens:290] bch_with_tokens_activation:212]",
  "error_type":"PlatformCoinCreationError",
  "error_data":{
    "ticker":"tBCH",
    "error":"bch:633] utxo:1704] utxo:995] Error parsing the native wallet configuration '/home/user/.Bitcoin Cash Testnet/Bitcoin Cash Testnet.conf': No such file or directory (os error 2)"
  },
  "id":null
}

{
  "mmrpc":"2.0",
  "error":"Error bch:633] utxo:1667] Failed to connect to at least 1 of [ElectrumRpcRequest { url: \"bch0.kister.net:5100\", protocol: TCP, disable_cert_verification: false }, ElectrumRpcRequest { url: \"testnet.imaginary.cash:5000\", protocol: TCP, disable_cert_verification: false }, ElectrumRpcRequest { url: \"blackie.c3-soft.com:6000\", protocol: TCP, disable_cert_verification: false }, ElectrumRpcRequest { url: \"tbch.loping.net:6000\", protocol: TCP, disable_cert_verification: false }, ElectrumRpcRequest { url: \"electroncash.de:5000\", protocol: TCP, disable_cert_verification: false }] in 5 seconds. on platform coin tBCH creation",
  "error_path":"platform_coin_with_tokens.bch_with_tokens_activation",
  "error_trace":"platform_coin_with_tokens:290] bch_with_tokens_activation:212]",
  "error_type":"PlatformCoinCreationError",
  "error_data":{
    "ticker":"tBCH",
    "error":"bch:633] utxo:1667] Failed to connect to at least 1 of [ElectrumRpcRequest { url: \"bch0.kister.net:5100\", protocol: TCP, disable_cert_verification: false }, ElectrumRpcRequest { url: \"testnet.imaginary.cash:5000\", protocol: TCP, disable_cert_verification: false }, ElectrumRpcRequest { url: \"blackie.c3-soft.com:6000\", protocol: TCP, disable_cert_verification: false }, ElectrumRpcRequest { url: \"tbch.loping.net:6000\", protocol: TCP, disable_cert_verification: false }, ElectrumRpcRequest { url: \"electroncash.de:5000\", protocol: TCP, disable_cert_verification: false }] in 5 seconds."
  },
  "id":null
}

More methods coming in the comments below.

hero image on mobile, not scaling

@media (max-width: 419px){ 
//hero image, default is 210px & auto 
  .home .hero img {
    max-height: 100%;
    max-width: 100%;
  }

Possible deprecation warning

Seeing this after yarn docs:dev

TIP  override.styl has been split into 2 APIs, we recommend you upgrade to continue.
      See: https://v0.vuepress.vuejs.org/default-theme-config/#simple-css-override

-ac_blocktime and tables

From dukeleto on Discord:

dukeletoLast Tuesday at 5:21 AM
@siddhartha-crypto i have some suggestions for improving KMD ac creation docs
so i will braindump here
I am researching all the params i want to use for the new HUSH chain
and I am pretty sure I want to use -ac_ccenable, but the number of each CC is undocumented
it would be awesome to see a table of each CC name and number, so it's possible to read docs and then come up with your AC creation command, without reading source code
dukeletoLast Tuesday at 5:51 AM
@siddhartha-crypto also, you can add -ac_blocktime to the experimental list

Changes to RPC affected by sapling update and disabling of z-txns on KMD mainchain

API related to Z-txns that need changes after sapling update: in disclosure.md, wallet.md, util.md

Also z-txn functionality is disabled on the KMD chain. Need to test and note if RPC such as z_mergetoaddress, z_sendtomany which were useful for transparent addresses too are functional

Need to note for the other z-RPC that they are only available in assetchains that have private txns enabled

Format for linking internal files, sections

Currently we use:

[`oraclesdata`](../cryptoconditions/cc-oracles.html#oraclesdata)

which gets rendered as

The green underline doesn't even appear till the pointer hovers above it. Without the pointer, it looks no different than a regular in-line code snippet.

If we use

[oraclesdata](../cryptoconditions/cc-oracles.html#oraclesdata)

it gets rendered as

The second format does a better job of suggesting a hyperlink. This behaviour is similar in tip,warning blocks too.

Add "utxo_merge_params" to enable/electrum docs

Add to legacy docs:

mm2 supports this options on enable/electrum command: \"utxo_merge_params\":{\"merge_at\":200,\"check_every\":600,\"max_merge_at_once\":100}
in this example, mm2 would check every 10 minutes if the number of utxos is bigger then 200 and if, it will merge automatically, but only max. 100 utxos at once, so that tx does not get too big

Originally posted by @cipig in KomodoPlatform/komodo-wallet-desktop#1436 (comment)

Change ### Arguments/Response etc. to ####

The ### hashtag registers in the search bar, whereas the #### hashtag does not.

Need to change this mistake throughout documentation.

I fixed many of the immediately visible issues, but there are probably many more.

Add cancellation_reason field in the order_status response examples.

@shamardy implemented this feature some time ago. It returns the status for all orders, even for canceled ones.

RPC Intro page + link to agama cli guide

New Agama CLI guide @ https://support.komodoplatform.com/support/solutions/articles/29000026800-agama-desktop-cli-command-line-

The section for RPC commands has no intro. Something like, "the following ......yada yada, you may have landed here from the Agama CLI guide" linking back to the cli guide as well.

I've asked (only in chat) if it's worth putting in a request to agama devs to create a regtest mode for people to safely test cli commands with a single host test chain.

Few packages mentioned in the liquidity provider tutorial are outdated

I was trying to follow the liquidity provider tutorial but I found the command specified in the guide is outdated.
I was suggesting installing old packages:
sudo apt-get install build-essential git jq llvm-3.9-dev libclang-3.9-dev clang-3.9 cmake libssl-dev pkg-config
Many of them where missing from Ubuntu 20.04, this worked for me:
sudo apt-get install build-essential git jq llvm-dev libclang-dev clang cmake libssl-dev pkg-config

https://developers.komodoplatform.com/basic-docs/atomicdex/atomicdex-tutorials/how-to-become-a-liquidity-provider.html#installing-dependencies

Document save_in_history argument of buy/sell/setprice.

It defines whether to save all information about order updates in a separate DB folder/table. It has a boolean type and the default value is "true".

Creating asset chain - what about for precompiled binary users?

like the title says

Had a complaint about how the binaries don't need to compile software. may need to make a note in docs.

Document new "is_mine" field in orderbook atomicDEX-API response.

Please document the new field. Related to KomodoPlatform/komodo-defi-framework#669

Add "How to Activate CryptoConditions on an Existing Chain"

Add into either asset chain parameters doc or into launch settings and maintenance.

https://docs.komodoplatform.com/cc/activate-cc-independent-chain.html

Documentation: Bitcoin should be changed to Litecoin

The documentation claims security by BTC but it has been changed by LTC.