EDUCATIONAL DEMO Fictional computer parts. Real records on a public test blockchain.
FROM WAREHOUSE TO HANDOFF
Every part. Accounted for.
Follow high-value components from registration to confirmed receipt.
Shipment watch
View all ↗Loading shipment records…
A shared record of each handoff.
Authorized staff register parts and record shipments. Everyone viewing this dashboard can inspect the same confirmed history.
- Register serial-numbered parts
- Group parts into a shipment
- Dispatch and confirm receipt
Latest activity
Open audit trail ↗Loading recorded events…
SERIAL-LEVEL VISIBILITY
Asset inventory
One record per physical component. Use fictional information only.
Registered components
Register an asset
Requires an authorized operator and a wallet confirmation.
Add a correction note
Preserve the original record and append an explanation to its audit trail.
CONTROLLED HANDOFFS
Shipments
Created → Dispatched → Received. Only assigned staff can complete each handoff.
Shipment register
Create a shipment
Choose 1–20 available assets from the same warehouse. Your connected account becomes the dispatcher.
VERIFIABLE HISTORY
Audit trail
Confirmed events from this contract. Open a transaction to inspect it independently.
Failed or cancelled requests do not create contract events. Wallet activity and the explorer may show submitted failures separately.
PEOPLE & PERMISSIONS
Team access
Public viewing. Authorized changes. Separate dispatch and receipt.
Connected account
Connect a wallet to check your permissions.
A wallet identifies the account signing a change. Viewing records does not require one.
Role responsibilities
Administrator: authorize or remove operators.
Operator: register assets, create shipments and add notes. Only a shipment’s dispatcher may dispatch it; only its receiver may confirm receipt.
Manage an operator
Administrator only. For the receiving role, use another wallet you control on Amoy. Never use a temporary Remix VM account address.
CHAINTRACK CAPSTONE
From first part to final receipt.
A practical demonstration for managers and shareholders.
1. Explore without a wallet
The overview, inventory, shipments and audit trail read the deployed Amoy contract. Your audience can watch and follow explorer links without installing MetaMask. This demonstration website is publicly accessible. Viewing records requires no ChatGPT account or blockchain wallet.
2. Register two demo parts
Open this site in the browser with MetaMask installed. Connect your deployment wallet on Amoy. Register CT-GPU-001 (GPU) and CT-CPU-001 (CPU), using fictional model names and Warehouse A. Approve each transaction and wait for confirmation.
3. Authorize a receiver
Create or select a second MetaMask account, switch it to Amoy, and obtain free test POL for its receipt transaction. Copy its public address. Switch back to the administrator and authorize that address in Team access.
4. Group and dispatch
As the first operator, create shipment 1 with the two serial numbers, destination Warehouse B, and your second account as receiver. After confirmation, select Dispatch on the shipment.
5. Confirm the handoff
Switch MetaMask to the assigned receiving account and reconnect if requested. Select Confirm receipt. Both asset records should now show Warehouse B and be available for another shipment. The completed shipment remains in history.
6. Show the evidence
Open Audit trail and follow each transaction link. Explain who authorized the change, the recorded sequence, and why the original records cannot be silently overwritten.
What this demonstrates
Logistics: shared shipment status and accountable handoffs.
Supply management: current warehouse visibility and prevention of double allocation.
Asset tracking: distinct serials, fixed shipment membership and a recorded history.
Cybersecurity: role checks, wallet signatures and append-only correction notes.
What it cannot prove
A blockchain records submitted claims; it does not verify that a physical GPU exists or arrived undamaged. Mistakes and compromised wallets remain possible.
Records are public. Use no customer names, real addresses, secrets or sensitive inventory. Testnet availability and free RPC services are not production guarantees. Gas costs, wallet recovery, privacy and real-world identity need further work.
When something goes wrong
Insufficient funds: use an Amoy faucet for test POL; no real purchase is required.
Rejected change: check your role, the exact serials and shipment state. Increasing gas does not fix a permission or validation error.
Pending: check the transaction link before trying again.
Reload: records live in the contract, independent of this browser. Refresh to read them again.