๐Ÿ”ท
Locentra OS
๐Ÿ”ท
Locentra OS
  • ๐Ÿง  Introduction
  • โš™๏ธ Features
  • ๐Ÿ›  Under The Hood
  • ๐Ÿงฉ Installation
  • ๐Ÿš€ Usage
  • ๐Ÿงฎ CLI Commands
  • ๐Ÿ”Œ API Reference
  • ๐Ÿค– Agents System
  • ๐Ÿง  Semantic Memory
  • ๐ŸŽ“ Training & Fine-Tuning
  • ๐Ÿ” $LOCENTRA Token Access
  • ๐Ÿ— System Architecture
  • ๐Ÿงฉ Extending the System
  • ๐Ÿงช Testing & Quality Assurance
  • ๐Ÿ“„ License & Open Source
Powered by GitBook
On this page

๐Ÿ” $LOCENTRA Token Access

Itโ€™s not just another governance token. $LOCENTRA is the control surface for Locentra OS. It decides what agents you can launch, how far your model can learn, and how much bandwidth you get on decentralized compute rails.

Itโ€™s infrastructure powerโ€”measured in tokens.


๐Ÿงญ What It Enables

Holding $LOCENTRA unlocks three core pillars of the Locentra OS runtime:

  1. Feature Access Access private models, memory tiers, and advanced tools.

  2. Agent Deployment Run automated training agents, evaluators, and vector optimizers.

  3. Governance Participation (future) Influence the global intelligence layer via staking, data curation, and prompt voting.


๐Ÿ”“ Access Tiers (Wallet-Gated)

Your token balance determines what you can do. The more $LOCENTRA you hold, the deeper you go:

Token Balance
Access Tier
Capabilities

0โ€“9,999

Basic

Inference, memory view, prompt optimizer

10kโ€“49,999

Extended

CLI training, agent visibility, logs

50k+

Operator

Launch agents, retrain live, stream metrics

100k+

Protocol Builder

Full system control, vote, stake + share models

Wallets are checked via Solana RPC calls from the backend. Authentication handled via signature challenge in the frontend (Phantom, Backpack).

You can configure access logic in:

  • core/config.py

  • core/registry.py

  • services/user_service.py


โš™๏ธ How It Works (Technical Flow)

flowchart TD
    A[User connects wallet] --> B[Frontend requests $LOCENTRA balance]
    B --> C[Backend verifies via Solana RPC]
    C --> D[Tier is resolved based on config]
    D --> E[Access flag injected into user session]

Everything is stateless and scoped per session.

Example: A user with 50k $LOCENTRA can launch an AutoTrainer agent via CLI or UI, but cannot modify core registry keys.


๐Ÿงช Real-World Example

Letโ€™s say you're building a Twitter agent that listens to mentions of your token and retrains the model accordingly.

python cli/agent_launch.py --target "token_mentions"

Requirements:

  • โœ… Wallet with 50k+ $LOCENTRA

  • โœ… Access to agent modules

  • โœ… AgentRunner CLI available

  • โœ… Token verified on-chain at runtime

This structure keeps LLM deployment trustless, modular, and wallet-native.


๐Ÿ“ˆ Upcoming: Staking System

Weโ€™re building a staking mechanism where:

  • You stake $LOCENTRA to unlock bandwidth on shared LLMs

  • Vote on:

    • Public dataset inclusion

    • Prompt libraries

    • New agent behaviors

  • Earn protocol rewards via:

    • Training contribution

    • Evaluation feedback

    • Vector memory curation

Itโ€™s not about speculation. Itโ€™s about bandwidth, ownership, and modular AI power.

Previous๐ŸŽ“ Training & Fine-TuningNext๐Ÿ— System Architecture

Last updated 1 day ago

Page cover image