mopdf.com

another. Moreover, it will be appreciated that such a development effort might be complexand time-consuming, but would nevertheless be a routine undertaking of engineering forthose of ordinary skill in the art having the benefit of this disclosure.Figure 1 is block diagram of one embodiment of an integrated ecosystem 100 offinancial services utilizing blockchain technology. The integrated ecosystem 100 may beimplemented on a host system and a network of devices. The host system can include ahost processor, a host database, and a non-transitory computer-readable mediumcomprising code, executable by the host processor. It is understood that the integratedecosystem and host system can include additional systems, subsystems and elementsthan those specifically shown and/or described herein. Additionally, or alternatively, theecosystem and host system can omit one or more of the systems, subsystems andelements that are specifically shown and/or described herein.As illustrated in Figure 1, the integrated ecosystem 100 may include a marketplaceclient 102, an electronic exchange client 104, and an agent portal 106. The ecosystemmay further include an authentication element 108 that can be commonly shared betweeneach subsystem of the integrated ecosystem 100.In one embodiment, the authentication element 108 may include encryption,firewalls, user passwords, and two-factor authentication such as Google Authenticator .If the user successfully meets the requirements of the authentication element 108, theuser will have access to the remainder of the elements of the system or subsystem towhich the authentication element 108 is connected. The authentication element 108 canalso integrate Firebase Authentication which uses an internally modified version ofscript to hash account passwords. The authentication element 108 can be multipleelements as shown in Figure 1 as three elements, 108A, 108B, 108C. Alternatively theauthentication element 108 can be one singular element connected to all of the otherelements in the integrated ecosystem 100. Still alternatively, the authentication element108 can be connected to less than all of the other elements in integrated ecosystem 100and authentication element 108 may only be connected to one other element. Theauthentication element 108 can include other elements, systems, subsystems,functionalities and modalities not specifically shown and/or described herein.In another embodiment, the marketplace client 102 can be a user interface on an6

electronic device. The marketplace client 102 may include functionality including assetcategories, user settings and/or options, product lists, product purchase options, productmulti-media galleries, integrated origin and/or title assurance, and integrated point-of-saleor digital wallet systems. After a user satisfies the authentication element 108, the userwill have access to the entirety of the marketplace client 102. The marketplace client 102can include other elements, systems, subsystems, functionalities and modalities notspecifically shown and/or described herein.In some embodiments, the electronic exchange client 104 may be a user interfaceon an electronic device. After a user satisfies the authentication element 108, the userwill have access to the entirety of the electronic exchange client 104. The electronicexchange client 104 allows a user to create representation equity tokens for a wide varietyof mixed assets types. The mixed asset types, as a non-exclusive example can includeautomobiles, stocks, bonds, business ownership interests, collectibles, digital assets(such as cryptocurrencies), and/or real estate. The representative equity tokens, asblockchain-verified tokens, are proof of ownership of the underlying mixed asset typeswithin the representative equity tokens. The electronic exchange client 104 may alsoallow a user to define the underlying assets and determine the weighting of assets in theportfolio similar to an exchange-traded fund (“ETF”) product. The electronic exchangeclient 104 can also allow the token creator to determine the total quantity and/or initialsupply of issued tokens. The electronic exchange client 104 can include other elements,systems, subsystems, functionalities and modalities not specifically shown and/ordescribed herein.In one embodiments, the agent portal 106 can be a user interface on an electronicdevice. The agent portal 106 can facilitate consumer blockchain transactions that will behandled by registered agents. After an approved partner or brand satisfies theauthentication element 108, the agent portal 106 allows the approved partner or brand toupload product details, assured title, or origin information to the blockchain. Customersof the approved partner or brand can verify the origin authenticity by scanning a product’sQR code with an integrated digital wallet system. The agent portal 106 can include otherelements, systems, subsystems, functionalities and modalities not specifically shownand/or described herein.7

In other embodiments, the integrated ecosystem 100 can further include anapplication programming interface (API) 110. The application programming interface(API) 110 can include a set of functions and procedures that allow the creation of newapplications that access the features, data or applications of the integrated ecosystem100 and its various subsystems. One non-exclusive, non-limiting example of applicationprogramming interface (API) 110 may include user-added web addresses for real-timepricing data within the electronic exchange client 104. The application programminginterface (API) 110 may also include support for older or legacy APIs for integration withlegacy systems. Modern APIs can also be supported within the application programminginterface (API) 110 and may include web or https as non-exclusive, non-limitingexamples. The application programming interface (API) 110 can have multiple elementsas shown in Figure 1 as three elements, 110A, 110B, 110C. Alternatively the applicationprogramming interface (API) 110 can be one singular element connected to all of theother elements in the integrated ecosystem 100. Still alternatively, the applicationprogramming interface (API) 110 can be connected to less than all of the other elementsin integrated ecosystem 100 and the application programming interface (API) 110 mayonly be connected to one other element. The application programming interface (API)110 can include other elements, systems, subsystems, functionalities and modalities notspecifically shown and/or described herein.In various embodiments, the integrated ecosystem 100 can further include adatabase 112. The database 112 may be the host database on the host system asprevious described. The database 112 can also be a single computer, a cluster ofcomputers, a large mainframe, a minicomputer clusters, a group of servers functioning asa single unit, or a server coupled to a web server. The database 112 may also include ablockchain ledger of the current value of blockchain verified assets. In one embodiment,every element within the integrated ecosystem 100 may need to access the database112. Alternatively, less than every element within the integrated ecosystem 100 mayneed to access the database 112. The database 112 can be multiple databases as shownin Figure 1 as three databases 112A, 112B, and 112C. Alternatively, the database 112can be one singular database connected to all of the other elements in the integratedecosystem 100. Still alternatively, the database 112 can be connected to less than all of8

the other elements in integrated ecosystem 100 and the database 112 may only beconnected to one other element. The database 112 can include other elements, systems,subsystems, functionalities and modalities not specifically shown and/or describedherein.Sometimes, the integrated ecosystem 100 may also include deployable smartcontracts 114. A smart contract may control the execution of a transaction digitally byrecording the terms of the transaction on the blockchain. Smart contracts may function asa trusted distributed application that gains its security/trust from the blockchain and theunderlying consensus among peers. A smart contract may include data which is signedand has consensus associated with validation among nodes in the blockchain. Thisprevents the smart contract from being repudiated. In one embodiment, every elementwithin the integrated ecosystem 100 may need a deployable smart contract 114.Alternatively, the integrated ecosystem 100 may need only one deployable smart contract114. There can be two deployable smart contracts as shown in Figure 1 114A and 114B.The deployable smart contract 114 can include other elements, systems, subsystems,functionalities and modalities not specifically shown and/or described herein.One non-exclusive, non-limiting example including the use of deployable smartcontracts 114 is within the electronic exchange client 104. In this non-exclusive, nonlimiting example, a user can complete a form describing the deployable smart contract114 including details such as the token trading symbol, the token name, and initial supply.The deployable smart contract 114 may include a serial number of a digital currency heldon a blockchain.In other embodiments, the user may also define assets for the deployable smartcontract 114 to track. When all of the requisite information is provided to the deployablesmart contract 114, the deployable smart contract 114 can be deployed to a blockchain.In some embodiments, when the deployable smart contract 114 is tokenized by the blockchain, the token owner’s address can be transferred to a third-party financial exchangeto facilitate trade, investment and token/asset liquidity.In one embodiment, the token owner may edit contract details after the deployablesmart contract 114 is already deployed to the blockchain. In another embodiment, thedeployable smart contract 114 can assist with price discovery, liquidity arbitrage,9

rebalancing, utilizing oracle API functionality, or other built-in call to popular pricing APIs.In various embodiments, title assurance 116A is another non-exclusive, nonlimiting example system that may be included in the integrated ecosystem 100.Ownership of a piece of land can be verified using the title assurance 116A system. Inthe title assurance 116A system, a buyer, a seller, a buyer’s bank, a seller’s bank, ablockchain record, and a current title / land registry can be integrated into the titleassurance 116A system to verify and record title to a piece of real property. The data canbe handed within the title assurance 116A system in a similar manner as the originassurance system described above. Hashes can be made for the data stored in thedatabase 112. Hash data may be stored on the blockchain for future verification ofdocuments.In one embodiment of the title assurance 116A system, a buyer can receive a titledeed from a seller, the buyer can send payment to a verification company, the buyer mayenter the seller’s details and title deed details into the system, a company can returnownership details from the database 112, the blockchain and the title/land registry, andthe buyer may confirm the seller’s ownership of the property as valid or invalid. The sellercan pay a verification company to upload property ownership details, the title deed canbe recorded in the database 112, the blockchain and can be checked with title/landregistry or the verification company stores the data on behalf of the title/land registry, andthe seller’s title deed can be verified as being valid and that the seller is the verified owner.In another embodiment of the title assurance 116A system, an agent can login orregister to use the title assurance 116A system, the agent can upload the asset title andassociated ownership data, the agent can query the national or local land/home/assetregistry, if the ownership data is invalid, a prompt warning of invalid data may be provided,if the ownership data is valid the valid data can be added to the blockchain with acryptographic signature. A public user may also get access to the title assurance 116Asystem. The public user can query the blockchain, the public user can parse theblockchain asset title data, the public user can compare the blockchain asset title data tothe official records blockchain data and cryptography, if the data does not match a promptvalidation warning can be provided, if the data matches, a prompt valid ownershipmessage is provided.10

Sometimes, the integrated ecosystem 100 may also include origin assurance116B. A goods or product owner can be verified and approved for access to the originassurance system in order to verify the origin of the goods or product. The good or productowner may be able to provide details for verification by the origin assurance 116B system.After the details are provided, the data of the goods or product may be cryptographicallyhashed, signed and placed onto a blockchain. Similarly, the same data of the goods orproduct may be stored on the database 112. The origin assurance 116B system cangenerate a detailed URL and a QR code to place on the goods or product packaging. TheQR code can be scanned to access the detail page on the web. The blockchain data mayalso be parsed and can be verified against the stored data in the database 112 when thedetail page on the web is accessed. The web data may be verified if it matches the datathat was originally placed and signed on the blockchain.In various embodiments, the integrated ecosystem 100 can further include a tokenengine 118. The agent may help an asset owner create a tokenized security asset orequity asset. The tokens may represent a whole or fractional ownership in an asset issuedon the blockchain in digital tokens. The asset and equity can be defined on the tokenengine 118. The token details can be defined on the token engine 118. The tokens canbe issued onto the blockchain using a deployable smart contract. The token engine 118can generate new smart contract tokens based on the defined token attributes. The newlyissued smart contract’s blockchain address may be recorded in the database 112. Theissued tokens may be digitally transferred to the asset owner’s pre-determined assetreceiving address. The owner may also send the tokens to any other investors’ digitalasset receiving addresses. The owner can also send tokens to an exchange ormarketplace to facilitate liquidity for the asset. The token engine 118 can include otherelements, systems, subsystems, functionalities and modalities not specifically shownand/or described herein.In one embodiment, the integrated ecosystem 100 can further include amarketplace API 120. The marketplace API can facilitate the tracking of issued andpurchased assets within the integrated ecosystem 100. A user can issue, transfer, and/orview assets by utilizing the marketplace API 120. The marketplace API 120 can includeother elements, systems, subsystems, functionalities and modalities not specifically11

shown and/or described herein.Sometimes, a cloud storage 122 can be implemented within the integratedecosystem 100. The cloud storage may provide storage of and access to data objectsthat can also be stored on the database 112. Generally, uploading, access andmanipulation of data stored on a cloud storage 122 is conducted via an HTTP, FTP orsimilar network connection. Cloud storage 122 service providers include those serviceprovides known to those having ordinary skill in the art. The cloud storage 122 can includeother elements, systems, subsystems, functionalities and modalities not specificallyshown and/or described herein.Figure 2 is a flow chart depicting one embodiment of a method for authenticatingthe origin of property of a seller, which can include one or more of the following steps. Itis understood that the method can include additional steps than those specifically shownand/or described herein. Additionally or alternatively, the method can omit one or moreof the steps that are specifically shown and/or described herein.The method forauthenticating the origin of property of a seller can be implemented on integratedecosystem 100, or other systems and subsystems not specifically shown and/ordescribed herein.At step 224, a user (typically a potential seller) of the system can upload data intoa host database of a host system. The host system can be the integrated ecosystem 100or other systems and subsystems not specifically shown and/or described herein. Thehost database may be database 112, cloud storage 122 or another database, data server,cluster of servers, or cloud server system not specifically shown and/or described herein.The data includes information regarding the property to be sold or offered for sale. Thedata can include one or more of the type of property (i.e. personal or real), the specificsof the property, location of the property, etc., as non-exclusive examples. A cryptographicprivate key is generated by the host system from the data that is uploaded (input) in thehost system. The cryptographic private key may be associated with a digital wallet or achip on a smart card or a secure element of a user device. The cryptographic private keymay also be kept secret and may be used to digitally sign messages sent to other users.At step 226, a cryptographic public key is generated by the host system from theprivate key. The cryptographic public key may also be associated with a digital wallet.12

The cryptographic public key may serve as an address to receive signed message fromother users.At step 228, a first data object is structured with the private key and the public key.The first data object is structured for hashing. The user data uploaded onto the hostsystem, the cryptographic private key, and the cryptographic public key may be bundledto together in the structure for hashing.At step 230, the first data object is cryptographically hashed into a first hash on thehost database of the host system. A hash can be generated from data of arbitrary size(e.g., a string of text). The hash may be, for example, a numerical or string value. Thehash may be significantly smaller than the data itself. A hash may be generated by afunction such that it is extremely unlikely that some other data will produce the same hashvalue, and it is extremely difficult to reconstruct the data based on the hash value.At step 232, the first hash is inserted into a blockchain. The blockchain may be ina digital ledger that is on many computing devices. The transactions may be recorded ona set of blocks. Each block may contain a hash of one or more previous blocks.Accordingly, the record of each transaction cannot be altered retroactively without thealteration of all subsequent blocks and the collusion of the network. The first hash can beunique and may be used to verify the data from the first data object has not been changedor manipulated.At step 234, a signed message is generated from the first hash.At step 236, a second hash is generated from the signed message. The secondhash may be in the form of a cryptographic signature.At step 238, the second hash is signed with the private key.At step 240, the first hash is verified by comparing the public key and the signedsecond hash. The authenticity of the message be verified using the public key and thesigned second hash by matching the content of the first hash to the second hash.At step 242, a second data object is generated that includes one or more of thedata from host database, the first data object, the first hash and the second hash. Thesecond data object may include an address, the cryptographic private key, an imageURL,the first data object, the first hash, and/or the second hash.At step 244, the first hash is verified on the blockchain.13

At step 246, the first hash is recreated to confirm consistency between the firsthash on the host database and the first hash on the blockchain. The first hash may beadded to the blockchain while simultaneously adding the updated data from the seconddata object to the database. After the first hash is added to the blockchain, the block

In certain embodiments, the host system can be configured to transfer the smart contract token to a third-party financial exch