GameChanger Wallet Library and CLI

Official GameChanger Wallet library and CLI for integrating Cardano via intents in links, QRs, dapps, web, screens, social media and solve other related tasks (https://gamechanger.finance/)

Complete refactor for Node v24.x.x . Supports all GameChanger Wallet V2.x.x flavors

Try it online:

✨ Kitchen Sink Dapp ✨

100 % backend-less: (no special backend required)
All the supported outputs formats for you to integrate or share
All the supported code generation languages for you to integrate

Examples:

To run Kitchen Sink and other web based examples:

$ pnpm run examples

To run the backend example:

$ pnpm run examples:express

To run the NPM project example:

$ pnpm install
$ pnpm run dev

Custom examples

Kitchen Sink: all outputs in one example
NPM Project Example: a modular, GCScript multi-file NPM (dummy) project with auto frontend generation

CLI/library output examples

html and react outputs are richer shared-state app boilerplates with local storage persistence that can host multiple intents (scripts coded in GCScript DSL) in one dapp and auto-render end-user UI from the intent code itself.

html-zero is the minimal zero-dependency flavor aimed at highly resilient, offline-ready, small-footprint frontends for long term reliability that can be stored on-chain with GCFS and work without any dependencies or centralized points of failure.

express is a minimal Node/Express backend example that redirects browser users to the wallet and then captures the response via "webhook" redirection. Express is suggested only for serving snippets or running Express examples; it is not required for normal CLI encode, snippet generation, or build actions.

Install CLI

$ npm install --global @gamechanger-finance/gc

Node target: >=24.12.0

Install Library

$ npm install -s @gamechanger-finance/gc
# or
$ pnpm add @gamechanger-finance/gc

Import library on your projects:

For importing on html document:

Install:
  $ npm install -s @gamechanger-finance/gc
    or
  copy or host individual file 'dist/browser.min.js'

Load locally:
  <script src='dist/browser.min.js'></script>

Load using CDN :
  <script src="https://cdn.jsdelivr.net/npm/@gamechanger-finance/gc/dist/browser.min.js"></script>

Use:
  const {gc} = window;

For Node.js / React / Vite / webpack projects:

Install:
  $ npm install -s @gamechanger-finance/gc
Use (ESM default export):
  import gc from '@gamechanger-finance/gc'
Use (ESM named exports):
  import {gc, encode, snippet, build, validate, encodings} from '@gamechanger-finance/gc'
Use (CommonJS):
  const gc = require('@gamechanger-finance/gc')

Local repository build targets:
  import gc from './dist/nodejs.js'
  const gc = require('./dist/nodejs.cjs')

Distribution targets

Published artifacts kept for npm and CDN usage:

dist/browser.js
dist/browser.min.js
dist/nodejs.cjs
dist/nodejs.js
dist/index.d.ts and the emitted declaration graph under dist/** for TypeScript consumers

Package entrypoints:

ESM / Node: import gc from "@gamechanger-finance/gc"
CommonJS / Node: const gc = require("@gamechanger-finance/gc")
Browser global: const {gc} = window

The Node and CLI QR path no longer depends on canvas / easyqrcodejs-nodejs at install time. Styled QR output is generated from EasyQRCodeJS SVG output and rasterized on Node only when PNG output is requested.

The browser bundle now keeps the Node-only QR runtime isolated from browser-targeted builds, so bundlers such as Vite can consume the package without pulling @napi-rs/canvas, jsdom, or the Node EasyQRCodeJS runtime into browser dependency graphs.

For local packaging / smoke tests during development:

npm run pack:local

Library usage:

Encode dapp intent (dapp -> wallet message):

//GCScript: the DSL scripting language to interact with GameChanger Wallet
const gcscript = {
  type: 'script',
  title: '🚀 Connect with dapp?',
  description:
    'About to share your basic public wallet information to the dapp',
  exportAs: 'connect',
  run: {
    name: {
      type: 'getName'
    },
    address: {
      type: 'getCurrentAddress'
    },
    spendPubKey: {
      type: 'getSpendingPublicKey'
    },
    stakePubKey: {
      type: 'getStakingPublicKey'
    },
    addressInfo: {
      type: 'macro',
      run: "{getAddressInfo(get('cache.address'))}"
    }
  }
}

const url = await gc.encode.url({
  input: JSON.stringify(gcscript), // GCScript is pure JSON code, supported on all platforms
  apiVersion: '2', //APIV2
  network: 'mainnet', // mainnet or preprod
  encoding: 'gzip', //suggested, default message encoding/compression
  refAddress: 'addr1...', // optional - appends ref=<address>. For referral programs, a valid Cardano address under the same `network`
  disableNetworkRouter: false, // optional - by default appends networkTag=<network>. Set true to avoid prompting a network switch.
  urlPattern: 'http://localhost:3000/api/2/run/{gcscript}' // optional - override the default wallet URL pattern (must include {gcscript})
})

then redirect users to the URL like:

<a href="${url}">Connect with GC Wallet</a>

or render a QR encoded URL image like this:

const pngDataURI = gc.encode.qr({
  input: JSON.stringify(gcscript),
  apiVersion: '2',
  network: 'mainnet',
  encoding: 'gzip',
  refAddress: 'addr1...', // optional - appends ref=<address>. For referral programs, a valid Cardano address under the same `network`
  disableNetworkRouter: false, // optional - by default appends networkTag=<network>. Allows to stop requesting the user to switch to the network specified in `network` tag
  urlPattern: 'http://localhost:3000/api/2/run/{gcscript}', // optional - override the default wallet URL pattern (must include {gcscript})
  qrResultType: 'png'
})

then redirect users with the QR code like:

<image src="${pngDataURI}">Scan QR code to connect</image>

By default, gc.encode.url(...) and gc.encode.qr(...) handlers append networkTag=<network> to generated wallet URLs. Set disableNetworkRouter: true to skip that query string. When refAddress is provided, handlers also append ref=<address> while preserving any query string data already present in the base URL pattern.

Snippet customization (html / html-zero / react / button / express)

All snippet handlers support:

urlPattern (string): override the wallet URL pattern used by snippet-generated code and defaults (must be an absolute URL and contain {gcscript}).
snippetArgs (object): per-placeholder overrides for snippet templates. Values are injected as-is.

Special snippetArgs.defaultIntents can override the entire defaultIntents JS object literal (comments allowed). This override has priority over the single intent injected from the provided input script.

Build multi-file GCScript projects

The build.file handler receives the same raw JSON string shape as the other handlers, resolves build-time directives such as $importAsData and $importAsScript, and returns one final GCScript JSON file as a data URI. These directives run only during the build step; they are not wallet interpreter macros.

Build inputs may use JSONC comments (// and /* ... */) and trailing commas. This compatibility is scoped to the build handler and to JSON-compatible imports ($importAsScript, $importAsData with as: "object", and $importAsData with as: "json"). The emitted GCScript is always strict JSON again: no comments, no trailing commas. Other handlers still require strict JSON.

const files = {
  'config.json': {
    data: gc.utils.Buffer.from('{"enabled":true}', 'utf8')
  },
  'scripts/connect.gcscript': {
    data: gc.utils.Buffer.from(
      '{"type":"script","run":{"address":{"type":"getCurrentAddress"}}}',
      'utf8'
    )
  }
}

const outputDataURI = await gc.build.file({
  input: `{
    // JSONC comments are allowed during build only.
    "type": "script",
    "run": {
      "config": {
        "type": "$importAsData",
        "as": "object",
        "from": { "config": "app://config.json" },
      },
      "connect": {
        "type": "$importAsScript",
        "args": "{get('args')}",        
        "from": { "connect": "app://scripts/connect.gcscript" },
      },
    }
  }`,
  // fileUri is only the logical parent URI used to resolve relative imports.
  // It is never read or written as the build input file.
  fileUri: 'app:///main.gcscript',
  files
})

// Use compactOutput for smaller generated files when whitespace is not needed.
const compactOutputDataURI = await gc.build.file({
  input: '{"type":"script","run":{}}',
  fileUri: 'app:///main.gcscript',
  compactOutput: true
})

const builtGcscript = gc.utils.dataURIToBuffer(outputDataURI).toString('utf8')

$importAsScript is a thin build-time wrapper for the normal GCScript script function. It resolves from into the generated wrapper run, and every other property such as args, argsByKey, isolateCache, return, or finally is passed through verbatim for the final GCScript/schema/wallet validation layers. The build layer does not distribute argsByKey into imported children.

$importAsData is a thin build-time wrapper for the normal GCScript data function. It resolves from, converts each imported resource according to as (string, object, json, hex, or base64), and emits the converted result as the generated data node value. Other data-node properties are passed through for final GCScript/schema/wallet validation.

By default, build.file validates the final resolved strict JSON against the GCScript JSON Schema. Library validation requires a useSchema object; if doValidate is not false and no schema is provided, the library throws a clear Missing useSchema error. Pass doValidate: false only when you intentionally want to skip schema validation, for example in tests or offline prototyping. The helper below downloads the production schema URL and can be overridden by callers:

const useSchema = await gc.utils.downloadGCScriptSchema()
const outputDataURI = await gc.build.file({
  input: sourceJSONC,
  fileUri: 'app:///main.gcscript',
  files,
  useSchema
})

Notes:

Build imports are explicit and protocol-qualified. Protocol-less imports such as ./common.gcscript.jsonc, ../common.gcscript.jsonc, or lib/common.gcscript.jsonc are rejected before loading.
Useapp://./common.gcscript.jsonc or app:///lib/common.gcscript.jsonc for app-rooted resources.
Protocol file:// remains disabled by default; when explicitly enabled, file://./x and file://../x resolve with the same directory-navigation semantics as app://, but may traverse outside the app root.
In CLI -f argument only selects the input file; pass --cwd as the app filesystem root and --fileUri app:///main.gcscript as the logical build URI.

Validate built GCScript JSON

The validate.file handler consumes the already-built GCScript strict JSON. It does not accept JSONC comments or trailing commas because validation is meant for build artifacts and CI/CD checks, not source files.

const useSchema = await gc.utils.downloadGCScriptSchema()
const reportDataURI = await gc.validate.file({
  input: builtGcscript,
  fileUri: 'app://dist/built.gcscript',
  fileName: 'built.gcscript',
  useSchema
})
const report = JSON.parse(
  gc.utils.dataURIToBuffer(reportDataURI).toString('utf8')
)
if (!report.isValid)
  console.error(report.errors[0].jsonPath, report.errors[0].message)

Reports include isValid, errors, non-blocking warnings, the relevant file identifiers, JSON path, location when available, provided value, and concise hints/examples when the full schema flavor provides documentation metadata. Validation also performs lightweight ISL checks for very likely inline code strings, reporting probable function-name typos as warnings rather than errors.

For bulk fixture checks, run:

pnpm run test:gcscript

That command dynamically validates every GCScript fixture under test/gcscript/, writes one JSON report per fixture into test/gcscript/report/, and continues through all files before failing the run if any report is invalid. The validation fixture suite also rewrites test/validation-fixtures/reports/*.report.json for manual inspection of invalid-code DevEx regressions.

Build protocol resolvers:

app://: the only default allowed protocol. In library calls, it reads from files. In the CLI, it resolves relative to --cwd and cannot escape that directory.
file://: platform-specific and not allowed by default. Browser builds do not include Node filesystem code. In the CLI, file:// is unrestricted once explicitly enabled with --allowProtocols; use app:// for cwd-restricted project files.
http:// and https://: resolved through fetch where available. Callers may restrict hosts with allowedRemoteDomains; CLI users can pass --allowedRemoteDomains example.com,*.example.org.
blob:: browser-oriented local resolver through fetch where available.

Security model:

DefaultBuildAllowedProtocols is ['app'].
CLI build logging prints a summary with dependency resource sizes and GCScript hashes unless --quiet is set or output is sent to stdout.
gc.utils.hashCode(code) matches the wallet-side hash: SHA-512 over JSON.stringify(code). It is not called by build() unless a caller opts into logging/summary work.
Protocol categories are exported as BuildResourceProtocolCategories: local, immutable, and mutable.
Unknown future protocols are treated as mutable by default.
Mutable remote resources such as http/https taint their dependency branch and cannot import nested local resources such as app, file, or blob.

CLI notes:

The CLI keeps generated output POSIX-friendly: human progress, warnings, and validation summaries are written to stderr; generated artifacts and validation JSON reports are written to stdout only when -o/--outputFile is omitted.
--quiet suppresses non-essential human logs without changing generated output.
Validation warnings are shown by default during build and validate; pass --hide-warnings to hide them.
Successful encode, snippet, and build actions exit 0; failures exit non-zero.
validate exits 0 only when the report has isValid: true.

Virtual files use Buffer for cross-target consistency:

type VirtualFileSystem = {
  [relativeFilePath: string]: { data: Buffer; mimeType?: string }
}

For online IDEs and project import/export flows, use the ZIP or TAR.GZ helpers:

const zipDataURI = gc.utils.virtualFileSystemToZip(files)
const restoredZipFiles = gc.utils.zipToVirtualFileSystem(zipDataURI)

const tarGzDataURI = gc.utils.virtualFileSystemToTarGz(files)
const restoredTarGzFiles = gc.utils.tarGzToVirtualFileSystem(tarGzDataURI)

A package-based example is available under examples/project.

Decode intent execution results (wallet -> dapp message):

//Once GC Wallet executes an intent script, it can return arbirary JSON data to be exported back to the dapp
const resultObj = await gc.encodings.msg.decoder(resultRaw)
console.log(resultObj)

and will log something like:

{
  "exports": {
    "connect": {
      "name": "MyCardanoWallet",
      "address": "addr1q8aw6dzpw3cld828cqywp0sql4sxfw6syhzyh2kfcfccakddqwj2u3djrag0mene2cm9elu5mdqmcz9zc2rzgq7c5g6qshxn7l",
      "spendPubKey": {
        "pubKeyHex": "48362707efe478336740139127d8468aca10bf1358d2ab903d2d58876c99733b",
        "pubKeyHashHex": "faed34417471f69d47c008e0be00fd6064bb5025c44baac9c2718ed9",
        "derivationKind": "spend"
      },
      "stakePubKey": {
        "pubKeyHex": "9bef2297c79a52da05c33e99097e806e44ddda04e0dbaf7afef9274a64059557",
        "pubKeyHashHex": "cb6785612a53f5a093f38212db67bf4da23881d0fcf99518d02463a0",
        "derivationKind": "stake"
      },
      "addressInfo": {
        "isByron": false,
        "isReward": false,
        "isEnterprise": false,
        "isPointer": false,
        "isPaymentScript": false,
        "isStakingScript": false,
        "paymentScriptHash": "",
        "stakingScriptHash": "",
        "isScript": false,
        "kind": "base",
        "isCardano": true,
        "isShelley": true,
        "isBase": true,
        "isPaymentKey": true,
        "isStakingKey": true,
        "paymentKeyHash": "faed34417471f69d47c008e0be00fd6064bb5025c44baac9c2718ed9",
        "stakingKeyHash": "ad03a4ae45b21f50fde67956365cff94db41bc08a2c2862403d8a234",
        "rewardAddress": "stake1uxks8f9wgkep758aueu4vdjul72dksdupz3v9p3yq0v2ydqpd3mre",
        "network": "mainnet",
        "networkId": 1,
        "identity": {
          "scriptHex": "8201818200581cfaed34417471f69d47c008e0be00fd6064bb5025c44baac9c2718ed9",
          "scriptHash": "ddb4f2d0f44774964f57b444995e4a4a750d7b452a7177e739f8e21c",
          "scriptRefHex": "d818582582008201818200581cfaed34417471f69d47c008e0be00fd6064bb5025c44baac9c2718ed9"
        }
      }
    }
  }
}

Important:

"Connection intents" that share basic wallet information to dapps are the default sample script used in all examples here
Connection intents like these are not mandatory: Intent-based dapps may not require to pre-connect in order to work!
For simplicity sake these conection examples does not address:
- signature validation
- challenge validation
- HTTP origin validation
- nor encrypts comms beyond SSL against MITM attacks
A highly secure/private connection intent could be added in the future (let us know your needs!)

CLI Usage

✨ GameChanger Wallet CLI
	Official GameChanger Wallet library and CLI for integrating Cardano in dapps and related workflows.

Usage
	$ gamechanger-cli [network] [action] [subaction] [options]
	$ gamechanger-cli build [-f file] [-o output] [--cwd projectRoot] [--fileUri app:///main.gcscript]
	$ gamechanger-cli validate [-f built.gcscript] [-o report.json]

Networks: 'mainnet' | 'preprod'

Actions:
	'encode': Generate wallet connector artifacts from a valid GCScript.
	'url' : generates a ready-to-use URL dapp connector
	'qr'  : generates a ready-to-use QR code image
	'snippet': Generate ready-to-use dapp/snippet source files from a valid GCScript.
	'html'      : generates a ready-to-use HTML dapp with shared app state and auto-rendered intent argument UI
	'html-zero' : generates a resilient offline-ready zero-dependency HTML dapp
	'button'    : generates an embeddable HTML button snippet with a URL connector
	'express'   : generates a Node.js Express backend that redirects users to the wallet
	'react'     : generates a React dapp with shared app state and auto-rendered intent argument UI
	'build': Build a multi-file GCScript project into one strict JSON GCScript file.
	'file'    : builds a multi-file GCScript project into one final GCScript JSON file
	'project' : supported CLI subaction
	'validate': Validate built strict JSON GCScript and emit a JSON report.
	'file'    : validates a built strict JSON GCScript file against the production language schema
	'project' : supported CLI subaction

Common options:
	--args [gcscript] | -a [gcscript] : Load GCScript from arguments.
	--file [filename] | -f [filename] : Load GCScript from file.
	without --args or --file       : Load GCScript from stdin.

	--outputFile [filename] | -o [filename] : Write generated artifact/report to a file.
	without --outputFile                 : Write generated artifact/report to stdout.

Encoding and wallet URL options:
	--apiVersion [version] | -v [version] : Target API version.
	Valid API versions: '2'

	--encoding [encoding] | -e [encoding] : Target wallet message encoding.
	Valid encodings by API version: {"2":["json-url-lzma","gzip","base64url"]}

	--refAddress [cardanoAddress] | -r [cardanoAddress] : Append ref=<address> to generated wallet URLs and QRs.
	--disableNetworkRouter | -R : Do not append the default networkTag=<network> query parameter.
	--urlPattern [url] | -u [url] : Override the default wallet URL pattern. It must include {gcscript}.

QR options:
	--template [template] | -t [template] : QR predefined style.
	Valid QR templates: 'boxed' | 'printable'. Default: boxed.
	QR output type is inferred from --outputFile extension when it is 'png' | 'svg'. Without --outputFile, PNG is used.

Snippet options:
	--snippetArgs [json] | -A [json] : JSON map of snippet placeholder overrides.
	--snippetArgsFile [filename] : JSON file with snippet placeholder overrides.
	When both are provided, --snippetArgs wins over --snippetArgsFile per object property.
	Use {"defaultIntents":"..."} to override the whole defaultIntents block.

	--serve | -S : Serve HTML snippet outputs on http://localhost:3000.

Build options:
	--cwd [path] | -C [path] : Working directory used by the CLI app:// resolver. Defaults to the current working directory.
	--fileUri [uri] | -U [uri] : Absolute app:// URI identity used by build. Defaults to app:///main.gcscript.
	--allowProtocols [csv] : Build protocol allow-list. Defaults to app.
	--allowedRemoteDomains [csv] : Optional exact or wildcard host allow-list for http(s) build imports.
	--compactOutput : Emit compact strict JSON.
	--noValidate : Disable schema validation during build. Validation is enabled by default.

Validation options:
	--schemaUrl [url] : Override the GCScript JSON schema URL. Defaults to https://wallet.gamechanger.finance/schema/api/v2/index.json.full.
	--hide-warnings : Hide non-blocking validation warnings during build/validate.

	--quiet | -q : Disable non-essential human logs. Generated output still uses stdout when --outputFile is omitted.

POSIX behavior:
	Human help, progress, warnings, validation summaries, and errors are written to stderr.
	Generated artifacts and JSON reports are written to stdout only when --outputFile is omitted.
	Exit codes: encode/snippet/build succeed with 0 and fail non-zero; validate returns 0 only when isValid is true.

Examples

	⭐ GCScript build:
		$ gamechanger-cli build -f ./main.gcscript -o ./dist/built.gcscript
		$ gamechanger-cli build -f ./src/main.gcscript -o ./dist/built.gcscript --cwd . --fileUri app://src/main.gcscript

	⭐ GCScript validation for CI/CD:
		$ gamechanger-cli validate -f ./dist/built.gcscript -o ./dist/validation-report.json
		$ gamechanger-cli validate -f ./dist/built.gcscript >/tmp/report.json

	⭐ URL encoding:
		$ gamechanger-cli mainnet encode url -v 2 -f examples/connect.gcscript
		https://wallet.gamechanger.finance/api/2/run/1-H4sIAAA...?networkTag=mainnet
		$ gamechanger-cli mainnet encode url -v 2 -r addr1... -f examples/connect.gcscript
		https://wallet.gamechanger.finance/api/2/run/1-H4sIAAA...?networkTag=mainnet&ref=addr1...
		$ gamechanger-cli mainnet encode url -v 2 -a '{"title":"Get Address","description":"Do you authorize sharing your address with this dapp?","type":"script","exportAs":"MyData","run":{"address":{"type":"getCurrentAddress"}}}'
		https://wallet.gamechanger.finance/api/2/run/1-H4sIAAA...?networkTag=mainnet

	⭐ QR encoding:
		$ gamechanger-cli mainnet encode qr -v 2 -f examples/connect.gcscript -o examples/qr_output.png
		$ gamechanger-cli mainnet encode qr -e gzip -v 2 -f examples/connect.gcscript -o examples/qr_output.svg

	⭐ Snippet generation:
		$ gamechanger-cli mainnet snippet html -v 2 -S -o examples/htmlDapp.html -f examples/connect.gcscript
		$ gamechanger-cli mainnet snippet html-zero -v 2 -o examples/htmlZeroDapp.html -f examples/connect.gcscript
		$ gamechanger-cli mainnet snippet react -v 2 -o examples/reactDapp.html -f examples/connect.gcscript
		$ gamechanger-cli mainnet snippet html -v 2 -f ./dist/open.gcscript.json --snippetArgsFile ./config/snippet-args.json
		$ gamechanger-cli mainnet snippet html -v 2 -f ./dist/open.gcscript.json --snippetArgsFile ./config/snippet-args.json --snippetArgs '{"title":"Local override"}'

Build protocol resolvers:
	'app://' | 'http://' | 'https://' | 'file://' | 'blob://' | 'gcfs://' | 'ipfs://'
	app:// is the default virtual filesystem resolver in the CLI and resolves from --cwd.
	file:// is unrestricted when explicitly enabled with --allowProtocols.
	http:// and https:// are mutable remote resources and can be restricted with --allowedRemoteDomains.
	blob://, gcfs://, and ipfs:// are available to the library build pipeline when supported by the runtime/protocol handler.

Breaking Changes Notice

Generated code outputs are now much richer and complex than the ones produced over the last years. For improvements and maintainance these may require more internal breaking changes in their internal design, decoupling from the versioning strategy of the actual library. If you need special treatment on outputs let us know or consider forking for your use case.

Resources

License

MIT

Development

pnpm install
pnpm run build
pnpm test

Name		Name	Last commit message	Last commit date
bin		bin
examples		examples
scripts		scripts
src		src
test		test
.eslintrc.cjs		.eslintrc.cjs
.gitignore		.gitignore
.prettierrc		.prettierrc
CHANGELOG.md		CHANGELOG.md
LICENSE		LICENSE
README.md		README.md
package-lock.json		package-lock.json
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
rollup.browser-min.config.js		rollup.browser-min.config.js
rollup.browser.config.js		rollup.browser.config.js
rollup.nodejs.config.js		rollup.nodejs.config.js
rollup.shared.config.mjs		rollup.shared.config.mjs
tsconfig.json		tsconfig.json
tsconfig.types.json		tsconfig.types.json

Navigation Menu

Repository navigation

About

Repository files navigation

GameChanger Wallet Library and CLI

Try it online:

Examples:

Custom examples

CLI/library output examples

Install CLI

Install Library

Import library on your projects:

For importing on html document:

For Node.js / React / Vite / webpack projects:

Distribution targets

Library usage:

Encode dapp intent (dapp -> wallet message):

Snippet customization (html / html-zero / react / button / express)

Build multi-file GCScript projects

Notes:

Validate built GCScript JSON

Decode intent execution results (wallet -> dapp message):

Important:

CLI Usage

Breaking Changes Notice

Resources

License

Development

About

Releases

Packages

Used by

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

GameChanger Wallet Library and CLI

Try it online:

Examples:

Custom examples

CLI/library output examples

Install CLI

Install Library

Import library on your projects:

For importing on html document:

For Node.js / React / Vite / webpack projects:

Distribution targets

Library usage:

Encode dapp intent (dapp -> wallet message):

Snippet customization (html / html-zero / react / button / express)

Build multi-file GCScript projects

Notes:

Validate built GCScript JSON

Decode intent execution results (wallet -> dapp message):

Important:

CLI Usage

Breaking Changes Notice

Resources

License

Development

About

Topics

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages