OP_FALSE OP_RETURN size limit is still at 100kb as far as I can tell and this is the methodology employed by bitsv library to create data carrier transactions.
So let's see how it plays out... there are two ways it could go:
-
Miners raise this limit and we just increase the limit in the bitsv codebase
-
Developers port their protocols over to use OP_PUSHDATA inside of the evaluated script (which afaict will currently have a 100MB size limit and hard consensus cap of 1GB).
OP_FALSE OP_RETURN size limit is still at 100kb as far as I can tell and this is the methodology employed by bitsv library to create data carrier transactions.
So let's see how it plays out... there are two ways it could go:
Miners raise this limit and we just increase the limit in the bitsv codebase
Developers port their protocols over to use OP_PUSHDATA inside of the evaluated script (which afaict will currently have a 100MB size limit and hard consensus cap of 1GB).