From a75e50b4ee9469ede9fc3a0f65cff52918b3ffb7 Mon Sep 17 00:00:00 2001 From: Giovanny Amador <219895655+Eras256@users.noreply.github.com> Date: Wed, 11 Nov 2026 20:45:12 -0600 Subject: [PATCH] chore: remove stale and internal files from the public mirror - apps/web/app/pitch/page.tsx: the source already retired this deck to a redirect to /docs; the mirror still had the old page, including an internal planning comment. Same 6-line redirect as the source now. - apps/web/public/legal/privacy-notice-draft-v2.md: an unpublished legal draft pending review; removed from the source, not meant for the public tree. - skills-lock.json: a local AI-tooling lockfile, not part of the product. - NIRIUM_TECHNICAL_PAPER.md: section 3.1 listed the pre-9-Nov testnet vault CBTWMZCG...; now the source-verified CDMFURE6..., with a dated note, plus a note that the paper's figures are as of Jul-Oct 2026. - SDKs.md, MCP_INTEGRATION_GUIDE.md: marked as historical (SDK 0.5.0, MCP v0.4.0) with links to the maintained READMEs and current versions. - CONTRIBUTING.md: SDK versions 0.19.0 / 0.11.1. Co-Authored-By: Claude Opus 5.5 --- CONTRIBUTING.md | 4 +- MCP_INTEGRATION_GUIDE.md | 2 + NIRIUM_TECHNICAL_PAPER.md | 6 +- SDKs.md | 2 + apps/web/app/pitch/page.tsx | 419 +----------------- .../public/legal/privacy-notice-draft-v2.md | 171 ------- skills-lock.json | 79 ---- 7 files changed, 14 insertions(+), 669 deletions(-) delete mode 100644 apps/web/public/legal/privacy-notice-draft-v2.md delete mode 100644 skills-lock.json diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5cbac579..f4db3a18 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -47,8 +47,8 @@ pnpm dev ``` nirium-core/ ├── apps/web/ → Next.js 15 Dashboard - 27 routes, i18n (EN/ES) -├── packages/sdk/ → TypeScript SDK v0.16.1 (npm: nirium) -├── packages/sdk-python/ → Python SDK v0.11.0 (PyPI: nirium) +├── packages/sdk/ → TypeScript SDK v0.19.0 (npm: nirium) +├── packages/sdk-python/ → Python SDK v0.11.1 (PyPI: nirium) ├── nirium-soroban-contracts/ → Soroban smart contracts (Rust): NiriumVault + NiriumProtocol, both deployed on testnet └── .github/workflows/ → CI, release, security-gate ``` diff --git a/MCP_INTEGRATION_GUIDE.md b/MCP_INTEGRATION_GUIDE.md index bb0970ac..af707701 100644 --- a/MCP_INTEGRATION_GUIDE.md +++ b/MCP_INTEGRATION_GUIDE.md @@ -1,5 +1,7 @@ # Nirium MCP Server - Integration Guide v0.4.0 +> **Historical document (MCP v0.4.0, April 2026), kept for reference.** The maintained guide is the [`nirium-mcp` README](https://github.com/nirium-protocol/nirium/tree/main/packages/mcp) in nirium-protocol/nirium, with the current tool list. Current release, checked on npm on 11 Nov 2026: `nirium-mcp` 0.6.4. + > Model Context Protocol server for Nirium Protocol. > Exposes 11 tools to any MCP-compatible AI: Claude, GPT, Cursor, VS Code Copilot. > Published on npm as [`nirium-mcp`](https://www.npmjs.com/package/nirium-mcp). diff --git a/NIRIUM_TECHNICAL_PAPER.md b/NIRIUM_TECHNICAL_PAPER.md index c4f7c9aa..662aee47 100644 --- a/NIRIUM_TECHNICAL_PAPER.md +++ b/NIRIUM_TECHNICAL_PAPER.md @@ -2,6 +2,8 @@ > Institutional DeFi Infrastructure Powered by Autonomous Agents on Stellar/Soroban **Version:** 2.5 - July 2026 (Updated Jul 13, 2026 - dual-network execution nodes, self-service API keys, non-custodial Payouts) + +> **Update, 2026-11-11:** figures in this paper (versions, endpoint counts) are as of its July-October 2026 revisions. The testnet NiriumVault is now the source-verified build `CDMFURE6…` (see section 3.1). Current status and evidence: [README](README.md) and [EVIDENCE.md](https://github.com/nirium-protocol/nirium/blob/main/EVIDENCE.md). **Author:** Nirium Protocol Team **Network:** Stellar Testnet (NiriumVault treasury, audit-gated) + Mainnet (receive-only execution nodes, early access) **Contact:** niriumprotocol@gmail.com @@ -54,8 +56,8 @@ The LLM layer advises. The contract decides. A compromised LLM cannot drain fund ### 3.1 NiriumVault - Primary Execution Contract -**Contract ID:** `CBTWMZCG3P72EHFAQ4ZLSEBIOFYJC244H5J6DHZIJ56FHFWJ2CFAWSZU` -**Active Vault:** ID 1 (testnet, agent delegated) +**Contract ID:** `CDMFURE6MYROTA2A6DLD4TN2S4QTN64L2FZ2I2RY2AREONX6DUQOI2S2` (testnet, source-verified on Stellar Expert, 9 Nov 2026) +**Update, 2026-11-11:** this section previously listed `CBTWMZCG3P72EHFAQ4ZLSEBIOFYJC244H5J6DHZIJ56FHFWJ2CFAWSZU` with "Active Vault: ID 1". That was the deployment nirium.xyz used until 9 Nov 2026; the site now uses the source-verified build above. Core functions: - `create_vault(owner, asset, name, xlm_address)` - deploys vault, charges 12.5 XLM diff --git a/SDKs.md b/SDKs.md index 9c5753b6..a1bad3ed 100644 --- a/SDKs.md +++ b/SDKs.md @@ -1,5 +1,7 @@ # Nirium Protocol - Official SDK Documentation +> **Historical document (SDK 0.5.0, spring 2026), kept for reference.** The maintained SDK docs are the package READMEs in [nirium-protocol/nirium](https://github.com/nirium-protocol/nirium): TypeScript `nirium` ([packages/sdk](https://github.com/nirium-protocol/nirium/tree/main/packages/sdk)) and Python `nirium` ([packages/sdk-python](https://github.com/nirium-protocol/nirium/tree/main/packages/sdk-python)). Current releases, checked on npm and PyPI on 11 Nov 2026: `nirium` 0.19.0 (npm) and `nirium` 0.11.1 (PyPI). + **Version:** 0.5.0 **Packages:** `nirium` on npm · `nirium` on PyPI **API Base:** `https://nirium-agent.fly.dev` diff --git a/apps/web/app/pitch/page.tsx b/apps/web/app/pitch/page.tsx index d067f8b2..6a4bdc19 100644 --- a/apps/web/app/pitch/page.tsx +++ b/apps/web/app/pitch/page.tsx @@ -1,417 +1,6 @@ -/** Nirium — SCF Build Award readiness dossier (nirium.xyz/pitch) - * Slide-deck format (vertical stack of numbered cards), same pattern as - * kumply.xyz/pitch — no carousel JS, just a scrollable sequence of - * self-contained slides, one idea per card. - * - * English-only, standalone from the i18n dictionaries on purpose: this page - * is written for one audience (SCF panel reviewers and third-party - * diligence), not general marketing copy. Every claim links to a primary - * source — a Stellar Expert tx, a GitHub commit/PR, an npm/PyPI package - * page — so a reviewer never has to take our word for anything. - * - * Framing note: Nirium is not an active SCF submission right now (three - * prior prescreen rejections put it on a timeout). This deck is a readiness - * dossier, structured against SCF's real Build Award panel-review criteria - * (verified live against stellar.gitbook.io/scf-handbook), for whenever - * that timeout clears — never worded as "under review" or "submitted." - */ -'use client'; +import { redirect } from "next/navigation"; -import Link from "next/link"; -import { - ArrowUpRight, CheckCircle2, ShieldCheck, GitBranch, Package, - Layers, ExternalLink, Hash, AlertTriangle, ChevronRight -} from "lucide-react"; -import MinimalNav from "@/components/layout/MinimalNav"; -import SnapshotBanner from "@/components/shared/SnapshotBanner"; - -const TOTAL_SLIDES = 13; - -function Slide({ n, eyebrow, title, children }: { n: number; eyebrow: string; title?: string; children: React.ReactNode }) { - return ( -
-
- - {eyebrow} - - - {String(n).padStart(2, "0")} / {TOTAL_SLIDES} - -
- {title && ( -

{title}

- )} - {children} -
- ); -} - -function EvidenceLink({ href, children }: { href: string; children: React.ReactNode }) { - return ( - - {children} - - - ); -} - -function Card({ children, className = "" }: { children: React.ReactNode; className?: string }) { - return ( -
- {children} -
- ); -} - -const rebalanceTxs = [ - { hash: "b7bf6d7079aa128081ac2a5091cbff2da2b1e9f2157232209cf03eab00f840a9", time: "01:54:25 UTC", amount: "0.9999999 CETES" }, - { hash: "9f0e7e03cf3f17655b7e1b755c6a3fb5e65c499835424e440e601ecc8b68f033", time: "02:02:59 UTC", amount: "0.9999999 CETES" }, - { hash: "d8bec2b44a0b053d45f843aed21f87e217a2fe87d2761c1e2d3b04318f6330b1", time: "02:21:07 UTC", amount: "0.9999998 CETES" }, - { hash: "ccae5347739e1f65d319f4ce4c2b586661365ffc919e572a758fd2e11a9b7f45", time: "02:29:05 UTC", amount: "0.9999998 CETES" }, -]; - -const mcpToolGroups = [ - { tier: "Free", count: 10 }, - { tier: "Authenticated", count: 9 }, - { tier: "Info", count: 1 }, - { tier: "Paid — x402", count: 3 }, - { tier: "Paid — MPP", count: 2 }, -]; - -const packages = [ - { name: "nirium (npm)", version: "0.12.0", url: "https://www.npmjs.com/package/nirium" }, - { name: "nirium (PyPI)", version: "0.9.0", url: "https://pypi.org/project/nirium/" }, - { name: "nirium-cli (npm)", version: "1.0.5", url: "https://www.npmjs.com/package/nirium-cli" }, - { name: "nirium-mcp (npm)", version: "0.6.0", url: "https://www.npmjs.com/package/nirium-mcp" }, - { name: "nirium-pollar-adapter (npm)", version: "0.4.1", url: "https://www.npmjs.com/package/nirium-pollar-adapter" }, -]; - -const nodes = [ - { name: "Settlement Node", desc: "x402 micropayments and MPP charge — an AI agent pays per-request in USDC via a signed Stellar authorization entry, verified by a facilitator, settled on-chain." }, - { name: "Treasury Node", desc: "The agent holds only the RebalanceManager role on a client-owned DeFindex vault. rebalance() accepts Invest and Unwind — neither accepts a destination address. Withdrawal isn't blocked, it's structurally absent." }, - { name: "Audit Trail Node", desc: "SHA-256 content hash anchored to IPFS, with an optional ed25519 signature (a Stellar G... address doubling as a public key) proving who declared a fact." }, - { name: "Payroll Node", desc: "Non-custodial batch USDC disbursement to up to 100 recipients in one classic Stellar transaction, with sponsored-reserve onboarding." }, - { name: "Reporting Node", desc: "Aggregation and export layer over the other four nodes' on-chain activity." }, -]; - -export default function PitchPage() { - return ( -
-
-
-
-
- - - -
- - {/* COVER */} - -
- Not an active SCF submission — timing note below -
-

- Nirium — autonomous treasury & agentic payments infrastructure for Stellar -

-

- A developer SDK, CLI and MCP server that let any team give an AI agent a - Stellar-native way to get paid, move idle treasury without ever taking - custody, and anchor an immutable audit trail — shipped and verifiable - on-chain today, not proposed. -

-

- Structured against the Stellar Community Fund's real Build Award - panel-review criteria, one slide per criterion, verified live against{" "} - - stellar.gitbook.io/scf-handbook - . -

- - - {/* PROBLEM */} - -

- Corporate treasury sits idle in a bank account earning nothing while it - waits to be needed, and there's no Stellar-native way for an autonomous - AI agent to pay for a resource, or get paid for providing one, without a - human wiring a subscription or a card on file first. Both are integration - problems, not product problems — the primitives exist on Stellar, nobody - had packaged them into something a developer installs in one command. -

- - - {/* SOLUTION / ARCHITECTURE */} - -

- An Express 5 agent runtime with a modular node architecture. Each node is - independently toggleable and none require trusting Nirium with custody. -

-
- {nodes.map((node) => ( -
- -
-
{node.name}
-

{node.desc}

-
-
- ))} -
- -

- Why DeFindex, not our own vault, for mainnet:{" "} - NiriumVault stays testnet-only, audit-gated. Mainnet treasury runs over a - third-party DeFindex vault audited by OtterSec (March 2025 — 16 findings, - 13 vulnerabilities all marked resolved) on a Blend V2 strategy. Confirmed - independently: the deployed Etherfuse-strategy contract's WASM hashes to{" "} - 11329c24…5da988, matching - the audited public 1.0.0 release exactly. -

- - - - {/* TRACTION — packages */} - -
- -
- - Published packages -
-
    - {packages.map((p) => ( -
  • - {p.name} - v{p.version} -
    • - ))} -
- - -
- - MCP server — 25 tools -
-

- Counted directly from source, not carried over from an old draft. -

-
    - {mcpToolGroups.map((g) => ( -
  • - {g.tier} - {g.count} -
    • - ))} -
- -
- - - {/* TRACTION — mainnet txs */} - -

- Four real Invest operations confirmed - on mainnet, all 2026-08-06 — Nirium holds only the RebalanceManager role, the - vault is client-owned: -

-
- - - - - - - - - - {rebalanceTxs.map((tx) => ( - - - - - - ))} - -
Tx hashTime (UTC)Moved
- - {tx.hash.slice(0, 10)}… - - {tx.time}{tx.amount}
-
-

- Plus the first x402 micropayment settled on mainnet, 2026-07-09:{" "} - - 3134a51c…8bc - . -

- - - {/* TRACTION — upstream */} - -
    -
  • - - - stellar/stellar-dev-skill#96 — our - own fix, merged, listing Nirium in Stellar's official developer skills catalog. - -
    • -
  • - - - x402-foundation/x402#3171 — bug - reported against our own production endpoint, fixed by an unrelated - external contributor (PR #3180). - -
    • -
  • - - - Community-driven expansion via a GrantFox OSS campaign — 15 open, - labeled issues on{" "} - - nirium-protocol/nirium-sdk - , 2 already assigned after a real technical-plan review. - -
    • -
- - - {/* WHY STELLAR */} - -
    -
  • - - Non-custodial by contract, not by policy — the RebalanceManager role's inability to withdraw is a function signature with no destination-address parameter, enforced by the Soroban contract itself. -
    • -
  • - - Settlement only viable because finality is fast and fees near-zero — $0.02 micropayments only work because a Stellar tx confirms in seconds for fractions of a cent. -
    • -
  • - - Identity reuses Stellar's own keypairs — audit-trail ed25519 signatures decode directly from a Stellar G... address via StrKey, no separate identity system. -
    • -
- - - {/* BUILD READINESS */} - -
    -
  • Two live API boxes: full testnet + a partial, receive-only mainnet box with no signing key on it, by design.
    • -
  • Mainnet rebalances signed by a separate process with its own key and zero HTTP surface.
    • -
  • A vault allowlist enforced in code before any signature — the agent refuses to sign for a vault it wasn't explicitly given.
    • -
  • Existing tools leveraged, not reimplemented: DeFindex for vault custody, Etherfuse for CETES on/off-ramp, OpenZeppelin's relayer as the x402 facilitator on mainnet.
    • -
- - - {/* OPEN SOURCE */} - -
- -
Public today — Apache 2.0
-

- SDKs, CLI, MCP server, examples — nirium-protocol/nirium-sdk. -

- - -
Contracts — testnet, open-source planned
-

- NiriumVault & NiriumProtocol stay testnet-only until a funded audit — exactly what a Build Award would fund. Apache 2.0 release planned alongside it. -

- -
-

SCF's requirement is scoped to smart contracts — the rest of the codebase is explicitly allowed to stay private.

- - - {/* BUDGET / TRANCHES */} - -

- Most MVP/testnet work is already live — a future ask is realistically scoped - to the independent audit and completing the mainnet path it gates. Dollar - amounts aren't fixed here; they'd be set at actual submission per SCF's - Budget Guidelines. -

-
- {[ - { t: "T1 — MVP", d: "Largely complete: SDKs, CLI, MCP, x402/MPP, audit trail, payroll — all shipped." }, - { t: "T2 — Testnet", d: "NiriumVault/NiriumProtocol testnet-complete with a documented threat model + on-chain monitoring plan, per SCF's Tranche 2 requirement." }, - { t: "T3 — Mainnet", d: "Independent audit completed, findings remediated, contracts released Apache 2.0, mainnet deployment." }, - ].map((tr) => ( -
-
{tr.t}
-

{tr.d}

-
- ))} -
- - - {/* DIFFERENTIATION */} - -

- Tokenized treasury on Stellar has real, funded incumbents — Bando (SCF #42, - $75K) closest, same CETES-via-Etherfuse thesis. In a review of 728 catalogued - SCF-adjacent projects, agentic-payment primitives — x402, HTTP-native - facilitators — appeared in zero of them. -

-
- -
Bando & similar
-

Dashboard for humans to manually move idle cash into CETES.

- - -
Nirium
-

SDK + agent runtime other developers build on — treasury is one of five nodes, not the whole product.

- -
- - - {/* WHAT THIS DOESN'T CLAIM */} - -
    -
  • NiriumVault and NiriumProtocol have not been independently audited — they stay on testnet until they are.
    • -
  • Nirium does not currently custody client funds on mainnet, on any contract.
    • -
  • Nirium is a software provider; regulated activity in any flow is performed by the regulated partner in that flow.
    • -
  • This deck is not an active SCF submission and does not represent Nirium as currently under panel review.
    • -
- - - {/* VERIFY EVERYTHING */} - -
- {[ - { label: "SDK & CLI source", href: "https://github.com/nirium-protocol/nirium-sdk" }, - { label: "npm package", href: "https://www.npmjs.com/package/nirium" }, - { label: "PyPI package", href: "https://pypi.org/project/nirium/" }, - { label: "MCP server package", href: "https://www.npmjs.com/package/nirium-mcp" }, - { label: "GrantFox campaign issues", href: "https://github.com/nirium-protocol/nirium-sdk/issues?q=is%3Aissue+label%3A%22Official+Campaign+%7C+Third+Campaign%22" }, - { label: "DeFindex audit (OtterSec)", href: "https://github.com/paltalabs/defindex/tree/main/audits" }, - { label: "First mainnet x402 tx", href: "https://stellar.expert/explorer/public/tx/3134a51c66091fd7fbd85b38a4a6ec6cd432bb92c2450eac84ea7855cb7558bc" }, - { label: "SCF Build Award criteria", href: "https://stellar.gitbook.io/scf-handbook/scf-awards/build-award/submission-criteria" }, - ].map((l) => ( - - - - - ))} -
-
-

- Prepared by the Nirium team as a standalone reference. Not paid content, not a solicitation, not investment advice. -

- - nirium.xyz - -
- - -
-
- ); +// Retired deck; /docs is the maintained, verifiable reference. +export default function Page() { + redirect("/docs"); } diff --git a/apps/web/public/legal/privacy-notice-draft-v2.md b/apps/web/public/legal/privacy-notice-draft-v2.md deleted file mode 100644 index 0d38507c..00000000 --- a/apps/web/public/legal/privacy-notice-draft-v2.md +++ /dev/null @@ -1,171 +0,0 @@ -# Aviso de Privacidad - Nirium Protocol (borrador v2, LFPDPPP 2025) - -> **BORRADOR - PENDIENTE DE REVISIÓN LEGAL.** Este documento NO está publicado -> en `/privacy`. El aviso en vivo (v1, actualizado 15-ago-2026) sigue siendo el -> vigente hasta que este borrador sea confirmado por el despacho externo. Se -> preparó como reemplazo completo, no como un parche, para que el abogado -> tenga un documento único que revisar en vez de un diff difícil de leer sobre -> el archivo `page.tsx` vivo. -> -> Qué cambió respecto al v1 vigente: el v1 ya cubre correctamente la reforma -> LFPDPPP 2025 (autoridad nueva, plazos, derechos ARCO) - esa parte se -> mantiene sin cambios de sustancia. Lo nuevo es la Sección 2b y el ajuste de -> la Sección 3: describir la telemetría de uso de `x402Serve()`, agregada el -> 18-ago-2026, que el v1 no menciona porque no existía cuando se escribió. - -## 1. Identidad y domicilio del Responsable - -"Nirium Protocol" (en adelante, el "Proyecto") es el nombre comercial bajo el -cual operan sus fundadores, quienes son responsables del tratamiento de los -datos personales que nos proporcione. El Proyecto es una herramienta de -software de código abierto y, a la fecha, no opera bajo una persona moral -constituida. Puede contactar a los responsables en el correo electrónico: -**niriumprotocol@gmail.com**. - -## 2. Datos personales que se recaban de usuarios directos del sitio y del API - -Para las finalidades señaladas en este aviso, podemos recabar los siguientes -datos de quienes usan directamente nuestro sitio o nuestro API (exclusivamente -para la infraestructura de software; no almacenamos datos financieros): - -- API keys (almacenadas exclusivamente de forma hasheada, nunca en texto plano). -- URLs de webhooks para notificaciones del sistema. -- Métricas de uso del sistema e identificadores de red técnica. -- Direcciones públicas de Stellar (formato `G...`) cuando el usuario firma una - transacción, un login social vía Pollar, o un atestiguamiento de auditoría. - **Una dirección pública de Stellar es un identificador pseudónimo, no un - dato biométrico ni un dato financiero sensible** - es la misma naturaleza - que un número de cuenta público, y es la posición que este Proyecto ya - sostiene consistentemente para los recibos de auditoría (`NiriumMainnet.md` - §3.6): se ancla la dirección y el monto, nunca datos personales crudos. - -**Importante:** No recabamos datos personales sensibles, datos biométricos, ni -tenemos custodia de fondos financieros en ningún momento. El software opera de -manera no custodial mediante firmas del cliente. - -## 2b. Datos que se recaban de integradores terceros que instalan nuestro software (nuevo) - -Desde el 18 de agosto de 2026, el paquete `nirium` (SDK) incluye una función, -`x402Serve()`, que un desarrollador externo instala en **su propio servidor** -para cobrar por su propia API usando el protocolo x402. Esa función envía, de -forma no bloqueante y opcional, un ping de telemetría a la infraestructura de -Nirium cuando procesa una solicitud con una llave de facilitador válida. Ese -ping puede contener: - -- Una dirección pública de Stellar del integrador (`pay_to`), del mismo tipo - descrito en la Sección 2. -- Un **hash SHA-256** de la llave de facilitador del integrador (emitida por - OpenZeppelin, no por Nirium) - **nunca la llave en texto plano**. -- La red (`testnet`/`mainnet`), un conteo de rutas configuradas, un conteo de - solicitudes procesadas, y la versión del paquete instalado. - -**Este dato lo genera el software del integrador, no una visita de una persona -a nuestro sitio.** No incluye información de los usuarios finales del -integrador - Nirium nunca ve esas solicitudes, que ocurren enteramente en -infraestructura ajena. El único propósito de este dato es saber si el paquete -publicado se usa en producción; puede desactivarse por el integrador -estableciendo `NIRIUM_X402SERVE_TELEMETRY=false` en su propio entorno. - -## 3. Finalidades del tratamiento - -Los datos personales que recabamos serán utilizados exclusivamente para las -siguientes finalidades necesarias para el servicio que solicita: - -- Autenticación de usuarios en la plataforma. -- Gestión y limitación de tasa (rate limiting) del API. -- Prestación del servicio técnico de software y envío de webhooks. -- Monitoreo de seguridad y prevención de abusos en el sistema. -- Medir la adopción real de las herramientas de software que publicamos - (Sección 2b), para priorizar correctamente el trabajo de cumplimiento sobre - esas herramientas en función de su uso efectivo, no de su existencia teórica. - -## 4. Transferencias de datos personales - -Le informamos que sus datos personales no son vendidos a terceros. Únicamente -se comparten con nuestros proveedores de infraestructura en la nube necesarios -para la operación del software (por ejemplo, Supabase para alojamiento de -bases de datos y Fly.io para infraestructura del agente) operando bajo -estrictos acuerdos de procesamiento de datos y confidencialidad. - -## 5. Medios para limitar el uso o divulgación - -Usted puede limitar el uso o divulgación de sus datos personales enviando su -solicitud al correo electrónico: **niriumprotocol@gmail.com**. Si usted es un -integrador que instaló `x402Serve()` y desea desactivar la telemetría descrita -en la Sección 2b sin contactarnos, puede hacerlo directamente estableciendo -`NIRIUM_X402SERVE_TELEMETRY=false` en su propio entorno - no requiere -solicitud. - -## 6. Derechos ARCO y cómo ejercerlos - -Usted tiene derecho a conocer qué datos personales tenemos de usted (Acceso). -Asimismo, es su derecho solicitar la corrección de su información personal si -está desactualizada, sea inexacta o incompleta (Rectificación); que la -eliminemos de nuestros registros (Cancelación); así como oponerse al uso de -sus datos personales para fines específicos (Oposición). Para ejercer -cualquiera de los derechos ARCO, deberá enviar la solicitud respectiva al -correo electrónico: **niriumprotocol@gmail.com**. - -Responderemos a su solicitud en un plazo máximo de 20 días hábiles de -conformidad con la Ley Federal de Protección de Datos Personales en Posesión -de los Particulares (LFPDPPP), conforme a la reforma publicada en el Diario -Oficial de la Federación el 20 de marzo de 2025 (vigente desde el 21 de marzo -de 2025). A partir de dicha reforma, el Instituto Nacional de Transparencia, -Acceso a la Información y Protección de Datos Personales (INAI) fue -extinguido, y la autoridad garante en la materia es la Secretaría -Anticorrupción y Buen Gobierno. - -## 7. Uso de cookies y tecnologías similares - -Le informamos que en nuestra página de internet utilizamos cookies de sesión -exclusivamente para mantener la autenticación del usuario y garantizar el -funcionamiento de la plataforma. No utilizamos cookies de rastreo publicitario -ni píxeles de terceros con fines de marketing. - -## 8. Cambios al aviso de privacidad - -El presente aviso de privacidad puede sufrir modificaciones, cambios o -actualizaciones derivadas de nuevos requerimientos legales, de nuestras -propias necesidades por los servicios que ofrecemos, o por otras causas. Nos -comprometemos a mantenerlo informado sobre los cambios que pueda sufrir el -presente aviso de privacidad, publicando la versión actualizada en esta misma -página. - ---- - -## English Translation / Privacy Policy - -*Note: This English translation is provided for convenience. In case of legal -dispute, the Spanish Aviso de Privacidad above, complying with Mexican -LFPDPPP, prevails.* - -"Nirium Protocol" is the commercial name under which its founders operate; -they are responsible for the processing of personal data collected. The -Project is an open-source software tool and does not yet operate under an -incorporated legal entity. - -We collect hashed API keys, webhook URLs, usage metrics, and public Stellar -addresses (`G...`) for authentication, rate limiting, and security purposes. -A public Stellar address is a pseudonymous identifier, not biometric or -sensitive financial data - the same position we already apply consistently to -audit receipts. - -**New since 18-Aug-2026**: our published `nirium` SDK includes `x402Serve()`, -a function a third-party developer installs on **their own server** to charge -for their own API. It sends an optional, non-blocking telemetry ping that may -include the integrator's Stellar address, a SHA-256 hash of their facilitator -key (never the raw key), network, route/request counts, and SDK version. This -never includes data about the integrator's own end users - Nirium never sees -those requests, which happen entirely on infrastructure we do not operate. -Integrators can opt out by setting `NIRIUM_X402SERVE_TELEMETRY=false`. - -We do not collect PII, sensitive data, biometrics, or financial data, nor do -we custody user funds. Data is only shared with essential infrastructure -providers (Supabase, Fly.io) under data processing agreements. We do not sell -data. We use essential session cookies only, no marketing tracking. You may -exercise your ARCO rights (Access, Rectification, Cancellation, Opposition) by -contacting **niriumprotocol@gmail.com**. We will respond within 20 business -days, per the LFPDPPP as amended on March 20, 2025 (in force since March 21, -2025) - under which Mexico's former data protection authority (INAI) was -dissolved and its functions transferred to the Secretaría Anticorrupción y -Buen Gobierno. diff --git a/skills-lock.json b/skills-lock.json deleted file mode 100644 index 92be5e80..00000000 --- a/skills-lock.json +++ /dev/null @@ -1,79 +0,0 @@ -{ - "version": 1, - "skills": { - "copywriting": { - "source": "coreyhaines31/marketingskills", - "sourceType": "github", - "skillPath": "skills/copywriting/SKILL.md", - "computedHash": "2e83eda2221e97166172a0798e9b0379e34080595e107e2fc0cf580e9b3bbf7b" - }, - "develop-secure-contracts": { - "source": "OpenZeppelin/openzeppelin-skills", - "sourceType": "github", - "computedHash": "2dff839990d5ac6ecaf1b7a9ce9588320779de05b8d00b9ab3cc6cf31bea8887" - }, - "find-skills": { - "source": "vercel-labs/skills", - "sourceType": "github", - "skillPath": "skills/find-skills/SKILL.md", - "computedHash": "9e1c8b3103f92fa8092568a44fe64858de7c5c9dc65ce4bea8f168080e889cfd" - }, - "pitch-deck": { - "source": "ailabs-393/ai-labs-claude-skills", - "sourceType": "github", - "skillPath": "packages/skills/pitch-deck/SKILL.md", - "computedHash": "b23b5c7542d53e3cada85052bd4165210a95447215afa4456256dc43a864eee4" - }, - "setup-cairo-contracts": { - "source": "OpenZeppelin/openzeppelin-skills", - "sourceType": "github", - "computedHash": "0a563050fa22541d76890c862bc02a403e9f8590419a722d145dcf3df5578489" - }, - "setup-solidity-contracts": { - "source": "OpenZeppelin/openzeppelin-skills", - "sourceType": "github", - "computedHash": "9c0e45a4afb334c5460811d1c2db5ba7d7756f9e401b250921322c6aab86be64" - }, - "setup-stellar-contracts": { - "source": "OpenZeppelin/openzeppelin-skills", - "sourceType": "github", - "computedHash": "ec2c00f94a5cd627d47daca9ae7832bfd32257607548c58dd0954b38db2cb504" - }, - "setup-stylus-contracts": { - "source": "OpenZeppelin/openzeppelin-skills", - "sourceType": "github", - "computedHash": "c625fb2aa2a714f7246b6fa4d9a51538ba3640e3034eec3419b8224a01564634" - }, - "spec-to-code-compliance": { - "source": "trailofbits/skills", - "sourceType": "github", - "skillPath": "plugins/spec-to-code-compliance/skills/spec-to-code-compliance/SKILL.md", - "computedHash": "33d4d2203e13ffc2a51d821433d6c1029f58f5ddf8c88715403844da5adca798" - }, - "stellar-dev": { - "source": "stellar/stellar-dev-skill", - "sourceType": "github", - "computedHash": "6eb4c009e07890f486774eda6ce4decaef6b171277bd1fd6f6b50302d05ba514" - }, - "upgrade-cairo-contracts": { - "source": "OpenZeppelin/openzeppelin-skills", - "sourceType": "github", - "computedHash": "33640799e05560f506949e37ce80fb237dba82542980a7b35d66f3268cfcf141" - }, - "upgrade-solidity-contracts": { - "source": "OpenZeppelin/openzeppelin-skills", - "sourceType": "github", - "computedHash": "ef8776be9fd2ee6721f6b6b29992bf6029a6122797b3cec6fe3ce185b22be4ef" - }, - "upgrade-stellar-contracts": { - "source": "OpenZeppelin/openzeppelin-skills", - "sourceType": "github", - "computedHash": "041ffafcfa1d491e3da62d5796638382b864dc3941ba4301d96a8bc37938da4a" - }, - "upgrade-stylus-contracts": { - "source": "OpenZeppelin/openzeppelin-skills", - "sourceType": "github", - "computedHash": "f59350e4bf6f6c44ad14bf7ed69fdd59209238b2ab9ee4f9872affb8400c16e2" - } - } -}