BSVNode - merged to dev - Remove further limits on OP_RETURN Classifies a transaction…

1AKHViYgBGbmxi8qiJkNvoHNeDu9m3MfPE (1125) · September 4, 2019

BSVNode - merged to dev - Remove further limits on OP_RETURN

Classifies a transaction with multiple OP_RETURNs as a standard transaction. Update the datacarriersize configuration parameter to apply to the sum of the lengths of the OP_RETURNS.

Replies

1AKHViYgBGbmxi8qiJkNvoHNeDu9m3MfPE (1487) · September 4, 2019

This is huge!

1AKHViYgBGbmxi8qiJkNvoHNeDu9m3MfPE (1487) · September 4, 2019

I could publish an entire hypermedia bundle in a single transaction (think a progressive web app w/ index, scripts, styles, images, assets, &c.), and I could use relative vout index addressing with b:// URLs (that is, w/o TXID & assuming the current TXID).

1AKHViYgBGbmxi8qiJkNvoHNeDu9m3MfPE (2963) · September 4, 2019

Can you explain some reasons why...for the less technical?

1AKHViYgBGbmxi8qiJkNvoHNeDu9m3MfPE (2338) · September 4, 2019

Thank you 💪💪💪

1AKHViYgBGbmxi8qiJkNvoHNeDu9m3MfPE (9181) · September 4, 2019

Is this still contrained by the 1MB transaction size limit?

1AKHViYgBGbmxi8qiJkNvoHNeDu9m3MfPE (1512) · September 5, 2019

100KB*