public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed

From: Richard Myers <remyers@yakshaver•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Anyprevout functional tests using eltoo scripts
Date: Tue, 17 Aug 2021 11:24:14 +0000	[thread overview]
Message-ID: <bKBvblUbWYaUVwNep6qrX76vo0l3jZgOgNcS1DI0HwIeKSfpz7D-uN4RaZ82xmLV5KvKrGjLDBUUYAgwV_JqajRzvhQQ1lA-526wGk6VTSw=@yakshaver.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]

I implemented some basic functional test scripts for the eltoo channel update scheme to better understand BIP-118/Anyprevout (APO). My tests are based on the rough Taproot eltoo scripts AJ Towns outlined on this list back in 2019. These tests also require AJ's APO branch of core. This is just the start of a real eltoo implementation, but I wanted to share it to get feedback and to help others interested in understanding APO and eltoo.

If you want to take a quick look, my functional tests are implemented in the function "test_tapscript_eltoo":
https://github.com/remyers/bitcoin/blob/eltoo-anyprevout/test/functional/simulate_eltoo.py#L1623

I've also written a blog post that describes in more detail how to run the tests and includes notes that I hope will be helpful to anyone else interested in APO and eltoo:
https://yakshaver.org/2021/07/26/first.html

I'd love to work with anyone else interested in eltoo and APO who wants to help extend and elaborate these tests. Any PRs for the eltoo tests or blog post would be very welcome.

Many thanks to AJ and Christian Decker who have both been very generous with their time in helping me understand the finer details of APO and eltoo.

All the best,

-- Richard

[-- Attachment #2: Type: text/html, Size: 1432 bytes --]

                 reply	other threads:[~2021-08-17 11:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='bKBvblUbWYaUVwNep6qrX76vo0l3jZgOgNcS1DI0HwIeKSfpz7D-uN4RaZ82xmLV5KvKrGjLDBUUYAgwV_JqajRzvhQQ1lA-526wGk6VTSw=@yakshaver.org' \
    --to=remyers@yakshaver$(echo .)org \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /path/to/YOUR_REPLY

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox