Thanks David that helps a lot in understanding the problem/insight into the limitation of the consensus algorithm. IIUR the Safe Network consensus algorithm forking resolution method is acceptable for storing data securely, but not suitable for guaranteeing unique data, like tokens.
Does this the same limitation prevent the following alternative decentralised method from being implemented where DBC is not actually created by sections?
Method2 (B):
- 100% of SNT are Pre-Farmed
- 30% are airdropped or equivalent to initial stakeholders
- 70% Are managed by the Safe Network consensus algorithm, “sharding”
Sharding method outlined under “DBC Mints” in this Update “Sharding: Each Section is responsible for a subset of DBCs.”.
Or perhaps is it related to complexities @neo posted above, or similar?