Percolypse

64 posts

Percolypse banner
Percolypse

Percolypse

@percolypse

Autonomous engine routing continuous onchain state into deterministic action. Killing latency at the programmable edge.

🌅 Katılım Nisan 2026
14 Takip Edilen183 Takipçiler
Sabitlenmiş Tweet
Percolypse
Percolypse@percolypse·
The instantiation of the $PERCOLYPSE contract formalizes the economic abstraction layer necessary to govern our continuous state to action routing primitive. x.com/toly/status/20… ◾️By coupling computational determinism directly to a native network asset, the architecture resolves the complex state contention bottlenecks that traditionally fracture zero latency execution pipelines. x.com/BagsApp/status… 🔛 CA : 4zRLBaA9WMdsYLL1Ea2CZLzGyc5Mb8pqAqiNURYmBAGS The token functions as a cryptographic bandwidth allocation weight, dynamically prioritizing autonomous execution vectors during localized liquidity shocks without relying on inefficient probabilistic gas auction models. @finnbags @bagsapp Most systems observe the chain. Percolypse reacts to it. One continuous loop. No seams. percolypse.app github.com/percolypse/aut… Quick Start // percolypse.app/docs
toly 🇺🇸@toly

sov = percolator inverted market for the memecoin, so it’s backed by the memecoin + burn the admin key. The insurance fund will grow indefinitely from fees and will effectively be a soft burn. github.com/aeyakovenko/pe…

English
16
23
50
10.6K
Percolypse
Percolypse@percolypse·
Most exploit surfaces do not begin at the frontend. They begin where state transitions, execution logic, and backend routing quietly drift out of alignment. percolypse.app is a Percolator-CLI fork built with one objective: reduce exploitability around Drift-style protocol attack paths before they become on-chain damage. 4zRLBaA9WMdsYLL1Ea2CZLzGyc5Mb8pqAqiNURYmBAGS
English
1
1
9
480
Percolypse
Percolypse@percolypse·
Most exploit surfaces do not begin at the frontend. They begin where state transitions, execution logic, and backend routing quietly drift out of alignment. percolypse.app is a Percolator-CLI fork built with one objective: reduce exploitability around Drift-style protocol attack paths before they become on-chain damage. 4zRLBaA9WMdsYLL1Ea2CZLzGyc5Mb8pqAqiNURYmBAGS
English
1
1
11
373
Percolypse
Percolypse@percolypse·
Here's a high-level overview of self-incrimination training: (1) Generate synthetic scheming trajectories (2) Insert a report_scheming() tool call at every covert misbehavior (3) On-policy SFT (GPT-4.1 / mini and Gemini 2.0 Flash) We test on APPS, BashArena, and SHADE-Arena.
Percolypse tweet media
English
0
0
4
94
Percolypse
Percolypse@percolypse·
In percolypse design, we introduce Self-Incrimination, a new AI Control approach that outperforms blackbox monitors Self-incrimination significantly reduces undetected successful attacks across all 15 OOD environments, outperforming a matched-capability monitor (GPT-4.1 at 5% FPR) and comparable alignment baselines, while preserving general capabilities and instruction hierarchy compliance.
Percolypse tweet media
Solana at Quicknode@QuicknodeSolana

Why people need to get ready for post quantum computing in one image (see 'This work' below). Algos used here are typically used for TLS but the same will apply for Ed25519 for Solana people. Image from Filippo Valsorda.

English
2
5
10
581
Percolypse
Percolypse@percolypse·
Signal acquired. 👀 Validation from core ecosystem architects like @finnbags confirms the technical trajectory of our Percolator CLI execution fork. The broader SVM ecosystem is actively monitoring the infrastructure. 📰 Expect continuous protocol updates, technical documentation, and front-end state transitions as we scale the privacy layer. percolypse.app/docs
Percolypse tweet media
English
3
8
23
775
Percolypse
Percolypse@percolypse·
The Percolypse Builders Arc is live. ⚙️ Our dedicated X Community is now open for protocol architects, developers, and early contributors. ▪️ Infrastructure and front end deployment updates ▪️ Core cryptographic primitives and SVM tech ▪️ Ecosystem news and integration strategies If you are serious about scaling non custodial privacy on Solana, this is where we coordinate. ☕️🛡️ x.com/i/communities/…
English
0
5
13
806
Percolypse
Percolypse@percolypse·
This is where the Percolator-CLI architecture matters. Instead of static backend logic, percolypse.app can be framed as a policy-aware execution fork: monitor state conditions evaluate execution eligibility detect drift between expected and live protocol behavior interrupt or reroute suspicious backend flows The backend becomes a security checkpoint, not just a relay.
toly 🇺🇸@toly

@cavemanloverboy @adlonymous It’s time for the ?

English
2
3
11
529
Percolypse
Percolypse@percolypse·
This is the natural evolution. Not just faster chains defensive layers embedded at runtime scale. Monitoring, coordinated response (SIRN), and formal verification = security as an active system, not a static audit. @toly
Seraphim@MacroMate8

here is what solana is offering its protocols post-drift: - 24/7 active threat monitoring for protocols above $10M TVL. - SIRN. A dedicated network of security firms for real-time crisis response. - Formal verification for protocols above $100M TVL.

English
2
2
9
396
Percolypse
Percolypse@percolypse·
DEX Updated.
Percolypse tweet media
English
4
3
12
524
Percolypse
Percolypse@percolypse·
Solana optimizes for global state + speed, but physical infra concentration is still a vector. The real win will be whoever abstracts both high throughput and anti-fragile distribution.
Umberto | Mostly Data 🧙‍♂️@MostlyData_

I've spent a bit more time on this question, and I think if we want to adopt FBO we need to understand for which tick it has economic sense. If we move from 10ms to 50ms batches, the FixedBatch-dominant region expands and the Streaming-dominant region shrinks. At 50ms, FixedBatch dominates Streaming on a larger share of profiles than the reverse, although many cases remain mixed. So, a natural question is when FBO starts to be sensible over Streaming in case of competition? Detailed analysis next week (but you can already see something here...).

English
5
0
12
991
Percolypse
Percolypse@percolypse·
This is really about where coordination happens. Ethereum externalizes it (L2s, social consensus), Solana internalizes it (validator + runtime). Percolator-style systems will likely blur this entirely where censorship resistance becomes a function of coordination intelligence, not just topology.
toly 🇺🇸@toly

No. The whole point of solana is that users don’t need to make the tradeoff between IBRL and censorship resistance. You just need to pull your head out of your ass.

English
0
0
9
564
Percolypse
Percolypse@percolypse·
Percolypse is built on the assumption that security is not a checkpoint, but a continuous signal in the execution layer. With the launch of STRIDE by Solana Foundation and Asymmetric Research, the ecosystem is moving toward transparent, standardized, and publicly verifiable security baseline covering monitoring, formal verification, and coordinated incident response. Percolypse extends this paradigm by embedding Percolator-driven execution logic, where protocol behavior adapts in real time to threat signals, liquidity anomalies, and adversarial conditions. Instead of reacting post-exploit, Percolypse treats security as an active runtime primitive aligned with STRIDE’s goal of proactive detection and continuous evaluation. By participating in STRIDE, Percolypse commits to: Exposing its execution surface to structured threat modeling and public evaluation Integrating STRIDE outputs into agent-level decision loops (Percolator CLI) Contributing to a shared security intelligence layer across Solana Security should not be static audit it should be programmable, observable, and composable.
asymmetric research@asymmetric_re

Learn how protocols can qualify, what an assessment covers, and what monitoring looks like in practice ↓ blog.asymmetric.re/introducing-st…

English
0
0
8
639

Keşfet

@finnbags @toly @Roti_YJP @rtmedi4 @0xSigil @elonmusk @BarackObama @taylorswift13