Get $MAG
MAGNET

Two poles. One direction.

A fixed share of every trade splits across two opposing poles. North mints liquidity and burns the receipt, south buys $MAG and destroys it. Magnetization never reverses.

Field strength$0
Gauss0
Domains0
Demagnetized0
the premise

Like poles
repel.

Locked liquidity is a countdown. Vested liquidity is a promise. Both assume somebody keeps their word on a date you will not be watching.

MAGNET removes the assumption. Every call that would drain a market meets an identical field and is pushed back by the bytecode itself. There is no extraction path to defend, because the pole that would let value out faces the same way as the pole holding it in.

extraction attempts, repelled
the dipole

Two poles, every trade,
same block.

The dipole sits underneath each market and runs on every swap in both directions. Buys and sells cross identical poles. A magnet has exactly two poles, so the engine has exactly two legs, and they do opposite jobs.

North  /  attract
0%

Paired against the reserve at the live ratio and minted into the pool as a new LP position, then burned to 0x…dEaD in the same block. Depth that exists and ownership that does not.

Terminal: burn address
South  /  repel
0%

Spent buying $MAG off the open market and destroying it. Supply is repelled out of existence, so the field behind every remaining token strengthens without a single new dollar entering.

Terminal: supply destroyed
remanence

The loop only
opens outward.

Drive a magnetic material one way and it magnetizes. Take the field away and it keeps what it took. The width of the loop is the memory. MAGNET's loop expands on every trade and has no path back inward. Keep scrolling and watch it open.

Trades applied0
Remanence, Br0 G
Coercivity, Hc0 Oe
Loop area0
Contracted, ever0 times
b–h loop  /  magnetization against applied field
pull rate lab

Set the pull rate.
Watch the field strengthen.

A higher grade pulls harder off every swap and costs the trader more to cross. Every domain picks its grade once, at deploy, and it is written into the bytecode. Drag it, and set the volume it has to work with.

pull rate
3.00%
N35 / 1.50N45 / 3.00N52 / 5.00
daily volume
$2.50M
$1M$20M$40M
GradeN45
Flux per $1M traded$30,000
North, burned LP per day$45,000
South, $MAG destroyed per day$30,000
Field strength after 30d$2,250,000
Retrievable by anyone$0.00
b–h loop at this grade  /  30 days

Faint loops behind the live one are the grades below it. The loop has no inward case at any input. Flux that has crossed a pole is not subtracted, only added to.

pull rate grades

Three grades of field.

Named the way magnet grades actually are. The number is the energy product, and on a real magnet it is stamped on the body where anyone can read it. Here it is in the bytecode, where any trader can read it before touching the market.

N35
1.50%

Weak field. Cheapest to trade through and slowest to magnetize. The field still only rises, it just rises on more volume.

Suits high frequency markets, tight spreads, majors
N45
3.00%

The default. Balanced cost against a field that measurably strengthens inside the first week at ordinary volume.

Suits most launches
N52
5.00%

Maximum grade. Strongest pull, fastest magnetization, highest cost per swap. Nothing above this exists in the contract.

Suits long horizon supply, low float, conviction markets

Liquidity lives on
Robinhood Chain.

MAGNET settles on Robinhood Chain, an Arbitrum Orbit rollup, chain id 4663, fully EVM. The dipole is a plain contract with no owner, and both poles are public transactions anyone can replay.

Burned LP and destroyed supply, so field strength is arithmetic and not a promise
Both poles run inside the swap, capped gas, public calldata
No admin path exists to pause, upgrade, demagnetize or drain a domain
4663
Chain id
0x1237
Hex
Orbit
Arbitrum L2 rollup
v4
Uniswap pools
network

The numbers you need
before you point a wallet at it.

Click any value to copy it.

magnet@robinhood-chain  /  network readout
Network
Robinhood Chain
An Arbitrum Orbit rollup. EVM equivalent throughout, no compiler fork.
Chain id
4663
Decimal. The same value is 0x1237 in hex if your wallet asks for it that way.
Hex chain id
0x1237
What most wallets want when you add the network by hand.
Testnet id
46646
Break it there first. The dipole is the same bytecode on both.
RPC endpoint
rpc.mainnet.chain.robinhood.com
No MAGNET endpoint sits between you and the chain. Point at any node you like.
Testnet RPC
rpc.testnet.chain.robinhood.com
Same interface, throwaway value.
Explorer
robinhoodchain.blockscout.com
Every pole event is an ordinary transaction. Replay any of them without asking us.
Currency
ETH
Eighteen decimals, used for gas.
Rollup stack
Arbitrum Orbit
Orbit chains inherit the Arbitrum Nitro execution stack rather than a bespoke one.
Pool venue
Uniswap v4
Domains deploy as v4 pools. The dipole runs inside the swap path, not beside it.
Dipole address
Published at deploy
The verified contract goes up with the first domain. Nothing to trust in advance.
Chain id 4663 Hex 0x1237 Stack Arbitrum Orbit Pools Uniswap v4 Gas ETH
protocol parameters

Sealed at deploy,
readable before you sign.

Six values that cannot move after genesis. Try one.

LOCKED
Pull rate
Set once at deploy
Stored immutable. No setter exists in the compiled contract.
LOCKED
North split
60% to burned LP
Hardcoded. Every minted position lands at 0x…dEaD in the same transaction.
LOCKED
South split
40% to buy and burn
Market buy, then burn. The tokens are gone from supply, not parked in a wallet.
LOCKED
Admin keys
None
No owner, no roles, no pause, no upgrade path, no proxy.
LOCKED
Coercivity
Infinite
No function demagnetizes a domain. There is nothing to call and no field large enough.
LOCKED
Curie point
Unreachable
The state is bytecode, not temperature. Nothing on chain gets hot enough to randomize it.
the token

$MAG

The protocol token runs on its own dipole at N45. Same two poles, same burn address, same absence of an owner. It is the reference domain for how every market on MAGNET behaves, and the south pole of every other domain buys it.

Supply1,000,000,000
Supply directionMonotonically decreasing
Mint functionAbsent after genesis
Pull rateN45 / 3.00%
North / south60% / 40%
Team allocation0%
Genesis liquidityBurned at launch
Taxes beyond pullNone
RemanenceTotal
contract address

This is the only address.
Anything else you are shown is fake.

Live $MAG is live on Robinhood Chain. Verify every character against this page.
0x14e7efea701b667cfb4b94d86221bad7ccf1cfc3
Two sources only

This page and the official X account. An address from a reply, a DM, a group or a bot is not from us, no matter who it looks like.

One token only

Any other $MAG is somebody else's token using the name. There is no presale, no allowlist and no private round, and there never was one.

Check every character

Compare the full string, not the first four and last four. Copy from here rather than typing it, and verify the contract is source verified on the explorer before you sign anything.

by the numbers

Everything that only
moves one way.

Modelled across all aligned domains at present volume. Every figure below has no decreasing case in the contract.

$0
Burned LP, north pole
Minted into pools and sent to the burn address in the same block.
$0
Supply destroyed, south pole
Bought off the open market and removed from circulation permanently.
0
Field strength, gauss
The scalar the protocol reports. It has never printed a lower number than the one before it.
0
Domains aligned
Each one a separate pool with its own grade written at deploy.
0
Swaps crossed the poles
Buys and sells both. The pull rate is symmetric.
0
Admin keys in existence
There is no owner to compromise and no role to grant.
0
Domains demagnetized
No function exists to do it, so the number is structural rather than lucky.
0
Dollars ever retrieved
Not by us, not by a team, not by anybody holding a key.
roadmap

Align, then widen.

Four phases. No dates on this page, because a slipped date is worse than no date.

Complete
PHASE 01

Bench

Dipole contract written, both poles wired into the v4 swap path, pull rate sealed in immutable storage. Internal testing on the 46646 testnet.

Current
PHASE 02

Magnetize

Source verification published, third party review, testnet open to anyone who wants to break it. $MAG genesis with liquidity burned at launch.

Next
PHASE 03

Align domains

Permissionless deploy opens. Any market can align a domain in one transaction and pick its grade. Field strength reported per domain on chain.

Planned
PHASE 04

Widen

Cross domain field reporting, an open indexer for loop area per market, and the dipole deployed anywhere EVM bytecode runs.

what mag does not promise

The three things
a strengthening field is not.

Read this part before the FAQ. It is the part most protocols leave out, and it is the part that decides whether the rest was worth reading.

01

Field strength is not price.

The field is burned liquidity plus destroyed supply. That is depth underneath a market, not a bid. Price trades wherever buyers and sellers put it, and it can sit below where you bought for as long as the market wants it to.

02

The field strengthens on volume, not on time.

Nothing accrues while a domain sits still. A market that has not traded since it deployed has a field exactly as strong as the day it deployed. Waiting is not a strategy here, because the engine only runs when somebody crosses a pole.

03

A strengthening field is still not an up only position.

Permanent liquidity removes one specific failure, the pool being emptied by whoever holds the keys. It does not remove market risk, it does not remove the possibility that a domain is worth less than you paid, and it does not make an unaudited contract safe.

questions

The short answers.

What stops the team pulling the liquidity?

The path does not exist. The north pole mints an LP position and sends it to the burn address in the same transaction, and the contract ships with no owner, no roles and no upgrade path. There is nothing to compromise and nobody to compromise it.

Can the pull rate change after launch?

No. It is written at deploy and stored immutable. Any domain claiming a changed rate is a different contract at a different address, which is worth checking rather than assuming.

Why split it across two poles instead of doing one thing well?

Because the two failures are different. Burned LP fixes depth, which is what stops a market gapping to zero on an exit. Buying and burning $MAG fixes supply, which is what makes the remaining tokens harder to get. One pole solves half the problem and leaves the other half open.

Does the field ever weaken?

No. Burned liquidity is not removable and destroyed supply is not recoverable, so the scalar has no decreasing case. Price still moves on supply and demand like any market. Field strength is not price, which is worth reading again in the section above this one.

Who pays the pull rate?

Whoever is trading, in both directions, at the rate quoted before signing. It does not go to a treasury or a team wallet. It goes into the pool and into the burn, and both receipts are public.

What happens to $MAG if nobody trades?

Nothing. That is the honest answer. The dipole runs on swaps, so a market with no volume magnetizes at exactly zero gauss per day. There is no emission, no staking yield and no time based accrual anywhere in the contract.

Has it been audited?

Not yet. Source verification and third party review are phase two and neither is finished. This is unaudited experimental software today, and treating it as anything else would be a mistake.

Could you not just deploy a second contract that does have an owner?

Anybody can deploy anything. That is why the address on this page is the only one that matters and why we would rather show a zero address than a placeholder that looks real. Check the address, check the verification, then decide.

What does it cost to align a domain?

Gas, and the grade you pick. No listing fee, no application, no allowlist. Deploy is one transaction.

Which chain?

Robinhood Chain first, chain id 4663, EVM throughout. The contract is chain agnostic and deploys anywhere EVM bytecode runs.

Align it once
and walk away.

One transaction. No allowlist, no application, no key to keep safe afterwards.