What Is Kilt Mashnet and How Do You Connect to It?

Quick Answer: What Is Kilt Mashnet?

Kilt Mashnet is the production mainnet of the Kilt blockchain, a protocol built specifically for decentralized identity (DID) and verifiable credentials. Unlike general-purpose smart contract chains, Kilt focuses on enabling self-sovereign identity: users hold their own credentials, and verifiers can check them without relying on a central authority.

Mashnet is the network where real KILT tokens are used, and where decentralized identifiers (DIDs) are anchored. If you are building an application that issues, holds, or verifies credentials, Mashnet is the network you will target for production deployments.

For developers, the practical question is usually: how do I connect my application to Mashnet? This article walks through the chain settings, RPC endpoint options, and configuration examples so you can move from testnet to mainnet with confidence.

Decision Guide: Which Endpoint Should You Use?

Before you start coding, decide how you will access Mashnet. Your choice depends on your traffic patterns, reliability needs, and whether you want to manage infrastructure.

If you are unsure, start with a public endpoint for development, then move to a managed provider when you approach production. OnFinality offers RPC pricing that scales with usage, and you can check supported RPC networks to confirm Mashnet availability.

Kilt Mashnet Chain Settings at a Glance

To connect to Mashnet, you need the correct network parameters. The table below summarizes the key settings.

Note that Kilt is a Substrate-based chain, so it does not use an EVM-style chain ID. Instead, you connect via WebSocket or HTTP using the wss:// or https:// protocol.

For the most current public endpoint, refer to the official Kilt Mashnet network page on OnFinality.

Connecting to Mashnet: Wallet and dApp Configuration

Most wallets and dApps that support Kilt use the Polkadot.js browser extension or the Kilt Wallet. To add Mashnet as a custom network, you typically need the WebSocket endpoint.

Here is an example of adding Mashnet to the Polkadot.js extension:

{
  "networkName": "Kilt Mashnet",
  "endpoint": "wss://kilt-rpc.dwellir.com",
  "tokenSymbol": "KILT",
  "tokenDecimals": 15
}

If you are using a library like @polkadot/api, you can connect programmatically:

const { ApiPromise, WsProvider } = require('@polkadot/api');

const provider = new WsProvider('wss://kilt-rpc.dwellir.com');
const api = await ApiPromise.create({ provider });

console.log('Connected to Kilt Mashnet');

For production applications, consider using a managed RPC provider that offers both WebSocket and HTTP endpoints, load balancing, and failover. OnFinality's dedicated node service can provide a private endpoint with higher throughput.

Understanding Kilt's Unique Features

Kilt is not a general-purpose blockchain; it is optimized for identity. This affects how you interact with the network.

• DIDs: Decentralized identifiers are stored on-chain. Each DID has a public key and associated service endpoints.
• Credentials: Verifiable credentials are issued off-chain but anchored on-chain via attestations.
• Attestation: Attesters verify claims and create on-chain attestations that can be revoked.

When building on Mashnet, you will likely use the Kilt SDK, which abstracts many of these complexities. The SDK provides methods for creating DIDs, issuing credentials, and verifying them.

RPC Methods and Common Use Cases

Kilt exposes standard Substrate RPC methods, plus some custom ones for identity operations. Here are a few common ones:

• chain_getBlock – Get a block by hash or number.
• state_getStorage – Read a storage value.
• kiltapi – Custom methods for DID and attestation queries.

For example, to query the current block number using curl:

curl -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"chain_getHeader","params":[],"id":1}' https://kilt-rpc.dwellir.com

This returns the latest block header, which you can use to verify network sync.

Common Pitfalls and Troubleshooting

When connecting to Mashnet, developers often run into a few issues:

• Wrong endpoint: Using a testnet endpoint (Peregrine) instead of mainnet. Double-check the URL.
• WebSocket vs HTTP: Some tools require WebSocket for subscriptions. If you see connection errors, try the wss:// endpoint.
• Token decimals: KILT uses 15 decimals, not 18. Incorrect decimals can cause display errors in wallets.
• Rate limiting: Public endpoints often have rate limits. If you get 429 errors, consider a managed provider.

If you encounter issues, first verify your endpoint and network settings. Then check the Kilt documentation or community channels. For RPC-specific problems, OnFinality's RPC troubleshooting guide may help.

Key Takeaways

• Kilt Mashnet is the mainnet for Kilt's decentralized identity protocol.
• Use the correct WebSocket endpoint and token decimals (15) when configuring wallets or dApps.
• For production, evaluate managed RPC providers like OnFinality to handle reliability and scaling.
• Understand Kilt's unique features (DIDs, credentials, attestations) to build effectively.

Frequently Asked Questions

What is the difference between Kilt Mashnet and Peregrine?

Mashnet is the production mainnet with real KILT tokens, while Peregrine is the testnet for development. They have different endpoints and token values.

How do I get KILT tokens for testing?

You can get test KILT from the Peregrine faucet, but for mainnet you need to purchase KILT from exchanges.

Can I use Ethereum tools with Kilt?

No, Kilt is a Substrate-based chain, so you need tools that support Substrate, such as Polkadot.js or the Kilt SDK.

Does OnFinality support Kilt Mashnet?

Yes, OnFinality provides RPC endpoints for Kilt Mashnet. Check the network page for details.