Author: Natanael 2014-02-20 07:50:51
Published on: 2014-02-20T07:50:51+00:00
The use of oracles in P2SH addresses with 2-of-3 signatures requires pregenerating transactions for both outcomes in advance, which the oracle may not want to share before the event occurs. To solve this issue, the oracle can share a transaction hash in advance and provide a Zero-knowledge proof of that transaction's adherence to agreed-upon rules, allowing the full tree of transactions to be pregenerated. The oracle then releases one of the possible transactions after the event occurs, allowing the broadcast of the chosen chain. However, this method becomes impractical when the number of possible outcomes is too high as it would require the generation and storage of a massive outcome tree.Meanwhile, a "only-mine-with-child flag" can address issues with broadcasting pre-generated subchains separately by making parent transactions invalid unless spent together with their dependent transactions. This method requires all miners to respect it at once to avoid network forking. Changes to transaction versions are intended to provide non-malleability guarantees for clients willing to restrict their functionality, but they should not outlaw malleability as there are intended use cases for it. It is also noted that soft forks are easier to implement than hard forks, which would require more extensive modification of software.
Updated on: 2023-06-08T02:44:27.788993+00:00