Performance Improvements
Several improvements to save gas fees and increase finality speed
Batch Inscription
Multiple co-processor transactions can be inscribed into a single Bitcoin transaction to save gas fees. In this way, each co-processor transaction only requires about 1/4 of the gas fee compared to a Bitcoin transaction because all of its data is stored in the witness.
Any third party can be a batch builder, receiving co-processor transactions and inscribing them into a Bitcoin transaction. This will increase the finality speed of co-processor transactions. For example, you can create a Uniswap on Bitboost and then maintain a batch builder for receiving all the transactions that interact with the Uniswap. In this way, you sequence these Uniswap transactions and provide instant finality, just like a sequencer in rollups.
Transaction Compression
Co-processor transactions can be further compressed like rollup transactions. This will reduce the transaction size to 12 bytes, which is approximately 1/10 of its original size. So, overall, the gas fee for a Bitboost transaction can be as low as about 1/40 of a Bitcoin transaction.
OP_RETURN
After compressing co-processor transactions to 12 bytes, storing them in an OP_RETURN output becomes feasible. The OP_RETURN can hold a maximum of 80 bytes of data, which is sufficient for 6 transactions. Additionally, users do not need to create two Bitcoin transactions (commit and reveal) to publish a co-processor transaction. After all, the transaction structure will look like this.
Note that if the Data's size is very large, for example, a transaction creating or calling a smart contract, storing it in the OP_RETURN may become expensive or even infeasible. Therefore, we will make OP_RETURN as an option, allowing users to freely decide whether to publish their transactions in the witness or OP_RETURN based on the transaction size.
Last updated
