pull down to refresh
Conflicts with what Rob Hamilton claims, that he found the bug quickly with Kimi K3. Who ya gonna believe, Coinkite or Rob Hamilton?
You know what I thought this morning, if governments want to attack Bitcoin they don't have to bother. Leave it to us to self destruct by ourselves, we're showing we can do a pretty good job.
And we'll achieve our long stated goal of reducing goverment deficits, cos they won't have to spend any taxpayers money on it.
Other note, very good article here on the technical side of this. There's no other way to say this, it's negligence (polite word for piss poor technical design, execution and testing) by Coinkite.
I use CC and have recommended them to friends and family, not any more. In the process of moving all my funds somewhere else now.
https://wizardsardine.com/blog/coldcard-rng-vulnerability/
"and did not generate the seed using dice rolls only"
what is the exposure if you generated the seed on the device and then added entropy with 100 dice rolls?
maybe so, but jeez. do you stay with any coldcard after this, if it's true that it's a device vulnerability. or is any RNG at risk? i remember how "safe" i felt after learning how big a 256 bit number was, hope that's still the case.
Driver? I would've used a 3 wood for that.
Looked like a sharp dogleg which he ended up overshooting into it so better to keep it short.
A few years ago we had the same number of merchants here in CHCH as they did in Queenstown, but now they're way ahead.
I know that place on Lichfield St and go there when I'm in town.
This guy also accepts Bitcoin, I get my hair cut here:
https://btcmap.org/merchant/21584
Thanks for the guides, I will work on connecting my node to SNs and also my Primal wallet. Will probably use Alby Hub as I want to keep it all on my own stack.
We have a meetup on the first Wed of the month at Bar Yoku, and usually most Wednesdays some of us are there. Bitkiwi is in town on 7 March too.
Be great to see you there, come say hello. I'll be the one wearing the Sparrow cap.
It's great down there, the people and the merchants are going for it.
More than just bars and restaurants too, activities, haircuts, even a lawyer if you cross the thin blue line!
I think that would be more fun and help bitcoin more than arguing with people on the other side of the world.
there's a meetup in your town too, i think: https://kiwibitcoinguide.org/#events
Come along and say hi.
i used to have my alby wallet connected but when SN moved to the cowboy credits i lost that, just tried to pair my node using LNC but got some errors in that so I'll work on that and reconnect.
If i run an LND node, what's the best way to connect my SN wallet?
Well, here's somewhere outside of the internet where you can use LN on a daily basis.
And if I'm not mistaken, it's just down the road from you @Solomonsatoshi
I was in Queenstown this week using LN at merchants, routing all the payments through my own node. Have you been there and tried?
I'd be interested to hear what you think of an initiative like this.
https://bitcoinbasin.nz/
If you're interested in privacy, you could consider running your own node instead of connecting through Trezor Suite. When I started running my own node I switched to Sparrow and Coldcard to complete the set. Haven't looked back since and am very comfortable with that setup for cold storage.
If you're running Linux, then I guess you are interested in privacy and sovereign computing to some degree, and running a node on your own server would be a good fit for this.
Thanks for sharing.
Is there a stream from the Open Source Stage?
I'm a little over Stablecoins and "Crypto" speeches on the main stage.
What is the source of this line please:
"Audience are too dumb to understand this”. But most of us can appreciate: only 7 OP_RETURN larger than 83 byte this year, and the rest millions are <= 83 bytes. "
Hi Murch.
Your answers here have really helped me understand more about OP_RETURNs in general, and this issue, so thanks.
Here are my questions.
Given the 3 ways data can be embedded in the blockchain, how effective against each of these methods are the actions proposed in the PR?
My understandings are:
- Writing data to a taproot leaf script. Lifting the OP_RETURN limit will not provide an attractive alternative for people embedding data, for any data above 143 bytes. So not effective against most arbitrary data.
- Data in the output script using the OP_RETURN op code. Lifting the limit seeks to encourage more data to be embedded using OP_RETURNs, as the current limit may prevent some data from being propagated around the network as it becomes non standard. (But can be worked around by going to a miner out of band)
- Embedding data using fake public keys or hashes. Does raising the OP_RETURN limit offer an incentive for this kind of embedded data? Does it become cheaper using OP_RETURN or not?
I'm trying to focus on the logic and incentives of the proposal, not the emotion and blah blah.
And one final question, why is this company Citrea being cited so much in this PR and discussion? I see Core Devs linking to their Whitepaper in the PR and I wonder why a single company's use case and requirements are being considered to heavily in this discussion. Shouldn't that be a non factor for a Bitcoin Core PR?
Anyway, thanks for helping out with these questions.
With all due respect, I don't think you've answered the question.
Your make valid points for the justification of the increase in the limit and explain that individual nodes may be harming themselves, default settings are the norm and the transactions will be propagated anyway. You've even pointed out that the ability to configure this setting was debated anyway and some consider that it shouldn't have been added.
But the question asks something different, something I am wondering also. As a sovereign node runner in an open permissionless network, why does this PR propose to remove the ability for me to configure the mempool settings on my own node?
If I make a decision that harms myself and doesn't make any difference to the propagation of transactions, isn't that for me to decide and bear the consequences of?
It's like re-using addresses, commonly accepted as poor for privacy but there is no rule in the protocol that permits it. It's up to me to understand and accept the consequences.
The government has changed since Covid, technically towards the right but not much has changed. Just different people squealing about different things.
New Zealand's biggest problem is apathy and lack of leadership, and I don't mean this from a political point of view, society in general. Life was generally OK here for most people for a long time, now it's not.
There's a line that Peter Jackson is credited with many years ago, "Kiwis often show up a day late and a dollar short", when he was asked about how NZ engages on the world stage, and I think that still applies to this day.
Most of us live here because we were born here and our families are here, the landscape here is great and so are the people.
New Zealand runs the fiat property ponzi as well as anyone, regardless of which party is in power.
There are some interesting initiatives and companies in the Bitcoin space here, let's call it small but active. Here's a summary from last year:
https://kiwibitcoinguide.org/articles-and-guides/bitcoin-in-new-zealand-in-2024-the-year-in-review/
One mitigation I have adopted for this is to only trade with sellers who are online. Not 100% fool proof but I started doing this a while ago and it seems to have helped.
I had a similar instance of this (not with a gift card though) last year on Robosats and it made me aware that you can potentially be scammed by a seller. In my instance I had sent the fiat but the seller claimed I hadn't so we opened a dispute.
The coordinator adjudicated and ruled in my favour, as I had clear evidence of the fiat being sent and I got my sats.
But it made me realize that if the coordinator and seller collaborate they could scam you, so we're really relying on the coordinator.
Although you can't recognize a seller by their bot identity, you can identify them by their Wise or Revolut tag if you're using those payment methods.
After this incident I was in another trade with the same coordinator and when I got to the send Fiat stage the Revolut tag was the same as the seller who tried to scam me previously so I cancelled the trade and forfeited my bond.
Robosats is still me preferred P2P method (especially now as no one in my community wants to sell sats P2P right now for some reason!) but since this happened I limit the size of my buys and be mindful of who I am trading with (coordinators and sellers).
It's a jungle out there :)
They may have been crap at generating entropy, but I'll bet they'll be world leaders in creating bullshit to (try) and cover their arses. The more I read about this the more I think there's no way they couldn't have known about this.