neural-hash-collider VS mev-boost-relay

That assumes the hash is base 26 which would be fun, but most hashing systems including NeuralHash are hexadecimal. NeuralHash also outputs 24 character hashes so there are 1624 possible NeuralHashes. However all of that ignores that NeuralHash is designed so that visually similar images will return the same hash on purpose. You can even provide two images of your choosing to this library and it will make them collide https://github.com/anishathalye/neural-hash-collider

This is incorrect.

The images in this link [1], are completely different. One is a cat, one is a dog. Same hash produced for both.

[1] https://github.com/anishathalye/neural-hash-collider

And here: https://github.com/anishathalye/neural-hash-collider

Also, Apple’s NeuralHash is rather prone to hash collisions, i.e. false positives, so you should absolutely expect at least some of your on-device pics to be viewed by unauthorized Apple/government personell.

time="2023-06-11T19:51:35-04:00" level=info msg="best bid" blockHash=0xf2bd4f24d68a792c88cb5f885a5cd1682662fe26c0e0eb9e8b274e586df16681 blockNumber=17460239 method=getHeader parentHash=0x03beefa5530f40cec9c00119309838f5d3e82c007e1c98cc179ed269929a0f77 pubkey=0xa96f35d5a9d94d844e320ac284f7d86d9c5a238f7a1695bd7940290e6d964c11b8527763344b144d4e3f38a32f23c0ae relays="https://0xac6e77dfe25ecd6110b8e780608cce0dab71fdd5ebea22a16c0205200f2f8e2e3ad3b71d3499c54ad14d6c21b41a37ae@boost-relay.flashbots.net" slot=6641956 txRoot=0x63337111b810cd01e1ca5d9676831cc08c6da778ec1b9b462131efed5dd7b203 value=0.248591416663511916 version=v1.5.0 time="2023-06-11T19:51:35-04:00" level=info msg="http: GET /eth/v1/builder/header/6641956/0x03beefa5530f40cec9c00119309838f5d3e82c007e1c98cc179ed269929a0f77/0xa96f35d5a9d94d844e320ac284f7d86d9c5a238f7a1695bd7940290e6d964c11b8527763344b144d4e3f38a32f23c0ae 200" duration=0.147492 method=GET path=/eth/v1/builder/header/6641956/0x03beefa5530f40cec9c00119309838f5d3e82c007e1c98cc179ed269929a0f77/0xa96f35d5a9d94d844e320ac284f7d86d9c5a238f7a1695bd7940290e6d964c11b8527763344b144d4e3f38a32f23c0ae status=200 version=v1.5.0 time="2023-06-11T19:51:44-04:00" level=warning msg="error making request to relay, retrying" blockHash=0xf2bd4f24d68a792c88cb5f885a5cd1682662fe26c0e0eb9e8b274e586df16681 error="HTTP error response: 400 / {\"code\":400,\"message\":\"sent too late - 9234 ms into slot\"}\n" method=getPayload parentHash=0x03beefa5530f40cec9c00119309838f5d3e82c007e1c98cc179ed269929a0f77 slot=6641956 url="https://boost-relay.flashbots.net/eth/v1/builder/blinded_blocks" version=v1.5.0

I'm using boost-relay.flashbots.net and bloxroute.max-profit.blxrbdn.com

Relays have rolled out a quick fix that checks the user agent on getHeader calls and ignores requests from prysm users. Long story short again, this means that prysm users will fall back to local block production, so no MEV but still produce a block and get some rewards.

This the PR https://github.com/flashbots/mev-boost-relay/commit/84a943925e62f20b812c60688b6e433fba8e0da7

The relay fix to prevent this happening again is here (https://github.com/flashbots/mev-boost-relay/pull/330). This does has some significant side effects, the biggest of which is that ~10 sets of relay beacon nodes are now responsible for propagating all new blocks. Our (/u/austonst) relay (https://aestus.live) was taken offline for builders as soon as we became aware of the threat and will update before we come online again. Never a dull day in ethereum.

Interesting PR in the flashbots mev-boost-relay GitHub repo today, with a very interesting discussion in an earlier revision that I think is worth a read. It's a proposal to accept blocks from builders optimistically, assuming they are proper valid blocks, in order to reduce latency. Blocks are eventually validated, but only once the slot has passed and latency is no longer critical. Overall this increases the value of proposed blocks (compared to relays that don't implement this) and reduces mean transaction inclusion time.

We are currently using Flashbots' mev-boost-relay, and Flashbots' block-validation-geth for validating builder-submitted blocks. Flashbots' OFAC censorship is coded into block-validation-geth, and for the moment we have simply emptied their ofac_blacklist.json file with no intent to ever place anything in there.

Flashbot's relay is open source and written in GO. Create your own fork, load the Docker container and start testing and learning. https://github.com/flashbots/mev-boost-relay

Code: Flashbots' mev-boost relay code is open source. Blocknative and Eden both have their relays open-sourced as well, so it's possible to see if there's anything important. Eden's seems vanilla, Blocknative's is actually a completely separate implementation.