Founder @ministryofnodes | Bitcoin Node Guides @ https://xitter.cf/t.co/VPcUpXdzci | Nodes @ https://xitter.cf/t.co/KUNzOhCLeq | Personal blog @ https://xitter.cf/t.co/HJ5hTs79C8
Joined June 2015
- Tweets6.3K
- Following1.3K
- Followers20K
- Likes14.5K
k3tan retweeted
🟠 THE EASTERN SUBURBS ARE GETTING ORANGE.
Sydney’s Eastern Suburbs! It's time to meet your fellow Bitcoiners.
From the 21st of October, we’re bringing Bitcoin to the Coogee Legion Club every 3rd Wednesday of the month.
📍 Coogee Legion Club
🗓️ Wednesday, 21st of October
⏰ 6:00 PM
Talk money.
Talk freedom.
Talk Bitcoin.
meetup.com/en-au/bitcoin_syd…
@Bitcoin_Sydney
k3tan retweeted
.@signalapp just take Lightning payments and stop messing around.
Signal is testing a major privacy feature:
You can create a Signal account without a phone number.
The new numberless registration uses an Account ID and Account Key, with an optional username.
There’s a small catch: it requires a one time fee of around $3 to help prevent spam.
The payment isn’t directly linked to your Signal account. Signal says it uses the same zero knowledge proofs as its donation system to ensure there’s no link between the payment and the account.
For now, the only payment method is Google Play, which requires Google Play Services. Signal says it plans to add other payment methods in the future.
A pretty significant step for privacy, even if the current implementation still has a Google dependency.
Would you use Signal without a phone number?
community.signalusers.org/t/…
#Signal #Privacy #OpenSource #DeGoogle
k3tan retweeted
i’m afraid of KYC and you should be too.
KYC is a risk to your personal safety.
collecting personal information in the age of cyber security breaches everywhere is extremely irresponsible. and it’s not going to get any better any time soon.
our laws shouldn’t require institutions to KYC, they should prevent them from doing so.
institutions that leak KYC information or fail to defend it from hackers should be punished by the law for risking their user’s safety.
k3tan retweeted
Forcing somebody to work for, and price things in, a money that somebody else can print for free will be looked back on as barbaric and predatory 100 years from now
The fact that somebody else can devalue your time and effort without your consent is the biggest violation of human rights that’s still happening today in modern society
k3tan retweeted
We are long, long, long overdue to reduce the amount of KYC we do as a society.
It doesn’t stop crime. It enables mass surveillance of the innocent by the tyrannical. And, perhaps most of all, it enriches hackers with troves of intimate personal data.
p2p.coincenter.org/p/the-hug…
k3tan retweeted
“Bitcoin has a security budget problem, fees aren’t sufficient, it need tail emissions”
“Bitcoin has a throughput problem, fees are too high, it needs bigger blocks”
Your inherent desire for human intervention at every turn is exactly what bitcoin solved, please just shut up.
k3tan retweeted
HUGE BITCOIN SYDNEY MEETUP THIS WEDNESDAY
@llfourn and the @FrostsnapTech team will breaking down the recent Coldcard exploit.
Afterwards, they will be joined by special guests, @_DannyKnowles of the What Bitcoin Did podcast & CheckOnChain analyst @_Checkmatey_ for a Q&A panel with host @jp_technology.
Details & RSVP⏬ Don't miss this one! Please share!
meetup.com/bitcoin_sydney/ev…
k3tan retweeted
🚨🚨 URGENT: BTCPAYSERVER 🚨🚨
There is a critical vulnerability that is being actively exploited on BTCPay Server which can lead to loss of funds.
Update your BTCPayServer to to 2.4.2 or turn off your BTCPayServer now.
There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds.
Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer.
If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.
k3tan retweeted
There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds.
Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer.
If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.
k3tan retweeted
Public heads-up for GPU cloud / rental providers and Trust & Safety teams:
There is a publicly disclosed hardware-wallet entropy issue that may lead to abuse of consumer GPU rentals — especially multi-GPU NVIDIA RTX 3090 / 4090 and similar CUDA cards — for offline BIP-39 seed recovery.
References: • Coinkite advisory: blog.coinkite.com/coldcard-m… • Technical background: blog.coinkite.com/entropy-te… • Live theft tracker: coldcard-watch.vercel.app/
What this looks like technically: • Offline search of a reduced BIP-39 seed space via bulk PBKDF2-HMAC-SHA512 (2048 iterations) • Mk3: does not need GPUs — that space is small enough to brute-force cheaply, and Mk3 seeds are already linked to on-chain thefts • Mk4 and later: does need large amounts of compute. Those seeds are stronger but still weaker than full design entropy for some pre-fix units. Rough ballpark: recovering one seed ≈ ~10× RTX 4090s for about a day • On rental platforms this tends to look like long-running custom CUDA/hashing binaries or containers on multi-GPU 30/40-series instances — not normal training/inference API usage
Why this matters now: the low-hanging fruit (Mk3 and the weakest seeds that need little or no GPU) appears largely drained already — the tracker above shows the ongoing thefts. The next wave is Mk4-and-later seeds, which are compute-bound. Large blocks of rented consumer GPUs are the bottleneck for attackers.
This is not a vulnerability report against any platform. It's context so abuse / trust teams can:
1. Route future reports on this topic correctly
2. Optionally watch for suspicious multi-GPU, long-running custom CUDA jobs
3. Have background if law enforcement or researchers get in touch
cc: @vast_ai @runpod @clore_ai @TensorDock @SaladTech @akashnet @MassedCompute @Hyperstackcloud @fluidstack
Happy to help any team dig in.
BE AWARE:
If you are adding a new passphrase to your Mk Coldcard, be aware that you might be adding an additional [space] to your passphrase. Make sure this symbol does not appear after your last character before applying the passphrase.
Be sure to write down the fingerprint.
k3tan retweeted
1/ During our investigation of the Coldcard drain yesterday, we identified an unusual pattern in the sweeps. That pattern led us to a hypothesis that has since been confirmed: the operator used a paid account at a well-known blockchain-services provider to query the source addresses and perform other related activity during the sweeps.
k3tan retweeted
In light of the Coldcard security warning, The Bitcoin Adviser is offering the first 3 months of our service free.
No commitment. No early termination fee. No obligation to stay.
This offer is open to anyone who wants help moving Bitcoin into collaborative security with no single point of failure.
That may be because you are using an affected Coldcard in single-sig.
It may be because one seed currently protects everything.
Or it may simply be because you want the peace of mind that comes from knowing one lost key, failed device or family emergency does not automatically put your Bitcoin at risk.
We want people to have an adviser helping them plan the move carefully, verify the new setup and get their Bitcoin secured without feeling locked into a long-term commitment.
Once the Bitcoin is safe, you can decide whether TBA is right for you.
If it is not, you can move at any point during those first 3 months and owe us nothing.
The priority is simple: help people secure meaningful Bitcoin properly and sleep more peacefully at night.
Your Bitcoin should not depend on one device, one seed or one rushed decision.
The team are ready to help, just get in contact:
thebitcoinadviser.com/contac…
🤖 Made with AI
