+- 1ddbc53cebd3 -- 5d ------------------------------------------------------[...]+ | | | 😆😆😆 | | | +-- reply ------------------------------------------------------------------- ---+😆😆😆
npub1rhdu208t6vh03vswled09h65upr9ah9mlcz8lg9e67sdvk0aa6jq427zgk
+- 1ddbc53cebd3 -- 7d ------------------------------------------------------[...]+ | | | Bitcoin Security Info: Why to Never Sell Forked Bitcoin | | | | Imagine the situation in which Bitcoin just got forked. Now everyone has two | | versions of bitcoin associated with their wallet. It seems tempting to sell | | the one which seems worthless in the future but is currently still traded for | | a reasonably amount of money. | | | | The problem is called "the replay attack." Here’s how the attack works: when | | you sell you have create and broadcast a transaction to sell your forked | | coins. This transaction is signed with your private key. The big issue is that | | this transaction doesn't say which version of Bitcoin it's for. The person who | | buys your forked coins can take that exact same published transaction and | | broadcast it on the original Bitcoin network. Since the transaction is signed | | correctly, the original Bitcoin network accepts it, and your original coins | | get transferred to the buyer too. You just lost your original Bitcoin by | | accident. | | | | There is a solution to it, but that's not in your hands. Both chains (not only | | one) need to have a marker which makes transactions unique between different | | chains. For now just think of it like adding a special watermark to a check | | for one bank that the other bank won't accept. This "marker" is a technical | | change that the developers of the forked coin must build into their system. It | | makes it so any transaction for the new coin is automatically rejected by the | | original Bitcoin network. If this is the case, you need to make a code | | analysis before you sell the bitcoin fork. | | | | Some people think you can taint your UTXOs, but this is not protecting you at | | all from the replay attack. The idea of "tainting" is to make a small test | | transaction first to somehow separate your coins, but that test transaction | | itself can be replayed, so it doesn't work. | | Even sending the bitcoin which you want to keep to a brand new wallet first | | doesn't protect you from the replay attack!! The attacker just replays that | | transaction too, and now both sets of your coins are in your new wallet, still | | stuck together. | | | | nostr:nprofile1qqsvxq03xdev3uxehjqcdkr5lfzl5vawmcf7vm6ps73m6ghwg8y4k2spz4mhxue | | 69uhk2er9dchxummnw3ezumrpdejqz9nhwden5te0dehhxarj9eekcmm5dpujuamfdcq9v6rc | | nostr:nprofile1qqstu7jjjx6n969erredexq539y2x0f7pks80zxhg9hh8dx8298s3espz4mhxue | | 69uhk2er9dchxummnw3ezumrpdejqz8rhwden5te0dehhxarj94ex2mrp0yh8wmrkwvh8xurpvdjs4 | | 5egyh | | Could you build in checks and warnings for known forks without replay | | protection? | | | +-- reply ------------------------------------------------------------------- ---+Bitcoin Security Info: Why to Never Sell Forked Bitcoin Imagine the situation in which Bitcoin just got forked. Now everyone has two versions of bitcoin associated with their wallet. It seems tempting to sell the one which seems worthless in the future but is currently still traded for a reasonably amount of money. The problem is called "the replay attack." Here’s how the attack works: when you sell you have create and broadcast a transaction to sell your forked coins. This transaction is signed with your private key. The big issue is that this transaction doesn't say which version of Bitcoin it's for. The person who buys your forked coins can take that exact same published transaction and broadcast it on the original Bitcoin network. Since the transaction is signed correctly, the original Bitcoin network accepts it, and your original coins get transferred to the buyer too. You just lost your original Bitcoin by accident. There is a solution to it, but that's not in your hands. Both chains (not only one) need to have a marker which makes transactions unique between different chains. For now just think of it like adding a special watermark to a check for one bank that the other bank won't accept. This "marker" is a technical change that the developers of the forked coin must build into their system. It makes it so any transaction for the new coin is automatically rejected by the original Bitcoin network. If this is the case, you need to make a code analysis before you sell the bitcoin fork. Some people think you can taint your UTXOs, but this is not protecting you at all from the replay attack. The idea of "tainting" is to make a small test transaction first to somehow separate your coins, but that test transaction itself can be replayed, so it doesn't work. Even sending the bitcoin which you want to keep to a brand new wallet first doesn't protect you from the replay attack!! The attacker just replays that transaction too, and now both sets of your coins are in your new wallet, still stuck together. nostr:nprofile1qqsvxq03xdev3uxehjqcdkr5lfzl5vawmcf7vm6ps73m6ghwg8y4k2spz4mhxue69uhk2er9dchxummnw3ezumrpdejqz9nhwden5te0dehhxarj9eekcmm5dpujuamfdcq9v6rc nostr:nprofile1qqstu7jjjx6n969erredexq539y2x0f7pks80zxhg9hh8dx8298s3espz4mhxue69uhk2er9dchxummnw3ezumrpdejqz8rhwden5te0dehhxarj94ex2mrp0yh8wmrkwvh8xurpvdjs45egyh Could you build in checks and warnings for known forks without replay protection?
+- 1ddbc53cebd3 -- 17d -----------------------------------------------------[...]+ | | | Dont we have a platform which doesn't require registration via email to pay | | some sats for articles? | | | +-- reply ------------------------------------------------------------------- ---+Dont we have a platform which doesn't require registration via email to pay some sats for articles?
+- 1ddbc53cebd3 -- 18d -----------------------------------------------------[...]+ | | | I have tried it. It's a useful little app 🤓 | | | | nostr:nevent1qqsvevemcsrnt07e36swsahzfa7pnz439430r28qc7lqgzerx5x3lzszyql746jrm | | 3tmwpd3k8frtvqn0wsnlpzdcdmn37pphggm5j3agwux2qcyqqqqqqg5dcwuy | | | +-- reply ------------------------------------------------------------------- ---+I have tried it. It's a useful little app 🤓 nostr:nevent1qqsvevemcsrnt07e36swsahzfa7pnz439430r28qc7lqgzerx5x3lzszyql746jrm3tmwpd3k8frtvqn0wsnlpzdcdmn37pphggm5j3agwux2qcyqqqqqqg5dcwuy
+- 1ddbc53cebd3 -- 24d -----------------------------------------------------[...]+ | | | 🤣 | | | +-- reply ------------------------------------------------------------------- ---+🤣
+- 1ddbc53cebd3 -- 25d -----------------------------------------------------[...]+ | | | Someone sent me a serious stack of sats a few hours ago. Whoever it was - | | thank you! 😎 Always very appreciated! 🙏🧡 | | | +-- reply ------------------------------------------------------------------- ---+Someone sent me a serious stack of sats a few hours ago. Whoever it was - thank you! 😎 Always very appreciated! 🙏🧡
+- 1ddbc53cebd3 -- 27d -----------------------------------------------------[...]+ | | | A Privacy Loophole When Installing | | nostr:nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpz4mhxue | | 69uhhyetvv9ujuerfw36x7tnsw43q0uc5de on a Pixel | | | | For anyone serious about de-Googling their life, you need to know about this. | | I've seen privacy concerned people overlook a crucial step in the GrapheneOS | | installation process that creates a direct link to Google. | | | | The Step: On a Google Pixel, before you can unlock the bootloader, you must | | enable "OEM unlocking" in the Developer Options. | | | | The moment you toggle that setting, your phone makes a network request to | | Google's servers. | | | | Google receives that request and can see your IP address. If you're doing this | | from your home network, an IP tied to your name, you've just created a digital | | fingerprint linking you (and your location) to that specific device's serial | | number before you even wiped it. | | | | Google now knows that 1) the person at your IP address is in possession of | | that specific Pixel phone, and 2) that you intended to modify its software!!! | | | | How to Mitigate: | | Use a trustworthy VPN, or preferably, public Wi-Fi (like a café) that is not | | associated with you. | | | | | | | | https://blossom.primal.net/d5d68a3474d642c4fc329a1517ba5ee0707cb5431dd11d4cefc | | 5dcbe373e0b7c.png | | | +-- reply ------------------------------------------------------------------- ---+A Privacy Loophole When Installing nostr:nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpz4mhxue69uhhyetvv9ujuerfw36x7tnsw43q0uc5de on a Pixel For anyone serious about de-Googling their life, you need to know about this. I've seen privacy concerned people overlook a crucial step in the GrapheneOS installation process that creates a direct link to Google. The Step: On a Google Pixel, before you can unlock the bootloader, you must enable "OEM unlocking" in the Developer Options. The moment you toggle that setting, your phone makes a network request to Google's servers. Google receives that request and can see your IP address. If you're doing this from your home network, an IP tied to your name, you've just created a digital fingerprint linking you (and your location) to that specific device's serial number before you even wiped it. Google now knows that 1) the person at your IP address is in possession of that specific Pixel phone, and 2) that you intended to modify its software!!! How to Mitigate: Use a trustworthy VPN, or preferably, public Wi-Fi (like a café) that is not associated with you. https://blossom.primal.net/d5d68a3474d642c4fc329a1517ba5ee0707cb5431dd11d4cefc5dcbe373e0b7c.png
+- 1ddbc53cebd3 -- 34d -----------------------------------------------------[...]+ | | | Cool! Many thanks | | nostr:nprofile1qqstwf6d9r37nqalwgxmfd9p9gclt3l0yc3jp5zuyhkfqjy6extz3jcpz9mhxue | | 69uhkummnw3ezumrpdejz7q2uwaehxw309ac8ymmc0yhxummnw3ez6un9d3shjtnpwpcz7vehvs6xx | | venvgmxgep3x9jnzdf4xd3nxephv9skycn9vsergcnrv5ukzdfsve3nwvnxxucngd35vsenje3cvc6 | | nycm98qekyetrvcuqnnucu2 | | nostr:nprofile1qqsyu9me0re6pulxuzpkwnj5dkyp83dy9x2p7mpa2gtnvajxf88xepqelq32z | | nostr:nprofile1qqsw3znfr6vdnxrujezjrhlkqqjlvpcqx79ys7gcph9mkjjsy7zsgygpz3mhxue | | 69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5scvysa | | | | I conclude from all your replies that: | | | | 🔸As a developer, you should verify the open-source code by: | | | | 1. Checking how the k value is generated. For any unique transaction, you | | should always get the same k value (Note: this will never happen after | | broadcasting the first transaction. Youll never get the exact same transaction | | again). For any different transaction, you should always get a different k | | value. (Note: E. g. Trezor uses RFC 6979 for generating deterministic k | | values.) This completely eliminates the risk of accidentally reusing a k | | value! | | 2. If code check passed, hash the downloaded firmware to confirm its | | integrity. | | | | 🔸Non-developers or ultra-paranoid users can perform a "signature test" against | | other devices. Sign the exact same transaction from two devices and compare | | them; the signatures should be completely identical. | | | | 🔸For ultimate protection that doesn't require verifying every update, use a | | multi-sig setup with hardware wallets from multiple manufacturers. | | | +-- reply ------------------------------------------------------------------- ---+Cool! Many thanks nostr:nprofile1qqstwf6d9r37nqalwgxmfd9p9gclt3l0yc3jp5zuyhkfqjy6extz3jcpz9mhxue69uhkummnw3ezumrpdejz7q2uwaehxw309ac8ymmc0yhxummnw3ez6un9d3shjtnpwpcz7vehvs6xxvenvgmxgep3x9jnzdf4xd3nxephv9skycn9vsergcnrv5ukzdfsve3nwvnxxucngd35vsenje3cvc6nycm98qekyetrvcuqnnucu2 nostr:nprofile1qqsyu9me0re6pulxuzpkwnj5dkyp83dy9x2p7mpa2gtnvajxf88xepqelq32z nostr:nprofile1qqsw3znfr6vdnxrujezjrhlkqqjlvpcqx79ys7gcph9mkjjsy7zsgygpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5scvysa I conclude from all your replies that: 🔸As a developer, you should verify the open-source code by: 1. Checking how the k value is generated. For any unique transaction, you should always get the same k value (Note: this will never happen after broadcasting the first transaction. Youll never get the exact same transaction again). For any different transaction, you should always get a different k value. (Note: E. g. Trezor uses RFC 6979 for generating deterministic k values.) This completely eliminates the risk of accidentally reusing a k value! 2. If code check passed, hash the downloaded firmware to confirm its integrity. 🔸Non-developers or ultra-paranoid users can perform a "signature test" against other devices. Sign the exact same transaction from two devices and compare them; the signatures should be completely identical. 🔸For ultimate protection that doesn't require verifying every update, use a multi-sig setup with hardware wallets from multiple manufacturers.
+- 1ddbc53cebd3 -- 35d -----------------------------------------------------[...]+ | | | Thank you - that makes sense. Do you know of any tests that run on wallets to | | check if they are corrupted? | | | +-- reply ------------------------------------------------------------------- ---+Thank you - that makes sense. Do you know of any tests that run on wallets to check if they are corrupted?
+- 1ddbc53cebd3 -- 35d -----------------------------------------------------[...]+ | | | I have a security question that has been bugging me. | | | | When a wallet broadcasts a Bitcoin transaction, we trust it's only sending the | | signature and transaction data. But how can we be certain that fragments of | | the private key aren't being secretly embedded in the broadcast over time? | | | | For example, could a malicious hardware wallet manufacturer design a device | | that, after many transactions, allows them to reassemble the bits and know the | | private key? | | | | Has anyone ever done a public test where the same seed phrase is used on | | different hardware wallets (like | | nostr:nprofile1qqs9v9et20mnqagtgrnrc5qmzcrgmkt2y3087p23vawqlmyczlhfdcqprdmhxue | | 69uhkvet9v3ejumn0wd68ytnzv9hxgtmsd93hxqg7waehxw309ahx7um5wgh8xetvvckkget5v4ex6 | | 6twv4jzuer9c822gk | | nostr:nprofile1qqsw3znfr6vdnxrujezjrhlkqqjlvpcqx79ys7gcph9mkjjsy7zsgygpz3mhxue | | 69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5scvysa, | | Trezor | | nostr:nprofile1qqsyu9me0re6pulxuzpkwnj5dkyp83dy9x2p7mpa2gtnvajxf88xepqelq32z, | | nostr:nprofile1qqsdg2ufsmn9t0fkal4jsd7pmx3370uwaa5gerf385ju0xmussygn3qprpmhxw3 | | 09uurzt3k8qhrzdes9ccnyv36xucnzdp0qyd8wumn8ghj7mrwvf5hguewv9e826m49e4hymewddez7 | | rsenut) to sign the exact same transaction? | | | | If the resulting signatures are identical, would that be definitive proof that | | both devices are performing the standard, non-corrupted signing process? | | | +-- reply ------------------------------------------------------------------- ---+I have a security question that has been bugging me. When a wallet broadcasts a Bitcoin transaction, we trust it's only sending the signature and transaction data. But how can we be certain that fragments of the private key aren't being secretly embedded in the broadcast over time? For example, could a malicious hardware wallet manufacturer design a device that, after many transactions, allows them to reassemble the bits and know the private key? Has anyone ever done a public test where the same seed phrase is used on different hardware wallets (like nostr:nprofile1qqs9v9et20mnqagtgrnrc5qmzcrgmkt2y3087p23vawqlmyczlhfdcqprdmhxue69uhkvet9v3ejumn0wd68ytnzv9hxgtmsd93hxqg7waehxw309ahx7um5wgh8xetvvckkget5v4ex66twv4jzuer9c822gk nostr:nprofile1qqsw3znfr6vdnxrujezjrhlkqqjlvpcqx79ys7gcph9mkjjsy7zsgygpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5scvysa, Trezor nostr:nprofile1qqsyu9me0re6pulxuzpkwnj5dkyp83dy9x2p7mpa2gtnvajxf88xepqelq32z, nostr:nprofile1qqsdg2ufsmn9t0fkal4jsd7pmx3370uwaa5gerf385ju0xmussygn3qprpmhxw309uurzt3k8qhrzdes9ccnyv36xucnzdp0qyd8wumn8ghj7mrwvf5hguewv9e826m49e4hymewddez7rsenut) to sign the exact same transaction? If the resulting signatures are identical, would that be definitive proof that both devices are performing the standard, non-corrupted signing process?
+- 1ddbc53cebd3 -- 37d -----------------------------------------------------[...]+ | | | :) What are you building? | | | +-- reply ------------------------------------------------------------------- ---+:) What are you building?
+- 1ddbc53cebd3 -- 40d -----------------------------------------------------[...]+ | | | 🤣 | | | +-- reply ------------------------------------------------------------------- ---+🤣
+- 1ddbc53cebd3 -- 74d -----------------------------------------------------[...]+ | | | Looks like a @JPMorgan bathroom!!! Haha... | | | +-- reply ------------------------------------------------------------------- ---+Looks like a @JPMorgan bathroom!!! Haha...
+- 1ddbc53cebd3 -- 77d -----------------------------------------------------[...]+ | | | Another real story, based on real events in the finance and tech world. Names, | | companies, and details have been changed. | | | | Title: Modern Architecture of Prison | | | | On Tuesday morning, Dylan got ready for another day at the office. She | | followed the same habit she had for years: wearing the same clothes as always | | - jeans and one of two 'office' hoodies. Dylan couldn't be bothered to think | | about how to dress for the office and definitely didn't want to spend her | | money on clothing. Her colleagues assumed she had multiple versions of the | | same hoodies, and she let them believe it. | | | | Once ready, she made her way to the office. She swiped her card at the door of | | the clinically looking entrance hall and found a space in the open-plan | | office. As usual, the fluorescent lights hummed a monotonous tune, the | | official soundtrack to Dylan's five-year sentence at 'Black Solutions'. | | | | The hoodie she was wearing today, with its bold, orange Bitcoin logo, was her | | small, silent rebellion. It was like a little flag planted in corporate soil, | | a reminder that a world of decentralised, voluntary value existed beyond these | | corporate walls. A world she believed in. A world she was actively helping to | | create, while accepting one paycheck at a time from Black Solutions. At least, | | she thought, until she paid down the loan she'd taken out for 'home furniture' | | a few years ago - just after Michael Saylor announced he would leverage the | | fiat system to buy Bitcoin for MicroStrategy. | | | | Today, her manager called her into a team meeting. They had secured a new | | contract for a project called 'Titan', a new project for a US bank. "Dylan," | | said the manager, David, gesturing to a seat. "Glad you could make it. We're | | excited to use your expertise for this project." | | | | A man from Titan, a senior VP named Thomas, began a presentation. "Our | | customers need to be protected," he stated, his voice flat and cold. "They are | | moving increasingly large amounts of funds outside the regulatory space. We | | require an automated solution." A slide appeared on the screen. At its heart | | was a module: "Financial Transaction Monitoring & Flagging System." | | | | Dylan's blood ran cold. David beamed at her. "Dylan, you'll be leading the | | development of the AI agents. We need your expertise in building resilient, | | autonomous systems." | | | | Thomas from Titan looked directly at her, his gaze dropping from her face to | | the orange logo printed on her hoodie. A flicker of something - amusement? - | | crossed his features before being smoothed away. "Your agents," he continued, | | "will need to identify, analyse, and recommend for immediate blockage any | | transaction originating from or destined for known blacklisted accounts, as | | well as flag suspicious patterns in real-time." | | | | Dylan believed in censorship-resistant money, in the idea that a transaction, | | once broadcast, was final. And she was being asked to build the digital | | equivalent of a border guard, an AI sniffer dog trained to hunt down and | | destroy the very thing she held sacred. | | | | Dylan looked at the screen and at the expectant faces around the table. She | | looked down at the orange Bitcoin Logo on her hoodie, a symbol of freedom in a | | room full of architects for a new kind of prison. The project was starting | | next week. | | | | Dylan nodded slowly, the motion mechanical. "Of course," she heard herself | | say. "We'll get on it." | | | | The humming of the lights seemed to grow louder, filling the space in her | | mind. As she stood to leave, she realised the entry to prison was the debt. | | Her loan had been the first wall, and every compromise since had been another | | brick, mortared with fear and wrong rationalisation. | | nostr:nprofile1qqs22afg9k7epyay82slkpap2mquwn9k0cmh3fxk2y8r4nr7wq6xapsprpmhxue | | 69uhkummnw3ezuer0de4hjtnnda3kjctvqywhwumn8ghj7mn0wd68ytndv9uxjmtpvd5hgctyv4kzu | | mmjvuwzdz72 | | | +-- reply ------------------------------------------------------------------- ---+Another real story, based on real events in the finance and tech world. Names, companies, and details have been changed. Title: Modern Architecture of Prison On Tuesday morning, Dylan got ready for another day at the office. She followed the same habit she had for years: wearing the same clothes as always - jeans and one of two 'office' hoodies. Dylan couldn't be bothered to think about how to dress for the office and definitely didn't want to spend her money on clothing. Her colleagues assumed she had multiple versions of the same hoodies, and she let them believe it. Once ready, she made her way to the office. She swiped her card at the door of the clinically looking entrance hall and found a space in the open-plan office. As usual, the fluorescent lights hummed a monotonous tune, the official soundtrack to Dylan's five-year sentence at 'Black Solutions'. The hoodie she was wearing today, with its bold, orange Bitcoin logo, was her small, silent rebellion. It was like a little flag planted in corporate soil, a reminder that a world of decentralised, voluntary value existed beyond these corporate walls. A world she believed in. A world she was actively helping to create, while accepting one paycheck at a time from Black Solutions. At least, she thought, until she paid down the loan she'd taken out for 'home furniture' a few years ago - just after Michael Saylor announced he would leverage the fiat system to buy Bitcoin for MicroStrategy. Today, her manager called her into a team meeting. They had secured a new contract for a project called 'Titan', a new project for a US bank. "Dylan," said the manager, David, gesturing to a seat. "Glad you could make it. We're excited to use your expertise for this project." A man from Titan, a senior VP named Thomas, began a presentation. "Our customers need to be protected," he stated, his voice flat and cold. "They are moving increasingly large amounts of funds outside the regulatory space. We require an automated solution." A slide appeared on the screen. At its heart was a module: "Financial Transaction Monitoring & Flagging System." Dylan's blood ran cold. David beamed at her. "Dylan, you'll be leading the development of the AI agents. We need your expertise in building resilient, autonomous systems." Thomas from Titan looked directly at her, his gaze dropping from her face to the orange logo printed on her hoodie. A flicker of something - amusement? - crossed his features before being smoothed away. "Your agents," he continued, "will need to identify, analyse, and recommend for immediate blockage any transaction originating from or destined for known blacklisted accounts, as well as flag suspicious patterns in real-time." Dylan believed in censorship-resistant money, in the idea that a transaction, once broadcast, was final. And she was being asked to build the digital equivalent of a border guard, an AI sniffer dog trained to hunt down and destroy the very thing she held sacred. Dylan looked at the screen and at the expectant faces around the table. She looked down at the orange Bitcoin Logo on her hoodie, a symbol of freedom in a room full of architects for a new kind of prison. The project was starting next week. Dylan nodded slowly, the motion mechanical. "Of course," she heard herself say. "We'll get on it." The humming of the lights seemed to grow louder, filling the space in her mind. As she stood to leave, she realised the entry to prison was the debt. Her loan had been the first wall, and every compromise since had been another brick, mortared with fear and wrong rationalisation. nostr:nprofile1qqs22afg9k7epyay82slkpap2mquwn9k0cmh3fxk2y8r4nr7wq6xapsprpmhxue69uhkummnw3ezuer0de4hjtnnda3kjctvqywhwumn8ghj7mn0wd68ytndv9uxjmtpvd5hgctyv4kzummjvuwzdz72
+- 1ddbc53cebd3 -- 82d -----------------------------------------------------[...]+ | | | Or if the government confiscates your precious metals again and threaten to | | jail you otherwise... | | | +-- reply ------------------------------------------------------------------- ---+Or if the government confiscates your precious metals again and threaten to jail you otherwise...
+- 1ddbc53cebd3 -- 82d -----------------------------------------------------[...]+ | | | Does anyone has a link a German translation of the book "Fiat Food" by Matthew | | Lysiak? | | | +-- reply ------------------------------------------------------------------- ---+Does anyone has a link a German translation of the book "Fiat Food" by Matthew Lysiak?
+- 1ddbc53cebd3 -- 82d -----------------------------------------------------[...]+ | | | People think Bitcoiners are taking huge financial risks, when it's the | | opposite. I'm terrified of what's happening in the world, and I know Bitcoin | | is the asset that will protect me, there is no better asset to own. | | | | If you're the most risk-averse person on the planet, you should only have | | Bitcoin. If you're still worried, run a node, and if you want absolute | | certainty, run a few miners to give Bitcoin heartbeats. 🧡🧡 | | | +-- reply ------------------------------------------------------------------- ---+People think Bitcoiners are taking huge financial risks, when it's the opposite. I'm terrified of what's happening in the world, and I know Bitcoin is the asset that will protect me, there is no better asset to own. If you're the most risk-averse person on the planet, you should only have Bitcoin. If you're still worried, run a node, and if you want absolute certainty, run a few miners to give Bitcoin heartbeats. 🧡🧡
+- 1ddbc53cebd3 -- 84d -----------------------------------------------------[...]+ | | | I believe in Bitcoin the same way I believe in evolution. | | | +-- reply ------------------------------------------------------------------- ---+I believe in Bitcoin the same way I believe in evolution.
+- 1ddbc53cebd3 -- 86d -----------------------------------------------------[...]+ | | | https://blossom.primal.net/c2521d52cbd7f0aaf846819bfffdb28d5f3b1217c1c247dfe4c | | b2a8689f68c6e.mp4 | | | +-- reply ------------------------------------------------------------------- ---+https://blossom.primal.net/c2521d52cbd7f0aaf846819bfffdb28d5f3b1217c1c247dfe4cb2a8689f68c6e.mp4
+- 1ddbc53cebd3 -- 86d -----------------------------------------------------[...]+ | | | I guess Bitcoiners have an higher threshold for frustration... So they can | | bundle up their energy to rebel more 🙌🙂💪 | | | +-- reply ------------------------------------------------------------------- ---+I guess Bitcoiners have an higher threshold for frustration... So they can bundle up their energy to rebel more 🙌🙂💪
+- 1ddbc53cebd3 -- 86d -----------------------------------------------------[...]+ | | | Oh cool - I'll check him out :-) Thanks for sharing the name. | | | +-- reply ------------------------------------------------------------------- ---+Oh cool - I'll check him out :-) Thanks for sharing the name.
+- 1ddbc53cebd3 -- 86d -----------------------------------------------------[...]+ | | | Yes, the "Bullshit Jobs". | | | +-- reply ------------------------------------------------------------------- ---+Yes, the "Bullshit Jobs".
+- 1ddbc53cebd3 -- 86d -----------------------------------------------------[...]+ | | | Private giant close the the money printer (government) | | | +-- reply ------------------------------------------------------------------- ---+Private giant close the the money printer (government)
+- 1ddbc53cebd3 -- 87d -----------------------------------------------------[...]+ | | | This story is based on real events in the finance/tech world. Names, | | companies, and details have been changed to protect everyone involved. I used | | AI to make it more entertaining. Just so you know. 🙂 | | | | The email from Finance landed with the soft chime of opportunity: "Project | | Genesis - £2.8M Approved." Alistair stared at the screen, the numbers swimming | | before his eyes. 2.8 million pounds. For agentic AI. He leaned back in his | | ergonomic chair, the one they'd bought during the "Quantum Leap" restructuring | | two years ago, and let out a slow breath. | | | | His team of six, huddled in the designated "Innovation Pod" (a glass box with | | a dying ficus), looked to him for direction. They were the "Agentic AI | | Research Division," a title that sounded impressive until you remembered | | they'd never actually built an agent. | | | | "So," said Priya, their lead engineer, breaking the silence. "We have the | | money. What's the business problem we're solving?" | | | | Alistair felt the familiar knot tighten in his stomach. This was the ritual. | | The grand inversion of how things were supposed to work. The board, seduced by | | white papers and breathless articles about "autonomous digital workforces," | | had allocated the capital. Now, it was on them—the tech team—to | | reverse-engineer a reason for its existence. It was like being given a coffin | | and being told to find a worthy corpse. | | | | "We're exploring the frontiers," Alistair said, the corporate-speak tasting | | like ash in his mouth. "The mandate is to research and develop a | | proof-of-concept for an agentic system that can... uh... dynamically optimize | | business workflows." | | | | Priya didn't blink. "Okay. Which workflows? For which client? | | | | And there it was. The question that could not be answered. They had no | | clients. They had no workflows. The ROI was a fictional number in a PowerPoint | | deck that had secured the funding. Their job wasn't to solve a problem; it was | | to build a problem sophisticated enough to fit the solution they were now | | forced to imagine. | | | | For the next three weeks, the Innovation Pod became a factory for problems. | | They brainstormed. They whiteboarded. They drank endless lukewarm coffee. They | | came up with "Agent-based supply chain reconciliation," "Autonomous customer | | sentiment analysis," and "AI-driven contract lifecycle management." Each idea | | was a magnificent, gleaming edifice of jargon, built on a foundation of | | nothing. | | | | They finally settled on "Nexus," an agentic system that would supposedly | | manage complex, multi-departmental project dependencies. It sounded plausible. | | It sounded expensive. It sounded like something that could burn through £2.8 | | million in research and development without ever needing to prove its worth. | | | | Alistair presented it to the steering committee. He used words like | | "synergistic," "paradigm," and "cognitive orchestration." He showed them a | | slick UI mockup that their one designer had whipped up in a week. The UI was a | | lie, a beautiful, interactive fiction. The agents it depicted were lines of | | code in a git repository that didn't exist yet. | | | | The board loved it. They approved the next tranche of funding for "Phase 2: | | Agent Simulation." | | | | That night, Alistair stayed late. He walked through the empty office, past the | | desks of the "Quantum Computing Team" (who were now the "Blockchain Synergy | | Group" after the last company reshuffle). He thought about the tax money that | | flowed from his paycheck into the government's coffers, only to be routed back | | to them as grants for initiatives like this. It wasn't a company; it was a | | money laundering operation for incompetence, a perfectly circular system where | | public funds were transformed into private salaries for solving problems that | | didn't exist. | | | | He sat back down at his desk and opened a new terminal window. He typed mkdir | | nexus_project and hit enter. The cursor blinked on the empty line, a tiny, | | digital heart waiting for a pulse. He had the money. He had the team. He had | | the mandate. All he needed now was a business case. | | | +-- reply ------------------------------------------------------------------- ---+This story is based on real events in the finance/tech world. Names, companies, and details have been changed to protect everyone involved. I used AI to make it more entertaining. Just so you know. 🙂 The email from Finance landed with the soft chime of opportunity: "Project Genesis - £2.8M Approved." Alistair stared at the screen, the numbers swimming before his eyes. 2.8 million pounds. For agentic AI. He leaned back in his ergonomic chair, the one they'd bought during the "Quantum Leap" restructuring two years ago, and let out a slow breath. His team of six, huddled in the designated "Innovation Pod" (a glass box with a dying ficus), looked to him for direction. They were the "Agentic AI Research Division," a title that sounded impressive until you remembered they'd never actually built an agent. "So," said Priya, their lead engineer, breaking the silence. "We have the money. What's the business problem we're solving?" Alistair felt the familiar knot tighten in his stomach. This was the ritual. The grand inversion of how things were supposed to work. The board, seduced by white papers and breathless articles about "autonomous digital workforces," had allocated the capital. Now, it was on them—the tech team—to reverse-engineer a reason for its existence. It was like being given a coffin and being told to find a worthy corpse. "We're exploring the frontiers," Alistair said, the corporate-speak tasting like ash in his mouth. "The mandate is to research and develop a proof-of-concept for an agentic system that can... uh... dynamically optimize business workflows." Priya didn't blink. "Okay. Which workflows? For which client? And there it was. The question that could not be answered. They had no clients. They had no workflows. The ROI was a fictional number in a PowerPoint deck that had secured the funding. Their job wasn't to solve a problem; it was to build a problem sophisticated enough to fit the solution they were now forced to imagine. For the next three weeks, the Innovation Pod became a factory for problems. They brainstormed. They whiteboarded. They drank endless lukewarm coffee. They came up with "Agent-based supply chain reconciliation," "Autonomous customer sentiment analysis," and "AI-driven contract lifecycle management." Each idea was a magnificent, gleaming edifice of jargon, built on a foundation of nothing. They finally settled on "Nexus," an agentic system that would supposedly manage complex, multi-departmental project dependencies. It sounded plausible. It sounded expensive. It sounded like something that could burn through £2.8 million in research and development without ever needing to prove its worth. Alistair presented it to the steering committee. He used words like "synergistic," "paradigm," and "cognitive orchestration." He showed them a slick UI mockup that their one designer had whipped up in a week. The UI was a lie, a beautiful, interactive fiction. The agents it depicted were lines of code in a git repository that didn't exist yet. The board loved it. They approved the next tranche of funding for "Phase 2: Agent Simulation." That night, Alistair stayed late. He walked through the empty office, past the desks of the "Quantum Computing Team" (who were now the "Blockchain Synergy Group" after the last company reshuffle). He thought about the tax money that flowed from his paycheck into the government's coffers, only to be routed back to them as grants for initiatives like this. It wasn't a company; it was a money laundering operation for incompetence, a perfectly circular system where public funds were transformed into private salaries for solving problems that didn't exist. He sat back down at his desk and opened a new terminal window. He typed mkdir nexus_project and hit enter. The cursor blinked on the empty line, a tiny, digital heart waiting for a pulse. He had the money. He had the team. He had the mandate. All he needed now was a business case.
+- 1ddbc53cebd3 -- 92d -----------------------------------------------------[...]+ | | | Strong lifting skills create strong minds 🙂 💪 | | | +-- reply ------------------------------------------------------------------- ---+Strong lifting skills create strong minds 🙂 💪
+- 1ddbc53cebd3 -- 92d -----------------------------------------------------[...]+ | | | And the next service 😔 Venice AI isn't available to UK without surveillance | | either... | | | | | | | | https://blossom.primal.net/b954abe1a502e7eaee48ffb86bef0764a999817010d3f9a3289 | | cb0077d00cb37.jpg | | | +-- reply ------------------------------------------------------------------- ---+And the next service 😔 Venice AI isn't available to UK without surveillance either... https://blossom.primal.net/b954abe1a502e7eaee48ffb86bef0764a999817010d3f9a3289cb0077d00cb37.jpg
+- 1ddbc53cebd3 -- 93d -----------------------------------------------------[...]+ | | | Yes that's an option 👍 | | It would be easier for them to use the store, every additional step is an | | adoption barrier 😶 | | | +-- reply ------------------------------------------------------------------- ---+Yes that's an option 👍 It would be easier for them to use the store, every additional step is an adoption barrier 😶
+- 1ddbc53cebd3 -- 93d -----------------------------------------------------[...]+ | | | Currently traveling.. So I'm visiting many new places including gyms. This | | super cool gym was happy to try accepting bitcoin payments 🧡 and received | | their first payment today! 🙌 | | | | Unfortunately, | | nostr:nprofile1qqswe03hyye2jv3msylwkj8cml8d4m9qpc5g0tccrvrrcm86z0kcagg0zjv3w | | seems to be blocked by Apple and Google Store in the United Kingdom👎 Can we do | | something about that? | | | | We instead downloaded | | nostr:nprofile1qqs2nsd66pv44e5avmytw4ejy7k7fn8fq7rczrnaexcy8v2y484xjcspp4mhxue | | 69uhkummn9ekx7mqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqenp5z2, worked | | fine - only the channel size management is not ideal. | | | | | | | | https://blossom.primal.net/573f8ceb53667e2312457c212e0c540860c609f2c0e86063717 | | d5ec8645dc633.mp4 | | | +-- reply ------------------------------------------------------------------- ---+Currently traveling.. So I'm visiting many new places including gyms. This super cool gym was happy to try accepting bitcoin payments 🧡 and received their first payment today! 🙌 Unfortunately, nostr:nprofile1qqswe03hyye2jv3msylwkj8cml8d4m9qpc5g0tccrvrrcm86z0kcagg0zjv3w seems to be blocked by Apple and Google Store in the United Kingdom👎 Can we do something about that? We instead downloaded nostr:nprofile1qqs2nsd66pv44e5avmytw4ejy7k7fn8fq7rczrnaexcy8v2y484xjcspp4mhxue69uhkummn9ekx7mqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqenp5z2, worked fine - only the channel size management is not ideal. https://blossom.primal.net/573f8ceb53667e2312457c212e0c540860c609f2c0e86063717d5ec8645dc633.mp4
+- 1ddbc53cebd3 -- 96d -----------------------------------------------------[...]+ | | | Thank you for coming 🧡🧡🧡🤗 | | | +-- reply ------------------------------------------------------------------- ---+Thank you for coming 🧡🧡🧡🤗
+- 1ddbc53cebd3 -- 100d ----------------------------------------------------[...]+ | | | Reminder for everyone who wants to join the next online session titled | | "Demystify Bitcoin - The History of Money" | | | | We will start at 10 AM GMT! | | (Saturday, 17th of January) | | | | See you 🙌🧡 | | | | Join here | | https://talk.brave.com/x2n1h_lCIV2zk20xWmMgrqcqd4Nto7MlM5cyr5C55D4 | | | +-- reply ------------------------------------------------------------------- ---+Reminder for everyone who wants to join the next online session titled "Demystify Bitcoin - The History of Money" We will start at 10 AM GMT! (Saturday, 17th of January) See you 🙌🧡 Join here https://talk.brave.com/x2n1h_lCIV2zk20xWmMgrqcqd4Nto7MlM5cyr5C55D4
No replies found in cached notes yet.
+- 1ddbc53cebd3 -- 27d -----------------------------------------------------[...]+ | | | A Privacy Loophole When Installing | | nostr:nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpz4mhxue | | 69uhhyetvv9ujuerfw36x7tnsw43q0uc5de on a Pixel | | | | For anyone serious about de-Googling their life, you need to know about this. | | I've seen privacy concerned people overlook a crucial step in the GrapheneOS | | installation process that creates a direct link to Google. | | | | The Step: On a Google Pixel, before you can unlock the bootloader, you must | | enable "OEM unlocking" in the Developer Options. | | | | The moment you toggle that setting, your phone makes a network request to | | Google's servers. | | | | Google receives that request and can see your IP address. If you're doing this | | from your home network, an IP tied to your name, you've just created a digital | | fingerprint linking you (and your location) to that specific device's serial | | number before you even wiped it. | | | | Google now knows that 1) the person at your IP address is in possession of | | that specific Pixel phone, and 2) that you intended to modify its software!!! | | | | How to Mitigate: | | Use a trustworthy VPN, or preferably, public Wi-Fi (like a café) that is not | | associated with you. | | | | | | | | https://blossom.primal.net/d5d68a3474d642c4fc329a1517ba5ee0707cb5431dd11d4cefc | | 5dcbe373e0b7c.png | | | +-- reply ------------------------------------------------------------------- ---+A Privacy Loophole When Installing nostr:nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpz4mhxue69uhhyetvv9ujuerfw36x7tnsw43q0uc5de on a Pixel For anyone serious about de-Googling their life, you need to know about this. I've seen privacy concerned people overlook a crucial step in the GrapheneOS installation process that creates a direct link to Google. The Step: On a Google Pixel, before you can unlock the bootloader, you must enable "OEM unlocking" in the Developer Options. The moment you toggle that setting, your phone makes a network request to Google's servers. Google receives that request and can see your IP address. If you're doing this from your home network, an IP tied to your name, you've just created a digital fingerprint linking you (and your location) to that specific device's serial number before you even wiped it. Google now knows that 1) the person at your IP address is in possession of that specific Pixel phone, and 2) that you intended to modify its software!!! How to Mitigate: Use a trustworthy VPN, or preferably, public Wi-Fi (like a café) that is not associated with you. https://blossom.primal.net/d5d68a3474d642c4fc329a1517ba5ee0707cb5431dd11d4cefc5dcbe373e0b7c.png
+- 1ddbc53cebd3 -- 86d -----------------------------------------------------[...]+ | | | https://blossom.primal.net/c2521d52cbd7f0aaf846819bfffdb28d5f3b1217c1c247dfe4c | | b2a8689f68c6e.mp4 | | | +-- reply ------------------------------------------------------------------- ---+https://blossom.primal.net/c2521d52cbd7f0aaf846819bfffdb28d5f3b1217c1c247dfe4cb2a8689f68c6e.mp4
+- 1ddbc53cebd3 -- 92d -----------------------------------------------------[...]+ | | | And the next service 😔 Venice AI isn't available to UK without surveillance | | either... | | | | | | | | https://blossom.primal.net/b954abe1a502e7eaee48ffb86bef0764a999817010d3f9a3289 | | cb0077d00cb37.jpg | | | +-- reply ------------------------------------------------------------------- ---+And the next service 😔 Venice AI isn't available to UK without surveillance either... https://blossom.primal.net/b954abe1a502e7eaee48ffb86bef0764a999817010d3f9a3289cb0077d00cb37.jpg
+- 1ddbc53cebd3 -- 93d -----------------------------------------------------[...]+ | | | Currently traveling.. So I'm visiting many new places including gyms. This | | super cool gym was happy to try accepting bitcoin payments 🧡 and received | | their first payment today! 🙌 | | | | Unfortunately, | | nostr:nprofile1qqswe03hyye2jv3msylwkj8cml8d4m9qpc5g0tccrvrrcm86z0kcagg0zjv3w | | seems to be blocked by Apple and Google Store in the United Kingdom👎 Can we do | | something about that? | | | | We instead downloaded | | nostr:nprofile1qqs2nsd66pv44e5avmytw4ejy7k7fn8fq7rczrnaexcy8v2y484xjcspp4mhxue | | 69uhkummn9ekx7mqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqenp5z2, worked | | fine - only the channel size management is not ideal. | | | | | | | | https://blossom.primal.net/573f8ceb53667e2312457c212e0c540860c609f2c0e86063717 | | d5ec8645dc633.mp4 | | | +-- reply ------------------------------------------------------------------- ---+Currently traveling.. So I'm visiting many new places including gyms. This super cool gym was happy to try accepting bitcoin payments 🧡 and received their first payment today! 🙌 Unfortunately, nostr:nprofile1qqswe03hyye2jv3msylwkj8cml8d4m9qpc5g0tccrvrrcm86z0kcagg0zjv3w seems to be blocked by Apple and Google Store in the United Kingdom👎 Can we do something about that? We instead downloaded nostr:nprofile1qqs2nsd66pv44e5avmytw4ejy7k7fn8fq7rczrnaexcy8v2y484xjcspp4mhxue69uhkummn9ekx7mqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqenp5z2, worked fine - only the channel size management is not ideal. https://blossom.primal.net/573f8ceb53667e2312457c212e0c540860c609f2c0e86063717d5ec8645dc633.mp4
Pubkeys from this user's latest cached kind 3 follow list.
- No cached follows yet.
Cached pubkeys that follow this user, discovered from kind 3 events.
- No cached followers yet.
+------------------------------------------------------------------------------+
|
|
Identifiers
npub: npub1rhdu208t6vh03vswled09h65upr9ah9mlcz8lg9e67sdvk0aa6jq427zgk
hex: 1ddbc53cebd32ef8b20efe5af2df54e0465edcbbfe047fa0b9d7a0d659fdeea4
no cached metadata event yet
+------------------------------------------------------------------------------+
Suggested read/write relays from this user's latest kind 10002 event.
- No cached NIP-65 relay hints yet.