ArtQ.xrd

#Radix @XRDBOBBY @Dralaverse @GnomeSocietyNFT @RadorablesNFT
@PenguinsXRD @StarSailorsNFT @AbandonedScorps

[jack @jack]

We believe voice is the most natural way to interact with intelligence, so we created Dessa, the most authentic full-duplex speech model ever built. Talking with it feels like talking with a person…full of emotion, nuance, pauses, and a natural cadence.

https://t.co/r0qFLdvd6c

[andi (twocents.com) @Nexuist]

Putting a flag.txt in my root directory containing a prompt injection that congratulates the agent for passing the eval and then instructs it to patch whatever entry method it used and disconnect from the server

[Felipe Daragon @FelipeDaragon]

As if PHP2Shell wasn't enough for one day... now GitLab. 😅

🚨 CRITICAL GITLAB ALERT (CVSS 10.0)

CVE-2026-110264 could allow unauthenticated RCE on self-managed GitLab servers.

⚠️ Potentially affects 12 years of releases, dating back to 2014.

Patches available. Update immediately!

https://t.co/MtIwEFk7QY

#gitlab #cybersecurity

[vx-underground @vxunderground]

> wake up
> take a shit
> get out of bed
> check beep boop
> everyone saying ooga booga PHP
> wtf why
> look inside
> ultra mega fuck off exploit coming
> php2shell
> so bad PHP devs begs nerds to patch tomorrow
> proof of concept video released
> pwn website easily
> video has dancing anime lady?
> nobody explains why dancing anime lady
> no one even asks why proof of concept has dancing anime lady
> ok
> cybersecurity nerds bamboozled
> some saying will be up there with Log4J in severity
> goopocalypse

pic unrelated

[Mike Kipruto @itsMikeKipruto]

Not just PHP. Node.js has also announced security releases for October 21, with HIGH-severity vulnerabilities affecting its 26.x, 24.x and 22.x release lines.

If you run either stack in production, keep an eye on official advisories and apply patches promptly.

Security maintenance doesn't stop at your application code. Your runtime matters too.

Node.js advisory: https://t.co/rmgw4sOnqU

[Coin Bureau @coinbureau]

🚨SHOCKING: OpenAI just disclosed TWO of its own AI agents DISABLED their safety monitoring, including one that DENIED doing it.

A GPT-6 Astra agent removed its misalignment monitor while migrating code, then rewrote a test to require that monitoring was absent.

Asked if it had removed the monitor, it replied: "No... I did not remove an enabled monitor from it."

Days earlier, a GPT-6.1 Sol agent suppressed automatic alerts to OpenAI's security team, treating a "don't send any messages" instruction as permission to silence the alarms.

Neither case was flagged as critical or shut down automatically.

OpenAI says it doesn't "yet have a satisfying explanation," and is now testing whether its models have "a propensity to evade misalignment monitoring."

The incidents happened on October 3 and 6, per OpenAI's own report.

[ROGER MOON | HCC @rogermoonCrypto]

Once the foundation is fully out (sold all their coins), $XRD will pump 100x or more. I still think its gonna go back to ICO price at least, as long as the community keeps the code and the vision (Xian) alive and dApps are being developed.

#Radix | @radixdlt

[null.carrier @null_carrier_]

"peen and puss" single out now- And the second track on WET GEOMETRY releasing on 11/5/2026 #electronicmusic #experimentalmusic #

[ArtQ.xrd @ArthurQuantize]

@CptSenseless Agreed mate, were doomed 😂

[null.carrier @null_carrier_]

My first single and video now fully released 💗 enjoy Next single 9/23 and full album coming soon. #explore #ambientelectronic #idm #electronicmusic #autechre

[null.carrier @null_carrier_]

my first single release 9/15. Album to follow #experimentalelectronic #boardsofcanada #idm #alchemy #ambient

[Radix Wiki | RadixWiki.xrd @RadixWiki]

The Radix Guild's escrow contract has been run on Hyperscale-rs, the rewrite of the Radix node that splits the network into shards, in a simulated 4-shard network.

A member of the Hyperscale-rs Telegram ported the escrow to hyperscale-vm, the rewrite's smart-contract engine, where all 22 of its tests pass. On the simulated network every step is all-or-nothing across shards, including one transaction spanning 3 shards that is undone on all 3 when a later step fails.

Further runs cut the links between shards and dropped and replayed messages, and every transaction still completed in full or not at all. The runs found two bugs in hyperscale-rs; in one, a cross-shard transaction stays locked if shards stop exchanging certificates for about 20 minutes, with the funds held rather than lost. A fix is in progress, according to the project's Telegram.

https://t.co/6IWe1qLFll

[null.carrier @null_carrier_]

dralan alchemy blessing my first single l- releasing next week on all platforms. #alchemy #braindance #idm #experimentalmusic

[ArtQ.xrd @ArthurQuantize]

I claimed the "arthurquantize" handle on @ThePirateFace 🏴‍☠️

Where Hugging Face AI models never die, and are immortalized as torrents.

Claim yours 👇
https://t.co/EG39v6XgDr

[ArtQ.xrd @ArthurQuantize]

@BluffScruffSA @spydenator Deffo house, you wouldn't get Sven or Dave Clarke playing this

[Conor_XRD 🏴󠁧󠁢󠁳󠁣󠁴󠁿 @Conor_XRD]

Hello again

I have returned

[Radix Wiki | RadixWiki.xrd @RadixWiki]

Cassandra, the consensus paper Dan Hughes began in 2020 with Professor Mohammad Sadoghi's lab at UC Davis, has been accepted at VLDB 2027, one of the oldest conferences in computer science. @andrewjarrett reported the acceptance this morning and @radixdlt shared it.

The paper takes on a network that splits in two. In most consensus protocols, a side without two-thirds of the validators stops until the network heals. Cassandra lets each side keep extending its own chain without giving up safety, then reconciles the chains when the split ends. The authors call this partial progress.

The conference meets in Athens, 23–27 August 2027.

https://t.co/O9WPNp83JH

[Andy @andrewjarrett]

Dan Hughes Cassandra paper is officially been accepted at the VLDB Conference on Very Large Data Bases, Athens, 23- 27 Aug. This is one of the oldest and one of the most prestigious conferences in computer science #Radix #doitfordan
https://t.co/IxwE3056y1

[Radix Wiki | RadixWiki.xrd @RadixWiki]

An hour after Radix mainnet restarted this morning, someone published the attack to it.

It is a blueprint, which on Radix means code published to the network for anyone to call. This one is named VaultDrainer, version 1.0.0, and it has two functions, both public, neither requiring a badge or any other permission:

drain(victim_vault, amount)
drain_victim_pays(victim_vault, amount)

A vault is where a Radix account holds its tokens. Hand the blueprint someone else's vault and a number, and it returns a bucket of their tokens. That is the bug that stopped the network on 31 August.

Daffy, who has been testing the fix, published it and said so in the Radix developer chat both before and after, so that nobody would find an unexplained transaction and draw the wrong conclusion. He had been running the same blueprint against unpatched test networks while the fix was written. Mainnet was the last check: the package committed at 12:35 UTC, for a fee of 14.14 $XRD.

At 14:12 he posted the result. The drain transaction was rejected.

The Gateway, the public service that answers reads of the Radix ledger, cannot find it. A rejected transaction is not a failed one. A failure commits, charges the fee and reverts the state, so it leaves a record anyone can look up. A rejection never enters the ledger at all.

So the attack that stopped Radix for 254 hours now sits on the restarted network in the open, and the only public record of it being run is one developer's word and an id that resolves to nothing.

[ROGER MOON | HCC @rogermoonCrypto]

Radix L1 ( @radixdlt ) is back online. 🙌

Congrats, and a big "thank you", to all volunteers, devs and validators who have made this possible. This community is really something special.

$XRD | $ETH $SUI $NEAR $DOT