@jam10o is there a mode where a parachain or parathread will do "non-blocking" finality for a chain?
like - the chain just moves on, whatever... but submits blocks to the relay chain and it records it, so "third parties" (e.g. other chains) who trust the relay chain and polkadot more than the parachain in question ...might check what the relay chain has and only accept the parachain blocks or data if it matches what the relay chain says
...but chains who don't mind, they don't care what the relay chain says
...but i find it weird that the parachain has to wait for the relay chain for finality
JAM
@serapath block production and finality are separate
the entire point of Polkadot is to have strong security guarantees about communication between the relay chain and parachains
if you don't want to use finality from the relay chain, you need to bridge, not be a parachain
for the large part, we've made no commitment to actually turn datdot into a parachain
but most of our potential users (of the datdot runtime module, not the datdot client) are prospective parachains
ideally, most people using the client won't care
and the UX would be better if they spun up chains unrelated to polkadot
@todoserapath
JAM