John Davis writes everything here
Every guide and article on Arctools carries the same name, which is a claim worth being able to check. This page sets out what that byline covers, how the numbers in the writing are produced, and the commercial interest behind it — in that order, because the last one is the easiest to leave out.
What the writing is accountable for
A byline means someone is answerable for the claims underneath it. These are the subjects those claims are made about, and what makes each one verifiable rather than asserted.
Arc Mainnet itself
What the chain does differently from a stock EVM: USDC as the gas token, the 20 Gwei fee floor, sub-second deterministic finality, the value-transfer cases that revert. Sourced from Arc's own documentation and then checked against the live chain rather than repeated from a summary.
Token design and launch mechanics
Supply, taxes, wallet limits, anti-sniper delays, ownership and what each choice costs a buyer in trust. The trade-offs are described as trade-offs, including where the article's own recommendation would be wrong.
Liquidity, pools and locks
Pool depth, ratio matching, price impact, impermanent loss and the difference between locking and burning. The arithmetic is shown, so a reader can redo it with their own numbers instead of trusting the conclusion.
Distribution and after-launch operations
Snapshots, CSV pipelines, multi-recipient sends, ownership changes and supply management — the unglamorous half of running a token, which is where most launches actually go wrong.
Reading a token before buying it
How ownership, mint authority, tax surface and holder concentration are verified onchain, so that a claim about a token can be checked rather than believed.
Five commitments, published so they can be held to
None of this is required by anything other than the fact that the writing recommends tools the site sells.
The commercial interest is disclosed, not buried
Arctools charges a flat 50 USDC for most of the services these guides walk through. That is the whole business model, and it means the writing has a commercial interest in you using the tools. It is stated here, and on the pages that walk through a specific tool, so it is never a surprise.
No paid placements, no sponsored posts, no affiliate links
No company has paid for coverage, supplied a link, or been given the chance to review a guide before publication. There is no advertising inventory on this site, and nothing on it is written in exchange for money.
No position in anything written about
There is no Arctools token, no allocation held in any launched token and no arrangement to buy or promote one. Guides are not written about tokens the author holds.
Numbers are derived, and estimates say so
Figures in the guides come from chain parameters, the deployed contract sources, or arithmetic shown in the article itself. Where a number can only be an estimate — a gas cost, a slippage outcome, a price impact on a pool that does not exist yet — it is labelled an estimate and the assumption behind it is given.
Limits are stated up front
The contracts are not audited, and the site says so rather than implying otherwise. Nothing here is financial, legal or tax advice. Where a guide describes a risk that cannot be engineered away, it says that instead of offering a workaround.
If something here is wrong, it gets fixed
Technical writing about a live chain goes stale and occasionally goes wrong. Both are treated the same way: the page is corrected and the change is visible in its modified date.
Reporting an error
Send the page, the claim you think is wrong and, if you have one, the source that contradicts it. A transaction hash, a line of a deployed contract or a page of Arc's documentation is worth more than a description. Corrections are made on the merits of the evidence, and nothing on this site is exempt from being corrected — including the pages that describe the tools.