2026-05-14
Publish to ethereum blobdata using monero payment and atomic swap
Disclaimer
- Quick Note
- Contains politically sensitive info
- Incomplete
- This is an experimental idea, and no existing implementation exists.
Main
- I noticed this exact problem when I wrote the US govt whistleblower guide, although a vague version of this idea was in my head for many years.
- As of 2026-05, here is SOTA
- Ethereum blobdata is the best place to publish data that govts want to censor (such as leaked classified information), without paying a huge amount of money
- Mining monero on your own on a TAILS machine is the (arguably) the best way to obtain cryptocurrency privately.
- Atomic swap XMR to ETH exists but there is no GUI and hence no liquidity.
- Publishing to blobdata is possible but again, there is no stable GUI. You need your own ETH and need to use a cli tool.
- Ideally you should be able to mine monero, pay to publish a message using this monero, and have it automatically published to ethereum blobdata. Not 100% confident but I think it should be possible to do the atomic swap and publishing to blobdata atomically (trustless)
- Process
- Bob (the relayer) generates keypair P_b, s_b and publishes P_b on their website.
- Bob also stakes some ETH into a specialised smart contract that recognises P_b as the relayer pubkey.
- Alice (the person with monero and the message they want to publish) generates keypair P_a, s_a
- Alice uses P_a and P_b to compute a monero address P_a+b that requires both s_a and s_b to control.
- Alice sends the payment required, in XMR, to this address.
- Alice signs the message M they want published using s_a to generate M_a
- Alice sends this signed message M_a to Bob. Alice sends the public monero address P_a+b to Bob. Alice sends P_a to Bob.
- Bob submits M_a and P_a to the smart contract, along with s_b. The smart contract atomically does the following things - verifies M_a is signed by P_a, verifies s_b is the secret key for the P_b previously recognised, and publishes M_a to blobdata.
- Alice now ... incomplete
Update
- Never mind I now think this whole idea is stupid. It is probably easier to write two separate GUIs, one for the atomic swap and another for the EIP4844 tx, and have the same liquidity provider provide liquidity for both, than it is to create this kind of complex smart contract and find a liquidity provider for it.
Subscribe
Enter email or phone number to subscribe. You will receive atmost one update per month
Comment
Enter comment