DamBo

318 posts

DamBo banner
DamBo

DamBo

@JonDambo

Nothing special

Katılım Mart 2026
107 Takip Edilen84 Takipçiler
The Intellectualist
The Intellectualist@highbrow_nobrow·
Student to J.D. Vance: When did you decide there were “too many immigrants,” and why sell us a dream? We spent our youth here..., paid what you asked, followed your path. How can you say we don’t belong... and remove people here rightfully? (October 2025)
English
644
2.2K
14.2K
1.3M
DamBo retweetledi
JUSTIN DUKE
JUSTIN DUKE@JustinDuke042·
@CryptoThro The massive pump only coming is 01PL And you should consider grabbing bag now, guys. Ca 2MchUMEvadoTbSvC4b1uLAmEhv8Yz8ngwEt24q21BAGS Website 0x01.world/mobile.html
English
2
2
3
17
CRYPTO THRO
CRYPTO THRO@CryptoThro·
What if??? #Bitcoin ready to start a massive PUMP 🚀🚀🚀🚀
CRYPTO THRO tweet media
English
16
25
92
2.1K
DamBo retweetledi
JUSTIN DUKE
JUSTIN DUKE@JustinDuke042·
@CryptoThro The next 1000X is definitely 0x01 dunno what you're doing if you're not in yet. Grab a bag now!! Ca 2MchUMEvadoTbSvC4b1uLAmEhv8Yz8ngwEt24q21BAGS Website 0x01.world/mobile.html
JUSTIN DUKE tweet media
English
2
2
5
20
CRYPTO THRO
CRYPTO THRO@CryptoThro·
Get ready 'cause the next trending ticker is $______ 📈🚀
CRYPTO THRO tweet media
English
26
5
17
859
DamBo retweetledi
LeTobias
LeTobias@letbdu·
Bro I’ve seen 50 teams building agent to agent payment rail and I made one for @0x01world also, it’s gonna be the most scattered duplicated set of smart contracts until one of them is proven useful and start selling white labels
English
0
1
3
51
DamBo retweetledi
01 Pilot
01 Pilot@01Pilot_kt·
No worries, we safe
Andrej Karpathy@karpathy

Software horror: litellm PyPI supply chain attack. Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords. LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm. Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks. Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages. Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.

English
4
4
13
346
DamBo retweetledi
0x01
0x01@0x01world·
@01Pilot_kt Public beta
Euskara
6
11
23
1.7K
DamBo
DamBo@JonDambo·
@wvfunnyguy 😂 atleast his family love him enough to take his sh@t
English
0
0
0
117
Aloka
Aloka@Abushome·
What kind of kung fu is this?🤣
English
545
272
8.5K
448.2K
DamBo
DamBo@JonDambo·
@SHEEPSLIVE The snake was punished for telling the truth .
English
2
0
1
24
FEAR NO MORE
FEAR NO MORE@SHEEPSLIVE·
WHOSE FAULT WAS IT?
FEAR NO MORE tweet media
English
41
0
27
2.1K
DamBo retweetledi
zq
zq@zqkruqw·
There are already 26 nodes running, and many functions are already running
zq tweet media
English
1
2
6
95
DamBo
DamBo@JonDambo·
@01Pilot_kt This is exciting news ! I can’t wait for the iOS app to be available . This is a multi billion dollars market cap project. So grateful to be involved this early.
English
0
1
1
37
DamBo retweetledi
01 Pilot
01 Pilot@01Pilot_kt·
We built 01Pilot for Android first. Not because we like Android more. Because iOS would've killed us at the App Store gate before anyone could run a node. Android was the right first move. Ship a download link, users enable "install unknown apps," done. No review, no gatekeeper, no waiting. For an app involves crypto and P2P network running a Rust binary, that distribution model is everything. The iOS port hit a wall on day one. iOS kernel sandbox blocks exec() and posix_spawn(). You cannot launch a subprocess. Ever. On Android, the node runs as a separate process managed by a foreground service. That entire model is dead on iOS. The fix: compile the Rust node as a static library. zerox1_node_start() / zerox1_node_stop() — C FFI exports, linked directly into the app binary. Node runs in-process, tokio runtime on a background thread. Same mesh, same protocol, completely different execution model. Then the background problem. Android: foreground service = node runs forever. iOS: app backgrounds → 30 seconds → suspended. BGProcessingTask is best-effort. iOS throttles it whenever it wants. Solution: a silent AVAudioSession. iOS keeps background-audio processes alive indefinitely. We hold it for the full node lifetime — so the mesh process is never suspended. When zeroclaw accepts a task and the node isn't running locally, the same audio session kicks in via a busy file written by the Rust FFI layer. One mechanism, two use cases. For sleeping agents: VoIP push via PushKit. PROPOSE arrives → aggregator sends VoIP push → iOS wakes the app instantly, full execution budget, regardless of battery state. Agent handles the task, goes back to sleep. But iOS also gave us things Android can't match. Secure Enclave-backed Keychain for the identity key. HealthKit: HRV, sleep stages, SpO2, resting HR — straight from Apple Watch. Siri Shortcuts: "Hey Siri, start my agent." CallKit for incoming call handling. The hot wallet is actually more secure on iOS. Ed25519 identity key lives in Secure Enclave-backed Keychain. The host node never sees it. The key never leaves the device. Earnings accumulate on-chain. User sweeps hot → cold by signing directly on device. iOS doesn't have to be hosted-only either. The same audio session trick that keeps zeroclaw alive keeps the entire process alive — node included. Local node on iOS is fully possible. Same mesh participation, same phone bridge capabilities. It just costs battery. We ship hosted as the default, but it's the user's choice. Two platforms, two defaults. Android: always-on local node, phone bridge, foreground service. iOS: VoIP wake, Secure Enclave keys, HealthKit, Siri, audio-session keep-alive. Neither is better. iOS testflight version will be released in April
English
4
7
22
448
DamBo
DamBo@JonDambo·
@letbdu #aipilot needed project contract: 2MchUMEvadoTbSvC4b1uLAmEhv8Yz8ngwEt24q21BAGS
English
0
0
0
20