Hi everyone, my name is David. For the longest of times, I've battled with my own need to control life and outcomes.
Day after day, I work hard, often wrestling with low motivation, not know what to do, confused, sad, and angry.
Sometimes, it feels easier to pull back.
DO YOU WANT TO pull the latest Dune query results to a local file in one shot ?.. JSON, JSONL, or CSV. Tiny script, no fluff, just works...
https://t.co/CaqHHjowKL
`pip install dune-client` + your `DUNE_API_KEY` and you're set.
#DuneAnalytics#Python
WE HAVE PROBABLY NOT EVEN STARTED THE AI BOOM...
AI WILL BE FREE FOR EVERYONE!!
In the coming times, controlling your data and selling it will become the new meta.
==UNDILUTED ALPHA📢📢==
You can get free $100+ Claude or OpenAI credits through Agent Router using your old GitHub accounts. Just sign up here: https://t.co/t4Q8FLvLWD and follow their official docs :
https://t.co/iTA1Dga7YQ
@agentrouter .
I will reply to all comments.
Good alpha, my problem is.. Everytime y'all say things like this .. it crowns me to ask... How do you find the people who own the project , that's the real alpha I need..
Lots of people asking me how I did this. I want to summarize the whole process.
It’s called an independent audit or security research with no job, no invite, and no special access.
You do not need permission to audit because smart contracts are public code that holds money, and anyone can read them and report what is broken.
Here is the process.
→ Pick a relatively small, new project with a team you can actually message. New code has more bugs, and small teams reply faster. (EVM projects in most cases).
→ Get the verified source from the chain explorer. That is the real code and contract that is running.
→ Read it with a few questions in mind.
Who is allowed to move the money?
What happens at the risky moment when funds move between contracts?
Can a stranger trigger something only the team should?
You are hunting for just one wrong assumption at the moment, and you can as well use AI for faster reviews and code checks.
→ When you think you found it, prove it on a local copy of the chain, never on the real network.
A copy behaves like the real thing but touches no real funds. If you are right, it shows the money moving. If you are wrong, you find out before you embarrass anyone.
→ Write it short. What the bug is, what it costs, the exact code, and the exact command to reproduce it.
The best line you can give a team is "Do not trust me; run this yourself."
→ Send it privately. Don't post details while the bug is still open.
→ The team might bring you in to fix the bug with them, or rather, you submit your report and PoC (Proof of Concept).
Ask for their offer of a reward for the bug; criticals pay the highest.
→ Help them check the fix after the new changes.
The rule that matters most is to test on copies only.
Never inflate a medium bug into a critical.
Tools to learn. A chain explorer to read verified sources and Foundry to run a local copy of a chain and test against it.
The first bug is the hardest because you do not believe you can do it yet. But you can by finding the wrong assumption, proving it on a copy, reporting it with respect, and repeating it again.
Since everybody wanna win in web3 this new year , I'll to show you what I built and it's open on my github btw https://t.co/V0Tf2i9gs1..
Imagine a liquidation bot script that tracks @Morpho contracts onchain and look for lenders who defaulted, liquidate them and earn incentives.
The script is sile,deploy the sol file onchain, and run the script....that runs the liquidation easy try various L2 for easier fees cheaper fees less than 3$ for up to maybe 15 tx. Like @arbitrum@HyperliquidX etc.
I've outlined everything you need in my repo.
Easy to implement.
Since everybody wanna win in web3 this new year , I'll to show you what I built and it's open on my github btw https://t.co/V0Tf2i9gs1..
Imagine a liquidation bot script that tracks @Morpho contracts onchain and look for lenders who defaulted, liquidate them and earn incentives.