This is premised on the following Logic.
If you have a digital template for each item the system is capable of making, Then, when the template is executed a small fee is charged to an account held by the system owner.
Expectations are this fee would be on the order of 2.5-3% of the items value.
There are then 5 main divisions this fee would fund.
- Royalties: The creators of templates, or in the case of derivative work, some fraction would be paid to multiple creators
- Advertisers/Marketing rewards.
- Sales commissions
- Maintenance/Version Releases – each quarter?, bi annually?, annually? All the best innovations of the period would be rolled into a packaged release
- Incentive Fund – in under served areas a financing/training package could get a new system into operation, keeping shipping distances very short
This also re-imagines the utterly annoying NFT concept of the last 10 years Rather than a using a token to store a low quality jpg on the blockchain, (or even a high quality one) what if you used it to store all the design and automation steps to build a dialysis machine? or a set of hand tools? or SOMETHING useful?
This is the stuff that gives crypto a black eye, over and over, poorly conceived applications to the technology rather than socially redeeming use cases.
But blueprints to essential technology should elevate the concept and presents an actual use case with merit and utility value.
A zero fee escrow mechanism at a jobs commencement should discourage cheating.
A multi-option exit status for processed runs, such as (Complete, Partial due to X, Failed, Rejected due to Y, et al) is entirely consistent with the “Machine State” that MTConnect uses to coordinate system level operations and should allow for full to partial funds recovery based on outcomes.
On failure, Logging to a sub-chain for post-op perhaps via pooled storage on “sponsors” can be used to validate status, the same mechanism could enforce QC by triggering support requests. Given that blockchains bring traceability benefits at the expense of considerable overhead, storing the root hash of a sub-chain (Merkle Root) on multiple public chains, rather than attempting maintaining an independent chain is a strong alternative for the near future.