01
DESIGN
GCODE
GCODE
AES-256
IPFS
bafy…7e2a
bafy…7e2a
HASH
ON-CHAIN
ON-CHAIN
[ ENCRYPT ]
Anchor the design
Encrypt every design, move the payload to IPFS, and commit only its CID and hash on-chain.
Introducing ProofMesh: physical print verification on-chain.Learn more
The Trust Layer
for 3D Printing.
A blockchain-secured control plane for printer fleets, protecting design IP, authorizing every job, and proving every physical run.
read the implementation planAES-256IPFS CIDBLOCK 18,492
“We don't just store a log. We can prove the log is true without trusting the machine or its operator.”
THE CORE GUARANTEESnapshot-commitment verification
[ PROTOCOL ]
How Rubyx secures every print
Every critical action moves through a verifiable chain, from encrypted design upload to an immutable final verdict.
HOW IT WORKS
02
OPERATOR
AUTHORIZED
AUTHORIZED
JOB
CONTRACT
CONTRACT
P-01 BUSYP-02 READYP-03 IDLE
ASSIGNED → P-02[ AUTHORIZE ]
Coordinate the fleet
Smart contracts approve the operator, reserve an available printer, and record every transition.
03
LIVE SENSOR TRACE
t03t09t14
REFERENCE MATCH20 / 20
VERDICT · VERIFIED[ VERIFY ]
Prove the outcome
Secret sensor samples and geometry checks produce a verdict the operator cannot rewrite.
[ DETECTION ]
Catch every kind of tampering
From forged completion signals to swapped payloads and failed geometry checks.
THREE JOBS THAT SHOULD NEVER REACH PRODUCTION.
☆ 01⑂ JOB_84VERIFIED
▱ encrypted/design_1.gcode
RUBYX
Legitimate production run
Every committed snapshot matches the expected printing envelope.
20 / 20
☆ 02⑂ JOB_85TAMPERED
▱ encrypted/design_2.gcode
RUBYX
False completion signal
Idle telemetry exposes a forged job before payment can unlock.
SAMPLE 07
☆ 03⑂ JOB_86REJECTED
▱ encrypted/design_3.gcode
RUBYX
Modified design payload
The received ciphertext fails its ledger commitment before execution.
HASH ≠
[ PRIVATE BY DESIGN ]
Your design. Your rules. Your proof.
Confidential manufacturing data stays private while its integrity remains independently verifiable.
DESIGN.GCODE12.8 MB
AES-256
IPFS CIDbafy...7e2a
[ PAYLOAD PROTECTION ]
Secrets stay off-chain
Only encrypted payloads leave the client. The ledger receives integrity anchors, never the source design.
3 verified roles
ADMINGRANT
CLIENTUPLOAD
OPERATOREXECUTE
[ ACCESS CONTROL ]
Every action has an owner
Contract-level role checks gate every state-changing call before the fleet receives it.
[ YOUR STACK ]
The Central Validation Layer.
One coordinated system joins the operator interface, edge gateway, private storage, printers, and immutable ledger.
See the proof01 / 04
01Fleet dashboard
Live printers, job state, verification results
02 / 04
02Gateway + API
Authentication, encryption, scheduling, sampling
03 / 04
03Off-chain data
Encrypted payloads and private sensor evidence
04 / 04
04Ethereum ledger
Roles, commitments, lifecycle events, verdicts
[ PROOFMESH ]
Autonomously Verify Every Print
Secret sampling catches false jobs and missed edge cases.
Explore the methodCOMMIT
Lock the sample plan
H(seed + times)
0x8e4f…c219Publish the commitment before the printer starts. The sample times remain secret.
SAMPLE
Observe the real job
t03t09t14
Capture power, thermal, filament, and geometry evidence only at committed moments.
REVEAL
Open the schedule
[ 03, 09, 14 ] COMMITMENT MATCHReveal the seed after execution so anyone can reproduce and verify the sample plan.
VERIFY
Finalize the verdict
20 / 20SNAPSHOTS VALID VERIFIED
The contract records one immutable result and unlocks the authorized next action.
[ SECURITY-FIRST DESIGN ]
Built for sensitive manufacturing
Independent controls protect intellectual property, prevent unauthorized execution, and keep the full lifecycle queryable.
Hash-anchored integrity
Every file is checked against its on-chain commitment before a printer can execute it.
Private by default
CAD and G-code stay encrypted off-chain; only compact integrity anchors reach the ledger.
Role-bound execution
Solidity access controls reject unauthorized uploads, assignments, and state changes.
01MONTH 01
Protocol foundation
Freeze interfaces, deploy the local chain, and validate the contract model.
02MONTH 02
Secure pipeline
Connect AES-256, IPFS, contracts, printer simulation, and telemetry datasets.
03MONTHS 03-04
Physical verification
Build secret sampling, geometry checks, scheduling, and fleet monitoring.
04MONTHS 05-06
Integrated proof
Exercise tamper scenarios, measure the system, and deliver the complete MVP.
[ TECHNICAL FAQ ]
Questions,
answered.
The short version of how Rubyx handles trust, privacy, physical proof, and prototype scope.
The ledger gives authorizations, schedule changes, file commitments, and verification verdicts one shared timestamped history that no operator can silently edit.