Wednesday, February 14, 2018

The sandbox is making it universally available

Russian Deputy PM: Our Banks Are Ready To Turn Off SWIFT

To the escrow router, SWIFT looks like another queued ledger service.  If any protocol is validated to use it, then the router allows it.

So, if the SWIFT notaries want to restrict usage by national sanction, they must do it on a personal contract basis.  The SWIFT notary will require the thumbprints to verify a digital nationality, or the notary must distribute a banned thumbprint exclusion list. These are the only methods for national sanctions. 

The sandbox has no standard for a digital nationality, no enforceable one and it is not a monetary issue. The  auto network network maintains no product lists, much less nationalities on thumbprints.

So the SWIFT notaries have to get everyone to agree to some digital nationality standard, enforceable, and kick the sanctions up a layer.

Or, the SWIFT notaries will need to do shoe leather first, and identify the thumb print exclusion list.  The central banker and government sanctionizers are learning this as we speak.

If the SWIFT notaries fail to cooperate, they fail to deliver a valid contract for qualification, then the sandbox defaults to the basic contract, the user must supply all the proper codewords for robotic operation.  

The code words are held in the pipeline, masked from view by controlling the kernel thread, and stable state are verifiable with internal calls to external calls to the escrow notary system, the escrow miners on duty.

Or the user can use a ready sandbox format like stablecoin, if the central banks cooperate.

No comments: