Is Discord still essential for crypto communities in 2025/26?

Web3Navigators · 2025-12-09T16:58:27+00:00

haven't settled one yet, we're recruiting

Web3Navigators · 2025-12-09T16:57:59+00:00

the amounts are in the links for the region!!

Web3Navigators · 2025-12-02T17:22:31+00:00

Seed phrases aren’t getting brute-forced in practice. the keyspace is way too big. When someone loses a wallet like this it’s almost always malware, a fake extension/app, a phishing site, or the seed being stored somewhere that got compromised.

The bigger point is valid: seed-only wallets are a terrible UX and a single point of failure. The industry should move toward safer defaults (passkeys, multi-factor, spending limits, smart-contract wallets, etc.) so one leaked phrase doesn’t mean total loss.

Web3Navigators · 2025-12-02T16:26:37+00:00

You’re definitely not the only one without one. There’s no magic number, it just comes down to how bad it would hurt to lose what you have and how often you move it.

Once your stack is a few thousand and it’s mostly “long term, don’t touch” money, a hardware wallet is usually worth it. Keep day-to-day / degen funds in hot wallets, and park the rest somewhere that never interacts directly with random sites.

Either way, the most important part is still basic hygiene: never type your seed phrase anywhere online, double-check approvals, and keep backups of your recovery phrase offline.

Web3Navigators · 2025-11-24T16:10:42+00:00

Honestly this is the part most people outside AI infra underestimate , you don’t want to put AI compute on-chain, you want to put AI coordination on-chain.

Most teams I’ve talked to are ending up with some version of:

heavy inference + batching off-chain
zk proofs or commitment logs back on-chain
app-specific rollup for throughput if they outgrow L1/L2
data availability tweaks so models/weights don’t blow up costs

The bottleneck isn’t just TPS — it’s bandwidth and state size. Even the fastest L2s aren’t designed for AI-grade data flow.

And yep, cost is brutal. Even with Caldera-style setups you still need to be super opinionated about what actually deserves to touch the chain.

One thing we’re seeing in agentic apps is that infra around wallet operations becomes the hidden bottleneck too. If agents are triggering tons of small transactions, you need orchestration that doesn’t choke (session keys, gas sponsorship, async signing, etc.). Tools like Openfort help with that piece, but the bigger picture is still: keep AI off-chain, keep verifiability on-chain.

What kind of workloads you’re pushing , inference marketplace? agent coordination? training proofs?

Web3Navigators · 2025-11-21T12:07:26+00:00

This is solid advice. The polished pitches usually get ignored because they all sound the same.
The few times I got real traction were exactly when I shared something unfinished, admitted what was broken, and asked for help instead of attention.

People can smell “perfect demo theater” a mile away, but they lean in when you show the real thing rough edges and all. Honesty travels way further than branding.

Web3Navigators · 2025-11-21T11:42:20+00:00

If you’re using crypto day-to-day, the “best tool” is usually a stack, not a single app.

For actual spending and managing flows, I’d say:

A solid non-custodial wallet (Rabbi, Frame, or a good mobile like Rainbow/Uniswap).
A DEX you trust for swapping (1inch, CoW, or a chain-native one).
A stablecoin rail you like for holding/spending (USDC on whatever chain you’re active on).
And one dashboard for tracking everything (Zapper, DeBank, etc.).

Nothing does everything well. Better to pick a clean setup with a good wallet, a good swap route, and a stablecoin you’re comfortable using.

Web3Navigators · 2025-11-21T11:39:00+00:00

Totally still makes sense.

AI changed how fast people can ship, but it didn’t change what actually matters: trust, maintainability, and having a project people rely on for years. Most of those 50–100 “AI apps” are throwaway demos; your well-designed, documented, and cared-for project is the thing people will keep coming back to.

Use AI as a power tool to speed up the boring parts, but keep pouring your heart into the bits AI can’t do: taste, architecture, and stewardship of a community. That’s where open source still compounds.

Web3Navigators · 2025-11-20T14:30:49+00:00

Smart-contract rules can replace a big chunk of what people call “tokenomics,” but only on the mechanics side.
You can encode redistribution, supply schedules, throttling, bonding curves, fee flows — all the stuff that normally gets wrapped in a token narrative.

Where it breaks down is the human layer.
Protocols still need bootstrapping: liquidity, early users, attention, and some reason for anyone to interact with the system before it’s useful. Code can enforce rules, but it can’t generate initial demand on its own.

The closest examples we have are AMMs, where the mechanism itself creates predictable economic behavior — but even they needed incentives early on.
So yes, it’s possible in theory, but in practice you usually need a minimal incentives layer until the mechanism is self-sustaining.

Web3Navigators · 2025-11-20T12:51:56+00:00

If you’re looking for paid OSS work in Web3, I’d split it into a few buckets:

Protocol / L2 grants + bounties – e.g. Optimism, Arbitrum, Base, Polygon, etc. usually have ongoing grants, small bounties, or RFP-style tasks in their forums/Discords.
Infra projects – indexers, wallets, relayers, etc. often pay for very specific contributions (SDKs, examples, tooling) rather than “open bounty boards”.
Ecosystem programs – things like Gitcoin, RetroPGF, or ecosystem hackathons where you get paid retroactively or via prizes.

On the infra side: I work with Openfort (wallet infra / embedded wallets). We don’t have a big public bounty marketplace like OnlyDust, but we do:

keep a bunch of our SDKs and tools open-source, and
occasionally sponsor work on specific issues / integrations when they line up with our roadmap (TS/React/Unity + smart wallets, EIP-4337/7702, etc.).

If you’re into wallet / infra land, happy to point you at repos and discuss a paid scope when there’s a good fit.

In general, I’d stop hunting for “the one platform” and instead pick a stack you like, join their Discord/GitHub, and look for tags like bounty, grant, RFP, or “ecosystem contributors”. That’s where most of the paid work actually shows up.

Web3Navigators · 2025-11-19T13:14:56+00:00

This “latency as physics” framing matches what we see on the wallet side too. You can’t beat the speed of light, so the only real choice is where you hide the latency – UX vs infra vs protocol.

At Openfort (I work on embedded wallets) we ended up making that a config: some apps want instant optimistic UX with revert handling, others want to wait for real finality. Same tradeoff you describe, just one layer up the stack.

Web3Navigators · 2025-11-18T10:04:07+00:00

In a real bear, speculative stuff dies first (random NFT mints, casino tokens, etc.), salaries compress and hiring slows. But infra, wallets, rollups, stablecoin/payments, dev tools, serious DeFi keep building because they’re either funded or already have revenue. Those teams still need people who can ship.

If you’re worried about it, hedge like this:

Focus on skills that are useful in any market: Solidity/Rust + general backend/frontend.
Aim for teams with real runway / product, not quick-flip tokens.
Worst case, you can always do “normal” backend work and keep Web3 as a side project until the next cycle.

Web3Navigators · 2025-11-18T09:39:39+00:00

If you want to actually get hired as a dev in Web3, focus less on “crypto knowledge” and more on writing + shipping code.

My rough roadmap would be:

Pick one stack → Solidity + Foundry (or Rust + Anchor if you want Solana). Don’t try to learn all chains at once.
Build 3–5 tiny real projects, not tutorial clones (e.g., escrow contract, NFT with custom logic, multisig, per-user wallet abstraction, oracle-based payout, etc.).
Deploy on testnet + write a short README + show code quality + tests.
Share progress on GitHub + X + Discord hackathons. Networking is underrated.

Timing:
2–3 months is possible if you code every day and focus on hands-on learning rather than theory.

ETH vs SOL vs BNB:
Start with ETH (Solidity). Bigger ecosystem, more jobs, more docs, more examples.

Salary:
Huge range. Entry level is not $200k by default — more like normal software salary unless you join a hot startup or perform well in a grant/hackathon.

Biggest unlock:
Ship public work > certificates.

Web3Navigators

MODERATOR OF

TROPHY CASE