Looking at your repository, I find omni interesting as a protocol to bookmark all blockchains, I have a few questions
1. everyone can use the synchroniser, so how is the synchroniser incentivised, as it seems that proof submission requires gasfee
2. you mentioned that btc and evm including polkdot are synchronised at the same time, so I submit a transfer tx on btc and then I have to wait for 10 mins right, isn't that very inefficient of him then
3. also, i have doubts about its security as the sync seems to be run by everyone, so can i run a lot of sync and then do a double spend
There is also the question of whether users need to submit their own nonce if they make a transfer on bitcoin, and then whether this is a bad place to work out because people don't know what the current nonce is, and the nonce overlap or even the transaction will fail. So wouldn't this protocol be very inconvenient to transfer token on bitcoin? Looking forward to your answer.
Hey pc9527zxx,
Nice questions.
1. when submitting the transactions onto different chains, the gas fee is a concerned problem. And this is why we are developing an Execution Layer (zk-based) to make rollups currently. Here we just focus on the protocol itself.
2. basically, the second question is the second point when making a product, an Execution Layer (we may call it a special layer2) is important. What you concern, the inefficiency, is what we concern too.
3. the double-spend attacks can be detected by verifiable fraud-proof, as the same input is spent twice associating to different outputs, and as the signature is non-repudiation, it will be detected. But the cost is the necessary waiting time.
the last question is about the `nonce`.
if we use the account-based model, the `nonce` is necessary. And this is one of the reasons why now we are trying the UTXO-based version of the
protocol.
According to your question about the `nonce` itself, as the account-based model is managed by smart contracts, when users submit a new transaction, they can get their working nonce on any chain where the protocol is deployed.