1. you don’t need to write smart contracts for 90% of use cases.
most protocols already expose great typescript and rust sdks.
👉 github.com/sendaifun/so... has everything to get you started.
1
1
14
2. landing a transaction on solana is tricky.
use this guide to properly set priority fees: www.helius.dev/blog/how-to-...
or use jito bundles for transaction atomicity.
1
8
3. everything is an account, and every account has an owner.
half of the bugs happen because you’re accessing the wrong account. understand the account model well:
1
6
4. evm → svm mental model:
abi = idl
eoa = account (owned by system program — the godfather)
contracts = programs aka program accounts (owned by bpf loader)
2
6
5. once you understand pdas, they become an incredibly powerful tool.
this guide helps you shift from evm to svm thinking
1
10
6. if you’re using partial signing:
make sure the frontend (farcaster wallet) signs the transaction before the backend does.
⚠️ not recommended as-is — the frontend can send a malicious transaction. if you do this, use it with a nonce.
the current farcaster wallet setup invalidates previous signatures — the team is working on fixing this.
1
7
7. use good rpcs: helius, triton, or quicknode are reliable choices.
once you understand the solana account model and how transactions are formed, it all gets much simpler.
the solana community is actually super welcoming — way more beginner-friendly and supportive than people often perceive.
1
8
some more deep dives
1. solana.com/developers/ [ the best? ]
2. www.helius.dev/blog [ domain specific ]
3. blog.quicknode.com/tag/solana-2/
7
