camfairchild

# The MIT License (MIT)
# Copyright © 2023 Yuma Rao
# Copyright © 2023 Opentensor Foundation
# Copyright © 2023 Cameron Fairchild

# Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
# documentation files (the “Software”), to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,
# and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

camfairchild

### Keybase proof

I hereby claim:

  * I am camfairchild on github.
  * I am camfairchild (https://keybase.io/camfairchild) on keybase.
  * I have a public key ASAK07Ct_ShI2s8YrZ9Tf6ekQIfeiON9CrFOTt47D1aLoAo

To claim this, I am signing this object:

camfairchild

Bittensor IP Watcher and Axon Updater Script

Background and Motivation

Bittensor has model-serving peers (Servers) and model-validating peers (Validators).
A large component of the protocol involves Validators sending requests to Servers, querying their models, and validating their intelligence.
Therefore, model-serving peers must have a port open to the internet for access by Validators.

The Problem

Since model-serving peers have open ports, they must also filter traffic to only serve valid Validators, otherwise they risk wasting time and compute on invalid requests.
This leaves us with an issue. How do we verify a request is coming from a Validator?

Current Approach

camfairchild

Setup Talisman and TensorWallet for Bittensor (TAO)

Get Extension

https://talisman.xyz/ to get the extension on Chrome or Firefox

Add Metadata

https://polkadot.js.org/apps/?rpc=wss://entrypoint-finney.opentensor.ai:443#/settings/metadata
or
https://polkadot.js.org/apps/ > Network Switch Menu (Top-Left) > Live Networks > Bittensor > Switch

Approve prompts from extension