#TOKEN TERMINAL HOW TO#
#TOKEN TERMINAL UPDATE#
#TOKEN TERMINAL FULL#

Since they are bound to our environment they are great for things such as API access tokens.

#TOKEN TERMINAL FULL#

With PATH, you can write just the name of an executable rather than the full path to it in your terminal since the shell will check the local directory as well as all directories specified in the PATH variable for this executable.Īside from ‘built-in’ variables we also have the opportunity to define our own environment variables. The most well known environment variable is probably PATH which contains the paths to all folders that might contain executables. Environment Variables?Įnvironment variables, as the name suggests, are variables in your system that describe your environment. Environment variables are a good solution and they are easy to consume in most languages. These are often configuration values that depend on the environment such as debugging flags or access tokens for APIs like Twilio. You can check out more info from here.There are some things we just shouldn’t share with our code. Creating a pull requestĬreating a pull request from a fork is as easy as creating one within the repo. You can check out commitlint.js.org for more info. It has same principles as in the creation of a branch.

#TOKEN TERMINAL UPDATE#

In this repo we have two feature types: the ones that add a new project ( add) to the repo and the ones that update an existing project ( update).Īn example branch name could be: update-compound-comptroller. We focus on two main naming conventions: feature type and description. Having consistent branch naming makes the initial step of the review clear. We want to encourage best practices in the creation of branches. In order for you to contribute, you will have to fork our repo. Being able to gather all relevant smart contracts in the ecosystem is a community-effort, which you are part of.

#TOKEN TERMINAL HOW TO#

How to contributeįirst of all, thank you for being awesome and taking the time to contribute. You can check Uniswap's uniswap.json registry for an example. That's why we'd like to track only the factory contract and one example of a factory-instantiated contract. This means that there's a contract that dynamically creates new contracts.įor the registry to be practical we don't necessarily want to track all the factory-instantiated contracts. Some projects make use of a Factory pattern in their smart contract design. How to add smart contracts with factory contracts If you're adding a project that's already listed on Token Terminal, you can check out the individual project page's URL: /terminal/projects/binance-smart-chain.

Binance Smart Chain: binance-smart-chain.

The naming of projects must match our main website's project pages, which adopt the 'kebab-case' naming convention: names are lowercase and spaces are replaced by hyphens.

explorers: A list of explorers that can be used to deep dive into the smart contracts.

description: A one-liner that explains what the smart contract does.

That's why we want to categorize each smart contract with either core or governance for standardization purposes.

type: Every smart contract is either core to the business or related to governance of the project.

For tokens the version should default to v1, although exceptions exist.

version: Smart contracts evolve and new versions get developed constantly.

If the chain doesn't exist, let's check it out together in the Pull Request. We've chosen polygon over matic for 0xPolygon as an example.

chain: Check the template.json for a valid chain.address: We prefer the address in the template to be checksummed.name: Should be something short and easy to understand, spaces are allowed.'description': 'Logic for the COMP lending market and the associated cCOMP token',Ĭheck out the template.json to see a field-by-field example.

Token terminal