System and method for retrieving dial to be displayed

Abstract

A system for retrieving a dial to be displayed is disclosed, comprising one or more processors configured by machine readable instructions to: receive a display request to display the dial on a watch screen, where the display request indicates a particular dial and a user associated with the watch screen; in response to the received display request, determining whether a user wallet of a decentralized account book holds a non-homogenized token associated with the specific dial, the user wallet being associated with the user; and responsive to the user wallet holding the non-homogenized token associated with the dial, facilitating display of the dial on the watch screen, where facilitating display of the dial includes initiating a transmission of information to the watch screen that causes the watch screen to display the dial. A method for retrieving a dial to be displayed is also disclosed.

Description

[0001] This application is a divisional application of a Chinese patent application with an application date of June 29, 2022, application number 202280046767.0, and invention name “System and method for creating customized watch faces and retrieving watch faces to be displayed”. Technical Field

[0002] The present disclosure relates to systems and methods for retrieving a watch face to be displayed. Background Art

[0003] Smart watches configured to display visual content are known. Watch faces capable of displaying on smart watches are known. Distributed ledgers are known technologies for generating secure records or registers of ownership of assets, transactions, and other information. For example, a distributed blockchain is a distributed ledger. Different types of distributed ledgers are known. Summary of the invention

[0004] The present invention discloses a system for retrieving a watch face to be displayed, the system comprising one or more processors configured by machine-readable instructions to: receive a display request to display the watch face on a watch screen, wherein the display request indicates a specific watch face and a user associated with the watch screen; in response to receiving the display request, determine whether a user wallet of a decentralized ledger holds a non-fungible token associated with the specific watch face, the user wallet being associated with the user; and in response to the user wallet holding the non-fungible token associated with the watch face, facilitate display of the watch face on the watch screen, wherein facilitating display of the watch face comprises initiating transmission of information to the watch screen that causes the watch screen to display the watch face.

[0005] The present invention also discloses a method for retrieving a watch face to be displayed, the method comprising: receiving a display request to display the watch face on a watch screen, wherein the display request indicates a specific watch face and a user associated with the watch screen; in response to receiving the display request, determining whether a user wallet of a decentralized ledger holds a non-fungible token associated with the specific watch face, the user wallet being associated with the user; and in response to the user wallet holding the non-fungible token associated with the watch face, facilitating the display of the watch face on the watch screen, wherein facilitating the display of the watch face comprises initiating the transmission of information to the watch screen that causes the watch screen to display the watch face.

[0006] One aspect of the present disclosure relates to a system configured to create a custom watch face that can be displayed on a watch screen (e.g., of a smartwatch). A user can select watch face features of different styles, formats, colors, and / or other aspects through a selection interface. For example, a user can select hour markers, hour hands, minute hands, and / or other features of a particular style to be included in a custom watch face. The values ​​of the watch face features selected by the user can define a watch face design that is subsequently used to generate the watch face. A user can purchase a custom watch face design by submitting a mint request and transferring an appropriate amount of consideration from a user wallet to an administrative wallet. The transfer of consideration from a user wallet to an administrative wallet can include a value transfer from an address associated with a user wallet to an address associated with an administrative wallet on a decentralized ledger. Once the administrative wallet receives the consideration, a watch face that can be displayed can be cast, and the watch face can contain the values ​​of the watch face features defined by the watch face design purchased by the user. A watch face record can be generated for the cast watch face, and a non-fungible token can be transferred to an address corresponding to a user wallet on a decentralized ledger. The watch face record can include information related to the watch face features and can include a watch face identifier that is unique to the watch face. A non-fungible token may indicate a watch face identifier, such that holding the non-fungible token indicates ownership of the watch face associated with the watch face identifier.

[0007] The system is further configured to retrieve a watch face to be displayed on the watch screen. The system may receive a display request from a user. The display request may indicate the watch face being requested (e.g., using a watch face identifier), the user associated with the watch screen, and / or other information. In response to receiving the display request, the system may determine whether a user wallet associated with the user holds a non-fungible token associated with the requested watch face. Holding a non-fungible token may indicate that the non-fungible token is recorded on a decentralized ledger at an address associated with the user wallet. In response to determining that the user wallet holds a non-fungible token, the system may facilitate the transmission of information that causes the watch screen to display the watch face to the watch screen. In response to determining that the user wallet does not hold a non-fungible token, the system may take no further action to transmit the information to the watch screen.

[0008] A system configured to create a watch face and retrieve a watch face to be displayed may include one or more of a server, a decentralized ledger server, a client computing platform, an external resource, a network, a user, a user interface, and / or other components. One or more servers and / or decentralized ledger servers may include electronic storage, one or more hardware processors, one or more blockchains, and / or other components. The electronic storage may be configured to store information. One or more hardware processors may be configured to execute one or more computer processing components. One or more computer processing components may include one or more of a presentation component, a transaction component, a casting component, a receiving component, a verification component, a display component, an input component, a communication component, and / or other components.

[0009] As used herein, any association (or relationship, or reflection, or indication, or correspondence) involving a server, processor, client computing platform, user, user account, watch face, watch face feature, asset, request, usage, exchange, challenge, offer, transaction, ownership, decentralized ledger, response, rejection, contract, incentive, suggestion, instruction set, operation, decision, allocation, transfer, presentation, interface, notification and / or another entity or object that interacts with any part of the system and / or plays a role in the operation of the system may be a one-to-one association, a one-to-many association, a many-to-one association and / or a many-to-many association or an "N" to "M" association (note that "N" and "M" can be different numbers greater than 1).

[0010] As used herein, the term "receiving" (and its derivatives) may include active and / or passive retrieval, determination, derivation, transmission, uploading, downloading, submission and / or exchange of information, and / or any combination thereof. As used herein, the term "implementing" (and its derivatives) may include any local and remote "implementation" of active and / or passive cause and effect. As used herein, the term "determining" (and its derivatives) may include measuring, calculating, computing, estimating, approximating, generating and / or otherwise deriving and / or any combination thereof.

[0011] These and other features and characteristics of the present technology, as well as the methods of operation and functionality of the related structural elements and combinations of parts and the economy of manufacturing, will become more apparent after considering the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for illustration and description purposes only and are not intended as a definition of the limits of the present invention. As used in the specification and claims, the singular form 'a', 'an ... ’ , 'an ’ and 'the' includes plural references. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 A system configured to create a custom watch face and retrieve the watch face to be displayed is shown in accordance with one or more implementations.

[0013] Figure 2 Methods of creating a custom watch face according to one or more implementations are shown.

[0014] Figure 3 A method of retrieving a watch face to display is shown according to one or more embodiments.

[0015] Figure 4 An exemplary selection interface that may be used by the system to create a custom watch face is shown in accordance with one or more implementations.

[0016] Figure 5 An example watch screen is shown showing a watch face that the system can use to create a custom watch face and retrieve a watch face to display in accordance with one or more implementations. DETAILED DESCRIPTION

[0017] Figure 1 A system 100 configured to create a custom watch face and retrieve a watch face to be displayed according to one or more embodiments is shown. As used herein, the term "watch face" may refer to a custom watch face selected and / or created by a user. As used herein, an "identifier" may refer to a watch face identifier that is unique to a particular watch face. For example, in some embodiments, an identifier or identification information for a watch face may include or be based on a combination of different types of information, including but not limited to information about the type of watch face, watch face features, values ​​of watch face features, an alphanumeric string (e.g., a serial number or other text string) or other human and / or machine readable identifier of a watch face, and / or other types of information. As used herein, ownership of a watch face may be tracked, recorded, and / or otherwise registered on one or more decentralized ledgers.

[0018] System 100 may include one or more servers 102, a decentralized ledger server 111, a management server 115, one or more client computing platforms 104, a user interface 125, one or more external resources 126, and / or other components. As used in the description herein, any use of the term "user" may refer to user 123. Electronic storage 128a and electronic storage 128b may be similar to electronic storage 128 described elsewhere in this disclosure, but included in management server 115 and decentralized ledger server 111, respectively, as shown in FIG. Figure 1 shown.

[0019] The decentralized ledger server 111 may be used to implement one or more decentralized ledgers 117. In some embodiments, the decentralized ledger 117 may be hosted by a distributed computing platform ( Figure 1 In some embodiments, the distributed computing platform may be implemented by a group of client computing platforms and / or servers (including, for example, one or more decentralized ledger servers 111). The distributed computing platform may support virtual machines ( Figure 1 117). The distributed computing platform and / or virtual machine may form a runtime environment for smart contracts and / or other executable code. The distributed computing platform may include an electronic storage configured to store part or all of the decentralized ledger 117. Smart contracts may be stored on the decentralized ledger 117 and / or another decentralized ledger. In some embodiments, the distributed computing platform may be an EOSIO platform. In some embodiments, the distributed computing platform may be similar to or based on the EOSIO platform. In some embodiments, the distributed computing platform may be Ethereum. In some embodiments, the distributed computing platform may be similar to or based on Ethereum. In some embodiments, the virtual machine may be a decentralized virtual machine.

[0020] In some embodiments, at least one of the decentralized ledgers 117 implemented by the decentralized ledger server 111 is a private permissioned decentralized ledger. The private permissioned blockchain can be configured to record information. The recorded information can be related to one or more dials recorded on the decentralized ledger 117. The recorded information may include ownership of the dial. User actions can modify the recorded information related to the dial. For example, ownership and / or other rights can be modified. In some embodiments, the dial can be removed from one decentralized ledger and added or recorded on another decentralized ledger. In some embodiments, at least one of the decentralized ledgers 117 implemented by the decentralized ledger server 111 is a public decentralized ledger. The public decentralized ledger can be configured as an EOSIO mainnet, an Ethereum mainnet, Ethereum 1.5, Ethereum 2.0, a derivative of Ethereum 2.0 configured to trade Ether (ETH) between accounts, or a part of an EOSIO derivative configured to trade EOS between different accounts.

[0021] Decentralized Ledger 117 Elements of the ledger can be grouped together into units called blocks and / or nodes. For example, an individual block may include one or more assets (e.g., dials) and / or one or more transactions. For example, an individual block may be connected to one or more other individual blocks. Individual blocks may be connected or linked together to form a structure of blocks and / or a hierarchy of blocks, such as, for example, a chain of blocks. An individual block may include one or more assets (e.g., dials), one or more transactions, and / or other information. As used herein, a "separate block including a dial" may refer to a separate block that includes a dial record and / or a dial identifier associated with a dial.

[0022] like Figure 1 As shown, the decentralized ledger server 111 may include one or more of an electronic storage 128b, a processor 130b, a machine-readable instruction 106b, a decentralized ledger 117 (node), and / or other components. The machine-readable instruction 106b may include one or more instruction components. The instruction component may include a computer program component. The instruction component may include one or more of a receiving component 114, a verification component 116, a display component 118, and / or other instruction components. In some embodiments, a separate decentralized ledger server 111 may be dedicated to a specific node of the decentralized ledger 117. Typically, different nodes are included in different servers or different computer systems (or implemented or hosted by different servers or different computer systems) to improve the security and confidentiality of transactions on decentralized ledgers and / or blockchains. When different nodes are located in different geographic locations, on different types of computing platforms, and / or are otherwise distributed and diversified, the consensus protocol for a particular blockchain will be more difficult to forge or circumvent.

[0023] In some embodiments, one or more decentralized ledgers 117 implemented by the decentralized ledger server 111 may be publicly accessible. In some embodiments, one or more decentralized ledgers implemented by the decentralized ledger server 111 may be private and / or permissioned. In some embodiments, one or more decentralized ledgers 117 implemented by the decentralized ledger server 111 may be append-only. In some embodiments, existing blocks and / or nodes of one or more decentralized ledgers 117 implemented by the decentralized ledger server 111 cannot be substantially changed or deleted unless multiple copies are changed. This is unlikely to occur if multiple copies are stored on different computing platforms (e.g., different geographic locations) according to the relevant consensus protocol. The decentralized ledger 117 can be replicated on multiple computing platforms, preferably in multiple different geographic locations. In addition, individual blocks and / or nodes can be connected together in a tamper-proof manner, such as, for example, using hash chains and / or digital signatures. Specifically, the hash value may be generated using a fixed output length one-way hash function that takes a variable length input and is practically impossible (or at least computationally infeasible) to reverse. Thus, the hash function may provide one-way encryption. As non-limiting examples, the hash function may be SHA-256, BLAKE2, SHAKE256, and / or another hash function. The contents of individual blocks, individual nodes, transactions, and / or assets may be digitally signed in a manner that proves integrity and / or prevents tampering, such as by providing authentication and repudiation.

[0024] The server 102 may be configured to communicate with one or more client computing platforms 104 according to a client / server architecture and / or other architectures. The client computing platform 104 may be configured to communicate with other client computing platforms 104 via the server 102 and / or according to a peer-to-peer architecture and / or other architectures. The user 123 may access the system 100 via the client computing platform 104. In some embodiments, the system 100 and / or the decentralized ledger server 111 may be configured to communicate with one or more of the server 102, the user 123, and / or other entities and / or components, for example, via one or more networks 116. In some embodiments, the client computing platform 104 may be accessed via one or more user interfaces 125. The user interface 125 is shown as a mobile device, but may include one or more other computing devices. The user interface 125 may be connected and / or associated with one or more user watch screens 127. The user watch screen 127 may be included in a smart watch, a digital watch, a wearable device, a non-wearable device, a portable electronic device (e.g., a personal digital assistant (PDA)), and / or other devices. The user interface 125 may be connected and / or associated with the user's watch screen 127 via a wireless connection (eg, Bluetooth pairing), a wired connection, and / or other pairing methods.

[0025] Server 102 may include electronic storage 128, processor 130, machine-readable instructions 106, and / or other components. Server 102 may be configured by machine-readable instructions 106. Machine-readable instructions 106 may include one or more instruction components. Instruction components may include computer program components. Instruction components may include one or more of presentation component 108, transaction component 110, minting component 112, and / or other instruction components. Processor 130a and processor 130b may be similar to processor 130 described elsewhere in this disclosure, although including management server 115 and decentralized ledger server 111, respectively, as in Figure 1 The machine-readable instructions 106a and the machine-readable instructions 106b may be similar to the machine-readable instructions 106 described elsewhere in this disclosure, although included in the management server 115 and the decentralized ledger server 111, respectively, as shown. Figure 1 shown.

[0026] The presentation component 108 can be configured to implement presentation of a selection interface on one or more client computing platforms 104 associated with the user 123. The selection interface can facilitate the user 123 to enter and / or select a dial design. The selection interface can display one or more values ​​of individual features in the dial features. The dial features can include one or more of an hour hand, a minute hand, a splashback, a dial, a sub-dial, an hour mark, a weather display, a date display, and / or other components that can be included in the dial. In some embodiments, a particular dial feature can be static and / or unchanging (e.g., an hour mark). In some embodiments, the dial feature can change based on one or more of the passage of time (e.g., an hour hand, a minute hand, a date display), real-world events and / or real-time data (e.g., a weather display), and / or other factors. For example, the splashback of the dial can include a video, a gif, a slide show of images, and / or other dynamic and / or static images.

[0027] In some embodiments, the selection interface may display one or more values ​​of a dial feature with an associated cost. The value of the dial feature may indicate and / or represent a change in the color, style, format, type, and / or other aspects of the dial feature. For example, a first dial feature may be an hour marker and / or another feature. The hour marker may be displayed as a dash, a number, a Roman numeral, and / or other symbol. A first value may represent the hour marker as a dash, a second value may represent the hour marker as a number, a third value may represent the hour marker as a Roman numeral, and so on. The first value, the second value, the third value, and / or other values ​​may be included in the selection interface and / or may be selected by the user 123. The associated cost of a separate value may be based on the popularity of the value, the remaining inventory of the value (i.e., the value can only be selected a fixed number of times and / or by a fixed number of users), the appearance of the value, and / or other information. In some embodiments, the associated cost of one or more values ​​may change based on the popularity of the value, the remaining inventory of the value, the appearance of the value, and / or other information. The associated cost of one or more values ​​may change every day, every two days, every 12 hours, every 2 hours, every hour, and / or other time intervals. In some implementations, the associated cost may be in U.S. dollars (USD), Euros (EUR), and / or other currencies.

[0028] In some embodiments, the selection interface may display one or more pre-selected dial designs that can be selected by the user 123 for purchase. Individual dial designs may be defined by one or more values ​​of dial features. The dial design may represent the appearance of the associated dial. For example, the dial design may indicate Roman numeral hour markers, gold hour hands, silver minute hands, blue splashbacks, and / or other values ​​of dial features. The pre-selected dial designs may include one or more values ​​of dial features selected by other users 123, selected by one or more administrative users, randomly generated, and / or other selected methods. In some embodiments, individual dial designs in the pre-selected dial designs may include an associated cost. The associated cost of a particular pre-selected dial design may be based on the combined associated costs of the values ​​of the dial features included in the dial design. In some embodiments, the associated cost of a particular pre-selected dial design may be set by the user who created the dial design. In some embodiments, the user 123 may purchase a randomly generated dial design before viewing the dial design and / or after viewing the dial design. In some embodiments, a particular dial design may only be selected (i.e., purchased) a fixed number of times. In response to a particular watch face design being selected a fixed number of times, the particular watch face design may be displayed on the selection interface as having a sold-out status and / or not included in the selection interface.

[0029] The transaction component 110 can be configured to receive a casting request from the client computing platform 104 to cast a dial according to a dial design input and / or selected through the selection interface. In some embodiments, the casting request can include information related to the dial design, the user, and / or other information. The information related to the dial design can include values ​​of dial features that define the dial design, the cost of the dial design, and / or other information. In some embodiments, the casting request can be received from the client computing platform 104 via one or more networks 116. In response to the user 123 selecting a dial design through the selection interface, the user 123 selecting one or more action buttons on the user interface 125, the user 123 initiating a transfer of consideration, and / or other user actions, the casting request can be automatically submitted to the transaction component 110.

[0030] The transaction component 110 can be configured to implement a transfer of consideration from a user wallet associated with the user to an administrative wallet and / or other wallets in response to receipt of a minting request. The user wallet and the administrative wallet can each correspond to an address on the decentralized ledger 117, so that the transfer of consideration involves a transfer of value on the decentralized ledger 117 from an address associated with the user wallet to an address associated with the administrative wallet. In some embodiments, the amount and / or value of the consideration can be determined by the cost of the dial design and / or the cost of the value of the dial features defining the dial design. The amount and / or value of the consideration can be included in the received minting request. In addition to the cost of the dial design, the amount and / or value of the consideration can further include transfer fees, transaction fees, handling fees, and / or other types of fees.

[0031] In some embodiments, the user wallet can be connected to an external wallet. The external wallet can allow the user to store and manage funds on the public decentralized ledger 117. The public decentralized ledger 117 can be part of the EOSIO mainnet, the Ethereum mainnet, Ethereum 1.5, Ethereum 2.0, a derivative of Ethereum 2.0 configured to trade Ether (ETH) between accounts, a derivative of EOSIO configured to trade EOS between different accounts, and / or other distributed computing platforms. In some embodiments, funds can be transferred from a connected external wallet to a user wallet. Funds transferred from a connected external wallet to a user wallet can be in U.S. dollars (USD), euros (EUR), and / or other currencies. Transferring funds from an external wallet to a user wallet may include transfer fees, handling fees, and / or other types of fees. Funds transferred and / or stored in a user wallet can be used within the system 100 (e.g., to purchase a watch face). In some embodiments, a user wallet can store funds from transactions conducted within the system 100 (e.g., from selling a watch face). In some embodiments, funds stored in a user wallet can be used only for transactions (e.g., buying, selling, or transferring watch faces) on the decentralized ledger 117. Funds stored in a user wallet can be transferred to an external wallet for transactions on a decentralized ledger outside of the system 100 (e.g., buying, selling, or transferring other digital and / or non-digital assets).

[0032] The casting component 112 may be configured to cast a dial in response to the management wallet receiving the consideration. As used herein, the term "casting" may refer to the conduct, initiation and / or execution of a process, transaction, procedure, operation and / or step that results in the instantiation of a dial, including the establishment of ownership and the definition of the appearance of the dial. Casting a dial may include generating a dial record for the dial according to the dial design. Casting a dial may further include converting the dial design into a format readable by a device having a watch screen and / or other methods of creating a displayable dial. In some embodiments, casting a dial may include building an executable program. The executable program is transmitted to a device capable of executing the program. In some embodiments, a dial having a value of a dial feature defining the dial design may be displayed on a watch screen of a device and / or other devices by executing the program on the device. In some embodiments, a dial record may include a value of a dial feature defining the dial design. In some embodiments, a dial record may be recorded at an address on a decentralized ledger 117 in a smart contract and / or other executable code. The dial record may include information related to casting a dial, including but not limited to the value of a dial feature defining the dial design.

[0033] In some embodiments, the dial record may include a dial identifier. The dial identifier may be unique to the dial that was cast. The identifier may include an alphanumeric string (e.g., a serial number or other text string) or other human and / or machine readable identifier and / or other information of the dial. The identifier may be based on the value of a dial feature, the time the dial was cast, the date the dial was cast, and / or other information. For example, a first dial may have a first dial identifier "001", a second dial may have a second dial identifier "002", a third dial may have a third dial identifier "003", and so on. The first, second, third dial identifiers and / or other identifiers may be determined based on the order in which the dials were cast. The first, second, third dial identifiers and / or other dial identifiers may be unique such that no two dial identifiers are the same. In some embodiments, the first dial and the second dial may be cast according to a first dial design and a second dial design, respectively. The first dial design and the second dial design may be defined by the value of the same dial feature (i.e., the first dial and the second dial have a similar or identical appearance). The first dial identifier and the second dial identifier may still have different values. In some embodiments, the dial identifier may indicate the owner history of the associated dial. For example, the dial identifier may include ownership information. The ownership information may indicate and / or identify a first owner, a second owner, a current owner, and / or other owners. As a non-limiting example, the dial may have been owned by the first owner before being owned by the second owner. The dial may have been owned by the second owner before being owned by the current owner.

[0034] In some embodiments, casting a dial may include burning a combination of values ​​of dial features that define the dial design. As used herein, the term "burn" may refer to the recording of the values ​​of dial features for a separate dial, so that future casting of a dial with the same values ​​of some or all of the dial features is limited or even prohibited. Burning a combination of values ​​may include making the combination of values ​​unavailable for selection, unavailable for casting, and / or unavailable for other actions. For example, an unavailable combination of values ​​may not be displayed in a selection interface and / or the user may not be allowed to continue purchasing the dial. In some embodiments, a combination of values ​​may be burned after being cast once, after being cast five times, and / or after being cast a fixed number of times. In some embodiments, a list of burn combinations may be stored in an electronic memory 128, on a decentralized ledger 117, and / or at other locations. The list of burn combinations may include information related to the combination of values ​​of dial features that have been burned and / or cannot be cast. In some embodiments, a casting component 112 that receives a casting request may implement a smart contract and / or other executable code to check the dial design included in the casting request according to the list of burn combinations. In response to the dial design being on the burnout combination list, the casting request may not be satisfied. In response to the dial design not being on the burnout combination list, the casting request may be satisfied and / or the dial may be cast according to the dial design.

[0035] The minting component 112 can be configured to transfer a non-fungible token indicating a dial identifier to an address on a decentralized ledger 117 corresponding to a user wallet. In some embodiments, the non-fungible token can be transferred simultaneously to the dial record being generated. In some embodiments, transferring a non-fungible token can indicate the formation of a smart contract and / or record the smart contract on a decentralized ledger 117 at an address corresponding to a user wallet. In some embodiments, these instructions can instruct the decentralized ledger 117 to record and / or modify dial records, transactions, and / or rights (e.g., ownership, distribution rights, etc.). In some embodiments, the non-fungible token can be stored on a blockchain. The blockchain can implement a decentralized ledger 117 and can record rights related to a digital asset (e.g., a dial). For example, a blockchain is a ledger and a decentralized database that records rights related to a digital asset. Multiple rights can form a group of rights or bundles of rights that can be transferred together and / or acted and / or operated in other ways. For example, rights may include one or more of the right to use, the right to sell, the right to destroy, certain types of distribution rights, and / or other rights. In some embodiments, a non-fungible token may be an asset. In some embodiments, a non-fungible token may include one or more of a security token, a utility token, a payment token, an initial coin offering (ICO) token, a virtual currency token, an encrypted token, an ERC-20 token, an ERC-721 token, an EOS token, a dedicated token, a platform token, and / or other tokens. In some embodiments, a token not only represents a value, but may also have a specific purpose in a specific distributed computing platform, for example, in the operation of a decentralized ledger 117.

[0036] The receiving component 114 can be configured to receive a display request to display a watch face on the watch screen. The display request can indicate that the user 123 attempts and / or wants to display a watch face on the watch screen. In some embodiments, the user 123 can submit a display request by interacting with one or more user interfaces 125, interacting with one or more devices having a user watch screen 127, and / or other means. The display request can indicate a specific watch face (e.g., using a watch face identifier), a user associated with the watch screen, a user wallet associated with the user, an address on the decentralized ledger 117 associated with the user wallet, and / or other information.

[0037] The verification component 116 can be configured to determine whether a user wallet of the decentralized ledger 117 holds a non-fungible token associated with a particular watch face in response to receiving a display request. In some embodiments, determining whether the user wallet holds a non-fungible token may include determining whether the non-fungible token is recorded on the decentralized ledger 117 at an address associated with the user wallet. In some embodiments, the address associated with the user wallet may hold one or more tokens (i.e., the user owns one or more watch faces). The non-fungible token may be recorded on a smart contract and / or other executable code. In response to the non-fungible token being recorded on the decentralized ledger 117 at an address associated with the user wallet, it is determined whether the non-fungible token indicates a watch face identifier associated with the watch face. In some embodiments, the watch face identifier may be included in the display request. In response to the non-fungible token indicating a watch face identifier associated with the watch face, it can be determined that the user has ownership of the watch face. In response to the non-fungible token not indicating a watch face identifier associated with the watch face, it can be determined that the user does not have ownership of the watch face. In some embodiments, the verification component 116 can be configured to obtain watch face rights (e.g., ownership, distribution rights, licensing rights, and / or other rights) for a particular watch face in response to the user having ownership of the particular watch face. In some embodiments, the verification component 116 can be configured to access the decentralized ledger 117 to obtain the watch face rights (recorded on the decentralized ledger 117, such as in one or more smart contracts).

[0038] The display component 118 can be configured to facilitate the display of the watch face on the watch screen in response to the user wallet holding the non-fungible token associated with the watch face. Facilitating the display of the watch face may include initiating the transmission of information to the watch screen that causes the watch screen to display the watch face. In some embodiments, the information may include a watch face design, values ​​of watch face features, executable programs, other executable code, and / or other information. In some embodiments, the watch screen may be associated with the user 123 and / or associated with the user wallet. The display component 118 may be further configured to take no further action to facilitate the display of the watch face on the watch screen in response to the user wallet not holding the non-fungible token associated with the watch face, such that the watch face is not displayed on the watch screen

[0039] The input component 120 can be configured to receive user input from an administrative user. For example, the user input can include entering and / or selecting specific information, watch face designs, values ​​for watch face features, watch faces, and / or any entity or object that interacts with any portion of the system 100 and / or plays a role in the operation of the system 100. For example, an administrative user can select a specific set of watch face designs and / or values ​​for watch face features as input to other components of the system 100, such as the presentation component 108. In addition, the administrative user can select a specific adjustment displayed by the presentation component 108 (e.g., a cost to increase one or more values ​​of a watch face feature).

[0040] The communication component 122 can be configured to facilitate communication and / or interaction between the management server 115 and the rest of the system 100. For example, the communication component 122 can transmit user input received by the input component 120 to other components of the system 100.

[0041] Figure 4 4 shows an exemplary selection interface 400 that can be used by the system to create a custom watch face and retrieve a watch face to be displayed according to one or more embodiments. In some embodiments, the selection interface 400 can be presented in a manner similar to the user interface 125 (e.g., Figure 1 In some embodiments, the user may view the selection interface 400 through a web browser, a mobile browser, a mobile application, and / or other platform. In some embodiments, the user may need to create and / or log in to a user account associated with the user to access the selection interface 400. The user account may be specific to the distributed computing platform and / or system 100 (e.g., Figure 1 ). A user account associated with a user may also be associated with a user wallet. In some embodiments, the user account and / or the user wallet may store the user's inventory. The user's inventory may include one or more watch faces that the user has purchased and / or currently owns (i.e., the user wallet holds a non-fungible token indicating a watch identifier associated with the watch face). In some embodiments, a user account may be used to store an association with one or more watches, watch screens, and / or other devices capable of displaying a watch face. One or more devices associated with a user account may be capable of displaying one or more watch faces owned by the user.

[0042] refer to Figure 4, the selection interface 400 may include one or more dial features 40a-40b and / or other dial features. For example, dial feature 40a may indicate a selection for "hour and minute hands", and dial feature 40b may indicate a selection for "hour markings". The selection interface 400 includes values ​​42a-42e for dial feature 40a, values ​​44a-44e for dial feature 40b, and / or other values. In some embodiments, individual values ​​of values ​​42a-42e may indicate variations of dial feature 40a that can be selected by a user, and individual values ​​of 44a-44e may indicate variations of dial feature 40b. For example, values ​​42a-42e each correspond to different styles and / or types of hour and minute hands that can be included in a dial design and / or a displayed dial. In some embodiments, a user may select one or more values ​​for individual dial features, may not select any values ​​for individual dial features, and / or may select exactly one value for individual dial features.

[0043] In some implementations, selection of a particular value may include clicking, touching, tapping, and / or sliding an action button associated with that value and / or other actions. Figure 4 , the selection interface 400 may include check marks 43, 45, and / or other check marks and / or components. Check mark 43 may indicate that the user has selected value 42b for dial feature 40a, and check mark 45 may indicate that the user has selected value 44c for dial feature 40b. In some embodiments, the user may select values ​​for one or more dial features before submitting a casting request. In some embodiments, dial features for which the user has not selected values ​​may be randomly selected by the system during casting of the dial. In some embodiments, the dial features may include an hour hand, a minute hand, a splash guard, a dial, subdials, hour markers, a weather display, a date display, a score display (e.g., a score for a sports game), a stock price display, and / or other dial components.

[0044] Figure 5 An exemplary watch 500 is shown including a watch screen displaying a watch face 54, which can be used by the system to create a custom watch face and retrieve a watch face to be displayed according to one or more embodiments. The watch 500 may include a watch band 50, a watch screen 52, and / or other components. The watch screen 52 may be displayed in conjunction with the user's watch screen 127 (e.g., Figure 1 The watch screen 52 may be held by the frame 51 and / or other housings and / or holders. In some embodiments, the watch screen 52 may have a square shape, a rectangular shape (such as Figure 5), a circular shape, an oval shape, and / or other shapes. The watch screen 52 can be configured to display a dial 54 and / or other dials and / or content. The dial 54 may include one or more dial features. The dial features may include one or more of hour markers 55, a splash guard 56, a minute hand 57, a date display 58, an hour hand 59, and / or other components of the dial 54. In some embodiments, the value of one or more dial features may be selected by a user through a selection interface that is the same or similar to the selection interface 400. In some embodiments, the dial 54 may be adjusted before being displayed on the watch screen 52. The size, arrangement, orientation, and / or other aspects of the dial 54 may be adjusted so that the dial 54 is optimally displayed on the watch screen 52. In some embodiments, the dial 54 may be adjusted by one or more computer program components (e.g., display component 118) included in the system 100 and / or one or more computing program components included in the watch 500. Adjustment of dial 54 may be based on the size, shape, type, and / or other aspects of watch 500 , dial 54 , and / or other information.

[0045] refer to Figure 1 , user interface 125 can be configured to facilitate interaction between user 123 and system 100 and / or between user 123 and client computing platform 104. In some embodiments, user interface 125 can include one or more of a display screen, a touch screen, a monitor, a keyboard, buttons, switches, knobs, a joystick, a mouse, a microphone, a sensor for capturing voice commands, a sensor for capturing body movements, a sensor for capturing hand and / or finger gestures, and / or other user interface devices configured to receive and / or communicate user input. In some embodiments, one or more user interfaces 125 can be included in one or more client computing platforms 104. In some embodiments, one or more user interfaces 125 can be included in system 100. In some embodiments, user interface 125 can be a type of interface that facilitates the exchange of virtual items between users.

[0046] refer to Figure 1 In some embodiments, the server 102, the client computing platform 104, the management server 115, the decentralized ledger server 111, and / or the external resource 126 may be operably connected via one or more electronic communication links. For example, such electronic communication links may be established at least in part via one or more networks 116 (such as the Internet and / or other networks). It should be understood that this is not intended to be limiting, and the scope of the present disclosure includes embodiments in which the server 102, the client computing platform 104, the management server 115, the decentralized ledger server 111, and / or the external resource 126 may be operably connected via some other communication medium.

[0047] A given client computing platform 104 may include one or more processors configured to execute computer program components. The computer program components may be configured to enable an expert or user associated with a given client computing platform 104 to interface with the system 100 and / or external resources 126, and / or to provide other functionality attributed herein to the client computing platform 104. As non-limiting examples, a given client computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a netbook, a smart phone, a game console, and / or other computing platforms.

[0048] The management server 115 may include one or more of the server 102a, the processor 130a, the machine-readable instructions 106a, the electronic storage 128a, and / or other components. The server 102a may be configured by the machine-readable instructions 106a. The machine-readable instructions 106a may include one or more instruction components. The instruction component may include one or more of the input component 120, the communication component 122, and / or other instruction components. The management server 115 may include a communication line or port to enable information to be exchanged with a network and / or other computing platform. In some embodiments, the management server 115 may be used by one or more management users, for example, to configure and / or control the operation of the system 100. In some embodiments, the management server 115 may include or user one or more user interfaces to receive user input and / or otherwise interact with one or more management users. In some embodiments, one or more management users may be able to modify the associated cost of the value of the dial feature, the cost of the pre-selected dial design, and / or make other modifications. In some embodiments, one or more management users may be able to trade consideration and / or value from and / or to a management wallet.

[0049] External resources 126 may include information sources external to system 100, external entities participating in system 100, external providers of computing and / or storage services, and / or other resources. In some embodiments, some or all of the functionality attributed herein to external resources 126 may be provided by resources included in system 100. In some embodiments, external resources 126 may include one or more blockchain oracles.

[0050] Server 102 may include communication lines or ports to enable information to be exchanged with a network and / or other computing platforms. Figure 1 The illustration of the server 102 in is not intended to be limiting. The server 102 may include multiple hardware, software, and / or firmware components that operate together to provide the functionality attributed herein to the server 102. For example, the server 102 may be implemented by a cloud as a computing platform with which the server 102 operates.

[0051] Electronic storage 128 may include non-transitory storage media that electronically stores information. The electronic storage media of electronic storage 128 may include one or both of system memory provided integrally (i.e., substantially non-removable) with server 102 and / or removable storage that may be removably connected to server 102 via, for example, a port (e.g., a USB port, a FireWire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 128 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, a magnetic hard drive, a floppy disk drive, etc.), charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drives, etc.), and / or other electronically readable storage media. Electronic storage 128 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and / or other virtual storage resources). Electronic storage 128 may store software algorithms, information determined by processor 130, information received from server 102, information received from client computing platform 104, and / or other information that enables server 102 to function as described herein.

[0052] Processor 130 may be configured to provide information processing capabilities in server 102. Thus, processor 130 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and / or other mechanisms for electronically processing information. Figure 1 130 is shown as a single entity, but this is for illustration purposes only. In some embodiments, processor 130 may include multiple processing units. These processing units may be physically located in the same device, or processor 130 may represent the processing functions of multiple devices operating in coordination. Processor 130 may be configured to execute components 108, 110, 112, 114, 116, 118, 120 and / or 122, and / or other components. Processor 130 may be configured to execute components 108, 110, 112, 114, 116, 118, 120 and / or 122 and / or other components by software, hardware, firmware, some combination of software, hardware and / or firmware and / or other mechanisms for configuring the processing power on processor 130. As used herein, the term "component" may refer to any component or group of components that perform the functions attributed to the component. This may include one or more physical processors, processor-readable instructions, circuits, hardware, storage media, or any other components during the execution of processor-readable instructions.

[0053] It should be understood that although components 108, 110, 112, 114, 116, 118, 120, and / or 122 are Figure 1 108, 110, 112, 114, 116, 118, 120, and / or 122 may be implemented remotely from other components. The description of functionality provided by different components 108, 110, 112, 114, 116, 118, 120, and / or 122 described below is for illustrative purposes and is not intended to be limiting, as any of the components 108, 110, 112, 114, 116, 118, 120, and / or 122 may provide more or less functionality than described. For example, one or more of the components 108, 110, 112, 114, 116, 118, 120, and / or 122 may be eliminated, and some or all of their functionality may be provided by other of the components 108, 110, 112, 114, 116, 118, 120, and / or 122. As another example, the processor 130 may be configured to execute one or more additional components that may perform some or all of the functionality attributed below to one of the components 108, 110, 112, 114, 116, 118, 120, and / or 122.

[0054] Figure 2 A method 200 for creating a custom watch face according to one or more embodiments is shown. The custom watch face can be recorded on a decentralized ledger. The custom watch face can be displayed on a watch screen. The operations of method 200 presented below are intended to be illustrative. In some embodiments, method 200 may be accomplished with one or more additional operations not described and / or one or more operations not discussed. Additionally, Figure 2 The order of the operations of method 200 is shown in FIG. 1 and the following description is not intended to be limiting.

[0055] In some embodiments, method 200 may be implemented in one or more processing devices (e.g., digital processors, analog processors, digital circuits designed to process information, analog circuits designed to process information, state machines, and / or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices that perform some or all of the operations of method 200 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured by hardware, firmware, and / or software to be specifically designed to perform one or more operations of method 200.

[0056] Operation 202 may include enabling presentation of a selection interface on a client computing platform associated with a user. The selection interface may facilitate user input and / or selection of a watch face design. The watch face design may be defined by values ​​of watch face features. Operation 202 may be performed by a presentation component 108 (in Figure 1 This can be done using the same or similar presentation components as shown in and described herein.

[0057] Operation 204 may include receiving a casting request from a client computing platform to cast a watch face according to a watch face design input and / or selected through a selection interface. Operation 204 may be performed by a transaction component 110 (in Figure 1 and described herein).

[0058] Operation 206 may include, in response to receiving the minting request, effecting a transfer of consideration from a user wallet associated with the user to an admin wallet. The user wallet and the admin wallet may each correspond to an address on a decentralized ledger, such that the transfer of consideration involves a transfer of value on the decentralized ledger from an address associated with the user wallet to an address associated with the admin wallet. Operation 206 may be performed by a transaction component 110 (at Figure 1 and described herein).

[0059] Operation 208 may include minting a watch face in response to the management wallet receiving the consideration. Minting the watch face may include generating a watch face record for the watch face according to the watch face design. The watch face record may include values ​​defining watch face features of the watch face design. The watch face record may include a watch face identifier. Operation 208 may be performed by a minting component 112 (at Figure 1 The same or similar casting assembly as shown in and described herein can be used.

[0060] Operation 210 may include transferring a non-fungible token indicating the dial identifier to an address on a decentralized ledger corresponding to a user wallet. Operation 210 may be performed by a minting component 112 (at Figure 1 The same or similar casting assembly as shown in and described herein can be used.

[0061] Figure 3 A method 300 for retrieving a watch face to be displayed on a watch screen is shown in accordance with one or more embodiments. The operations of method 300 presented below are intended to be illustrative. In some embodiments, method 300 may be accomplished with one or more additional operations not described and / or one or more operations not discussed. Additionally, Figure 3 The order of the operations of method 300 is shown in FIG. 1 and the following description is not intended to be limiting.

[0062] In some embodiments, method 300 may be implemented in one or more processing devices (e.g., digital processors, analog processors, digital circuits designed to process information, analog circuits designed to process information, state machines, and / or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices that perform some or all of the operations of method 300 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured by hardware, firmware, and / or software to be specifically designed to perform one or more operations of method 300.

[0063] Operation 302 may include receiving a display request to display a watch face on a watch screen. The display request may indicate a particular watch face, a user associated with the watch screen, and / or other information. Operation 302 may be performed by receiving component 114 (at Figure 1 This can be done using the same or similar receiving components as shown in and described herein.

[0064] Operation 304 may include, in response to receiving the display request, determining whether a user wallet of the decentralized ledger holds a non-fungible token associated with a particular watch face. The user wallet is associated with the user. Operation 304 may be performed by the verification component 116 (at Figure 1 This can be done using the same or similar authentication components as shown in and described herein.

[0065] Operation 306 may include facilitating display of the watch face on the watch screen in response to the user wallet holding a non-fungible token associated with the watch face. Facilitating display of the watch face may include initiating transmission of information to the watch screen that causes the watch screen to display the watch face. Operation 306 may be performed by a user associated with display component 118 (in Figure 1 This can be done using display components that are the same or similar to those shown in and described herein.

[0066] Operation 308 may include, in response to the user wallet not holding a non-fungible token associated with the watch face, taking no further action to facilitate display of the watch face on the watch screen, such that the watch face is not displayed on the watch screen. Operation 308 may be performed by a user associated with display component 118 (in Figure 1 This can be done using display components that are the same or similar to those shown in and described herein.

[0067] Although the present technology has been described in detail for purposes of illustration based on what is presently considered to be the most practical and preferred embodiments, it is to be understood that such details are intended only for that purpose and that the technology is not limited to the disclosed embodiments, but rather is intended to cover modifications and equivalent arrangements within the spirit and scope of the appended claims. It should be understood that the present technology contemplates that, to the extent possible, one or more features of any embodiment may be combined with features of any other embodiment.

Claims

1. A system for retrieving a watch face to be displayed, the system comprising: One or more processors configured by machine-readable instructions to: receiving a display request to display the watch face on a watch screen, wherein the display request indicates a specific watch face and a user associated with the watch screen; In response to receiving the display request, determining whether a user wallet of a decentralized ledger holds a non-fungible token associated with the particular watch face, the user wallet being associated with the user; and In response to the user wallet holding the non-fungible token associated with the watch face, facilitating display of the watch face on the watch screen, wherein facilitating display of the watch face includes initiating transmission of information to the watch screen that causes the watch screen to display the watch face.

2. The system according to claim 1, wherein: In response to the user wallet holding the non-fungible token associated with the watch face, the user is able to sell, trade, and transfer ownership of the watch face to another user.

3. The system according to claim 1, wherein: The decentralized ledger is configured to record information associated with the watch face, wherein the recorded information includes ownership of the watch face by holding the non-fungible token associated with the watch face, and the one or more processors are further configured to enable at least some actions of selling, trading, or transferring the watch face performed by the user to modify the recorded information associated with the watch face.

4. The system according to claim 1, wherein: The watch face is a custom watch face generated according to a watch face design determined by values ​​of watch face features, and the values ​​of the watch face features determine the appearance of the custom watch face.

5. The system according to claim 4, wherein: The dial features include one or more of an hour hand, a minute hand, a splashback, a dial, subdials, hour markers, a weather display, or a date display.

6. The system according to claim 4, wherein: The values ​​of the dial features that determine the dial design are selected by the user through a selection interface, or are determined randomly.

7. The system according to claim 1, wherein: The watch dial is associated with a watch dial record, the watch dial record including a watch dial identifier unique to the watch dial.

8. The system according to claim 1, wherein: The decentralized ledger includes recorded information related to the dial, including ownership and distribution rights.

9. The system according to claim 1, wherein: The user wallet is connected to an external wallet, wherein the user wallet retrieves funds from and deposits funds into the external wallet, and the external wallet allows the user to manage funds on a public decentralized ledger.

10. The system according to claim 9, wherein: The public decentralized ledger is part of the EOSIO mainnet, the Ethereum mainnet, Ethereum 1.5, Ethereum 2.0, a derivative of Ethereum 2.0 configured to conduct Ether (ETH) transactions between accounts, or a derivative of EOSIO configured to conduct EOS transactions between different accounts.

11. A method for retrieving a watch face to be displayed, the method comprising: receiving a display request to display the watch face on a watch screen, wherein the display request indicates a specific watch face and a user associated with the watch screen; In response to receiving the display request, determining whether a user wallet of a decentralized ledger holds a non-fungible token associated with the particular watch face, the user wallet being associated with the user; and In response to the user wallet holding the non-fungible token associated with the watch face, facilitating display of the watch face on the watch screen, wherein facilitating display of the watch face includes initiating transmission of information to the watch screen that causes the watch screen to display the watch face.

12. The method according to claim 11, wherein: In response to the user wallet holding the non-fungible token associated with the watch face, the user is able to sell, trade, and transfer ownership of the watch face to another user.

13. The method according to claim 11, wherein: The decentralized ledger is configured to record information associated with the watch face, wherein the recorded information includes ownership of the watch face by holding the non-fungible token associated with the watch face, and the one or more processors are further configured to enable at least some actions of selling, trading, or transferring the watch face performed by the user to modify the recorded information associated with the watch face.

14. The method according to claim 11, wherein: The watch face is a custom watch face generated according to a watch face design determined by values ​​of watch face features, and the values ​​of the watch face features determine the appearance of the custom watch face.

15. The method according to claim 14, wherein: The dial features include one or more of an hour hand, a minute hand, a splashback, a dial, subdials, hour markers, a weather display, or a date display.

16. The method according to claim 14, wherein: The values ​​of the dial features that determine the dial design are selected by the user through a selection interface, or are determined randomly.

17. The method according to claim 11, wherein: The watch dial is associated with a watch dial record, the watch dial record including a watch dial identifier unique to the watch dial.

18. The method according to claim 11, wherein: The decentralized ledger includes recorded information related to the dial, including ownership and distribution rights.

19. The method according to claim 11, wherein: The user wallet is connected to an external wallet, wherein the user wallet retrieves funds from and deposits funds into the external wallet, and the external wallet allows the user to manage funds on a public decentralized ledger.

20. The method according to claim 19, wherein: The public decentralized ledger is part of the EOSIO mainnet, the Ethereum mainnet, Ethereum 1.5, Ethereum 2.0, a derivative of Ethereum 2.0 configured to conduct Ether (ETH) transactions between accounts, or a derivative of EOSIO configured to conduct EOS transactions between different accounts.

Images