@Saifedean Ammous shouldn’t the next book be « FIAT technologies » ? All those useless stuff developed with high time preference which were waste of resources (private and public). Amongst them the “good bad ideas” from the top , and the IP/licensing battles Throwaway razors and pens. 3D glasses AV1 Military stuff Large scale infrastructure like France’s EPR

NOSTR is a paradigm shift NOSTR decentralises content discovery user is sovereign and via his client he is in control of the algorithms (not google) he chooses what he sees, how he sees it and when he sees it Consent and control are everything

I see 3 main challenges for humanity 1/ how do we get out of all the slavery systems we have burdened ourselves with 2/ how do we prevent earth colonisation by one of the competing amoral alien races who seek our ressources and make us a colony (they tantalize our elites with futile tech) 3/ how does humanity finally grow wiser and get out of the current plateau Bitcoin is the path to 1/ and helps with 3/ a bit

This morning my brain is like my CPU running local LLM or generative AI: sucking all the ressources Just in order to reinvent how to present Bitcoin to businesses Getting there …

My sats stacking DCA method is rather strange : I let time pass by, if I am equally on more convinced I keep stacking.

Proof of work

We haven’t started to use Bitcoin yet if all we’ve done is take it off from exchanges ?

@fiatjaf @Mike Brock About #keyrotation issue, proposal: Let's have 2 npubs per profile. The master Npub is generated (preferably on airgapped seedsigner) and is the only one that is allowed to modify the master npub associated with the profile. The child npub is the one used for everyday signing and so on If/when the child npub is compromised simply publish a profile update with new master and child npub. optionnally stamp blockheight+UTC after which the user wants to signal compromission ideally the Nostr note publishing the new profile update should be QR coded from airgapped device I know it's not perfect but it makes it already that much harder to break until we are dependent on DNS we're kinda stuck even with DIDs... also we always forget about things like the proper nonces being used for signing messages etc.... we have no control over the client's source code and whether they are doxing or not

@fiatjaf @Mike Brock About #keyrotation issue, proposal: Let's have 2 npubs per profile. The master Npub is generated (preferably on airgapped seedsigner) and is the only one that is allowed to modify the master npub associated with the profile. The child npub is the one used for everyday signing and so on If/when the child npub is compromised simply publish a profile update with new master and child npub. optionnally stamp blockheight+UTC after which the user wants to signal compromission ideally the Nostr note publishing the new profile update should be QR coded from airgapped device I know it's not perfect but it makes it already that much harder to break until we are dependent on DNS we're kinda stuck even with DIDs... also we always forget about things like the proper nonces being used for signing messages etc.... we have no control over the client's source code and whether they are doxing or not

@fiatjaf @Mike Brock About #keyrotation issue, proposal: Let's have 2 npubs per profile. The master Npub is generated (preferably on airgapped seedsigner) and is the only one that is allowed to modify the master npub associated with the profile. The child npub is the one used for everyday signing and so on If/when the child npub is compromised simply publish a profile update with new master and child npub. optionnally stamp blockheight+UTC after which the user wants to signal compromission ideally the Nostr note publishing the new profile update should be QR coded from airgapped device I know it's not perfect but it makes it already that much harder to break until we are dependent on DNS we're kinda stuck even with DIDs... also we always forget about things like the proper nonces being used for signing messages etc.... we have no control over the client's source code and whether they are doxing or not

@fiatjaf @Mike Brock About #keyrotation issue, proposal: Let's have 2 npubs per profile. The master Npub is generated (preferably on airgapped seedsigner) and is the only one that is allowed to modify the master npub associated with the profile. The child npub is the one used for everyday signing and so on If/when the child npub is compromised simply publish a profile update with new master and child npub. optionnally stamp blockheight+UTC after which the user wants to signal compromission ideally the Nostr note publishing the new profile update should be QR coded from airgapped device I know it's not perfect but it makes it already that much harder to break until we are dependent on DNS we're kinda stuck even with DIDs... also we always forget about things like the proper nonces being used for signing messages etc.... we have no control over the client's source code and whether they are doxing or not

No such thing as private property exists in nature in my opinion. However Bitcoin gets you the closest to it but not exactly. As many chance to guess your seed as there are atoms in the universe. Still not “yours”