Quote from: markm on Today at 11:28:17 AM

Seems like paying for storage could end up being a problem...

Even if you store stuff on some kind of filecoin type functionality and had your UTXOs on your blockchain hold staked coins enough to pay for storage indefinitely of the actual data linked to, what if whatever you are staking loses value enough that its staking earnings no longer cover the storage fees?

Maybe if there is a filecoin type thing that has staking and its staking can be depended on for foreseeable future (decades, centuries, whatever, the kind of spans over which e.g. bitcoin's blockchain should need to always be stored live and accessible to the entire internet), you could somehow wrap that filecoin's tokens onto your blockchain to provide a stake with each link? Or convince a stakeable-coin filecoin of some kind to support your application, or just go ahead and use it to implement your application like third party extra layers manage to make use of bitcoin?

-MarkM-

Great comment and I think there is different aspects to consider when it comes to the data starting with the local processing .

All 3D data is processed locally on your device through the 3DPass app, utilising RAM to ensure that no raw 3D data is uploaded or stored externally without your consent. By processing data locally, we eliminate the risk of transmitting sensitive 3D information over the internet, preserving the privacy of your scanned objects.

Instead of storing full 3D models on the blockchain—which could reveal the object's shape—we generate a unique hash ID using our Grid2D recognition algorithm. These hash IDs represent the object's shape without disclosing detailed 3D information, maintaining privacy while ensuring uniqueness kinda like zK. This approach also requires significantly less storage space than full 3D models, keeping the blockchain lean and efficient.

If you choose to store 3D data, IPFS is utilised for decentralized offchain storage. This supports the creation of a public repository for items like monuments and landmarks, where sharing full 3D models can be beneficial. IPFS ensures that stored 3D data is accessible and shareable across the network without burdening the blockchain. When tokenizing an object in P3D, a validation fee covers the verification of uniqueness and storage costs. By paying this fee, you ensure that your object's hash ID and associated data are securely stored and maintained over the long term. It's of course essential to retain the physical object or the original 3D file so it can be rescanned or recreated if necessary.

In terms of storage 3DPass should be good for the short term, for the mid to long term let's see how this develops.

your comment about the storage costs centuries from now does have me thinking whether this initial fee paid is sufficient or whether something else is needed. I will follow up on this.