A project encompassing NFT monitors, Backend Infra, Web3 utils and Snipers/Minters. I am frequently updating this repo & it is WIP.
Should you want to reach out, please do so on Discord at weeaa. π€π»
- Discord Bot with Slash & Buttons features
- Postgres Database with CRUD API
- Friend Tech
- Indexer
- Buy/Sells w/ filters
- New Users w/ filters
- Deposits w/ filters
- Pending Deposits w/ filters
- Invite Redeemer
- Watchlist Adder
- Sniper
- Stars Arena
- Monitors
- Sniper
- DeFi
- Uniswap
- V2 Swap
- V3 Swap
- Pair Audit
- Utils
- Raydium
- Swap
- Uniswap
- Etherscan Monitoring
- New Verified Contracts
- ExchangeArt Monitoring
- New Drops by Artist (need to update to gql)
- LMNFT Monitoring Top Drops
- Solana
- Polygon
- Ethereum
- Binance
- Aptos
- Avalanche
- Fantom
- Stacks
- OpenSea Monitoring
- Sales
- Listings
- Premint Monitoring
- Hype Weekly/Daily Raffles (Premint NFT Required) β (needs fixes)
- Bitcoin
- Unisat BRC20 Hype Mint Monitor (Discontinued due to header encryption, cba)
- Fees Monitor
- Unisat BRC20 Minter (thoon)
- Wallet Watchers
- Ethereum (thoon)
- Base (thoon)
- Solana
- Polygon
- Bitcoin (thoon)
- Twitter Scraper
Below is a demo of our Friend Tech monitor running for Machi, where we had a large pool of new users who hadn't deposited ETH at that time. It's running on localhost, hence the latency. (It is normal for the response status to be 404)
machi.mov
Here is how your .env file should be looking like, these values are mainly used for testing purposes.
NODE_WSS_URL=
NODE_HTTP_URL=
BASIC_USERNAME=
BASIC_PASSWORD=
BOT_TOKEN= <mandatory>
PSQL_PORT=
PSQL_USERNAME=
PSQL_PASSWORD=
PSQL_DB_NAME=
FT_BEARER_TOKEN=Within the scripts directory, you will find a db.sh Bash script that, upon request, generates a database and a table. Please refer to the instructions provided below.
unix ο£Ώ
$ chmod +x ./scripts/run.sh
$ ./scripts/run.shwindows β
soon-
Please be aware that for new users of Friend Tech, the use of proxies is essential. Friend Tech tends to impose temporary bans on the same IP address after approximately 90 requests. In my current configuration, I have 1K ISP proxies in place, with bans typically resolved within one second, as demonstrated in the video above.
-
You need WSS & HTTP RPCs (commonly named nodes) to monitor on-chain, free ones work well but are subject to rate limits.
There are various examples which can be found in the /examples folder. In order to build a binary, Go 1.20 or higher is required.
After Go is installed, git clone the repository and cd in examples/~ (wherever you want) and execute go build yourfilename.go.
s/o DALL-E for the image πΈ