• Tutorials
  • >
  • Institutional Host Implementation
  • >
  • HCNet.toml

HCNet.toml

HCNet.toml:-

How and Why to Complete Your HCNet.toml

If you are interested in issuing a token on the HC Net, but haven’t yet, start by consulting the step-by-step instructions for custom asset creation here.

Hello! We made this short guide to help you, a token issuer, put your token in the best possible place to succeed on HC Net.

Mostly, we want to make sure you know how to provide information to the network about yourself and your token, so that potential buyers and apps, like exchanges and wallets, will trust your asset. You provide this necessary information by completing your HCNet.toml file.

The best tokens on HC Net already follow the guidelines below, and apps and buyers will expect your token to do the same.

Why you should complete your HCNet.toml file

The most successful token issuers give exchanges and potential buyers lots of information about themselves. On HCNet, they do this in the HCNet.toml file. More information in your token’s HCNet.toml will mean:

  • your token is listed on more exchanges
  • your token holders are more confident
  • very likely, your project is more successful

For example, the HCNet app, HCX, uses the HCNet.toml file to decide how your token is presented to traders in its markets view. If you don’t provide enough information, your token may be hidden from many traders. Other HC Net exchanges like HCNetport.io and HCNetterm.com make similar decisions.

Many won’t list your token at all without a robust HCNet.toml.

The HCNet.toml file is so important that the first HCNet Ecosystem Proposal is devoted to outlining what it should contain. You can find the complete SEP 0001 here, but we’ll summarize the important parts below.

What is your HCNet.toml?

Your HCNet.toml is a file you write in TOML, which is a simple configuration file format, and publish at https://YOUR_DOMAIN/.well-known/HCNet.toml. Anyone can look it up, and it proves that the owner of the https domain hosting the HCNet.toml claims responsibility for the accounts and tokens listed in it. So it’s your chance to legitimize your offering, and to announce vital information about your organization and your token. If you offer multiple tokens, you can list them all in one HCNet.toml file.

How to complete your HCNet.toml

SEP 0001 specifies five sections you can add to your HCNet.toml: Account Information, Issuer Documentation, Point of Contact Documentation, Currency Documentation, and Validator Information. Within those sections, some fields only apply to specialized tokens, but many apply to all tokens, and these guidelines will outline which fields are:

  • Required: all token issuers must include this information in their HCNet.toml if they want to be listed on exchanges.
  • Suggested: any token issuer who wants their offering to stand out should complete these fields.

ACCOUNT INFORMATION

There is one field in the Account Information section required for all token issuers:

  • ACCOUNTS: A list of public keys for all the HC Net accounts associated with your token.

Listing your public keys lets users confirm that you, in fact, own them. For example, when https://google.com hosts a HCNet.toml file, users can be sure that only the accounts listed on it belong to Google. If someone then says, “You need to pay your Google bill this month, send payment to address GIAMGOOGLEIPROMISE”, but that key is not listed on Google’s HCNet.toml, then users know to not trust it.

Most of the other information specified in the Account Information section is only necessary for validators and financial institutions.

Here’s an example of a completed ACCOUNTS field listing three public keys:

  • ACCOUNTS=[
  • "GAPJN32J7O6EXXWNZ2P5VIMT7KFETQMZN27IILUSW7KZDZKCNRLQFON",
  • "GRSX5RFPE6GCKMY3US5U8B6UZLKIGSPIUKSLRB6Q723BM2OARMDUYEIO",
  • "GKLANGBA5YHTNYVVV4C3U2522EB6P6F5T3U6MM63WBSBZATA3IEQJKE2"
  • ]

ISSUER DOCUMENTATION

Basic information about your organization goes into a TOML table called [DOCUMENTATION]. Issuer Documentation is your chance to inform exchanges and buyers about your business, and to demonstrate that your business is legitimate and trustworthy.

The more you fill out, the more likely people are to believe in your offering.

Required: All issuers must include the following information:

  • The legal name of your organization (org_name), and if your business has one, its official dba (org_dba).
  • The URL of your organization’s official website (org_url). In order to prove the website is yours, you must host your HCNet.toml on the same domain you list here. That way, exchanges and buyers can view the SSL certificate on your website, and feel reasonably confident that you are who you say you are.
  • A URL to a company logo (org_logo), which will show up next to your organization on exchanges. If you fail to provide a logo, the icon next to your organization will appear blank on many exchanges.
  • The physical address of your organization (org_physical_address). We understand you might want to keep your work address private. At the very least, you should put the city and country in which you operate. A street address is ideal and provides a higher level of trust and transparency to your potential users.
  • Your organization’s official phone number (org_phone_number).
  • Your organization’s official Twitter handle (org_twitter).
  • The best contact email address for you organization (org_official_email). This should be hosted at the same domain as your official website.

Suggested: Including this information will help your offering stand out:

  • Your organization’s official Github account (org_github).
  • Your organization’s official Keybase account (org_keybase). Your Keybase account should contain proof of ownership of any public online accounts you list here, including your organization’s domain.
  • A description of your organization (org_description). This is fairly open-ended, and you can write as much as you want. It’s a great place to distinguish yourself by describing what it is that you do.

Exchanges might desire additional verifiable information when deciding how to present your token to traders, and prioritize tokens that include it:

  • Attestation of the physical address listed above (org_physical_address_attestation). This is a URL to an image on your organization’s domain of an official third party document (such as a utility bill) that shows your organization’s name and address.
  • Attestation of the phone number listed above (org_phone_number_attestation). This is a URL to an image on your domain showing a phone bill listing both your phone number and your organization’s name.

Here’s an example of completed Issuer Documentation:

  • [DOCUMENTATION]
  • ORG_NAME="Organization Name"
  • ORG_DBA="Organization DBA"
  • ORG_URL="https://www.domain.com"
  • ORG_LOGO="https://www.domain.com/awesomelogo.jpg"
  • ORG_DESCRIPTION="Description of issuer"
  • ORG_PHYSICAL_ADDRESS="123 Sesame St., New York, NY, 12345"
  • ORG_PHYSICAL_ADDRESS_ATTESTATION="https://www.domain.com/address_attestation.jpg"
  • ORG_PHONE_NUMBER="1 (123)-456-7890"
  • ORG_PHONE_NUMBER_ATTESTATION="https://www.domain.com/phone_attestation.jpg"
  • ORG_KEYBASE="accountname"
  • ORG_TWITTER="orgtweet"
  • ORG_GITHUB="orgcode"
  • ORG_OFFICIAL_EMAIL="support@domain.com"

POINT OF CONTACT DOCUMENTATION

Information about the primary point of contact for your organization goes into a TOML list called [[PRINCIPALS]]. You need to put contact information for at least one person at your organization. If you don’t, exchanges can’t verify your offering, and it is unlikely that buyers will be interested.

Required: All token issuers should include the following information about their point of contact:

  • The name of the primary contact (name).
  • The primary contact’s official email address (email). This should be hosted at the same domain as your organization’s official website.
  • The personal Twitter handle of the point of contact (twitter).

Suggested: If the point of contact for your organization has them, we suggest you also include:

  • The personal Github account of the point of contact (github).
  • The personal Keybase account for the point of contact (keybase). This account should include proof of ownership of the email address listed above.

Again, the more information you provide, the better. Exchanges might desire additional verifiable information when deciding how to present your token to traders, and prioritize tokens that include it:

  • A SHA-256 hash of a photo of the point of contact’s government-issued photo ID (id_photo_hash).
  • A SHA-256 hash of a verification photo of the point of contact holding a signed, dated, handwritten message detailed in SEP 0001 (verification_photo_hash).

The photo hashes allow exchanges and wallets to confirm the identity of your point of contact. Those services can contact you privately to request ID and verification photos, then check those photos against the hashes listed here to make sure they match. If the hashes match, they will let their clients know that your contact information is verified.

Here’s an example of completed Point of Contact Documentation for one principal:

  • [[PRINCIPALS]]
  • name="Jane Jedidiah Johnson"
  • email="jane@domain.com"
  • twitter="@crypto_jane"
  • keybase="crypto_jane"
  • github="crypto_jane"
  • id_photo_hash="7g249e170f4f134b18ab3de069c5a13e5c3ef3ef90f3643afa15a1603c34cf36"
  • verification_photo_hash="703687f6abd594366a09cfe6b380e58f9023867a851cc9fa71f302ab4889e23"

TOKEN DOCUMENTATION

Information about your token goes into a TOML list called [[CURRENCIES]]. If you are issuing multiple tokens, you can include them all in one HCNet.toml. Each token should have its own [[CURRENCIES]] list.

Required: All issuers must provide the following information for each token they issue:

  • The asset code (code). This is one of two key pieces of information that identify your token. Without it, your token cannot be listed anywhere.
  • The HC Net public key of the issuing account (issuer). This is the second key piece of information that identifies your token. Without it, your token cannot be listed anywhere.
  • The status of your token (status): live, dead, or test. Marking your token live means you are ready for exchanges to list it. If your token is ready to trade, and you fail to list its status, it may not appear on exchanges.
  • An indication of whether your token is Institutional Hosted or native (is_asset_institutional_hosted): true if your token can be redeemed for an asset outside the HC Net, false if it can’t. Exchanges use this information to sort tokens by type in listings. If you fail to provide it, your token is unlikely to show up in filtered market views.
  • A preference for number of decimals when client displays currency balance (display_decimals).
  • A short name for the token (name). If you fail to name your token, exchanges may not be able to display it properly.

You also need to describe your token issuance policy by filling in exactly one of the following mutually exclusive fields:

  • fixed_number, which you should specify if you are issuing a set number of tokens, and that number will never increase.
  • max_number, which you should specify if there is an upper limit to the number of tokens you will issue.
  • is_unlimited, which you should specify if you reserve the right to create more tokens at your discretion.

Suggested: If you want your token to stand out, you should also include the following:

  • A description of your token and what it represents (desc). This is a good place to clarify what your token does, and why someone might want to own it.
  • Any conditions you place on the redemption of your token (conditions).
  • A URL to an image representing token (image). Without it, your token will appear blank on many exchanges

Here’s what an example of completed Currency Documentation:

  • [[CURRENCIES]]
  • code="GOAT"
  • issuer="GRTBKZPYOQYPDEFJKLKY9FNNRQMGFLVHKBVCGNSLRRGSMPGF78GFDCVK5"
  • status=”live”
  • display_decimals=2
  • name="goat share"
  • desc="1 GOAT token entitles you to a share of revenue from Elkins Goat Farm."
  • conditions="There will only ever be 10,000 GOAT tokens in existence. We will distribute the revenue share annually on Jan. 15th"
  • image="https://pbs.twimg.com/profile_images/666921221410439168/iriHah4f.jpg"
  • fixed_number=10000

INSTITUTIONAL HOSTED OR ASSET-BACKED TOKEN REQUIREMENTS:

Institutional Hosted tokens are specialized assets in the HC Net ecosystem because they can be redeemed outside of the network for other assets. If you are issuing an Institutional Hosted token, you need to provide additional information about those assets, and about how to redeem your token for them.

In addition to Currency Documentation listed above, the following fields are required for Institutional Hosted tokens:

  • The type of asset your token represents (institutional_host_asset_type). The possible categories are fiat, crypto, stock, bond, commodity, real estate, and other.
  • The name of the asset that serves as the Institutional Host for your token (institutional_host_asset).
  • Instructions to redeem your token for the underlying asset (redemption_instructions).

Because of the nature of assets Institutional Hosted to crypto, exchanges are unlikely to list them without the following verifiable information:

  • The public addresses that hold the crypto assets (collateral_addresses).
  • Proof that you control those public addresses (collateral_address_signatures). SEP 0001 contains a template for these signatures, and instructions for tailoring them to your token.

Exchanges use the collateral address signatures to verify that the accounts you list belong to you, and will look at the reserve in those accounts. If you cannot prove 100% reserve, it is unlikely they will list your token.

  • [[CURRENCIES]]
  • code="BTC"
  • issuer="GRTBKZPYOQYPDEFJKLKY9FNNRQMGFLVHKBVCGNSLRRGSMPGF78GFDCVK5"
  • status=”live”
  • display_decimals=7
  • name=”Bitcoin”
  • desc=”Organization promises to purchase each BTC token from any holder for the value of 1 Bitcoin”
  • conditions="Withdrawal fees apply"
  • image="https://domain.com/img/Bitcoin-100x100.png"
  • institutional_host_asset_type="crypto"
  • institutional_host_asset="BTC"
  • redemption_instructions="Use SEP6 with our mapping server"
  • collateral_addresses=["3C1mCx3ukix1KfegAY5zgQJV7sanAciZkf"]
  • collateral_address_signatures=["404502206e21798a42fae0e859381abd38bacd1aeed3ee3738d9e1446618c4571d12"]

How to publish your HCNet.toml

After you’ve followed the steps above to complete your HCNet.toml, post it at the following location:

  • https://YOUR_DOMAIN/.well-known/HCNet.toml

Enable CORS so people can access this file from other sites, and set the following header for an HTTP response for a /.well-known/HCNet.toml file request.

  • Access-Control-Allow-Origin: *

Once you’ve done that, you’re all set! Now apps and buyers can access all the information you’ve provided with a simple HTTP request.

An example of a good HCNet.toml: Stronghold

If you want to see a HCNet.toml done right, take a look at Stronghold’s here. You can easily find out everything you need to know about the company, their Hashcash accounts, their points of contact, and their tokens, and you can take steps to verify that information.

If your HCNet.toml looks like Stronghold’s, exchanges and buyers will take notice.

How to publish your HCNet.toml

After you’ve followed the steps above to complete your HCNet.toml, post it at the following location:

  • https://YOUR_DOMAIN/.well-known/HCNet.toml

Enable CORS so people can access this file from other sites, and set the following header for an HTTP response for a /.well-known/HCNet.toml file request.

  • Access-Control-Allow-Origin: *

Once you’ve done that, you’re all set! Now apps and buyers can access all the information you’ve provided with a simple HTTP request.

An example of a good HCNet.toml: Stronghold

If you want to see a HCNet.toml done right, take a look at Stronghold’s here. You can easily find out everything you need to know about the company, their Hashcash accounts, their points of contact, and their tokens, and you can take steps to verify that information.

If your HCNet.toml looks like Stronghold’s, exchanges and buyers will take notice.

HCNet.toml

Introduction

The HCNet.toml file is used to provide a common place where the Internet can find information about your domain’s HC Net integration. Any website can publish HC Net information. You can announce your validation key, your mapping server, peers you are running, your quorum set, if you are an Institutional Host, etc.

The HCNet.toml file is a text file in the TOML format.

Publishing HCNet.toml

Given the domain “DOMAIN”, the HCNet.toml will be searched for at the following location:

https://DOMAIN/.well-known/HCNet.toml

Enabling cross-origin resource sharing (CORS)

You must enable CORS on the HCNet.toml so people can access this file from other sites. The following HTTP header must be set for a HTTP response for HCNet.toml file request.

Access-Control-Allow-Origin: *

Important: Only enable CORS for HCNet.toml (or any files it references). For example, in Apache you would set something like:
  • <Location "/.well-known/HCNet.toml"> Header set Access-Control-Allow-Origin "*" </Location>

Or in nginx:

  • location /.well-known/HCNet.toml {
  • add_header 'Access-Control-Allow-Origin' '*';
  • }

For other web servers, see: http://enable-cors.org/server.html

Testing CORS

  • 1. Run a curl command in your terminal similar to the following (replace HCNet.org with the hosting location of your HCNet.toml file):

curl --head https://HCNet.org/.well-known/HCNet.toml

  • 1. Verify the Access-Control-Allow-Origin header is present as shown below.

curl --head https://HCNet.org/.well-known/HCNet.toml

  • HTTP/1.1 200 OK
  • Accept-Ranges: bytes
  • Access-Control-Allow-Origin: *
  • Content-length: 482
  • ...

  • 1. Also run the command on a page that should not have it and verify the Access-Control-Allow-Origin header is missing.

HCNet.toml example

This file is UTF-8 with Dos-, UNIX-, or Mac-style end of lines. Blank lines and lines beginning with ‘#’ are ignored. Undefined sections are reserved. All sections are optional. Many of these sections reflect what would be listed in your HCNet-core.cfg

  • # Sample HCNet.toml
  • # The endpoint which clients should query to resolve HC Net addresses
  • # The endpoint which clients should query to resolve HC Net addresses
  • # for users on your domain.
  • MAPPING_SERVER="https://api.HCNet.org/mapping"
  • # The endpoint used for the regulation protocol
  • AUTH_SERVER="https://api.HCNet.org/auth"
  • # The signing key is used for the regulation protocol
  • SIGNING_KEY="GRTBKZPYOQYPDEFJKLKY9FNNRQMGFLVHKBVCGNSLRRGSMPGF78GFDCVK5"
  • # convenience mapping of common names to node IDs.
  • # You can use these common names in sections below instead of the less friendly nodeID.
  • # This is provided mainly to be compatible with the HCNet-core.cfg
  • NODE_NAMES=[
  • "GKLANGBA5YHTNYVVV4C3U2522EB6P6F5T3U6MM63WBSBZATA3IEQJKE5 lab1",
  • "GR6REF5GOGGSEHZ3L2YK6K4T4KX3YDMWHDCPMV7MZJDLHBDNZXEPRBKL donovan",
  • "GRTY22MRCIVW2UZHFXMY5UIBJGPYABPQXQ5GGMNCSUM2KHE3N6CNHGFR nelisky1",
  • "GLOPQCSKVYAJSUGR2HBYVFVR7NA7YWYSYK3XYKKFO553OQGOHAUP2OPQ jianing",
  • "GRTEYLWBC4XF6VWRP5ESJ6IBHAISVJMSBTALHOQM2EZG7Q477UWA6LTY institutional host"
  • ]
  • # A list of accounts that are controlled by this domain.
  • ACCOUNTS=[
  • "$sdf_watcher1",
  • "GKKNZLGHJGJRCMX5VCHOLHQXU3EMCU5XWDNU4BGGJFNLI2EL354IVBLR"
  • ]
  • # Any validation public keys that are declared
  • # to be used by this domain for validating ledgers and are
  • # authorized signers for the domain.
  • OUR_VALIDATORS=[
  • "$sdf_watcher2",
  • "GRSB2S2KGYARPVIA37HYZXVRM2YZUEXA6S33ZU5BUDC6THSB62LZSTLO"
  • ]
  • # DESIRED_BASE_FEE (integer)
  • # This is what you would prefer the base fee to be. It is in jots.
  • DESIRED_BASE_FEE=100
  • # DESIRED_MAX_TX_PER_LEDGER (integer)
  • # This is how many maximum transactions per ledger you would like to process.
  • DESIRED_MAX_TX_PER_LEDGER=400
  • # List of IPs of known HCNet-core's.
  • # These are IP:port strings.
  • # Port is optional.
  • # By convention, IPs are listed from most to least trusted, if that information is known.
  • KNOWN_PEERS=[
  • "192.168.0.1",
  • "core-testnet1.HCNet.org",
  • "core-testnet2.HCNet.org:11290",
  • "2001:0db8:0100:f101:0210:a4ff:fee3:9566"
  • ]
  • # list of history archives maintained by this domain
  • # This section allows an Institutional Host to declare currencies it currently issues.
  • # Can be used by wallets and clients to trust Institutes by domain name
  • [[CURRENCIES]]
  • code="USD"
  • issuer="GOOJM35NKGVK47BB4SPBDV25477PZYIYPVVG453LPYFNXLS3FGHDXORS"
  • display_decimals=2 # Specifies how many decimal places should be displayed by clients to end users.
  • [[CURRENCIES]]
  • code="BTC"
  • issuer="$institutional host"
  • display_decimals=7 # Maximum decimal places that can be represented is 7
  • # asset with meta info
  • [[CURRENCIES]]
  • code="GOAT"
  • issuer="GSSS6IPRNCKFOHQWT264YPKOZAWUMMZOLZBJ6BNQMUGPWGRLBK3U7ZLR"
  • display_decimals=2
  • name="goat share"
  • desc="1 GOAT token entitles you to a share of revenue from Elkins Goat Farm."
  • conditions="There will only ever be 10,000 GOAT tokens in existence. We will distribute the revenue share annually on Jan. 15th"
  • image="https://pbs.twimg.com/profile_images/666921221410439168/iriHah4f.jpg"
  • # Potential quorum set of this domain's validators.
  • [QUORUM_SET]
  • VALIDATORS=[
  • "$self", "$lab1", "$nelisky1","$jianing","$eno","$donovan"
  • ]
  • # optional extra information for humans
  • # Useful place for Institutional Hosts to detail various policies and required info
  • ###################################
  • # Required compliance fields:
  • # name=
  • # addr=<recipient address> </recipient>
  • # Mapping Format:
  • # *InstitutionalHost.com
  • # Forwarding supported by sending to:
  • forward*InstitutionalHost.com
  • # forward_type=bank_account
  • # swift=< swift code of receiving bank>swift>
  • # acct=<recipient account number at receiving bank></recipient>
  • # Minimum Amount Forward: $2 USD
  • # Maximum Amount Forward: $10000 USD
+
Chat Now
Welcome to HashCash Support