there are different flavors of ark that use CTV and CSFS to reduce the interactivity for the user
https://delvingbitcoin.org/t/evolving-the-ark-protocol-using-ctv-and-csfs/1602
for me this is a critical requirement. ark is gimped without at least CTV
This whole spectacle that Ark is "gimped" without a covenant is way over the top.
Yes, Ark can be better with covenants. In fact, at nostr:npub1hf5sgehj874r3y2hps9r36qap20cffauc7t895var2ajlsg32mcqa7dp8n we have both variants developed and concluded that a covenantless variant today is not only viable, but can exceed expectations through the right optimizations and engineering. We have a path for multiple hundreds of vtxo creation in a single commitment transaction while keeping the interactivity at an acceptable level.
We also have paths of varying methods to mitigate the approaching expiry dilemma.
Ark does not need covenants. It is FUD to state otherwise. You'll see soon enough though!
When you say multiple hundreds, let's say 600 transactions per tx, is that on average per 10m (per block), i.e. 1 tx/s?
Are there other upper bounds (or isn't this one?)?
No, this doesn't refer to the typical tps measurement used by blockchains.
I refer to the pragmatic upper bound for creation of new vtxos within a single onchain tx.
This bound is mostly defined by interactivity rounds between participants to construct the covenant. Since we do not have introspection covenants, we use a a series of n-of-n musig transactions. More vtxos = more interactivity.
We've had a functional ark for bitcoin for almost a year now, and since then we've optimized heavily along with plans to go even further. We have methods to achieve the above in concurrency, so that even with a single onchain transaction, we can create higher vtxo counts, without increasing interactivity for each VTXO owner.
In terms of "tps", I would say it is similar to lightning in that we have offchain instant transactions, but with actual transaction composability -- just craft a bitcoin transaction, sign, and submit.
There is of course no free lunch: one must swap their existing vtxos for new ones that are created with the commitment transaction (covenant session) described above, a trustless swap through connector outputs, for two reasons:
Batch expiries: these covenants have an expiry that allow the ark operator to reclaim its initial liquidity.
Switching from preconfirmation security (previous owner + ark operator collusion risk) to bitcoin finality (fully under your control). This also prunes the unilateral exit to a minimum tx set for broadcasting to.covnert vtxos to utxos.
