jungly (@jungly) header
jungly (@jungly) profile picture

Building P2Poolv2. PhD distributed systems. https://teapaw.org/t.co/pqcolZ5m2f

Joined April 2008
The definition of what is illegal content onchain can be changed at any time. Stay permissionless.
8
23
4
99
11,622
Bitcoin++ Insider News Hour TODAY, at 1pm EST @jungly joins the show to cover all the new developments around P2Pool v2 and testnet5 ⛏️ Tune in live here on the X stream, or Youtube!
5
2
8
1,595
"If your wages only allow you to eat and sleep, it's not a job; in the past, that was called slavery." - George Orwell
191
9,160
187
44,309
408,413
Scumbags. This is a large reason why we pay our international employees in Bitcoin.
I'm an Ethiopian founder who won $10,000 AWS Global Innovation Award. Today, @Wise closed my personal account with $9,000 of my money in it. am now unable to pay next month's rent because I can't access my own money. @Wise, I'm asking you to return my $9,000.
27
120
1
1,442
173,687
Just finished up two Hydrapool versions; the @IxTechCrypto Mujina build-inspired theme, and the @256FOUNDATION standard theme. Which one do you prefer? Hydrapool is an open source pool that can be used as a solo Bitcoin mining pool, or to quickly spin up a PPLNS pool for your friends, charitable event, or organization. I packaged this for Umbrel, and will share a community store link after the last round of testing is complete. Learn about Hydrapool here: hydrapool.org
2
2
5
433
jungly retweeted
welcome to @p2poolv2, tb1q2rm5jr...teytvm
4
12
372
jungly retweeted
bitaxeBonanza, the first non-bitmain @osmu_global bitaxe @johnny9dev and I have been working on supported by @OpenSats with the Intel BZM2 ASICs donated to @256FOUNDATION by @protomining is mining on p2poolv2 by @jungly via p2pool-lab by @avg_gary The open source Bitcoin mining stoke is high AF today folks.
6
13
2
62
2,640
Replying to @avg_gary
Mining? P2PoolV2? rbitcoin? yesplz.
4
9
421
jungly retweeted
Not everything associated with Bitcoin or bitcoin mining needs to be open source. But things that are open source will be significantly more performant, secure and freedom preserving.
10
3
46
2,081
jungly retweeted
The software engineering game has changed.
6
14
133
10,120
P2POOL V2 AIMS TO DECENTRALIZE BITCOIN MINING A new open-source mining protocol is being developed to eliminate centralized pool operators’ control over transaction selection, share accounting, and payouts. Unlike Stratum V2 and DATUM, which decentralize block template construction but still rely on pool-operated accounting, P2Poolv2 allows every node to independently verify miners’ work and payouts. The system introduces: Permissionless mining without pool operators censoring transactions or withholding credit for valid work. Decentralized share accounting verified by every node. Self-custodial Bitcoin payouts directly to miners. Tradable mining shares, with planned atomic swaps over Lightning and Ark to help smaller miners receive payments. Improved support for smaller miners through variable difficulty and reduced orphaned-share losses. The protocol is currently running on Bitcoin testnets, with share trading and mainnet readiness still under development. p2poolv2.org/
10
17
2
64
11,562
While everyone was busy selling their Bitcoin to invest in the Anthropic IPO, Bitcoin showed huge momentum towards mining security and decentralization: (a) Foundry announced testing of Sv2 (b) MARA mined their first block using Sv2 (c) Luxor announced they now supported Sv2 (d) P2PoolV2 beta is working well as a substantial portion of Testnet5 hashpower While only the last one is an immediate mining decentralization win, supporting Sv2 in pool-work mode is an important first step towards miner Job Declaration and shows commitment by the mining industry to finally move forward, not to mention is a huge security upgrade for the entire Bitcoin system.
39
128
17
828
46,619
Wait we have an explorer now??
rbitcoin.space v0.2.0 is out. - Ark explorer for @secondhq and @arkade_os - Silent payments support (thanks @w3irdrobot ) - If you don't like my frontend, then swap it with @mempool frontend and rbitcoin space backend will work for most things. (Some fancy things like mempool goggles and the shiny lightning graph don't work yet) - Way more stuff for lightning node operators that you usually have to go to amboss for. - still very fast and uses @rbitcoin_org and LDK.
2
7
41
1,687
Coinbase looking better. Six nodes now. @p2poolv2 #testnet5
3
25
633
jungly retweeted
Luxor Commander this week, Hiveon last week. If you're using proprietary miner management software, you'll probably want to stop.
🚨 64,000 BITCOIN MINERS HIJACKED IN MASSIVE ATTACK An estimated 64,000 Bitcoin miners representing 13 EH/s of hashrate were reportedly hijacked overnight, with their mining power redirected to OCEAN mining pool and payouts assigned to an attacker-controlled Bitcoin address. The attack reportedly began around 8 PM CT on November 14. OCEAN’s dashboard shows a sharp spike in hashrate, briefly approaching 50 EH/s before falling back toward 40 EH/s. CoreX Hosting first raised the alarm, reporting that miners were being redirected without authorization. One affected operator says their entire mining farm was hijacked and identified Luxor’s Commander mining management software as the source of the compromise. Other operators reported similar unauthorized pool changes several days earlier, potentially pointing to a broader incident. CoreX later reported that the attack appeared to be over, with the hijacked hashrate falling from 13 EH/s to approximately 100 PH/s. The attackers reportedly failed to mine a Bitcoin block during the hijack, meaning no block rewards were collected. However, affected miners permanently lost the opportunity to earn Bitcoin during the attack. That hashing time cannot be recovered. The full scope of the breach and whether Luxor Commander was compromised have yet to be independently confirmed.
1
5
1
22
1,307
jungly retweeted
Security has finally been promoted to a first class citizen in the world of software engineering and internet infrastructure, because it's no longer feasible to sweep problems under the rug and gamble that they won't be found. teapaw.org/hash_bender/status/212…
This is probably as good a time as any to talk about what it's been like in the trenches the last 4-6 weeks. It's a topic i've been wanting to post about but wasn't sure how to approach it, so here it goes: At this moment, anyone running any sort of substantial business, especially in crypto, is inundated with AI-enabled attacks. Abliterated models are running 24/7 against your entire surface, looking for a little crack, which they then use to (almost instantly) expand. This does not seem to be slowing down; rather, it's speeding up as models get better and more attackers enter the arena. @luxor we have taken a very proactive approach. We acquired our own baremetal GPUs to run our own abliterated models and have made huge strides in our security posture. I urge anyone running a similar service to do the same. It's your only defense in this new AI-powered dark forest. "The only thing that stops a bad guy with a gun is a good guy with a gun." We have put the majority of our new feature work on hold (which really sucks because we have some awesome new features that I am incredibly excited about) to harden every aspect of our infrastructure; rotating keys, updating kernels, pinning dependencies and responding to the daily feed of CVEs being disclosed. It is a necessary step that I'm sure most companies are already doing behind the scenes. Again, i can't thank everyone enough for their support during this time. The @luxor engineers working round the clock and customers continuing to place their trust with us as we navigate this new world. I'm optimistic about where the world is headed, but there will be a few bumps along the road.
13
14
1
157
15,418
jungly retweeted
WTF: Luxor is remotely monitoring customers mining operations and can change settings at will?
Last night our internal monitoring alerted us to an unauthorized redirect of hashrate through Commander. Our on-call engineering team jumped on it right away. Impact: just over a dozen client accounts. Affected machines were pointed to a different pool for a limited window. No data was leaked or exfiltrated from our systems. What we did: within 2 hours Commander was patched and we started restoring affected machines to their original pool settings. Compensation: every affected client will be paid in full for the redirected hashrate, as if it had mined normally. Commander is operating normally and no action is needed from users. We're working with the teams involved and will share a full post-mortem.
10
9
3
71
4,952
jungly retweeted
my first P2Poolv2 reward on #testnet5 (#BIP95) 🤩 h/t @jungly @johnnyasantos @stevenroose3 & many others o7
3
3
26
575