A few thoughts:

1. This will be fixed for segwit v1 addresses in an upcoming release (once we finish taproot support)
2. That said, console.warn was meant primarily for wallet developers to be sure that they don't show versions they can't guarantee are safe.
3. However, we have no way programmatically to relay that info back to the program, and the program has no way to tell us "ok, I made my GUI understandable so the end user is not in danger".
4. Also, we want to respect the BIP and DO NOT THROW on parsing unknown segwit versions.

Perhaps we should add a new set of functions for to/fromOutputScript and deprecate the current ones for removal in the next major version bump?

As a temporary solution, though super hackey, the consuming app could do something like:

function wrappedFromOutputScript(script, network) {
  const oldWarn = console.warn
  console.warn = () => {}
  const result = fromOutputScript(script, network)
  console.warn = oldWarn
  return result
}

As a temporary solution, though super hackey, the consuming app could do something like:

function wrappedFromOutputScript(script, network) {
  const oldWarn = console.warn
  console.warn = () => {}
  const result = fromOutputScript(script, network)
  console.warn = oldWarn
  return result
}

Is there an ETA on this at all?

Is there an ETA on this at all?

Please help review this PR #1742, and the rest will follow 🎵

This also happens when parsing some Litecoin transactions.
Maybe adding an optional argument in fromOutputScript to disable these warnings?

I guess we can just do it once. See PR.