Signal
Advertise
Signal
Advertise
Sign in
Discover trends that matter
Trending repositories
Daily
Weekly
Monthly
Yearly
Live mentions
Topics
GitHub trending
Repositories
Developers
Insights
Stats
Log in
8144225309/obscurity — GitHub trending stats & insights | Trendshift
Featured
LinkMap
open-connector
8144225309/obscurity
#
Programming examples
obscurity: steganography based merge mining proof of concept and hackathon demo examples, special thanks BitcoinGrove Miami
Visit GitHub
C++
5
2
1 contributors
Social mentions
Recent discussions about this repository across the web
83 bytes isn't the limit for opreturn on bitcoin, its the limit in one implementation's policy and then nodes validate anything up to 1mb. Core before v30 validates opreturns uptot 1mb, period. I…
@ClioBitcoinBank · x.com
You can store data in the cryptographic proof if it has inputs necessarily. Show me your method of cryptographic proof, I'll put some data in it.
@ClioBitcoinBank · x.com
In information theory, there are these things called "open fields". When you send bitcoin, there is a recipient, pubkey, txid, several "fields" that are determined by the sender. You cannot have…
@ClioBitcoinBank · x.com
Ironically, if the cap on opreturn had been lowered sooner, all this spam crap would have no dust outputs and inscriptions might not exist. You incentivize this utxo growth when you try to cap op…
@ClioBitcoinBank · x.com
It's not any single example, it's literally all examples. There isn't a working filter, there is spam in the blocks of bip110 signalling blocks already. They never patched it, they can't.
@ClioBitcoinBank · x.com
There is a data limit, it's called the blocksize. I know you're not a comp sci guy, but TX data is also data.
@ClioBitcoinBank · x.com
Repository activities
repository's daily and monthly activities across stars, forks, merged PRs, issues, and closed issues