Fully Noded®️ retweeted
I love how @FullyNoded now analyzes transactions and gives a little privacy overview/rating before you broadcast it.
Fully Noded®️ retweeted
Replying to @FullyNoded
Silent Payments support is exciting. Any known edge cases to watch out for during testing?
Fully Noded®️ retweeted
Replying to @FullyNoded
@FullyNoded v3.0.0 was just uploaded for public TestFlight!
Its huge! Block Explorer, Payjoin via integrated onion endpoints, Nostr Connect, Silent Payments, Privacy Checkups, Transaction Analysis, massive UI/UX upgrade, local psbt signing, many security and privacy improvements!
Given the size of these changes it would be wise to test first!
See the new and improved docs which represent v3.0.0: github.com/Fonta1n3/FullyNod…
Fully Noded®️ retweeted
Now accepting Silent Payment donations powered by @FullyNoded
Thank you for your support!
sp1qqg4qv8t3xytwye4ymhmfeujw7khc3nw9wpr5k95fjpgdlumr988mjqcuus93gqqwcg27purhq2wt4htemuu2tzplhzrp6nyc2t2nrdsmfyneult4
Fully Noded®️ retweeted
Replying to @FullyNoded
@FullyNoded v2.4.0 pull request for initial Silent Payments and major UI update is a huge update with 14,156 lines of code added and 31,883 lines removed.
Love adding functionality whilst simultaneously reducing the amount of code.
Fully Noded®️ retweeted
Finally, the website for @FullyNoded has been updated!
fullynoded.app
Fully Noded®️ retweeted
Replying to @FullyNoded
@FullyNoded now automatically detects Silent Payment inputs when you tap sign in the transaction verifier view and will sign said Silent Payment inputs if you have the signer for it.
Follow along at the Silent Payments branch of FN!
github.com/Fonta1n3/FullyNod…
Fully Noded®️ retweeted
Replying to @FullyNoded
@FullyNoded Server now scans each block and parses every transaction to see if it matches your silent payment address, if it does it imports it into a specified wallet as a raw taproot output descriptor.
Fully Noded®️ retweeted
PSA, @FullyNoded v2.3.2 went live yesterday. I noticed a couple bugs, fixed them and have submitted 2.3.3, May as well wait for 2.3.3 before testing.
Fully Noded®️ retweeted
⚠️If using mini-script descriptors in Bitcoin Core you should wait to upgrade to v31.1 as it can result in a corrupted wallet file error. Downgrading fixes it.
Fully Noded®️ retweeted
Replying to @Fonta1n3 @FullyNoded
Thanks for the good work sir i use your products and love them!
Fully Noded®️ retweeted
This is the PR I am actively working on: github.com/Fonta1n3/FullyNod…
Please feel free to test, review and attack with your AI. Still a WIP.
Fully Noded®️ retweeted
Updated Keychain storage to the strictest settings possible without requiring biometrics.
@FullyNoded creates a crypto secure random private key and stores it on the keychain for encrypting and decrypting mnemonics and node creds.
It also stores app unlock password there as well as a timeout value incase you input the incorrect password. This timeout doubles every attempt.
Previously two separate functions were called to create seed words, now it all boils down to one function to make it ultra simple to review.
More paranoid defensive coding around deriving a dummy key for use in multisig taproot keypath (till I replace with NUMS).
Bug fixes which may have caused a crash when adding a new node and closing reopening the app.
Refactored and improved the node detail view, am testing everything on iphone SE moving forward so no stupid UI bugs from small devices.
Added nodeless support for timelock descriptors.
Started adding ability to timelock single sig native segwit addresses, segwit multisig next.
Lots of testing!
Tidying up a few loose ends, more testing and I will be shipping this awesome upgrade shortly. Which also includes a brand new UX and method for backups and recovery.
Next up on the agenda, Silent Payments and block templates for DATUM.
🔥
Fully Noded®️ retweeted
Increased entropy to 512bits, put said entropy through sha256 to output 256bits of said entropy. 💪 @FullyNoded
Fully Noded®️ retweeted
Anyone running BTC Payserver do the following in this order.
1. Shutdown BTC PayServer
2. Rotate your macroons, delete all macroons
3. Update BTC PayServer
4. rest is up to you, but personally i wouldn't turn it back on
Fully Noded®️ 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.
Fully Noded®️ retweeted
Replying to @FullyNoded
@FullyNoded does not rely on any central service or servers. Run your own node behind Tor if you are serious about using bitcoin in a censorship resistant manner.
DMs and the telegram are always open if you need help or have questions.
Fully Noded®️ retweeted
Replying to @FullyNoded
@FullyNoded relies on Apples Secure Enclave for entropy and to store secrets. It has been rigorously tested and certified: “Apple’s Secure Enclave Processor (SEP) True Random Number Generator (TRNG) entropy source is validated under NIST’s Entropy Source Validation (ESV) program against SP 800-90B.”
Also the Secure Enclave is sealed during the manufacturing process not even Apple has access or the FBI see the following court case: “2015–2016 San Bernardino investigation dispute (often called Apple v. FBI or the San Bernardino iPhone case)”
The @BlockstreamJade is one of the best hardware wallets on the market, bar none. I wonder how many people dismissed it due to the FUD that it lacked a secure element?
Secure elements aren't a panacea but are often sold as such. A physical SE in the device means everything needed to extract the seed is sitting right there, and potentially in the hands of someone that steals it. It's a stationary target. An attacker can wreck a dozen units learning the technique before touching yours. Ledger's Donjon has done exactly this to Coldcard silicon twice, the Mk2 ATECC508A and later the SE2 on Mk4, and voltage-glitched the Trezor Safe 3's MCU.
Jade moves the target instead. Your seed is encrypted with an AES-256 key that the device and a blind oracle build between them, and the oracle never holds more than a piece of it. The ESP32 only has ciphertext. You can't extract something that was never in there. The attack turns interactive, against a party who rate-limits you and wipes its half after three bad PINs.
Coldcard split your secret across three chips from different SEs. That genuinely helps against one vendor's silicon getting broken. But the pitch lands as arithmetic, and security doesn't really work that way. As we've seen, bad entropy at setup meant none of the silicon even mattered. You could have 10 SEs in the CC and that wouldn't have saved you. But people ate that security theater up.
My mind keeps circling back to what we could have done differently. I keep landing on the same conclusion: we should have pushed back on the SE FUD much harder, and promoted Jade far more aggressively. We'd never have attacked CC, but we should never have taken the unwarranted flak for Jade's security model. The FUD steered people away from Jade. If we'd fought it, maybe more of them would have avoided the CC tragedy.
When we first launched the Jade, it sold for just $39.99. For that price you got such an incredible amount of value (at launch and later with subsequent updates).
➡️ Virtual secure element via blind oracle (@Blockstream's or self-hosted)
➡️ Can function as a stateless signing device (like SeedSigner)
➡️ Anti-Exfil protocol to protect against your seed being exfiltrated (Jade is one of only two HWWs that do this)
➡️ Genuine Check verification to prove the device is authentic and untampered with
➡️ Secure Boot ensuring only properly signed firmware runs
➡️ BIP39 passphrase and duress PIN
➡️ Air-gapped operations
➡️ Store Liquid assets like @tether USDT
➡️ Multisig support AND the ability to back up the multisig config (descriptors) for a setup involving ANY devices (or mixed hardware/software), as long as at least one Jade is part of the multisig - this makes multisig far less brittle since losing the config is catastrophic
The best part of all of this? You don't even need to BUY a Jade. You can build your own with almost any ESP32 board. Pair it with your own self-hosted blind oracle and you have a completely sovereign stack with no HWW vendor supply chain risk.
If you're looking for a new hardware wallet, take a serious look at @BlockstreamJade. It's built by a world-class team of engineers and cryptographers assembled by @adam3us. But don't take my word for it. The firmware is fully open source, so read it yourself.
Don't Trust. Verify.
blockstream.com/jade










