Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
be me
write 3000 word deep dive on saylor's money printer
mass produce three custom graphics
mass produce a cover
"just publish it bro, you have an MCP server"
MCP server doesn't connect
restart claude. still nothing
binary works. token works. config works
server just doesn't feel like it today
fine. grab session cookie manually
decode it. paste it. curl it
403
try encoded version. 403
try decoded version. 403
try with cloudflare cookies. 403
try with every cookie in the jar. 403
"just log in again"
substack uses magic link
magic link doesn't arrive
try again. doesn't arrive
try again. now they rate limit you
inbox flooded with six magic links at once. none work
"just set a password"
search entire settings page
password field doesn't exist
substack literally removed the ability to have a password
what kind of platform does this
ai decides to decrypt my browser's cookie database
reverse engineers brave's AES-128-CBC encryption
extracts the real token
token works in browser. 403 everywhere else
cloudflare personally hates me
enable "allow javascript from apple events"
a setting i didn't know existed
in a menu i've never opened
on a browser i use daily
ai starts remote-controlling my browser via applescript
tabs opening and closing on their own
like my laptop is possessed
twenty tabs. maybe thirty
each one executing javascript i cannot read
watch from the side. zero control
"this is fine"
first attempt: wrong block format
article shows up as title only. empty body
turns out substack uses "text" not "content" as json key
and "heading" with attrs not "heading-two"
documentation for this: zero
fix format. retry. body appears
images uploaded through base64 injected into browser tabs
250kb of png data traveling through applescript
this cannot be the intended workflow
"publish endpoint is PUT right?"
404
it's POST
of course it's POST
article goes live at 2am
three hours to write it
two hours to publish it
fourteen failed approaches
the article is about how saylor built a money printer
the real money printer was the bugs we fought along the way