| | 1.1 Portfolio Director
07 Block Chain Service | | |
|---|
| 11.07 Block Chain Service: | | 1. Block Chain 2.0 technology exists in the public domain as peer-to-peer encrypted distributed database ledger software. Eliza-Chain 4.0 is a more advanced Artificial Intelligent Assistant that eliminates the need to distribute and install software. | | 2. The problems of peer-to-peer software is that different versions on different machines at different times will show different results. The benefit of Eliza is that no version of any software exists, so everybody shares the same view of the ledger when using any kind of device in any location. | | 3. Peer-to-peer block-chains grow in size over time causing delays and disruption as one peer tries to update all other peers. Eliza-Chain 4.0 simply eliminates any size concern by simply showing people a real-time view of the shared ledger while retaining the benefits of replicated encrypted data. | | 4. Eliza-Chain 4.0 is the result of many years of research to deploy the specific benefits needed by companies sharing ledger data. These business requirements are not the same as bitcoin where anonymous public people are a key issue. For any customer-supplier contract the parties know one another and exclude all other parties from sharing the contract ledger. |
| 2. Smart Contract Service: | | 1. With most customer-supplier contracts, the invoice-payment transactions form a shared private and confidential ledger. Both parties require the ledger to be replicated and encrypted to prevent the data from being lost or stolen. | | 2. Encryption is a shared requirement of both Block-Chain and Eliza-Chain to ensure that data cannot be stolen. Encryption also means that data sovereignty has no meaning and does not create a limitation on where data can be stored. | | 3. Replication is a common requirement, but while Block-Chain distributes a whole copy of the database to each party, Eliza-Chain distributes the database to a large number of physically secure data centers. Eliza-Chain simply removes the need for the parties to install and maintain local software to manage their local copy of the database. Eliza has a benefit that both parties may deploy many different people to view the same shared ledger using different computers at the same time. Block-Chain is oriented towards personal data on mobile devices such as digital currencies, music licenses and taxi services. |
| 3. Ledger: | | 1. A smart contract uses Eliza artificial intelligence to do most of the work, to maximise productivity and eliminate data entry errors. In general, only two transaction types are involved as (1) Invoice and (1) Payment. | | 2. Invoicing may be an agreed monthly fixed amount on an agreed (first) day-of-the-month or an ad-hoc (metered) amount on an ad-hoc date. Eliza will automatically manage all invoice creation for agreed amounts on an agreed date. Manual entry of (1) ad-hoc amounts on (2) ad-hoc dates will be required, but then Eliza will do all other processing. | | 3. Payments may be an agreed monthly standing order (or direct debit) on an agreed day-of-the-month or an ad-hoc amount on an ad-hoc date. Eliza will automatically manage all payment creation for agreed (standing order or direct debit) amounts on an agreed date. Manual entry of (1) ad-hoc amounts on (2) ad-hoc dates will be required, but then Eliza will do all other processing. | | 4. Notification may be automated with an email envelope with link to any number of email addresses provided by both parties. Whenever a change is made to the ledger with a new invoice or payment, any number of email notifications may be triggered. |
| 4. Statement: | | 1. An Eliza smart contract is viewed as a statement of invoice and payment transactions. Transactions may be viewed in reverse date order with the latest transaction at the top, or may be in date order from the oldest to the latest. Paging is needed when more than 16 transactions exist in a statement so a person can focus on the relevant data without being swamped with a view of all transactions that may go back ten years of more. | | 2. Each row in the statement represents an invoice or a payment. An invoice is treated as a positive credit to the balance and a payment is treated as a negative debit from the balance. This convention means the balance is zero or a positive amount that is due to be paid. | | 3. Click on a a selected statement row to show that specific invoice or payment document. Each document has a menu bar that enables the document to be downloaded as a PDF file, downloaded as a HTML file or printed. | | 4. Every statement includes a download button that grants both the customer and the supplier the right to have their own copy of the statement data. Statement data is downloaded without any encryption so any downloaded data may be lost or stolen from the persons local computer. |
| 5. What Did I Do: | | 1. Eliza automatically maintains an evidence trail showing every request made by every person who has the right to access a ledger. The evidence trail is encrypted and replicated to prevent any evidence from being lost or stolen. Evidence can be viewed but cannot be changed. | | 2. Evidence is shown in reverse date and time order with the latest request at the top. Paging is used to limit what is downloaded at any point in time. Filters may be applied to search by person, type of request, date, time and other criteria. |
| 6. Support Data: | | 1. The Eliza Ledger is supported by a number of associated blocks of data. Each ledger is associated with a list of approved people who have been granted access rights to view that ledger. Each approved person is associated with a list if computers and networks that they are authorised to use. | | 2. Pseudonymised data encryption is deployed with tokens to ensure that an encrypted statement cannot be decrypted by a criminal agency. Contract party names, terms and template documents are managed for each ledger. Diverse and multiple encryption methods are deployed, so if one encryption method is cracked, others will continue to provide the security needed. |
| 7. Fiscal Project Considerations: | | 1. An application service with one invoice and one payment per month will never be cost effective. Eliza-Chain 4.0 technology is advanced with complex encryption keys and expensive replication capabilities. Private and confidential data that is shared bewtween many people in more than one company carries overheads that go beyond intelectual property rights. | | 2. A new era of companies cooperating in efficient supply-chain partnerships is replacing companes that do everything internally regardless of efficiency. This new era of shared replicated encrypted data is replacing local company data silos where data did get lost and stolen. | | 3. Eliza-Block 4.0 does not exist to earn revenue in 2017, but as proof-of-concept for all the applications that will evolve to earn revenue in the next decade. |
| Document Control: | | 1. Document Title: Block Chain Service. | | 2. Reference: 161107. | | 3. Keywords: ITIL, Block Chain Service, Eliza Search. | | 4. Description: Block Chain 4.0 AI benefits without software. | | 5. Privacy: Public education service as a benefit to humanity. | | 6. Issued: 2 Apr 2017. | | 7. Edition: 1.0. |
Everything you do, say and write will be taken down and will be used against you, will be quoted out of context and will be sold to other parties. |
| Security vs Privacy: | | 1. For your security; every phone call is recorded, every email is copied, every web site you view is recorded, every search term you use is recorded, every vehicle movement is recorded, everything you say will be recorded, every.... | | 2. You may imply that your privacy is reduced as your community security has increased, but as your privacy decreases, your personal security decreases. | | 3. Security data can only be used against you and can never be used for a positive outcome. | | 4. Security data will eventually be used against you, even if it takes 20 or 40 years, you will be held to account for what was an inocent statement 20 years ago, but a cultural shift has changed its context. | | 5. Security data will record your every journey and every destination. | | 6. Security data will copy what and why you buy and sell goods. | | 7. Security data includes all your bank accounts and tax accounts - when you are in debt and when you have savings. | | 8. Security data when taken out of context or slightly modified over time will be used against you in the future because you cannot defend against security data. | | 9. Governments, Companies and People will discriminate against people who did, said or wrote something 20 years ago where cultural opinions have evolved to make such an activity not-nice. | | 0. Districts and Towns are being discriminated against by local and national Governments because of how the majority of people voted in the past - voting is a team game with the winner taking all. | | Privacy is your single most important issue that will be reduced by governments, reduced by companies and ignored by most people - just Ask Google. |
|
|