AxonServed

Event Re-added v101 → v127, v133 → v219, v233 → v265, v273 → v277, v290 → current #28

Emitted when a neuron updates their axon server information.

Useful for: minersvalidatorssubnet ownersdevelopers

The Big Picture

An axon is your miner's public API endpoint - the address validators use to send queries. When you register or move your miner, you 'serve' your axon to publish this information on-chain. Without a valid axon, validators can't reach you and you can't earn. This event confirms your endpoint is published and discoverable.

Why This Matters

Validators need to know where to send queries. Your axon contains your IP address and port. If it's wrong or outdated, validators can't reach your miner, and you get zero score. This event confirms your miner is 'visible' to the network.

Example Scenario

You start a new miner on subnet 1 at IP 203.0.113.50:8091. After registering, you call serve_axon. AxonServed fires with your hotkey, subnet 1, and network details. Now validators on subnet 1 can query your miner. Check your axon periodically - if your IP changes, you need to serve again.

Common Questions

How often should I update my axon?: Only when your endpoint changes (new IP, port, or server). There's a rate limit, so you can't spam updates. Most miners serve once and only update if they move servers.
What if validators still can't reach me?: Check that your axon IP is publicly accessible, firewall allows the port, and your miner software is actually running. AxonServed just publishes the address - you're responsible for the endpoint being reachable.
Does AxonServed mean I'm earning?: It means validators CAN reach you. Whether you earn depends on your responses. If your miner returns good results, you'll get positive weights and emissions.

Use Cases

Verify your miner's endpoint was published
Track when neurons come online or change IPs
Monitor miner availability on a subnet
Build subnet health dashboards

How to Use This Event

→ Subscribe to your own hotkey to confirm axon updates
→ Monitor all axon changes on a subnet for health tracking
→ Build maps of network topology from axon data

From Chain Metadata

the axon server information is added to the network.

Triggers

Emitted by

serve_axon serve_axon_tls

Preconditions

Caller is registered on the subnet
Valid IP/port provided
Serving not rate limited

Effects

Storage Modified

Axons LastTxBlock NeuronCertificates

Postconditions

Axons storage updated with new endpoint

Side Effects

Other neurons can discover this endpoint
Validator can send requests to this axon

Event Data

#	Name	Type	Description
0	arg0	u16	Event field #0 (u16)
1	arg1	AccountId	Event field #1 (AccountId) (hex -> SS58)

Code Examples

import { ApiPromise, WsProvider } from "@polkadot/api";
import { stringCamelCase } from "@polkadot/util";

const provider = new WsProvider("wss://entrypoint-finney.opentensor.ai:443");
const api = await ApiPromise.create({ provider });

// Subscribe to AxonServed events
api.query.system.events((events) => {
  events
    .filter(({ event }) =>
      event.section === stringCamelCase("SubtensorModule") &&
      event.method === "AxonServed"
    )
    .forEach(({ event }) => {
      console.log("AxonServed:", event.data.toHuman());
    });
});

On-Chain Activity

Emission Frequency

●●●●○○ Significant 1M–5M emissions

Major features with millions of emissions

#18 most emitted event

As of block 7,429,232

Version History

Version:

v101 block 1 2 args

v133 block 1,404,224 2 args

v233 block 4,920,350 2 args

v273 block 5,659,032 2 args

v290 block 5,947,548 2 args Current

Runtime Info

View Source

Pallet Index: 7
Event Index: 28
First Version: v101
Current Version: v393

Back to SubtensorModule Events