green w/ nits on remaining _LEN constants

Is it possible to have a "valid" SLP OP_RETURN string that exceeds the OP_RETURN byte limit?

How is this function expected to be used? For the most part, correctly parsing an SLP OP_RETURN is often irrelevant, since we lack the indexer data (e.g. a well-formed SEND OP_RETURN could be a burn; validity in general depends on the indexer).

patch conditional rendering for test

Pushing up this last round of feedback-based changes to support incremental review, but this is not ready to land yet

Update interfaces, add some intermediate steps, take sighash as a param

this diff was created on the master branch, which makes it difficult to rebase onto the latest master

• If we are switching from px to rem, switch; remove all the px comments, mb keep one to show what the base-level px is
• do not use calc. if some ratios seem unreadable, create a variable for them and use the variable
• remove all unused variables

back out the pythonpath stuff, add dep

debian python note

would be a good change and help to get some of the css more standardized in Cashtab

better comments

tighten up comments, remove "get" prefix from utxo selection methods

TIL coin consolidator is a thing in electrum

another diff just deleted the test

rebase

rebase, correct indefinite article in test name

remove other test that appears to fail for the same reason

use spendablesatsonlyutxos instead of fuelutxos, make getSpendableCoinbaseUtxos private

add comments for verifyMsg

In D17782#405166, @emack wrote:

Add .only to a test file in ecash-lib, run arc lint, get a lint error, remove it, all good, npm test with a test using .only and only that test runs

I added .only to describe('SLP Integration Test') and it is not the only test that is run.

no arrow syntax, stop testing files that do not yet exist, use correct COINBASE_MATURITY term, clean up comments

do not assume coinbase utxos cannot be tokens, add token utxos to tests to show we do not get them as fuel utxos