ottosch
@ottosch_
Followers
1K
Following
11K
Media
224
Statuses
1K
GPG DFA035EB1E00E516 https://t.co/DnKOjZGHsp
Joined August 2019
Please donate to the defense fund, if you can. Not only two individuals can go to prison for trying to improve Bitcoin privacy, but this also sets a very bad precedent for Bitcoin and cryptocurrencies development in general.
1
14
34
We are unstoppable. Today, with the girls from @Fundguadalupepy, we took a massive step: we learned how to use Ashigaru Wallet (the @SamouraiWallet fork) and connected it to @ottosch_ node. 🔒 Real self-custody 👧🏽 Girls learning what many adults still don’t understand
7
27
67
Here's a transaction from Jan 2024 holding a whole, contiguous, 5.6KB JPEG on OP_RETURN. Get it with: bitcoin-cli getrawtransaction 4719e7252f4bdefd9f7bdf5058f17af28729b79c303b067eb01c107e57235754 1 | jq -r '.vout[0].scriptPubKey.asm | sub("^OP_RETURN "; "")' | xxd -p -r | tail
22
10
128
Can someone tell this guy that OP_RETURN data is (and has always been) contiguous data? Maybe he's just ill-informed? No "special P()RN tools" are needed to read this 2013 (!) transaction: d29c9c0e8e4d2a9790922af73f0b8d51f0bd4bb19940d9cf910ead8fbe85bc9b @Beautyon_
3
2
18
Just a question for current DeFi devs: How can you be so sure you won’t be charged by the DOJ as an MSB - for building a non-custodial protocol - and then accused you should’ve built it custodial instead? If SDNY can charge a dev for building a non-custodial protocol… who’s
73
121
701
2017 Tank Man: - 1189 fake coins, each holding 20 bytes of the image in the pubkey hash. Those will live forever in the UTXO set, since nobody owns the private keys; - Lots of unnecessary bytes (not part of the image): 8 (amount) + 1 (size) + 5 (opcodes); at least 16.6 KB added
7
7
44
Ever wondered how exchanges view your wallet? Today, we released our auto-analysis feature. This allows you to scan where bitcoins are coming from or being sent to and will provide you with a complete overview. This can be done for: - Transactions - Blocks - Addresses -
2
15
53
Follow this account for the latest updates on Bitcoin Core releases. Bonus: get a list of NPCs to mute/block.
A new release candidate of Bitcoin Core, v30.0rc3, is available for testing. This is a new major release, and follows v29.0. It is available here: https://t.co/8FLkdBqus2 Work-in-progress release notes are available here:
3
0
20
Reminder that this has been debunked multiple times. Here's when I made a non-standard op_return paying 1 sat/vb: https://t.co/bNwbzNcJ91
Reminder that filters made non-standard OP_RETURN transactions 3x more costly and 6x slower on average.
0
0
8
Should I make an experiment and bind 5000 onion/tor addresses to a single Core node? 300 retweets and I’ll do it.
19
69
156
F2Pool is actively attacking the network RIGHT NOW. All it takes is one attacker to send them a single instance of CSAM, and Bitcoin users will have to knowingly and intentionally receive, store, and distribute it until the end of time. This will permanently impact Bitcoin
0
0
6
If you do not think that financial bitcoin transactions will eventually price out non-financial bitcoin transactions you do not believe that bitcoin will succeed.
93
95
572
@NickSzabo4 @maxtannahill @Bitcoinpoet_JP @phyrooo @lorandimecs @Excellion @_jonasschnelli_ @adam3us The 7k bitcoin in the Whirlpool shows how serious it is. It was close to 10k at peak. That is bigger than lightning network public or liquid on Clark Moody's dashboard.
7
13
57
I'm tired of repeatedly asking this question and never getting an answer: Why would this central banking cartel bother with relay policies when they can just mine blocks full of CSAM? Surely they can afford enough ASICs to get a single block mined, can't they? Even if everybody
I’m tired of repeatedly describing this attack, so I’ll write it out once more and reference this post. A CSAM Flood Attack is when a well-funded enemy (e.g. central banking cartel) “floods” the network with a brutal, relentless, never-ending stream of “spam” with the intent of
3
0
13
It took about 2.5 days to sync the new Fulcrum on a laptop (Ryzen 7 5700U, db_mem 8000 GiB). The v2 DB is a little larger than v1: 176 GiB against 166 GiB. To test performance, I repeteadly queried a large BTC address (1HckjUpRGcrrRAtFaaCAUaGjsPx9oYmLaZ) for balance and history
Fulcrum 2.0 Beta is available for testing. If you're interested in testing it, check the link in the next post.
12
13
69
I will not be running Bitcoin Core v30. (I'm running it already)
I will not be running Bitcoin Core v30.
1
3
29
Fulcrum 2.0 Beta is available for testing. If you're interested in testing it, check the link in the next post.
2
10
52
reminder: the perverse incentive created by the current default op_return limits isn't theoretical. there are applications in operation today which abuse fake outputs (at ~no additional cost) because they need to publish slightly more than 80 bytes of data.
did you know? there's a rune-adjacent protocol with reasonable adoption that stuffs arbitrary data into fake segwit outputs. they do this because their transactions already use one op_return for a separate runestone message, and multiple op_returns would violate standardness.
35
43
204