Kinetic in Production

Are You Ready?

Before moving your application onto the Mainnet, it's good practice to make sure you're able to transact on the Devnet. If it's all working how you want, then let's get going!

Connecting to Mainnet

When you set up your Kinetic Client using one of our SDKs, you need to set your environment.

This can be either devnet or mainnet. For Production, you should choose mainnet.

For example, here's how it works with the TypeScript SDK:

const clientOptions = {
  environment: 'mainnet', // the name of your mainnet environment as defined in your Kinetic instance
  index: 1, // your App Index
  endpoint: 'https://your_kinetic_instance', // kinetic instance endpoint
}

const kineticClient = await KineticSdk.setup(clientOptions)

You'll notice in the example above, you have to pass in an endpoint when you set up the Kinetic Client.
This setting gives us some options in the ways we can connect to Kinetic on mainnet:

Self Hosted

Host and manage your own Kinetic instance for maximum power.

Kinetic As A Service

Connect to a Kinetic Service hosted by a 3rd party.

Self Hosted

For larger scale apps or those looking for more control.

  • Get insights into your transactions
  • Get insights into your hot-wallet usage
  • Configure multiple mints (e.g. other tokens, nfts, etc)
  • Stay on a specific Kinetic version
  • Unlimited log retention
  • Configure multiple hot-wallets
  • Customisable (Open Source)

Connecting To Your Own Kinetic Instance

Point to mainnet as your environment and set your endpoint to where you've deployed your own Kinetic Instance. E.g. TypeScript SDK:

const clientOptions = {
  environment: 'devnet', // the name of your environment, e.g. devnet, mainnet
  index: 1, // your App Index
  endpoint: 'https://your_kinetic_instance', // your kinetic server address
}

const kineticClient = await KineticSdk.setup(clientOptions)

Your endpoint can be your own deployed Kinetic instance or a locally running instance.

Host Kinetic

Learn how to host your own Kinetic instance

Run Kinetic Locally

Develop with Kinetic on your own machine

Configuration

Configure Kinetic

Set your Environment Variables and use Kinetic Manager to configure and manage your Kinetic instance.

Kinetic As A Service

If you want to connect to Kinetic on mainnet without running your own Kinetic server, then Kinetic As A Service is the way forward.

Kinecting to Kinetic As A Service

Instantiate your Kinetic Client via your SDK of choice with the endpoint set to the endpoint provided by your Kinetic As A Service provider. E.g. TypeScript SDK:

const clientOptions = {
  environment: 'mainnet', // the name of your environment, get this from your KAAS provider
  index: 1, // your App Index
  endpoint: 'kinetic_as_a_service_endpoint', // get this from your KAAS provider
}

const kineticClient = await KineticSdk.setup(clientOptions)

Kinetic As A Service Providers

Kinetic As A Service

Connect to a Kinetic Service hosted by a 3rd party.

That's it!

What If I Get Stuck?

Pop into the kinetic-hosting channel on Discord and we'll give you a hand.

Getting Help

Stuck? No problem, we have an amazing community waiting to help out.

Developer Discord

Join our fantastic developer community.


Was this page helpful to you?
Provide feedback