WO2020018939A9

WO2020018939A9 - Distributed ledger-based property-listing system

Info

Publication number: WO2020018939A9
Application number: PCT/US2019/042656
Authority: WO
Inventors: Alexander SHEYNER; Oleg A. Vyadro
Original assignee: Lyste Corporation
Priority date: 2018-07-19
Filing date: 2019-07-19
Publication date: 2020-09-17
Also published as: WO2020018939A1

Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, employing a permissioned distributed ledger to store transaction data within a property-listing system. In one aspect, a method includes receiving, from an owner, a request to transfer listing rights for a property to a broker; generating a smart contract assigning a broker option for the property to the broker, wherein the smart contract includes information to facilitate a listing process and a sales process for the property; persisting the smart contract to an operational data store; generating an event record for the property, wherein the event record includes property data and a reference to the smart contract; and persisting the event record to an real-estate data store, wherein the real-estate data store provides a single source of property assets.

Description

DISTRIBUTED LEDGER-BASED PROPERTY-LISTING SYSTEM

BACKGROUND

[0001] The right to sell a real estate property is a highly valuable and sought-after right for a real estate broker. This right can be granted contractually by a property owner to a real estate broker through the execution of a listing agreement after a decision to sell has been made. Moreover, the right to market a property is a distinct, asset that exists throughout the duration of property ownership.

SUMMARY

[0002] Implementations of the present disclosure are generally directed to a system that enables property owner to formalize, securely record, manage, assign, and monetize their “rights-to-sell” through smart contracts, at any point of property ownership. The system also standardizes the way to reference and identify a real-estate asset, such as an apartment, a piece of land, a building, and so forth. Contract conditions programmatically implemented through the smart contract can be triggered automatically based on the occurrence of a triggering event.

[0003] In a general implementation, systems, apparatus, and methods for receiving, from an owner, a request to transfer listing rights for a property to a broker. A smart contract assigning a broker option for the property to the broker is generated. The smart contract includes information to facilitate a listing process and a sales process for the property. The smart contract is persisted to an operational data store (ODS). An event record for the property is generated. The event record includes property data and a reference to the smart contract. The event record is persisted to a real-estate (RE) data store. The RE data store provides a single source of property assets.

[0004] In another general implementation, one or more non-transitory computer-readable storage media coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations that include: receiving, from an owner, a request to transfer listing rights for a property to a broker. A smart contract assigning a broker option for the property to the broker is generated. The smart contract includes information to facilitate a listing process and a sales process for the property. The smart contract is persisted to an operational data store (ODS). An event record for the property is generated. The event record includes property data and a reference to the smart contract. The event record is persisted to a real- estate (RE) data store. The RE data store provides a single source of property assets. [0005] In yet another general implementation, a system includes one or more processors; and a computer-readable storage device coupled to the one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations that include: receiving, from an owner, a request to transfer listing rights for a property to a broker. A smart contract assigning a broker option for the property to the broker is generated. The smart contract includes information to facilitate a listing process and a sales process for the property. The smart contract is persisted to an operational data store (ODS). An event record for the property is generated. The event record includes property data and a reference to the smart contract.

The event record is persisted to a real-estate (RE) data store. The RE data store provides a single source of property assets.

[0006] An aspect combinable with the general implementations, the key value pairs include date and time of the latest version of an application.

[0007] In an aspect combinable with any of the previous aspects, the ODS and the RE data store are implemented through blockchain technology.

[0008] In an aspect combinable with any of the previous aspects, the operations or method include before receiving the request to transfer listing rights, receiving, from a trusted source or a system of record, a record for the property.

[0009] In an aspect combinable with any of the previous aspects, the record is stored in a block on the RE data store, wherein the block includes records for other properties, and wherein each of the records is received from the respective trusted source or system of record for each of the other properties.

[0010] In an aspect combinable with any of the previous aspects, the received records are updated based on load data received incrementally for each of the respective trusted source or system of record.

[0011] In an aspect combinable with any of the previous aspects, the operations or method include before receiving the request to transfer listing rights, receiving validation data from the owner; verifying ownership of the property by the owner based on the validation data; persisting an initial owner-broker smart contract to the ODS; and persisting the verified ownership of the property by the owner to the RE data store, through a link to the initial owner-broker smart contract on the ODS.

[0012] In an aspect combinable with any of the previous aspects, the validation data includes a photo of a license, a passport, mortgage statement, or utility bill for the owner that includes address information matching the property. [0013] In an aspect combinable with any of the previous aspects, the validation data includes information obtained through a credit check.

[0014] In an aspect combinable with any of the previous aspects, the smart contract includes a value assigned to the property for the broker option, wherein the value is set by the broker.

[0015] In an aspect combinable with any of the previous aspects, the value include cash value and an escrow value.

[0016] In an aspect combinable with any of the previous aspects, the smart contract include a horizon that sets an expiration date of the broker option when the property is not sold within an allotted timeframe.

[0017] In an aspect combinable with any of the previous aspects, the operations or method include generating a property listing smart contract for a property listing of the property by the broker, wherein the property listing smart contract includes a reference to the smart contract that includes the broker option; and persisting the property listing smart contract to the ODS.

[0018] In an aspect combinable with any of the previous aspects, the request to transfer listing rights for a property to a broker is based on an auction for broker services.

[0019] Particular implementations of the subject matter described in this disclosure can be implemented so as to realize one or more of the following advantages. The described system creates a global repository of assets registered via a common consortium blockchain. The system provides homeowners with that ability to register and sell owned property -listing rights. Contractual obligations between parties (e.g., homeowners, brokers, and investors) are managed through smart contracts. These smart contracts encapsulate listing rights and associated investments by brokers and investors through an internal (private) blockchain. The system also employs these smart contracts to link unique assets between these distinct but correlated blockchains.

[0020] It is appreciated that methods in accordance with the present disclosure can include any combination of the aspects and features described herein. That is, methods in accordance with the present disclosure are not limited to the combinations of aspects and features specifically described herein, but also may include any combination of the aspects and features provided.

[0021] The details of one or more implementations of the present disclosure are set forth in the accompanying drawings and the description below. Other features and advantages of the present disclosure will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

[0022] FIG. 1 depicts an example environment that can be employed to execute implementations of the present disclosure.

[0023] FIGS. 2A and 2B depict an example architecture of a property-listing system according to implementations of the present disclosure.

[0024] FIG. 3 depicts platform events that are persisted and reference by records on the RE consortium blockchain.

[0025] FIG. 4 depicts RE consortium blockchain events according to implementations of the present disclosure.

[0026] FIG. 5A-5B depict examples of ODS private blockchain events according to implementations of the present disclosure.

[0027] FIGS. 6A-6C depict the various contract types within a property -listing system according to implementations of the present disclosure.

[0028] FIGS. 7A-7B depict example contract lifecycles according to implementations of the present disclosure.

[0029] FIG. 8 depicts a flow diagram of an example process according to implementations of the present disclosure.

[0030] FIG. 9 depicts a block diagram of an exemplary computer system that can be employed to execute implementations of the present disclosure.

DETAILED DESCRIPTION

[0031] Implementations of the present disclosure are generally directed to a distributed ledger based property-listing system. More particularly, implementations of the present disclosure are directed to a system that applies Big Data, machine learning and artificial intelligence (AI) to manage property-listing rights. For example, the described system enables property owner to formalize, securely record, manage, assign, and monetize their“rights-to- sell” through smart contracts, at any point of property ownership. These smart contracts programmatically implement terms of a contact and may be persisted to, for example, a distributed ledger. The system standardizes the way to reference and identify a real-estate asset, such as an apartment, a piece of land, a building, and so forth.

[0032] The described system may also serve as an auction based marketplace that allows a broker to value a future listing right and secure it in the present. For example, brokers may compete to secure property-listing rights from property owners. Furthermore, the property- listing system may serve as an investor marketplace where brokers can acquire outside smart- contract-based funding to, for example, build their book-of business.

[0033] Implementations of the present disclosure provide for a property-listing system that employs a distributed ledger. An example distributed ledger is the commonly known Blockchain (or blockchain). Blockchain is referenced within the present disclosure for purposes of illustration. It is contemplated, however, that any appropriate distributed ledger can be used in implementations of the present disclosure. A blockchain is a continuously growing list of records or blocks that are linked and secured using cryptography. Each block with the blockchain may include transaction data provided from transactions that have been executed in one or more contexts, such as negotiable instrument transactions, digital currency transactions, and so forth. In some examples, a single block may include transaction data provided from multiple transactions (e.g., multiple deposits of different checks by different people). A blockchain may grow as completed blocks are added with a new set of transactions thus forming a (e.g., public) ledger of the transaction. Each block may include a hash pointer to a previous block and a timestamp along with the transaction data in a permanent manner.

[0034] In some implementations, the blocks of a blockchain are hashed and encoded into a Merkle tree (e.g., the blocks are leaf nodes of a Merkle tree). A Merkle tree (or hash-based tree) is a hash-based data structure that is a generalization of a hash list. A Merkle tree includes a tree structure in which each leaf node is a result of a CHF applied to a block of data to generate a hash value or“hash.” Example CHF include the Secure-Hash Algorithm 256 (SHA-256), SHA-3, and Message Digest 5 (MD5), among others. In general, the CHF receives information as input, and provides a hash value as output. The hash value can be a predetermined length. For example, SHA-256 outputs a 256-bit (32-byte, 64-character) hash value. In some examples, the hash value is a one-way hash value, in that the hash value cannot be‘un-hashed’ to determine what the input was. Additionally, a Merkle tree may be implemented as a k-ary tree, which is a rooted tree data structure in which each node has no more than k children. For example, a Merkle tree may be implemented as binary tree where each node may have 0, 1, or 2 children. The Merkle root (or root hash) of such a binary tree can be generated by repeatedly hashing each pair of nodes until only one hash is left.

[0035] The use of a blockchain within the described a property-listing system provides both transparency and auditability of transaction data to establish trust between participants. As described above, the blockchain employed by the system is secured by a cryptography and is inherently immutable. The system provides for security and verifiability of transactional data generated by employing such described features of the blockchain.

[0036] In some implementations, smart contracts (or self-executing contracts) may be stored on the blockchain. Smart contracts may include executable code that represents contract terms. As such, a smart contract not only defines the rules and penalties related to an agreement in the same way that a traditional contract does, but also automatically enforces those obligations. In some implementations, a smart contract may accomplish this by taking information as input, assigning a value to that input through the rules set out in the contract, and executing the actions required by those contractual clauses. For example, the smart contract may determine whether an asset should be sent to a destination entity or whether it should be returned to an originating entity.

[0037] Smart contacts may be coded in a programming language, such as Solidity™. In this format, contracts could be converted to computer code, stored and replicated on the system, and supervised by a network of computers that run the blockchain. In an example context employing the described property-listing system, once a contract is finalized between a broker and a property owner, a smart contract is created and stored to the permissioned blockchain. The stored smart contract is immutable and may be executed automatically when a condition is met (e.g. the arrival of property data) in real-time. For example, a smart contract may be programed to deliver payment from an investor pool to a broker’s account. Other examples of smart contracts that may be employed in the described property-listing system provide for value exchanges between brokers and investors. For example, an investor may provide a pool of tokens under specific terms (e.g. , duration, flat fee, geography, percent of income, and so forth). Brokers may‘bid’ for these pools of tokens through an auction service. Once an agreement is reached, the terms are codified via smart contracts persisted to an ODS private blockchain. Another example of the use of smart contracts with the describe system includes integration with a broker’s book-of-business. Such a book-of-business provides information as to the funds that were used to purchase listing rights (e.g., from which investor pool(s) the funds originated). In such examples, smart contracts can be employed to provide the investor with ‘return tokens’ based on the terms of the contract between the broker and investor.

[0038] As used herein, the term“real-time” refers to transmitting or processing data without intentional delay given the processing limitations of a system, the time required to accurately obtain data and images, and the rate of change of the data and images. In some examples, “real-time” is used to describe the presentation of information obtained from components of a distributed-ledger based system, such as depicted in FIGS. 1-12. [0039] In some implementations, property information can be received and registered on a consortium blockchain (e.g., RE blockchain). For example, regular data feeds (daily/weekly) can be processed to identify changes in ownership and updates that can be applied to keep the information on the RE consortium blockchain current.

[0040] The described property-listing system can be employed to ensure compliance with local, federal, and international guidelines, such as Know Your Customer (KYC) and Anti- Money Laundering (AML) regulations. Each marketplace participant, such as property owners, brokers, and investors, may register and provide the necessary documentation required for minimum compliance. For example, after aKYC compliance process (e.g., a short message service (SMS) message, upload of license with current address, and so forth), a property owner can‘claim’ property before participating in marketplace auctions. In some implementations, property owners can provide financial institution information (e.g., routing number, account numbers, debit/credit card, and so forth) to manage flow of funds. An additional KYC compliance and third-party verification process may also be applied to ensure property ownership.

[0041] In some implementations, for example, a property claim by verified owner generates a smart contract that is registered via third-party with local (county) registry of deeds. The described system allows verified homeowners sell to an option to a broker for a future listing of the property. For example, once the smart contract is in place, the property may be presented to an owner-broker auction, where multiple brokers may bid on the property -listing rights. The property owner may select a desired broker bid. In some implementations, such a selection generates update to the smart contract between the property owner and the broker. Further, transaction details are recorded and managed through the centralized facilities provided by the property-listing system.

[0042] In some implementations, brokers may register with the described property-listing system. After a minimal KYC compliance process (e.g., SMS message, upload of real-estate and driver licenses, etc.), a brokers may register. Brokers may provide financial institution information (e.g., routing number, account numbers, debit/credit card, and so forth) to manage purchase of tokens and/or other transactions. Moreover, additional compliance and/or a third- party verification process may apply to ensure broker credentials.

[0043] In some implementations, prior to participating in an owner-broker auction, such as described above, a broker may purchase tokens. In some implementations, brokers may be provided access to the full inventory of listing or a subset of listings based on various credentials and/or criteria. For example, inventory services may be employed to help brokers manage bids for properties of interest. Such services may include, filtering based on various criteria (e.g., property type, Zone Improvement Plan (ZIP) code, street address, radius, price, and so forth) and enable brokers to navigate the inventory. In some implementations, brokers can make bids on single or multiple properties at the same time. Once property owner accepts broker bid, updates to smart contract(s) are generated. Such smart contracts record the broker listing rights and transferring appropriate token or cash value between the parties.

[0044] FIG. 1 depicts an example environment 100 that can be employed to execute implementations of the present disclosure. The example system 100 includes computing devices 102, 104, 106, 108, a back-end system 130, and a network 110. In some implementations, the network 110 includes a local area network (LAN), wide area network (WAN), the Internet, or a combination thereof, and connects web sites, devices (e.g., the computing devices 102, 104, 106, 108) and back-end systems (e.g., the back-end system 130). In some implementations, the network 110 can be accessed over a wired and/or a wireless communications link. For example, mobile computing devices (e.g., the smartphone device 102 and the tablet device 106), can use a cellular network to access the network 110. In some examples, the users 122-126 may be brokers, investors, and/or property owners, such as described above. In some examples, the users 122-126 may be agents of the described parties.

[0045] In the depicted example, the back-end system 130 includes at least one server system 132 and a data store 134. In some implementations, the at least one server system 132 hosts one or more computer-implemented services employed within the described property-listing system, such as an integration and data acquisition service (see FIGS. 2A-2B), that users 122- 126 can interact with using the respective computing devices 102-106. For example, the computing devices 102-106 may be used by respective users 122-126 to verify ownership of a property or to participate in a broker auction for a listing contract through services hosted by the back-end system 130. In some implementations, the back-end system 130 provides an application programming interface (API) services with which the server computing device 108 may communicate. For example, the server computing device 108 may provide listing data through the provided API from trusted source or a system of record, such as a Register of Deeds.

[0046] In some implementations, back-end system 130 may include server-class hardware type devices. In some implementations, back-end system 130 includes computer systems using clustered computers and components to act as a single pool of seamless resources when accessed through the network 110. For example, such implementations may be used in data center, cloud computing, storage area network (SAN), and network attached storage (NAS) applications. In some implementations, back-end system 130 is deployed using a virtual machine(s).

[0047] The computing devices 102, 104, 106 may each include any appropriate type of computing device such as a desktop computer, a laptop computer, a handheld computer, a tablet computer, a personal digital assistant (PDA), a cellular telephone, a network appliance, a camera, a smart phone, an enhanced general packet radio service (EGPRS) mobile phone, a media player, a navigation device, an email device, a game console, or an appropriate combination of any two or more of these devices or other data processing devices. In the depicted example, the computing device 102 is a smartphone, the computing device 104 is a desktop computing device, and the computing device 106 is a tablet-computing device. The server computing device 108 may include any appropriate type of computing device, such as described above for computing devices 102-106 as well as computing devices with server-class hardware. In some implementations, the server computing device 108 may include computer systems using clustered computers and components to act as a single pool of seamless resources. It is contemplated, however, that implementations of the present disclosure can be realized with any of the appropriate computing devices, such as those mentioned previously.

[0048] FIGS. 2A and 2B depict an example architecture 200 of a property-listing system according to implementations of the present disclosure. As depicted in FIG. 2, the example architecture 200 includes a data acquisition interface, a data staging and transformation database, a data quality management node, an ODS, a big data platform, reference data, blockchain and smart contract services, business data services, and ODS services.

[0049] The data acquisition interface rationalizes data from multiple sources to ensure a consistent view. The interface is scalable and integrates with external data sources. For example, a country may have a single property record keeping entity or the service may be distributed and more localized (e.g., the Register of Deeds service a local county in the United States). Each of these entities may have differing implementation. For example, a blockchain for the registry of deeds for real estate has been implemented by both Singapore and Dubai. As described above, this information may be updated periodically (e.g., daily weekly, or monthly) and the data retrieved from these trusted source or a system of record via the data acquisition interface. In some implementations, the received property data is public and validated based the third-party, trusted sources that provided the data. In some implementations, the data is retrieved trough an API provided by the source.

[0050] The data staging and transformation database stores the data received through the data acquisition interface. The data quality management node processes the received data for integration providing full lineage for various data flows into a consistent model. Such a model is employed by the property-listing system 200 to, for example, improve the accuracy of acquired data. The reference data may include a broker master data management (MDM), an owner MDM, and an asset MDM.

[0051] Blockchain data is acquired, processed and managed via the Big Data platform. The platform standardizes inbound information from external sources (e.g., flat files, external blockchain, APIs, etc.). In some implementations, a first pass source data (the initial load) is used to populate the RE consortium blockchain.

[0052] The ODS and business data services provide user functions and data access. For example, auction services for a property listed may be provided such as described below. Such services are re-useable and support multiple consuming applications. In some implementations, these services are provided through an API to ensure consistency and freshness of information across the ecosystem (e.g., ODS, Business Data and Blockchain / Smart Contract services).

[0053] The blockchain and smart contract services provide access to the underlying blockchain data. In some implementations, access is provided to the real-estate records stored on an RE consortium blockchain. In some implementations, the real-estate data for a property is provided as a record. Records may be bundled together as a set and persisted as a block on the RE consortium blockchain. For example, the size of each block may include one hundred, five hundred, or one thousand records.

[0054] For example, generated smart contracts and owner validation records are stored on the ODS private blockchain. The owner verification, which may be provided through the ODS service, may include service such that an owner can upload a document, such as a license, that includes a picture and address information. Other forms of verification may include a credit check, a passport, a mortgage statement, or a utility bill. Once validated the owner has the right to present associated property. In such example, the RE consortium blockchain data, (e.g., the property listing data) is updated to includes a pointer to the ODS transaction record and associated smart contract

[0055] FIG. 3 depicts example platform events 300 that are persisted and referenced by records on the RE consortium blockchain. Event 1 includes an initial load of property data as received from a trusted source. The data is formatted and stored as a record on the RE consortium blockchain. When the owner of the property signs up and/or is verified by the system, a transaction is managed in the ODS, recorded to the ODS private blockchain and a new RE consortium blockchain record is created with a pointer to the transaction data (e.g., the smart contract Id). Other system events, such as a change of ownership of the property (event 3) or the expiration of the option contract (event 4) may also trigger a new record stored to the RE consortium blockchain referencing the transaction data in the ODS private blockchain

[0056] FIG. 4 depicts RE consortium blockchain events 400 according to implementations of the present disclosure. RE consortium blockchain data is acquired, processed and managed through the Big Data platform, such as depicted in FIG. 2. The Big Data platform processes received property data to standardize the information from external sources. Such data may be received in various formats, such as flat files, be retrieved from other external blockchains, or be pulled through a provided API. As depicted, in initial load is used to populate the RE blockchain (event A) while incremental updates or internal processes, such as the sale of a property sale or contact expiration may trigger event C.

[0057] FIG. 5A-5B depict examples 500 and 520 of ODS private blockchain events according to implementations of the present disclosure. The ODS private blockchain includes transactional records for each property listing stored on the RE consortium blockchain. For example, stored transactions may reflect changing status of the owner-broker process as defined by contract smart contract type A. Additionally, a cross reference(s) to RE consortium blockchain and associated contract are embedded into ODS record with additional required data. The ODS private blockchain may also be populated when a property owners signs-up (event B). Information from the RE consortium blockchain is augmented and stored in ODS and recorded appropriately in both blockchains (RE and ODS). Moreover, the ODS private blockchain manages the smart contracts and leverages data from the RE consortium blockchain to ensure data authority and validity.

[0058] As depicted the example events 500 include RE consortium blockchain events, A, B, and C, such that two of them (B and C) have correlating data to the ODS records. Other events and scenarios are possible. Event A represents the initial registration of property on to the RE blockchain (e.g., after being received from a third-party and reformatted accordingly). In the depicted example, event A is not recorded in the ODS private blockchain. Event B represents an assignment of the property listing control rights after the property owner is verified. The RE consortium blockchain is updated with the owners contact identifier and other supporting information. Multiple records in the ODS and the ODS Blockchain reflect the status of various processes. For example, the agreement between the property owner and the broker is represented as a transaction (smart contract type Al, See FIGS. 6A-6C) in the ODS private blockchain. When the property is listed, another transaction (smart contract type A2) is stored on the ODS private blockchain. Event C represents new transactions that are applied to the RE consortium blockchain as new information is processed and matched against existing data. For example, multiple use cases that terminate the RE consortium blockchain contract may be stored as transaction on the ODs private blockchain. Event C may be initiated by both system processes and changes in property data received, for example, via the incremental data uploads.

[0059] The contract types A1-A5 include the same contract identifier, but the information is being enhanced to evolve to represent the actual status of the process of the relationship. The ODS Blockchain contract types (Al, A2, . . . An,) represent lifecycle stage of the RE smart contract created when property owner signs up. In some implementations, a smart contract identifier can be referenced on both blockchains (RE and ODS).

[0060] In some implementations, an ODS record identifier is assigned during the registration of the owner and is a reference number that is used to manage ODS information. For example, the ODS record identifier may be a single pointer for ODS transaction data along with composite data used for the ODS private blockchain and ODS smart contract management.

[0061] The examples 520 depicted the structure of the records stored to the ODS private blockchain.

[0062] FIGS. 6A-6C depict the various contract types within a property-listing system according to implementations of the present disclosure. FIG. 6A depicts the owner-broker type A contract. The type A contract links together the property reference to specific owner decision to transfer listing rights. In some implementations, the type A smart contract supports full term obligation and contains required information to facilitate, for example, owner/broker auction(s), listing and sale processes.

[0063] FIG. 6B depicts the broker-investor type B contract. The type B contact links together a broker portfolio with acquired investments (e.g., individual properties) used to purchase control of rights. In some implementations, the type B smart contract supports full term obligation and includes information require to manage revenue sharing that is based on, for example, specific investor pool terms that may be used to purchase listing rights.

[0064] FIG. 6C depicts the investor-platform type C contract. The type C contract links together geographically dispersed investment areas and defines financial terms for participating brokers (e.g., investment pools). In some implementations, the type C smart contract includes required information to manage investment pool distributions and collection of revenue from broker transactions. For example, an investor may purchases tokens on the platform, which can allocate various amounts for different markets (e.g., $1 million each for Dubai, Massachusetts, New York, and California) to creates investment pools. The conditions associated with each pool can be different. For example, for the New York and Dubai markets, a 5 percent interest value can be set or a 30 percent transaction fee with first part of refusal can be set for another market. These provide the business rules that are exposed to the brokers. The pools provide a layer of management because there are different conditions that may be associated due to, for example, geographic, regional, and/or religious condition.

[0065] FIGS. 7 A depicts an example lifecycle 700 of an owner-broker (type A) contract. The initial data load event (event 1) includes the importing of external public and/or purchased data. In some implementations, no smart contracts are generated.

[0066] The owner sign-up event (event 2) may trigger the creation of smart contract. For example, the owner sign-up event may trigger the creation of an ODS smart contract, recording of the smart contract to the ODS private blockchain, and updates (e.g., a new record) to the RE consortium blockchain with the ODS smart contract information.

[0067] The broker-auction event (event 3) includes the acceptance of a bid by the listing party (e.g., the property owner). The system may support multiple and different auction types (e.g., English, Dutch, and so forth). The winner of the auction for specific property controls the listing rights for a specific period of time. In some examples, the ODS smart contract is updated with winning broker / investor information the update is persisted to the ODS private blockchain, and if owner does not list his or her property for sale within specified time (the horizon of the contract), the contract expires (e.g., event 7)

[0068] The property listing and sale event (event 4) may include offers to purchase the respective property. In some examples, when an owner accepts an offer and signs a purchase and sales agreement the ODS smart contract is updated with the broker / investor information, the transaction is persisted to the ODS private blockchain, and when an investor contract(s) are in-place, the smart contract allocates funds.

[0069] The closing event (event 6) may include close on the sale of the property. In some examples, when a sale is closed for a property the ODS smart contract is updated with broker / investor information, the transaction is persisted to the ODS private blockchain and when investor contracts are in-place, the smart contract allocates appropriate funding back to investor.

[0070] The expiration event (event 7) may include the expiration of the listing contract between a property owner and a broker. In some examples, an ODS smart contract can expire under the certain conditions, including that the owner did not list property for sale during term of the contract, the broker failed to sell the property within term specified by negotiated owner / broker listing contract, after completion of the closing, sale of the property, and reassignment of control rights. [0071] The contract reassignment event (event 8) may include reassignment of a contract between parties. For example, an accumulated portfolio of control rights may be sold (e.g., transferred) individually or in bulk between brokers and/or investors.

[0072] FIGS. 7B depicts an example lifecycle 700 of a broker-investor (type B) contract. The investment event (event 1) include when a broker or invests funds and creates investment pool (e.g., available tokens) for purchasing. In some examples an ODS smart contract is generated and registered on ODS private blockchain

[0073] The investment pools event (event 2) includes when a broker applies to available investment pools. In some implementations, when the broker accepts and agrees to terms and conditions for the pool, investment tokens are allocated to broker. In some examples, an ODS smart contract with appropriate references to investment pool, terms and allocated funds is generated and register on to the ODS private blockchain.

[0074] The owner-broker auction event (event 3) may occur when a broker is using their own funding or an investment pools. For example, when an investment pools are used to purchase listing rights, appropriate term and conditions are applied to the contact. In some implementations, the winner(s) of an auction for specific property controls the listing rights for specific period of time. In some examples, a smart contract is updated with winning broker and investor information, the transaction is recorded to the ODS private blockchain, and when an owner does not list his property for sale within specified time, the contract expires.

[0075] The property-closing event (event 4) is when, for example, a contract for sale of a property closes. In some examples, an ODS smart contract is updated with the broker and investor information, the transaction is recorded on the ODS private blockchain, and when the investor contracts are in-place, the smart contract allocates appropriate funding back to investor based on terms and conditions of the investment pool contract.

[0076] The expiration event (event 5) may include the expiration of a contract. In some examples, an ODS smart contract can expire under the certain conditions, including after completion of the closing, sale of the property and the reassignment of control rights.

[0077] The contract reassignment event (event 6) may include reassignment of a contract between parties. For example, accumulated portfolio of control rights may be sold (e.g., transferred) individually or in bulk between brokers and/or investors.

[0078] FIG. 8 depicts a flow diagram of an example process 800 for the generation of a smart contract for transfer of listing rights for a property. For clarity of presentation, the description that follows generally describes the process 800 in the context of FIGS. 1-7 and 9. However, it will be understood that the process 800 may be performed, for example, by any other suitable system, environment, software, and hardware, or a combination of systems, environments, software, and hardware as appropriate. In some implementations, various operations of the process 800 can be run in parallel, in combination, in loops, or in any order.

[0079] At 802, a request to transfer listing rights for a property to a broker is received from an owner. In some implementations, before the request to transfer listing rights is received, a record for the property is received from a trusted source or a system of record. The trusted source or a system of record maintains a public record for the property. In some implementations, the record is stored in a block on an RE data store. Such a block may include records for other properties. Each of the records having been received from a respective trusted source or system of record for each of the other properties. In some implementations, the received records are updated based on load data received incrementally for each of the respective trusted source or system of record. In some implementations, before receiving the request to transfer listing rights, validation data is received from the owner. Ownership of the property by the owner is verified based on the validation data. An initial owner-broker smart contract is persisted to an ODS and the verified ownership of the property by the owner is persisted to the RE data store, through a link to the initial owner-broker smart contract on the ODS. In some implementations, the validation data includes a photo of a license, a passport, mortgage statement, or utility bill for the owner that includes address information matching the property. In some implementations, the validation data includes information obtained through a credit check. In some implementations, the request to transfer listing rights for a property to a broker is based on an auction for broker services. From 802, the process 800 proceeds to 804.

[0080] At 804, a smart contract assigning a broker option for the property to the broker is generated. The smart contract includes information to facilitate a listing process and a sales process for the property. In some implementations, the smart contract includes a value assigned to the property for the broker option. In some implementations, the value may be set by the broker. In some implementations, the value include cash value and an escrow value. In some implementations, the smart contract include a horizon that sets an expiration date of the broker option when the property is not sold within an allotted timeframe. From 804, the process 800 proceeds to 806.

[0081] At 806, the smart contract is persisted to an ODS. From 806, the process 800 proceeds to 808. [0082] At 808, an event record for the property is generated. The event record includes property data and a reference to the smart contract. From 808, the process 800 proceeds to 810.

[0083] At 810, the event record is persisted to the RE data store. The RE data store is a single source of truth property assets. In some implementations, the ODS and the RE data store are blockchain are implemented through blockchain technology. In some implementations, a property listing smart contract is generated for a property listing of the property by the broker. The property listing smart contract may include a reference to the smart contract that may include the broker option. The property listing smart contract may be persisted to the ODS. From 810, the process 800 ends.

[0084] FIG. 9 depicts a block diagram of an exemplary computer system 900 used to provide computational functionalities associated with described algorithms, methods, functions, processes, flows, and procedures as described in the instant disclosure, according to an implementation. The illustrated computer 902 is intended to encompass any computing device such as a server, desktop computer, laptop or notebook computer, wireless data port, smart phone, personal data assistant (PDA), tablet computing device, one or more processors within these devices, or any other suitable processing device, including both physical or virtual instances (or both) of the computing device. Additionally, the computer 902 may comprise a computer that includes an input device, such as a keypad, keyboard, touch screen, or other device that can accept user information, and an output device that conveys information associated with the operation of the computer 902, including digital data, visual, or audio information (or a combination of information), or a graphical user interface (GUI).

[0085] The computer 902 can serve in a role as a client, network component, a server, a database or other persistency, or any other component (or a combination of roles) of a computer system for performing the subject matter described in the instant disclosure. The illustrated computer 902 is communicably coupled with a network 930. In some implementations, one or more components of the computer 902 may be configured to operate within environments, including cloud-computing-based, local, global, or other environment (or a combination of environments).

[0086] At a high level, the computer 902 is an electronic computing device operable to receive, transmit, process, store, or manage data and information associated with the described subject matter. According to some implementations, the computer 902 may also include or be communicably coupled with an application server, e-mail server, web server, caching server, streaming data server, business intelligence (BI) server, or other server (or a combination of servers).

[0087] The computer 902 can receive requests over network 930 from a client application (for example, executing on another computer 902) and responding to the received requests by processing the said requests in an appropriate software application. In addition, requests may also be sent to the computer 902 from internal users (for example, from a command console or by other appropriate access method), external or third parties, other automated applications, as well as any other appropriate entities, individuals, systems, or computers.

[0088] Each of the components of the computer 902 can communicate using a system bus 903. In some implementations, any or all of the components of the computer 902, both hardware or software (or a combination of hardware and software), may interface with each other or the interface 904 (or a combination of both) over the system bus 903 using an API 912 or a service layer 913 (or a combination of the API 912 and service layer 913). The API 912 may include specifications for routines, data structures, and object classes. The API 912 may be either computer-language independent or dependent and refer to a complete interface, a single function, or even a set of APIs. The service layer 913 provides software services to the computer 902 or other components (whether or not illustrated) that are communicably coupled to the computer 902. The functionality of the computer 902 may be accessible for all service consumers using this service layer. Software services, such as those provided by the service layer 913, provide reusable, defined business functionalities through a defined interface. For example, the interface may be software written in JAVA, C++, or other suitable language providing data in extensible markup language (XML) format or other suitable format. While illustrated as an integrated component of the computer 902, alternative implementations may illustrate the API 912 or the service layer 913 as stand-alone components in relation to other components of the computer 902 or other components (whether or not illustrated) that are communicably coupled to the computer 902. Moreover, any or all parts of the API 912 or the service layer 913 may be implemented as child or sub-modules of another software module, enterprise application, or hardware module without departing from the scope of this disclosure.

[0089] The computer 902 includes an interface 904. Although illustrated as a single interface 904 in FIG. 9, two or more interfaces 904 may be used according to particular needs, desires, or particular implementations of the computer 902. The interface 904 is used by the computer 902 for communicating with other systems in a distributed environment that are connected to the network 930 (whether illustrated or not). Generally, the interface 904 comprises logic encoded in software or hardware (or a combination of software and hardware) and operable to communicate with the network 930. More specifically, the interface 904 may comprise software supporting one or more communication protocols associated with communications such that the network 930 or interface’s hardware is operable to communicate physical signals within and outside of the illustrated computer 902.

[0090] The computer 902 includes a processor 905. Although illustrated as a single processor 905 in FIG. 9, two or more processors may be used according to particular needs, desires, or particular implementations of the computer 902. Generally, the processor 905 executes instructions and manipulates data to perform the operations of the computer 902 and any algorithms, methods, functions, processes, flows, and procedures as described in the instant disclosure.

[0091] The computer 902 also includes a memory 906 that holds data for the computer 902 or other components (or a combination of both) that can be connected to the network 930 (whether illustrated or not). For example, memory 906 can be a database storing data consistent with this disclosure. Although illustrated as a single memory 906 in FIG. 9, two or more memories may be used according to particular needs, desires, or particular implementations of the computer 902 and the described functionality. While memory 906 is illustrated as an integral component of the computer 902, in alternative implementations, memory 906 can be external to the computer 902.

[0092] The application 907 is an algorithmic software engine providing functionality according to particular needs, desires, or particular implementations of the computer 902, particularly with respect to functionality described in this disclosure. For example, application 907 can serve as one or more components, modules, applications, etc. Further, although illustrated as a single application 907, the application 907 may be implemented as multiple applications 907 on the computer 902. In addition, although illustrated as integral to the computer 902, in alternative implementations, the application 907 can be external to the computer 902.

[0093] There may be any number of computers 902 associated with, or external to, a computer system that includes computer 902, with each computer 902 communicating over network 930. Further, the term“client,”“user,” and other appropriate terminology may be used interchangeably as appropriate without departing from the scope of this disclosure. Moreover, this disclosure contemplates that many users may use one computer 902, or that one user may use multiple computers 902.

[0094] Implementations of the subject maher and the functional operations described in this specification can be implemented in digital electronic circuitry, in tangibly embodied computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Implementations of the subject matter described in this specification can be implemented as one or more computer programs, that is, one or more modules of computer program instructions encoded on a tangible, non-transitory, computer-readable computer-storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively or in addition, the program instructions can be encoded on an artificially generated propagated signal, for example, a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. The computer-storage medium can be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of computer-storage mediums.

[0095] The terms“data processing apparatus,”“computer,” or“electronic computer device” (or equivalent as understood by one of ordinary skill in the art) refer to data processing hardware and encompass all kinds of apparatus, devices, and machines for processing data, including by way of example, a programmable processor, a computer, or multiple processors or computers. The apparatus can also be or further include special purpose logic circuitry, for example, a central processing unit (CPU), a field programmable gate array (FPGA), or an application-specific integrated circuit (ASIC). In some implementations, the data processing apparatus or special purpose logic circuitry (or a combination of the data processing apparatus or special purpose logic circuitry) may be hardware- or software-based (or a combination of both hardware- and software-based). The apparatus can optionally include code that creates an execution environment for computer programs, for example, code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of execution environments. The present disclosure contemplates the use of data processing apparatuses with or without conventional operating systems, for example LINUX, UNIX, WINDOWS, MAC OS, ANDROID, IOS or any other suitable conventional operating system.

[0096] A computer program, which may also be referred to or described as a program, software, a software application, a module, a software module, a script, or code, can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data, for example, one or more scripts stored in a markup language document, in a single file dedicated to the program in question, or in multiple coordinated files, for example, files that store one or more modules, sub-programs, or portions of code. A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network. While portions of the programs illustrated in the various figures are shown as individual modules that implement the various features and functionality through various objects, methods, or other processes, the programs may instead include a number of sub-modules, third-party services, components, libraries, and such, as appropriate. Conversely, the features and functionality of various components can be combined into single components as appropriate.

[0097] The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, for example, a CPU, an FPGA, or an ASIC.

[0098] Computers suitable for the execution of a computer program can be based on general or special purpose microprocessors, both, or any other kind of CPU. Generally, a CPU will receive instructions and data from a read-only memory (ROM) or a random access memory (RAM) or both. The essential elements of a computer are a CPU for performing or executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to, receive data from or transfer data to, or both, one or more mass storage devices for storing data, for example, magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, for example, a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device, for example, a universal serial bus (USB) flash drive, to name just a few.

[0099] Computer-readable media (transitory or non-transitory, as appropriate) suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, for example, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices; magnetic disks, for example, internal hard disks or removable disks; magneto-optical disks; and Compact Disc Read-Only Memoiy (CD-ROM), Digital Versatile Disk (DVD)+/-R, DVD-RAM, and DVD- ROM disks. The memory may store various objects or data, including caches, classes, frameworks, applications, backup data, jobs, web pages, web page templates, database tables, repositories storing dynamic information, and any other appropriate information including any parameters, variables, algorithms, instructions, rules, constraints, or references thereto. Additionally, the memory may include any other appropriate data, such as logs, policies, security or access data, reporting files, as well as others. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[00100] To provide for interaction with a user, implementations of the subject matter described in this specification can be implemented on a computer having a display device, for example, a CRT (cathode ray tube), LCD (liquid crystal display), LED (Light Emitting Diode), or plasma monitor, for displaying information to the user and a keyboard and a pointing device, for example, a mouse, trackball, or trackpad by which the user can provide input to the computer. Input may also be provided to the computer using a touchscreen, such as a tablet computer surface with pressure sensitivity, a multi-touch screen using capacitive or electric sensing, or other type of touchscreen. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, for example, visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a web browser on a user’s client device in response to requests received from the web browser.

[00101] A GUI may be used in the singular or the plural to describe one or more graphical user interfaces and each of the displays of a particular graphical user interface. Therefore, a GUI may represent any graphical user interface, including but not limited to, a web browser, a touch screen, or a command line interface (CLI) that processes information and efficiently presents the information results to the user. In general, a GUI may include a plurality of UI elements, some or all associated with a web browser, such as interactive fields, pull-down lists, and buttons operable by the business suite user. These and other UI elements may be related to or represent the functions of the web browser.

[00102] Implementations of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, for example, as a data server, or that includes a middleware component, for example, an application server, or that includes a front-end component, for example, a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of wireline or wireless digital data communication (or a combination of data communication), for example, a communication network. Examples of communication networks include a LAN, a radio access network (RAN), a metropolitan area network (MAN), a WAN, Worldwide Interoperability for Microwave Access (WIMAX), a wireless local area network (WLAN) using, for example, 802.11 a/b/g/n or 802.20 (or a combination of 802.1 lx and 802.20 or other protocols consistent with this disclosure), all or a portion of the Internet, or any other communication system or systems at one or more locations (or a combination of communication networks). The network may communicate with, for example, Internet Protocol (IP) packets, Frame Relay frames, Asynchronous Transfer Mode (ATM) cells, voice, video, data, or other suitable information (or a combination of communication types) between network addresses.

[00103] The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

[00104] In some implementations, any or all of the components of the computing system, both hardware or software (or a combination of hardware and software), may interface with each other or the interface using an API or a service layer (or a combination of API and service layer). The API may include specifications for routines, data structures, and object classes. The API may be either computer language independent or dependent and refer to a complete interface, a single function, or even a set of APIs. The service layer provides software services to the computing system. The functionality of the various components of the computing system may be accessible for all service consumers using this service layer. Software services provide reusable, defined business functionalities through a defined interface. For example, the interface may be software written in JAVA, C++, or other suitable language providing data in extensible markup language (XML) format or other suitable format. The API or service layer (or a combination of the API and the service layer) may be an integral or a stand-alone component in relation to other components of the computing system. Moreover, any or all parts of the service layer may be implemented as child or sub-modules of another software module, enterprise application, or hardware module without departing from the scope of this disclosure. [00105] While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any invention or on the scope of what may be claimed, but rather as descriptions of features that may be specific to particular implementations of particular inventions. Certain features that are described in this specification in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable sub-combination. Moreover, although features may be described earlier as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

[00106] Particular implementations of the subject mater have been described. Other implementations, alterations, and permutations of the described implementations are within the scope of the following claims as will be apparent to those skilled in the art. While operations are depicted in the drawings or claims in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed (some operations may be considered optional), to achieve desirable results. In certain circumstances, multitasking or parallel processing (or a combination of multitasking and parallel processing) may be advantageous and performed as deemed appropriate.

[00107] Moreover, the separation or integration of various system modules and components in the implementations described earlier should not be understood as requiring such separation or integration in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Accordingly, the earlier description of example implementations does not define or constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure.

[00108] Furthermore, any claimed implementation described later is considered to be applicable to at least a computer-implemented method; a non-transitory, computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system comprising a computer memory interoperably coupled with a hardware processor configured to perform the computer-implemented method or the instructions stored on the non-transitory, computer-readable medium.

Claims

WHAT IS CLAIMED IS:

1. A computer-implemented method being executed by one or more processors and comprising:

receiving, from an owner, a request to transfer listing rights for a property to a broker; generating a smart contract assigning a broker option for the property to the broker, wherein the smart contract includes information to facilitate a listing process and a sales process for the property;

persisting the smart contract to an operational data store (ODS);

generating an event record for the property, wherein the event record includes property data and a reference to the smart contract; and

persisting the event record to a real-estate (RE) data store, wherein the RE data store provides a single source of property assets.

2. The computer-implemented method of claim 1 , wherein the ODS and the RE data store are implemented through blockchain technology.

3. The computer-implemented method of claim 2, comprising:

before receiving the request to transfer listing rights, receiving, from a trusted source or a system of record, a record for the property.

4. The computer-implemented method of claim 3, wherein the record is stored in a block on the RE data store, wherein the block includes records for other properties, and wherein each of the records is received from the respective trusted source or system of record for each of the other properties.

5. The computer-implemented method of claim 4, wherein the received records are updated based on load data received incrementally for each of the respective trusted source or system of record.

6. The computer-implemented method of claim 2, comprising:

before receiving the request to transfer listing rights, receiving validation data from the owner;

verifying ownership of the property by the owner based on the validation data;

persisting an initial owner-broker smart contract to the ODS; and

persisting the verified ownership of the property by the owner to the RE data store, through a link to the initial owner-broker smart contract on the ODS.

7. The computer-implemented method of claim 6, wherein the validation data includes a photo of a license, a passport, mortgage statement, or utility bill for the owner that includes address information matching the property.

8. The computer-implemented method of claim 6, wherein the validation data includes information obtained through a credit check.

9. The computer-implemented method of claim 1, wherein the smart contract includes a value assigned to the property for the broker option, wherein the value is set by the broker.

10. The computer-implemented method of claim 9, wherein the value include cash value and an escrow value.

11. The computer-implemented method of claim 1, wherein the smart contract include a horizon that sets an expiration date of the broker option when the property is not sold within an allotted timeframe.

12. The computer-implemented method of claim 1, comprising:

generating a property listing smart contract for a property listing of the property by the broker, wherein the property listing smart contract includes a reference to the smart contract that includes the broker option; and

persisting the property listing smart contract to the ODS.

13. The computer-implemented method of claim 1, wherein the request to transfer listing rights for a property to a broker is based on an auction for broker services.

14. One or more non-transitory computer-readable storage media coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations comprising:

persisting the smart contract to an operational data store (ODS);

15. The one or more non-transitory computer-readable media of claim 14, wherein the ODS and the RE data store are implemented through blockchain technology.

16. The one or more non-transitory computer-readable media of claim 14, wherein the operations comprise:

verifying ownership of the property by the owner based on the validation data;

persisting an initial owner-broker smart contract to the ODS data store; and persisting the verified ownership of the property by the owner to the RE data store, through a link to the initial owner-broker smart contract on the ODS data store.

17. A system, comprising:

one or more processors; and

a computer-readable storage device coupled to the one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations comprising:

persisting the smart contract to an operational data store (ODS); generating an event record for the property, wherein the event record includes property data and a reference to the smart contract; and

18. The system of claim 17, comprising:

before receiving the request to transfer listing rights, receiving, from a trusted source or a system of record, a record for the property, wherein the trusted source or a system of record maintains a public record for the property.

19. The system of claim 18, wherein the record is stored in a block on the RE data store, wherein the block includes records for other properties, and wherein each of the records is received from the respective trusted source or system of record for each of the other properties.

20. The system of claim 19, wherein the received records are updated based on load data received incrementally for each of the respective trusted source or system of record.