DJ: DID YOU KNOW? What a GCR would actually look like?
DJ: DID YOU KNOW?
What a GCR would actually look like
For the sake of argument, let’s say a GCR has occurred. What would that look like? Taking into consideration all the elements the ongoing narratives have spewed for years, are implemented.
QFS is operational, asset holders, both currencies and bonds, have been notified with instructions on how to proceed and funds are being distributed. How would the funds actually move through the financial system? How will you be notified? What would actually happen to economies and the world, when it occurs?
Traditional computers use “bits”. A bit (binary digit) is the smallest unit of data that a computer can process and store. A “bit” is always in one of two states, (like an on/off light switch). The “state” is represented by a single binary value, usually a 0 or 1. The “state” might also be represented by yes/no , on/off or true/false. Quantum computers use “qubits” (quantum bits), which can exist as 0 , 1, or both at the same time , allowing unlimited data, that lies between the 0 and the 1, to process and store. Meaning information moves a lot faster than traditional computing.
So money is available and is moving . Reputedly through the QFS. The only ones who actually have quantum computers are the major banks at the top of the food chain. They hold the money to be distributed!. But they have to move the money down the food chain through traditional computers, so the average person can access the funds at their local bank.
Converting quantum information into a classical format has its own set of difficulties. Quantum systems are inherently delicate, often struggling with information loss, a problem classical systems generally don’t have.To convert the qubits ( That hold vast amounts of bits) into bits ( that are 1’s and O’s, true/false, yes/no or on/off stored data) each qubit has to transfer the store data (which could be millions of bits) into smaller pieces of data that a legacy system can process, this is where data can quickly become chaotic, limiting memory efficiency or losing the data.
Think of it like this. You have a bucket full of water. If you put a hole in the bucket, the water will leak out. If the flow of water you keep putting back in the bucket matches the amount leaving the bucket, the water level will stay the same. But if the flow going back in the buck is more than what is leaking out, the bucket will overflow. If too much data is being sent at once (Q-bits) the receiving computer can’t process fast enough to absorb the influx of data, leading to a loss of coherent data.
So even if the funds are sitting in the banks ready for distribution, it will come out only as fast as the receiving institutions can receive and process the deposit. What has been suggested is that when anyone is paid they will receive 1% at first followed by another 10% a week later, then a multiple month or year pay schedule for the balance.
If you are one of those who is going to be notified, how do they have the information on you for you to be notified?
You will have to have submitted your assets through some channel that logged your information to an end buyer or redeemer. You can’t be notified by an email, way too unsecured and hackable. So it will have to be by courier. When funds do start coming out the large asset holders will get paid first. It makes sense that they would distribute as much as they can with the least amount of effort.
The more you have the sooner you may get paid. How much you have will dictate your place in line. Those who have not registered their assets will most likely have to turn them in and wait. The funds entering the economies will also have to come in slowly so as not to cause economic chaos. You’ll have to allow time for economies to adjust.
There are 5000 pieces to this puzzle. And 5000 people hold one piece of the puzzle each. All waiting for their time to put their piece in. I wouldn’t count on all 5000 showing up and wanting to put their piece in all at the same time. Just think of that chaos.
DJ