- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Today
--update D17815
Please rebase before landing
rebase
rebase
fix fuzzer and add compiling bitcoin-fuzzers to test plan
rebase, merge two if branches now that we only need to compute one value and already know its results prior to the branch
rebase on D17878
Yesterday
rename more consts
comment nits, const, update test plan to include a full background validation (test still ongoing)
green w/ nits on remaining _LEN constants
rename:
- SLP_GENESIS_HASH_LEN -> SLP_NUM_GENESIS_HASH_BYTES
- SlpOpreturn -> SlpData
Mon, Mar 31
Sun, Mar 30
Sat, Mar 29
add .js suffix
add consts to address review; also factor out nextMintOutIdx
Fri, Mar 28
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).