Our thread was taken down, seems to be getting mass reported, also site has been getting ddos'd so we are updating that, and increasing helius limits. Bad actors targetting the website.
All bugs will be fixed, all feedback will be heard.
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?
We are doing our best to address load but also are experiencing DDoS attacks.
Thank you for bearing with us!
Higher retweeted
Gah, sorry about that, hit the wrong button. Got questions? Ask here.
teapaw.org/i/spaces/1rJqkplbzzyvB…
Higher retweeted
Replying to @maradydd @Higherdotfun_
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.
Higher retweeted
Replying to @maradydd @Higherdotfun_
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…
Higher retweeted
Replying to @maradydd @Higherdotfun_
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.
Higher retweeted
Replying to @maradydd @Higherdotfun_
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.)
Higher retweeted
Replying to @maradydd @Higherdotfun_
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.
Higher retweeted
Replying to @maradydd @Higherdotfun_
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.
Higher retweeted
Replying to @maradydd @Higherdotfun_
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.












