From: "Martin Habovštiak" <martin.habovstiak@gmail•com>
To: Chris Stewart <stewart.chris1234@gmail•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] [Proposal] 64-bit arithmetic in Script
Date: Mon, 12 May 2025 16:32:08 -0300 [thread overview]
Message-ID: <CALkkCJbeAYA2X8jv8iWthKBB8GqxA49DCFm+UMnhmXYpexTNtw@mail.gmail.com> (raw)
In-Reply-To: <CAGL6+mH+9iq5_SR-Fa5zVZRoTpHasX7xoprYeJZRd5D80J1GqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3116 bytes --]
Hi,
the proposal seems to be quite confused about how it's going to do that. It
mentions upgrading existing opcodes, which is a hardfork, not soft fork, at
least without using a different leaf version. But it also mentions
OP_SUCCESSX which are different opcodes. I think it needs some analysis.
(leaf version seems better intuitively)
I'd also love to see analysis why stop at 64 bits and not go all the way to
256 which could be useful for cryptography.
Anyway, pushing amounts on the stack would be great. Though I'm surprised
you're only proposing the sum, not individual outputs. Why?
Good luck!
Martin
Dňa po 12. 5. 2025, 14:21 Chris Stewart <stewart.chris1234@gmail•com>
napísal(a):
> This soft fork proposal extends the range of numeric operands in Script
> from -2^31+1 to 2^31-1, to -2^63+1 to 2^63-1. It further expands the
> result range for arithmetic operations from -2^63 to 2^63-1, to -2^127 to
> 2^127- 1.
>
> All existing opcodes[1
> <https://github.com/Christewart/bips/blob/2025-03-17-64bit-pt2/bip-XXXX.mediawiki#cite_note-1>
> ] that interpret stack elements as numbers are upgraded to support 64-bit
> parameters.
>
> The existing number encoding format[2
> <https://github.com/Christewart/bips/blob/2025-03-17-64bit-pt2/bip-XXXX.mediawiki#cite_note-2>
> ] and arithmetic semantics[3
> <https://github.com/Christewart/bips/blob/2025-03-17-64bit-pt2/bip-XXXX.mediawiki#cite_note-3>
> ] from the original Bitcoin implementation are preserved, while enhancing
> the supported precision.
>
>
> https://github.com/Christewart/bips/blob/2025-03-17-64bit-pt2/bip-XXXX.mediawiki
>
> The purpose for this BIP is to lay the groundwork for introducing amounts
> into Script. This document takes no opinion on how this is done.
>
> I've prototyped a few different proposals now introducing amount locks
> into Script[0][1] and feel like this proposal is stable enough for serious
> review.
>
> -Chris
>
> [0] - https://delvingbitcoin.org/t/op-inout-amount/549/4?u=chris_stewart_5
>
> [1] - https://delvingbitcoin.org/t/op-inout-amount/549/5?u=chris_stewart_5
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Bitcoin Development Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to bitcoindev+unsubscribe@googlegroups•com.
> To view this discussion visit
> https://groups.google.com/d/msgid/bitcoindev/CAGL6%2BmH%2B9iq5_SR-Fa5zVZRoTpHasX7xoprYeJZRd5D80J1GqA%40mail.gmail.com
> <https://groups.google.com/d/msgid/bitcoindev/CAGL6%2BmH%2B9iq5_SR-Fa5zVZRoTpHasX7xoprYeJZRd5D80J1GqA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CALkkCJbeAYA2X8jv8iWthKBB8GqxA49DCFm%2BUMnhmXYpexTNtw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 4896 bytes --]
next prev parent reply other threads:[~2025-05-12 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 16:15 Chris Stewart
2025-05-12 19:32 ` Martin Habovštiak [this message]
2025-05-13 9:03 ` Chris Stewart
2025-05-13 11:44 ` Christian Decker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALkkCJbeAYA2X8jv8iWthKBB8GqxA49DCFm+UMnhmXYpexTNtw@mail.gmail.com \
--to=martin.habovstiak@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
--cc=stewart.chris1234@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox