Shipped a trust upgrade across NexArt: • Canonical node now issues signed attestation receipts (Ed25519) + publishes public keys • @nexart/ai-execution v0.5.0: offline verification of node receipts + reason codes • @nexart/codemode-sdk v1.9.0: same receipt verification for deterministic runs Try it: 1. Generate a certified AI record: https://nexartaiauditor.xyz 2. Verify independently (no account): https://recanon.xyz Proofs are now portable + independently verifiable — no “trust our database”.

0 reply

0 recast

2 reactions

Gm Today we shipped three major updates to NexArt. • CER API for certifying AI executions • n8n integration for workflow automation • upgraded public verifier AI decisions can now produce Certified Execution Records (CERs) that anyone can verify. Create one with: POST /v1/cer/ai/certify Then verify it publicly. Example record: https://verify.nexart.io/e/retest-certify-002

1 reply

2 recasts

6 reactions

NexArt: From Artnames to AI Execution Infrastructure This is not a product update. It’s the path. Phase 1 — Artnames (August 2024) A simple idea: convert names into art. That became Artnames. A tiny team formed. ◼ CORE  ◻ Founder ◼ TEAM  ◻ Developer (departed)  ◻ Marketing (departed) Momentum felt real, briefly. The developer disappeared. The marketer left to run a gaming company. Suddenly it was just me. No coding experience. No marketing background. Just an idea I refused to drop. The structure collapsed. The idea survived. Phase 2 — Rebuilding Alone as NexArt Everything was stripped back to basics. NexArt.xyz: a geometric canvas I could realistically build. Simple. Achievable. As coding skills improved, the engine evolved — modes, deterministic rendering, eventually Code Mode. ◼ CORE  ◻ Founder ◼ PRODUCT  ◻ NexArt.xyz Solo. Focused. Survival. Phase 3 — First Ecosystem Layer NexArt matured beyond a single site. The question became: could others build on this engine? That led to the NexArt Foundation and the Nexa Token. ◼ CORE  ◻ Founder ◼ ECOSYSTEM  ◻ NexArt.xyz  ◻ NexArt Foundation  ◻ Nexa Token Stable. Functional. It could have stopped there. Phase 4 — Choosing Infrastructure A new mode was needed: byX. Two paths: • Build it inside NexArt.xyz (easier) • Extract the engine as a standalone SDK (harder) Infrastructure was chosen. byXcollection was built independently using the SDK. NexArt split into two parallel tracks: an independent engine, and the products built on top of it. ◼ CORE  ◻ Founder   ▼ ◼ INFRASTRUCTURE  ◻ CodeMode SDK ◼ ECOSYSTEM  ◻ NexArt.xyz  ◻ byXcollection  ◻ NexArt Foundation  ◻ Nexa Token That structural decision changed everything. Phase 5 — Infrastructure for the AI Era To make the art engine work, the system had to be fully deterministic and replayable. As the SDK matured, a realization emerged: The execution discipline required for verifiable generative art was the same discipline missing in enterprise AI systems. AI is moving rapidly into finance, insurance, trading, and agentic workflows. But most systems share a structural weakness. They cannot: • Replay decisions deterministically • Certify exact configurations • Survive audits with cryptographic proof The execution engine built to verify art turns out to be exactly what enterprises need to verify AI. The infrastructure expanded accordingly. NexArt Today (2026) Clear separation: infrastructure is modular and independent; the ecosystem operates on top without entanglement. ◼ INFRASTRUCTURE (Core Execution Layer; Growing)  ◻ CodeMode SDK  ◻ UI Renderer SDK  ◻ AI Execution SDK  ◻ Canonical Node  ◻ Protocol  ◻ NexArt.io (Verification Platform)  ◻ Protocol Demos ◼ ECOSYSTEM (Built on Top; Stable)  ◻ NexArt.xyz  ◻ byXcollection  ◻ Frontierra  ◻ NexArt Foundation  ◻ Nexa Token The Evolution Artnames → personal art engine → SDK → infrastructure → verifiable AI execution framework. This was not a pivot. Each limitation forced a structural choice. Being alone forced clarity. Clarity forced architecture. Architecture created infrastructure. The Next Phase AI is now embedded everywhere, and entering regulated domains. Soon, three requirements will become non-negotiable: • Determinism • Replayability • Certification NexArt is built for exactly that layer. Not another model. Not another interface. Execution infrastructure beneath AI systems. Vision To become the trusted, invisible layer for execution integrity. Any decision, human or machine, captured, version-pinned, replayed, verified, certified. Across industries. Across jurisdictions. Across time. Good infrastructure disappears. It simply works, reliably. What started as turning names into art has evolved into infrastructure for trustworthy AI in a regulated world. If this resonates, whether you’re a builder needing deterministic execution, an investor focused on verifiable AI infrastructure, or a researcher exploring auditability, let’s talk.

1 reply

1 recast

6 reactions

https://paragraph.com/@artnames/verifiable-ai-decisions-need-a-standard-record-introducing-aief

3 replies

51 recasts

61 reactions

What if every AI decision could be independently verified? Here’s a 40s demo built on @replit: LLM response → policy engine → CER → canonical attestation. No black box. Try it: nexartaiauditor.xyz (Mock LLM included, or plug OpenAI/Claude + NexArt API)

1 reply

5 recasts

12 reactions

SDK, CLI, local execution: free. If you’re building systems that require certification, reproducibility, and audit-ready proofs, NexArt provides certified runs. Pricing → nexart.io/pricing

0 reply

0 recast

97 reactions

Nexart SDK + CLI are free. The Canonical Node is where certification happens: deterministic execution, canonical outputs, and verifiable audit trails. Plans: • Free — 100 certified runs/month • Pro — 5,000 runs for $6k/year • Scale — 50,000 runs for $18k/year • Enterprise — unlimited, from $50k/year Built for fintech, simulations, AI pipelines, and anything auditors will ask questions about.

0 reply

2 recasts

4 reactions

New NexArt update 🚀 Canonical rendering now has: • Account-level quota enforcement • Explicit pricing tiers • Hardened security architecture docs • Clear protocol compliance standards If results need to be reproducible, verifiable, and auditable, this is the foundation. NexArt.io

0 reply

0 recast

6 reactions

I just created "noino" on /nexart

1 reply

0 recast

1 reaction

GM NexArt Protocol v1.2.0 is done and locked Code Mode SDK v1.6.0 is live UI Renderer SDK is live Node runtime (private, for now) is ready Apps built on the protocol: Creative coding • http://NexArt.xyz : no-code + code generative art, SoundArt, open minting, $NexA rewards • http://ByXcollection.xyz : independent collections where creators define their own outputs Gaming • http://Frontierra.xyz : open-world exploration proving you don’t need expensive backend infra to generate and scale massive player maps Verification / Prediction • http://Recanon.xyz : deterministic result verification, sealed and reproducible forever This is one protocol. Multiple real products. All live. Now loooking for serious builder to built with it

3 replies

52 recasts

9 reactions

https://artizen.fund/index/p/

0 reply

21 recasts

21 reactions

https://paragraph.com/@artnames/ @nexart.eth

0 reply

1 recast

9 reactions

Frontierra is now live 🌍 A generative world built with NexArt for deterministic world generation. Out first multiplayer world is live ( which is our Beta ) and can accomodate the first 100 people claiming it. Claim your land. Shape your path. Explore, discover, and make the world yours. https://frontierra.xyz/ NOT ONCHAIN - at least not yet ...

2 replies

23 recasts

28 reactions

I wanted a visual demo that isn’t art to show what the NexArt SDK actually enables. This was built in ~3 prompts: a fully deterministic 3D generated world. Because it’s deterministic, there’s no need to store large world data, just a seed + vars. The same world regenerates tomorrow, in a month, or in 10 years, bit-for-bit identical. This is less about worlds, and more about what happens when systems depend on determinism instead of storage.

1 reply

3 recasts

8 reactions

Putting a list of potential sector for Nexart 1) Mint platforms / generative drops / marketplaces Hook: “Canonical rendering you can prove.” • Same mint renders identically across devices forever • Dispute-proof: “this is the one true output for these inputs” • Works for previews, reveals, traits, and long-term hosting 2) Games + UGC studios Hook: “Deterministic cosmetics & badges without shipping heavy assets.” • Generate cosmetics/cards/badges from seed + params • Ship tiny inputs, not large files • Easy to cache, easy to regenerate, consistent across clients 3) Ticketing / access / POAP-style products Hook: “Tickets & passes that never break and are instantly verifiable.” • Regenerate the visual from wallet/event data anytime • No “image missing” risk • Easy uniqueness: each ticket is deterministic + personal 4) Identity + reputation systems (Farcaster/Lens/etc.) Hook: “Verifiable identity cards.” • Deterministic profile art, rep badges, “proof cards” • Shareable visuals that map cleanly to public inputs (FID, address, attestations) • No storage headaches; regen on demand 5) Brands + campaigns (non-crypto) Hook: “Mass personalization at scale, zero asset ops.” • Personalized posters/recaps/receipts from user + campaign inputs • Deterministic = no “why did mine change?” support tickets • Cheap and fast to render + cache; works for share cards 6) Museums / cultural institutions / archives Hook: “Archival-grade generative works.” • Determinism + version pinning = future-proof • A work can be re-rendered from the spec decades later • “Executable reference” is the trust layer institutions want 7) Compliance-heavy orgs needing audit trails Hook: “Human-readable audit artifacts.” • Deterministic “visual receipts” for actions/events • Easy to verify later from logs (inputs) • Makes audits legible without screenshots/files that can be tampered with 8) Developer tooling companies (wallets/explorers/indexers/analytics) Hook: “Deterministic visual primitives for your UI.” • Risk cards, portfolio badges, onchain activity receipts • Consistent visuals across web/mobile/embeds • Cached by input hash; reproducible for support/debugging

0 reply

0 recast

5 reactions