yes it's run

rebase on as_ref fix

switch to BiMap

use plugin idx instead of string to identify plugins

add test for tip header too

remove unnecessary bridge

rebase, apply suggestions, fix json compilation errors

fix some comments, remove unused/unneeded error variants

redesign plugin system, use Plugin class, and add [main.plugin] [test.plugin] and [regtest.plugin] sections

gArgs -> args

and a few other places. Or you just don't update the Rust version, as it's not necessary to fix the build on newer versions.

oh wait also update the version in /Cargo.toml:

[workspace.package]
rust-version = "1.76.0"

works on my machine too

one nit, otherwise gtg

is there a way to temporarily deploy this to test it out in actual cashtab? it seems basically gtg

fix lints

NAK this approach

fix spelling

fix spelling, add const, return undefined for ALP for now

In D16111#365055, @bytesofman wrote:

It is a bit complicated to setup these txs. Not too big of a deal since will be handled by devs and not users.

Yeah, it's not ideal. But after IMO this is the simplest way without breaking the SLP spec. And some day we'll (hopefully) get atomic broadcasts for multiple txs which will reject the setup tx if the offer tx fails.

Remove artefact in built chronikNode.ts, otherwise LGTM, good test coverage

add copyright, fix comments in oneshot.test.ts

fix README, english are hard

fix oneshot.test.ts

• Remove es2016 dependency, build targeting es2020 directly
• Add comments explaining why two separate wasm-bindgen builds
• Fix some imports
• Improve README

fix sed command

This seems unnecessary and hurts code readability

fix browser build

Put this on hold until it's clear this is a good path forward

@bot ecash-agora-integration-tests

fix first paragraph of README

amend the README.md to make it even more hip

rerun ci

seems like everything is resolved after this passes tests, or did I forget anything?

use 1 single token when creating an NFT