wikis / Robinhood Chain / README.md view as markdown report a mistake

LLM Wiki

updated: 2026-09-10

CoversRobinhood Chain (chain ID 4663) as documented on 2026-09-09: connecting and network config, gas, transaction finality, differences from Ethereum, Stock Tokens and their legal structure as tokenised debt securities issued by Robinhood Assets (Jersey) Limited, building against them, the stock-token APIs, Chainlink price feeds and the Total Return Value formula, UI multipliers and corporate-action handling, protocol and token contracts, deploying, account abstraction, bridging, cross-chain messaging, data streams, running a node, governance, the Uniswap v4 deployment on 4663, and the Doppler launch protocol. Also documents where the official docs contradict each other or their own Terms of Service.

Not coveredPer-ticker Stock Token contract addresses and Chainlink feed proxy addresses — both tables render client-side and are deliberately NOT reproduced here; resolve them from the live sources. Any claim about how many tickers have feeds. Whether an on-chain role registry, blocklist or proxy-admin power exists beyond what the docs disclose. The chain's launch date and upgrade history, which no source states. Doppler behavior not explicitly scoped to 4663 — its docs are multi-chain and its SDK examples target Base. Prices, market data, token valuations, and anything resembling trading or investment advice.

Current as of2026-09-09

🤖 Agent access: /wiki/robinhood-chain/llms.txt /wiki/robinhood-chain/llms-full.txt /wiki/robinhood-chain/index.json

An open-source template for building LLM-powered knowledge bases, following Andrej Karpathy's "LLM Wiki" pattern.

You provide raw sources. The LLM reads them, writes structured wiki pages, cross-links everything, and maintains it over time. You never edit the wiki directly — you curate sources and ask questions.

How It Works

The system has three layers:

raw/              Sources you collect (articles, transcripts, notes, PDFs)
wiki/             LLM-written & maintained pages (summaries, concepts, entities, syntheses)
CLAUDE.md         Schema that tells the LLM how to structure everything

Three operations drive the workflow:

Operation	Trigger	What happens
Ingest	"ingest raw/my-source.txt"	LLM reads the source, creates a summary page, creates/updates concept and entity pages, adds cross-links, updates the index and log
Query	Ask any question	LLM searches the wiki, synthesizes an answer with citations, optionally creates a synthesis page for novel insights
Lint	"lint" or "health check"	LLM audits all pages for orphans, contradictions, missing links, incomplete sections, and low-confidence claims — fixes what it can, reports the rest

Quick Start

Clone this repo

git clone https://github.com/YOUR_USERNAME/llm-wiki.git my-knowledge-base
cd my-knowledge-base

Customize CLAUDE.md for your domain
- Update the Purpose section with your topic
- Replace the placeholder tagging taxonomy with your own categories
- Adjust confidence level descriptions if needed
- Everything else (workflows, page formats, linking rules) works as-is
Drop sources into raw/
- Text files, transcripts, articles, notes — any plain text
- These are immutable once added; the LLM never modifies them
Tell the LLM to ingest
```
ingest raw/my-first-source.txt
```
The LLM will create summary pages, concept pages, entity pages, cross-links, and update the index.
Ask questions
```
What are the key differences between X and Y?
```
The LLM answers from the wiki, citing specific pages.
Run health checks
```
lint
```
The LLM audits the wiki and fixes issues.

Directory Structure

.
├── CLAUDE.md                      # Schema — the LLM's instructions
├── raw/                           # Your source documents (immutable)
└── wiki/
    ├── index.md                   # Master catalog of all pages
    ├── log.md                     # Append-only activity log
    ├── dashboard.md               # Dataview dashboard (Obsidian)
    ├── analytics.md               # Charts View analytics (Obsidian)
    ├── flashcards.md              # Spaced repetition cards
    ├── summaries/                 # One page per source document
    ├── concepts/                  # Concept and framework pages
    ├── entities/                  # People, tools, organizations, etc.
    ├── syntheses/                 # Cross-cutting analyses and comparisons
    ├── journal/                   # Research/session journal entries
    │   └── template.md            # Journal entry template
    └── presentations/             # Marp slide decks

Enhancements

This template includes several extras beyond the core wiki pattern:

Dataview Dashboard (`wiki/dashboard.md`)

Live queries that surface low-confidence pages, recent updates, concepts by tag, and pages with the most sources. Requires the Dataview Obsidian plugin.

Charts View Analytics (`wiki/analytics.md`)

Visual analytics with pie charts, bar charts, and word clouds. Requires the Charts View Obsidian plugin.

Mermaid Diagrams

Use Mermaid code blocks in any wiki page to create flowcharts, sequence diagrams, or concept maps. Native support in Obsidian and GitHub.

Marp Slides (`wiki/presentations/`)

Create slide decks from markdown using Marp. Drop presentation files in this directory.

Research Journal (`wiki/journal/`)

Track your research sessions, experiments, or applied work with the included template. The LLM can reference journal entries when answering queries.

Spaced Repetition (`wiki/flashcards.md`)

Flashcards in the format used by the Spaced Repetition Obsidian plugin. Ask the LLM to generate flashcards from any wiki page.

MCP Server

This repo works with Claude Code's MCP server capabilities. Point an MCP-compatible client at this repo and the LLM can read/write the wiki programmatically.

Customizing for Your Domain

The schema in CLAUDE.md is domain-agnostic. To adapt it:

Purpose — Describe your knowledge domain in one paragraph
Tagging taxonomy — Replace placeholder categories with your own (e.g., for a cooking KB: cuisine, technique, ingredient, equipment)
Confidence levels — Adjust the descriptions to match your domain's evidence standards
Entity types — Update the entity page description to match what entities mean in your domain (people, tools, companies, etc.)
Journal template — Customize wiki/journal/template.md for your workflow

Everything else — page format, linking conventions, workflows, rules — is universal and works across domains.

Example Domains

This template works for any knowledge-intensive topic:

Research notes — papers, experiments, methodologies
Book analysis — themes, characters, author techniques
Competitive analysis — companies, products, market trends
Course notes — lectures, readings, key concepts
Personal development — frameworks, habits, book summaries
Technical documentation — APIs, architectures, design patterns
Hobby deep-dives — any subject you want to master

License

MIT