In addition to the numbers franky1 posted, how many people are not paying because they don't have to? No evictions, no penalties, etc. So you stick the money into a savings account and then sit on it making some interest till you have to pay. And if something else bad does happen, then you have the money in the bank. Because you know the landlord isn't going to give it back.
-Dave
|
|
|
What I like is they were one of the first if not the first to have a 100% open hardware public design. Don't trust us, fine.
Here is the open source code. Here is the list of hardware used. Here are the schematics. Now stop complaining and do it yourself.
Also, a clear plastic calculator looking thing is more likely to be left alone by random people.
-Dave
|
|
|
Wow 2 updates in under a week after none for months. Guess it's 2021 and back to work. https://coldcardwallet.com/docs/upgrade <-- Don't trust my link verify. Major Address Explorer enhancements! Thanks go to @switck for this major feature bump. View sub-accounts as exported, just enter the account number. Multisig wallet support! (Caveat: addresses are for verification purposes and never for direct use as deposit, so they are partially redacted) Enter any custom derivation path, by entering numbers directly; for gurus. Warning screen can be suppressed after reading first time (press 6) Export of addresses now named "addresses.csv" not ".txt" Bugfix: Disable a few more path derivation checks for "Skip Checks" for multisig compatibility. Handles error shown when working with previously-imported Spectre multisig wallets (ie. multisig.py: 891). Bugfix: Generic wallet export (JSON) name for BIP49 wallets changed from "p2wpkh-p2sh" to "p2sh-p2wpkh".
Does not look like that big of an update but as always it's probably good to be running the latest firmware on anything financial related. Just my view, I could be wrong :-) -Dave
|
|
|
Not a Meme but if you live in NY the headline (probably written by someone from Brooklyn) is still funny: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F1nzUvOel.png&t=663&c=rt4qbLXjZ-W2sw)
|
|
|
And since more then likely as of Jan 21st when he is no longer president the lawsuits are going to start rolling in it's, better for them not to be holding any of his money. No frozen accounts, no dealing with having to distribute funds per government orders, etc. Yes records will have to be given to people, bank employees will have to testify, etc. But no other financial issues. Except perhaps fines. That's just good business. And they have the out of "we could not do this while he was still in office due to fear of reprisals"
-Dave
|
|
|
Send payment to the BTC in the 1st post and send me your address and I'll ship it later today / tomorrow.
-Dave
|
|
|
I love the wild theories about this, but couldn't it just be someone who set up (or is testing) some micro payment system?
That was my 1st thought, BUT I would think that. 1) It went on for longer then I have the screen shot for so that just seems excessive. That's a lot of testing. 2) They would be using their own nodes. 3) That is what testnet is for (yeah I know it's such a small amount who cares) So I dismissed it. Looing back through some logs it did happen once before so I'll just put it in the "meh, whatever" pile and move on. -Dave
|
|
|
Was cleaning up, forgot it was sitting around. No fan, and the usb plug is held on with some electrical tape. $10 shipped US. Not going to ship out of the US, not worth it. If you want I can grab a picture in the morning.
bc1qz9j3ts56fvnvl05tg30u36z5utts7huzyutrzy
-Dave
|
|
|
Just putting it out therre: could that be used to check if your node is online by sending a transaction every 30 mins worth 2 sats and getting a notification from it? That's my best guess atm...
Why would anyone care and it's not a regular interval: 12/JAN/2021 13:35 12/JAN/2021 13:04 12/JAN/2021 13:00 12/JAN/2021 13:00 12/JAN/2021 12:58 12/JAN/2021 12:57 12/JAN/2021 12:55 12/JAN/2021 12:53 12/JAN/2021 12:49 12/JAN/2021 12:46 12/JAN/2021 12:42 12/JAN/2021 12:41 12/JAN/2021 12:40 12/JAN/2021 12:40 12/JAN/2021 12:39 12/JAN/2021 12:38 12/JAN/2021 12:34 12/JAN/2021 12:34 12/JAN/2021 12:33 12/JAN/2021 12:29 12/JAN/2021 12:27 12/JAN/2021 12:26 12/JAN/2021 12:26 12/JAN/2021 12:21 12/JAN/2021 12:17 12/JAN/2021 12:16 12/JAN/2021 12:13 12/JAN/2021 12:10 12/JAN/2021 12:09 12/JAN/2021 12:02 12/JAN/2021 12:02 12/JAN/2021 11:51 12/JAN/2021 11:49 12/JAN/2021 11:47 12/JAN/2021 11:46 12/JAN/2021 11:45 12/JAN/2021 11:45 12/JAN/2021 11:44 12/JAN/2021 11:42 12/JAN/2021 10:49 12/JAN/2021 05:37 12/JAN/2021 05:20 12/JAN/2021 05:19 And unless it was someone at WalletOfSatoshi.com I don't think there would be anyway to force it to use my node. According to 1ML WalletOfSatoshi.com [6] has 128 channels open. Don't get me wrong I'll take the 1 sat per transaction all day long, but it makes you wonder what else is going on out there that nobody sees. -Dave
|
|
|
So was looking at my node just now and saw this: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FATeGOuEl.png&t=663&c=iWWpyO_d0giHxg) Just dozens of 2sat (3 with fee) transactions. Any idea why someone would be doing it? Just seems real odd. Never saw it before, so I don't know if its something odd or I just never noticed. -Dave
|
|
|
I don't think a new licence can apply to old versions of the code... you can't (or at least, you shouldn't be able to) retroactively change the rules like that. Imagine if you have a repo that people had been forking for years and then just suddenly decided "you must pay $1000 to use this code".
Anything created after the date of the licence change should be covered by the new licence... but anything that was done prior to that, should be covered by the old licence.
I agree 100%, and that seems to be the take of a lot of people. But, there are a few lawyers out there, one of which I spoke to who think differently (old friend nothing to do with this at all). The general take is that if you don't have a commercial product out yet then yes they can change the license terms. If you were selling and delivering a product then it's a line in the sand, anything after this you can't use. No idea how accurate that is, but they do work for a major firm who deals with this stuff. -Dave
|
|
|
--snip-- They went to the CC Commons Clause license to screw with these people: https://bitcointalk.org/index.php?topic=5265233.0 and were public about it. I have no problem with them changing how they do / license stuff but it should be for all work after "X" date. If I am doing something using your code that was GPLd and then you come back and change what I can do after, it's just a dick move. Now, what the Passport people did was not cool either so there is that, I just think they could have handled it a tiny bit better. -Dave I'm a bit confused, does that mean they change every single git commit (which means commit hash changed) to make every single commit contain current license (GPL, MIT & CC rather than only GPL)? Depends on the lawyers ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) But, from what was explained to me from what I posted in the other thread (and this could be 100% wrong) If you have a git repository etfbitcoin/etfbitcoins-amazing-project and you change it from one license to another then the latest version stands across the entire project. So even if you don't change it everywhere if someplace you posted the new license it stands. IF even in the same account you have etfbitcoin/etfbitcoins-amazing-project2 then you can fork it off and keep the old code under the old license and everything you do from there going forwards in the ...2 git is under the new. It's also as far as she knew never been tested in court and also since they are a Canadian company and she is a US based it might be interpreted differently. You know know as much as I do. -Dave
|
|
|
Depends on price.
Not to put too fine a point on it but you can get very high priced FPGAs to do 2TH @ 80W add in a bit for fan & such and you are still well under 100W. 145W although still nothing in the real world of power is still a big % over what is out there. I own several of just about everything you made, but unless this is really low cost I would have to pass.
-Dave
|
|
|
Paper Wallet features temporarily removed to free space; will return in future version. License changed from GPL to MIT+CC on files for which the GPL doesn't apply. Going to CC is BS for something like this. But whatever. Let's see if there is any backlash. Killing the paper wallet is a bummer, I actually used it a lot.
Removing paper wallet feature doesn't make sense, but what's wrong by using multiple license when AFAIK both MIT and CC are less restrictive than GPL? They said they needed space, I am guessing something they were doing (QR code generation?) was using a large library for something. They went to the CC Commons Clause license to screw with these people: https://bitcointalk.org/index.php?topic=5265233.0 and were public about it. I have no problem with them changing how they do / license stuff but it should be for all work after "X" date. If I am doing something using your code that was GPLd and then you come back and change what I can do after, it's just a dick move. Now, what the Passport people did was not cool either so there is that, I just think they could have handled it a tiny bit better. -Dave
|
|
|
As far as I know localbitcoins.com is still working.
Thought this was not an option for most US people? Unless you wanna run into trouble. Didn't say it was a great option, just that is was an option. ;-) So long as you trade with people who have high feedback it's mostly safe. Kind of like eBay. Don't buy the new PS5 from the guy with 1 feedback who joined yesterday. Same thing with your bank, if they block certain types of transactions, don't back there or don't use them for those transactions. Bit of a "1st world problem" statement but: I am 'forced' to have 3 checking accounts. One is my main day to day, paychecks go in, bills get paid from account but....they absolutely positively will not allow an automatic withdraw to pay a bill that is not 100% in my name AND although they do have high interest checking their ATM network sucks. So I opened a 2nd one, just to have better ATM access and a bit of easier time paying some bills now and then. Fine whatever not a big deal. Till, they merged with another bank that is crypto unfriendly, and publicly so. Just to be safe I opened a 3rd account for crypto things (and eBay / PayPal stuff) so neither my main account or other will ever be shut down / blocked / whatever if they don't like something they see. Which a lot of banks are know to do. -Dave
|
|
|
Going to sleep. Will check in to see if anyone bought spots when I wake up.
EDIT: Well it's noon on Monday and no takers. Will lock for now.
-Dave
|
|
|
Quoting myself from the LoyceV thread that you have posted above. And adding this: NEVER EVER WORK ON THE ORIGINAL FILE. ONLY EVER WORK ON A COPY OF IT.I have helped people recover some wallets over the years and it's been made more difficult because we did not have an untouched file to work with. When recovering the wallet.dat or the default_wallet OR ANY OTHER ACTUAL FILE. MAKE A BACKUP ON REMOVABLE MEDIA BEFORE DOING ANYTHING. Hell make several, just in case. Let me bold that a bit more: MAKE A BACKUP ON REMOVABLE MEDIA BEFORE DOING ANYTHING. Don't put it in your Dropbox / google drive / Microsoft one drive. Just keep it local on media you control. This way if you damage the file for whatever reason, no big deal.
And when you are done, you can destroy the media and know 100% it's gone.
Make backups on a USB stick / SD card / whatever just don't play with the original file. -Dave
|
|
|
So after 5 months we get an update. https://coldcardwallet.com/docs/upgrade <-- Don't trust my link verify. Version 3.2.1 - Jan 8, 2021 Major Multisig improvements! If you are using multisig features, please backup your Coldcard before upgrade, just in case (but shouldn't be a problem). Tracks derivation path for each co-signer and no longer assumes they all use a shared derivation path. Blocks multiple instances of same XFP in the wallet (not supported anymore, bad idea). Various displays updated to reflect derivation path change. Text file import: "Derivation:" line can be repeated, applies to all following xpubs. Show Ypub/Zpub formated values from SLIP-132 when viewing details of wallet. Standardize on "p2sh-p2wsh" nomenclature, rather than "p2wsh-p2sh", thanks to @humanumbrella. For airgaped multisig wallet creation, you must use same firmware verison on all Coldcards or this change can make trouble. Address type (p2sh-p2wsh, p2sh, p2wsh) is captured from MS wallets created by PSBT file import. Can now store multiple wallets involving same set of XFP values, if they have differing subkey paths and/or address formats. New mode which disables certain multisig checks to assist bug compatibility. Enhancement: Add support for signing Payjoin PSBT files based on BIP-78. Enhancement: Promoted the address explorer to the main menu. It's useful! (credit to @matt_odell) Bugfix: zero-length BIP39 passphrase, when saved, would cause a crash when restore attempted. We recommend longer passphrases, but fixed the issue. Enhancement: Move the "blockchain" setting deeper into the "Danger Zone" and add warning screen. This mitigates a concern raised by @benma (Marko Bencun) where an attacker could socially-engineer you to sign a transaction on Testnet, which corresponds to real UTXO being stolen. Only developers should be using Testnet. Bugfix: Display of amounts could be incorrect by a few sats in final digits. Bugfix: Incorrect digest method picked when P2SH-P2WSH incorrectly identified as plain P2SH. Bugfix: Better error reporting when importing bogus multisig wallet files. Enhancement: Files created on MicroSD will have date and time determined by the version of firmware that made them. Downstream systems might use this to know when the Coldcard should be upgraded, or which firmware version created the data. Idea from @sancoder Enhancement: Show version of secure element, under Advanced > Upgrade > Show Version. Enhancement: Improve 'None of the keys involved...' message to show XFP value actually found inside PSBT file. Enhancement: "Invalid PSBT" errors are shown with more information now. Paper Wallet features temporarily removed to free space; will return in future version. License changed from GPL to MIT+CC on files for which the GPL doesn't apply. Not real happy about these 2: Paper Wallet features temporarily removed to free space; will return in future version. License changed from GPL to MIT+CC on files for which the GPL doesn't apply.Going to CC is BS for something like this. But whatever. Let's see if there is any backlash. Killing the paper wallet is a bummer, I actually used it a lot.Bugfix: Display of amounts could be incorrect by a few sats in final digits.I really though it was me just not paying attention when an amount looked wrong. Heh, should have mentioned it.
-Dave
|
|
|
|