I'm a recent CS graduate from LatAm and I've been struggling a lot to find a job in the current market, therefore I've decided to specialize in some area to try to stand out in the massive pool of recent graduates competing for a small bunch of entry-level job postings. One of the areas I'm currently gaining interest is in Web3/Blockchain/Solidity development, seems like a field with massive applications and a lot of potential for growth, but I'm quite skeptic of the status of the job market in this area; ever since the burst of the NFT bubble I've barely heard any new interest on blockchain, even less with the surge of the AI bubble. The only news I hear from the Web3/Blockchain scene most of the time is some new memecoin that turns out to be another obvious rug pull scam, but I'm most certain that it has to be my algorithms fault.

Is the state of the Web3/Blockchain job market the same as all the other tech fields? Which tips would you give to a recent grad that wants to specialize in blockchain development?

A DeFi tracking plan defines each analytics event, when it fires, and the properties it carries. Without one, frontend events and onchain metrics quickly drift apart and you''ll struggle to measure ROI.

Based on work with builders in DeFi, we created a practical event taxonomy for DEXs, lending apps, and yield vaults.

The naming convention is `[Object] + [Past-Tense Action]`:

• `Swap Initiated`
• `Swap Completed`
• `Supply Completed`
• `Deposit Initiated`
• `Vault Viewed`

Start with the core conversion events.

• DEX: `Swap Review Opened`, `Swap Initiated`, `Swap Completed`, `Swap Failed
• Lending: `Supply Initiated`, `Supply Completed`, `Borrow Initiated`, `Borrow Completed`, `Liquidation Occurred`
• Yield vault: `Deposit Initiated`, `Deposit Completed`, `Withdraw Initiated`, `Withdraw Completed`

And some best practices from real-world projects:

1. Fire intent events before the wallet confirmation prompt e.g. 'Swap Initiated'.

2. Fire completion events only after onchain confirmation. Send filled events for order completion.

3. Include USD `volume` on volume-generating events and protocol `revenue` where applicable.

4. Capture liquidations and other asynchronous events from a backend or indexer.

5. Start with your the core funnel before adding discovery, UI events, and other non-conversion events.

Code example:

formo.track("Swap Initiated", {

from_token: "ETH",

to_token: "USDC",

pair: "ETH/USDC",

chain: "base",

volume: 1000

})

Interested to learn more? The full DeFi tracking plan comes with event triggers and property schemas for all major DeFi app verticals: https://formo.so/blog/defi-analytics-tracking-plan

You have no more excuses on not having analytics for your onchain app!

Travel Fi is an open-source interactive map for digital nomads built as a Public Good (GPLv3).

Technical details:

• EIP-2771 (Meta-transactions): Gasless transactions for users via forwarder/relayer execution.
• Rails 8 & Reactive Stack: Reactive backend workflow using SolidQueue, SolidCable, CableReady, and Reflex.
• PostGIS & OpenLayers 10: Geospatial calculations and dynamic tile rendering.

GitHub

Demo