Bitcoin Development Mailinglist
 help / color / mirror / Atom feed
From: "'Toby Sharp' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: eric@voskuil.org
Cc: 'Bitcoin Development Mailing List' <bitcoindev@googlegroups.com>
Subject: Re: RE: [bitcoindev] Hornet Update: A declarative executable specification of Bitcoin consensus rules
Date: Sat, 18 Apr 2026 22:26:31 +0000	[thread overview]
Message-ID: <--C53DoYZLFJgwz6T6jBLFNjx3dNCZRC06RK981Cj40XsyFGNMf2pX7eiUpG-hzsMXnEIxFFyEWjost7GyuM3xKkvpqj99ODyTQprnl-N1g=@hornetnode.org> (raw)
In-Reply-To: <00b401dccf78$6f5e7a00$4e1b6e00$@voskuil.org>

> It appears that Hornet is missing the rule prohibiting forward references within a block.

This is implied by Rule S02: "A transaction input MUST reference a previous transaction output that remains unspent." However, to make it clearer, I will rewrite it as:

"S02: A transaction input MUST reference a preceding transaction output that remains unspent."

> Otherwise there are potential malleation issues to deal with depending on how blocks/headers are being managed. This can affect consensus behavior (via archival) while not showing up as an issue in these rules.

That would be an implementation correctness detail rather than part of a declarative spec.

The intention here is to specify what must be true for consensus validity rather than how it should be computed.

Best wishes,
T#

-- 
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/--C53DoYZLFJgwz6T6jBLFNjx3dNCZRC06RK981Cj40XsyFGNMf2pX7eiUpG-hzsMXnEIxFFyEWjost7GyuM3xKkvpqj99ODyTQprnl-N1g%3D%40hornetnode.org.


  reply	other threads:[~2026-04-19  1:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 22:42 'Toby Sharp' via Bitcoin Development Mailing List
2026-04-16  0:21 ` eric
2026-04-16 18:41   ` 'Toby Sharp' via Bitcoin Development Mailing List
2026-04-18 21:15     ` eric
2026-04-18 22:26       ` 'Toby Sharp' via Bitcoin Development Mailing List [this message]
2026-04-19  2:07         ` eric

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='--C53DoYZLFJgwz6T6jBLFNjx3dNCZRC06RK981Cj40XsyFGNMf2pX7eiUpG-hzsMXnEIxFFyEWjost7GyuM3xKkvpqj99ODyTQprnl-N1g=@hornetnode.org' \
    --to=bitcoindev@googlegroups.com \
    --cc=eric@voskuil.org \
    --cc=toby@hornetnode.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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