Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(release): publish v1.2.0 #481

Merged
merged 94 commits into from
Jan 25, 2024
Merged

chore(release): publish v1.2.0 #481

merged 94 commits into from
Jan 25, 2024

Conversation

MicaiahReid
Copy link
Contributor

No description provided.

timstackblock and others added 30 commits July 21, 2023 10:42
chore: update
Added @MicaiahReid's suggestions.
The test was designed around the OpReturn matcher only. This change
generalizes it so that we can test other matchers.
This is preparatory work to introduce Wallet descriptor testing.
This introduces support for wallet descriptors.
Descriptors provide a compact and semi-standardized method for
describing how scripts and addresses within a wallet are generated[1].

Chainhooks users that want to track addresses derived from an extended
pubkey or a multisig-wallet for example, can now rely on this feature
instead of defining one predicate per address.

For example if we wanted to track the first 3 addressed generated by
the following descriptor:

```
wpkh(tprv8ZgxMBicQKsPePxn6j3TjvB2MBzQkuhGgc6oRh2WZancZQgxktcnjZJ44XdsRiw3jNkbVTK9JW6KFHvnRKgAMtSyuBevMJprSkZ4PTfmTgV/84'/1'/0'/0/*)
```

which reads: describe a P2WPKH output with the specified extended public
key, and produces these BIP84 addresses:

```
bcrt1qzy2rdyvu8c57qd8exyyp0mw7dk5drsu9ewzdsu
bcrt1qsfsjnagr29m8h3a3vdand2s85cg4cefkcwk2fy
bcrt1qauewfytqe5mtr0xwp786r6fl39kmum2lr65kmj
```

we could use the following predicate:

```json
...
  "networks": {
    "regtest": {
      "if_this": {
        "scope": "outputs",
        "descriptor": {
          "expression": "wpkh(tprv8ZgxMBicQKsPePxn6j3TjvB2MBzQkuhGgc6oRh2WZancZQgxktcnjZJ44XdsRiw3jNkbVTK9JW6KFHvnRKgAMtSyuBevMJprSkZ4PTfmTgV/84'/1'/0'/0/*)",
          "range": [0,3]
        }
      },
      "then_that": {
        "file_append": {
          "path": "txns.txt"
        }
      }
    }
  }
...

```

1: https://bitcoindevkit.org/descriptors/
chore: merge main back into develop
I was attempting to update Clarinet to the latest version of
chainhook-sdk/types, and I ran into this issue when testing the devnet.

The devnet mines 100 bitcoin blocks, and the default
`pox_info.first_burnchain_block_height` is also 100, so devnet startup
would always fail.
Fixes #401 

Previously, memory usage peaked at 32 GB. Now, I didn't see it go above
8 MB
@MicaiahReid MicaiahReid changed the title chore(release): publish v1.1.2 chore(release): publish v1.2.0 Jan 25, 2024
@MicaiahReid MicaiahReid requested a review from lgalabru January 25, 2024 20:14
Copy link
Contributor

@lgalabru lgalabru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @MicaiahReid!

@MicaiahReid MicaiahReid merged commit fd0615c into main Jan 25, 2024
9 of 13 checks passed
Copy link

🎉 This PR is included in version 1.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

10 participants