Join GitHub today
Remove reliance on OP_DATASIGVERIFY and simplify assert scripts #6
The original assert script was designed to accommodate features given in early development. The design is no longer required.
Proposal: We change assert scripts to
A token-p2pkh would then be
This would allow recursive smelting to have more tight overlay the traditional bitcoin transactions and simplify the parsing of outputs (in turn simplifying proofs).
In addition this should allow easier integration with existing wallets. Wallets can function as is with the only change being that the quantity is queried from the token "quantity" in output script rather than the transaction "quantity" in the transaction output itself.
referenced this issue
Aug 11, 2018
Yep. So most of the implementation should be relatively easy - the token transactions are simply Bitcoin transactions with an extra condition supplemented to the pubkey/script signatures (see OP). Therefore most of the infrastructure for this already exists in wallets today!
The key ingredient is creating the backend to generate and verify proofs used in RS. And this is what we're hard at work at currently. We aim to create a library to do this which existing wallets can interface with easily and add token support with very little change to existing code.
The aim is to fork an existing wallet, write up a reference interface with the proof library and then let other wallets replicate it if they please.
Luckily great open-source libraries already exist from generating and verifying proofs:
We are in the very early stages - producing candidate OCaml scripts at the moment and brainstorming. We hope to get a repository containing at least some rough drafts in the upcoming weeks. We are optimistic but realise that this first hurdle is the highest.