authentication

Abstract

Disclosed is a user authenticator device for use in authenticating a user's identity and / or an asset, comprising: a plurality of different machine-readable unique identifiers provided on or in the device, each containing or encoding different ID information for identifying the authenticator device. Also disclosed is a method and system for authenticating a user identity using the authenticator device, a method and system for authenticating an asset using the authenticator device, methods of secure transaction and sign in using the authenticator device, and a physical media asset, such as a vinyl record, having machine-readable unique identifiers containing information for authenticating the physical media asset.

Description

[0001] AUTHENTICATION

[0002] Technical Field

[0003] The invention relates generally to an authenticator device having machine-readable unique identifiers containing information for authenticating a user identity, a method and system for authenticating a user identity using the authenticator device, a method and system for authenticating an asset, methods of secure transaction and sign in using the authenticator device, and a physical media asset, such as a vinyl record, having machine-readable unique identifiers containing information for authenticating the physical media asset.

[0004] Background to the Invention

[0005] Authentication is a process by which the claimed identity and attributes of a product, asset or a person are verified. Authentication is used in many contexts, but in particular for verifying whether or not a product or asset is genuine or fraudulent, proving ownership of a product or asset, track and trace, and preventing unauthorised parties from gaining access to secured databases, systems or facilities.

[0006] Reliable methods of proving authenticity and ownership are particularly relevant to certain high value collectable physical assets, such as limited-edition artworks or unique productions. With the evolution of digital assets, artwork and blockchain, non-fungible tokens (NFTs) have become a popular secure means to assign and demonstrate uniqueness and value. However, there is no analogue equivalent for physical assets, artworks, in particular physical media assets containing audio and / or video recordings.

[0007] For example, certain physical media assets such as vinyl records have had a resurgence in recent years due to users / fans wanting better quality audio, a desire for ownership of a physical music product and something to show off and ritualise. Certain vinyl albums can be traded for high value based on factors such as the artist, age, edition, and history / provenance (e.g. past owners) of the album. For example, Discogs (https: / / w w w .discogs.co / ) is the world's largest database marketplace for vinyl and other disc-based media, which lists vinyl albums for sale and facilitates purchasing. However, often the authenticity of the seller’s identity, the ownership and the provenance of the physical asset is taken on trust and is difficult to verify. In some cases, even the existence of the physical media asset listed for sale with its claimed attributes is taken on trust. For example, a new copy of an old vinyl album could be sold with an old sleeve / packaging to give the impression of authenticity, when in fact it is a fake. Historically the most granular identifier on a vinyl is typically the scratched or engraved manufacturing batch number on the central run out area. Owners have to go to great lengths to try to catalogue and distinguish their collections, for example, photographing and dating the vinyl, noting the etched batch number and any other identifying features to help establish authenticity and provenance. The same is true for other physical media assets such as cassettes, video tape, CD and DVD, all of which can be desirable collectable items. There is therefore a need for an improved method of authenticating the veracity of an asset, such as a physical media and other products, and proving ownership thereof. There is also a need for an improved method of secure transaction of an asset, such as physical media assets and other products, and verifying the identity of an individual. Aspects and embodiments of the present invention have been devised with the foregoing in mind.

[0008] Summary of the Invention

[0009] According to a first aspect of the invention, there is provided a physical media asset comprising: a storage medium for storing a copy of a media recording; and one or more machine-readable unique identifiers provided on or in preferably a non-playing area, portion or surface of the storage medium, the one or more unique identifiers containing or encoding information for identifying the asset and / or the copy from all other copies of the media recording.

[0010] A physical media asset may be defined as a physical consumer product / item of manufacture that stores, in persistent physical form, a copy of an audio / video recording, such as a vinyl, optical disc or cassette (as opposed to a digital media asset which may exist only in virtual / electronic form and can be arbitrarily downloaded to a memory device). The physical media asset comprises a playing area, portion or surface having certain physical, optical or magnetic properties that stores the recording and which interacts with a media player to playback the recording, and a non-playing area, portion or surface, as is known in the art. In this context, a “copy” of a media recording means a genuine copy produced from a master as a one-off production or as part of a batch (e.g. multiple vinyl records are typically pressed from a stamp representing a master of the media recording, thereby creating a copy). In contrast, a fake physical copy may be produced from a genuine copy or a digital copy of an original copy.

[0011] The provision of machine-readable unique identifiers (UIDs) on the asset allows the authenticity and ownership of the asset to be verified in a secure and reliable manner, e.g. when used as part of an authentication system described in more detail below. In particular, the physical media asset and / or the storage medium may be or comprise a phonograph record disc (e.g. a vinyl record), an optical disc (e.g. CD or DVD, or Blu Ray), a cassette (e.g. audio and / or video cassette), or any other physical medium for storing a physical copy of an audio / video recording. All of which can be collectable and high-value items whose authenticity and ownership should preferably be verified before (and even after) any transaction takes place, yet traditionally such items are difficult to authenticate. In practice, the physical media asset is registered to a user who is the designated “owner” of the asset, whereby the information associated with the asset and the information contained in its UIDs is stored in a secure online database and associated with the user. The information contained in the UIDs can be read or scanned by a suitable device (e.g. by a computing device with a camera and / or other readers) and cross-referenced against the stored ID information associated with the user’s registered asset to verify the authenticity and ownership of the asset. As all the information associated with the asset is stored in the database and linked to the user, if an asset is damaged, destroyed or lost, it can be replaced with an exact copy by the supplier with new identifiers linked to the user’s account. The approach can be applied to new physical media assets, whereby UIDs are provided / applied as part of the manufacture process, or to pre-existing physical media assets whereby UIDs can be applied retrospectively.

[0012] This approach enables physical media asset collections to be memorialised, e.g. when handing on a collection of physical media assets to beneficiaries of wills. Rather than having to itemise each asset sometime before death, each asset is recorded in the user database and can be associated with a value. Associating a value with the user’s assets in the database can also assist in insuring the collection by allowing insurance companies to know the value of individual assets or a collection at the time of insurance.

[0013] The physical media asset can also comprise packaging (e.g. a sleeve, box, case etc.), which may also be provided with one or more machine-readable UIDs containing information for identifying the packaging. The information in the UIDs on the packaging is preferably linked with the storage medium in the database (and to the user’s database account). Thus, the packaging can be matched to the storage medium to further assist in proving authenticity of the asset.

[0014] Preferably, the asset comprises a plurality of different machine-readable UIDs, each containing different information for identifying the asset and / or the copy. In one example, the asset comprises at least four or at least six different UIDs.

[0015] Providing multiple different UIDs adds additional levels and factors of security to authenticate the asset. For example, much like online multi-factor verification techniques, while it might be possible for an unauthorised person to circumvent one type of UID, it is less likely for them to circumvent two different types of UIDs, and even less likely to circumvent three, and so on.

[0016] Preferably, the one or more machine-readable UIDs include at least a physical unclonable function (PUF) tag, such as a nanoparticle or quantum dot-based PUF tag; and / or a surface topographybased tag. Such tags are particularly difficult to clone or simulate. Such tags are also optically readable, i.e. readable using an optical reader or imaging device, such as a camera on a conventional smartphone or mobile device. The surface topography-based tag may be or comprise a textured surface of the asset (e.g. provided by naturally or intentionally textured material).

[0017] The one or more machine-readable UIDs may include a radio frequency identification (RFID) tag. An RFID tag can be read with an RFID reader, which may, for example, be incorporated with a mobile device such as a smartphone. The one or more machine-readable UIDs may include a nearfield communication (NFC) tag, that can be read with an NFC reader e.g. on a mobile device.

[0018] The one or more machine-readable UIDs may include at least one (i.e. any combination) from the following list of UIDs: an encoded image, such as a QR code; a symbol sequence or alphanumeric code; a production sequence number associated with the asset; a unique graphic or image; a fingerprint (e.g. the user’s or owner’s fingerprint); and a pattern of holes or indentations, optionally or preferably, wherein the holes or indentations have different or congruent shapes. The unique symbol sequence or graphic may be or comprise a unique set or combination of hieroglyphs. A hieroglyph is defined herein as a pictorial character. All of these UIDs are also optically readable.

[0019] In particular, providing a production sequence number associated with the physical media asset not only allows the specific asset to be identified from all other copies made in a production run / batch but also the specific position / order of the asset in the production / manufacture sequence. For example, the production sequence number may indicate whether a vinyl is the first pressing in a run or the 100th pressing or the 10,000th pressing, etc.

[0020] The unique set or combination of hieroglyphs may be selected from a larger set or dictionary / library of hieroglyphs. Each hieroglyph in the larger set may itself be unique or bespoke / custom. Preferably, the set or dictionary of hieroglyphs contains at least 500 or 1000 different hieroglyphs. The hieroglyphs may be coloured, greyscale, and / or have varying pixelation (which may be used in combination in the set). One or more of the hieroglyphs may be combined or overlaid, optionally in different orientations, to provide a composite hieroglyph formed of multiple component hieroglyphs. The composite hieroglyph may extend the library of bespoke hieroglyphs. Alternatively, the composite hieroglyph may serve to obfuscate the component hieroglyphs, requiring image analysis / processing to detect and determine / extract the component hieroglyphs.

[0021] Preferably, at least some of the one or more UIDs are integrated with one or more labels attached to a non-playing area, portion or surface of the storage medium. In this context, integrated with a label means to form part of the label or be attached or connected to the label. For example, a UID may be applied to or form part of the outer surface of the label, or it may be located on an underside of the label, or it may be embedded within the label, e.g. sandwiched or laminated between single or multiple layers of opaque or transparent material of the label. Where the one or more UIDs includes an RFID tag and / or NFC tag, this may be located beneath a label attached to the non-playing area, portion or surface of the storage medium or embedded within the label.

[0022] Alternatively or additionally, at least some of the one or more UIDs may be embedded within the storage medium itself, preferably a non-playing surface / region of the storage medium. Preferably, an RFID tag is embedded within an insert that is located / secured (permanently or releasably) within a recess or depression in a (non-playing) surface of the storage medium. The insert is preferably located beneath a label which may comprise further UIDs. Locating the insert and / or the RFID and / or NFC tag beneath the label may help to prevent tampering with the UIDs.

[0023] Preferably, the dimensions of the insert substantially match the dimensions of the recess or depression such that, when secured or fitted within the recess or depression, it provides or forms a substantially smooth outer surface of a non-playing area of the storage medium to which a label can be attached / applied.

[0024] The insert may be or comprise a multilayer structure including a first layer and a second layer, wherein the RFID tag and / or the NFC tag is located between the first and second layers. The insert may be formed of the same material as the storage medium, or a different material. Optionally, the physical media asset may further comprise a unique silk thread located in the recess beneath the insert. The silk thread comprises one or more unique features such as a weave, knot, dye, or biological material (e.g. saliva, blood, etc.), that can be analysed upon removable of the insert to identify the physical media asset.

[0025] Alternatively or additionally, an optically readable UID, such as a PUF or unique graphic (e.g. unique set or combination of hieroglyphs), may be embedded with the insert. In this case, at least the material of the insert above the embedded UID is transparent to facilitate its reading. Where both an RFID tag (and / or NFC tag) and an optically readable UID are embedded in an insert, these may be embedded in the same insert or in different inserts.

[0026] Preferably, where the storage medium is a phonograph record disc, such as a vinyl, at least some of the one or more UIDs are integrated with a label attached to the central (non-playing) area / surface of the record disc. In this case, where the asset further includes one or more UIDs embedded in one or more inserts, these may be located beneath the label and otherwise embedded in the central (non-playing) area.

[0027] It will be appreciated from the foregoing and the below that the invention is not limited to physical media assets comprising storage mediums, but can also be applied to physical assets in general such as: physical artworks, merchandise, memorabilia, a physical product, and / or a physical document such as a deed, contract, agreement, pledge, certificate, or accreditation. Such physical assets can similarly comprise machine-readable UIDs (optical or RF) attached thereto, each containing different information for identifying the physical asset. Similarly, the various aspects of the invention can alternatively or additionally be applied to digital assets, which may be embedded with one or more optically readable UIDs each containing or encoding different information for identifying the asset.

[0028] According to another aspect of the invention, there is provided, an insert for a physical media asset as defined in the first aspect. The insert comprises one or more unique identifiers embedded therein, the one or more unique identifiers containing information for identifying the physical media asset (or the copy of the media recording). The insert may be configured to fit into a recess in a surface of a (preferably) non-playing area of the storage medium of the physical media asset. Optionally or preferably, the dimensions of the insert substantially match the dimensions of the recess so as to provide a substantially smooth surface of the non-playing area of the storage medium.

[0029] The insert may be or comprise a multilayer structure including a first layer and a second layer, wherein the one or more unique identifiers are located between the first and second layers. Preferably, the one or more unique identifiers include an RFID tag. The insert may include any further features described above in the first aspect. According to a second aspect of the invention there is provided an authenticator device for use in authenticating a user’s physical asset or physical media asset, and / or for use in verifying a user’s identity. The authenticator device comprises one or more machine-readable UIDs provided on or in the authenticator device containing or encoding ID information for identifying the authenticator device. The authenticator device may be a handheld device.

[0030] The authenticator device is configured to be used in conjunction with an authentication system described in more detail below to verify the authenticity and ownership of an asset, such as a user’s physical (e.g. media) or digital asset, and / or to authenticate / verify a user’s identity in a secure and reliable manner. The authenticator device is associated with specific user, and is unique to that user. That is, no two authenticator devices carry the same ID information as a whole in their UIDs. The authenticator device may thus be referred to as a user and / or personal authenticator device.

[0031] Preferably, the authenticator device comprises a plurality of different machine-readable UIDs, each containing or encoding different information for identifying the authenticator device. Optionally or preferably, the authenticator device comprises at least four or at least six different UIDs.

[0032] Preferably, the one or more machine-readable UIDs include at least a physical unclonable function (PUF) tag, such as a nanoparticle or quantum dot-based PUF tag, and / or a surface topographybased tag. The surface topography-based tag may be or comprise a textured surface of the asset (e.g. provided by naturally or intentionally textured material). The one or more machine-readable UIDs may include a RFID tag and / or an NFC tag. The one or more machine-readable UIDs may include at least one (i.e. any combination) from the following list of UIDs: an encoded image, such as a QR code; a symbol sequence or alphanumeric code; a unique graphic or image; a fingerprint (e.g. the user’s or owner’s fingerprint); a microchip; and a pattern of holes or indentations, optionally or preferably, wherein the holes or indentations have different or congruent shapes. The unique symbol sequence or graphic may be or comprise a unique set or combination of hieroglyphs. One or more of the hieroglyphs may be a composite hieroglyph as described above. All of these UIDs may also be optically readable.

[0033] Preferably, the authenticator device comprises a main body with one or more internal compartments for housing one or more of the machine-readable unique identifiers. The main body may comprise a window through which one or more of the machine-readable unique identifiers housed within the internal compartments are readable by a reader device. The window may comprise an optically transparent material and / or a cover moveable between an open position in which the window is substantially open and a closed position in which the window is substantially closed.

[0034] At least one of the one or more of the machine-readable unique identifiers housed within the internal compartments may include an optical element comprising portions or areas of different optical properties arranged to form a first optical identifier readable through the window. The optical properties may include one or more of a transparency, opacity, colour, fluorescence, etc. The device may further comprise an internally mounted light emitting device to illuminate the first optical element.

[0035] The device may comprise an adjustable occluder arranged and configured to occlude a portion or area of the one or more of the machine-readable unique identifiers located behind the window in dependence on a position of the occluder relative to the window. The occluder is preferably rotatable relative to the window.

[0036] Preferably, the authenticator device comprises a main body with one or more internal compartments configured to receive (and store) one or more drawers, wherein at least some of the one or more machine-readable UIDs of the authenticator device are provided on or in the drawers. The drawers are preferably removable and / or interchangeable. Each UID may be provided on or in a separate drawer, or each drawer may comprise a separate UID. In this way, the UIDs can be stored within the body of the authenticator device and protected from the external environment. This may in turn prevent or reduce damage to, and slow any degradation of, the UIDs that may occur over time.

[0037] Preferably, the one or more drawers are moveable between an open position in which the respective UIDs provided therein are located outside of the main body and readable, e.g. by a reader device such as a mobile device, and a closed position in which the UIDs are located inside the main body.

[0038] A drawer may be any element for carrying, supporting or holding a UID which can fit into and be removed from an internal compartment of the main body to provide access to the UID, e.g. by a sliding or pivoting movement. E.g. a carrier, holder, or tray etc.

[0039] The one or more drawers may be received through one or more respective openings in the main body. The one or more drawers may be configured to close, and optionally seal, the one or more respective openings when in the closed position. Closing or sealing the opening to the internal compartments further assists in protecting the UIDs.

[0040] Preferably, each drawer comprises a carrier portion on which at least one of the one or more UIDs is provided. Each carrier portion may be configured to rotate relative to the respective drawer so as to adjust the orientation of the UID relative to the respective drawer. The carrier portion may be configured to rotate between at least 4, 6 or 8 (stable) positions / orientations.

[0041] Adjusting the orientation of the UIDs adds a further level of security whereby the orientation of, and the information contained in, the UID can be read and combined as part of the authentication process. For example, a user may be requested to scan / read a particular UID in a particular drawer in a particular orientation, as described in more detail below.

[0042] Preferably, each carrier portion comprises a set of markings (e.g. graduations) to visually identify the relative orientation. For example, the carrier portion may be substantially circular and its markings may extend along the periphery of the carrier portion. The drawer may also include at least one marking adjacent to the carrier portion to enable a relative orientation of the carrier portion to be read / determined. The markings can be captured by the reader (e.g. mobile device camera) and used to determine the relative orientation.

[0043] The one or more machine-readable unique identifiers may include one or more machine-readable multi-state identifiers configured to provide or produce unique ID information in a static state when read that is changeable in response to a user interaction with the device that causes a change in the static state; and optionally or preferably, wherein the user interaction is one or more of a press, push, roll, rotation shake or rub. The multi-state identifiers preferably comprise one or more adjustable, moveable and / or mobile elements that form part of a unique optical identifier in a static state to be scanned / read, and provide or produce a change in the overall configuration of the unique optical identifier (and its ID information) in response to a user interaction with the multistate identifier that changes the static state of the adjustable, moveable and / or mobile elements. The adjustable, moveable and / or mobile elements may comprise, mobile particles, mobile fluids, movable optical elements, or rotatable dials, as described in more detail below.

[0044] The one or more machine-readable multi-state identifiers may include an optical device, comprising: a first optical element housed within an internal compartment of the device behind a window of the device, the first optical element comprising portions of different optical properties arranged to form a first optical identifier, and wherein at least a portion of the first optical element is substantially transparent; a second optical element arranged within the internal compartment behind the first optical element, the second optical element including portions of different optical properties arranged to form a second optical identifier such that first and second optical identifiers superimpose to form a unique optical identifier that is readable through the window. The position of at least one of the first and second optical elements is adjustable, preferably in predefined increments, relative to the other so as to change the static state of the unique optical identifier in dependence on a relative position of the first and second optical elements. Optionally or preferably, the at least one of the first and second optical elements is rotatable relative to the other. Preferably, the device further comprises an adjustable occluder arranged and configured to occlude a part or an area of the unique optical identifier in dependence on a position of the occluder relative to the window so as to further change the static state of the unique optical identifier. Preferably, the occluder is rotatable relative to the window. The authenticator device or the optical device may further comprise an internally mounted light emitting device to illuminate the first and second optical element.

[0045] The one or more machine-readable multi-state identifiers may include a fluid device, comprising: an enclosure with a deformable wall, the enclosure containing a mixture of immiscible fluids including at least one liquid, and optionally a plurality of particles, wherein the mixture is configured to form, in a static state, a unique optical identifier readable through a transparent wall of the enclosure, and wherein the unique optical identifier is changeable in response to a force applied to the enclosure that deforms the deformable wall and causes a change in the static state of the immiscible fluids, and optionally the particles, contained therein. In this case, the particles and fluids are mobile elements of the identifier.

[0046] The mixture may include a gas and / or at least two different coloured immiscible liquids. At least some of the particles preferably have different properties including one or more of: size, shape, colour, and other externally visible feature such as a surface pattern. The enclosure may include a static background optical pattern or graphic to visually identify the relative positions of the particles and / or fluids.

[0047] The one or more machine-readable multi-state identifiers may include a shaker device comprising: a hollow enclosure containing therein a plurality of solid particles configured to form, in a static state, a unique optical identifier readable through a transparent wall of the enclosure, and wherein the unique optical identifier is changeable in response to a force applied to the device which causes a change in the static state of the particles within the hollow enclosure.

[0048] The plurality of particles preferably include at least some particles with different properties including one or more of: size, shape, colour, and other externally visible feature such as a surface pattern. The hollow enclosure may include a static background optical pattern to visually identify the relative positions of the particles. The hollow enclosure may include one or more interior portions for receiving and occluding one or more particles during scanning / reading (e.g. opening, tunnels and / or enclosures).

[0049] The hollow enclosure may in some examples comprise a substantially transparent hollow rolling element (such as a spherical or cylindrical element) held by one or more retaining elements such that a portion of the rolling element is externally accessible for reading and receiving a user interaction that rotates the rolling element to thereby cause a change in the static state of the particles contained therein.

[0050] The one or more machine-readable multi-state identifiers may include a roller device, comprising: one or more rolling elements (such as spherical or cylindrical elements) held by one or more retaining elements such that a portion of each rolling element is externally accessible for receiving a user interaction, wherein each rolling element comprises a spatially non-uniform visual feature such that the externally accessible portions of the one or more rolling elements collectively form, in a static state, a unique optical identifier readable by a reader device, and wherein the optical identifier is changeable in response to user interaction that causes a change in a rotational position of at least one of the one or more rolling elements. The spatially non-uniform visual feature of one or more rolling elements may comprise an exterior surface feature and / or an interior feature, such as one or more encapsulated or enclosed internal layers, objects or particles.

[0051] The one or more machine-readable multi-state identifiers may include a deformable topographic surface of the device, comprising: deformable projections or fibres configured to form, in a static state, a unique topographic and / or optical identifier readable by a reader device, and wherein the unique topographic and / or optical identifier is changeable in response to a user interaction with the deformable topographic surface that deforms at least some of the deformable projections or fibres and causes a change in the static state thereof.

[0052] The one or more machine-readable multi-state identifiers may include an integrated musical instrument (sting or wind instrument), playable by the user, configured to produce a sound with a frequency or tone dependent on a position of one or move adjustable elements, e.g. which may affect airflow or engage one or more strings of the instrument in various user positions to influence the vibrational frequency. In this case, the sound is the unique identifier.

[0053] The one or more machine-readable unique identifiers of the authenticator device may include a dynamic machine readable identifier configured with one or more driven / movable elements that interact, preferably with one or more static elements, to provide ID information and / or a unique optical identifier that continuously changes with time.

[0054] Preferably, the dynamic identifier is a clock device, comprising: a first set of machine-readable hands driven by a motor assembly and configured to move in a first direction according to a first movement from a first start time; a second set of machine-readable hands driven by the motor assembly configured to move in a second direction according to a second movement from a second start time that is different to the first start time; and optionally or preferably one or more occluders configured to occlude at least a part of the first and / or second sets of hands in dependence on a position of the first and / or second sets of hands with respective to the one or more occluders. The first and second sets of machine-readable hands, and preferably the one or more occluders, collectively form a unique optical identifier readable by a reader device.

[0055] The first and / or second sets of machine-readable hands may comprise a machine-readable shape and / or one or more optical features. The dynamic identifier may further comprise an integrated compass which forms part of the unique optical identifier.

[0056] Each of the one or more occluders occludes a respective area of the clock. At least one of the one or more occluders may be adjustable so as to vary the respective occluded area. At least one of the one or more occluders may be adjustable in size so as to vary a spatial extent of occluded area.

[0057] At least one of the one or more occluders may be driven by the motor assembly and configured to move (around a clock face of the device) in a third direction according to a third movement. The third movement may include a fixed or time-dependent speed.

[0058] The first and second movements may include a fixed or time-dependent rotary speed. The motor assembly may comprise one or more drive shafts and / or one or more motors for driving the hands and optionally at least one of the occluders.

[0059] Any of the multi-state identifiers and / or the dynamic identifier or identifiers may further comprise a rotatable ring or dial extending around the identifier, wherein the rotatable ring comprising one or more markings or symbols that form part of the unique optical identifier. Optionally or preferably, the markings can comprise at least partially transparent portions of the rotatable ring and the device comprises an internally mounted light emitting device to illuminate a given one of the markings in dependence of the position of the rotatable ring with respect to the light emitting device.

[0060] Preferably, the authenticator device is not connectable to a network such as the internet. The authenticator device may be a passive device, e.g. without a power source or any other active electrical components.

[0061] Alternatively, the authenticator device may be an active device. In this case, the authenticator device may comprise: a power source, an output device e.g. a display, speaker or light emitting device, one or more inputs, and a processor. The device may further comprise an audio output such as a speaker. Preferably, the authenticator device does not include a wireless communication module, or any means to be in connect to a network such as the internet, or be in data communication with a mobile device.

[0062] The processor may be configured to generate, in response to a user input via the one or more inputs, additional ID information for identifying the authenticator device. Preferably, the additional ID information is based, at least in part, on ID information from or contained in one or more of the machine-readable UIDs on / in the authenticator device. The additional ID information may comprise a unique image or dynamic image for outputting on the display. Alternatively or additionally, the additional ID information may comprise an audio signal. The device may comprise one or more light sources or light emitting devices, e.g. to provide backlighting for the one or more inputs or the hieroglyphs.

[0063] According to a third aspect of the invention, there is provided a method of authenticating an asset such as a physical asset or digital asset comprising one or more machine readable UIDs containing ID information for identifying the asset. In one embodiment, the physical asset is a physical media asset as defined in the first aspect, and the terms can be exchanged accordingly. References to “mobile device” herein may be exchanged with “computing device” or “client device”. Reference to ‘asset’ may be exchanged with ‘physical asset’ or ‘digital asset’ where appropriate, and vice versa.

[0064] The method comprises: receiving, at a server system in communication with one or more user mobile devices, an authentication request, optionally from a user mobile device, to authenticate an asset such as a user’s physical or digital asset; sending a first request to a user mobile device for reading (or obtaining first ID information from) one or more machine-readable UIDs of the asset (e.g. on the physical asset); receiving, at the server system, the first ID information or scan data comprising the first ID information read by the mobile device from each requested UID of the asset; comparing, at the server system, the received / requested first ID information with stored first ID information associated with the UIDs of the user’s registered asset; and authenticating the asset if the received first ID information matches the stored first ID information. The server system may comprise a secure user database storing ID information associated with the UIDs on a user’s registered asset(s). Comparing may comprise accessing or querying the stored ID information in the secure user database.

[0065] Where the asset comprises a plurality of different machine-readable UIDs, each containing different first ID information for identifying the asset, the first request may comprise a request for reading (or first ID information from) each of the plurality of UIDs of the asset, or from a particular selection of one or more of the UIDs on the asset. The selection may be generated randomly based on the stored ID information associated with the user’s registered asset, . Alternatively, the selection may be based on one or more predefined criteria, e.g. a user’s prior authentication request history. Alternatively the selection may be specified by an authentication requesting entity or party.

[0066] The method may further comprise performing the method of the sixth aspect (see below) to authenticate or verify the identity of the user(s), and authenticating the asset if the received first ID information matches the stored first and ID information and the user’s identity is authenticated / verified. The method may further comprise sending, by the server system in response to the authentication request, a second request to the mobile device for reading (or second ID information from) one or more machine-readable UIDs on a user’s authenticator device as defined in the second aspect; receiving, at the server system, second ID information, or scan data comprising the second ID information, read by the mobile device from each requested UID on a user authenticator device; comparing, at the server system, the received second ID information with stored second ID information associated with the UIDs of the user’s registered authenticator device; and authenticating the asset if the received first and second ID information match the respective stored first and second ID information.

[0067] Where the asset comprises a plurality of different machine-readable UIDs, each containing different second ID information for identifying the authenticator device, the second request may comprise a request for reading (or second ID information from) each of the UIDs on the authenticator device, or a particular selection of one or more of the UIDs on the authenticator device. The selection may be chosen at random based on the stored second ID information, or based on one or more predefined criteria e.g. a user prior authentication request history. Alternatively, the selection may be specified by an authentication requesting entity or party.

[0068] The method may further comprise reading, by the user mobile device in response to the first and / or second request, the requested one or more UIDs on the respective asset and / or authenticator device (or the first / second ID information therefrom). This may comprise acquiring, by the mobile device, scan data comprising the respective first / second ID information. The method may further comprise, following the reading step, sending the first / second ID information or scan data comprising the first / second ID information to the server system.

[0069] Comparing may comprise processing, at the server system, the received scan data to determine or extract the respective first / second ID information. This may involve sending scan data from at least some of the UIDs to a third party server for decoding / extracting the ID information, and receiving the ID information from the third party server.

[0070] Preferably, the first / second ID information or scan data is not stored on the mobile device thereafter. That is, the reading and sending is performed without persistently storing the read first / second ID information or scan data on the mobile device. This may comprise storing the first / second ID information or scan data only temporarily for the purposes of transmission to the server system, and deleting any stored first / second ID information or scan data. The method may comprise encrypting, at the mobile phone, the scan data and sending the encrypted scan data to the server system, where it is decrypted and processed to extract the relevant ID information.

[0071] The method may further comprise receiving, at the server system, a first geolocation of the mobile device associated with a time of reading the requested UIDs (or the first ID information therefrom) on the asset, and a second geolocation of the mobile device associated with a time of reading the requested UIDs (or the second ID information therefrom) on the authenticator device; comparing, at the server system, the received first and second geolocations associated with the respective first and second ID information; and authenticating the asset if the received first and second ID information match the respective stored first and second ID information, and if the first and second geolocations substantially match.

[0072] The method may further comprise, determining, by the mobile device, the first and second geolocations of the mobile device associated with a time of reading the UIDs (or the first / second ID information therefrom) on the asset and the authenticator device.

[0073] The method may comprise performing the method of the sixth aspect to authenticate the identity of a further user, e.g. observing the asset authentication; and authenticating the asset if the received first ID information matches the stored first ID information and if the user’s identity and the further user’s identity is authenticated.

[0074] The method may further comprising storing, in a user database of the server system or a distributed ledger system, a record of the authentication request including one or more of: a time of the authentication request, a location of the user(s) mobile device(s), a result of the authentication request, the unique identifiers scanned, information associated with the asset and / or authentication request, and information associated with the authenticating user(s) and / or the authentication requesting entity or party.

[0075] Where the authenticator device comprises one or more drawers, each with a rotatable carrier portion on which at least one of the one or more UIDs is provided, the second request may be a request for reading one or more machine-readable UIDs (or the second ID information therefrom) when in a particular respective orientation relative to the drawer. In this case, the scan data further comprises the relative orientation of the carrier portion, and the method may comprise determining the relative orientation of the carrier portion from the scan data (e.g. based on markings). The second request may comprise a request to adjust the orientation of the carrier portion by a predetermined amount relative to a current orientation / position or user-defined starting orientation / position of the carrier portion, whereby the requested orientation is the result of adjusting the orientation of the carrier portion from the current / start position by the requested amount. The requested orientation may be determined based on a user’s prior authentication request history. The method may comprise comparing the received / requested orientation to an expected orientation. The expected orientation may be determined based on the previous requested orientation or user-defined start position and the current requested orientation or adjustment.

[0076] The start position may be user-defined set of orientations for each carrier portion, that are stored in the database (similar to a password). As such, the user may, in response to the request to adjust the orientation of the requested carrier portions by a predetermined amount, either set the carrier portion to the start position and then adjust the orientation by the predetermined amount, or the user may simply adjust the orientation from the current position by the predetermined amount.

[0077] Each carrier portion may comprise a set of markings to visually identify the relative orientation. In this case, reading the requested unique identifiers on the authenticator device may comprise capturing (by the mobile device) an image of the carrier portion including the markings and the UID.

[0078] The method may further comprise: sending, by the server system in response to the authentication request, a third request to the mobile device for reading third ID information from a user’s authenticator device; generating, by the authenticator device, third ID information based, at least in part, on second ID information from one or more machine-readable UIDs on the authenticator device, wherein the third information comprises visual and / or audio information; outputting, by a display and / or speaker of the authenticator device, the third ID information; receiving, at the server system, the third ID information, or scan data comprising the third information, read by the mobile device from authenticator device.

[0079] The method may further comprise comparing, at the server system, the received third ID information to corresponding third ID information generated (at the server system) using stored second ID information associated with the UIDs on the user’s authenticator device.

[0080] The method may further comprise authenticating the asset if the received first ID information matches the user’s stored first ID information, and if the received third ID information matches the corresponding third ID information generated by the server system.

[0081] Preferably, the third ID information comprises a unique dynamic image output on a display of the authenticator device. The third ID information may further comprise audio information output simultaneously with the dynamic image. Reading the third ID information may comprise acquiring, by the mobile device, video data of the dynamic image. The video data may optionally comprise an audio component of the third information. Reading the requested UIDs on the asset and / or authenticator device may comprise, reading using one or more ID readers of the mobile device. Preferably, the one or more ID readers include an imaging device, microphone and / or an RFID reader.

[0082] According to a fourth aspect of the invention, there is provided a system for authenticating an asset such as a physical asset or a digital. The system comprises an asset (physical or digital) with one or more machine readable UIDs containing or encoding ID information for identifying the asset. In one embodiment, the asset is a physical media asset as defined in the first aspect, and the terms can be exchanged accordingly. The system further comprises a server system comprising a secure user database storing ID information associated with the UIDs on a user’s registered asset(s). The server system is configured to communicate with a user mobile device via a network. The server system is preferably configured to perform the method of the third aspect. The server system is configured to: receive an authentication request from the mobile device to authenticate the user’s asset; send a first request to the mobile device for reading (or first ID information from) one or more UIDs of the asset; receive the first ID information, or scan data comprising the first ID information, read by the mobile device from each requested UID on the asset; compare the received first ID information with stored first ID information associated with the UIDs on the user’s registered asset; and authenticate the asset if the first ID information matches the user’s stored first ID information.

[0083] Reading ID information from one or more machine-readable UIDs or reading the one or more machine-readable UIDs may comprise acquiring, by the mobile device, scan data comprising the ID information.

[0084] Comparing may comprise processing, at the server system, the received scan data to determine or extract the ID information. Comparing may comprise accessing or querying the stored ID information in the user database. The server system may be configured to analyse / process scan data from a hieroglyph UID to detect hieroglyphs in the scan data based at least in part on a library of stored hieroglyphs. Where the UID contains a composite hieroglyph, the server system may be configured to analyse / process the scan data to determine / extract the component hieroglyphs, based at least in part on a library of stored hieroglyphs.

[0085] Preferably, the asset comprises a plurality of different machine-readable UIDs, each containing different first ID information for identifying the physical media asset. In this case, the server system may be configured to send a first request for reading (or first ID information from) each of the plurality of UIDs on the physical asset. Alternatively, the server system may be configured to send a first request for reading (or first ID information from) a particular selection of one or more of the plurality of UIDs on the asset. The selection may be chosen at random, e.g. based on the stored first ID information, or generated based on one or more predefined / determined criteria (e.g. a user’s prior authentication request history). Alternatively, the selection may be specified by an authentication requesting entity or party. Preferably, the system further comprises an authenticator device as defined in the second aspect. In this case, the server system further stores in the secure user database ID information associated with the UIDs on a user’s registered authenticator device.

[0086] The server system may be further configured to perform the method of the sixth aspect (see below) to authenticate or verify the identity of the user(s), and authenticate the asset if the received first ID information matches the stored first and ID information and the user’s identity is authenticated / verified. The server system may be further configured to: send, in response to the authentication request, a second request to the mobile device for reading (or second ID information from) one or more machine-readable UIDs on the user’s authenticator device; receive the second ID information, or scan data comprising the second ID information, read by the mobile device from each requested UID on the user authenticator device; compare the received second ID information with stored second ID information associated with the UIDs of the user’s registered authenticator device. The server system may further be configured to authenticate the asset if the received first and second ID information match the respective stored first and second ID information.

[0087] The mobile device is configured to read the one or more UIDs on the asset and the authenticator device. The mobile device comprises one or more ID readers, such as an imaging device (camera), and / or a RFID reader. The mobile device is preferably further configured to determine its geolocation, e.g. the mobile device may comprise one or more locator modules, such as a GPS module or any other suitable location technology.

[0088] The server system may further be configured to: receive a first geolocation of the mobile device associated with a time of reading the UIDs of the asset (or the first ID information therefrom), and a second geolocation of the mobile device associated with a time of reading the UIDs of the authenticator device (or the second ID information therefrom).

[0089] The server system may be configured to compare the first and second geolocations associated with the respective first and second ID information; and authenticate the asset if the received first and second ID information match the respective stored first and second ID information, and if the first and second geolocations substantially match.

[0090] Preferably, the authenticator device comprises one or more drawers, each drawer comprising a carrier portion on which at least one of the one or more UIDs is provided, and wherein each carrier portion is configured to rotate relative to the respective drawer so as to adjust the orientation of the UID relative to the respective drawer. In this case, the server system may be configured to send a second request for reading the one or more UIDs on the authenticator device when in a particular respective orientation.

[0091] Preferably, each carrier portion comprise respective sets of markings to visually identify the relative orientation. The markings may be numbered to enable a user to correctly adjust the orientation prior to reading. Preferably, reading the requested UIDs on the authenticator device by the mobile device comprises capturing image data of the carrier including the UID and the markings. Preferably, the scan data includes the UID / ID information and orientation information. The server system may be configured to process the scan data to extract the ID information and determine the orientation of the carrier portion.

[0092] Where the authenticator device is an active device for generating third ID information for identifying the authenticator device based, at least in part, on second ID information from the one or more of the machine-readable UIDs on the authenticator device as described in the second aspect, the server system may be further configured to: send, in response to the authentication request, a third request to the mobile device for reading third ID information from the authenticator device; receive the third ID information, or scan data comprising the third ID information, read by the mobile device from authenticator device; compare the received third ID information to corresponding third ID information generated (at the server system) using stored second ID information associated with the UIDs on the user’s authenticator device. The server system may be further configured to authenticate the asset if the received first ID information matches the user’s stored first ID information, and if the received third ID information matches the corresponding third ID information generated by the server system.

[0093] According to a fifth aspect of the invention, there is provided a method of secure transaction of an asset comprising one or more machine readable UIDs containing or encoding ID information for identifying the asset. In one embodiment, the asset is a physical media asset as defined in the first aspect, and the terms can be exchanged accordingly.

[0094] The method comprises receiving, at a server system configured to communicate with user mobile devices over a network, from a mobile device of a first user, an offer to purchase a second user’s asset listed on an online marketplace (or exchange or bourse) optionally hosted by the server system. The server system contains a secure user database storing ID information associated with UIDs on each user’s registered asset(s) and on each user’s registered authenticator device. The method may further comprise verifying or authenticating the identity of the first user (preferably by performing the method of the sixth aspect); sending, in response to positive verification of the first user and in response to the second user accepting the offer, an authentication request to the second user’s mobile device to authenticate the asset; and initiating a transaction for the purchase of the asset in response to positive authentication of the physical asset.

[0095] In this context, a registered asset and / or authenticator device means that the asset and / or the authenticator device, along with their respective ID information (and any other information associated with the assets) are stored in the user database, and associated with a user’s database account - thereby indicating that the user owns the asset and / or the authenticator device.

[0096] The method may further comprise, upon completion of the transaction, deregistering or removing the purchased asset and its associated ID information from the second user’s database or their database account maintained by the server system. The method may then comprise (i) adding the purchased asset with its associated ID information to the first user’s database or database account maintained by the server system. Alternatively, the method may comprise (ii) adding the purchased asset with ID information associated with new UIDs provided with or on the purchased asset to the first user’s database or database account (if new UIDs are requested by the first user).

[0097] The method may further comprise, upon receipt of the purchased asset by the first user, registering or activating (or confirming registration) the purchased asset with the first user’s database according to the method of the third aspect. This may comprise authenticating, by the first user, the purchased asset.

[0098] The method may further comprise, prior to receiving an offer for the asset from a first user: listing the second user’s asset for sale on the online marketplace. This may comprise: receiving, at the server system, a request from the second user to list their asset for sale on the online marketplace; and sending, by the server system in response to that request, a request to a mobile device of the second user to authenticate the asset. The process of asset authentication preferably proceedings as defined in the third aspect. The method may then comprise listing the second user’s asset for sale on the online marketplace in response to a positive authentication.

[0099] Verifying the identity of the first user may comprise performing the method of the sixth aspect, e.g.: sending, by the server system, a request to the mobile device of the first user for reading (or second ID information from) one or more machine-readable UIDs on an authenticator device of the first user; receiving, at the server system, second ID information or scan data comprising the second ID information read by the mobile device from each requested UID on the authenticator device; comparing, at the server system, the received second ID information with stored second ID information associated with the UIDs on the first user’s registered authenticator device; and authenticating the first user’s identity if the second ID information matches the stored second ID information.

[0100] Verification may further include the particular orientation of the UID, and / or the third ID information as described above.

[0101] According to a sixth aspect of the invention, there is provided a method of authenticating a user identity, using an authenticator device as defined in the second aspect. The method comprises: sending, by a server system configured to communicate with a user mobile device over a network and containing a secure user database storing ID information associated with UIDs on each user’s registered authenticator device, a request to the user mobile device for reading (or ID information from) one or more machine-readable UIDs on the user’s authenticator device; receiving, at the server system, ID information or scan data comprising the ID information read by the mobile device from each requested UID on the user’s authenticator device; comparing, at the server system, the received ID information with stored ID information associated with the UIDs on the user’s registered authenticator device; and authenticating the user’s identity if the received ID information matches the stored ID information.

[0102] The method may further comprise, receiving, at the server system, an authentication request to authenticate a user’s identity. The authentication request may be received from a third party entity. Comparing may comprise processing, at the server system, the received scan data to determine or extract the ID information. Comparing may comprise accessing or querying the stored ID information from a secure user database.

[0103] Where the authenticator device comprises a plurality of different machine-readable UIDs, each containing or encoding different ID information for identifying the authenticator device, the ID request may comprise a request for reading (or ID information from) each of the plurality of UIDs on the asset, a particular selection of one or more of the UIDs. The selection may be generated randomly, e.g. based on stored ID information, or generated based on one or more predefined criteria (e.g. a user prior authentication request history, a requesting party). Alternatively, the selection may be specified by an authentication requesting entity or party

[0104] The method may further comprise: reading, by the mobile device in response to the ID request, the ID information or scan data comprising the ID information from the requested one or more UIDs on the authenticator device, and sending the ID information or the scan data comprising the ID information to the server system. Preferably, the ID information or scan data is not stored on the mobile device thereafter. That is, the reading and sending is performed without persistently storing the read first ID information or scan data on the mobile device. This may comprise storing the ID information or scan data only temporarily for the purposes of transmission to the server system, and deleting any stored first ID information or scan data. Data sent to the server system may be encrypted.

[0105] The ID request may comprise a request for reading biometric ID information from the user’s hand, preferably one or more of the user’s digits, more preferably from a nail side of the one or more digits. In this case, the scan data preferably includes image or video data of the one or more user’s digits holding the user authentication device. The step of comparing then comprises performing a finger recognition process. The finger recognition process preferably involves: processing the image or video data to extract biometric ID information comprising one or more biometric features associated with one or more of the user’s digits, preferably wherein the biometric features include one or more of: a digit dimension, a digit geometry, a digit position, a grip, a nail feature, a skin feature, an anatomical feature, and a worn object; and comparing the extracted one or more biometric features with stored biometric features associated with the user’s digits to determine a similarity metric, preferably using a machine learning model. Preferably, the authenticating step includes authenticating the user’s identity if the similarity metric meets a threshold similarity metric indicative of a match.

[0106] The method may further comprise: sending, by the server system, a further ID request to the user mobile device for further ID information. The further ID information may comprise one or more of: ID information from one or more different machine-readable unique identifiers on the user’s authenticator device; ID information from a multi-state unique identifier of the authenticator device after performing a user interaction with the multi-state unique identifier that causes a change in the state of the multi-state unique identifier; and / or biometric ID information from one or more of the user’s digits. The method then comprises receiving, at the server system, scan data from the mobile device comprising the further ID information from each requested unique identifier on the user’s authenticator device; comparing, at the server system, the received further ID information with stored ID information associated with the unique identifiers on the user’s registered authenticator device; and authenticating the user’s identity if the received further ID information matches the stored ID information. Preferably, the further ID request is sent if a determined confidence level in the ID information obtained from the ID request is below a threshold confidence level, wherein the confidence level is determined based, at least in part, on the comparison of the ID information to stored ID information. Alternatively or additionally, the further ID request is sent if specified by an authentication requesting entity or party.

[0107] The method may further comprise storing, in the user database at the server system or a distributed ledger system, a record of the user authentication request including one or more of: a time of the authentication request, a location of the user mobile device, a result of the authentication request, the unique identifiers scanned, information associated with authentication request, and information associated with the authentication requesting entity or party.

[0108] The method may further comprise: associating a unique machine-readable optical identifier with the record of the user authentication request, wherein the unique machine-readable optical identifier contains ID information linked with the record of the user authentication request; and optionally or preferably wherein information associated with the record is retrievable or accessible, from the server system, in response to receiving a request containing the ID information linked with the record.

[0109] The step of associating may comprise: generating the unique machine-readable optical identifier for the record of the user authentication request, preferably based at least in part on the received ID information from the requested machine-readable unique identifiers of the user authenticator device and / or information in or associated with the record; and storing, at the server system, the unique machine-readable optical identifier for the record and / or its ID information in association with the record in the user database. Alternatively, the step of associating may comprise receiving, at the server system, a unique machine-readable optical identifier from the user mobile device; and storing, at the server system, the unique machine-readable optical identifier for the record and / or its ID information in association with the record in the user database.

[0110] Where the user authenticator device comprises a multi-state identifier, the ID request may comprise a request for ID information from the multi-state unique identifier after the user has performed a user interaction with the multi-state unique identifier that causes a change in the static state of the multi-state unique identifier. In this case, the method preferably comprises: processing the received scan data to extract ID information from the multi-state identifier; comparing the extracted ID information read from multi-state identifier to corresponding expected ID information generated at the server system using stored ID information associated with the multi-state identifier on the user’s registered authenticator device; and wherein the authenticating step includes authenticating the user’s identity if at least a first part of the extracted ID information matches the expected ID information, and optionally also if a second part of the received ID information does not match the any ID information stored in the user database.

[0111] Where the user authenticator device comprises a dynamic identifier, the ID request may comprise a request for ID information from the dynamic unique identifier optionally after the user has performed a user interaction with the dynamic identifier that causes a change in a static feature of the dynamic identifier. In this case, the method preferably comprises: processing the received scan data to extract ID information from the dynamic identifier; comparing the extracted ID information read from dynamic identifier to corresponding expected ID information generated at the server system using stored ID information associated with the dynamic identifier on the user’s registered authenticator device; and wherein the authenticating step includes authenticating the user’s identity if at least part of the extracted ID information matches the expected ID information.

[0112] Stored ID information associated with a clock device on the user’s registered authenticator device preferably includes the first and second start times, and preferably wherein the scan data includes image or video data of the clock device.

[0113] Stored ID information associated with a fluid device on the user’s registered authenticator device preferably includes properties of the immiscible fluids and optionally the particles, such as one or more of a colour and volume of the immiscible fluids, and one or more of a size, size distribution, shape, colour and / or other externally visible feature, number of the particles.

[0114] Stored ID information associated with a shaker device on the user’s registered authenticator device preferably includes properties of the particles, such as one or more of: a size, size distribution, shape, colour and / or other externally visible feature such as a pattern, and number, and optionally a static background optical pattern of the enclosure.

[0115] Stored ID information associated with a roller device on the user’s registered authenticator device preferably includes the spatially non-uniform visual feature on each rolling element, and optionally one or more geometric features of the rolling elements.

[0116] Stored ID information associated with a deformable topographic surface on the user’s registered authenticator device preferably includes the one or more topographic or visual features of the topographic surface.

[0117] According to a seventh aspect of the invention, there is provided a system for authenticating a user’s identity. The system comprises an authenticator device as defined in the second aspect; and a server system as described previously. The server system comprises a secure user database storing ID information associated with the UIDs on a user’s registered authenticator device. The server system is configured to communicate with a user mobile device via a network. The server system is configured to perform the method of the sixth aspect. For example, the server system is configured to: send an ID request to the user’s mobile device for reading (or ID information from) one or more machine-readable UIDs on the user’s authenticator device; receive ID information, or scan data comprising the ID information, read by the mobile device from each requested UID on the user’s authenticator device; compare the received ID information with stored ID information associated with the UIDs on the user’s registered authenticator device; and authenticate the user’s identity if the received ID information matches the stored ID information.

[0118] The server system may further be configured to receive an authentication request to authenticate a user’s identity. The authentication request may be received from a third party entity.

[0119] The authenticator device and server system may have any further features as defined in the appended claims or in the previous aspects in relation to authentication (in this case, a user’s identity), such as those related to the authenticator having a plurality of different machine-readable UIDs, having drawers with optional rotatable carrier portions, and being an active device for generating third (additional) ID information, along with the corresponding features of the server system such as the requests for ID information appropriate to the features of the authenticator device.

[0120] According to an eighth aspect of the invention, there is provided a physical asset, comprising a plurality of different machine-readable UIDs attached thereto, each containing different information for identifying the physical asset. The plurality of machine-readable UIDs preferably includes a nanoparticle or quantum dot-based physical unclonable function (PUF) tag and / or a surface topography-based tag. The physical asset may be or comprise: physical artwork, merchandise, memorabilia, a document such as a deed, contract, agreement, pledge, certificate, accreditation.

[0121] The plurality of machine-readable UIDs may further include at least one (any combination) from the following list: a symbol sequence or alphanumeric code; a unique graphic or image; an encoded image, preferably a QR code; a radio frequency identification (RFID) tag; a fingerprint; and a pattern of holes or indentations, optionally or preferably, wherein the holes or indentations have different or congruent shapes.

[0122] Preferably, at least some of the one or more UIDs are integrated with one or more labels attached to the asset; and / or embedded within the asset. Preferably, the asset comprises at least four or at least six different machine-readable UIDs.

[0123] A physical asset in general can be defined as a tangible item of value, produced by a physical process, that can be held and possessed. In the context of the invention, a connection between a mobile device and a server system means a relationship in which one program (running on the mobile device or server system) requests a service or data / resource from another program (running on the other of the mobile device or server system).

[0124] An ID reading device may be any electronic device that can scan, capture, process and / or interpret the data contained in a UID. An RFID tags includes an antenna and a microchip that contains information that can be queried and retrieved by an RFID reader, and which in turn transfers the information to a data processing system (e.g. that of the mobile device or server system). RFID readers are specific to the type of RFID tag adopted, as is known in the art.

[0125] According to a nineth aspect of the invention, there is provided use of the method of the third or sixth aspects, or the system of fourth or seventh aspects in a transaction process, or in a supply chain management process.

[0126] According to a tenth aspect of the invention, there is provided use of the method of the sixth aspect or the system or seventh aspect in a user account set-up or sign-in process.

[0127] According to an eleventh aspect of the invention, there is provided a method of secure sign in to a user account. The method is preferably implemented on a user or client device. The method comprises: sending, from a user mobile device, a request to a third-party server system to sign in to a user account hosted by the third-party server system using the user’s authenticator device as defined in the second aspect; receiving, at the user mobile device from an authenticating server system configured to perform the method of sixth aspect and in response to the authenticating server system receiving an authentication request from the third-party server system to authenticate a user’s identity, an ID request for ID information from one or more machine-readable unique identifiers on the user’s authenticator device; scanning, using the user mobile device, each requested machine-readable unique identifier on the user’s authenticator device; sending, from the user mobile device to the authenticating server system, scan data comprising the ID information from each requested unique identifier on the user’s authenticator device; and accessing the user account hosted by the third-party server system in response to a positive authentication of the user’s identity by the authenticating server system based on the ID information.

[0128] The ID request may comprise a request for ID information from a selection of one or more machine- readable unique identifiers on the user’s authenticator device required to satisfy a security level, wherein the security level is determined by the authenticating server system based, at least in part, on a required security level indicated by the third-party entity server system in the authentication request and / or one or more predefined criteria associated with the third-party server system.

[0129] The method may further comprise: receiving, by the user mobile device from the authenticating server system, a further ID request for further ID information, wherein the further ID information comprise one or more of: ID information from one or more different machine-readable unique identifiers on the user’s authenticator device; ID information from a multi-state unique identifier of the user’s authenticator device after the user has performed a user interaction with the multi-state unique identifier that causes a change in the state of the multi-state unique identifier; and / or biometric ID information from a scan of one or more of the user’s digits holding the user authenticator device. The method then comprises: scanning, using the user mobile device, each (further) requested machine-readable unique identifier on the user’s authenticator device; sending, from the user mobile device to the authenticating server system, scan data comprising the further ID information from each requested unique identifier on the user’s authenticator device; and accessing the user account hosted by the third-party server system in response to a positive authentication of the user’s identity by the authenticating server system based on the further ID information.

[0130] Optionally or preferably, the further ID request is received if a confidence level in the ID request is below a threshold confidence level, the confidence level determined by the authenticating server system based, at least in part, on a comparison of the ID information to stored ID information; and / or if required to satisfy a security level, wherein the security level is determined by the authenticating server system based, at least in part, on a required security level indicated by the third-party entity server system in the authentication request and / or one or more predefined criteria associated with the third-party server system.

[0131] According to a twelfth aspect of the invention, there is provided a method of secure transaction, comprising: receiving, at a server system configured to communicate with user mobile devices an over a network and containing a user database storing ID information associated with unique machine-readable identifiers on each user’s registered authenticator device as defined in the second aspect, a request for transaction between a first entity and a second entity; authenticating the identity of a first user representing the first entity according to the method of the third aspect; initiating or authorising the transaction based at least in part on a positive authentication of at least the first user; and storing, in a user database of the server system or a distributed ledger system, a record of the transaction.

[0132] The method preferably further comprises associating a unique machine-readable identifier with the record of the transaction, wherein the unique machine-readable identifier contains or encodes ID information linked with the record of the transaction for individuating the transaction; and preferably, wherein information associated with the record is retrievable or accessible, from the server system, in response to receiving a request containing the ID information linked with the record.

[0133] The step of associating may comprise: generating or receiving, at the server system, the unique machine-readable optical identifier for the record of the transaction; and storing, at the server system, the unique machine-readable optical identifier for the record and / or its ID information in association with the record in the user database. Optionally or preferably, the generated unique machine-readable identifier is a digital image generated based at least in part on information associated with the record, and more preferably encodes information associated with the record. Alternatively or additionally, the associating step may comprise generating instructions for producing a physical object representing the unique machine-readable optical identifier for the record.

[0134] The authentication step may comprise sending, by the server system, an ID request to the first user’s mobile device for ID information from a selection of one or more machine-readable unique identifiers on the first user’s authenticator device required to satisfy a transaction security level; and optionally or preferably, wherein the transaction security level is determined at the server system based, at least in part, on a required security level indicated by the second entity (and / or any additional entity involved in the transaction) in the transaction request and / or one or more predefined criteria associated with information in the transaction request.

[0135] Where the first user’s authenticator device comprises a multi-state unique identifier, the ID request of the authenticating step may include a request for ID information from the multi-state unique identifier after the user has performed a user interaction with the multi-state unique identifier that causes a change in the static state of the multi-state unique identifier for individuating the transaction; and preferably wherein the record includes at least part of the ID information from the multi-state unique identifier for individuating the transaction.

[0136] The method may further comprise authenticating a second user representing the second entity according to the method of the sixth aspect and initiating or authorising the transaction based at least in part on a positive authentication of the first user and the second user.

[0137] The authentication step may comprise sending, by the server system, an ID request to the second user’s mobile device for ID information from a selection of one or more machine-readable unique identifiers on the second user’s authenticator device required to satisfy a transaction security level; optionally or preferably, wherein the transaction security level is determined by the server system based, at least in part, on a required security level indicated by the first entity and the second entity (and any additional entities involved) in the transaction request and / or one or more predefined criteria associated with information in the transaction request.

[0138] The authentication step may comprise sending, by the server system, a further ID request to the respective user’s mobile device for further ID information, wherein the further ID information comprise one or more of: ID information from one or more different machine-readable unique identifiers on the respective user’s authenticator device; ID information from a multi-state unique identifier after performing a user interaction with the multi-state unique identifier that causes a change in the state of the multi-state unique identifier; and / or biometric ID information from a scan of one or more of the user’s digits. Then the method comprises: receiving, at the server system, scan data from the mobile device comprising the further ID information from each requested unique identifier on the respective user’s authenticator device; comparing, at the server system, the received further ID information with stored ID information associated with the unique identifiers on the respective user’s registered authenticator device; and authenticating the respective user’s identity if the received further ID information matches the stored ID information.

[0139] Optionally or preferably, the further ID request is sent if a confidence level in the ID information of the ID request is below a threshold confidence level, the confidence level determined at the server system based, at least in part, on the comparison of the ID information to the stored ID information; and / or if required to satisfy a transaction security level, or if requested by any entity involved in the transaction process at any time through the transaction process. Preferably, the record of the transaction includes one or more of: information associated with the transaction, information associated with the first and second entities, a time of the transaction, a location of the user’s mobile device, and information associated with the authenticating step.

[0140] Where the transaction relates to a physical asset, the method may further comprise producing a physical unique machine-readable optical identifier, or instructions for producing a physical unique machine-readable optical identifier, preferably based on the associated unique machine-readable optical identifier for attaching to the physical asset, containing or encoding ID information linked with the record of the transaction.

[0141] Features which are described in the context of separate aspects and embodiments of the invention may be used together and / or be interchangeable. Similarly, where features are, for brevity, described in the context of a single embodiment, these may also be provided separately or in any suitable sub-combination. Features described in connection with the system(s), physical media asset and authenticator device may have corresponding features definable with respect to the method(s), and vice versa, and these embodiments are specifically envisaged.

[0142] Brief Description of Drawings

[0143] In order that the invention can be well understood, embodiments will now be discussed by way of example only with reference to the accompanying drawings, in which:

[0144] Figure 1 is a schematic diagram of a system according to an embodiment of the invention;

[0145] Figure 2 shows a schematic diagram of a physical asset according to an embodiment of the invention;

[0146] Figure 3 is a schematic diagram of a physical media asset according to an embodiment of the invention;

[0147] Figure 4(a) is a schematic cross-sectional view of the physical media asset of figure 3 according to an example embodiment;

[0148] Figure 4(b) is a schematic cross-sectional view of the physical media asset of figure 3 according to an alternative embodiment in which the RFID tag is embedded in an insert;

[0149] Figure 4(c) is a schematic cross-sectional view of an insert;

[0150] Figure 5 is a schematic diagram of an authenticator device according to an embodiment of the invention;

[0151] Figure 6 is a schematic diagram of an authenticator device having drawers according to an embodiment of the invention;

[0152] Figures 7(a) and 7(b) are, respectively, illustrate top and side views of an example authenticator device with drawers according to an embodiment of the invention;

[0153] Figure 7(c) shows a drawer of the authenticator device of figure 7(a) and 7(b) in an open position;

[0154] Figures 8(a) and 8(b) are, respectively, schematic top and side views of an authenticator device with drawers according to another embodiment of the invention;

[0155] Figure 8(c) illustrates the authenticator device of figure 7(a) with the drawers in an open position; Figure 9 is a schematic diagram of an active authenticator device according to an embodiment of the invention;

[0156] Figure 10 is an illustration of an authenticator device according to another embodiment of the invention;

[0157] Figures 11(a) to 11 (d) show diagrams of an example multi-state identifier of the authenticator device of figure 10;

[0158] Figures 12(a) and 12(b) show diagrams of another example multi-state identifier of the authenticator device of figure 10;

[0159] Figures 13 and 14 show diagrams of further example multi-state identifiers of the authenticator device of figure 10;

[0160] Figures 15(a) and 15(b) show diagrams of a further example multi-state identifier of the authenticator device of figure 10;

[0161] Figure 16 shows a schematic diagram of a method of authenticating an asset according to an embodiment of the invention;

[0162] Figure 17 shows a schematic diagram of a method of authenticating a user identity according to an embodiment of the invention;

[0163] Figure 18 illustrates a user holding the authentication device of figure 10 for a finger scan;

[0164] Figures 19(a) and 19(b) show example record identifiers generated based on scan data;

[0165] Figure 20 shows a schematic diagram of a physical record identifier;

[0166] Figure 21 shows a schematic diagram of a method of secure transaction of a physical asset according to an embodiment of the invention;

[0167] Figure 22(a) is a schematic diagram of a physical media asset in the form of a vinyl record according to an embodiment of the invention;

[0168] Figure 22(b) illustrates an example functional label applied to the vinyl record of figure 12(a);

[0169] Figure 23(a) is a schematic exploded cross-sectional view of the vinyl record of figure 12(a);

[0170] Figure 23(b) is a schematic exploded perspective view of the vinyl record of figure 12(a);

[0171] Figure 24 is a schematic view of a vinyl record with a pattern of indentations or holes in the central area for identification;

[0172] Figure 25 illustrates an example physical media asset in the form of an audio cassette according to an embodiment of the invention;

[0173] Figure 26 illustrates an example physical media asset in the form of an optical disc according to an embodiment of the invention;

[0174] Figure 27 shows a schematic diagram of a method of secure sign in according to an embodiment of the invention; and

[0175] Figure 28 shows a schematic diagram of a method of secure transaction according to an embodiment of the invention.

[0176] It should be noted that the figures are diagrammatic and may not be drawn to scale. Relative dimensions and proportions of parts of these figures may have been shown exaggerated or reduced in size, for the sake of clarity and convenience in the drawings. The same reference signs are generally used to refer to corresponding or similar features in modified and / or different embodiments. Detailed Description

[0177] Figure 1 shows a schematic diagram of a system 100 according to an embodiment of the invention. The system 100 comprises a server system 110 configured to communicate with a mobile device 120 (or similar computing device) via a wireless network 10, an asset 130, and a user authenticator device 140. The asset 130 can be a physical asset or a digital asset. In some examples, the asset 130 is a physical media asset 130 such as a phonograph record disc (e.g. a vinyl record), an optical disc (e.g. CD or DVD, or Blu Ray), a cassette tape (e.g. audio and / or video cassette), or any other form of physical media recording. In other examples, the asset 130 can more generally be a physical or digital item or product, or a physical or digital document such as a deed, contract, agreement, pledge, certificate, or accreditation. The asset 130 and the authenticator device 130 each comprise one or more machine-readable unique identifiers (UIDs) 132, 142 that contain or encode ID information for identifying the respective asset 130 and authenticator device 140. Where the asset 130 is a physical media asset, the UIDs 132 can be provided in or on, or applied to, a non-playing area, region or surface of the physical media asset 130 as part of the manufacture process or a new physical media asset 130, or UIDs 132 can be applied retrospectively to preexisting physical media products 130. Where the asset 130 is a digital asset, such as a digital document or media file, the digital asset can be embedded with one or more digital UIDs 132, e.g. optically readable UIDs which are readable when the digital asset 130 is rendered on a display device. The mobile device 120 comprises one or more ID reading devices 122a, 122b configured to scan or read the UIDs 132, 142 and a wireless communication module 124 configured to connect to the wireless network 10 so as to communicate and send scan data or ID information obtained from a UID 132, 142 to the server system 110. The server system 110 comprises a secure database 112 storing at least the ID information associated with the UIDs 132, 142 on the asset 130 and the authenticator device 140. The server system 110 is configured to compare ID information obtained from a scanned UID 132, 142 (via the mobile device 120) to the stored ID for authentication / verification purposes, as will be described in more detail below. The server system 110 further comprises a wireless communication module 114 for communicating with the mobile device 120 over the network 10 and one or more processing devices 116 for processing data / information (e.g. scan data) received from the mobile device 120 and performing one or more of the functions described herein. It will be appreciated that in general, the asset 130 may be a physical asset or a digital asset, so long as it includes one or more machine-readable UIDs 132 that contain or encode ID information for identifying the asset 130. As such, in the following description, references to asset can be interchanged with physical asset or digital asset or physical media asset, and vice versa.

[0178] The mobile device 120 (computing device) is preferably configured to establish a secure connection with the server system 110 and exchange data / information with the server system 110 via a software application, e.g. a mobile or web / browser application running on the mobile device 120, as is known in the art. The one or more ID readers 122a, 122b of the mobile device 120 capture or acquire scan data from a UID 132, 142. As described below, the one or more UIDs 132, 142 preferably include at least one optically readable UID, and may optionally further include (for physical assets) a radio frequency identification (RFID) tag and / or near-field communication (NFC) tag. As such, the mobile device 120 preferably comprises at least an optical reader 122a such as a camera or imaging device to capture image or video scan data from a UID 132, 142, and optionally also an RFID and / or NFC reader 122b to capture RF scan data from an RFID tag and / or NFC tag on the asset 130 or authenticator device 140 (where present).

[0179] It will be appreciated that the scan data comprises the ID information contained in the UID 132, 142 (or data from which the ID formation can be determined or extracted), and depending on the type of UID 132, 142, the scan data may require further analysis or processing to extract or derive the ID information from the scan data before it can be compared to stored ID data at the server system 110 for authentication. In one example implementation, the mobile device 120 is configured with appropriate software to process and extract the ID information from the captured / acquired scan data, and then send the ID information to the server system 110. Alternatively, the data processing can take place remotely from the mobile device 120, at the server system 110. In this case, the mobile device 120 is configured to send to the scan data, i.e. captured image scan data and / or RF scan data, to the server system 110 for processing to extract the ID information. This may be appropriate for more sophisticated UIDs 132, 142 that require significant or proprietary data processing to extract the ID information from the scan data, or the dynamic / multi-state UIDs described below. In either case, within the context of the invention, scan data comprising the ID information is sent from the mobile device 120 to the server system 110. Preferably, the mobile device 120 is configured to encrypt the scan data and send the encrypted scan data to the server system 110, where it is decrypted and optionally processed to extract the relevant ID information. Scan data / encrypted scan data is then deleted from the mobile device 120 after sending. The server system 1 10 can be configured to process the scan data to extract and encode relevant (geometric and / or optical) features from the image scan data using various image processing techniques, computer vision techniques and / or trained machine learning models, such as convolutional neural networks, optical character recognition (OCR) models and / or non-OCR models based on transformers.

[0180] It will be appreciated that the server system 110 comprises one or more servers in communication with each other. The one or more servers may be located remotely or co-located, and various functions of the present invention may be distributed or allocated between the one or more servers, as appropriate. For example, in one implementation the server system 110 comprises at least one primary server containing the database 112, and further comprises or is in communication with one or more third-party servers (e.g. a manufacturer / supplier of a particular UID 132, 142) configured to receive and process scan data obtained by the mobile device 120 to extract the ID information, which is then sent to the primary server(s) for further processing (e.g. comparison to the stored ID information). The server system 110 may comprise or be in communication with further third-party servers or entities for other purposes related to authentication as will be evident from the below description.

[0181] In some examples, the asset 130 and the authenticator device 140 are associated with a user who is registered with the system 100. In other examples, such as in supply chain management applications, the asset 130 (e.g. a physical asset 130) need not be associated with the user of the authenticator device 140, who may for example be person who is authenticating the asset 130 in transit from location to another as part of a track and trace process.

[0182] In practice, registering a user with the system 100 will typically involve a prospective user providing various details (e.g. name, address, and contact details) to the server system 110 via a secure connection established through the software application (e.g. a mobile application or web application) running on the user’s mobile device 120, much like any other online service, and also passing one or more security checks to verify the user’s identity. For example, this may be similar to a bank grade security check whereby a prospective user is required to provide or upload various forms of identification and proof of address etc. This registration stage preferably involves communication with a third-party identify verification entity / server. A user is the owner of their registered asset(s) 130 and authenticator device 140.

[0183] In practice, there can be any number of users registered with the system 100, each user having a registered authenticator device 140 and any number of registered assets 130 (whether physical or digital). The database 112 of the server system 110 thus comprises information relating to the authenticator device 140 and asset(s) 130 associated with each user, including information relating to the UIDs 132, 142 on each user’s registered authenticator device 140 and assets 130 (e.g. the number and types of UIDs), and the ID information associated with the UIDs 132, 142 on each user’s registered authenticator device 140 and asset(s) 130, as well as any other information associated with the asset(s) 130 and user. In one implementation, the database 112 is or comprises a relational database that manages the information for all the users and can be easily queried and updated, as is known in the art. The relational database 112 may also preferably offer temporal support in order to query past instances of the data content. Preferably, once registered with the system 100, each user has a user account (also referred to herein as a user database account) linked with the registered asset(s) 130 and authenticator device 140. Every interaction and transaction with the system 100 can be recorded in the database 112 or a distributed ledger system (e.g. blockchain) to build up a timeline / history for each user, and a history / provenance for each asset 130 that can optionally be transferred with the ownership of the asset 130.

[0184] As described in more detail below, the system 100 serves two primary purposes: first, the system 100 can be used with the authenticator device 140 to authenticate the identity of a user for various purposes; and second, the system 100 can be used, with or without (but preferably with) the authenticator device 140, to authenticate an asset 130 and ownership of the asset 130. These two functions together further facilitate the secure transaction of genuine assets 130 such as physical media or other assets registered with the system 100 and the transfer of their ownership between registered users of the system 100 preferably via a secure online exchange or marketplace (i.e. a bourse) hosted by the server system 110. They may also facilitate an effective supply chain management solution. It will be appreciated that secure user verification alone has many applications, including but not limited to: transactions such as a financial transactions, purchases or any other transaction instrument or event between two or more parties, user account sign in, etc. It will be appreciated that for authentication / verification of a user’s identity, the presence of an asset 130 is not necessary, while authenticating the user’s identity can optionally be used to improve the process of authenticating an asset 130 and ownership. As such, in certain embodiments, the system 100 can include either or both of the asset 130 and the authenticator device 140, depending on the specific use application.

[0185] The user authenticator device 140 is a physical tangible handheld device belonging to a registered user with one or more physical UIDs 142 that can be scanned or read by the mobile device 120 and referenced against the stored ID information in the database 112 to verify the user’s identity. Once a user is registered with the system 100, they are provided with an authenticator device 140 with one or more UIDs 142, the details and ID information of which are linked with the user account and stored in the database 112. As there is only one authenticator device 140 associated with any given registered user, each with a set of one or more UIDs 142 associated with the registered user’s account on the server system 110, a positive match between read / scanned ID information and the stored ID information associated with that user’s registered authenticator device 140 indicates that the person purporting to be a particular registered user (e.g. during a transaction, sign in or any other process requiring user verification) is in fact the registered user. The authentication device 140 can be used as part of a multi-factor verification process, whereby instead of, or in addition to, entering user-known factors such as a username, a password or a code into the mobile device 120, a user is requested to scan or read one or more of the UIDs 142 on their authenticator device 140 to provide the additional security factors (see method 400 below). Each separate UID 142 or a specific combination of UIDs 142 can be used to represent a security factor optionally in combination with a particular orientation of the UID 142 (see figure 7(c)) or other user adjustable feature of the UID 142, and requested by the server system 1 10 during the verification process. Unlike known software and hardware authenticator devices that generate a code based on locally or remotely stored algorithms for verification purposes, the physical nature of the UIDs 142 on the authenticator device 140 provides an entirely analogue verification means that, in a predominantly digital age, is not reliant on programming making it harder to fake or circumvent. The user authenticator device 140 thus enhances the robustness and security of any process requiring user verification and may eliminate the need for a password.

[0186] In a preferred embodiment, the asset 130 and the authenticator device 140 comprise a plurality of different machine-readable UIDs 132, 142, each containing different ID information for identifying the respective asset 130 and authenticator device 140. In one example, the physical asset 130 and the authenticator device 140 comprise at least four or at least six different UIDs 132, 142. Providing multiple different UIDs 132, 142 adds additional levels and factors of security to the authentication process. For example, much like online multi-factor verification technique, while it might be possible for an unauthorised person to circumvent one type of UID 132, 142, it is less likely for them to circumvent two different types of UIDs, and even less likely to circumvent three, and so on.

[0187] In a preferred implementation, the plurality of UIDs 132, 142 on the authenticator device 140 and physical asset 130 include at least a nanoparticle or quantum dot-based physical unclonable function (PUF) tag (referred to hereafter as a quantum-PUF), and a surface topography-based tag. Such tags are known in the field of product track and trace and are particularly difficult to clone or simulate. They are also optically readable using a mobile device 120 with an optical reader such as camera 122a, such as a conventional smartphone or tablet device. A surface topography-based tag may be or comprise a textured surface of the physical asset 130 or authenticator device 140, e.g. an area of naturally or intentionally textured material provided on the exterior of the authenticator device 130. Accordingly, in preferred implementations, the mobile device 120 is a smartphone or tablet device with at least an optical reader 122a such as a camera. Optionally, the physical asset 130 and / or the authenticator device 140 can further include a passive RFID tag and / or NFC tag. In this case, the mobile device 120 further includes an RFID and / or NFC reader 122b or RFID / NFC reader functionality, e.g. a high-frequency RFID chip which is present in most near-field communication (NFC)-enabled or RFID-enabled smartphones.

[0188] Such UIDs are examples of ‘static’ UIDs in the sense that their ID information is substantially fixed and the same each time they are scanned by a mobile device 120. In various embodiments, the authenticator device 140 may alternatively or additionally comprises one or more ‘dynamic’ UIDs configured to provide ID information that continuously changes with time, and / or one or more ‘multistate’ UIDs which are configured to provide ID information in a static state when read that is changeable in response to a user interaction with the authenticator device 140, such as a press, push, roll, shake, rotation or rub, that causes a change in the static state, as will be described in more detail below. Such dynamic and multi-state UIDs provide ID information that is unique to that scan instance and, in the case of multi-state UIDs, changeable in response to a user interaction (which may be prompted by the server system 110), which can advantageously serve as an antifraud feature in a verification process and individuate a transaction.

[0189] For example, in preferred embodiments, the dynamic and multi-state identifiers provide ID information including a variable but non-random ID portion or features which can be verified against expected ID information determined based on stored ID information associated with the respective dynamic and multi-state identifier at the server system 110. Producing variable but non-random ID portions or features, and particularly in response to prompted user interactions in the case of multistate UIDs, can be used to help protect against fraud by checking that the authenticator device 140 is a real device and the user is a live person. In other embodiments, the ID information provided by the multi-state identifier further includes a random ID portion or features, unique to each static state of the multi-state identifier, which can be checked against stored ID information to determine that the scan instance is indeed unique and individuated. The random ID portion in combination with non-random ID features can thus enhance anti-fraud protection by further checking that the scan data has not been seen by the server system before (e.g. which might be the case if an unauthorised person attempts to use a copy of previous or out of date scan data).

[0190] Figure 2 shows a schematic diagram of a physical asset 130 according to an embodiment of the invention. The physical media asset 130 comprises a body 131 and a plurality of machine-readable UIDs 132a-132d provided in various positions on or in the body 131 , each UID 132a-132d containing or encoding different ID information for identifying the asset 130. In some examples, the asset 130 can include, in addition to or instead of the UIDs 132a-132d, a machine-readable record identifier 150 that is generated or produced as part of a transaction or authorisation process, as described below with reference to methods 400 and 700.

[0191] Figure 3 shows a schematic diagram of a physical media asset 130 according to an embodiment of the invention. The physical media asset 130 comprises a storage medium 131 for storing a copy of a media recording (an audio and / or video recording), and a plurality of machine-readable UIDs 132a-132d provided on or in the storage medium 131 , each UID 132a-132d containing or encoding different ID information for identifying the asset 130 and / or the copy from all other copies of the media recording. The storage medium 131 a may be a phonograph record disc (e.g. a vinyl record), an optical disc (e.g. CD or DVD, or Blu Ray), a cassette tape (e.g. audio and / or video cassette), or any other suitable physical storage medium for storing a physical copy of a media recording in persistent physical form (rather than a d ig ita l / electro n ic copy).

[0192] The plurality of UIDs 132a-132d on the physical asset and physical media asset 130 include a quantum-PUF tag 132a, a surface topography-based tag 132b, an RFID tag 132c (and / or NFC tag) and one or more further UIDs 132d selected from the group: an encoded image, such as a QR code; a symbol sequence or alphanumeric code; a production sequence number associated with the physical asset 130 or physical media asset 130; a unique graphic or image; a human fingerprint (e.g. the user’s or owner’s fingerprint applied after receiving the asset 130); and a pattern of holes or indentations (whose shapes can be the same or different). The unique symbol sequence or graphic may be or comprise a unique combination of hieroglyphs selected from a set or dictionary of hieroglyphs. Preferably, the set or dictionary of hieroglyphs is bespoke / unique and contains at least 500 or 1000 different hieroglyphs.

[0193] A PUF is a device with unique optical behaviour produced by random physical characteristics that is hard to clone, hence providing a secure fingerprint (the ID information). A quantum-PUF 132a comprises a randomly deposited array of nanoparticles or quantum dots encapsulated in a transparent layer such as a polymer, forming a unique identification tag. The ID information in a quantum-PUF 132a can be read using a conventional imaging device 122a such as a camera on a smartphone. Reading the information typically involves exciting the tag with a light source (e.g. using a smartphone’s built-in camera flash) and measuring the non-linear response of the tag (e.g. using the camera) as described, e.g. in M. J. Fong et al. “Using intrinsic properties of quantum dots to provide additional security when uniquely identifying devices’’ Scientific Reports (2022), 12 16919. This captures the unique ID information or fingerprint, which is non-trivial to clone or simulate.

[0194] A surface topography tag 132b may be or comprise a specific coating or layer applied to the physical asset 130 which comprises a random or pseudorandom microscopic surface modulation, typically in the form of a pattern of indentations / undulations, which can represent or be assigned a unique code. An example of a suitable surface topography tag 132b is described in EP 1849139 B1 . Alternatively, the surface topography of the physical asset 130 itself or another material (natural or synthetic) applied to the physical asset 130 or physical media asset 130 can be used as the tag, whereby the microscopic structure and / or variations in the surface caused by the manufacture process provides a unique pattern or fingerprint which can be assigned or used to generate a unique code (see, e.g. EP 2960830 B1). The surface topography information can also be read using conventional optical readers 122a such as a camera on a smartphone.

[0195] The further UIDs 132d are also optically readable, e.g. using a camera 122a on a mobile device 120. For example, ID information contained in an encoded image or QR code can be read in the usual manner, and symbols, shapes, text, numbers, or a fingerprint in image data can be detected and extracted by suitable image processing algorithms known in the art. In the case of a pattern of holes or indentations, the pattern itself contains the ID information, e.g. defined by the relative positions of the holes or indentations and optionally their shapes, which can be read from image data using suitable image processing algorithms.

[0196] Providing a production sequence number 132d associated with the physical media asset 130 not only allows the specific asset to be identified from all other copies made in a production run / batch but also the specific position / order of the physical media asset 130 in the production / manufacture sequence. For example, the production sequence number may indicate whether a vinyl 131 is the first pressing in the run, the 100th pressing, or the 10,000th pressing. It will be appreciated that, like prints of reproduced artwork, early pressings of a vinyl 131 will be more collectable / valuable than later pressings of the same media recording. The same applies to cassettes and optical discs.

[0197] At least some of the plurality of UIDs 132a-132d of the physical asset and / or physical media asset 130 are incorporated into a label 134 applied to the body 131 or storage medium 131. For example, a UID 132 can be provided on a surface of the label 134, or embedded within the label 134, e.g. sandwiched or laminated between single or multiple layers of opaque or transparent material. It will be appreciated that, where an optically readable UID 132 is embedded within the label 134, the material or layer(s) of the label 134 covering the UID 132 should be transparent to allow it to be optically read. The physical asset 130 and / or physical media asset 130 can further include packaging 136 (e.g. a sleeve, case and / or box), which can optionally include a plurality of UIDs 132a-132d containing ID information for identifying the physical asset 130 or physical media asset 130 (not shown).

[0198] Figure 4(a) shows a schematic cross-sectional view of an example physical media asset 130 in which a quantum-PUF tag 132a and surface topography-based tag 132b is integrated with a label 134 applied to a surface 131 s of the storage medium 131 , and an RFID tag and / or NFC tag 132c is located beneath the label 134. In this example, the RFID tag and / or NFC tag 132c can be adhered to the surface 131 s of the storage medium 131 and the label 134 applied to the surface 131 s over the RFID tag and / or NFC tag 132c. The label 134 may of course comprise any combination of further UIDs 132d, as described above (not shown). In other implementations, the RFID tag and / or NFC tag 132c can be embedded within layers of the label 134 (not shown).

[0199] Figure 4(b) shows an alternative implementation whereby the RFID tag and / or NFC tag 132c is embedded within an insert 133 that is secured (permanently or releasably) within a recess 131 r or depression in the surface 131 s of the storage medium 131. The insert 133 can be secured within the recess 131 r by adhesive or other suitable means. The insert 133 is preferably located beneath or covered by the label 134, which may again comprise further UIDs 132d. Preferably, the dimensions (e.g. shape, width and thickness) of the insert 133 substantially match the dimensions of the recess 131 r or depression such that, when secured or fitted within the recess 131 r or depression, it provides or forms a substantially smooth surface 131 s of the storage medium 131 to which the label 134 can be applied. However, this is not essential, and in some examples, the insert 133 can have a thickness greater than the depth of the recess 131 r, so that the insert 133 protrudes slightly above the surrounding surface 131 s of the storage medium 131.

[0200] It will be appreciated that at least a part of the storage medium 131 typically comprises or is formed of a moulded plastic or polymer-based material in which a recess of depression can readily be formed during or after manufacture, e.g. as part of the initial moulding process or as an additional subtractive step after the initial moulding process. For example, a phonographic record is typically formed from a vinyl material, a CD, DVD or Blue Ray disc is typically formed from a plastic material (e.g. polycarbonate), and a cassette comprises a plastic shell or casing for holding spools of magnetic tape.

[0201] In a preferred implementation, the insert 133 is or comprises a multilayer structure including a first layer 133-1 and a second layer 133-2, whereby the RFID tag and / or NFC tag 132c is located between the first layer 133-1 and the second layer 133-2, as shown in figure 4(c). The first layer 133-1 may be located on the recess side of the RFID tag 132c and the second layer 133-2 may be located on the label side of the RFID tag and / or NFC tag 132c. The first and second layers 133-1 , 133-2 are preferably formed of or comprise a polymer or paper material (and the materials of the first and second layers 133-1 , 133-2 need not be the same). The multiple layers can be adhered or otherwise bonded together to form the insert 133. Alternatively, the insert 133 may be formed as a unitary plastic or polymer element in which the RFID tag 132c is embedded, e.g. during a moulding / forming process.

[0202] In another example, in addition to or instead of the RFID tag and / or NFC tag 132c, one or more optically readable UIDs 132, such as the quantum-PUF 132a and / or any of the further UIDs 132d, can be similarly embedded into an insert 133 (not shown). In this case, at least the material / layer(s) of the insert 133 above the optically readable UID(s) 132 should be transparent to allow them to be optically read. Where the insert 133 is covered by the label 134, the label 134 should similarly comprise a transparent region positioned above the optically readable UID(s) 132 to allow them to be optically read.

[0203] It will be appreciated that the above description of figures 4(a) to 4(c) applies equally to embodiments of a physical asset 130, save for references to the storage medium 131 of the physical media asset 130 being exchanged with body 131 of the physical asset 130.

[0204] Figure 5 shows a schematic diagram of a user authenticator device 140 according to an embodiment of the invention. The authenticator device 140 comprises a main body 144 and a plurality of different machine-readable UIDs 142a-142d provided in or on the main body 144, whereby each UID 142a-142d contains or encodes different information for identifying the authenticator device 140.

[0205] The plurality of UIDs 142a-142d preferably include a quantum-PUF tag 142a, a surface topographybased tag 142b, an RFID tag 142c and one or more further UIDs 142d selected from the group: an encoded image, such as a QR code; a symbol sequence or alphanumeric code; a unique graphic or image; a human fingerprint (e.g. the user’s or owner’s fingerprint applied after receiving the asset 140); a microchip; and a pattern of holes or indentations (whose shapes can be the same or different). The unique symbol sequence or graphic may be or comprise a unique set or combination of hieroglyphs.

[0206] Such UIDs are examples of ‘static’ UIDs in the sense that their ID information is substantially fixed and the same each time they are scanned by a mobile device 120. In various embodiments, the authenticator device 140 alternatively or additionally comprises one or more ‘dynamic’ UIDs 1424 that are configured to provide ID information that continuously changes with time, and one or more ‘multi-state’ UIDs 1421 -1423, 1425 which are configured to provide ID information in a static state when read / scanned that is changeable in response to a user interaction with the authenticator device 140, such as a press, push, roll, shake or rub, that causes a change in the static state, as will be described in more detail below with reference to figures 10 to 15. Such dynamic and multistate UIDs 1421 -1425 provide ID information that is unique to that scan instance and, in the case of multi-state UIDs, changeable in response to a user interaction, which can advantageously serve as an anti-fraud feature in a verification process and individuate a transaction.

[0207] In some embodiments, the main body 144 comprises one or more internal compartments 146 configured to receive (and store) one or more drawers 148a-148d on / in which at least some of the UIDs 142a-142d are provided. The authenticator device 140 may comprise a separate drawer 148 for each or different ones of the UIDs 142a-142d, or a particular drawer 148 may comprise multiple UIDs 142a-142d. The drawers 148a-148d are moveable (slidable) between an open position in which the UIDs 142a-142d are located outside of the main body 144 and readable, and a closed position in which the UIDs 142a-142d are located inside the main body 144, within an internal compartment 146. In this way, the UIDs 142a-142d can be stored within the main body 144 of the authenticator device 140 and protected from the external environment when not in use. This may in turn prevent or reduce damage to, and slow any degradation of, the UIDs 142a-142d that may occur over time. In a preferred embodiment, the drawers 148a-148d are removable and / or interchangeable.

[0208] One of the drawers 148d may contain a user-defined / selected unique physical object, such as a seashell or other such item with unique physical or optical properties that can be optically read. For example, a user can choose an object, and send an image of it to the server system 110 (via the mobile device 120), where it is stored in the database 112 for comparison to future images acquired during an authentication process, on the basis that only the registered user would have such an item in their authenticator device 140. The one or more internal compartments 146 can generally be used for housing one or more machine-readable unique identifiers 142 and / or other components of the authenticator device 140, such as a battery, light emitting devices, processing means etc. where needed. In some examples, instead or in addition to the drawers 148, the main body 144 further comprises one or more windows 147 through which one or more of the machine-readable unique identifiers 142 within the internal compartments 146 are readable by a reader device. In some examples, the windows 147 may be or comprise through holes or openings in the main body 144. In other examples, the windows 147 comprise an optically transparent material, such as glass or a plastic / polymer material, to enclose the internal compartment and protect the UID 142 located behind the window 252. Alternatively, the windows 147 can include a cover (not shown) that is moveable between an open position in which the window 147 is substantially open or exposed and the UID 142 behind it is readable, and a closed position in which the window 147 is substantially closed or covered.

[0209] Figure 6 shows a schematic diagram of an authenticator device 140 with one drawer 148a in an open position and another drawer 148b in a closed position. The drawers 148a-148d are received through respective openings 144o in the main body 144 that lead to the internal compartment(s) 146, as shown in figure 5. Preferably, the drawers 148a-148d are configured to at least partially close, and optionally seal, the openings 144o when in the closed position to further assist in protecting the UIDs 142-142d.

[0210] In one embodiment, the authenticator device 140 is a passive device which has no power source or means of connecting with another device or network 10 (other than an RFID reader 122b reading the passive RFID 142c).

[0211] Figures 7(a) and 7(b) illustrate top and side views of an example passive authenticator device 140 comprising four drawers 142d-148d. As before, each drawer 148a-148d is movable between an open and closed position. Figure 7(c) shows the authenticator device 140 with a drawer 148a in an open position. In this example, the drawer 148a comprises a quantum-PUF tag 142a and a QR code 142d. A through hole 144t is also provided in the main body 144 for attaching the device 140 to a key ring, key chain, or other loop of material.

[0212] Figures 8(a) and 8(b) illustrate top and side views of another example of a passive authenticator device 140 comprising eight drawers 148d-148d. As before, each drawer 148a-148d is movable between an open and closed position. Figure 8(c) shows the authenticator device 140 with the drawers 148a-148d in the open position. In contrast to the example of figure 7, each drawer 148a- 148d comprises a respective carrier portion 1481 on which a UID 142 is provided, whereby each carrier portion 1481 is configured to rotate relative to the respective drawer 148. This provides for manual adjustment of the orientation of the UID 142 relative to the respective drawer 148, as indicated by the arrow in figure 8(c). In one example, the carrier portions 1481 are adjustable between eight stable positions. Each carrier portion 1481 further comprise a set of markings (e.g. graduations) 1481 m to visually identify the relative orientation. In the example shown, the carrier portion 1481 is substantially circular and the markings 1481 m extend around the periphery of the carrier portion 1481. The drawer 148 may also include at least one marking 148m adjacent the carrier portion 1481 to help read / set the relative orientation. The markings 148m, 1481 m can be captured by the reader (e.g. mobile device camera) and used to determine the relative orientation.

[0213] Adjusting the orientation of the UIDs 142a-142d adds a further level of security whereby the orientation of, and the ID information contained or encoded in, the UID 142 can be read and combined as part of the authentication process. For example, a user may be requested to scan / read a particular UID 142 in a particular drawer 148 and in a particular orientation, as described in more detail below.

[0214] Figure 9 shows a schematic diagram of an example authenticator device 240 according to an alternative embodiment of the invention. In this example, authenticator device 140 is an active device. In addition to the plurality of UIDs 142a-142d, the authenticator device 240 further comprises: a power source 242 such as a battery, one or more output devices 244a, 244b including at least a display 244a (e.g. a touch screen display) and optionally an audio output (speaker) 244b, one or more inputs 246, and a processor 248. The one or more inputs 246 may be separate input devices such as buttons, or they may be integrated with the display 244a where the display 244a is a touch screen display, as is known in the art. Preferably, the authenticator device 240 does not include a wireless communication module, or any means to connect to a wireless network 10 such as the internet, or be in data communication with a mobile device 120. In some examples, the authenticator device 240 may further include a hardware crypto wallet module configured to securely store and provide access to a user’s cryptographic asset data (see e.g. figure 10). In this case, the authenticator device 240 includes a data port coupled to the hardware crypto wallet module for connecting to a computing device such as the mobile device 120.

[0215] In some embodiments, the processor 248 is configured with suitable programming to generate, in response to a user input via the one or more inputs 246, additional ID information for identifying the authenticator device 240. The additional ID information is preferably a unique and dynamic image for outputting on the display 244a generated based, at least in part, on ID information in one or more of the UIDs 142a-142d on / in the authenticator device 240. Alternatively or additionally, the additional ID information may comprise an audio signal output by the audio output 244b. In this case, the mobile device 120 can read or scan the additional ID information by capturing an image of the dynamic image or recording a video of the dynamic image over a period of time, and / or recording the audio signal (where generated). The corresponding additional ID information can be generated by the server system 110 based on the stored ID information associated with the authenticator device 240 using the same algorithm(s) for comparison to the additional ID information received from the mobile device 120 as part of the authentication process.

[0216] Figure 10 shows a schematic diagram of an example authenticator device 340 according to another embodiment of the invention. In this example, authenticator device 340 comprises a plurality of different multi-state UIDs 1421 , 1422, 1423 which are configured to provide ID information in a static state when read that is changeable in response to a user interaction with the authenticator device 340, such as a press, push, roll, shake or rub, that causes a change in the static state, as will be described in more detail below. The authenticator device 340 further includes a dynamic UID 1424, and one or more ‘static’ UIDs 142a-142d.

[0217] The multi-state UIDs 1421 -1423 and dynamic UID 1424 provide ID information that is unique to a particular scan instance, and in the case of multi-state UIDs changeable in response to a user interaction, which can advantageously serve as an anti-fraud feature in a verification process and to individuate an interaction with the server system 1 10 or transaction. For example, the multi-state and dynamic identifiers 1421 -1424 provide ID information, and in the case of multi-state UIDs responsive to a user interaction, which includes a variable and / or non-random ID portion or features which can be verified against expected ID information determined based on stored ID information associated with the respective identifier 1421-1424 at the server system 110 to at least partially verify a user identity. Producing variable and / or non-random ID portions or features, and particularly in response to prompted user interactions in the case of multi-state UIDs, can be used to help protect against fraud by checking that the authenticator device 140 is a real device and the user is a live person. In some embodiments, the ID information provided by the multi-state identifier 1421-1423 further includes a random ID portion or features, unique to each static state of the multistate identifier 1421 -1423, which can be checked against stored ID information to determine that the scan instance is indeed unique and individuated. In this way, the multi-state and dynamics UIDs 1421-1424 can enhance anti-fraud protection by checking that the scan data has not been seen by the server system before (e.g. which might be the case if an unauthorised person attempts to use a copy of previous or out of date scan data), and that the authenticator device 140 is a real device and the user is a live person.

[0218] The multi-state identifiers generally comprise one or more adjustable, moveable and / or mobile elements that form part of a unique optical identifier to be scanned, and are configured to provide or produce a change in the overall configuration of the unique optical identifier in response to a user interaction with the multi-state identifier that changes the static state of the adjustable, moveable and / or mobile elements. The adjustable, moveable and / or mobile elements may comprise, mobile particles, mobile fluids, movable optical elements, or rotatable dials, as described in more detail below.

[0219] With reference again to figure 10, the authenticator device 340 includes one or more (four in this example) machine-readable multi-state identifiers in the form of an optical device 1421 , which is shown in more detail in figures 11 (a) to 11 (d). The optical device 1421 comprises a first optical element 1421 e1 housed within an internal compartment of the main body 251 of the authenticator device 340 behind a window 252 in the main body 251 , and a second optical element 1421 e2 arranged within the internal compartment behind the first optical element 1421 e1 , as indicated in the exploded view of figure 11 (a). The first and second optical elements 1421 e1 , 1421 e2 each comprise portions or areas of different optical properties (e.g. transparency, colour, opacity, fluorescence, etc.) arranged to form respective first and second optical identifiers or patterns (which may be the same or different). At least a portion of the first optical element 1421 e1 is substantially transparent, such that first and second optical identifiers 1421 e1 , 1421 e2 superpose / superimpose or otherwise combine, overlap and occlude each other (when viewed through the window 252) to form a different, and variable, superposed shape that provides a unique optical identifier 1421 s readable through the window 252, as shown in figure 11 (b). In some examples, the first and second optical elements 1421 e1 , 1421 e2 comprise substantially transparent glass or plastic discs with a combination of transparent and at least partially opaque areas, optionally including different colours, to form the first and second optical identifiers.

[0220] The position of at least one of the first and second optical elements 1421 e1 , 1421 e2 is adjustable, preferably in predefined increments, relative to the other so as to change the static state of the unique optical identifier 1421 s in dependence on a relative position of the first and second optical elements 1421 e1 , 1421 e2. In this case, it will be appreciated that the static state is the arrangement of the superimposed first and second optical identifiers.

[0221] In the example shown, the at least one of the first and second optical elements 1421 e1 , 1421 e2 is rotatable relative to the other, such that rotation of the first and / or second optical elements 1421 e1 changes the static state of the superposed unique optical identifier 1421s, as indicated by the arrow R in figure 11 (c). The optical device 1421 preferably includes a movable adjuster 1421 a operatively engaged with a respective one of the first and second optical elements 1421 e1 , 1421 e2 so as to cause rotation thereof in response to user interaction with the adjuster 1421 a that moves the adjuster 1421 a. In preferred implementations, the adjuster 1421 a comprises a rotatable adjuster wheel 1421 a operatively engaged with the respective one of the first and second optical elements 1421 e1 , 1421 e2 via interlocking teeth, as illustrated in figure 11 (d). The adjuster wheel 1421 a is preferably shaped (e.g. hexagonal or octagonal) or otherwise configured (e.g. with features to snap to predefined rotary positions) to facilitate rotation in predefined increments. In other examples, the adjuster 1421 a is a slidable knob or other member that can be operatively engaged with the respective one of the first and second optical elements 1421 e1 , 1421 e2 via interlocking teeth to cause a change in the unique optical identifier 1421 s in response to linear movement of the adjuster 1421 a. Either one, or of both, of the first and second optical elements 1421 e1 , 1421 e2 can be rotatable in such ways.

[0222] In some examples, the optical device 1421 further comprises an adjustable occluder 1421 o arranged and configured to occlude part of the unique optical identifier 1421 s in dependence on a position of the occluder 1421 o relative to the window 252 so as to further change / vary the static state of the unique optical identifier 1421 s. In preferred implementations, the occluder 1421 o is rotatable relative to the window 252, as illustrated in figure 11 (d).

[0223] In some embodiments the authenticator device 340 includes one or more internally mounted light emitting devices (not shown), at least of which can be used to illuminate the first and second optical element and thus improve readability of the unique optical identifier 1421s.

[0224] Each relative position of the first and second optical elements 1421 e1 , 1421 e2, and optionally the occluder 1421 o, produces a different resulting optical identifier 1421 s providing different (variable but not random) ID information associated with the superposed geometric and optical properties that can be scanned / read using a conventional imaging device 122a such as a camera on a smartphone and compared to expected or possible ID information determined based on stored ID information (i.e. geometric and optical properties) associated with the individual first and second optical elements 1421 e1 , 1421 e2 (and optionally the occluder 1421 o) and preferably also an instructed user interaction (e.g. rotate the first optical element 1421 e1 a given number of increments clockwise or anticlockwise), as will be described in more detail below.

[0225] With reference again to figure 10, the authenticator device 340 includes a machine-readable multistate identifier in the form of a fluid device 1422, which is shown in more detail in figures 12(a) and 12(b). The fluid device 1422 comprises a sealed enclosure 1422e with and a transparent front wall 1422w and a deformable wall, wherein the enclosure 1422e contains a mixture of immiscible fluids 1422f, and a plurality of solid particles 1422p that can move substantially freely within the immiscible fluids 1422f. The immiscible fluids include a first liquid 1422f1 , and preferably further include a gas 1422f2 and / or and a second liquid 1422f3 which is immiscible with the first liquid. Preferably, the first and second liquids have different colours. Preferably, the plurality of solid particles 1422p have non-uniform properties (they are not all the same) such that at least some particles have different properties including one or more of: size, shape, colour, and other externally visible feature such as a surface pattern. The particles 1422p may have a predefined size distribution. In this way, the configuration of the immiscible fluids 1422f and particles 1422p in the mixture collectively forms, in a static state, a unique optical identifier readable through the transparent wall 1422t of the enclosure 1422e, and which is changeable in response to a force applied to the enclosure 1422e that deforms the deformable wall and causes a change in the static state (configuration) of the immiscible fluids 1422f and the particles 1422p contained therein.

[0226] Preferably, the transparent front wall 1422t is also deformable to also serve at the deformable wall, such that a force applied to the front wall 1422t redistributes the mixture within the enclosure 1422e. In other examples, the front wall 1422t is substantially rigid and a rear wall of the enclosure is deformable, such that a force applied to the front wall 1422t moves the enclosure (e.g. within a recess in the main body 251) and causes the rear wall to deform and redistribute the mixture.

[0227] In some examples, such as that shown in figures 10 and 12(a), the fluid device 1422 also includes a background image, pattern or visual / optical features 1422a that can combine with the mixture to collectively form the unique optical identifier 1422. The background pattern 1422 may also assist in determining or measuring relative positions and other features of the immiscible fluids 1422f and particles 1422p in the mixture from the scan data. In the example shown, the fluid device 1422 further includes a rotatable ring, dial or bezel 1422r surrounding the enclosure 1422e with one or more markings, preferably individual and distinct markings such as glyphs, that further form part of the unique optical identifier to be scanned / read. In this case, the unique optical identifier is further changeable in response to user interaction with the rotatable ring 1422r that rotates and changes the orientation of the ring 1422r relative to the enclosure 1422e as indicated by the arrows R, for use as an anti-fraud feature. In various examples, where the authenticator device 340 includes one or more internally mounted light emitting devices, at least one of these can be used as a back light to illuminate the fluid device 1422 and the mixture therein and enhance readability. In some examples, the mixture does not include particles 1422p. Each interaction with the fluid device 1422 which changes the static state of the mixture produces a different resulting optical identifier 1422 that can be scanned / read using a conventional imaging device 122a such as a camera on a smartphone and processed to extract unique ID information associated with the relative positions and shapes and other visible features of the immiscible fluids 1422f, particles 1422p and fluid device 1422. This ID information includes a non-random ID portion or features which can be verified against expected ID information determined based on stored ID information associated with the fluid device 1422 at the server system 110, and random ID portions of features for individuating a scan instance. In more detail, although the specific positions and shapes formed by the immiscible fluids 1422f and the positions of the particles 1422p in the static state are randomised in response to a user interaction with the fluid device 1422, and which produce random ID portions or features of the extracted ID information, there are certain features of the fluid device 1422 which are fixed and can be known to the server system 110 (the stored ID information), such as the volume of the respective immiscible fluids 1422f, the colours of the liquid(s), and the number, size, size distribution, shape, colours, and other externally visible features of the particles, and optionally the background pattern 1422a and markings on the ring 1422r. This non-random ID information can be extracted from the scan data and compared to expected ID information determined at the server system 110 based on such stored ID information to at least partially verify the identity of the user, while the random ID portions or features of the extracted ID information can be used to individuate the authentication attempt or process it is being used for (e.g. a transaction). Repeated scans after prompting a user to interact with the fluid device 1422 can be used to verify that the user is a live person and the authenticator device 340 is a real device.

[0228] With reference again to figure 10, the authenticator device 340 includes a machine-readable multistate identifier in the form of a shaker device 1423, which is shown in more detail in figures 13. The shaker device 1423 comprises a hollow enclosure 1423e containing therein a plurality of solid particles 1423p that can move substantially freely within the enclosure 1423e In this way, the enclosure 1423e and the arrangement of the particles 1423p therein collectively form, in a static state, a unique optical identifier readable through a transparent front wall of the enclosure 1423e, and is changeable in response to a force applied to the authenticator device 340 which causes a change in the static state (i.e. the arrangement) of the particles 1423p within the enclosure 1423e. Preferably, the plurality of solid particles 1423p have non-uniform properties (they are not all the same) such that at least some particles have different properties including one or more of: size, shape, colour, and other externally visible feature such as a surface pattern. The particles 1423p may have a predefined size distribution. In preferred examples, the particles 1423p have a non- spherical shape with at least one substantially flat side or edge to promote settling in a static state.

[0229] In the example shown, similar to the fluid device 1422, the hollow enclosure 1423e includes a static background image or optical pattern 1423a to form part of the resulting unique optical identifier and to assist in determining or measuring the relative positions of the particles 1423p from the scan data. Further, in some examples, such as that of figures 10 and 13, the hollow enclosure includes one or more interior and / or exterior occluding features 1423o for occluding one or more particles from the scan data. The occluding features 1423o may comprise opaque areas of the transparent front wall of the enclosure 1423e, and / or internal portions of the rear wall or base of the enclosure configured to receive and occlude one or more particles, such as openings, tunnels and / or sheds.

[0230] In the example shown, similar to the fluid device 1422, the shaker device 1423 the further includes a rotatable ring, dial or bezel 1423r surrounding the enclosure 1423e with one or more markings, preferably individual and distinct markings such as glyphs, that further form part of the unique optical identifier to be scanned / read. In this case, the unique optical identifier is further changeable in response to user interaction with the rotatable ring 1423r that rotates and changes the orientation of the ring 1423r relative to the enclosure 1423e as indicated by the arrows R, for use as an anti-fraud feature. In various examples, where the authenticator device 340 includes one or more internally mounted light emitting devices, at least one of these can be used as a back light to illuminate the fluid device 1423 and enhance readability.

[0231] Like with the fluid device 1422, each interaction with the shaker device 1423 which changes the static state of the particles 1423e produces a different resulting optical identifier 1423 that can be scanned / read using a conventional imaging device 122a such as a camera on a smartphone and processed to extract unique ID information associated with the relative positions and other visible features of the particles 1423p and shaker device 1423. This ID information includes a non-random ID portion or features which can be verified against expected ID information determined based on stored ID information associated with the fluid device 1422 at the server system 110, and random ID portions or features for individuating a scan instance. In more detail, although the specific positions of the positions of the particles 1423p in the static state are randomised in response to a user interaction with the shaker device 1423, and which produce random ID portions or features of the extracted ID information, there are certain features of the shaker device 1423 which are fixed and can be known to the server system 110 (the stored ID information), such as the number, size, size distribution, shapes, colours, and other externally visible features of the particles 1423p, and optionally the background pattern 1423a and markings on the ring 1423r.

[0232] Figure 14 shows a schematic cross-sectional view alternative embodiment of the shaker device 1423 wherein, instead of the hollow enclosure 1423e having a substantially flat rectangular crosssection as in figures 10 and 13, the hollow enclosure comprises a substantially transparent hollow rolling element 1423e (e.g. spherical or cylindrical) held by one or more retaining elements 1423z such that a portion of the rolling element 1423e (as indicated by the dashed box) is externally accessible for reading the unique optical identifier produced by the arrangement of particles 1423p, and receiving a user interaction that rotates the rolling element 1423 to thereby cause a change in the static state of the particles 1423p contained therein, as indicated by arrow R. Other features of the shaker device 1423 described with reference to figures 10 and 13 apply in the same way.

[0233] With reference again to figure 10, the authenticator device 340 further includes a machine-readable dynamic identifier in the form of a clock device 1424. The clock device 1424 comprises a first set of machine-readable hands 1424a driven by a motor assembly and configured to move around a clock face 1424f in a first direction according to a first movement and from a first start time, and a second set of machine-readable hands 1424b driven by the motor assembly configured to move around the clock face 1424f in a second direction according to a second movement and from a second start time that is different to the first start time. The clock device 1424 further includes one or more occluders 1424o configured to occlude at least a part of the clock face 1424f and thus occlude the first and / or second sets of hands in dependence on a position of the first and / or second sets of hands with respective to the one or more occluders 1424o. The first and second sets of machine- readable hands 1424a, 1424b and the one or more occluders 1422o superpose or otherwise combine to collectively form a dynamic unique optical identifier readable by a reader device, that is constantly changing and different for each scan instance.

[0234] In the example of figure 10, the sets of hands 1424a, 1424b are relatively featureless, however, in other examples (not shown), the first and second sets of machine-readable hands 1424a, 1424b can have a distinct machine-readable shape and / or one or more optically readable features such as a colour and / or surface pattern. The shapes and features of the hands 1424a, 1424b can then overlap (superpose), combine and occlude each other to for a different dynamically variable superposed unique optical identifier readable by a reader device. In this case, separate occluders 1424o are optional. The clock face 1424f itself may also include a background image, pattern or visual / optical features that can combine with the hands 1424a, 1424b and occluders 1424o where present to collectively form the dynamic unique optical identifier 1424.

[0235] In some examples, such as that shown in figure 10, the clock device further includes a rotatable ring, dial or bezel 1424r surrounding the clock face 1424f with one or more markings, preferably individual and distinct markings such as glyphs, that further form part of the dynamic unique optical identifier to be scanned / read. In this case, the clock device 1424 the dynamic unique optical identifier is further changeable in response to user interaction with the rotatable ring that changes the orientation of the ring 1424r relative to the clock face 1424f, for use as an anti-fraud feature, similar to the multi-state identifiers 1421 -1423 described above.

[0236] In some embodiments, the authenticator device 340 can include one or more internally mounted light emitting devices configured to illuminate the clock face 1424f and serve as a back light to enhance the readability of the resulting unique identifier. Alternatively or additionally, in some examples the markings on the rotatable ring 1424r can comprise at partially transparent portions of the ring 1424r and an internally mounted light emitting device configured to illuminate a selected one of the markings in dependence of the position of the rotatable ring with respect to the light emitting device.

[0237] The clock motor assembly is battery powered and configured to drive the first set of hands 1424a and the second set of hands 1424b according to different directions and movements. The first and second directions may be the same or different, and the first and second movements can include a fixed or time-dependent rotary speed / rate but which is preferably different for each movement. The motor assembly is further configured to enable to the first set of hands 1424a and the second set of hands 1424b to be started at different times, e.g. using separate starting mechanisms or inputs, e.g. which may be electronic inputs or mechanical inputs (e.g. which may engage certain gears in the motor assembly). In one example, the first set of hands 1424a is started when the authenticator device 340 is manufactured or assembled, and the second set of hands 1424b is started when a user registers their authenticator device 340. In some examples, the motor assembly can comprise separate motors and / or separate drive shafts for each set of hands 1424a, 1424b, or the movements of the first and second sets of hands 1424a, 1424b maybe linked via a set of gears and / or differentials. In some examples, the motor assembly is further configured to drive at least one of the one or more occluders 1424o (where present) around the clock face 1424f in a third direction according to a third movement which is preferably different to the first and second movements.

[0238] The combination of different start times, different movements, shapes of the hands and / or the presence occluders 1424o (which may optionally move) means that each instance of the clock device 1424 can provide a different resulting unique optical identifier 1424 providing different (variable but not random) ID information associated with the geometric configuration of the visible hands 1424a, 1424b and optionally the occluders 1424o that can be scanned / read using a conventional imaging device 122a such as a camera on a smartphone and compared to expected or predicted ID information determined based on stored ID information associated with clock device 1424, such as the first and second start times, the shape and features of the individual hands and / or the occluders 1424o where present, and the movements of the hands and optionally the occluders 1424o.

[0239] In some embodiments, the clock device 1424 further comprises a compass which is captured in the scan data and forms part of the unique optical identifier. The compass may be used to add context for the user verification process 400, e.g. by prompting the user to scan the authenticator device 140, 240, 340 or clock device 1424 while pointing the authenticator device 140, 240, 340 in a given direction. In some embodiments, at least one of the one or more occluders 1424o can be adjustable in size or shape, e.g. in an expanding or overlapping fan arrangement, so as to vary the shape and spatial extent of the occluded area.

[0240] Figures 15(a) and 15(b) show schematic plan and cross-sectional views of a further example of a multi-state identifier, in this case in the form of a roller device 1425 that can be integrated in various embodiments of the authenticator device 140, 240, 340. The roller device 1425 comprises one or more rolling elements 1425e, which may be spherical or cylindrical in shape, held by one or more retaining elements 1425z such that a portion of each rolling element (indicated by the dashed box in figure 15(b)) is externally accessible for receiving a user interaction and can freely rotate (similar to a bearing race). Each rolling element 1425e comprises a spatially non-uniform visual feature or pattern 1425a such that the externally accessible portions of the one or more rolling elements 1425e collectively form, in a static state, a unique optical identifier that is scanned / read by a reader device and which is changeable in response to user interaction with the roller device 1425 that causes a change in a rotational position of at least one of the one or more rolling elements 1425. Preferably, the roller device 1425 comprises a plurality of rolling elements 1425e arranged in a closed packed configuration or array, such that multiple rolling elements 1425e can be moved by the user moving and dragging their finger or thumb over the roller device 1425. Preferably, the spatially non-uniform visual feature 1425a of one or more rolling elements 1425e comprises areas of different colour or contrast that can be machine read. Preferably, the spatially non-uniform visual feature 1425a is implemented as a surface coating and / or marking, optionally encapsulated by a transparent coating to protect the features from deteriorating with use. In other examples, the visual features 1425a can be provided by an interior feature of the rolling element 1424e, such as encased objects or particles that are visible from the exterior of the rolling elements 1425e.

[0241] In this case, each interaction with the roller device 1425 which changes the rotational position of the rolling elements 1425e and thus the static state of the rolling elements 1425e produces a different resulting optical identifier 1425 that can be scanned / read using a conventional imaging device 122a such as a camera on a smartphone and processed to extract unique ID information associated with the visible features 1425a of the rolling elements 1425e. As a user moves their finger or thumb over the rolling elements 1425e, each rolling element 1425e will rotate in a different way and by a different amount, as indicated by the arrows R1 and R2 in figure 15(b), thus producing a different unique optical identifier with each interaction and scan instance. Like with the fluid device 1422 and the shaker device 1423, this extracted ID information includes a non-random ID portion or features which can be verified against expected ID information determined based on stored ID information associated with the roller device 1425 at the server system 110, and random ID portions or features for individuating a scan instance. In more detail, although the specific rotational positions of the rolling elements 1425 and their respective visual features 1425a in the static state are randomised in response to a user interaction with the roller device 1425, and which produce random ID portions or features of the extracted ID information, there are certain features of the roller device 1425 which are fixed and can be known to the server system 1 10 (the stored ID information), such as the size and arrangement of the rolling elements 1425e, and the visual features 1425a of each rolling element 1425e, and any other externally visible features of the device 1425.

[0242] In some examples, the authenticator device 140, 240, 340 can comprise a multi-state identifier in the form of a deformable topographic surface of the device. The deformable topographic surface comprises deformable projections or fibres configured to form, in a static state, a unique topographic and / or optical identifier readable by a reader device, and which is changeable in response to a user interaction with the deformable topographic surface that deforms at least some of the deformable projections or fibres and causes a change in the static state thereof. The deformable topographic surface can be provided by a natural material or a suitably configured synthetic material. For example, the deformable topographic surface may be a fabric such as velvet or other threaded material, or animal hide I skin I leather or suede, or any material or surface with the deformable property such that their topography, lean and / or curve may be altered by hand or surface movement between scans. Feature of the unique topographic configuration can be scanned / read using a conventional imaging device 122a such as a camera (e.g. through variations in reflectance) or a LIDAR functionality on a smartphone and processed to extract unique ID information associated with the detected features. The wear and tear of this identifier can also add a unique feature. The wear and tear can be monitored over time with each scan saved with the record, and eventually become a unique static feature of the surface that can be stored in the server system 110 used for user verification, e.g. compared to other identifiers to further ascertain its validity by scanning and machine reading its deterioration over time, thereby increasing its usefulness as an individuator and identifier.

[0243] With reference again to figure 10, in some embodiments, the authenticator device 340 further includes a hardware crypto wallet module 253 configured to securely store and provide access to a user’s cryptographic asset data. In this case, the authenticator device 240 includes appropriate processing circuitry for implementing the hardware crypto wallet module 253, a battery 254, one or more control inputs 255 for controlling an operation of the hardware crypto wallet module 253, and a data port 256 coupled to the hardware crypto wallet module 253 for connecting to a computing device such as the mobile device 120. The authenticator device 340 may also include one or more additional control inputs 255, such as for operating one or more internally mounted light emitting devices as described above.

[0244] Figure 16 shows an example method 300 of authenticating an asset 130 using the above-described system 100 according to an embodiment of the invention. The asset 130 may be physical or digital but must comprises one or more machine-readable unique identifiers 132, as described previously. The authentication method 300 is preferably facilitated in part by a software application (mobile or web app) running on the mobile device 120 which establishes a secure connection to the server system 110 and manages the data acquisition, transmission and receipt of data and the various requests to and from the server system 110. The software application preferably comprises a graphical user interface (not shown) providing the necessary options, input fields and output fields for initiating the method 300, displaying the various prompts, requests and messages received from the server system 110, and responding to the prompts / requests in order to guide the user through the authentication process 300. The method 300 may be used as part of a transaction process, or in supply chain management as part of a track and trace process.

[0245] In step 301 , the server system 110 receives an authentication request from the mobile device 120 to authenticate an asset 130, which may be a user’s physical media asset 130 or other asset 130. In some examples, this may be triggered by a user, who is logged into their user account on the software application, initiating the authentication process for a specific asset 130 via the software application. The authentication request may thus be associated with a specific user and an asset 130 linked to the user’s account. The authentication request will therefore comprise enough information to identify the user or user account and the asset 130 to be authenticated (e.g. the information in the request may include the username or a user ID, and the title and type of the asset 130, in a suitable format). In some examples, the asset 130, e.g. a physical asset 130 or digital asset 130, is owned by the user who is attempting to authenticate it. In other examples, the asset 130 is not owned by the user who is attempting to authenticate it, e.g. this may be the case in various supply chain management applications where assets 130 are tracked and traced during transit by observers and / or individuals who are not the owners of the asset 130. In such scenarios, the authentication request need not originate from the same mobile device 120 as the user who is attempting to authenticate the asset 130 (the authenticating user), but may for example originate from another user or computing device in communication with the server system 110, e.g. associated with the supplier or owner of the asset 130.

[0246] In step 302, the server system 110 sends a first request to the mobile device 120 of a user for first ID information from one or more UIDs 132 on the asset 130. The server system 110 may generate the first request based, at least in part, on information in the user database 112 regarding the UIDs 132 associated with the asset 130 being authenticated - that is, the server system 110 needs to at least know what UIDs 132 should be on the asset 130 before it can request ID information from it. Where the asset 130, e.g. a physical asset 130, comprises a plurality of different machine-readable UIDs 132a-132d, each containing different first ID information for identifying the asset 130, the first request may comprise a request for first ID information from each of the plurality of UIDs 132a- 132d on the asset 130. Alternatively, the first request may comprise a request for first ID information from a particular selection of one or more of the UIDs 132a-132d on the asset 130. In this case, the selection may be generated randomly based on the list of UIDs 132 associated with the registered asset 130. Alternatively, the selection may be based on one or more predefined criteria, e.g. a user’s prior authentication request history, or any further information included in the authentication request. Alternatively, the selection may be specified in the authentication request by the authentication requesting entity or party. The database 112 may be queried for any relevant information needed for generating the first request.

[0247] The authenticating user is then prompted, via the software application on the mobile device 120, to scan or read the requested UIDs 132 using their mobile device 120. As such, the method 300 may further comprise reading, by the mobile device 120 in response to the first request, the requested one or more UIDs 132 on the (e.g. physical) asset 130. This involves acquiring, by the mobile device 120, scan data comprising the ID information using the appropriate ID reader 122a, 122b. Following the reading / acquisition step, the mobile device 120 sends the first ID information or scan data comprising the first ID information to the server system 110. The first ID information or scan data is not stored on the mobile device 120 thereafter - which is required for security. That is, the mobile device 120 is configured to store the first ID information or scan data only temporarily for the purposes of transmission to the server system 110, and then delete first ID information or scan data. The first ID information or scan data from each requested UID 132 is a separate piece or packet of data sent by the mobile device 120 to the server system 110 and is associated with the respective UID 132, e.g. the data may include information identifying the UID 132, such as a name, type, or code. Preferably, data is encrypted before sending to the server system 110, where it is decrypted.

[0248] In step 303, the server system 110 receives the requested first ID information, or scan data comprising the first ID information, from the mobile device 120. The server system 110 may be configured to process the received data to extract the first ID information where necessary. Where necessary, this may involve sending the data to one or more third party servers (e.g. the manufacturer of the identifier 132) for processing, and receiving the extracted ID information from the one or more third party servers. In step 304, the server system 110 compares the received / requested first ID information with stored first ID information associated with the UIDs 132 on the user’s registered asset 130. Comparing comprises querying the user database 112 for the relevant ID information associated with the user’s registered asset 130. Preferably, the comparison is like-for-like, that is, the received / requested first ID information from a given UID 132 is compared with the corresponding stored ID information for that same UID 132 (i.e. rather than comparing each received / requested first ID information against all the stored ID information associated with the asset 130 to look for a match).

[0249] In step 305, the server system 110 authenticates the asset 130 if the received first ID information matches the stored first ID information. This preferably involves generating and sending a message to the mobile device 120 confirming success or failure of the authentication. Preferably, a record of every interaction with the server system 1 10 is recorded in the database 112. Alternatively or additionally, a record of the interaction (e.g. the authentication request) is stored in a distributed ledger system, which may be a third-party system, as in known in the art.

[0250] The record preferably includes one or more of: a time of the authentication request, a location of the user(s) mobile device(s), a result of the authentication request, the unique identifiers scanned, scan data collected, information associated with the asset and / or authentication request, and information associated with the authenticating user(s) and / or the authentication requesting entity or party.

[0251] The authentication method 300 may optionally involve the use of the authenticator device 140, 240, 340 to verify the identity of the user and improve the security of the authentication process. In this way, the asset 130 can only be authenticated if the asset 130 is the asset registered to a user (which need not be the same as the authenticating user), and the person purporting to be the user is in fact the user registered with the authenticating device (and a real live person), or the person attempting to authenticate the asset 130 is who they are purporting to be. This corresponds to the user verification process described further in method 400 below.

[0252] In this case, the method 300 further comprises a step 302a of sending, by the server system 110 in response to the authentication request, a second request to the mobile device 120 for second ID information from one or more machine-readable UIDs on a user’s authenticator device 140, 240, 340. Similar to the first request in step 302, the server system 110 may generate the second request based, at least in part, on information in the user database 112 regarding the UIDs 142 associated with the user’s registered authenticator device 140 (which may include dynamic and / or multi-state UIDs 1421 -1425). Where the authenticator device 140 comprises a plurality of different machine-readable UIDs 142a-142d, each containing different second ID information for identifying the authenticator device 140, the second request may comprise a request for second ID information from each of the plurality of UIDs 142a-142d, 1421-1425 on the authenticator device 140. Alternatively, the second request may comprise a request for second ID information from a particular selection of one or more of the UIDs 142a-142d on the authenticator device 140. In this case, similar to step 302, the selection may be generated randomly based on the list of UIDs 142a- 142d associated with the user’s registered authenticator 140. Alternatively, the selection may be based on one or more predefined criteria, e.g. a user’s prior authentication request history, or any further information included in the authentication request. In various examples, the selection may be specified in the authentication request by the authentication requesting entity or party. The database 112 may be queried for any relevant information needed for generating the second request.

[0253] The authenticating user is then prompted, via the software application on the mobile device 120, to scan or read the requested UIDs 142 of its authenticator device 140, 240, 340 using their mobile device 120, as described above in step 302. Following the reading / acquisition step, the mobile device 120 sends the second ID information or scan data comprising the second ID information to the server system 110, whereby the second ID information or scan data is not stored on the mobile device 120 thereafter.

[0254] In step 303a, the server system 110 receives the requested second ID information, or scan data comprising the second ID information, from the mobile device 120. The server system 110 may be configured to process the received scan data to extract the second ID information where necessary. This may involve sending the data to one or more third party servers (e.g. the manufacturer of the UID 142) for processing, and receiving the extracted ID information from the one or more third party servers.

[0255] At step 304, in addition to comparing the received / requested first ID information with stored first ID information, the server system 110 compares the received / requested second ID information with stored second ID information associated with the UIDs 142 on the user’s registered authenticator device 140. As described previously, comparing may comprise querying the user database 112 for the relevant ID information associated with the user’s registered physical media asset 130, and is preferably a like-for-like comparison. Further details of the user verification process are described below with reference to method 400, any of all of which features can be incorporated into method 300.

[0256] Finally, at step 305, the server system 110 authenticates the asset 130 if the received / requested first and second ID information match the respective stored first and second ID information.

[0257] Where the authenticator device 140 comprises one or more drawers 148a-148d, each with a rotatable carrier portion 1481 on which at least one of the one or more UIDs 142a-14d is provided, the second request in step 302a may be a request for reading one or more machine-readable UIDs 142a-142d when in a particular orientation relative to the respective drawer 148. In this case, the second request preferably comprises a message prompting the user to adjust the orientation of a carrier portion 1481 containing a requested UID 142 by a predetermined amount relative to a current orientation or a user-defined starting orientation of the carrier portion 1481 . In this way, the requested orientation is the result of adjusting (by the user) the orientation by the requested amount. The start positions are a user-defined set of orientations for each carrier portion 1481 , that are stored in the database (similar to a password). Where the requested adjustment is from the current position, the previous requested orientation should in principle be the current orientation of the carrier portion 1481. As such, the user may, in response to the request to adjust the orientation of the requested carrier portion(s) 1481 by a respective predetermined amount, either set the carrier portion 1481 to the start position and then adjust the orientation by the predetermined amount, or the user may simply adjust the orientation from the current position by the predetermined amount.

[0258] In this case, step 303a may comprise processing the scan data to determine the relative orientation of the carrier portion 1481 , and step 304 may further comprise comparing the requested orientation to an expected orientation determined based on the previous requested orientation or the user- defined starting position and the current requested adjustment. Authentication in step 305 may be conditional upon matching ID information and orientations.

[0259] Preferably, the method 300 further comprises authenticating the asset 130 on the basis of matching ID information and geolocations of the physical media asset 130 and the authenticator device 140. In this way, the asset 130 can only be authenticated if the asset 130 is the asset registered to a user, the person purporting to be the user is in fact the user, and if the user has the asset 130 and authenticator device 140 with them together at the same time.

[0260] In this embodiment, the mobile device 120 is further configured to determine its geolocation at a time of scanning the UIDs 132, 142 and send the geolocation information to the server system 110 along with the data containing the ID information. For example, the mobile device 120 may comprise one or more locator modules 126, such as a GPS module or any other suitable location / tracking technology.

[0261] Then, at steps 303 and 303a, the server system 110 further receives, respectively, a first geolocation of the mobile device 120 associated with a time of reading the requested UIDs 132 on the asset 130, and a second geolocation of the mobile device 120 associated with a time of reading the requested UIDs 142 on the authenticator device 140, 240, 340.

[0262] At step 304, in addition to comparing the received / requested first and second ID information with stored first and second ID information, the server system 110 compares the received first and second geolocations associated with the respective first and second ID information.

[0263] Finally, at step 305, the server system 110 authenticates the asset 130 if the received first and second ID information match the respective stored first and second ID information, and if the first and second geolocations substantially match.

[0264] In some example scenarios, authenticating an asset 130 may involve not only the authenticating user (a first user), but also one or more further authenticating users (second users) who may be observers, witnesses or interlocutors to the authentication process being carried out by the first authenticating user. The second user may be specified in the authentication request, e.g. based on one or more predefined criteria associated with the asset 130 or specified by the requesting party / entity. In this case, a further / second user is registered with the server system 110 with its own authenticator device 140, 240, 340, and the method 300 comprises performing the steps to additionally authenticate the identity of the further / second user, and the authenticating step 305 further includes authenticating the asset 130 if the received first ID information matches the stored first ID information and if the first user’s identity and the second user’s identity is authenticated. In this case, the record of the authentication request includes including information associated with the second user and the identifiers scanned on the second user’s authenticator device 140, 240, 340.

[0265] In a further embodiment, where the authenticator device 140 is an active device 240 as described above with reference to figure 8, the method 300 can comprise steps 302b, 302c and 303b. Steps 302b, 302c and 303b can be performed instead of or in addition to steps 302a and 303a. In step 302b, the server system 110 sends, in response to the authentication request, a third request to the mobile device 120 for third ID information from a user’s authenticator device 240. At step 302c, the authenticator device 240 generates third ID information based, at least in part, on second ID information from UIDs 142a-142d on the authenticator device 240, and outputs the third ID information, by the one or more output devices 244a, 244b (i.e. a display and / or speaker) of the authenticator device 240. The third ID information comprises visual and / or audio information, and is preferably a dynamic image output on the display 244a with an optional audio component output simultaneously by the audio output 244b. The authenticator device 240 can be configured to generate the third ID information using suitable pre-programmed algorithms. The authenticator device 240 generates and outputs the third ID information in response to a user input via the one or more inputs 246 (i.e. via input buttons or touch screen display 244a). The user then scans or reads the third ID information using their mobile device 120. This preferably comprises capturing image or video scan data of the dynamic image output by the authenticator device 240. Following the reading / acquisition step, the mobile device 120 sends the third ID information or data comprising the second ID information (preferably encrypted) to the server system 110, and then deletes the third ID information or scan data thereafter.

[0266] At step 303b, the server system 110 receives the third ID information, or scan data comprising the third ID information. The received data may be processed by the server system 110 to extract the third ID information where necessary. At step 304, the server system 110 further compares the received / requested third ID information to corresponding third ID information generated using stored second ID information associated with the UIDs 142a-142d on the user’s authenticator device 240. For example, the server system 110 can use the same algorithms as used by the processor 248 of the authenticator device 240 to generate the third ID information from the stored second ID information. Step 303b may further comprise receiving third geolocation of the mobile device 120 associated with a time of reading / scanning the third ID information.

[0267] At step 305, the server system 110 authenticates the physical media asset 130 if the received / requested first ID information matches the stored first ID information, and if the received / requested third ID information matches the corresponding third ID information generated by the server system 110, and optionally also conditional upon the first and third geolocations substantially matching, and / or the received / requested second ID information matching the respective stored second ID information.

[0268] Figure 17 shows an example method 400 of verifying or authenticating a user’s identity using the above-described authenticator device 140, 240, 340 and system 100 according to an embodiment of the invention. The method 400 can be used as part of the authentication method 300 described above (see e.g. steps 302a and 303a), as part of the transaction method 500 described below with reference to figure 11 , or as part of a third-party verification process, or a transaction or a user account sign in process. The method 400 is preferably facilitated in part by a software application (mobile or web app) running on the mobile device 120, as described previously.

[0269] In step 401 , the server system 1 10 sends, in response to a verification request to verify a user’s identity, an ID request to the user mobile device 120 for ID information from one or more machine- readable UIDs 142 on the user’s registered authenticator device 140, 240, 340. The verification request is received from a requesting entity. This may be a third party entity (where the method 400 is used as part of a third party verification process), the mobile device 120 of the user, or it may be generated / initiated within the server system 110 as part of method 300 or 500, or any other method described herein.

[0270] As described above with reference to method 300, the server system 110 may generate the ID request based, at least in part, on information in the user database 112 regarding the UIDs 142, 1421-1425 associated with the user’s registered authenticator device 140. Further, where the authenticator device 140 comprises a plurality of different machine-readable UIDs 142a-142d, 1421-1425, optionally with rotatable carrier portions 1481 and / or including one or more dynamic / multi-state identifiers 1421 -1425 described above, the ID request may comprise a request for ID information from each of the plurality of UIDs 142a-142d, 1421 -1425 on the authenticator device 140 optionally in particular orientations (where applicable), or from a particular selection of one or more of the UIDs 142a-142d optionally in particular orientations and / or including one or more of the dynamic / multi-state UIDs 1421 -1425.

[0271] In the latter case, similar to method 300, the particular orientations and / or the selection of UIDs to be scanned may be generated randomly based on the list of UIDs 142a-142d, 1421 -1425 associated with the user’s registered authenticator 140, 240, 340, or generated based on one or more predefined criteria, e.g. a user’s prior authentication request history, the requesting entity, the context of the verification request (e.g. in what type of process is the verification request being made), or any further information included in the authentication request. For example, where the verification request is being made in the context of a transaction or sign in process, the selection may be generated to satisfy a security level, where the security level can be determined at the server system 110 based, at least in part, on a required security level indicated by the requesting entity in the verification request and / or one or more predefined criteria (e.g. minimum security levels) associated with information in the authentication request. The database 112 may be queried for any relevant information needed for generating the ID request. The user is then prompted, via the software application on the mobile device 120, to scan or read the requested UIDs 142 using their mobile device 120, as described above in method 300. Following the reading / acquisition step, the mobile device 120 sends the ID information or scan data comprising the ID information (preferably encrypted) to the server system 110, and then deletes the ID information or scan data. Where the user authenticator device 140 includes one or more multistate identifiers 1421 -1423, 1425, at least one of which is specified in the ID request, the ID request may include a prompt to perform an appropriate user interaction with the respective multistate identifier 1421 -1423, 1425 before obtaining scan data to change the static state of the respective multi-state identifier 1421 -1423, 1425. For example, the prompt may be to rotate the first and / or second optical elements of the optical device 1421 by a certain amount / number of increments which may be specified in the ID request, or pressing the fluid device 1422, or shaking the shaker device 1423, or rubbing or moving the rolling elements of the device 1425, and / or rotating a dial on any of the dynamic / multi-state UIDs 1421 -1425 randomly or to a particular orientation.

[0272] At step 402, the server system 110 receives the requested ID information or scan data comprising the ID information read by the mobile device 120. As described in step 303a, the received data may be processed by the server system 110 to extract the ID information where necessary. The server system 110 may be configured to process scan data (image or video data) obtained from the one or more multi-state identifiers 1421 -1423,1425 and / or a dynamic identifier 1424 to extract ID information, e.g. associated with geometric and optical properties of the respective dynamic / multi- state identifier 1421 -1425. This may involve the use of one or more programs, algorithms and / or computer vision techniques configured or trained to extract the relevant ID information for the respective multi-state / dynamic identifier 1421 -1425. As discussed above, the ID information includes a non-random portion or features (such as colours, shapes, sizes of particles or fluids, or hands,

[0273] At step 403, the server system 110 compares the received / extracted requested ID information with stored ID information associated with the UIDs 142 on the user’s registered authenticator device 140, 240, 340 or expected / predicted ID information determined based at least in part on the stored ID information. As described previously, comparing may comprise querying the user database 112 for the relevant ID information associated with the user’s registered authenticator device 140, and is preferably a like-for-like comparison.

[0274] In this case of dynamic or multi-state UIDs 1421 -1425, the comparing step 403 comprises comparing the extracted ID information read or determined from scan data of the multi- state / dynamic UID(s) 1421 -1425 to corresponding expected / predicted ID information generated at the server system 110 using the stored ID information associated with the respective multi- state / dynamic UID on the user’s registered authenticator device 140.

[0275] In more detail, each multi-state or dynamic unique identifier 1421-1425 will have different stored ID associated with various fixed and known properties of it which enable a meaningful comparison to at least part of the extracted ID information to be made, as described above. For example, stored ID information associated with the optical device 1421 preferably includes at least the features of the individual optical identifiers of the first and second optical elements and their optical properties from which the expected superposed optical identifier for any given relative position of the first and second optical elements can be determined, optionally taking into account the relative position of any adjustable occluders. The stored ID information associated with a fluid device 1422 preferably includes properties of the immiscible fluids and optionally the particles, such as one or more of a colour and volume of the immiscible fluids, and one or more of the number of particles, the size, size distribution, shape, colour and / or other externally visible feature (such as a surface pattern) of the particles, and optionally the static background image, pattern or graphic of the enclosure and / or the markings on the rotatable dial. The stored ID information associated with a shaker device 1423 preferably includes properties of the particles, such as one or more of: a number of particles, a size, size distribution, shape, colour and / or other externally visible feature (such as a surface pattern) of the particles, and optionally the static background optical pattern of the enclosure and / or the markings on the rotatable dial. The stored ID information associated with the roller device 1425 preferably includes the spatially non-uniform visual feature on each rolling element, and optionally one or more geometric features of the rolling elements. The stored ID information associated with a clock device 1424 preferably includes the first and second start times, the first and second movement parameters, the configuration of the first and second hands when started (which can be scanned and sent to the server system 110 at the time of starting), and may further include the shapes and features of the hands and optionally the occluders, the static background image or graphic and / or the markings on the rotatable dial. Based on the stored ID information for a given dynamic / multi-state UID, expected or possible configurations of the respective identifier can be determined for comparison to the ID information extracted from the scan data.

[0276] Finally, at step 404, the server system 1 10 authenticates the user’s identity if the received ID information matches the stored ID information. This preferably involves generating and sending a message to the mobile device 120 or the requesting entity confirming success or failure of the authentication.

[0277] Preferably, a record of the user authentication request / process and the interactions with the server system 110 is stored in the database 112 or in a distributed ledger system, which may be a third- party system, as in known in the art. This can be used to build up a timeline / history for each user. The record preferably includes one or more of: a time of the authentication request, a location of the user mobile device, a result of the authentication / verification request, the unique identifiers scanned, scan data collected, information associated with the authentication / verification request, and information associated with the authenticating user(s) and / or the authentication requesting entity or party.

[0278] Where dynamic and / or multi-state UIDs 1421 -1425 are included in the ID request, the authenticating step 404 includes authenticating the user’s identity if at least a first (non-random) portion or feature of the extracted ID information from the multi-state / dynamic identifier 1421 -1425 matches the expected ID information. For multi-state UIDs 1421 -1425 that include a random portion or feature of the ID information, such as the fluid device 1422 and the shaker device 1423, the authenticating step 404 optionally includes authenticating the user’s identity if a second (random) part of the extracted ID information does not match the any ID information stored in the user database (this corresponds to checking that the server system 110 has not seen the scan data before in order to individuate the authentication attempt). In some embodiments, the ID request can comprise a request for reading biometric ID information from the user’s hand including one or more of the user’s digits, and a finger recognition process is performed at the server system 110 to extract biometric ID information / features from the scan data and compare to stored biometric ID information for the user’s digits to check for a match or threshold similarity. The ID request can include a prompt to obtain scan data (image or video data) of one or more user’s digits 10 preferably holding the user authentication device 140 such that at least a portion of the user’s nails 10n are visible, as illustrated in figure 18. The digits 10 can include the fingers 10f and thumb 10t. In this way, the user authenticator device 140 is also visible and identifiable in the scan data. Alternatively, the user may be prompted to obtain scan data of one or more user’s digits 10, nail side up, resting against or positioned over the user authentication device 140 (e.g. the front or back of the authenticator device 140) such that at least a portion of the user’s nails and the user authentication device 140 are visible and included in the scan data.

[0279] In this case, the step of comparing 403 comprises processing the image or video data to extract biometric ID information comprising one or more biometric features associated with one or more of the user’s digits, and comparing the extracted biometric features with stored biometric features associated with the user’s digits to determine a similarity metric. In some examples, this comparison process can be performed using a machine learning model. Then, the authenticating step 404 includes authenticating the user’s identity if the similarity metric meets a threshold similarity metric indicative of a match.

[0280] The finger / hand recognition process preferably uses features of the of the digits 10 other than the fingerprints as identifying features. The biometric ID features preferably include one or more of: a digit dimension, a digit geometry, a digit position, feature of the user’s grip of the authenticator device 140, a nail feature, a skin feature, an anatomical feature, and a worn object. For example, nail features can include: nailbed features; nail lengths; lunula; nail ridges; depth of nails past the lunula or nail bed; width of nail; cut angles; quicks; fungal infections; detritus; newly applied and worn nail varnish. Skin features can include skin tone, creases, rashes, scars, tattoos, bruises, cuts, scabs, grazes, eczema; psoriasis, other temporary or permanent skin irritations, or other marks. A worn object can include jewellery, rings etc. The machine learning model can be used to learn over time what the user’s hand looks like, including certain features and behaviours and nuances of the user’s digits in use (e.g. grip, finger positions, finger pressure which may e.g. manifest as more or less colouring in the fingertips or other visible feature) that are unique to a user. In this way, the finger recognition process can detect potentially fraudulent or unauthorised use of the authenticator device 140 by recognising that the hand in the scan data is not that of the registered user. Wearable items, such as jewellery or a thimble, can also become an identifying feature of the user’s hand, and in some example, the ID request can include a prompt to wear a particular item that the user has worn before to further challenge the veracity of the user. Where the authenticator device 140 is an active device 240 as described above with reference to figure 8, the method 400 can optionally comprise steps 401 a, 401 b, 402a, 403a and 404a. Steps 401 a to 404a can be performed instead of or in addition to steps 401 to 404. Steps 401 a-403a are equivalent to steps 302b, 302c and 303b in method 300.

[0281] In step 401 a, the server system 110 sends, in response to the authentication request, a second ID request to the mobile device 120 for additional ID information from a user’s authenticator device 240. At step 401 b, the authenticator device 240 generates (in response to a user input via the one or more inputs 246) additional ID information based, at least in part, on ID information from UIDs 142a-142d on the authenticator device 240, and outputs the additional ID information, by the one or more output devices 244a, 244b (i.e. a display and / or speaker) of the authenticator device 240. The user then scans or reads the additional ID information (visual and / or audio) using their mobile device 120. This preferably comprises capturing image or video scan data of the dynamic image output by the authenticator device 240. Following the reading / acquisition step, the mobile device 120 sends the additional ID information or scan data comprising the additional ID information to the server system 110 (and deletes the additional ID information or scan data thereafter).

[0282] At step 402a, the server system 110 receives the requested additional ID information, or scan data comprising the additional ID information. The received data may be processed by the server system 110 to extract the ID information where necessary.

[0283] At step 403a, the server system 110 compares the received / requested additional ID information to corresponding additional ID information generated using stored ID information associated with the UIDs 142a-142d on the user’s authenticator device 240.

[0284] At step 404a, the server system 110 authenticates the user’s identity if the received / requested additional ID information matches the corresponding additional ID information generated by the server system 1 10. This preferably involves generating and sending a message to the mobile device 120 or the requesting entity confirming success or failure of the authentication. Where steps 401 a-404a are performed in addition to steps 401 -404, the authentication is preferably further conditional upon the received ID information from the UID 142a-142d matching the stored ID information.

[0285] In some embodiments, method 300 can include sending, by the server system, a further ID request to the user mobile device for further ID information before the user’s identity can be authenticated in step 404, as indicated by arrow 405 in figure 17. In one example, the further ID request may be sent if a determined confidence level in the (previous) ID information obtained from the (previous) ID request is below a threshold confidence level, wherein the confidence level can be determined by the server system 110 at step 403 based, at least in part, on the comparison of the received / extracted ID information to stored ID information. Alternatively or additionally, the further ID request may be sent if it is specified, e.g. in the authentication request, by an authentication requesting entity or party, or by any other party involved in the process. For example, this additional scan / check step may be required to satisfy a security level associated with the auth enticat io n / verification request, where the security level can be determined at the server system 110 based, at least in part, on a required security level indicated by the requesting entity in the verification request and / or one or more predefined criteria (e.g. minimum security levels) associated with information in the authentication request (such as the context of the authentication request).

[0286] The further ID information may comprise one or more of the following: ID information from one or more different machine-readable unique identifiers on the user’s authenticator device to those which were scanned previously; ID information from a multi-state unique identifier 1421 , 1423-1425 after performing a user interaction with the multi-state unique identifier that causes a change in the state of the multi-state unique identifier; ID information from a UID (such as a dynamic or multistate unique identifier 1421 -1425) after performing an a user interaction with the device that causes a change in the resulting identifier, such as moving or rotating a dial or other adjustable feature; biometric ID information from one or more of the user’s digits.

[0287] In this case, the method 400 further comprises receiving, at the server system, scan data from the user mobile device comprising the further ID information from each requested unique identifier on the user’s authenticator device; comparing, at the server system, the received further ID information with stored ID information associated with the unique identifiers on the user’s registered authenticator device as described above in relation to step 403; and authenticating the user’s identity if the received further ID information matches the stored ID information as described above in relation to step 404.

[0288] It will be appreciated that the further ID request, in more generally asking the user to scan or rescan an identifier after performing a certain (in some cases, specific) user interaction with it which changes the scan data and / or the resulting unique optical identifier captured in the scan data, can serve to increase the security of the verification process and reduce the risk of fraud by demonstrating that the person is a live person and the authenticator device 140 is a real and genuine authenticator device 140.

[0289] In preferred embodiment, the method 400 further comprises associating a unique machine-readable optical identifier 150 with the record of the user authentication request, referred to herein as a record identifier 150, wherein the record identifier 150 contains or encodes record ID information linked with the record of the user authentication request. The record identifier 150 is preferably a digital mark or object that is stored at the server system 110 in association with the record, and which can be associated with a corresponding machine-readable physical record identifier 150p. The record identifier 150, and the corresponding physical record identifier 150p (where present), serves as a machine-readable and scannable receipt of the process completed using the server system 110, whereby information associated with the record is retrievable or accessible (from the server system 110 or a distributed ledger system storing the record) in response to receiving, at the server system 110 a request containing the record ID information linked with the record. In some examples, the request can contain scan data obtained from a scan of the record identifier 150 (whether digital or physical) from which the record ID information can be extracted. In some examples, where the user verification method 400 is used as part of a transaction process of any kind, the record identifier 150 can be used as proof of transaction, ownership, or completion of work, status of work, or status of any other process or task.

[0290] In some examples, a physical or digital item involved in the transaction process can be marked (physically or digitally) with the record identifier 150 as proof of transaction or ownership, and which can be scanned by a mobile device 120 to access / retrieve the associated information. For example, a physical product or a physical document can be marked with a corresponding physical identifier 150p, e.g. using a label with the record identifier 150 printed on it, or by directly printing the record identifier 150 onto the item. Certain physical items may also be marked by engraving, stamping or any other means of marking a physical item. In some cases where marking the physical item is not appropriate or possible, a physical record identifier 150p can be produced for keeping in the possession of the transactor / owner for proof. In other examples, the record identifier 150 can be embedded into a digital item, such as a digital document or media file, which is visible and scannable when rendered on a display device. In other examples, the record identifier 150 can be provided to or accessible by the mobile device 120 for rendering on a display of the mobile, which can then be scanned by another user to access / retrieve the associated information for proof / verification of the transaction (e.g. where a ticket is purchased, the record identifier 150 can serve as an electronic ticket). Once a physical or digital asset is marked with the record identifier 150, it may become an asset 130 as described above, in which case the record identifier 150 can become a UID for identifying the asset 130.

[0291] In some embodiments, the step of associating comprises generating, by the server system 110, the record identifier 150 for the record of the user authentication request (and / or process involving the user verification request), and storing, at the server system 110, the record identifier 150 for the record and / or its ID information in association with the record in the user database. In preferred implementations, the record identifier 150 is generated, based at least in part on the scan data, extracted ID information from the requested UIDs of the user authenticator device 140 and / or information in or associated with the record. In this case, the generated record identifier 150 is preferably a digital image containing or encoding the record ID information.

[0292] Figures 19(a) shows an example of a record identifier 150 comprising a unique optical identifier generated based on scan data obtained from the optical device 1421 shown in figure 11. Figures 19(b) shows an example of a record identifier 150 comprising a unique optical identifier generated based on scan data obtained from the fluid device 1422 shown in figure 12. In some examples, the record identifier 150 is generated using a machine learning model.

[0293] Alternatively, a record identifier 150 can be provided to the server system 110 for storing in association with the record. For example, the record identifier 150 can selected or generated by the user or a third-party entity or server. In this case, the step of associating comprises receiving, at the server system 110, a unique machine-readable optical identifier (record identifier) 150 from the user mobile device or a third-party entity, and storing, at the server system 110, the record identifier 150 for the record and / or its ID information in association with the record in the user database. Where the record identifier 150 is generated by a third-party entity or server, the method 400 may comprise (prior to the receiving of the record identifier 150) sending a request for the record identifier 150 to the third-party entity or server.

[0294] Figure 20 shows a schematic diagram of corresponding machine-readable physical record identifier 150p produced as a label for attaching to a physical item or asset. In addition to, or instead of, the generated or user-provided unique optical identifier for the record identifier 150 (as shown in figure 19), the physical identifier 152p can include any combination of physical machine-readable UID tags 152a-d described previously in relation to the label of the physical media asset 130 (e.g. one or more of: a quantum-PUF tag 152a, a surface topography-based tag 152b, an RFID / NFC tag 152c, and a further UID 152d selected from the group: an encoded image, such as a QR code; a symbol sequence or alphanumeric code; a unique graphic or image; a human fingerprint; a microchip).

[0295] In other examples, the machine-readable physical record identifier 150p can be represented as a 3D object (e.g. to be kept in possession of the user) with certain visual and / or topographic features which can be scanned (using a camera or LIDAR functionality of the mobile device 120) and extracted at the server system 110, and which can be associated with the record and / or digital record physical record identifier 150.

[0296] The physical record identifier 150p is preferably produced by a third-party entity. As such, in some examples, the method 400 can further comprise generating and sending a request to the third-party entity for producing the physical record identifier 150p, optionally including certain instructions for producing the physical record identifier 150p or 3D object representing the record identifier 150.

[0297] Figure 21 shows an example method 500 of secure transaction of an asset 130 using the abovedescribed system 100 according to an embodiment of the invention. The transaction is performed between two users who are registered with the system 100.

[0298] In step 501 , the server system 110 receives, from a mobile device 120 of a first user (a buyer), an offer to purchase a second user’s (the seller) asset 130 listed on an online marketplace (or exchange or bourse) hosted by the server system 110. Registered users can access and interact with the online marketplace (e.g. browse, list, and buy assets 130) via the software application on their mobile device 120. The asset 130 may be a physical or digital asset, and in some examples is a physical media asset 130.

[0299] Step 501 may further comprise, prior to receiving an offer for the asset from a first user, listing the second user’s asset 130 for sale on the online marketplace. This involves the second user sending a request, via the software application on their mobile device 120, to the server system 110 to list their asset 130 for sale on the online marketplace. In response to this request, the server system 110 sends a request to the mobile device 120 of the second user to authenticate the asset 130. This process of asset authentication preferably proceeds according to method 300 described above with reference to figure 16. Where the asset 130 is a physical asset 130 such as a physical media asset 130, the second user may also be asked to send images of the asset 130 to check its condition. Once the asset 130 is authenticated (and optionally its condition is checked), the server system 1 10 lists the asset 130 for sale on the online marketplace.

[0300] Step 502 comprises verifying or authenticating the identity of the first user. This preferably comprises the verification method 400 described above with reference to figure 17 (where, in this case, the requesting entity is the server system 110).

[0301] At step 503, the server system 110 sends, in response to positive verification of the first user and in response to the second user accepting the offer, an authentication request to the second user’s mobile device 120 to authenticate the asset 130. The authentication process preferably proceeds as described in method 300. The server system 110 may send a message to the mobile device 120 of the first user indicating success of failure of the authentication.

[0302] At step 504, the server system 110 initiates a transaction with the first user for the purchase of the asset 130 in response to positive authentication of the asset. This may involve the first user transferring funds to an account associated with the system 100. The server system 110 may send a message to the mobile device 120 of the second user indicating the initiation of the transaction.

[0303] At step 505, upon completion of the transaction, the server system 110 deregisters or removes the purchased asset 130 and its associated ID information from the second user’s database or their database account. The second user may be transferred the funds at this stage.

[0304] In some examples, at this point the second user (seller) preferably sends (posts) the physical asset 130 to a location or site associated with system 100 where the condition of the physical media asset 130 and its UIDs 132 are checked. The first user may then be informed of the results of the check (e.g. via message sent to their mobile device 120). In other examples, the first user is electronically sent the digital asset 130.

[0305] The first user may be asked if they want to keep the UIDs 132 on the purchased asset 130, or if they want new UIDs 132 on the purchased asset 130. This information may already be included / provided in the offer or the server system 110 may send a message to the mobile device 120 of the first user requesting this information. This request may be included in the message informing the first user of the results of the physical check, or it may be separate message. If new UIDs 132 are requested, the asset 130 with the new UIDs 132 is sent to the first user. If new UIDs 132 are not requested, the asset 130 with the existing UIDs 132 is sent to the first user. The method 500 then proceeds to either step 506a or 506b.

[0306] At step 506a, the server system 110 adds the purchased asset 130 with its associated (existing) ID information to the first user’s database or database account. Alternatively, at step 506b, the server system 1 10 adds the purchased asset 130 with ID information associated with the new UIDs 132 provided on the purchased asset 130 to the first user’s database or database account (if new UIDs were requested by the first user). At this stage, the first user becomes the new owner of the asset 130. A record of the transaction is stored in the database 112 or a distributed ledger system, as described with reference to methods 300 and 400.

[0307] Preferably, the method proceeds to step 507, whereby upon receipt of the purchased asset 130 by the first user, the first user authenticates the purchased asset 130, to check it is genuine and they have bought what they thought they bought. The authentication process preferably proceeds as described in method 300. This first authentication performed by the first user may serve to confirm completion of the transfer of ownership and transaction, and / or confirm the asset registration, by informing the server system 1 10 that the first user has received the purchased asset 130.

[0308] As described above, every interaction and transaction with the system 100 can be recorded in the database 112 or a distributed ledger system to build up a timeline / history for each user, and a history / provenance for each asset 130 that can optionally be transferred with the ownership of the asset 130. This may also be used a means of verifying a user’s identity, if e.g. the user loses their authenticator device 140, 240, 340 they can reference certain interactions and transactions recorded in their database 112 to verify their identity, and / or use their asset 130 as a means of user verification.

[0309] Figure 22(a) shows a schematic diagram of a physical media asset 130 according to an embodiment in which the storage medium 131 is a phonographic disc (referred to hereafter as a vinyl). The vinyl 131 comprises a substantially flat disc with central “run-off” area 1311 (a nonplaying area) with a centre spindle hole 1313, surrounded by a substantially annular track area 1312 (a playing area) comprising the grooves, as is known in the art. A label 134 comprising a quantum-PUF tag 132a, a surface topography tag 132b and one or more further UIDs 132d is applied to the central area 1311. Preferably, the vinyl 131 also includes an RFID and / or NFC tag 132c, either located beneath the label 134 and / or embedded within an insert 133, as described above.

[0310] Figure 22(b) shows an example label 134 comprising a quantum-PUF 132a, a surface topography tag 132b, and multiple further optically readable UIDs 132d. The label 134 comprises a central spindle hole 134o to align with the spindle hole 1313 of the vinyl 131. In addition, the diameter d2 of the label 134 is less than the diameter d1 of the central area 1311 of the vinyl 131 so as not to interfere with the playback of the media recording. In this example, the further optically readable UIDs 132d include: a set of symbols or a unique graphic (in this case a unique set or combination of custom hieroglyphs) 132d1 ; an encoded image (in this case a QR code) 132d2; a production sequence number associated with the vinyl 132d3; and a fingerprint (e.g. the user’s or owner’s fingerprint) 132d4. The label 134 also includes album information 134i.

[0311] Figure 23(a) shows an exploded cross-sectional view of the vinyl 131 of figure 22(a). As shown, the vinyl 131 comprises an insert 133 that fits into a recess 131 r in the surface of the central area 131 1 of the vinyl 131 to form a substantially flat outer surface onto which the label 134 can be applied. The insert 133 is a substantially circular or disc-shaped element with a central spindle hole 134o for aligning with the spindle hole 1313 of the vinyl 131 and the spindle hole 134o of the label 134, as shown in figure 23(b). The diameter d2 of the label 134 is greater than the diameter d3 of the recess 131 r (and corresponding insert 133) in order to cover the insert 133. A unique silk thread 138 can be positioned in the recess 131 r beneath the insert 133. With reference again to figure 23(b), the vinyl 131 may optionally further comprise an additional label 134’ on the central area of the rear side of the vinyl 131 (e.g. with corresponding album information 134i), and one or more intermediate layers 134” between the label 134 and the central area 1311. The intermediate layers 132” may serve as spacer layers. Although the insert 133 is shown as being substantially circular / disc shaped this is not essential. In other examples, the insert 133 and recess 131 r may be substantially non-circular in shape (not shown). Further, although the insert 133 is shown taking up the majority of the central area 1311 and including a spindle hole 133o, this is also not essential. In other examples, the insert 133 may instead be smaller in size and / or offset from the central spindle hole 1313 of the vinyl 131.

[0312] Figure 24 shows an example of a vinyl 131 comprising a pattern of holes or indentations provided in the central area 1311 which can serve as a further UID 132d5. The holes or indentations 132d5 can have different or congruent shapes to add further depth to the ID information encoded in the pattern.

[0313] The recess 131 r and / or the pattern of holes 132d5 can be produced during the pressing of the vinyl 131 (i.e. incorporated into the vinyl stamps), or produced after the pressing using a subtractive process (e.g. milling, laser etching, or other suitable technique). It will be appreciated that the recess 131 r should have a suitable depth not to substantially weaken or adversely affect the mechanical properties of the vinyl 131. It may, in some cases, be necessary to increase the thickness of the vinyl to accommodate the recess 131 r. The thickness of a standard vinyl record is approximately 2.2 mm. In one example, the recess 131 r can have a depth of approximately 0.6-0.7 mm and the insert 133 has a corresponding thickness. In another example, the thickness of the vinyl 131 can be increased slightly to 2.5 mm to accommodate a slightly thicker insert 133 where necessary.

[0314] Figure 25 shows an illustration of another example physical media asset 130 in the form of an audio cassette 131 with a label 134 comprising multiple UIDs 132, including a quantum-PUF 132a, a surface topography tag 132b, an RFID tag 132c (provided beneath the label 134 optionally within an insert 133 as described above), a set of symbols or a unique graphic (in this case a set or combination of custom hieroglyphs) 132d1 , an encoded image (in this case a QR code) 132d2, a production sequence number associated with the cassette 132d3, and a fingerprint (e.g. the user’s or owner’s fingerprint) 132d4. The label 134 also includes album information 134i. In this case, the non-playing area / region of the storage medium 131 is the casing part of the cassette that holds the spools of magnetic tape, as is known in the art.

[0315] Figure 26 shows an corresponding illustration of another example physical media asset 130 in the form of a compact disc (CD) 131 with a label 134 comprising multiple UIDs 132, including a quantum-PUF 132a, a surface topography tag 132b, an RFID tag 132c (provided beneath the label 134 optionally embedded within an insert 133 as described above), a set of symbols or a unique graphic (in this case a set or combination of custom hieroglyphs) 132d1 , an encoded image (in this case a QR code) 132d2, a production sequence number associated with the CD 132d3, and a fingerprint (e.g. the user’s or owner’s fingerprint) 132d4. The label 134 also includes album information 134i. In this case, the non-playing area / region of the storage medium 131 is the top / label side of the CD or the area surrounding the centre hole, as is known in the art. Other example physical media assets 130 according to the invention include a DVD, Blu Ray disc and video cassette (not shown).

[0316] Although not shown in figures 22 to 26, each of the example physical media assets 130 can include packaging 136, which can optionally include machine readable identifiers linked to the physical media asset 130 in the database 112.

[0317] Although the system 100 has been described as authenticating a asset 130, such as physical media asset, vinyl, cassette, CDs etc, it will be appreciated that the principles described above can be applied to any form of physical asset 130 that has value and / or is collectable and requires authentication from time to time. For example, the invention can be applied to physical assets 130 including but not limited to: physical artwork, memorabilia (e.g. music, film, or entertainment memorabilia), merchandise, and physical documents such as a deed, contract, agreement, pledge, certificate, or accreditation. Such a physical asset can be provided with one or more machine- readable UIDs to integrate and be used with the system 100 and methods 300, 400, 500 in the same way as described above for physical media assets 130. Preferably, a physical asset is provided with a plurality of machine-readable UIDs including at least a quantum-PUF 132a and a surface topography tag 132c, and may further include at least one (any combination) from the following list: a symbol sequence or alphanumeric code; a unique graphic or image; an encoded image, preferably a QR code; a radio frequency identification (RFID) tag; a fingerprint; and a pattern of holes or indentations (with different or congruent shapes).

[0318] In another example, it will be appreciated that system 100 and the principles of the invention can be applied to the fields of financial transactions and secure online user verification, whereby an external entity may send an authentication request to the server system 110 to verify the identity of a user for the purposes of a financial transaction or user account set-up or sign in. Where the user is registered with the server system 110 and has a registered authenticator device 140, 240, the method 400 described above reference to figure 10 is directly applicable and can be used as part of a multi-factor verification process.

[0319] In yet another example, the system 100 and the principles of the invention can be applied to managing and tracking transactions between entities to streamline collaborations and create a secure and reliable audit trail. In this case, a transaction is any interaction or exchange between two entities. For example, a first and second entity may be individually registered with the system 100, whereby certain authorised individuals associated with the respective first and second entities (e.g. users / employees / managers) are issued with an authenticator device 140, 240 registered with / linked to the respective entity’s database account. The first and second entity may enter into an agreement to undertake a joint venture, partnership, collaboration or generally to do business together. This may be established by a contract or other agreement signed by the respective authorised individuals of the first and second entities. Preferably, the agreement is in the form of a physical document (physical asset) provided with one or more UIDs 132 linked to both the entity’s accounts with the system 100, such that the document can be authenticated using the authentication method 300 described above. Preferably, each entity can be further associated with a third / joint account relating to the specific joint venture / collaboration. For each transaction between the first and second entities, (e.g. an authorised person authorising an action, event or process) the authorising person’s identity can be verified using the method 400, and the details of the transaction (e.g. details of the authorising person, the action or event being authorised, time and date, etc.) can be automatically recorded in the database 112 linked with the third / joint account, to create an audit trail indicating who authorised what and when. In addition, any products (physical assets) owned by the respective entities and involved in the joint venture can be provided with one or more UIDs 132 and registered with the respective entity’s database account, allowing any transport, exchange or change of ownership of the products to be tracked and traced using the system 100. Product track and trace can also be recorded in the database 112 linked with the third / joint account.

[0320] Figure 27 shows an example method 600 of secure sign in to a user account using the abovedescribed system 100 according to an embodiment of the invention. The sign in is performed by a user who is registered with the system 100 as part of a multi-factor sign / verification process, and the user account may be hosted or associated with a third-party server system or service who is linked with the system 100. Example third-party server systems include but are not limited to: electronic messaging systems, video messaging systems, video conferencing systems, banking systems, online marketplaces.

[0321] Step 601 comprises sending, from a user mobile device, a request to a third-party server system to sign in to a user account hosted by the third-party server system using the system 100. The request may be sent via the server system 110. In some examples, the third-party account to sign in to can be selected from a software application running on the user’s mobile device 120 which establishes a secure connection to the server system 110 and implements the various methods described herein. In other examples, the third-party account can be selected from a web-based application running on the user’s mobile device 120 associated with the third-party system. The request may be generated in response to selection of the third-party account.

[0322] Step 602 comprises receiving, at the user mobile device 120 from the server system 110 and in response to the server system 110 receiving an authentication request from the third-party server system to authenticate a user’s identity, an ID request for ID information from one or more machine-readable UIDs 142, 1421 -1425 on the user’s authenticator device 140, 240, 340.

[0323] Step 603 comprises scanning, using the user mobile device 120, each requested machine-readable UID 142, 1421-1425 on the user’s authenticator device 140, 240, 340. Step 604 comprises sending, from the user mobile device 120 to the server system 110, scan data comprising the ID information from each requested unique identifier 142, 1421 -1425 on the user’s authenticator device. Finally, step 605 comprises accessing the user account hosted by the third-party server system in response to a positive authentication of the user’s identity by the server system 110 based on the ID information. This verification process may include any of the features of method 400. The sign in process 600 can thus be used to achieve sign in with no username, or password. Preferably, the sign in request and associated information is to be recorded to the user timeline as described above with methods 300 and 400 (stored on the user database of the server system 110 or a distributed ledger system)

[0324] In preferred embodiments, the ID request comprises a request for ID information from a selection of one or more machine-readable UIDs 142, 1421 -1425 on the user’s authenticator device 140, 240, 340 required to satisfy a security level as described above in methods 300 and 400, wherein the security level is determined by the server system 110 based, at least in part, on a required security level indicated by the third-party entity server system in the authentication request and / or one or more predefined criteria associated with the third-party server system.

[0325] In preferred embodiments, the sign in method 600 further comprises, prior to step 605, a second scan / re-scan stage indicated by arrow 606 where steps 602 to 604 are repeated for a further ID request, as described above in relation to stage 405 of method 400, e.g. if a confidence level in the results from the ID request is below a threshold confidence level, and / or if required to satisfy a security level based, at least in part, on a required security level indicated by the third-party entity server system in the authentication request and / or one or more predefined criteria associated with the third-party server system, or if requested by any other party involved in the process at any stage of the process.

[0326] As described, above, the further ID request may request ID information from: one or more different machine-readable unique identifiers on the user’s authenticator device; ID information from any UID with an adjustable feature, such as the dynamic or multi-state UIDs 1421 -1425, after performing a user interaction with the UID that changes the UID; and / or biometric ID information from a scan of one or more of the user’s digits holding the user authenticator device 140, 240, 340.

[0327] In some examples, once a user has signed into the user account, the method 600 may include a further a user verification stage or ID challenge step, indicated by arrow 607, where steps 602 to 604 are repeated for a further ID request. This may be implemented randomly or periodically in response to a request from the third-party entity (e.g. via a request from another user of the third- party system who may or may not be registered with the system 100), while the user is signed in as an enhanced security feature to check that the user who is using the third-party system is still the same user who signed in. If the verification process performed at the server system 110 using the new scan data fails (e.g. because the registered user who was present at sign in is no longer present), the unverified and potentially unauthorised user can then be logged out of the user account. Figure 28 shows an example method 700 of secure transaction using the above-described system 100 according to an embodiment of the invention. The transaction is performed between two entities, at least one of which may be registered user of the system 100. It will be appreciated that ‘transaction’ is not limited to financial transactions, and may include any type of transaction between two entities which requires user verification prior to initiation or completion of the transaction.

[0328] Step 701 comprises receiving, at the server system 110, a request for transaction between a first entity and a second entity.

[0329] Step 702 comprises authenticating the identity of a first user representing the first entity according to the method 400 described above. Step 703 comprises initiating or authorising the transaction based at least in part on a positive authentication of the identity of at least the first user. Various transactions may require authenticating the identity of both the first and second entities or parties involved. As such, in various embodiments, step 702 further includes authenticating a second user representing the second entity according to the method 400, and step 703 comprises initiating or authorising the transaction based at least in part on a positive authentication of both the first user and the second user. Additional entities may also be involved in the transaction as required, e.g. as observers or witnesses, and these can be verified in the same way. The authenticating step 702 can include any or all of the features described with reference to method 400. In various examples, entities / parties whose identities have been verified are deemed to have ‘observer’ status throughout the remaining transaction.

[0330] Step 704 comprises storing, in the user database at the server system 110 or a distributed ledger system, a record of the transaction. The record of the transaction preferably includes one or more of: information associated with the transaction (e.g. items involved, type of transaction, value etc.), information associated with the first and second entities, a time of the transaction, a location of the user’s mobile device(s), and information associated with the user authentication steps (such as the user interactions, requested and received ID information as well as certain scan data), as described above with reference to methods 300 and 400.

[0331] Step 705 comprises associating a unique machine-readable identifier (the record identifier 150 described above with reference to method 400) with the record of the transaction, wherein the record identifier 150 contains or encodes ID information linked with the record of the transaction for individuating the transaction, and wherein information associated with the record is retrievable or accessible, from the server system 110, in response to receiving a request containing the ID information linked with the record, as described previously. The associating step 705 can include any or all of the features described with reference to method 400.

[0332] As described above, the record identifier 150 can be associated with a corresponding machine- readable physical record identifier 150p that can take various forms, and serves as a physical and / or digital machine-readable and scannable receipt of the transaction process completed using the server system 1 10. For example, the record identifier 150 can be used as proof of transaction, ownership, agreed terms of the transaction or an agreement, or completion of work, status of work, or status of any other process or task.

[0333] In preferred embodiments, the authentication step 702 comprises sending, by the server system 110, an ID request to the first user’s mobile device for ID information from a selection of one or more machine-readable unique identifiers on the first user’s authenticator device required to satisfy a transaction security level. The transaction security level is determined at the server system 110 based, at least in part, on a required security level indicated by the second entity in the transaction request and / or one or more predefined criteria associated with information in the transaction request such as a minimum security level for the transaction (e.g. based on the transaction context, including the type of transaction, transaction value, the entities involved, etc.). In this way, there may always be a minimum transaction security level for a transaction, set by the server system 110, which can be adjusted by the other party entity involved in the transaction.

[0334] Where the second user is being authenticated, the authentication step 702 similarly comprises sending, by the server system 110, an ID request to the second user’s mobile device for ID information from a selection of one or more machine-readable unique identifiers on the second user’s authenticator device required to satisfy a transaction security level. In this case, the transaction security level can be determined at the server system 110 based, at least in part, on a required security level indicated by the first entity in the transaction request and / or one or more predefined criteria associated with information in the transaction request such as a minimum security level for the transaction (e.g. based on the transaction context, including the type of transaction, transaction value, the entities involved, etc.). As such, the transaction security level for the first and second entities may be the same or different. In practice, the entities may need to agree on their respective security levels before the transaction request is received in step 701.

[0335] Where the first and / or second user’s authenticator device 140, 240, 340 comprises a multi-state UID 1421 -1425, preferably the ID request in the verification process 400, 702 includes a request for ID information from the multi-state UID 1421 -1425 after performing a user interaction with the multistate UID that causes a change in the static state of the multi-state UID for individuating the transaction, as described above with reference to method 400. In this case, the record includes at least part of the ID information extracted from the multi-state UIDs for individuating the transaction.

[0336] In various embodiments, the transaction process 700 includes a ID challenge step as indicated by arrow 706 wherein a further ID request is sent if a confidence level in the received / extracted ID information of the previous ID request in step 702 is below a threshold confidence level, and / or if required to satisfy a transaction security level, as described previously with reference to method 400, or if requested by any other party involved in the process at any stage of the process (preferably a party who has obtained observer status).

[0337] Where the transaction relates to a physical item or asset, the method 700 may further comprise producing a physical record identifier 150p, or instructions for producing a physical record identifier 150p, preferably based on the associated record identifier 150, for attaching to or marking the physical item.

[0338] Although the methods, devices and systems have been described herein in the context of specific applications, it will be appreciated that the disclosed methods, devices and systems have a myriad of use cases where user and / or asset authentication is required, including but not limited to: Oil; Mining; Gas; Maritime; Aviation; Military; Justice; Social Security; Healthcare; Prescriptions; Medical Records; Medical Testing; Accreditation; Signature, Agreements, Contracts, Membership; Ticketing; Ingress I Egress; Sign in online; Sign in offline; proof of work; proof of process; Streaming; Downloads; Validation of Age; Banking, Crypto transactions; Crypto assets; Sign out I resignation; Provenance of Origin of unprocessed and processed goods; Keyless start up and shut down; termination; Voting; Lending; Payments; loans; mortgaging; Marking; Romantic Dating; Insurance; remembrance; indemnification; Payments; Rewards; Loyalty Schemes; Fan Engagement; ownership of Copyrights; Licensing; Proof of origin; Proof of components history; Modern Day Slavery; People Trafficking; Friendship and support; Gaming; Gambling; Educational achievement; Merchandise; Proof of history; Board Meeting votes; attendance; disappearance; criminal records; border control; taxation; Capital Gains and losses; Sporting events; status and state, and Statistics.

[0339] From reading the present disclosure, other variations and modifications will be apparent to the skilled person. Such variations and modifications may involve equivalent and other features which are already known in the art, and which may be used instead of, or in addition to, features already described herein.

[0340] Although the appended claims are directed to particular combinations of features, it should be understood that the scope of the disclosure of the present invention also includes any novel feature or any novel combination of features disclosed herein either explicitly or implicitly or any generalisation thereof, whether or not it relates to the same invention as presently claimed in any claim and whether or not it mitigates any or all of the same technical problems as does the present invention.

[0341] Features which are described in the context of separate embodiments may also be provided in combination in a single embodiment. Conversely, various features which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable subcombination. Features of the various methods may be applied to the corresponding systems, and vice versa.

[0342] For the sake of completeness it is also stated that the term "comprising" does not exclude other elements or steps, the term "a" or "an" does not exclude a plurality, and any reference signs in the claims shall not be construed as limiting the scope of the claims.

Claims

CLAIMS1. A user authenticator device for use in authenticating a user’s identity, comprising: a plurality of different machine-readable unique identifiers provided on or in the device, each containing or encoding different ID information for identifying the authenticator device.

2. The device of claim 1 , wherein the device comprises at least four or at least six different unique identifiers.

3. The device of claim 1 or 2, comprising a main body with one or more internal compartments for housing one or more of the plurality of machine-readable unique identifiers.

4. The device of claim 3, wherein the main body comprises a window through which one or more of the machine-readable unique identifiers housed within the internal compartments are readable by a reader device; and optionally or preferably, wherein the window comprises an optically transparent material and / or a cover moveable between an open position in which the window is substantially open and a closed position in which the window is substantially closed.

5. The device of claim 4, wherein at least one of the one or more of the machine-readable unique identifiers housed within the internal compartments includes an optical element comprising portions of different optical properties arranged to form a first optical identifier readable through the window; and optionally or preferably, wherein the device comprises an internally mounted light emitting device to illuminate the first optical element.6 The device of claim 4 or 5, comprising an adjustable occluder arranged and configured to occlude a portion of the one or more of the machine-readable unique identifiers located behind the window in dependence on a position of the occluder relative to the window; and optionally or preferably, wherein the occluder is rotatable relative to the window.

7. The device of any of claims 3 to 6, wherein at least some of the one or more internal compartments are configured to receive and store one or more drawers, and wherein at least some of the one or more of the machine-readable unique identifiers of the authenticator device are provided on or in the drawers.

8. The device of claim 7 wherein the one or more drawers are moveable between an open position in which the respective unique identifiers provided therein are located outside of the main body and readable by a reader device, and a closed position in which the unique identifiers are located inside the main body; and optionally or preferably, wherein the one or more drawers are received through one or more respective openings in the main body and are configured to close, and optionally seal, the one or more respective openings when in the closed position.

9. The device of claim 7 or 8, wherein each drawer comprises a carrier portion on which at least one of the one or more unique identifiers is provided, wherein each carrier portion is configured to rotate relative to the respective drawer so as to adjust the orientation of the unique identifier relative to the respective drawer; and optionally or preferably, wherein each carrier portion comprise respective sets of markings to visually identify the relative orientation.

10. The device of any preceding claim, wherein the plurality of machine-readable unique identifiers include one or more machine-readable multi-state identifiers configured to provide unique ID information in a static state when read that is changeable in response to a user interaction with the device that causes a change in the static state; and optionally or preferably, wherein the multi-state identifiers comprise one or more adjustable, moveable and / or mobile elements that form at least part of a unique optical identifier in a static state, and provide or produce a change in the unique optical identifier in response to a user interaction with the multistate identifier that changes the static state of the adjustable, moveable and / or mobile elements.11 . The device of claim 10, wherein the one or more machine-readable multi-state identifiers include an optical device, comprising: a first optical element housed within an internal compartment of the device behind a window of the device, the first optical element comprising portions of different optical properties arranged to form a first optical identifier, and wherein at least a portion of the first optical element is substantially transparent; a second optical element arranged within the internal compartment behind the first optical element, the second optical element including portions of different optical properties arranged to form a second optical identifier such that first and second optical identifiers superimpose to form a unique optical identifier that is readable through the window, and wherein the position of at least one of the first and second optical elements is adjustable, preferably in predefined increments, relative to the other so as to change the static state of the unique optical identifier in dependence on a relative position of the first and second optical elements; and optionally or preferably, wherein the at least one of the first and second optical elements is rotatable relative to the other; and / or wherein the device further comprises an adjustable occluder arranged and configured to occlude part of the unique optical identifier in dependence on a position of the occluder relative to the window so as to further change the static state of the unique optical identifier; and optionally or preferably, wherein the occluder is rotatable relative to the window; further and optionally or preferably, wherein the device comprises an internally mounted light emitting device to illuminate the first and second optical element.

12. The device of claim 10, wherein the one or more machine-readable multi-state identifiers include a fluid device, comprising: an enclosure with a deformable wall, the enclosure containing a mixture of immiscible fluids including at least one liquid, and optionally a plurality of solid particles, wherein the mixture isconfigured to form, in a static state, a unique optical identifier readable through a transparent wall of the enclosure, and wherein the unique optical identifier is changeable in response to a force applied to the enclosure that deforms the deformable wall and causes a change in the static state of the immiscible fluids, and optionally the particles, contained therein.

13. The device of claim 12, wherein the mixture includes one or more of: a gas; at least two different coloured immiscible liquids; and at least some particles with different properties including one or more of: size, shape, colour, and other externally visible feature such as a surface pattern.

14. The device of claim 10, wherein the one or more machine-readable multi-state identifiers include a shaker device comprising: a hollow enclosure containing therein a plurality of solid particles configured to form, in a static state, a unique optical identifier readable through a transparent wall of the enclosure, and wherein the unique optical identifier is changeable in response to a force applied to the device which causes a change in the static state of the particles within the hollow enclosure.

15. The device of claim 14, wherein the plurality of particles include at least some particles with different properties including one or more of: size, shape, colour, and other externally visible feature such as a surface pattern; and / or wherein the hollow enclosure includes a static background optical pattern to visually identify the relative positions of the particles; and / or wherein the hollow enclosure includes one or more interior portions for receiving and occluding one or more particles.

16. The device of claim 14 or 15, wherein the hollow enclosure comprises a substantially transparent hollow rolling element held by one or more retaining elements such that a portion of the rolling element is externally accessible for reading and receiving a user interaction that rotates the rolling element to thereby cause a change in the static state of the particles contained therein.

17. The device of claim 10, wherein the one or more machine-readable multi-state identifiers include a roller device, comprising: one or more rolling elements held by one or more retaining elements such that a portion of each rolling element is externally accessible for receiving a user interaction, wherein each rolling element comprises a spatially non-uniform visual feature such that the externally accessible portions of the one or more rolling elements collectively form, in a static state, a unique optical identifier readable by a reader device, and wherein the optical identifier is changeable in response to user interaction that causes a change in a rotational position of at least one of the one or more rolling elements; and optionally or preferably, wherein the spatially non-uniform visual feature of one or more rolling elements comprises an exterior surface feature and / or an interior feature, preferably one or more encapsulated or enclosed internal layers, objects or particles.

18. The device of claim 10, wherein the one or more machine-readable multi-state identifiers includes a deformable topographic surface of the device, comprising:deformable projections or fibres configured to form, in a static state, a unique topographic and / or optical identifier readable by a reader device, and wherein the unique topographic and / or optical identifier is changeable in response to a user interaction with the deformable topographic surface that deforms at least some of the deformable projections or fibres and causes a change in the static state thereof.

19. The device of any preceding claim, wherein the plurality of machine-readable unique identifiers includes a dynamic machine-readable identifier configured with one or more driven movable elements that interact / combine to provide ID information and / or a unique optical identifier that continuously changes with time.

20. The device of claim 19, wherein the dynamic machine-readable identifier is a clock device, comprising: a first set of machine-readable hands driven by a motor assembly and configured to move in a first direction according to a first movement from a first start time; a second set of machine-readable hands driven by the motor assembly configured to move in a second direction according to a second movement from a second start time that is different to the first start time; and preferably one or more occluders configured to occlude at least a part of the first and / or second sets of hands in dependence on a position of the first and / or second sets of hands with respective to the one or more occluders; and wherein the first and second sets of machine-readable hands and preferably the one or more occluders collectively form a unique optical identifier readable by a reader device.

21. The device of claim 20, wherein the first and / or second sets of machine-readable hands comprise a machine-readable shape and / or one or more optical features; and / or wherein the clock device further comprises a compass which forms part of the unique optical identifier.

22. The device of claim 20 or 21 , wherein each of the one or more occluders occlude a respective area of the clock, and at least one of the one or more occluders is adjustable so as to vary the respective occluded area; and / or wherein the at least one of the one or more occluders is adjustable in size so as to vary a spatial extent of occluded area.

23. The device of any of claims 20 to 22, wherein at least one of the one or more occluders is driven by the motor assembly and configured to move around the clock in a third direction according to a third movement; and optionally or preferably, wherein the third movement includes a fixed or time-dependent speed.24 The device of any of claims 20 to 23, wherein the first and second movements include a fixed or time-dependent rotary speed; and / or wherein the motor assembly comprises one or more drive shafts and / or one or more motors.

25. The device of any of claims 10 to 24, wherein the identifier further comprises a rotatable ring or dial extending around the identifier, the rotatable ring comprising one or more markings that form part of the unique optical identifier; and optionally or preferably, wherein the markings comprise at least partially transparent portions of the rotatable ring and the device comprises an internally mounted light emitting device to illuminate a given one of the markings in dependence of the position of the rotatable ring with respect to the light emitting device.

26. The device of any preceding claim, wherein the plurality of machine-readable unique identifiers include at least one of: a physical unclonable function (PUF) tag, preferably a nanoparticle or quantum dot-based PUF tag; and a surface topography-based tag, optionally or preferably a textured surface of the device; a radio frequency identification (RFID) tag; near-field communication (NFC) tag; an encoded image, preferably a QR code; a symbol sequence or alphanumeric code; a unique graphic or image; a fingerprint; and a pattern of holes or indentations, optionally or preferably, wherein the holes or indentations have different or congruent shapes.

27. The device of any of claims 1 to 18, wherein the authenticator device is a passive device without a power source.

28. The device of any of claims 1 to 26, wherein the authenticator device is an active device comprising: a power source, an output device, one or more inputs, and a processor, wherein the processor is configured to generate, in response to a user input via the one or more inputs, additional ID information for identifying the authenticator device based, at least in part, on ID information from one or more of the machine-readable unique identifiers on the authenticator device, wherein the additional ID information comprises a unique image, preferably a dynamic image, or audio signal for outputting by the output device; and optionally or preferably, wherein the authenticator device does not comprise a wireless communication module.

29. The device of any of claims 1 to 26 or 28, further comprising a hardware crypto wallet module configured to securely store and provide access to a user’s cryptographic asset data, and wherein the authenticator device does not comprise a wireless communication module.

30. A method of authenticating a user identity using the user authenticator device of any of claims 1 to 29, comprising: receiving, at a server system configured to communicate with a user mobile device over a network and containing a user database storing ID information associated with unique identifiers oneach user’s registered authenticator device, an authentication request to authenticate a user’s identity; sending, by the server system, an ID request to the user mobile device for ID information from one or more machine-readable unique identifiers on the user’s authenticator device; receiving, at the server system, scan data from the user mobile device comprising the ID information from each requested unique identifier on the user’s authenticator device; comparing, at the server system, the received ID information with stored ID information associated with the unique identifiers on the user’s registered authenticator device; and authenticating the user’s identity if the received ID information matches the stored ID information.31 . The method of claim 30, wherein the ID request comprises: a request for ID information from a particular selection of one or more of the unique identifiers, optionally wherein the selection is generated randomly, or based on one or more predefined criteria, or specified by an authentication requesting entity or party; or a request for ID information from each of the plurality of unique identifiers on the user authenticator device.

32. The method of claim 30 or 31 , further comprising: processing, at the server system, the received scan data to extract or determine the ID information.

33. The method of claim 30, 31 or 32, further comprising: reading, by the mobile device in response to the ID request, the requested one or more unique identifiers on the user authenticator device, and sending, by the user mobile device, scan data comprising the ID information to the server system, wherein the scan data is not stored on the mobile device thereafter.

34. The method of any of claims 31 to 33, wherein the ID request comprises a request for reading biometric ID information from one or more of the user’s digits, preferably a nail side of the one or more digits, wherein the scan data includes image or video data of the one or more user’s digits holding the user authentication device, and wherein the step of comparing comprises performing a finger recognition process; optionally or preferably involving: processing the image or video data to extract biometric ID information comprising one or more biometric features associated with one or more of the user’s digits, preferably wherein the biometric features include one or more of: a digit dimension, a digit geometry, a digit position, a grip, a nail feature, a skin feature, an anatomical feature, and a worn object; and comparing the extracted one or more biometric features with stored biometric features associated with the user’s digits to determine a similarity metric, preferably using a machine learning model, and further optionally, wherein the authenticating step includes authenticating the user’s identity if the similarity metric meets a threshold similarity metric indicative of a match.

35. The method of any of claims 30 to 34, further comprising:sending, by the server system, a further ID request to the user mobile device for further ID information, wherein the further ID information comprise one or more of:ID information from one or more different machine-readable unique identifiers on the user’s authenticator device;ID information from a multi-state unique identifier of the authenticator device after performing a user interaction with the multi-state unique identifier that causes a change in the state of the multi-state unique identifier; and / or biometric ID information from one or more of the user’s digits; receiving, at the server system, scan data from the mobile device comprising the further ID information from each requested unique identifier on the user’s authenticator device; comparing, at the server system, the received further ID information with stored ID information associated with the unique identifiers on the user’s registered authenticator device; and authenticating the user’s identity if the received further ID information matches the stored ID information; and optionally or preferably, wherein the further ID request is sent if a determined confidence level in the ID information obtained from the ID request is below a threshold confidence level, wherein the confidence level is determined based, at least in part, on the comparison of the ID information to stored ID information; and / or wherein the further ID request is sent if specified by an authentication requesting entity or party.

36. The method of any of claims 30 to 35, further comprising storing, in the user database at the server system or a distributed ledger system, a record of the user authentication request including one or more of: a time of the authentication request, a location of the user mobile device, a result of the authentication request, the unique identifiers scanned, information associated with authentication request, and information associated with the authentication requesting entity or party.37 The method of claim 36, comprising: associating a unique machine-readable optical identifier with the record of the user authentication request, wherein the unique machine-readable optical identifier contains ID information linked with the record of the user authentication request; and optionally or preferably wherein information associated with the record is retrievable or accessible, from the server system, in response to receiving a request containing the ID information linked with the record.

38. The method of claim 37, wherein the step of associating comprises: generating the unique machine-readable optical identifier for the record of the user authentication request, preferably based at least in part on the received ID information from the requested machine-readable unique identifiers of the user authenticator device and / or information in or associated with the record; and storing, at the server system, the unique machine-readable optical identifier for the record and / or its ID information in association with the record in the user database; or receiving, at the server system, a unique machine-readable optical identifier from the user mobile device; and storing, at the server system, the unique machine-readable optical identifier for the record and / or its ID information in association with the record in the user database.

39. The method of any of claim 30 to 38, wherein the user authenticator device comprises a multi-state identifier as defined in any of claims 10 to 18, and the ID request comprises a request for ID information from the multi-state unique identifier after performing a user interaction with the multi-state unique identifier that causes a change in the static state of the multi-state unique identifier, and the method comprises: processing the received scan data to extract ID information from the multi-state unique identifier; comparing the extracted ID information read from multi-state unique identifier to corresponding expected ID information generated at the server system using stored ID information associated with the multi-state unique identifier on the user’s registered authenticator device; and wherein the authenticating step includes authenticating the user’s identity if at least a first part of the extracted ID information matches the expected ID information, and optionally if a second part of the received ID information does not match the any ID information stored in the user database.

40. The method of any of claims 30 to 39, wherein the user authenticator device comprises a dynamic identifier as defined in any of claims 19 to 24, and the ID request comprises a request for ID information from the dynamic unique identifier, and the method comprises: processing the received scan data to extract ID information from the dynamic unique identifier; comparing the extracted ID information read from dynamic unique identifier to corresponding expected ID information generated at the server system using stored ID information associated with the dynamic unique identifier on the user’s registered authenticator device; and wherein the authenticating step includes authenticating the user’s identity if at least the extracted ID information matches the expected ID information, and optionally wherein the dynamic identifier is the clock device of any of claims 20 to 24, and wherein the stored ID information associated with the clock device on the user’s registered authenticator device includes the first and second start times.

41. The method of claim 39, wherein the multi-state identifier is the fluid device of claim 12 or 13, and wherein the stored ID information associated with the fluid device on the user’s registered authenticator device includes properties of the immiscible fluids and optionally the particles, such as one or more of a colour and volume of the immiscible fluids, and one or more of a size, size distribution, shape, colour and / or other externally visible feature, number of the particles.

42. The method of claim 39, wherein the multi-state identifier is the shaker device of claim 14, 15 or 16, wherein the stored ID information associated with the shaker device on the user’s registered authenticator device includes properties of the particles, such as one or more of: a size, size distribution, shape, colour and / or other externally visible feature such as a pattern, and number, and optionally a static background optical pattern of the enclosure.

43. The method of claim 39, wherein the multi-state identifier is the roller device of claim 17, and wherein the stored ID information associated with the roller device on the user’s registered authenticator device includes the spatially non-uniform visual feature on each rolling element, and optionally one or more geometric features of the rolling elements.

44. The method of claim 39, wherein the multi-state identifier is the deformable topographic surface of claim 20, and wherein the stored ID information associated with the deformable topographic surface on the user’s registered authenticator device includes the one or more topographic or visual features of the topographic surface.

45. The method of any of claims 30 to 44, wherein the user authenticator device comprises one or more drawers, each drawer comprising a carrier portion on which at least one of the one or more unique identifiers is provided, wherein each carrier portion is configured to rotate relative to the respective drawer so as to adjust the orientation of the unique identifier relative to the respective drawer; wherein the ID request comprises a request for reading at least one of the machine- readable unique identifiers on the user authenticator device provided in the one or more drawers when in a particular respective orientation, and wherein the received scan data comprises the relative orientation of each requested unique identifier, and wherein the method comprises: comparing, for each requested unique identifier provided in the one or more drawers, the received relative orientation to an expected relative orientation; and wherein authenticating comprises authenticating the user’s identity if the received ID information matches the stored ID information, and if the received relative orientations match the expected relative orientations.

46. The method of any of claims 30 to 45, wherein the user authenticator device is an active device comprising: a power source, an output device, one or more inputs, and a processor for controlling the display, wherein the processor is configured to generate, in response to a user input via the one or more inputs, additional ID information for identifying the user authenticator device based, at least in part, on ID information from the one or more of the machine-readable unique identifiers on the authenticator device, the additional ID information comprising a unique image, preferably a dynamic image, or audio signal for outputting by the output device; wherein the method further comprises: sending, in response to the authentication request, an ID request to the mobile device for reading additional ID information from the user authenticator device; receiving scan data from the mobile device comprising the additional ID information; comparing the received additional ID information to corresponding additional ID information generated at the server system using stored ID information associated with the unique identifiers on the user’s authenticator device; and authenticating the user’s identity if the received additional ID information matches the corresponding additional ID information generated by the server system; and optionallyor preferably, wherein the user authenticator device does not comprise a wireless communication module.

47. A system for authenticating a user’s identity, comprising: a user authenticator device as defined in any of claims 1 to 29; and a server system comprising a user database storing ID information associated with the unique identifiers on a user’s registered authenticator device, wherein the server system is configured to communicate with a user mobile device via a network, and wherein the server system is configured to perform the method of any of claims 30 to 46.

48. A method of authenticating an asset, comprising: receiving, at a server system in communication with one or more user mobile devices, an authentication request to authenticate an asset, wherein the asset comprises one or more machine- readable unique identifiers, each containing or encoding different ID information for identifying the asset; sending, by the server system in response to the authentication request, a first request to a user mobile device for reading one or more machine-readable unique identifiers of the asset; receiving, at the server system, scan data from the user mobile device comprising first ID information from each requested unique identifier of the asset; comparing, at the server system, the received first ID information with stored first ID information associated with the unique identifiers of the registered asset; performing the method of any of claims 30 to 46 to authenticate the user’s identity; and authenticating the asset if the received first ID information matches the stored first ID information and if the user’s identity is authenticated.

49. The method of claim 48, wherein the asset comprises a plurality of different machine- readable unique identifiers, and wherein the first request comprises: a request for reading a particular selection of one or more of the unique identifiers of the asset, optionally wherein the selection is generated randomly or based on one or more predefined criteria or specified by an authentication requesting entity or party; or a request for reading each of the plurality of unique identifiers on the asset.

50. The method of claim 48 or 49, further comprising: reading, by the user mobile device in response to the first request, the requested one or more unique identifiers of the asset, and sending scan data comprising the first ID information from each read unique identifier of the asset to the server system, wherein the scan data is not stored on the user mobile device thereafter.51 . The method of any of claims 48 to 50, further comprising: receiving, at the server system, a first geolocation of the user mobile device associated with a time of reading the requested unique identifiers of the asset, and a second geolocation of the user mobile device associated with a time of reading the requested unique identifiers of the user authenticator device;comparing, at the server system, the received first and second geolocations associated with the respective first and second ID information; and wherein authenticating the asset further comprises authenticating the asset if the first and second geolocations substantially match.

52. The method of any of claims 48 to 51 , further comprising: performing the method of any of claims 30 to 46 to authenticate the identity of a further user observing the asset authentication; and authenticating the asset if the received first ID information matches the stored first ID information and if the user’s identity and the further user’s identity is authenticated.

53. The method of any of claims 48 to 52, further comprising storing, in a user database of the server system or a distributed ledger system, a record of the authentication request including one or more of: a time of the authentication request, a location of the user(s) mobile device(s), a result of the authentication request, the unique identifiers scanned, information associated with the asset and / or authentication request, and information associated with the authenticating user(s) and / or the authentication requesting entity or party.

54. A system for authenticating an asset, comprising: a user authenticator device as defined in any of claims 1 to 29; an asset comprising one or more different machine-readable unique identifiers, each containing or encoding different ID information for identifying the asset; and a server system comprising a user database storing ID information associated with the unique identifiers of registered assets and ID information associated with the unique identifiers on one or more user’s registered authenticator devices, wherein the server system configured to communicate with one or more user mobile devices via a network; and wherein the server system is configured to perform the method of any of claims 48 to 53.

55. Use of the method of any of claims 30 to 46 or 48 to 53, or the system of claims 47 or 54 in a transaction process, or in a supply chain management process.

56. Use of the method of any of claims 30 to 46, or the system of claim 47 in a user account set-up or sign-in process.

57. A method of secure sign in to a user account, comprising: sending, from a user mobile device, a request to a third-party server system to sign in to a user account hosted by the third-party server system using the user’s authenticator device as defined in any of claims 1 to 29, receiving, at the user mobile device from an authenticating server system configured to perform the method of any of claims 30 to 46 and in response to the authenticating server system receiving an authentication request from the third-party server system to authenticate a user’s identity, an ID request for ID information from one or more machine-readable unique identifiers on the user’s authenticator device;scanning, using the user mobile device, each requested machine-readable unique identifier on the user’s authenticator device; sending, from the user mobile device to the authenticating server system, scan data comprising the ID information from each requested unique identifier on the user’s authenticator device; and accessing the user account hosted by the third-party server system in response to a positive authentication of the user’s identity by the authenticating server system based on the ID information.

58. The method of claim 57, wherein the ID request comprises a request for ID information from a selection of one or more machine-readable unique identifiers on the user’s authenticator device required to satisfy a security level, wherein the security level is determined by the authenticating server system based, at least in part, on a required security level indicated by the third-party entity server system in the authentication request and / or one or more predefined criteria associated with the third-party server system.

59. The method of claims 57 or 58, further comprising: receiving, by the user mobile device from the authenticating server system, a further ID request for further ID information, wherein the further ID information comprise one or more of:ID information from one or more different machine-readable unique identifiers on the user’s authenticator device;ID information from a multi-state unique identifier of the user’s authenticator device after performing a user interaction with the multi-state unique identifier that causes a change in the state of the multi-state unique identifier; and / or biometric ID information from a scan of one or more of the user’s digits holding the user authenticator device; scanning, using the user mobile device, each requested machine-readable unique identifier on the user’s authenticator device; sending, from the user mobile device to the authenticating server system, scan data comprising the further ID information from each requested unique identifier on the user’s authenticator device; and accessing the user account hosted by the third-party server system in response to a positive authentication of the user’s identity by the authenticating server system based on the further ID information; and optionally or preferably, wherein the further ID request is received if a confidence level in the ID request is below a threshold confidence level, the confidence level determined by the authenticating server system based, at least in part, on a comparison of the ID information to stored ID information; and / or if required to satisfy a security level, wherein the security level is determined by the authenticating server system based, at least in part, on a required security level indicated by the third-party entity server system in the authentication request and / or one or more predefined criteria associated with the third-party server system.

60. A method of secure transaction, comprising:receiving, at a server system configured to communicate with user mobile devices over a network and containing a user database storing ID information associated with unique machine- readable identifiers on each user’s registered authenticator device as defined in any of claims 1 to 29, a request for transaction between a first entity and a second entity; authenticating the identity of a first user representing the first entity according to the method of any of claims 30 to 46; initiating or authorising the transaction based at least in part on a positive authentication of at least the first user; and storing, in a user database of the server system or a distributed ledger system, a record of the transaction; and associating a unique machine-readable identifier with the record of the transaction, wherein the unique machine-readable identifier contains or encodes ID information linked with the record of the transaction for individuating the transaction; wherein information associated with the record is retrievable or accessible, from the server system, in response to receiving a request containing the ID information linked with the record.61 . The method of claim 60, wherein the step of associating comprises: generating or receiving, at the server system, the unique machine-readable optical identifier for the record of the transaction; and storing, at the server system, the unique machine-readable optical identifier for the record and / or its ID information in association with the record in the user database; and optionally or preferably, wherein the generated unique machine-readable identifier is a digital image generated based at least in part on information associated with the record, and more preferably encodes information associated with the record; and / or generating instructions for producing a physical object representing the unique machine-readable optical identifier for the record.

62. The method of claim 60 or 61 , wherein the authentication step comprises sending, by the server system, an ID request to the first user’s mobile device for ID information from a selection of one or more machine-readable unique identifiers on the first user’s authenticator device required to satisfy a transaction security level; and optionally or preferably, wherein the transaction security level is determined at the server system based, at least in part, on a required security level indicated by the second entity in the transaction request and / or one or more predefined criteria associated with information in the transaction request.

63. The method of claim 62, wherein the first user’s authenticator device comprises a multistate unique identifier as defined in any of claims 12 to 18, the ID request of the authenticating step may include a request for ID information from the multi-state unique identifier after performing a user interaction with the multi-state unique identifier that causes a change in the static state of the multi-state unique identifier for individuating the transaction; and preferably wherein the record includes at least part of the ID information from the multi-state unique identifier for individuating the transaction.

64. The method of any of claims 60 to 63, further comprising authenticating a second user representing the second entity according to the method of any of claims 30 to 46; and initiating or authorising the transaction based at least in part on a positive authentication of the first user and the second user.

65. The method of claim 64, wherein the authentication step comprises sending, by the server system, an ID request to the second user’s mobile device for ID information from a selection of one or more machine-readable unique identifiers on the second user’s authenticator device required to satisfy a transaction security level; optionally or preferably, wherein the transaction security level is determined by the server system based, at least in part, on a required security level indicated by the first entity and the second entity in the transaction request and / or one or more predefined criteria associated with information in the transaction request.

66. The method of any of claims 60 to 65, wherein the authentication step comprises sending, by the server system, a further ID request to the respective user’s mobile device for further ID information, wherein the further ID information comprise one or more of:ID information from one or more different machine-readable unique identifiers on the respective user’s authenticator device; wherein the user authenticator device comprises a multi-state unique identifier as defined in any of claims 10 to 18, ID information from the multi-state unique identifier after performing a user interaction with the multi-state unique identifier that causes a change in the state of the multi-state unique identifier; and / or biometric ID information from a scan of one or more of the user’s digits; receiving, at the server system, scan data from the mobile device comprising the further ID information from each requested unique identifier on the respective user’s authenticator device; comparing, at the server system, the received further ID information with stored ID information associated with the unique identifiers on the respective user’s registered authenticator device; and authenticating the respective user’s identity if the received further ID information matches the stored ID information; and optionally or preferably, wherein the further ID request is sent if a confidence level in the ID information of the ID request is below a threshold confidence level, the confidence level determined at the server system based, at least in part, on the comparison of the ID information to the stored ID information; and / or if required to satisfy a transaction security level.

67. The method of any of claims 60 to 66, wherein the record of the transaction includes one or more of: information associated with the transaction, information associated with the first and second entities, a time of the transaction, a location of the user’s mobile device, and information associated with the authenticating step.

68. The method of any of claims 60 to 67, wherein the transaction relates to a physical asset, and the method further comprises producing a physical unique machine-readable optical identifier,or instructions for producing a physical unique machine-readable optical identifier, preferably based on the associated unique machine-readable optical identifier for attaching to the physical asset, containing or encoding ID information linked with the record of the transaction.

69. A method of secure transaction of an asset, the asset comprising one or more different machine-readable unique identifiers, each containing different ID information for identifying the asset, the method comprising: receiving, at a server system configured to communicate with user mobile devices over a network and containing a user database storing ID information associated with unique identifiers on each user’s registered asset(s) and on each user’s registered authenticator device, an offer from a mobile device of a first user to purchase a second user’s asset listed on an online exchange or marketplace hosted by the server system; verifying the identity of the first user; sending, in response to positive verification of the first user’s identity and in response to the second user accepting the offer, an authentication request to the second user’s mobile device to authenticate the asset according to the method of any of claims 48 to 53; initiating a transaction for the purchase of the second user’s asset in response to positive authentication of the asset; and upon completion of the transaction, deregistering the purchased asset and its associated ID information from the second user’s database, and either:(i) adding the purchased asset with its associated ID information to the first user’s database account; or(ii) adding the purchased asset with ID information associated with new unique identifiers provided with or on the purchased asset to the first user’s database account.

70. The method of claim 69, further comprising, upon receipt of the purchased asset by the first user, authenticating, by the first user, the purchased asset according to the method of any of claims 48 to 53.71 . The method of claim 69 or 70, further comprising: receiving, at the server system, a request from the second user to list their asset for sale on the online exchange or marketplace; sending, by the server system, a request to a mobile device of the second user to authenticate the asset according to the method of any of claims 48 to 53; and listing the second user’s asset for sale on the online exchange or marketplace in response to a positive authentication of the asset.

72. The method of any of claims 69 to 71 , wherein verifying the identity of the first user comprises the method of any of claims 30 to 46.

73. A physical media asset, comprising: a storage medium for storing a copy of a media recording; anda plurality of machine-readable unique identifiers provided on or in a preferably non-playing area of the storage medium, wherein each unique identifier contains or encodes different information for identifying the copy from all other copies of the media recording.

74. The asset of claim 73, wherein the plurality of machine-readable unique identifiers comprise at least one of: a physical unclonable function (PUF) tag, preferably a nanoparticle or quantum dot-based PUF tag; and a surface topography-based tag, optionally or preferably a textured surface of the asset.

75. The asset of claim 73 or 74, wherein the one or more machine-readable unique identifiers include at least one of: a radio frequency identification (RFID) tag; a near field communication (NFC) tag; an encoded image, preferably a QR code; a symbol sequence or alphanumeric code; a production sequence number associated with the asset; a unique graphic or image, optionally a unique set of hieroglyphs; a fingerprint; and a pattern of holes or indentations, optionally or preferably, wherein the holes or indentations have different or congruent shapes.

76. The asset of claim 73, 74, or 75, wherein at least some of the one or more unique identifiers are: integrated with one or more labels attached to the non-playing area of the storage medium; and / or embedded within the non-playing area of the storage medium.

77. The asset of any of claims 73 to 75, wherein the one or more unique identifiers include an RFID tag or NFC tag located beneath or embedded within a label attached to the non-playing area of the storage medium.

78. The asset of any of claims 73 to 77, wherein an RFID tag or NFC tag is embedded within an insert that is located within a recess in a surface of the non-playing area of the storage medium; and optionally or preferably, wherein the dimensions of the insert substantially match the dimensions of the recess so as to provide a substantially smooth surface of the non-playing area of the storage medium to which a label is attached.

79. The asset of claim 78, wherein the insert is or comprises a multilayer structure including a first layer and a second layer, wherein the RFID tag or NFC tag is located between the first and second layers; and / orwherein the asset further comprises a preferable unique silk thread located in the recess beneath the insert.

80. The asset of any of claims 73 to 79, wherein the storage medium comprises: a phonograph record disc; an optical disc; or a cassette.

81. The method of any of claims 48 to 53, or the system of claims 54, or the method of any of claims 69 to 72, wherein the asset is a physical asset or a digital asset.

82. The method of any of claims 48 to 53, or the system of claims 54, or the method of any of claims 69 to 72, wherein the asset is a physical media asset as defined in any of claims 73 to 80.

Images