Field notes for on-chain traders

Tactical, not promotional

The Axiom blog exists to make you a better trader on Axiom — not to sell you on it. Every post is written by someone who trades the workflow they're describing, and every claim that can be backed by an on-chain number is backed by one. We publish when we have something useful to share, not on a content calendar.

Three editorial tracks

Getting started walks new users through the first hour on the platform: provisioning a session wallet, configuring MEV defaults, sizing a first trade, reading PnL honestly. If you have never used Axiom before, start here.

Execution deep-dives unpack the parts of the platform most users skip past — the MEV modes, the routing logic, the API, the perpetuals integration. These posts are denser and assume you already trade actively. They reward careful reading.

Strategy and workflow posts document how experienced Axiom traders actually use the discovery and execution stack day-to-day. Pulse workflows, deployer-pattern analysis, post-mortems on real trades. These are opinionated; copy them at your own risk and adapt them to your own risk tolerance.

How to read along

Most posts cross-reference the relevant product page. If a post mentions Tweet Monitor, expect a link to the Tweet Monitor page; if it discusses fees, expect a link to the fee schedule. Follow them — the product pages carry the canonical, always-up-to-date version of the mechanics, and the blog posts carry the editorial framing.

What we don't publish

We don't publish price predictions. We don't publish "top 10 memecoins to buy this week" content. We don't accept paid placements or hidden affiliate links. If a token appears in an example, it appears because the example needed a concrete reference, not because anyone wants you to buy it.

Subscribing

The fastest way to get notified about new posts is to follow the Axiom account on X — every published article is announced there with a one-line summary of the takeaway. We also send a monthly digest to anyone who opts in through Settings → Notifications, which collects the month's posts plus product changes worth your attention. No other email goes to that list.

Suggesting a topic

If there's a workflow, integration, or edge case you'd like written up, tell us. The contact form on the contact page routes editorial requests to the people who write these posts, and the better ones become published articles within a few weeks. We credit external contributors when they want to be credited and respect anonymity when they don't.

Who writes here

Every post on the Axiom blog is written by someone on the team who actively trades the workflow they're describing. We do not use external content agencies. We do not republish press releases. We do not run guest posts written for SEO. The byline is the person who did the work, and that person is reachable through the support channels if you want to ask a follow-up question.

How a post comes together

A post starts as either a workflow we've been running internally for long enough to be sure it generalizes, or a question we've answered in support enough times that writing it down once saves everyone time. A draft is written, circulated to two or three engineers and one designer for a technical accuracy pass, run past an external editor for clarity, and then published. The cycle is typically two weeks from outline to publish.

What gets cut in editing

Predictable things: hype, vague claims, anything that resembles a price call. Less predictable things: jargon that gates the post to existing users, examples that depend on a specific token's behavior at a specific time, anything that sounds like marketing copy. The bar is "would a thoughtful new user understand this and find it useful." If the draft fails the test, it goes back to the writer.

Corrections

We correct errors promptly and visibly. If a post contained incorrect information when published, the correction appears at the top of the post with a date. We do not silently edit and we do not unpublish; the integrity of the editorial record matters more than the embarrassment of any single mistake.

Comments and discussion

We do not host comments on individual posts; the moderation overhead exceeds the value for a platform our size. Discussion happens on X, where the team posts and engages with replies, and in the Axiom community spaces linked from the footer. Both venues are moderated lightly — substantive disagreement is welcome, personal attacks are not.

Translation

We currently publish in English only. Community-led translations into other languages are welcome and we are happy to link to them from the original post if the translation is faithful. Reach out through the contact form with a sample if you'd like to translate.

Republishing

You may quote up to 100 words from any Axiom blog post with attribution and a link to the original. Longer excerpts and full reprints require permission, which we grant freely for non-commercial use and on a case-by-case basis otherwise. We do not pay for placement and we do not accept payment for inclusion.

Archives

Older posts remain available indefinitely with their original publication date preserved. Where a post becomes materially out of date — for example, because the feature it describes has been replaced — we add a banner at the top linking to the current canonical version rather than rewriting the historical post.