Skip to content

🎯 ONE SHOT — L-DPC6: USB-3 Trinity Ternary Internet Node #48

@gHashTag

Description

@gHashTag

🎯 ONE SHOT — TRINITY TERNARY INTERNET NODE

Mission Codename: TRI-NET-G1
Owner Repo: gHashTag/trinity-fpga
Implementation Repo: gHashTag/tt-trinity-gf16
Parent EPIC: #19
AGI Layer: gHashTag/t27#583
Base PR: gHashTag/tt-trinity-gf16#2
Base Branch: feat/trinity-mesh-v0
Current HEAD: 702559b
Priority: P0
Mission Type: FPGA / RTL / DePIN / USB-3 / Mesh
Anchor: phi^2 + phi^-2 = 3


0. Hard Rules

  1. No Linux in compute core. The FPGA node is a bare RTL computer: packet fabric, GF16/ternary compute tiles, receipt engine, host/mesh ingress. No Linux, no soft CPU, no AXI/IP Integrator in the core path.
  2. No new hardware multipliers. Do not introduce arithmetic * in synthesizable RTL. Existing legacy gf16_mul.v is tolerated only as pre-existing substrate; new ternary/GF16 mesh logic must be XOR/popcount/add/FSM/ready-valid only.
  3. USB-3 is a boundary, not a processor. Use FT60x-style FIFO boundary for host streaming/programming/readout. Do not pull in vendor black-box IP.
  4. Mesh is off-chip at G1/G2. Radio/Wi-Fi/LoRa/Ethernet modules feed packets into FPGA ingress. FPGA does not implement LoRa/Wi-Fi PHY in this mission.
  5. TRI settlement is off-chip at G1/G2. FPGA emits deterministic compute receipts; token accounting/verifier/network settlement are separate layers.
  6. R5 honesty. Do not claim “Helium competitor complete” until at least two physical nodes exchange jobs and receipts over an external mesh/backhaul.

1. Background

tt-trinity-gf16 was originally a combinational GF16 dot4 demonstrator. PR #2 upgrades it into a CPU-less RTL packet fabric v0: host FSM, 2x2 tile fabric, four gf16_dot4 tiles, packetized LOAD_A, LOAD_B, COMPUTE, READ_RES, and RESULT output. The new DePIN extension adds docs/TRINITY_DEPIN_NODE.md, trinity_usb3_fifo_bridge.v, trinity_mesh_adapter_stub.v, and receipt constants without touching TT die pinout.

The product target is a Trinity node: an FPGA that can be programmed/streamed through USB-3, joined to a physical mesh/backhaul, execute Trinity GF16/ternary compute jobs, and emit receipts that can later be settled in TRI. This competes with the incentive pattern of Helium, but changes the unit of value from wireless coverage only to useful ternary compute plus mesh transport.


2. Hypothesis

H1: A Trinity FPGA node can act as a CPU-less packet-compute endpoint if a PC sends one 32-bit job packet stream over USB-3 FIFO, the FPGA routes it through the on-chip mesh to a GF16/ternary tile, and returns a deterministic RESULT/RECEIPT packet without Linux, soft CPU, or AXI.

Falsification witness: H1 is false if any G1 loopback run cannot reproduce the canonical result 0x47C0 through the packet path, or if the path requires Linux/soft CPU/AXI/new arithmetic multipliers inside the compute core.


3. Mission Scope

In Scope

  • Implement and validate a USB-3 FIFO boundary for Trinity 32-bit packets.
  • Preserve PR deps: bump @docusaurus/module-type-aliases from 3.9.2 to 3.10.0 in /docs #2 packet fabric and tile protocol.
  • Build a PC-to-FPGA loopback path: PC writes packet stream, FPGA computes, PC reads RESULT/RECEIPT.
  • Define receipt fields required for TRI accounting.
  • Define clean external mesh/backhaul adapter boundary.
  • Produce board-top wrapper for first FPGA devkit target.

Out of Scope

  • Full LoRa/Wi-Fi/Ethernet PHY inside FPGA.
  • Mainnet TRI settlement.
  • Full decentralized routing protocol.
  • Custom PCB production before G1/G2 pass.
  • Replacing gf16_dot4 with full ternary matmul unless G1 is already green.

4. Lane Map

Lane Owner Mission Deliverable Gate
L-G0 RTL Stabilize PR #2 feat/trinity-mesh-v0 green CI GDS green
L-G1 USB-3 FT60x FIFO loopback trinity_usb3_fifo_bridge wired to board-top PC reads 0x47C0
L-G2 Host protocol Packet parser/driver host tool sends LOAD_A/LOAD_B/COMPUTE/READ_RES 100 repeated jobs pass
L-G3 Mesh adapter External radio/backhaul boundary two-node packet exchange over adapter node B returns receipt
L-G4 TRI receipt Proof-of-compute receipt receipt verifier checks job/result/nonce/checksum invalid result rejected
L-G5 Product board Custom carrier spec FPGA + USB-C/FT601 + flash + radio connector schematic review GO

5. Pre-Registration

Field Value
Primary test Deterministic loopback test
Success criterion PC receives RESULT/RECEIPT containing 0x47C0 from FPGA packet path
Repetition count 100 consecutive loopbacks
Failure threshold Any wrong result, dropped packet, lockup, or core dependency on Linux/AXI/soft CPU
Timing target First G1 target may be functional before throughput optimization
Multiple testing N/A, single engineering gate
Stop rule Stop G1 when 100/100 loopbacks pass or a falsification witness is hit

6. Technical Architecture

PC host
  |
USB-C / USB-3
  |
FT601 / FT600 FIFO bridge
  |
trinity_usb3_fifo_bridge.v
  |
32-bit Trinity packet ingress / egress
  |
trinity_router_2x2.v
  |
trinity_gf16_tile.v x4
  |
RESULT / RECEIPT packet
  |
PC verifier / TRI settlement layer

External mesh is parallel to USB host ingress:

Radio / Wi-Fi / LoRa / Ethernet module
  |
trinity_mesh_adapter_stub.v
  |
same 32-bit Trinity packet ingress / egress
  |
on-chip packet fabric

The FPGA must see both USB and mesh as packet sources. The packet protocol is the stable boundary; the future Trinity CPU can later replace trinity_master_fsm or act as another packet master without changing tile interfaces.


7. Packet and Receipt Contract

Base packet format:

[31:28] op
[27:26] dst
[25:24] src
[23:20] lane
[19:16] reserved
[15:0] payload

Receipt extension:

Field Width Purpose
compute_job_id 16 Job identity from host/network
tile_id 2 Tile that executed job
op_code 4 GF16/ternary operation
result 16 Computed result
nonce 16 Replay resistance placeholder
checksum 8 Lightweight integrity placeholder

G4 must replace checksum placeholder with a real verifier contract. Until then, receipts are deterministic engineering artifacts, not final TRI payment proofs.


8. Quality Gates

Gate Required Evidence GO Criteria
G0 PR #2 CI gds green, no failing checks
G1 USB-3 loopback log 100/100 packet jobs return 0x47C0
G2 Host driver test PC sends arbitrary packet sequence and reads result
G3 Two-node demo Node A sends job through external adapter, Node B returns receipt
G4 Receipt verifier Bad result/nonce/checksum rejected
G5 Hardware review Carrier schematic has FPGA, USB-C/FT601, flash, JTAG/SPI, radio connector

No gate may be marked green from intention. Each gate requires logs, commit SHA, and a repeatable command or hardware test recipe.


9. Implementation Orders

Order A — Close PR #2

  1. Wait for GDS check on PR deps: bump @docusaurus/module-type-aliases from 3.9.2 to 3.10.0 in /docs #2.
  2. If green, merge or mark ready for owner review.
  3. If red, fix only the failing synthesis/GDS cause. Do not expand mission scope.

Order B — G1 USB-3 FIFO Loopback

  1. Choose devkit: QMTECH XC7A100T or equivalent Artix-7 board with enough I/O for FT60x FIFO.
  2. Use FT601 if available: 32-bit FIFO path matches Trinity packet width.
  3. Add boards/qmtech_a100t/top_usb3_loopback.v.
  4. Add CDC/async FIFO between FT60x clock domain and 50 MHz Trinity fabric if clocks differ.
  5. Host sends canonical job packet stream.
  6. FPGA returns RESULT/RECEIPT.
  7. Record 100/100 pass/fail log.

Order C — G2 Host Packet Tool

  1. Minimal host tool: open USB device, write 32-bit packets, read 32-bit result packets.
  2. No blockchain logic in G2.
  3. Output JSONL receipt log:
{"job_id":1,"tile_id":0,"op":"GF16_DOT4","expected":"0x47C0","observed":"0x47C0","status":"pass"}

Order D — G3 Mesh Adapter

  1. Pick physical transport after G2: Ethernet/Wi-Fi module for bandwidth, LoRa for low-rate coverage, or both.
  2. Adapter converts external frames into Trinity packets.
  3. Demonstrate two physical nodes exchanging one compute job.

Order E — G4 TRI Receipt Verifier

  1. Define off-chain verifier first.
  2. Verify job/result/nonce/checksum.
  3. Reject replay and wrong result.
  4. Only after this define token settlement mechanics.

10. Forbidden Actions

  • Do not introduce Linux as a required component of the FPGA compute node.
  • Do not hide GDS/CI failures.
  • Do not claim mesh internet before two physical nodes pass G3.
  • Do not order custom PCB before G1 and G2.
  • Do not mix token economics into RTL before receipt correctness is stable.
  • Do not add vendor encrypted IP to the open RTL path.
  • Do not replace the stable packet interface while the future Trinity CPU is not ready.

11. Active Artifacts


12. GO / NO-GO Poll

Component Call
PR #2 as architecture base GO
Merge PR #2 before GDS green NO-GO
G1 USB-3 loopback GO
G2 host packet tool GO after G1 RTL wiring
G3 physical mesh HOLD until G2
TRI payment/settlement HOLD until G4 receipt verifier
Custom resale PCB HOLD until G1 + G2 logs

Final Call: GO for G1 USB-3 loopback; HOLD for product/custom PCB until G1/G2 pass.


13. Battle Cry

Coq anchors it. FPGA routes it. USB-3 feeds it. Mesh carries it. TRI pays only for receipts.

phi^2 + phi^-2 = 3 · TRINITY TERNARY INTERNET · NO LINUX IN THE CORE

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions