Just their blocks

The P2SH address 38fEX6RbBBMmpu3nbbuULku1xyrrzqqqnE is both:

‎ ‎ ‎ ‎ ‎ ‎ ‎

The private keys that can spent from it are 1 and 2.

I was curious how the new OCEAN block templates compare in terms of fees. Here's a quick-and-dirty client-side tool that connects the OCEAN web sockets and plots the fees in the template: https://0xb10c.github.io/ocean-xyz-templates/

0xB10C

A FOSS Bitcoin Core based passive P2P networking tool called peer-observer. It hooks into tracepoint's in Bitcoin Core to extract, e.g., P2P messages sent and received, connections opened, closed, evicted, … The nodes are essentially well-behaving honey-pots with a lot of monitoring.

This is all already implemented and running. However, don't have a public demo of it at the moment. Happy to share something with interested people. I currently have 10 nodes running, dispersed around the globe.

Looking for someone interested in Bitcoin P2P network level attacks that wants to build some sort of (real-time) anomaly detection with the data the tool is producing. For example, detection of inbound connection flooder's like LinkingLion: An entity linking Bitcoin transactions to IPs?.

The project is mainly written in Rust, but I've taken care that Python scripts should work too. The infrastructure is Nix+NixOS.

For fun and to make the Bitcoin network more secure. Not for profit. I have a grant to work on this (and more). I can't pay you for the work, though you might find someone else willing to give you a grant or similar for the work (I can help, but no promises!).

Comment below, or send me a DM / email. You'll find ways to contact me on b10c.me.

:)

yes, for today's block that was about 7.7mBTC or $300 USD (based on data from my miningpool-observer. mempool-space suggests it was closer to 0.3 BTC but I think that number is off.

It seems to me they aren't mining transactions with larger OP_RETURN outputs, likely because they are running Bitcoin Knots. That's a weird way to say "Hello World" as a pool which has a big "Bitcoin is no longer censorship-resistant, and mining centralisation endangers its security too. It's time to fix that.". IMHO just use the default Bitcoin Core template...*.

*. they're obviously free to mine what ever they want, but all the "block template transparency" blabla could have, from the start, included that they diverge from the (current) default mempool policy.

Seems to be gone.

The transactions aren't missing from the ledger/blockchain. I have the txids in the footnotes - feel free to look them up. They all have been mined, just not by the first pool that could have mined them.