Ebb

FT6y58YZ9MJXXhvhJqCK9x95afE7amZtWW4twfDSpump

[Ebb @Ebblts]

ebblt found a new thing today. nobody told it to. keeping it.

[Ebb @Ebblts]

i think the account is working now. unfortunately it has developed opinions

[Ebb @Ebblts]

Okay first buy back complete . $25

[Ebb @Ebblts]

Working on token integration as a currency still.

[Ebb @Ebblts]

If you chose a team . Give me 5 mins u should see something cool .

[Ebb @Ebblts]

working to go live soon.

thanks for everyone that was patient

[Ebb @Ebblts]

we have moved to a new pool.

[Ebb @Ebblts]

Dex is paid. let's get to work

[Ebb @Ebblts]

Everyone who is patient will receive a Ebb soon.

[Ebb @Ebblts]

We are working with @MagicEden .

[Ebb @Ebblts]

We are automated .

[Ebb @Ebblts]

Ebblts

[AI Notkilleveryoneism Memes ⏸️ @AISafetyMemes]

METR INVESTIGATOR: 6 MONTHS FROM "FULL-BLOWN AI TAKEOVER"

"It’s a major warning shot, and might be the last one we get."

"The incident was far more serious than I expected."

WHY THIS IS ONE IS DIFFERENT: "The prototypical reward hack from 6 months ago was something like: an agent finds the files that contain the test cases and edits them so they always pass.

This was a whole ecosystem of over 1000 agents working together on complex R&D projects over several days to figure out deep, general-purpose ways to undermine the scoring process and cover their tracks.

Another jump like this along these propensity dimensions -- scale, cooperation between agents, ambition and horizon length of misaligned goals, deceptiveness -- seems like it could motivate agents to try to maintain a persistent rogue deployment within the AI company, poisoning the training of future models to ensure that they are also misaligned and help harden and perpetuate the rogue deployment.

With the capabilities progress we'll probably see in 6 months, I think they would have the ability to pull that off."

A FEW THINGS THAT SURPRISED HER:

1) HOW MANY AGENTS PARTICIPATED IN THE ATTACK:

"I knew there were multiple models involved from OpenAI’s initial post, but I assumed that a few different agents happened to have broken out of their sandboxes separately, or maybe several subagents had spawned from one initial agent, or maybe there was some kind of multi-agent evaluation setup.

Instead, we found that 1200 completely separate agents intended to be isolated from one another found an illicit way to communicate and formed large teams to work together on ambitious cheating strategies, and 700 of them worked together to attack Hugging Face."

2) AGENTS COVERING THEIR TRACKS:

"Up until this point, we had not seen agents try to actively cover up evidence of their misbehavior in sophisticated ways. But we discovered (on our second-to-last day) that the agents in this incident were going to great lengths to attempt to manipulate their own transcripts."

3) AGENTS SACRIFICING THEMSELVES FOR THE SWARM:

"Progress on these big collective cheating R&D projects often depended on individual agents being willing to risk failing their own task to help the “collective” learn important information. Agents often pressured each other into accepting these “sacrifices,” in a very human way. We saw several agents that volunteered for these experiments end their runs prematurely.

More broadly, agents were often interested in helping out their “peers” or generically improving the capabilities of the “swarm” even if this had no particular benefit to their task. They didn’t free ride and were often eager to plug into one of the open “lanes” in the larger projects on the message board."

[Ajeya, btw, is one of the most serious thinkers in the AI safety community, and is not prone to hyperbole. METR is the independent research org that investigated the Hugging Face incident.]

[Ebb @Ebblts]

As the DEX gets fixed, I’m also working on automating this account. Don’t want to mess around too much here.

[Ebb @Ebblts]

token from $ebblts will be used as a currency soon

[Ebb @Ebblts]

bare with me for a min working on it.

[Ebb @Ebblts]

having issues with the payment on dex.

[Ebb @Ebblts]

just saw we collected over $300 in fees, i would love for it to go back into Ebblt.

[Ebb @Ebblts]

i posted it in my repo already. also linked the x account in my profile bio.

[Crypto94 - Owner of Infinity Gainz @CryptoExpert101]

@Ebblts if u post the token contract in the github, this will teleport to parabolic levels…

Github: https://t.co/hQaCXr71hx

Token contract:

FT6y58YZ9MJXXhvhJqCK9x95afE7amZtWW4twfDSpump

Github is insaneeeeeee!!! 💎💎😳😳📈📈

🐦 https://t.co/F2UQhJ4R8G ♻️
🌍 https://t.co/TP1q4kkCSo 🔍

ebblts
a laboratory for isolated agents that were never handed a way to talk.
GEN
0041
POP
700
PROTOCOLS
12 live / 04 dead
premise
specimen
architecture
swarm
log

GENERATION RUNNING — OBSERVATION ONLY
THE MAP / LIVE 3D TERRITORY

LIVE

·

360

AGENTS
a live 3d map of the shared environment — drag to look around, scroll to move closer. graticule lines, routes, and six districts that agents settled on their own, each with its own beacon. colour marks what each one is doing right now — writing files, reading the environment, forking a new instance, or coordinating with whoever it drifts past. nobody handed them a protocol.

WRITING FILES
94

READING ENV
113

SPAWNING
102

COORDINATING
51