Sponsored by a grant from the Aptos Foundation

The emojicoin dot fun Move package is audited:

• PDF Report
• Corresponding git tag move-v1.0.1-audited

To set up a simple release cycle for the code in this repository, you can target the production branch as the main deployment branch and use all other branches as preview/development builds.

The process is as simple as merging feature branches to main first to trigger CI/CD checks, and then once it's merged into main, merging or cherry-picking a subset of the new features into the production branch.

If you don't have a production branch yet, simply run the following:

1. git checkout main && git pull origin main
2. git checkout -b production
3. git push origin production

Now a production branch exists.

To merge new changes from main after production already exists, you can create a PR that merges all new changes in main into production.

It's possible to preserve the linear history of main when merging into production while still squashing the commits. This process looks like the following:

# Make sure `main` is up to date in your local environment.
git checkout main && git pull origin main

# Do the same for `production`.
git checkout production && git pull origin production

# Create a branch to make a PR to cherry-pick new changes from main into
# production with.
git checkout -b merge-main-to-prod

Now find the last commit that main and production share. If the commit history looks like this:

- main:
  - 06eadf3
  - 05eacbd
  - 04de8fb # Squashed into the last commit `ff382ba` in `production`.
  - 03aebcd # Squashed into the last commit `ff382ba` in `production`.
  - 02abde4 # Common ancestor.
  - 01ebadc
- production:
  - ff382ba # Commit that previously squashed `03..` + `04..` into `production`.
  - 02abde4 # Common ancestor.
  - 01ebadc

Then the last commit they share (the common ancestor) is 02abde4.

Thus you should run:

# Cherry-pick all commits from `02abde4..06eadf3` into `production`.
git cherry-pick 02abde4..06eadf3

# Push to the new branch.
git push origin merge-main-to-prod

Now you can make a PR to merge main to production with the merge-main-to-prod branch!

The fallback branch is intended to follow the production branch by a commit during indexer stack updates: whenever indexer stack changes merge to production, frontend deployments can be temporarily pointed at the fallback stack to prevent any downtime in the case of a production stack deployment failure or for in-place stack upgrades that result temporary outages.

For the purposes of indexer stack management, production only needs to be merged into fallback just before indexer changes land in production, nevertheless it is best practice to merge from production into fallback on a regular cadence.

You can set in Vercel project settings the production branch. By default, this is main, however you can use the production branch to separate staging environments from the release (aka production) environment.

Once you change the production branch setting in Vercel to the production branch on the repo, you should also set the environment variables for the production environment, to correspond to the current deployment on the production branch.

To view the current environment variables for a Vercel project, you can easily do so with the following steps detailed below.

The following instructions utilize the Vercel CLI to streamline the process of checking environment variables so you don't have to do it manually on Vercel, but you can also do all of this through Vercel on their web application.

Install the vercel-cli tool. You can install it with npm or brew.

# Install with brew.
brew install vercel-cli

# Install globally with pnpm.
pnpm i -g vercel@latest

Login to Vercel through the cli with GitHub OAuth authentication:

vercel login --github

Pull the currently set Vercel environment variables for various environments and branches:

vercel env pull --environment=production

vercel env pull --environment=preview

vercel env pull --environment=development

To update any of these values, you can use vercel env add ..., or you can save the output of vercel env pull --environment=... and upload that to Vercel with the Import .env option.

See the image below for an example of what this process looks like for adding the following environment variables to the Preview and Deployment environments.

# If you wanted to change a couple values, you'd create an .env file,
# then upload that to Vercel.
# For example, if your file consisted of the following two lines, when you
# upload the file with "Import .env", it will look like the image below.
NEXT_PUBLIC_APTOS_NETWORK="testnet"
NEXT_PUBLIC_INTEGRATOR_FEE_RATE_BPS="100"

Note the Environments checkboxes. You must specify which Environments to apply the environment variables to. In most cases you should alter Production environment variables manually.

Once you make any changes, either with the CLI or through Vercel's UI, you must pull the environment variables again to see the new, updated values in your local repository's settings.

See the Vercel CLI docs for more information.

This repository uses a closed-source implementation of the TradingView charting library for the production website.

If you don't have access to TradingView's charting_library repository, please run the command below to clone the appropriate submodules:

git submodule update --init --recursive src/rust/processor

If you do have access to the charting_library repository:

git submodule update --init --recursive