WO2023278635A1 - Suivi numérique de transferts d'actifs - Google Patents

Suivi numérique de transferts d'actifs Download PDF

Info

Publication number
WO2023278635A1
WO2023278635A1 PCT/US2022/035603 US2022035603W WO2023278635A1 WO 2023278635 A1 WO2023278635 A1 WO 2023278635A1 US 2022035603 W US2022035603 W US 2022035603W WO 2023278635 A1 WO2023278635 A1 WO 2023278635A1
Authority
WO
WIPO (PCT)
Prior art keywords
asset
logic
ownership
smart contract
blockchain
Prior art date
Application number
PCT/US2022/035603
Other languages
English (en)
Inventor
Joe L. RUIZ
Original Assignee
Vertrius Corp.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vertrius Corp. filed Critical Vertrius Corp.
Publication of WO2023278635A1 publication Critical patent/WO2023278635A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/018—Certifying business or products
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q2220/00—Business processing using cryptography

Definitions

  • Some embodiments of the invention are related to the execution of smart contracts to modify digital ownership records of an asset as recorded on a blockchain, the execution of the smart contract being dependent on digital shipping information, such as digital postage.
  • Blockchain can be used to securely record ownership information. Shipments of physical goods may be tracked using a tracking number.
  • Ownership of physical or digital assets are tracked using a combination of blockchain and shipping information, and/or other transfer of asset information.
  • the shipping information includes postage tracking numbers issued by shippers such as UPS or a postal service (e.g., the United States Postal Service).
  • the shipping information includes sending and receiving data associated with communication of a digital asset.
  • the transfer information includes sending and receiving data associated with transfer of a physical asset.
  • authenticity of an asset is established by a registered producer of the asset, referred to herein as the "owner of origin.”
  • a digital certificate of ownership (COO) is created by the owner of origin and this digital certificate may be represented by a non-fungible token (NFT).
  • NFT non-fungible token
  • Ownership of the digital certificate is intended to be recorded on a blockchain and transferred with transfer of the (digital or physical) asset. Under some circumstances, the certificate of ownership may also represent authenticity of the asset.
  • Various embodiments are distinguished by the use of shipping information and smart contracts to facilitate recording of ownership transfers on the blockchain. Such transfers may occur when the asset is conveyed from the owner of origin to one or more subsequent owners.
  • acceptance of an asset (from a sender) by a delivery service and delivery of that asset to a recipient may be represented by a tracking number, digital postage token, and/or other shipping information.
  • the shipping information may be used as input to a smart contract configured to automatically record a change in ownership on a blockchain in response to this information.
  • the smart contract may be further configured to execute other aspects of a transaction, such as, escrow, returns, and/or transfer of fund between accounts.
  • Various embodiments are distinguished by authentication of delivery of an asset to a recipient.
  • authentication may be accomplished by GPS data, biometrics (e.g., fingerprint or facial recognition), scanning of a QR code of the recipient, a digital signature, electronic activation of a delivered product, and/or other approaches to authentication discussed herein.
  • asset management system for tracking transfer of an asset
  • the system comprising optional party management logic (110) configured to manage parties to an asset transfer, the parties including a sender and a receiver; certificate logic (120) configured to receive requests for and to generate a certificate of ownership, the certificate of ownership including a non-fungible token and being associated the asset; blockchain logic (130) configured to record ownership of the asset on a blockchain, using the non-fungible token; request logic (135) configured to receive a request for transfer ownership of the asset; shipment tracking logic (140) configured shipment tracking information for the asset; smart contract logic (145) configured to generate a smart contact based on the receipt of the request for transfer, and to execute the smart contract based on the shipment tracking information, the smart contract being configured to transfer ownership of the asset and to update ownership of the asset on the blockchain; memory (170) configured to store at least the shipment tracking information; a microprocessor (190) configured to execute at least the smart contract logic; and optionally further comprising authentication logic 150 configured to authenticate delivery
  • Various embodiments of the invention include a method of documenting transfer of an asset, the method comprising: registering an owner of origin of the asset, the owner of origin being a party able to certify authenticity of the asset; receiving a request to generate a certificate of ownership for the asset from the owner of origin; creating the requested certificate of ownership; recording the certificate of ownership on a blockchain; receiving a request to transfer ownership of the asset; registering a recipient of the asset; establishing a smart contract including terms of the transfer of ownership; detecting shipment of the asset; detecting delivery of the shipment; executing the smart contract responsive to the detection of the shipment and/or the detection of the receipt, the execution of the smart contract including recording a change in ownership of the asset as recorded on the blockchain.
  • FIG. 1 illustrates an asset management system, according to various embodiments.
  • FIG. 2 illustrates methods of documenting transfer of an asset, according to various embodiments.
  • FIG. 1 illustrates an Asset Management System 100 configured for tracking transfer of an asset between parties, according to various embodiments.
  • Asset Management System 100 may be used to track ownership and assure authenticity of an asset from an original "owner of origin” (e.g., assembler, grower or manufacturer) of the asset through multiple owners.
  • the assets may include physical assets such as electronics or articles of clothing, or they may include digital assets such as images or software.
  • Authenticity is preferably assured by starting with an "owner of origin" whose interest is aligned with maintaining the authenticity of the assets.
  • a source of authenticity may be a rating agency, a bonded third-party, or entity certified by the owner of origin.
  • a reputable auction house or a licensed dealer in goods may be certified to establish initial authenticity of an asset.
  • a pharmacy having received a shipment of pharmaceuticals via a proper chain of custody may be able to establish original authenticity of the pharmaceuticals.
  • an owner of origin may be an authorized dealer or reseller.
  • Authenticity may be represented by a certificate of ownership tracible back to an owner of origin or other authority.
  • the certificate of ownership and corresponding asset are optionally associated with a separate "certificate of authenticity" associated with its own recordable non-fungible token (NFT).
  • NFT non-fungible token
  • Authenticity and ownership are maintained by tracking ownership and transfers of ownership of the asset on a blockchain.
  • transfers of ownership are tracked, at least in part, by the use of digital shipment tracking information.
  • the shipment tracking information can include, for example, shipping data and delivery data. Such data may be associated with a tracking number or digital postage.
  • shipping data refers to data indicating that an asset has been received by a shipping service, such as a national postal service (e.g., the United States Postal Service) or a private shipper (e.g., UPS or FedEx).
  • Shipping data may be associated with a tracking number and may be received from the shipping services using the tracking number.
  • An example of shipping data is a confirmation that a package has been received by the service via issuance of a tracking number and/or digital postage receipt.
  • Delivery data can include information accessed using a tacking number, or a variety of data associated with different approaches to authentication and/or confirmation. As described further herein, delivery data may be generated using authentication logic.
  • Asset Management System 100 optionally includes a Party Management Logic 110 configured to manage parties to an asset transfer.
  • the parties to an asset transfer typically include a "sender” and a "receiver” but may optionally include third parties such as an escrow agent, lender, trust company, intermediary, approval authority, government entity, identity management service, and/or the like.
  • Management of parties can include, for example, initial registration, authentication of party identity, maintenance of identity verification certificates, control of party or user permissions, control of activities and roles in which different parties are permitted to participate, association of parties with crypto currency wallets, bank accounts, addresses; and/or the like.
  • Party Management Logic 110 is optional in embodiments wherein the functions of Party Management Logic 110 are performed by a third party. For example, a large manufacturer of electronic products or collectable items may maintain their own private registration system.
  • Party Management Logic 110 is configured to manage an account of an owner of origin that is a footwear manufacturer.
  • the account may include several users having different authority, the ability to request certificates of authentication for specific products (assets) produced by the manufacturer, access to non-public data regarding certified owners of the produced products, management of login and security credentials, and/or the like.
  • Party Management Logic 110 may be configured to receive registration information and authentication information from the parties, establish their login credentials, perform login security (e.g., multi factor or device presence authentication).
  • a specific party e.g., a business, may have multiple user accounts with different privileges.
  • Party Management Logic 110 may be configured to register an owner of origin for an asset or a class of assets.
  • an owner of origin may be an owner of origin for a large number manufactured or produced by that party, and certificate logic (discussed elsewhere herein) is configured to issue a certificate of authority indicative of authority to request new certificates of ownership to the owner of origin.
  • certificates of ownership are issued by licensed or authorized third parties.
  • a certificate of ownership may be issued by a licensed dealer of goods, a manufacturer of the asset or a bonded certification entity, the certificate optionally indicating a retail purchaser as the owner of record.
  • Party Management Logic 110 is configured to connect one or more party's cryptocurrency wallets to an account for the purposes of authentication and/or funds transfer. Demonstratable access to a wallet may be used as a form of identity verification. For example, a party may identify them selves by transferring a small fee from the wallet to Asset Management System 100.
  • Certificate Management System 100 further includes Certificate Logic 120.
  • Certificate Logic 120 is configured to generate certificates of ownership, each of which is typically associated with a particular asset. Certificates of ownership may be indicative of the current owner of an asset by recordation of an NFT token on a blockchain. Certificates of ownership may also be indicative of authenticity of an asset, particularly when the certificate of ownerships is originally submitted to or generated by an owner of origin or other authorized authority. Certificate Logic 120 is optional in embodiments wherein, for example, certificates of ownership are issued by a third party, such as an owner of origin.
  • the certificate of ownership typically includes or is associated with a non-fungible token (NFT) that can be recorded on a blockchain.
  • NFT non-fungible token
  • the certificate of ownership represents less than full ownership of the asset and is configured to automatically expire, terminate, and/or be revoked in response to an event.
  • a certificate of ownership may expire at the termination of a lease, or may be revoked according to terms of a smart contract.
  • a certificate of ownership may represent a license to temporarily use an asset under certain restrictions.
  • Certificate Logic 120 may also be configured to generate and/or manage other types of certificates recordable on a blockchain. For example, a certificate of shipment, a certificate of delivery, and/or a certificate of payment. Such certificates are optionally used to execute smart contracts as discussed further elsewhere herein. Certificates of ownership may apply to digital asserts or physical assets.
  • Asset Management System 100 further includes Blockchain Logic 130.
  • Blockchain Logic 130 is configured to manage the recording of information on a blockchain (e.g., a distributed ledger) This information can include ownership transfers, certificates of ownership, other certificates discussed herein; asset characteristics (e.g., serial numbers) and/or other indicators of ownership and/or authenticity of an asset on a blockchain. Optionally, this recording includes use of non-fungible tokens.
  • Smart Contract Logic discussed elsewhere herein as element 145, is optionally configured to automatically record this information on the blockchain using Blockchain Logic 130.
  • the "blockchain” referred to herein may include one or more separate and distinct blockchains (i.e., distributed ledgers), optionally having different purposes, uses or requirements.
  • Parties to an asset transfer may further include a holder of a security interest, a lessor, a lien holder, a renter of the asset a lender, a payee, and/or the like.
  • the Blockchain Logic 130 is configured to record such interest(s) (less than full ownership) on the blockchain.
  • Smart Contract Logic 145 is optionally configured to release the security interest responsive to the shipment tracking information and a selected smart contract.
  • Blockchain Logic 130 is optionally configured to record terms of the smart contract(s).
  • Blockchain Logic 130 is further configured to record transactions including transfers of ownership interests in the assets. Such transfers may be recorded on either a public blockchain or a private blockchain as selected by one or more of the parties.
  • the private blockchain is optionally configured to provide confidentiality regarding identity of one or more parties.
  • the blockchain is configured to record ownership of two or more types of assets, and/or the smart contract logic is configured to treat differently the two or more types of assets.
  • These two types of assets can include origin certified assets and non-origin certified assets. Origin certified assets being those whose ownership is tracible, e.g., on the blockchain, back to an owner of origin.
  • Asset Management System 100 further includes Request Logic 135 configured to receive a request for transfer ownership of the asset. These requests are typically received from a party to the transaction.
  • Asset Management System 100 may be associated with an online store, eCommerce website, or retail establishment, and Request Logic 1350 may receive a request via one of these entities as part of a purchase.
  • Request Logic 135 is configured to offer one or more of the parties a predetermined set of smart contract templates from which the party may select. Terms of the smart contracts may include, for example, requirement for a payment, payment terms (e.g., payment at shipment and/or at delivery of the asset), escrow requirements for payment, shipment service, confirmation requirements for shipment or delivery, and/or the like.
  • Request Logic 135 is optionally configured to receive a selection of a smart contract template from among the set of smart contract templates. Smart Contract Logic 145 may be configured to generate the smart contract based on the selected smart contract template.
  • Asset Management System 100 further includes Shipment Tracking Logic 140 configured to receive shipment tracking information for the asset.
  • the shipment tracking information is optionally retrieved from a shipping service using a shipment tracking number.
  • shipping confirmation i.e., confirmation that the asset has been received by the shipping service
  • generation of shipping data includes a weighting a package, imaging or scanning of the asset, reading a serial number or other identifier of the asset, making a radio or electrical connection to a circuit within the asset, detection of a device of the sender, and/or the like.
  • the information (shipping data) thus obtained may be provided to Shipment Tracking Logic 140 as part of the shipping confirmation. Shipping data may include authentication of the sender.
  • the Shipment Tracking Logic 140 may be configured to track electronic transfer of the digital asset from the sender to the receiver. For example, Shipping Tracking Logic 140 may track sending of the asset from a device of the sender and/or delivery of the asset to a device of the receiver. Shipment Tracking Logic 140 may be configured to detect use of the asset by the receiver. For example, to receive a message from the asset that it is being used by the receiver or has been connected to a network device, or has been placed in a metaverse or game environment. Such confirmation may be accomplished by interaction between the smart contract established by Smart Contract Logic 145 and smart contracts or other computing instructions associated with the metaverse or game environment.
  • Shipment Tracking Logic 140 may be configured to receive a request from the receiver for a decryption and/or activation key which is needed before the asset can be utilized by the receiver, and to deliver the key, where this exchange servers as confirmation that the asset has been received by the receiver.
  • Asset Management System 100 further includes Smart Contract Logic 145 configured to generate a smart contact based on the receipt of the request for transfer of the asset, and to execute the smart contract based on the shipment tracking information.
  • the smart contract is typically configured to transfer ownership of the asset and to update ownership of the asset on the blockchain, based at least in part based on the shipment tracking information.
  • the smart contract may further be dependent on payments being made.
  • the smart contract may require payment from the receiver to the sender (optionally via an escrow account), payment a third party (e.g., a lender), payment of a service fee, periodic payments (e.g., lease or rental payments), payment of a security deposit, payment of a shipping fee, and/or the like.
  • a third party e.g., a lender
  • periodic payments e.g., lease or rental payments
  • payment of a security deposit e.g., payment of a shipping fee, and/or the like.
  • the Smart Contract Logic 145 is typically configured to require confirmed delivery of the asset or to require confirmed shipment of the asset prior to updating ownership of the asset on the blockchain. This confirmation is optionally facilitated by Authentication Logic 150, discussed further elsewhere herein. Smart Contract Logic 145 is optionally configured to record the smart contract, publicly or privately, on the blockchain.
  • Smart Contract Logic 145 is configured to execute a smart contract that requires a payment into a blockchain wallet for escrow purposes prior to shipping of an asset by a sender. After authenticated delivery of the asset, the Smart Contract Logic 145 then releases the escrow payment to the sender, according to terms of the smart contract.
  • the smart contract can include a wide range of terms agreed upon by the parties. These include, for example, automatic deactivation of an asset responsive to a failure of a payment, automatic transfer of ownership to a lien holder upon failure of the receiver to perform under the contract, reversal of ownership to the sender on expiration of a lease, etc.
  • Smart Contract Logic 145 may be configured to automatically record such events on the blockchain according to the smart contract.
  • the smart contract may be configured to initiate a payment in response to the shipment tracking information that includes shipment confirmation and/or delivery confirmation.
  • the smart contract may be configured to confirm payment into an escrow account and inform the sender of the payment, and to transfer payment from the escrow account to the sender responsive to delivery information regarding delivery of the asset.
  • Asset Management System 100 optionally further includes Authentication Logic 150 configured to authenticate delivery of the asset to the receiver.
  • Authentication Logic 150 may be configured to authenticate delivery of digital and/or physical assets.
  • Authentication Logic 150 may be configured to authenticate delivery of an asset into a virtual reality environment (e.g., a metaverse), to an augmented reality system, and/or to a physical location.
  • Authentication Logic 150 may be configured to authenticate delivery data based on face recognition, a photo, a QR code, a personal identification number, detected presence of a device, GPS data, or use of a lockbox.
  • delivery may include performing facial recognition on the receiver, require scanning of a QR code possessed by the receiver, and/or require wireless detection of a device (e.g., smartphone) of the receiver.
  • Authentication Logic 150 is configured to authenticate receipt of the asset based on electronic activation of the asset, receipt of a code attached to the asset from the receiver, and/or a request for an electronic or digital activation code from the receiver.
  • the asset may be encrypted or attached to a physical security device and receiver is required to confirm receipt of the asset in order to obtain a decryption key or a code needed to release the physical security device.
  • a phone number, email address, cryptocurrency wallet address, and/or other information related to a party's wallet may be used by Authentication Logic 150 as authentication information.
  • the buyer/recipient is assigned a recipient token with a unique universal identifier that is linked to the purchased merchandise, the digital postage token, and/or a shipping service's label.
  • a recipient token with a unique universal identifier that is linked to the purchased merchandise, the digital postage token, and/or a shipping service's label.
  • the buyer may be issued a token that allows them to confirm receipt of the asset and be registered as the new owner.
  • a token can be printed or electronic and can include an alphanumeric string, a QR code, or other identifying data.
  • the token is optionally generated by a point-of-sale device or provided with the purchase of the asset, e.g., provided with original packaging as a scratch-off code.
  • Authentication Logic 150 is configured to issue a one-time QR code is sent to buyer/recipient by email, text or mail.
  • the QR code can be scanned by the delivery service to verify the buyer/recipient along with the one-time code sent via email or text or by way of a one-time code generated using a token authenticator application. A login and password may be required.
  • a token e.g., a QR code or NFC chip
  • the link shows all public and private shipping history, transaction hash, owner of origin wallet address, any intermediaries wallet addresses and smart contract hash.
  • the Authentication Logic 150 marks the asset/package as having been delivered and an updated certificate of ownership is transferred to the buyer/recipient via email, text link or wallet to wallet.
  • the certificate of ownership may be used by the receiver or automatically to record the ownership transfer on the blockchain.
  • a receiver can request to return the asset purchased or gifted from a prior owner, e.g., the owner of origin or a retailer/agent thereof.
  • the receiver may be required to login to a verification page and enter their recipient ID, email, wallet information, phone number, and/or the like. If prior owner has preapproved or authorizes a return the receiver may transfers their ownership back to the prior owner using Asset Management System 100.
  • This transfer back optionally includes an escrow service capable of assuring that the asset returned is the asset that was originally transferred and/or provides a refund according to criteria established by a return smart contract.
  • Smart Contract Logic 145 and/or Authentication Logic 150 are configured such that returns of the asset are only permitted if delivery of the asset to the receiver has been acknowledged and/or authenticated. Restricting returns of the asset based on acknowledgement of delivery of the asset by the receiver prevents a type of fraud in which the receiver is not a proper owner of the asset. In some embodiments, returns require that the party wishing to make the return be recorded on the blockchain as the current owner of the asset. [0036] In a retail environment, in which an asset purchased and accepted by a receiver at a retail establishment, storefront, swap meet, or private facility, Authentication Logic 150 may be in communication with a point-of-sale system.
  • Information and devices used for authentication of receipt can include a recognition of the receiver's face or device of the receiver such as or other biometric, an identity card (e.g., driver's license), presence of a smartphone, a credit/debit card, a QR code provided by the receiver (e.g., displayed on their smartphone by a remote agent of Authentication Logic 150), and/or the like.
  • an identity card e.g., driver's license
  • a credit/debit card e.g., a credit/debit card
  • QR code e.g., displayed on their smartphone by a remote agent of Authentication Logic 150
  • Asset Management System 100 optionally further includes printer and/or Printer Logic 155 configured to print a postage label indicating that ownership of the asset is tracked using blockchain.
  • the label may include requirements for authentication of shipping and/or delivery, a tracking number, a QR code to be scanned by a shipping service and or a receiver.
  • the receiver is required to provide the tracking number or QR code to Authentication Logic 150 in order to activate and/or decrypt the asset.
  • the label may include any additional digital postage information.
  • Asset Management System 100 typically further includes User Interface Logic 160.
  • User Interface Logic 160 is configured to generate one or more user interfaces for 1) the sender or receiver of the asset to provide the request for transfer; 2) the receiver to be notified that their ownership of the asset has been recorded on the blockchain; 3) providing authentication of ownership for the asset; and/or 4) to receive the request to generate the certificate of ownership from an owner of origin for the asset.
  • User Interface Logic 160 may be configured to display user interfaces on the screen of a computing device and may also be configured to receive digital information such as a photograph from a camera or a wireless signal from smartphone or RFID device.
  • Asset Management System 100 further includes Memory 170 configured to store at least the shipment tracking information.
  • Memory 170 is optionally distributed among a plurality of computing and storage devices.
  • Memory 170 may further be configured to store: smart contracts, user registration information, private or public blockchains, smart contract templates, executable code configured included in any of the logic discussed herein, logs of transactions, authentication data, and/or any other information used in the systems and methods discussed herein.
  • Asset Management System 100 further includes a microprocessor 190 configured to execute at least Smart Contract Logic 145.
  • Asset Management System 100 may include multiple Microprocessor 190 distributed among multiple computing devices. These Microprocessor 190 may be configured to execute any combination of the logic discussed herein.
  • FIG. 2 illustrates methods of documenting transfer of an asset, according to various embodiments.
  • the methods illustrated in FIG. 2 are optionally performed by Assets Management System 100, and/or components thereof.
  • the methods illustrated by FIG. 2 may be used to transfer any of the assets (and associated rights) discussed herein, between any of the parties discussed herein.
  • the methods typically result in transfer of ownership, as represented on a blockchain, from a sender to a receiver.
  • the transfer of ownership represented by the blockchain is preferably, but not necessarily, represented by a change in possession from the sender to the receiver.
  • an item of clothing may be physically transferred from the sender to the receiver at a retail location or via a shipping service, in conjunction with the change in ownership as represented on the blockchain.
  • transfer of a security interest in an asset in the possession of a receiver may be transferred from a lien holder to the receiver upon satisfaction of the security interest (e.g., paying off a loan). This transfer does not require physical transfer of the asset.
  • transfer of a partial ownership interest (i.e., a security interest) to a lender may be recorded on the blockchain without physical transfer of the asset.
  • a distinguishing feature of the illustrated methods is that at least some of the transfers of ownership are facilitated using smart contracts and shipment tracking information.
  • the granting of a security interest does not require physical transfer of an asset, the ownership and physical possession of the asset by the party granting the security interest is established and recorded on the blockchain using the steps illustrated.
  • the steps illustrated in FIG. 2 may be performed in a wide variety of alternative orders and may be performed using a geographically distributed set of computing devices.
  • an owner of origin of an asset is registered.
  • the owner of origin is a party able to certify authenticity of the asset.
  • the asset may yet to be produced.
  • a sports star may register as an owner of origin for sports memorabilia signed in the future by the sports start.
  • the owner of origin is preferably a party that is able to certify authenticity of the asset.
  • the registration may specify a specific set and/or number of assets for which the party can act as the owner of origin.
  • the registration may also establish party information, such as , login/security credentials, or a list of individuals authorized to request certificates of ownership or view ownership information, and/or take other actions.
  • Register Step 210 is optionally performed using Party Management Logic 110 and/or User Interface Logic 160.
  • a request to generate a certificate of ownership for an asset is received.
  • the request is typically received from and/or approved by an owner of origin for the asset.
  • the request may include a serial number or some other unique identifier of the asset.
  • a particular pair of shoes may have a unique QR code or other pattern embossed onto a surface and the request may include an image of this pattern.
  • the certificate of ownership is associated with the identifier, and this association may be recorded on a blockchain with the certificate of ownership.
  • the request of Receive Request Step 215 is optionally received by Certificate Logic 120 via User Interface Logic 160.
  • the requested certificate of ownership is created.
  • the certificate of ownership is optionally created at the time the asset is produced, serialized, and/or sold.
  • the certificate of ownership typically lists the owner of origin as the original owner of the asset.
  • Steps 210-220 are optional in systems wherein a third party manages certificates of origin.
  • a third party manages certificates of origin.
  • an asset manufacture may choose to issue their own Certificates of Ownership.
  • a Record COO Step 225 the certificate of ownership generated In Create COO Step is recorded on a blockchain.
  • the certificate of ownership may be represented by an NFT.
  • Create COO Step 220 and Record COO Step 225 are optionally performed by Certificate Logic 120.
  • request to transfer ownership of the asset is received.
  • the request may come from a sender, receiver, or a third party. They request typically requires approval of the current owner of the asset as indicated on a blockchain.
  • Receive Request Step 230 may be performed using Request Logic 135 and/or User Interface Logic 160.
  • the request may be made using a user interface displayed on a computing device of a receiver and may be approved by a user interface displayed on a computing device of a sender (e.g., the current owner).
  • the request may be received, on behalf of the parties, from a point-of-sale system, an eCommerce website, a payment processor (e.g., a credit card company or Apple Pay ® ), a shipping service provider, a trust/escrow service provider, a lender, and/or the like.
  • Request Logic 135 and/or Certificate Logic 120 may provide the requester with a set of smart contract templates and a request that the requester provide contract terms to be used to generate a smart contract for the transfer.
  • the Request Logic 135 may be used to request a price, a type of authentication to use, a type of ownership being transferred, and whether the transfer should be recorded on a private or public blockchain.
  • Register Recipient Step 235 the intended recipient of the asset is registered. Register Recipient Step 235 is optionally performed using party Management Logic 110 and User Interface logic 160. Register Recipient Step 235 is optional if the recipient is already registered or is registered by a third party. Typically, the registration includes receiving identification information regarding the recipient. For example, registration may include receiving name and address information, downloading an agent of Authentication Logic 150 to a device of the recipient, gathering of biometrics of the recipient, gathering information regarding the device of the recipient, receiving identity documents of the recipient, and/or the like. Typically, registration includes establishing an account for the recipient.
  • an Establish Contract Step 240 a smart contract including terms of the transfer of ownership is established. Normally this contract is established according to terms received by Request Logic 135 and approved by the parties of the transaction.
  • the established smart contract is optionally based on a selected smart contract template.
  • the smart contract typically includes criteria required for the confirmation of shipping and delivery of the asset, and may require payment(s) recorded on a blockchain.
  • a Detect Shipment Step 245 shipment of the asset is detected.
  • Detect Shipment Step 245 and Detect Delivery Step 250 are optionally performed using Shipment Tracking Logic 140, Authentication Logic 150, and/or User Interface Logic 160. As discussed elsewhere herein, there are a wide variety of ways in what shipment and delivery information can include and how it may be obtained. Each of the detections of this information may trigger terms of the smart contract.
  • a Record Transfer Step 255 the smart contract is executed responsive to the detection of the shipment and/or the detection of the delivery, the execution of the smart contract including recording a change in ownership of the asset as recorded on the blockchain. Record Transfer Step 255 is optionally performed using Certificate Logic 120 and/or Blockchain Logic 130.
  • the change of ownership may be recorded on a private or public blockchain.
  • the change in ownership is recorded on a public blockchain but the new owner is represented by an alias configured to protect privacy of the new owner.
  • the alias may be recorded in combination with the actual identity of the new owner on a private blockchain.
  • the actual identity of the new owner can be kept confidential.
  • Authenticate Step 260 authentication of ownership of the asset is provided in response to a request. This authentication may be accomplished using Authentication Logic 150, Blockchain Logic 130, and/or User Interface Logic 160.
  • Authenticate Step 260 includes receiving a request for an owner's identity and an identifier of the asset. In response the identity may be retrieved from the blockchain and provided to the requestor. In situations on which the identity of the owner is only available on a private blockchain there are a number of approaches to confirming identity that may be used.
  • the request may include a proposed identity of the owner and an identity of the asset and Authentication Logic 150 may be configured to respond with a simple "yes/no" indicative if the received information is correct.
  • Authentication Logic 150 may require a unique and/or single use access code in order to provide the identity, or may require approval from the owner on a case by case basis to disclose the owner's identity.
  • Computing systems and/or logic referred to herein can comprise an integrated circuit, a microprocessor, a personal computer, a server, a distributed computing system, a communication device, a network device, or the like, and various combinations of the same.
  • a computing system or logic may also comprise volatile and/or non-volatile memory such as random- access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), magnetic media, optical media, nano-media, a hard drive, a compact disk, a digital versatile disc (DVD), optical circuits, and/or other devices configured for storing analog or digital information, such as in a database.
  • RAM random- access memory
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • magnetic media optical media, nano-media, a hard drive, a compact disk, a digital versatile disc (DVD), optical circuits, and/or other devices configured for storing analog or digital information, such as in a database.
  • a computer-readable medium, as used herein, expressly excludes paper
  • Computer-implemented steps of the methods noted herein can comprise a set of instructions stored on a computer-readable medium that when executed cause the computing system to perform the steps.
  • a computing system programmed to perform particular functions pursuant to instructions from program software is a special purpose computing system for performing those particular functions.
  • Data that is manipulated by a special purpose computing system while performing those particular functions is at least electronically saved in buffers of the computing system, physically changing the special purpose computing system from one state to the next with each change to the stored data.
  • the "logic” discussed herein is explicitly defined to include hardware, firmware or software stored on a non-transient computer readable medium, or any combinations thereof. This logic may be implemented in an electronic and/or digital device (e.g., a circuit) to produce a special purpose computing system. Any of the systems discussed herein optionally include a microprocessor, including electronic and/or optical circuits, configured to execute any combination of the logic discussed herein. The methods discussed herein optionally include execution of the logic by said microprocessor.

Abstract

Selon l'invention, la propriété et l'authenticité d'un actif sont suivies à l'aide d'informations générées pendant le transfert des actifs entre les parties. Ces informations peuvent comprendre des informations d'affranchissement, d'expédition ou de transfert numériques générées automatiquement. Le suivi de la propriété d'un actif en remontant jusqu'à une source d'origine faisant autorité fournit une preuve de l'authenticité de l'actif. L'intégrité du processus de suivi est assurée par l'enregistrement d'événements et l'exécution d'un contrat intelligent sur une chaîne de blocs.
PCT/US2022/035603 2021-06-29 2022-06-29 Suivi numérique de transferts d'actifs WO2023278635A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163216409P 2021-06-29 2021-06-29
US63/216,409 2021-06-29

Publications (1)

Publication Number Publication Date
WO2023278635A1 true WO2023278635A1 (fr) 2023-01-05

Family

ID=84692113

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/035603 WO2023278635A1 (fr) 2021-06-29 2022-06-29 Suivi numérique de transferts d'actifs

Country Status (1)

Country Link
WO (1) WO2023278635A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11783011B1 (en) * 2023-03-13 2023-10-10 Numéraire Financial, Inc. Asset metadata oracle service for facilitating digital asset trading
US20240086910A1 (en) * 2022-09-12 2024-03-14 Toshiba Tec Kabushiki Kaisha System and method for tracking and controlling print cartridge ownership transfers using non-fungible tokens

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160275461A1 (en) * 2015-03-20 2016-09-22 Rivetz Corp. Automated attestation of device integrity using the block chain
US20170046689A1 (en) * 2015-07-14 2017-02-16 Fmr Llc Crypto Voting and Social Aggregating, Fractionally Efficient Transfer Guidance, Conditional Triggered Transaction, Datastructures, Apparatuses, Methods and Systems
US20170140408A1 (en) * 2015-11-16 2017-05-18 Bank Of America Corporation Transparent self-managing rewards program using blockchain and smart contracts
US20170232300A1 (en) * 2016-02-02 2017-08-17 Bao Tran Smart device
US20190108482A1 (en) * 2017-10-06 2019-04-11 Sap Se Enablement of procurement processes with asset traceability using blockchain technology

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160275461A1 (en) * 2015-03-20 2016-09-22 Rivetz Corp. Automated attestation of device integrity using the block chain
US20170046689A1 (en) * 2015-07-14 2017-02-16 Fmr Llc Crypto Voting and Social Aggregating, Fractionally Efficient Transfer Guidance, Conditional Triggered Transaction, Datastructures, Apparatuses, Methods and Systems
US20170140408A1 (en) * 2015-11-16 2017-05-18 Bank Of America Corporation Transparent self-managing rewards program using blockchain and smart contracts
US20170232300A1 (en) * 2016-02-02 2017-08-17 Bao Tran Smart device
US20190108482A1 (en) * 2017-10-06 2019-04-11 Sap Se Enablement of procurement processes with asset traceability using blockchain technology

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240086910A1 (en) * 2022-09-12 2024-03-14 Toshiba Tec Kabushiki Kaisha System and method for tracking and controlling print cartridge ownership transfers using non-fungible tokens
US11783011B1 (en) * 2023-03-13 2023-10-10 Numéraire Financial, Inc. Asset metadata oracle service for facilitating digital asset trading

Similar Documents

Publication Publication Date Title
US11924324B2 (en) Registry blockchain architecture
US20210383377A1 (en) Decentralized identity verification platforms
US10621592B2 (en) Methods for authenticating a products
US8258924B2 (en) Merchandise-integral transaction receipt
WO2021159097A1 (fr) Authentification de produits
US11764974B2 (en) Method and system for certification and authentication of objects
US11443301B1 (en) Sending secure proxy elements with mobile wallets
JP2016512675A (ja) 安全な取引システム及び方法
WO2023278635A1 (fr) Suivi numérique de transferts d'actifs
CN111461813B (zh) 基于区块链的酒类新零售方法及系统
JP2002109409A (ja) 電子商取引システムにおける電子商取引方法
US11075766B1 (en) Method and system for certification and authentication of objects
JP2009512024A (ja) 識別情報の盗難および不正使用を防止し、これを保護するシステムおよび方法
RU96122982A (ru) Доверительные агенты для открытой электронной торговли
US8060452B2 (en) Sales methods, delivery methods, code verification methods, repudiation resolution methods, and articles of manufacture
KR20220113307A (ko) 블록체인과 정품인증 태그 기술을 사용한 제품 진위성 검증 및 소유권 변경이력관리 시스템
US11392949B2 (en) Use of mobile identification credential in know your customer assessment
US20230126016A1 (en) Tokenization of collectibles and related methods
DE102017217342B4 (de) Verfahren zum Verwalten eines elektronischen Transaktionsdokuments
US20220122072A1 (en) Systems and methods for secure redemption of electronic tickets using blockchain protocols
TWM562462U (zh) 銀行保險箱管理系統及能夠使用銀行保險箱管理系統之用戶端裝置
KR102635489B1 (ko) 블록체인 기반 자산 관리 시스템 및 방법
US20230396442A1 (en) Nft-based authentication system for tagged objects and methods for use therewith
US20230396430A1 (en) Tag-based authentication system and methods for use therewith
US20230394455A1 (en) Nft transactions via nft and pos platforms and methods for use therewith

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22834175

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE