ByAUJay
Supply Chain Blockchain Consulting for Global Manufacturers: Lessons from Early Deployments
Summary: Let's dive into what's really worked (and what hasn't) with enterprise supply-chain blockchain, plus how to craft a solid roadmap for 2026-2028 that lines up with key regulations like the DSCSA, UFLPA, EU Battery Passports, ESPR Digital Product Passports, CBAM, and the upcoming Sunrise 2027 2D barcodes. This post breaks down the tangible results, the pitfalls to avoid, and gives you a hands-on blueprint you can roll out in just 90 to 180 days.
Why 2026-2028 will separate pilots from production
Regulatory and Market Clocks: Moving Traceability from “Nice-to-Have” to “Table Stakes”
Regulatory frameworks and market demands are pushing traceability from something that companies could just consider a bonus to being absolutely essential:
- The enforcement for US DSCSA package-level interoperability is rolling out in stages: manufacturers and repackagers have until May 27, 2025; wholesalers by August 27, 2025; dispensers with 26 or more full-time employees by November 27, 2025; and smaller dispensers will have until November 27, 2026. Basically, that means the interoperable, electronic, serialized data exchange needs to be up and running, not just on the drawing board. (fda.gov)
- The enforcement of the UFLPA is ramping up with over 16,700 shipments being scrutinized and 144 entities on the Entity List as of 2025. This list now includes some key sectors like aluminum, steel, PVC, caustic soda, copper, lithium, red dates, and seafood. This means you’ll need to provide more detailed provenance evidence than just PDFs. (dhs.gov)
- When it comes to the EU Battery Regulation, from February 18, 2027, it’s mandatory to have battery passports and QR codes for EVs, industrial batteries over 2 kWh, and LMT batteries introduced to the market. Plus, the QR code needs to link back to the passport. Time to focus on design data, identifiers, and access controls now. (eur-lex.europa.eu)
- For the ESPR Digital Product Passport, the regulation kicked in on July 18, 2024, with the first working plan coming in 2025 that identifies priority groups such as textiles/apparel, furniture, tires, mattresses, iron/steel, and aluminum. The initial product-specific measures will start rolling out in 2027-2028, with model DPP data flows happening in 2025-2026. (commission.europa.eu)
- As for CBAM, during the transitional phase (from Q4 2023 to the end of 2025), you’ll need to report your data, with actual payments kicking off in 2026. Plus, only the EU’s calculation method will be accepted starting January 1, 2025. So, make sure your carbon data exchange with suppliers is both auditable and consistent. (taxation-customs.ec.europa.eu)
- Finally, looking ahead to Sunrise 2027 (GS1), by the end of 2027, retailers worldwide are aiming for 2D barcode capabilities. QR Codes backed by the GS1 Digital Link will become the standard for on-pack data and traceability. Manufacturers should get on the ball with serialization and binding lots/batches now. (gs1.org)
These mandates create reward programs that mix standards-based data sharing, like GS1 EPCIS 2.0, GS1 Digital Link, and W3C Verifiable Credentials, with tamper-evident audit logs. This is typically done using permissioned blockchains and data spaces, allowing us to hit the mark on traceability, privacy, and performance all at once. (gs1.org)
What early deployments taught us (with numbers)
1) Food safety: speed-to-trace changes recalls and cost exposure
- Walmart’s IBM Food Trust trials seriously shortened the time it takes to trace mangoes from a whopping 6 days and 18 hours all the way down to just 2.2 seconds! Plus, this innovation has helped enforce a mandate for leafy greens suppliers. The cool part? It really helps cut down on how far recalls need to reach and speeds up figuring out the root causes. (public.walmart.com)
- Over at Carrefour, consumer-friendly QR programs showed that folks are really interested in knowing where their chicken, milk, and orange juice come from. This insight is driving them to expand their offerings in organic and private-label products. Recent studies found that customers value traceability backed by blockchain especially for leafy greens, which means there’s a chance to charge a bit more if they manage costs well. (foodnavigator.com)
Implementation Pattern That Worked
- We kicked things off with GS1 data capture right at the farm and packhouse. Then, we tracked EPCIS events as the products moved through processing and distribution. A permissioned ledger was used to keep everything secure and maintain event integrity. Plus, we included an on-pack QR code (GS1 Digital Link) that gives both consumers and regulators easy access to all the information they need. Check it out for more details: gs1.org
2) Conflict minerals and luxury goods: provenance at scale
- De Beers’ Tracr has really taken off since its pilot phase, having registered nearly three million diamonds since 2022. It now covers the country-of-origin for all rough stones over 1 ct sourced from De Beers, making it possible to verify everything from rough to polished diamonds. Major labs like GIA are in on this too! (miningweekly.com)
- The Aura Blockchain Consortium, which includes big names like LVMH, Prada, and Cartier, has registered over 50 to 70 million luxury items using blockchain-based digital product passports linked to NFC/QR codes. This really shows how effective teamwork across the industry can take things to the next level, moving beyond just pilot projects. (cointrust.com)
- When it comes to automotive raw materials, Volvo is making strides by tracing cobalt with the help of Circulor and Oracle, working alongside CATL and LG Chem. Meanwhile, BHP is teaming up with Tesla to explore end-to-end traceability and assure carbon intensity for nickel. (media.volvocars.com)
Key Lesson:
- Industry utilities really take off when they can prove their worth through things like ethical sourcing, fighting counterfeits, and making solid DPP/ESG claims. Plus, it’s crucial for different players in the ecosystem--like retailers, labs, and OEMs--to team up and agree on sharing data and validation rules. (jassinconsultinggroup.com)
3) Automotive compliance and supplier data: TPS at enterprise scale
- Renault’s XCEED has been making waves! During a pilot at the Douai plant, it hit an impressive 500 transactions per second and archived over 1 million compliance documents. Now, they’re rolling it out to suppliers, which is really speeding up how they handle regulatory responses. Check it out here: (ibm.com)
- Over at BMW, their PartChain kicked off with front-lights at the Spartanburg plant in the US and Dingolfing in Germany. It’s growing fast with more suppliers joining in, and they’re leveraging a mix of cloud services and blockchain tech to boost transparency around component origins and track raw materials. Take a look at more details: (press.bmwgroup.com)
4) Why some platforms failed
- So, Maersk and IBM’s TradeLens shut down in 2023. Even though it was a pretty solid platform, it just couldn’t get the “full global industry collaboration” it needed to really take off. Turns out, it was more about adoption, governance, and creating the right incentives than about the technology itself. Check out more on their official statement here: (maersk.com)
- On the other hand, we.trade, which was all about bank-led trade finance, threw in the towel in 2022 after struggling with funding issues. Its limited network and lack of returns for investors meant that things just didn’t get moving as hoped. The takeaway? If the incentives don’t stack up for each new participant, people get tired of waiting around. You can read more about it here: (gtreview.com)
Emerging best practices you can adopt in 2025-2026
1) Start with Standards-First Data Design
- Kick things off by using GS1 EPCIS 2.0 for event-level traceability, which covers everything like who, what, when, where, why, and how, along with sensor data and certifications. Plus, make sure to share identifiers using GS1 Digital Link URIs for QR codes. This way, you're set for the future with DPP, recalls, and other secondary use cases. (gs1.org)
- Make sure to get your carbon data in line with the WBCSD’s PACT Methodology and Technical Specifications v3 (2025). This will help suppliers swap product carbon footprints (PCFs) without any hiccups. If you’re in the automotive game, don’t forget to follow the Catena-X PCF Rulebook to keep up with Battery Regulation and CBAM requirements. (docs.carbon-transparency.org)
2) Combine data spaces + blockchain, not “blockchain-only”
Data spaces, like Catena‑X, are all about ensuring that exchanges are sovereign and follow policies--thanks to things like EDC connectors, the Dataspace Protocol, and the GAIA‑X trust framework. On the flip side, blockchains provide the backbone for tamper-proof proofs, multi-party audit logs, and credential registries. When you mix these two together, you can keep sensitive info off-chain while still letting each party maintain control. Check out more about it here.
3) Use Verifiable Credentials (VCs) for Attestations
When it comes to supplier certifications--like “forced-labor-free,” ISO/IATF, organic, or AEO/CTPAT--modeling these as W3C Verifiable Credentials 2.0 is definitely the way to go. The cool thing about selective disclosure (BBS/ecdsa-sd) is that it allows suppliers to back up their claims without spilling too much information. By the way, W3C wrapped up the crucial specs for VCs back in 2025. Check out more on this here.
4) Design for Near-Term Mandates
- DSCSA: Make sure that serialized package data exchanges and verification processes work smoothly across all trading partners. Using hash-only anchoring can create a solid independent audit trail. Check it out here: fda.gov.
- Battery Passports: It’s crucial to implement unique IDs along with access control and role-based views. Plus, make sure that the QR code links back to the passport content as per Article 77, effective from February 18, 2027. Details can be found here: eur-lex.europa.eu.
- CBAM: Keep track of embedded emissions using EU-approved methods. We need to ensure that supplier Product Carbon Footprints (PCFs) are both verifiable and linkable to shipments. More info is available at: taxation-customs.ec.europa.eu.
- Sunrise 2027: Time to upgrade your labeling and packaging to support 2D barcodes. Make sure that both your point-of-sale (POS) and back-office systems can read GS1 Digital Link and GS1 DataMatrix. For further guidance, check out: gs1.org.
5) Build Governance Before Code
- Establish a neutral operating model: It’s essential to set up clear guidelines for things like IP and licensing regarding data schemas, quality standards, how to handle disputes, onboarding and offboarding processes, and ensuring ongoing funding. Just look at TradeLens and we.trade; they illustrate that it's really governance and the right incentives that keep a network thriving, not just the crypto mechanics. Check out more on this over at maersk.com.
- Architecting for Privacy, Performance, and Audit
- It's important to keep Personally Identifiable Information (PII) and sensitive business data safe in your systems. You can enhance security by publishing cryptographic commitments (like hashes) and credentials on the ledger. Using permissioned chains (like Hyperledger Fabric) combined with modern consensus mechanisms can help you achieve high Transactions Per Second (TPS) when needed, while data spaces help manage who can access what. Check out more about it here: (research.ibm.com).
Practical blueprints you can run in 90-180 days
A. 12-week “Regulatory Ready Traceability” pilot
- Weeks 1-2: Let’s kick things off by scoping out one product family, picking 3-5 suppliers, and selecting a single distribution center or plant. We'll also define the EPCIS event model and figure out the minimal set of data needed for DPP/DSCSA/CBAM. Don’t forget to map out those identifiers like GTIN, lot, and serial numbers. You can find more details on this over at gs1.org.
- Weeks 3-4: Next up, we’ll set up our connectors to either a data space or a secure exchange. We’ll need to decide on a permissioned ledger (or service) to anchor everything, and we should also enable the GS1 Digital Link QR for our pilot SKUs. For more guidance, check out catenax-ev.github.io.
- Weeks 5-8: It’s time to implement EPCIS capture at every node, including the farm, packhouse, plant, and distribution center. We’ll automate the ingestion of IoT/quality events and issue verifiable credentials for things like organic certifications and ISO 9001. More details are available at gs1.org.
- Weeks 9-10: During this phase, we’ll integrate the PCF exchange using PACT v3, set up the CBAM/ESG fields, and run a mock recall. Our goal is to prove traceability in under 5 seconds from SKU/lot back to its origin. For more on this, head over to docs.carbon-transparency.org.
- Weeks 11-12: To wrap things up, we’ll conduct security and penetration tests, review data minimization strategies, and hand over things to our vendors. We’ll also measure our KPIs, which include time-to-trace, the hours it takes to onboard suppliers, the percentage of events with verified signatures, and our PCF coverage rate.
B. 6-step production rollout (180 days)
- Standards and schemas: We're looking at EPCIS 2.0 along with Digital Link, VC credential catalog, and the DPP/DSCSA/CBAM field dictionary. Check it out here.
- Identity and trust: This includes the DID/VC issuer registry, certificate policies, revocation lists, and a QR resolver. More details can be found here.
- Data exchange: You'll want to pick a data space operator, maybe something like Cofinity‑X‑style, or you could go ahead and deploy EDC. Don’t forget to define some bilateral policies, too. Check out more here.
- Ledger strategy: Think about using a permissioned chain for audit anchoring, and if you need cross-ecosystem verification, plan for L2 or public anchoring. Dive deeper here.
- Ops and governance: You’ll want to establish onboarding SLAs, a fee model, rules for data quality, and incident playbooks.
- Expansion: Plan to add new suppliers and markets every quarter, and enhance PCF/ESG coverage along with consumer experiences through QR codes.
Sector-specific playbooks
Automotive and batteries
- Get on board with Catena‑X for smooth data sharing, PCF verification, and DPP alignment. Some automakers, like BMW, are incorporating Catena‑X readiness into their supplier onboarding process, aiming for 2025. (bmwgroup.com)
- Align your passport model with the EU Battery Regulation Article 13/77 data; make sure you’ve got your QR code and unique identifier ready by February 18, 2027. You might want to try a pilot for rough-to-polished trace or component-level genealogy, kind of like Tracr’s method for verifying diamonds--just tailored for cells, modules, and packs. (eur-lex.europa.eu)
Food and retail
- When it comes to EPCIS in the cold chain, the leaf and produce pilots really need to show off that sub-5 second traceback and help us scope out SKU and lot recalls. It's a good idea to use the GS1 Digital Link QR codes to pull up details about origin, harvest, and quality controls. Plus, studies on consumer willingness to pay (WTP) suggest that having solid traceability can justify those price premiums. Check out more on this here.
- Get ready for 2D at the point of sale! This means upgrading scanners, refreshing pack artwork, and enhancing digital content to stay in sync with GS1 Sunrise 2027. You can find more info about this here.
Luxury and CPG
- DPPs using NFC/QR on a large scale really can work (think Aura with 50-70M+ items). By combining anti-counterfeit measures with repair and ownership credentials, we can open the door to circular services and verified resale options. (cointrust.com)
Pharma
- The DSCSA interoperability and verification process now comes with solid staggered deadlines extending up to 2026. Make sure to leverage VCs for authorized trading partner credentials, and don’t forget about using blockchain to keep those audit trails secure. (fda.gov)
Architecture pattern that avoids common traps
- Off-chain truth, on-chain proof: Keep your operational data tucked away in your systems or data space. Publish those tamper-evident commitments (like hashes), credential registries, and process checkpoints to a permissioned chain. This approach helps you maintain low costs and privacy while making sure everything is auditable. Check it out for more details at IBM Research.
- Verifiable Credentials everywhere: Go ahead and issue credentials for supplier identities, facility certifications, forced-labor risks, and PCFs. Use BBS or ECDSA-SD techniques to share only what’s needed during those audits or customs clearances. For more info, take a look at W3.org.
- Interop first: Get on board with EPCIS 2.0 for event semantics, PACT v3 for PCFs, GS1 Digital Link/2D for on-pack info, and the Dataspace Protocol for policy enforcement. Steer clear of proprietary schemas that could leave you stuck later on. For more insights, visit GS1.org.
Two minimal, production‑friendly payloads
EPCIS 2.0 ObjectEvent (with condition monitoring):
EPCIS 2.0 introduces ObjectEvents that are super handy when it comes to tracking the condition of items throughout their supply chain journey. Here’s a breakdown of what you need to know:
What is an ObjectEvent?
An ObjectEvent is a specific type of event in the EPCIS standard that captures information about the physical movement or status of an object. Think of it like a digital breadcrumb trail that lets you keep tabs on where an item is and how it’s doing.
Key Features of ObjectEvent
- Identification: Each ObjectEvent is tied to a unique identifier for the item. This could be something like a serialized number or a barcode.
- Condition Monitoring: This is where things get interesting! With condition monitoring, you can track specific parameters related to the object’s status, like temperature, humidity, or other environmental conditions that could affect the product.
- Event Types: There are several types of ObjectEvents, such as:
- Capture when an item is created, modified, or destroyed.
- Monitor changes in condition (like temperature fluctuations).
- Time Stamps: Every ObjectEvent has a time stamp, so you’ll know exactly when an event occurred.
Example Data Structure
Here’s a quick look at what an ObjectEvent might look like in JSON format:
{
"eventTime": "2023-10-21T14:30:00Z",
"epcList": [
"urn:epc:id:sgtin:1234567.890123.4567"
],
"action": "ADD",
"condition": {
"temperature": {
"value": 5,
"unit": "Celsius"
},
"humidity": {
"value": 60,
"unit": "Percent"
}
},
"bizStep": "shipping",
"disposition": "inTransit"
}
Benefits of Using ObjectEvent with Condition Monitoring
- Real-Time Tracking: You get live insight into the status of your items.
- Improved Quality Control: By monitoring conditions, you can take action if something goes awry before it turns into a bigger problem.
- Enhanced Traceability: With the detailed records you keep, you can easily trace back through the supply chain if any issues come up.
For more details on the EPCIS 2.0 standard, check out the official documentation here.
Utilizing ObjectEvents can really elevate your supply chain management, ensuring that you have the right info at your fingertips when you need it!
{
"type": "ObjectEvent",
"eventTime": "2025-11-30T14:22:05Z",
"eventTimeZoneOffset": "+00:00",
"epcList": ["urn:epc:id:sgtin:0037000.12345.400"],
"action": "OBSERVE",
"bizStep": "shipping",
"disposition": "in_transit",
"readPoint": {"id": "urn:epc:id:sgln:0037000.00729.0"},
"bizLocation": {"id": "urn:epc:id:sgln:0037000.12345.0"},
"sensorElementList": [{
"sensorMetadata": {"time": "2025-11-30T14:21:58Z"},
"sensorReport": [{"type": "gs1:Temperature", "value": 3.8, "uom": "CEL"}]
}]
}
Powered by EPCIS 2.0 and GS1 identifiers for seamless interoperability. (gs1.org)
VC 2.0 Attestation for “ForcedLaborRiskAssessment” with Selective Disclosure:
Overview
In the world of digital credentials, VC 2.0 (Verifiable Credentials) serves as a powerful tool to provide trustworthy information without revealing more than necessary. This is especially important when it comes to sensitive topics like forced labor.
What is Forced Labor Risk Assessment?
The Forced Labor Risk Assessment helps organizations evaluate their supply chains and practices to identify any potential risks related to forced labor. This assessment can be crucial for ensuring ethical standards are upheld.
Why Selective Disclosure?
Selective disclosure allows individuals to share only the parts of their credentials that are relevant to a specific situation. This way, sensitive information remains protected while still proving compliance with standards or regulations.
Key Features
- Precision: Only the necessary information is disclosed.
- Privacy: Sensitive data remains confidential.
- Trust: Builds confidence among partners and consumers.
Benefits
- Enhanced Credibility: Organizations can showcase their commitment to ethical practices without compromising privacy.
- Improved Compliance: Meet regulations while protecting sensitive information.
- Risk Mitigation: Proactively manage forced labor risks in supply chains.
Conclusion
The VC 2.0 attestation for “ForcedLaborRiskAssessment” with selective disclosure is a game-changer. It not only helps organizations demonstrate their commitment to ethical practices but also safeguards sensitive information, making it easier to navigate the complexities of today’s supply chains.
{
"@context": ["https://www.w3.org/ns/credentials/v2", "https://example.com/traceability/v1"],
"type": ["VerifiableCredential", "ForcedLaborRiskAssessment"],
"issuer": "did:example:auditor-123",
"validFrom": "2025-10-01T00:00:00Z",
"credentialSubject": {
"id": "did:example:supplier-456",
"factoryId": "CN-HEB-00042",
"commodity": "aluminum",
"riskLevel": "low",
"assessedOn": "2025-09-20"
},
"proof": {
"type": "BbsBlsSignature2020",
"created": "2025-10-01T00:00:00Z",
"verificationMethod": "did:example:auditor-123#keys-1",
"proofPurpose": "assertionMethod",
"proofValue": "..."
}
}
Use BBS/SD to show just the riskLevel and commodity when doing import checks. Let's keep the factoryId under wraps unless it's absolutely necessary to escalate. (w3.org)
KPI menu that boards care about
- Time-to-trace (SKU/lot to origin) goal: We’re aiming for under 5 seconds during production. Benchmarks indicate this is totally doable. (public.walmart.com)
- Percentage of lots that come with verifiable credentials (UFLPA/DPP/ISO)
- Reduction in recall scope compared to baseline (units/$ at risk)
- Coverage and verification rate of PCFs (we want PACT‑conformant PCFs shared) (docs.carbon-transparency.org)
- Supplier onboarding should take days instead of weeks, thanks to standardized connectors and VC‑based onboarding. (lfdecentralizedtrust.org)
Vendor evaluation checklist (use this to save months)
- Standards: Are we looking at support for Native EPCIS 2.0, GS1 Digital Link, PACT v3, and W3C VC 2.0? What do the roadmap dates look like? Check out more on this at gs1.org.
- Data Control: What’s the deal with Dataspace/EDC, policy enforcement, and auditability? And what about exit options? Get the details over at catenax-ev.github.io.
- Identity and Privacy: How are we handling DID methods, selective disclosure (like BBS/ecdsa-sd), and revocation status lists? Find out more at w3.org.
- Performance and Ops: Can we prove 24×7 operations? Do we have TPS demonstrated (if necessary) and evidence from similar deployments (for example, XCEED’s 500 TPS)? Dive into the details at ibm.com.
- Regulatory Mappings: How do we align with DSCSA, Battery Passport Article 77, CBAM reporting, and UFLPA due diligence data structures? More info is available at fda.gov.
Budget and timeline realism
- You can pull off a 12-week pilot for one product family with 3-5 suppliers using off-the-shelf EPCIS, a hosted permissioned ledger, and a managed resolver for GS1 Digital Link.
- If you're looking at a production program that spans multiple countries with 50-200 suppliers, expect it to take around 6-12 months if you:
- Recycle supplier identities through VCs;
- Leverage a dataspace for entitlements;
- Roll out POS/2D upgrades and on-pack QR codes alongside your ERP/MES integrations. (t-systems.com)
Common failure modes--and how to avoid them
- "Build it and they will come" platforms: Without some solid governance, shared savings, or a little push from compliance, participation can hit a wall. It helps to pin down a regulatory deadline (think DSCSA or Battery Passport) and link your ROI to things like reducing recalls, speeding up customs clearance, or avoiding CBAM costs. (maersk.com)
- All data on-chain: Dumping everything on-chain can expose sensitive info, slow things down, and clash with privacy rules. Instead, keep data sovereign and just put the necessary proofs or credentials on-chain. (catenax-ev.github.io)
- Proprietary schemas: Getting locked into proprietary schemas can really stifle network effects. Stick with options like EPCIS, PACT, VC 2.0, or the GS1 Digital Link. (gs1.org)
What decision‑makers should do this quarter
- Choose a product or market that's really buzzing right now, like leafy greens, EV battery components, or aluminum/steel.
- Get a 12-week pilot rolling that includes EPCIS, VCs, QR codes, and anchoring.
- Make it a requirement in RFPs to adopt standards and a data-sharing approach.
- Set some ambitious goals for 2026: aim for 80% of lots featuring VCs, keep trace times under 5 seconds, ensure PACT-compliant PCF exchange with the top 50 suppliers, and get ready for 2D POS. (docs.carbon-transparency.org)
If you're looking for a practical plan that fits your needs, 7Block Labs can set up a pilot that meets industry standards, help you onboard your first suppliers, and provide you with playbooks that your team can easily follow.
Sources and further reading
- Walmart/IBM Food Trust is testing the waters with a new requirement for leafy greens, promising traceability in just 2.2 seconds. Check it out here.
- Carrefour is diving into blockchain for traceability and bringing consumer value to the forefront. You can read more about it here.
- De Beers is making strides with its Tracr platform, focusing on scale and verification. Learn more here.
- The Aura Blockchain Consortium is already making waves, surpassing 50 million registered luxury products. Discover the details here.
- Renault is rolling out its XCEED performance, and you can get the scoop here.
- BMW is piloting its PartChain and expanding its reach--find out what’s happening here.
- Unfortunately, TradeLens is winding down, and you can read the rationale behind it here.
- we.trade has officially shut down, and if you’re curious about its funding history, check it out here.
- The FDA has outlined the enforcement staging for DSCSA--find all the details here.
- The UFLPA 2025 enforcement will focus on certain priority sectors--get the specifics here.
- EU Battery Regulation is rolling out new battery passport and QR requirements starting February 18, 2027. Read more here.
- CBAM transitional reporting is in place, with payments set to start in 2026--find the details here.
- The ESPR DPP timeline and the working plan for 2025 are laid out--check it out here.
- GS1 EPCIS 2.0 and Digital Link are officially coming into play with a target date of 2027. Get the scoop here.
- W3C VC 2.0 is all about selective disclosure cryptosuites. Learn more here.
- The PACT Technical Specs v3 is rolling out with a focus on PCF exchange--check it out here.
- Catena-X is establishing dataspace principles and connectivity standards. Find more information here.
Like what you're reading? Let's build together.
Get a free 30-minute consultation with our engineering team.
Related Posts
ByAUJay
Building Supply Chain Trackers for Luxury Goods: A Step-by-Step Guide
How to Create Supply Chain Trackers for Luxury Goods
ByAUJay
Building 'Private Social Networks' with Onchain Keys
Creating Private Social Networks with Onchain Keys
ByAUJay
Tokenizing Intellectual Property for AI Models: A Simple Guide
## How to Tokenize “Intellectual Property” for AI Models ### Summary: A lot of AI teams struggle to show what their models have been trained on or what licenses they comply with. With the EU AI Act set to kick in by 2026 and new publisher standards like RSL 1.0 making things more transparent, it's becoming more crucial than ever to get this right.

