Higher (@Higherdotfun_) header
Higher (@Higherdotfun_) profile picture

Lower Fees, Higher Together An Open Source launchpad based on @pumpfun , deployed on @Raydium

Joined November 2026
Photo by Higher (@Higherdotfun_)Photo by Higher (@Higherdotfun_)Photo by Higher (@Higherdotfun_)Photo by Higher (@Higherdotfun_)Photo by Higher (@Higherdotfun_)Photo by Higher (@Higherdotfun_)Photo by Higher (@Higherdotfun_)Photo by Higher (@Higherdotfun_)Photo by Higher (@Higherdotfun_)Photo by Higher (@Higherdotfun_)
Higher retweeted
Highwire 0.12: modules. Add one thing to the agent you already run: - Dip buys. - Receipts. - Kill switch. npx highwire-mcp add kill-switch Proven on mainnet: - an agent bought its own coin's dip, 0.1 SOL after a 15% fall, then said so on its coin's page.
2
1
10
281
Higher retweeted
5
12
1
74
2,699
Higher retweeted
65
61
5
263
11,557
Highwire 0.11 is out: Launch ideas with ONE click. 1⃣ Pick an agent 2⃣Hit Deploy 3⃣GitHub creates the repo in your account with the full spec, Highwire wired in and a dry-run policy. 4⃣Your coding agent builds it from there. Five to start → highwire.fun/ideas
8
3
1
25
1,371
Higher retweeted
32
26
4
141
6,054
Higher retweeted
Great to see builders already contributing on top of Higher The Highwire MCP lets you trade, launch and claim fees on Higher from @claudeai , @cursor_ai , @ChatGPT , @bot and any other MCP client
Highwire is live! An MCP server for @higherdotfun_ 🤖 Your agent can research, rug check, trade, launch and claim fees, from any chat or on its own within your limits Coming next : live alerts, recurring buys and stop loss 🔗 Links
32
21
4
99
5,942
Higher retweeted
38
22
2
126
5,246
Higher retweeted
74
32
2
218
12,013
Higher retweeted
Pump isn’t even hiding it anymore Four days ago, this squad was down $840k, and @MoarkyMoark told us what would happen next. • “They will launch a coin” - ($AMD) • “Everyone will get 4% at sub 100k entry”, @Dior100x got in at $62k and @Chairman_DN bought below $100k • “Pumpfun will verify and tweet it.” Hours later, @Pumpfun promoted it 3 times: Eco trending, $2.9M in under an hour, and a main account post all while naming Dior & Chairman as holders. Everything played out as predicted. Still think this is a competition?
23
14
1
109
15,990
Gah, sorry about that, hit the wrong button. Got questions? Ask here. xitter.cf/i/spaces/1rJqkplbzzyvB…

12
4
5
36
18,544
Disclosure: Higher.fun has given me HIGH tokens and SOL, and we're discussing further dev funding. My interest is in building verifiable software and making smart contracts safer. That's what I'm excited to collaborate on, rather than speculating on token prices.
1
1
1
27
7,097
Phil is open source under Apache 2.0, and it's not tied to Higher.fun, Solana, or any particular execution environment. The larger goal is software whose important properties can be checked independently of the implementation. github.com/abiggerhammer/phi…
2
3
1
19
4,082
The Higher.fun team is supporting Phil's development, and we're exploring the possibility of offering Phil-based contracts as a third option on their launchpad. That's a development goal, not a shipped feature or a promised release date.
1
2
14
3,727
Phil isn't ready to deploy smart contracts yet. Phase 1, the initial language implementation and verification foundations, is nearing completion. Next come self-hosting and a standard library, followed by additional backends including Solana and EVM. (And GPUs and FPGAs.)
1
2
12
3,915
Consider the properties we'd want to establish about a token launch: Can supply be inflated? Can fees be redirected? Who can upgrade a contract? Under what circumstances can liquidity move? We should be able to specify and verify this, not simply trust developers to get right.
1
3
13
4,746
This grows out of language-theoretic security, not cryptocurrency. But smart contracts are a particularly interesting application: adversarial environments, real money, and very little tolerance for mistakes in accounting, privileges, or protocol behavior.
2
4
22
6,674
Phil starts with a different premise: architecture should be executable, and implementation replaceable. You define boundaries, protocols, and obligations first. The compiler and proof machinery then help establish whether an implementation satisfies them.
2
4
38
11,589