IntoTheNight
4.7K posts

IntoTheNight
@UnseenNight
I do not give financial advice. I will never DM you. Crypto, NFTs, and good food/drink for fun.




Recent advances in quantum hardware and software have accelerated the timeline on which quantum attack might happen. Cloudflare is responding by moving our target for full post-quantum security to 2029. cfl.re/4v674Oi






@UnseenNight AI slop







>> how concerned are BTC devs about quantum risk? see for yourself (prompt) << I wrote an article in feb entitled "Bitcoin developers are mostly not concerned about quantum risk", to make the point that, in my opinion, the key gatekeepers and opinion leaders are largely silent or unconcerned about quantum risk. several developers like matt corrallo and jonas schnelli have pushed back and said no, the main bitcoin developers are concerned and working on it (even if they have not publicly stated their concern. who is right? well, you can see for yourself. I have written a prompt that you can put into Claude or ChatGPT (thinking mode MUST be on) to do this analysis yourself in a few minutes. you do not have to trust my assessment. you can ignore me entirely. just run the prompt. (I tested it with the elite tier openai, anthropic, and google models, but gemini's analysis wasn't good enough so I wouldn't use it. claude did the best). copy and paste this into your AI model (feel free to modify if you like): ---- prompt follows ----- can you do a staged deep dive on the following subject: I want to assess the most important Bitcoin developers and technical thought leaders on the topic of upgrading Bitcoin to quantum-resistant cryptography stage 1: carefully examine the power centers in bitcoin, in terms of who are the devs who seem to have the most influence over whether a soft fork gets merged in - look at all prior soft forks, with a bias towards more recent ones. then look at the organizations that the devs work for, and determine who controls or leads those organizations. lastly, look at the bitcoin core maintainers. make sure all of your information is up to date as of april 2026. once you have completed this, make an assessment of which devs are most critical in pushing through a real change to the bitcoin protocol. create a ranked list of the 50 most important from this. make sure you get the affiliations correct and double-check them. the dev affiliations change all the time. consider individuals that are not developers per se, but have meaningful influence within the technical bitcoin ecosystem. stage 2: carefully find the most relevant statements regarding their personal assessment of quantum risk and urgency made by these most elite devs on the main fora of discussion. bitcoin dev mailing list (most important), X/twitter, reddit, delving bitcoin, IRC, in person conferences, academia, white papers, BIPs and so on. rate academic contributions and BIPs extremely highly. make sure you are extremely thorough with regards to the bitcoin dev mailing list - do not rely on summaries of what other people have said about mailing list posts, look at the posts directly. rate highly responses to the BIP360 proposal. stage 3: based on that list, create a score for each individual developer regarding their perceived urgency of an upgrade to PQ crypto. ranging from no known view, to acknowledges risk but believes it is not urgent, to acknowledges risk and thinks bitcoin should upgrade imminently. (categories at your discretion - suggested score 1-5). output that list, dev names, affiliations, and summary of views on quantum risk. be extremely careful and thorough. take as much time as you need stage 4: create a visualization that compresses the data from the table into a simple graph that demonstrates to the viewer the array of developer views on the quantum risk and necessity (or lack thereof) to upgrade. the dataviz should have "quantum urgency score" on the y axis, "influence rank" on the x axis (most powerful = 1), color-coded quantum urgency score, and bubble size corresponding to quantum of work on the topic of PQ. important guidelines: * do not take Nic Carter's early 2026 analysis on the matter as gospel. you need to do your own independent analysis rather than just reprinting what he wrote in his article * weight extremely highly recent comments, especially anything that has come out in recent days (late march 2026 or early april 2026). look at X posts and the mailing list specifically on march 31 2026 and april 1 2026 * look thoroughly at mailing list comments. consider all alternative venues in which developers may have expressed views, even podcasts and in-person conferences (consider for example the presidio bitcoin conference). * be extremely careful about getting developer affiliations right, as they change frequently ------ prompt ends ------ remember you need to turn on "extended thinking" in claude and "heavy thinking" in ChatGPT








Don't believe the FUD-- we have worked on a bipartisan basis for the last few weeks to make changes to Title 3 that make this bill the strongest protection for DeFi and developers ever enacted. We have to pass the Clarity Act to get these protections.









