Topic: 3DPass: Directly Storing 3D Objects on the Blockchain – A New Era for RWAs? (Read 95 times)

Thanks for backing me up! I was convinced, there were supposed to be something to it 

Let me put my two cents in by answering the question 

It didn't work because the network must take ultimate responsibility for each and every block/asset on the blockchain, which neither of single nodes/individuals can take. And this could not be fulfilled without having the whole bunch of data (proofs included) sealed into the Merkle tree. So it becomes irrefutable evidence proved by math.

The bottom line is that if we want the network to take responsibility for the asset authenticity, it must be stored on the blockchain and sealed into the block header by the block author. https://3dpass.org/features#ledger-why-1node-1vote

And if the asset owner takes 100% responsibility himself (no guarantee for public), he can store the  object wherever he likes. Having the HASH ID (the object identity) stored on the blockchain would be enough in the case.

3Dpass consensus Proof of Scan is based on recognition function instead of regular hashing. So, the network is capable of the object properties processing and thus it can take responsibility for the object authenticity (not to mistake with the file authenticity). Which none of the existing L1 blockchain platforms can provide.


 

That's an arguable point, whether it is pointless to store. imho
In PoW miners are finding new blocks, but they store "nonce" one the blockchain (proof is part of the blockchain).
Every block represents a piece of value, as well as the user object in 3Dpass does.

Miners could have stored proof of work somewhere outside of the blockchain. Why didn't it work this way?

The first part is already provided by the 3DPass blockchain in an immutable and trustless way. A sufficiently large community with many nodes would, of course, also be a mitigation, which is what 3DPass is striving for. See also my post on the Proof of Scan v2 upgrade that makes it Pool/ASIC/FPGA resistant to have as many nodes/miners on the network. You can read more in this thread https://bitcointalksearch.org/topic/3dpass-proof-of-scan-v2-first-pool-resistant-protocol-5509550

A future problem could, of course, be the very large database with respect to scaling up, as well as the cost element, since 3DPass is more interested in everyday users rather than huge institutions that could easily pull this off.

Having another storage focused blockchain could very well be an option or solution to address this.

If so a blockchain of its own is needless "bloat"; one could simply offer customers a range of costs of existing, expected to be secure chains on which to record a cryptographic proof, no need to store entire object, owner of object can retain actual object / 3D-file as long as they feel they need, holding also along with it algorithm / program that creates the algorithmic proof given the actual file.

Some customers might choose to have their proof written to bitcoin blockchain, others maybe even also to various other chains as redundancy.

-MarkM-

If my understanding right, the object authenticity verification service is the primary one in 3Dpass: https://3dpass.org/3DPass_white_paper.pdf  So, the storage fee is considered secondary, even after the mining period is finished.

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.

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-

I'm excited to share that 3DPass now enables the direct storage of actual 3D files on the blockchain and not just a random URL link to somewhere else as Elon Musk joked.

This is not just a concept or theory, In a recent video, I demonstrated this by creating an elephant head model with Meshy.ai (free credits provided), optimizing it from 4 MB to under 100 KB using MeshLab. The reason for the 100 KB is that this is the 'current' limit on what 3D files can be stored directly on the blockchain. I then uploaded and tokenised it on the 3DPass blockchain via the official app.

See the vid on my X/twitter under https://x.com/A_mo1111_/status/1835695740577849687

The 3DPass recognition algorithm checks that there isn't such an item on the blockchain already. For example no-one else should be able to upload such an Elephant head going forward therefore also counterfeit proof.

This advancement opens up new possibilities for artists, creators, and every day users to protect and authenticate their 3D works as well as real world assets (RWAs). The tools I used are free, and it costs less than $0.50 worth of P3D to upload and tokenize a 3D item. While there's currently a 100 KB file size limit, this is expected to increase to 1 MB for even fancier models.

What do you think about storing 3D assets directly on the blockchain? Which industries could benefit the most, and are there any challenges you foresee?

This thread is not aimed at price speculators but rather tech minded people, I'm looking forward to your insights, discussion and challenges.