I added a new query variant to get a little bit of a better visual representation of what's been changing since October's Core 30 release. You will already have guessed it: almost nothing. Only 8 OP_RETURN transactions with >1024 bytes (which isn't even really big) have been recorded in the last week. Query Win66 Com: This one starts in early September, so the "normal level" of activity can be well compared with the post-Core-30 evolution. I did this one with a log chart so even small changes in the bigger OP_RETURN transaction classes look really scary And really, the 83-256 bytes category is increasing (it's below the September high though). About 15% are now Core 30 nodes according to Bitnodes, so if even a third of them run with default values, it should be easy to connect with a node accepting your big ... pic without even paying a miner. It would be interesting if there's a chart out there where I can see the datacarriersize value, but don't know if this exists or is even public.
I added a new query variant to get a little bit of a better visual representation of what's been changing since October's Core 30 release. You will already have guessed it: almost nothing. Only 8 OP_RETURN transactions with >1024 bytes (which isn't even really big) have been recorded in the last week. Query Win66 Com: This one starts in early September, so the "normal level" of activity can be well compared with the post-Core-30 evolution. I did this one with a log chart so even small changes in the bigger OP_RETURN transaction classes look really scary And really, the 83-256 bytes category is increasing (it's below the September high though). About 15% are now Core 30 nodes according to Bitnodes, so if even a third of them run with default values, it should be easy to connect with a node accepting your big ... pic without even paying a miner. It would be interesting if there's a chart out there where I can see the datacarriersize value, but don't know if this exists or is even public.

I added a new query variant to get a little bit of a better visual representation of what's been changing since October's Core 30 release. You will already have guessed it: almost nothing. Only 8 OP_RETURN transactions with >1024 bytes (which isn't even really big) have been recorded in the last week. Query Win66 Com: This one starts in early September, so the "normal level" of activity can be well compared with the post-Core-30 evolution. I did this one with a log chart so even small changes in the bigger OP_RETURN transaction classes look really scary And really, the 83-256 bytes category is increasing (it's below the September high though). About 15% are now Core 30 nodes according to Bitnodes, so if even a third of them run with default values, it should be easy to connect with a node accepting your big ... pic without even paying a miner. It would be interesting if there's a chart out there where I can see the datacarriersize value, but don't know if this exists or is even public.

I added a new query variant to get a little bit of a better visual representation of what's been changing since October's Core 30 release. You will already have guessed it: almost nothing. Only 8 OP_RETURN transactions with >1024 bytes (which isn't even really big) have been recorded in the last week. Query Win66 Com: This one starts in early September, so the "normal level" of activity can be well compared with the post-Core-30 evolution. I did this one with a log chart so even small changes in the bigger OP_RETURN transaction classes look really scary And really, the 83-256 bytes category is increasing (it's below the September high though). About 15% are now Core 30 nodes according to Bitnodes, so if even a third of them run with default values, it should be easy to connect with a node accepting your big ... pic without even paying a miner. It would be interesting if there's a chart out there where I can see the datacarriersize value, but don't know if this exists or is even public.