austecon / polyglot Goto Github PK

I used the upload_bcat command with a file path: /Users/patrick/Desktop/landscape.mp3

As you can see, the OP_RETURN data actually contains the full file path instead of just the file name.
https://whatsonchain.com/tx/ba135a019f9314030c6b3766b1a96d26ac1729fef9be1e6e35daa248e50368b5

rendering issues on bico.media are now resolved with latest version of bitsv 0.10.1 (flips the ordering of outputs to place the OP_FALSE OP_RETURN output first )
please upgrade with pip install bitsv --upgrade.

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:

1. Miners raise this limit and we just increase the limit in the bitsv codebase

2. 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).

What's the next change needed to polyglot to move it forward?

Is it reasonable to provide a new release that includes the new download functions, so they can be used from public scripts?