solidity-supply-chain-us

Writes and audits Solidity smart contracts for supply chain traceability and regulatory compliance.

1|Updated Sep 4, 2025

Search Tags:#compliance #traceability #smart contracts #solidity #supply chain #fsma #dscsa

Ready to run

npx skills add https://github.com/FuzzysTodd/The-Nexus-Protocol-Token-DAO --skill solidity-supply-chain-us-fuzzystodd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: solidity-supply-chain-us
Source: https://github.com/FuzzysTodd/The-Nexus-Protocol-Token-DAO/tree/main/skills/solidity-supply-chain-us
Command: npx skills add https://github.com/FuzzysTodd/The-Nexus-Protocol-Token-DAO --skill solidity-supply-chain-us-fuzzystodd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing Solidity contracts for supply chain, logistics, and provenance tracking requires deep knowledge of US and global regulations like FDA FSMA 204, DSCSA, and Dodd-Frank 1502, and generic smart contract code often misses mandatory traceability, custody, and recall requirements. ## Core Features & Use Cases - Regulatory Data Structures: Provides Solidity structs and enums for Critical Tracking Events, Key Data Elements, DSCSA T3 transaction data, and conflict mineral declarations. - Mandatory Compliance Patterns: Implements chain-of-custody transfers, lot recall enforcement, letters of credit, cold-chain IoT condition monitoring, and carbon credit retirement. - Use Case: A developer building a pharmaceutical track-and-trace contract can use the DSCSA reference to implement serialized NDC identifiers, authorized trading partner checks, and suspect product quarantine flows that satisfy FDA verification requirements. ## Quick Start Use the solidity-supply-chain-us skill to write a Solidity contract that tracks chain of custody for food lots with FSMA 204 compliant recall support.

Frequently Asked Questions about solidity-supply-chain-us

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement chain of custody in a Solidity smart contract?▼

Chain of custody in Solidity uses a transferCustody function that verifies the caller is the current custodian, requires a non-zero document hash, and appends a CustodyEvent to an on-chain history mapping. Each transfer emits a CustodyTransferred event for off-chain regulatory reporting.

What Solidity data structures are needed for FDA FSMA 204 compliance?▼

FSMA 204 compliance requires structs for Critical Tracking Events and Key Data Elements capturing traceability lot code, quantity, unit of measure, location, event date, and reference document numbers. Transformation events must also record all input lot codes to enable backward tracing during recalls.

How do I enforce product recalls in a supply chain smart contract?▼

Product recalls use a recalledLots mapping checked inside every transfer path, so recalled lots cannot move custody. A RECALL_AUTHORITY_ROLE initiates recalls, and custodians can quarantine individual units by setting their status to RECALLED.

Does DSCSA require on-chain storage of full transaction documents?▼

DSCSA requires T3 records retained for six years, but full documents should be stored on IPFS with only the content identifier hash kept on-chain. This satisfies verification requirements while avoiding excessive gas costs for bulk data.

What are the limitations of on-chain carbon credit tracking?▼

On-chain carbon credit tracking records retirement and ownership but cannot verify real-world emission reductions without trusted third-party verifiers. Registry certificates from VERRA or Gold Standard must be referenced via IPFS CIDs and attested by accredited bodies.