mempool sniper bot for new friend.tech joiners. the story goes:
- op-stack is supposed to be blind mempool. but base node default config had txpool+ws rpcs open (see the patch notes)
- friend.tech uses blast-api rpc
- blast-api used base node default config for their backend nodes
- friendrekt-rs
- rust bot for finding new joiners, caching follow count and sniping
- friendrekt-contracts
- solidity contract for sniping w/ fail-safes
- twt-follower-api
- python http api for retrieving follower count
/*
here's a brief overview of the sniper:
there are two tokio threads.
1. listen to every block.
for every ETH transfer or bridge relays:
reverse search the addresses involved on friend.tech
find the number of followers
if the address is not cached:
cache the address
2. listen to blast-api eth_newPendingTransactions
there are multiple (4?) backend nodes so subscribe a few times
(afaict its mostly rng which stream you get)
(also run this bot on several geo-distributed servers)
if its a first-share-buy (a signup):
if the address is cached:
if follow count > 20k: send snipe tx
otherwise:
do a live lookup of follow count
if follow count > 20k: send snipe tx
*/
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent