[Bitcoin-ml] OP_Codes

[Joshua]

Hi all,

The interpreter code for the new opcodes is located on the bitcoin-abc phabricator instance at https://reviews.bitcoinabc.org/D1090. You can follow up through the related diffs by using going to the Revision Contents table and then clicking on Stack.

If you prefer Github I've got a personal repo located here (https://github.com/joshuayabut/bitcoin-abc/commits/enable-opcodes-rc5) with the commits so far... We've got the scripting engine and unit tests implemented already. Please keep in mind the code is still under review and it is still lacking an activation mechanism (which I am currently working on).

One thing that I think that may need to be worked on in the future is the benchmarking of opcode resource utilization; that way tx fees can be calculated in relationship to resource usage.

I think we're all re-experiencing the decentralized nature of Bitcoin development so I'm open to any and all comments/suggestions in order to expedite upgrading bitcoin.

As far as security issues are concerned, I get it... it's being factored throughout the development process as far as I can tell.

Contribution Guidelines here: https://github.com/Bitcoin-ABC/bitcoin-abc/blob/master/CONTRIBUTING.md

-Josh

Sent from [ProtonMail](https://protonmail.ch), encrypted email based in Switzerland.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On February 23, 2018 4:50 PM, George Macoukji via bitcoin-ml <bitcoin-ml at lists.linuxfoundation.org> wrote:

> I've already spotted an issue with the OP_CAT documentation. I'm not hugely familiar with Github. How do we report issues most effectively? With normal code, we can just open an issue or comment directly on the line in question.
>
> --
> "I got an "A" in philosophy because I proved my professor didn't exist."
>             -- Judy Tenuta
>
> On Fri, Feb 23, 2018 at 12:10 PM, G. Andrew Stone via bitcoin-ml <bitcoin-ml at lists.linuxfoundation.org> wrote:
>
>> Here are the current opcode specifications.  We would certainly appreciate your critical review for security flaws.
>>
>> OP_CAT, OP_SPLIT, OP_AND, OP_OR, OP_XOR, OP_DIV, OP_MOD, OP_BIN2NUM, OP_NUM2BIN:
>> https://github.com/shadders/uahf-spec/blob/reenable-op-codes/reenable-op-codes.md
>>
>> OP_DATASIGVERIFY:
>> https://github.com/gandrewstone/BitcoinUnlimited/blob/op_datasigverify/doc/opdatasigverify.md
>>
>> OP_GROUP:
>> https://github.com/gandrewstone/BitcoinUnlimited/blob/opgroup_fullnode/doc/opgroup-tokens.md
>>
>> On Fri, Feb 23, 2018 at 4:01 AM, Alexey Eromenko via bitcoin-ml <bitcoin-ml at lists.linuxfoundation.org> wrote:
>>
>>> Thats why I requested info per every op code, are there "dangerous " ones, that have downsides?
>>>
>>> On Fri, 23 Feb 2018 at 6:47 Amaury Séchet <deadalnix at gmail.com> wrote:
>>>
>>>> The downside depends on op_codes. Maybe you have question about specific op_codes ?
>>>>
>>>> 2018-02-23 1:54 GMT+01:00 Alexey Eromenko via bitcoin-ml <bitcoin-ml at lists.linuxfoundation.org>:
>>>>
>>>>> What are the downsides for each OPCODE enablement ?
>>>>>
>>>>> _______________________________________________
>>>>> bitcoin-ml mailing list
>>>>> bitcoin-ml at lists.linuxfoundation.org
>>>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-ml
>>>
>>> --
>>> -Alexey Eromenko "Technologov"
>>>
>>> _______________________________________________
>>> bitcoin-ml mailing list
>>> bitcoin-ml at lists.linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-ml
>>
>> _______________________________________________
>> bitcoin-ml mailing list
>> bitcoin-ml at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-ml
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-ml/attachments/20180223/63a56cbf/attachment.html>