Many say that the market is in the worst condition. Spending money to go there will not be a good choice?
Or shall I think like this?
Going now to avoid an annoying crowd? So that I could get noticed?!
I just got accepted for the solana trubin3 cohort.
Just wanted to know if it is worth it or not, kindly do share your experience if you have been in these cohorts!
Will this help me to get a job?!
And what type of task will be given at first. They mentioned that people who finish the 1st task will only enter into the cohort officially
So I've been prepping for Solidity interviews and decided to actually build something instead of just reading about it. Ended up making an ERC-4626 vault (the standard behind Yearn, Morpho, etc.) and specifically targeting the "inflation attack," a real exploit that's hit live vaults in production.
The attack is stupidly simple: deposit 1 wei, become the first depositor, then just transfer() a pile of tokens directly into the contract instead of going through deposit(). The next real user who deposits normally gets their shares rounded down to basically zero. No hacking required, just unchecked integer math.
I built the attack against my own vault first (to prove I understood it, not just copy a fix), then patched it using OpenZeppelin's decimals offset defense, and wrote a Foundry test that actually runs the exploit and checks the outcome. Result: attacker loses roughly half their money instead of stealing everything.
It's deployed live on testnet with a working demo, you can connect a wallet, mint fake tokens, deposit, simulate yield, and try to break it yourself:
https://vaultiss.vercel.app/
Code + tests + README:
https://github.com/SIDHARTH20K4/vaultis
Genuinely looking for feedback, brutal is fine. Is this the kind of project that'd actually get someone's attention for a junior/entry Solidity role, or am I missing something obvious that a real auditor would catch in five seconds?
After hours of searching...
You finally find a job that makes you smile.
Everything fits.
The skills.
The tech stack.
The location.
The salary.
Then your eyes land on one sentence.
"3+ Years of Experience Required."
That excitement disappears in seconds.
For many freshers, that's where the application ends.
Not because they aren't capable.
But because they're filtered out before they even get a chance.
The frustrating part?
Many graduates today have:
✅ Strong projects
✅ Internships
✅ Certifications
✅ Practical skills
Yet experience becomes the first filter.
This leaves many candidates wondering:
"How do I get experience if every opportunity asks for experience?"
It's one of the biggest challenges facing fresh graduates today.
I'm curious...
If you could change one hiring rule for entry-level jobs, what would it be?
👇 I'd love to hear your thoughts.
If you could change one hiring rule for freshers, what would it be?
A non-tech CEO said a $20/month vibe-coding plan completely replaces engineers by now.
So, I visited his web platform to see how he built it with AI.
When I opened devtools, every red flag was sitting right there in the front-end code.
API key exposed client-side.
Admin access could be unlocked from the browser.
The frontend held all the business logic.
The database was exposed directly to the client.
API keys and credentials were hardcoded.
Passwords weren't even hashed.
Membership access could be granted from the frontend.
He was true that he didn’t need an engineer to build a vulnerable app.
Code is cheap but good engineering is always expensive.
I've started contributing to rust based open-source repositories
Is that enough or am I missing something?!
Every time I sit down to build a smart contract, I hit the same wall. Decentralization, security, scalability, you only get 2.
The more audits I do, the more obvious this becomes. Yet every project markets itself as having all three nailed.
99% of crypto projects marketing "decentralized AND scalable AND secure" are scamming you on at least one of those words.
The trilemma is real. Pretending it doesn't exist is how people lose money.
Do you actually factor this in when picking projects, or is everyone just ignoring it until they get burned?
Every time I sit down to build a smart contract, I hit the same wall. Decentralization, security, scalability, you only get 2.
The more audits I do, the more obvious this becomes. Yet every project markets itself as having all three nailed.
99% of crypto projects marketing "decentralized AND scalable AND secure" are scamming you on at least one of those words.
The trilemma is real. Pretending it doesn't exist is how people lose money.
Do you actually factor this in when picking projects, or is everyone just ignoring it until they get burned?
I think germany is becoming competitive in all fields if I'm not wrong... How do Deutschers feel about the foreigners migrating to Deutschland... I could see most of the people migrating there for college studies and then ausbildung.
How about people who want to work directly there?!
I think germany is becoming competitive in all fields if I'm not wrong... How do Deutschers feel about the foreigners migrating to Deutschland... I could see most of the people migrating there for college studies and then ausbildung.
How about people who want to work directly there?!
We all have the dream to go the Germany and live there!
Lets try to make that dream come alive by practicing to speak frequently!!
Bei Interesse DM mich!
(If interested DM me!)
Ciao
Been deep in Solana security auditing through Rektoff, and noticed most vulnerabilities trace back to one thing: devs not fully understanding AccountInfo.
Quick breakdown of each field, security lens:
key - the account's address. Skip verifying this matches what you expect, and attackers can swap in a different account entirely.
is_signer - did this account actually sign the transaction? Skip this check and anyone can call privileged functions. This is the root of confused deputy attacks.
lamports - the SOL balance. Wrapped for safe mutable access. This is the field devs manually mess with instead of trusting Anchor's close constraint, often leading to redundant or buggy transfer logic.
data - the raw account state. Whatever struct you define lives here as bytes. Corrupt this, corrupt your protocol's integrity.
owner - which program owns this account. Don't verify this, and attackers can pass in a fake account owned by a malicious program instead of yours.
executable — is this account actual program code? Mostly matters for CPI calls.
Any good resource to learn and practice solana program auditing will be appreciated!