Will You Be Required To Use Crypto Currency By The Federal Reserve Known As “Project Hamilton”? Consequences Noted Here!

For those who do not wish to read the below documentation or comments, here is a brief synopsis:

1.) You will lose privacy (History of all purchases and vendors) 2.) You will lose freedom. (Buy approved products from approved vendors and no unapproved giving to political efforts, churches and charities) 3.) You will likely have no convenient recourse for hacking or mistakes. 4.) You will be controlled remotely (limited service areas including vehicle range) 5.) You will likely not be able to save – money with an expiration! 6.) It could get complicated for non-techie people – frequent updates. 7.) Breakdowns and failures making transactions impossible. (Hacking) It is well known that wealthy and powerful interests hate the church, GOD, Christ, Christians and the Bible, and are actively trying to eliminate it/us! We’ve already seen the credit card companies (banksters) shut down politically incorrect conservative causes and purchases of guns and ammo to name a few! In Canada, they shut down protesting trucker’s bank accounts! Churches are definitely on the horizon! All we need is another like Biden in the White House, and we’re done for!

The following are this writer’s excerpts from the Fed document with commentary:

…”This paper presents the project’s Phase 1 research. Our primary goal was to design a core transaction processor that meets the robust speed, throughput, and fault tolerance requirements of a large retail payment system. Our secondary goal was to create a flexible platform for collaboration, data gathering, comparison with multiple architectures, and other future research. With this intent, we are releasing all software from our research publicly under the MIT open source license. (Editor’s questions – “collaboration” with whom?; “data gathering” – whose data and for what purpose and shared or stored by or whith whom?)

….”baseline requirements include time to finality of less than five seconds, throughput of greater than 100,000 transactions per second, and wide-scale geographic fault tolerance. Topics left to Phase 2 include critical questions around high-security issuance, systemwide auditability, programmability, how to balance privacy with compliance (Editor’s note – “compliance” with what?), technical roles for intermediaries, and resilience to denial of service attacks.”

…”The second idea is a transaction format and protocol that is secure and provides flexibility for potential functionality like self-custody and future programmability.” (Editor’s comment – how will they program, and what will they program?)

“…users cannot custody their own funds,…” (Editor’s question – what does this mean?)

“…architecture can support many future designs for programmability…” (Editor’s comment – there we go again with programmability)

“…Project Hamilton’s approach, which assumes that the platform would be administered by a central actor.” (Editor’s question – who might that “central actor” be, and how do we know we can trust them? Remember, digital currency may be controlled remotely with a key stroke or algorithms, and you cannot hold it in your hand like cash or precious metals!)

“…architecture has downsides. For example, it creates performance bottlenecks…” (Editor’s note: “bottlenecks”? If there’s only one central actor, who ya gonna call? Ghost Busters?)

By breaking transaction processing into steps like creation, authorization, submission, execution, and storing history, CBDC designers can consider the potential roles for intermediaries at each stage, creating opportunities for innovation. (Editor’s observations and questions; “authorization” will be required implying that authorization can be denied – i.e. guns, ammo, church tithes, charitable giving, political objectives, medicine, food, gasoline, automobile purchases etc., and “storing history” means you’re on a watch list.)

By implementing a robust system, we identify new questions for CBDC designers and policymakers to address, regarding tradeoffs in performance, auditability, functionality, and privacy. (Editor’s comment – “tradeoffs” is a weasle word for manipulating the service to suit the “central actor” and not you the consumer/citizen. There will be NO ACCOUNTABILITY – NOT EVEN CONGRESS)

In depth history of banking HERE, and video documentary All Wars Are Bankers Wars (8.8 IMDb rating!) Excerpted below from the in depth history is a striking comment:

“These systems introduce a new phase: one where algorithmic governance, ESG (Environmental, Social, & Governance) compliance, and real-time surveillance form the substrate of global economic life. The future triad will not just enforce policy. It will predict, score, and condition it — automating obedience in the name of ethics and sustainability.”

The bottom line is the loss of three things – freedom, privacy and ultimately even the convenience they promise! Don’t let the banksTers win!