Q4: Quantum proof
When Q4 arrives, DAG anti quantum proof will be developed and perfected. ~

eneral

This new structure is made to store small pieces of data permanently, decentralized, and accessibly. This data can be used for many types of sitations but most importantly it can be used to store databases presistantly.

Thus our DAG is based on the concept that space on the chain costs 'money', this is necessairy as a preventative method. If we had a 'private' DAG we wouldn't need this construct, but because we want it decentralized and open we'll need to make it autonomous.
If you do not include the appropriate requirements (fees, signatures, transaction/data) it will be considered a invalid unit.

In case there was a huge split (unlikely unless there was a world wide outage) units can be marked as invalid, fees will still apply (if payed properly).
The block still needs to be stored in the database to make sure validation works correctly. We need to find a way to prevent this

The general principle for submitting data is that you use a id to indicate what it's meant to do, some id's will have internal uses, others will only be used by 3rd parties.
Some example of interal ids:


payment/fee
message
mark (wip)
template
vote
comment
subchain


These will be used for the core feature of our DAG, all other ids are free to use by developers/users


Templates

The use any app can described by a template, which is a typescript like class definition, this doesn't have any enforcing use.
This can be used to 'suggest' potential ways to fill in the data of any class. This can be handy for user submitted forms/data on the DAG.
It's also possible to enforce proper input by including a element in the 'app' that points to the template
........



https://git.shieldx.sh/SHIELD-team/Core-Projects/Prototypes/DAG-prototype/tree/master