SYSTEM FOR GENERATING STACKED NON-FUNGIBLE TOKENS ON A COLLABORATIVE TECHNICAL PLATFORM

Systems, computer program products, and methods are described herein generating stacked non-fungible tokens on a collaborative technical platform. The present invention is configured to electronically receive, from a computing device of a user, a collaborative digital artifact, wherein the collaborative digital artifact comprises portions of one or more digital artifacts; retrieve one or more non-fungible tokens (NFTs) associated the one or more digital artifacts; generate a stacked NFT for the collaborative digital artifact based on at least the one or more NFTs associated with the one or more digital artifacts; and store the stacked NFT associated with the collaborative digital artifact on a distributed ledger.

FIELD OF THE INVENTION

The present invention embraces a system generating stacked non-fungible tokens on a collaborative technical platform.

BACKGROUND

A growing trend in the music industry is the rise of NFTs or non-fungible tokens. NFTs have provided artists with the option to tokenize and publish their work to monetize and profit from their music as well as other content surrounding the themes of the music and the artists public image. While each work created by the artist may be associated with an NFT, an artist may want the ability to integrate their works with the works of other artists. For instance, one artist may have composed a melody or song, and another artist may want to collaborate by using the melody or song in a video production.

There is a need for a system for generating stacked non-fungible tokens for collaborative digital artifacts created on a collaborative technical platform.

SUMMARY

In one aspect, a system for generating stacked non-fungible tokens on a collaborative technical platform is presented. The system comprising: at least one non-transitory storage device; and at least one processing device coupled to the at least one non-transitory storage device, wherein the at least one processing device is configured to: electronically receive, from a computing device of a user, a collaborative digital artifact, wherein the collaborative digital artifact comprises portions of one or more digital artifacts; retrieve one or more non-fungible tokens (NFTs) associated the one or more digital artifacts; generate a stacked NFT for the collaborative digital artifact based on at least the one or more NFTs associated with the one or more digital artifacts; and store the stacked NFT associated with the collaborative digital artifact on a distributed ledger.

In some embodiments, the at least one processing device is further configured to generate the stacked NFT, wherein generating further comprises retrieving one or more portions of the one or more digital artifacts comprising the collaborative digital artifact; determining one or more weights for the one or more digital artifacts based on at least the one or more portions; and generating the stacked NFT as a weighted combination of the NFTs associated with the one or more digital artifacts based on at least the one or more weights.

In some embodiments, the at least one processing device is further configured to provide a digital artifact collaboration platform (DACP) for installation on the computing device of the user; electronically receive, via the DACP, one or more digital artifacts from one or more third party devices; retrieve, using the DACP, the one or more portions from the one or more digital artifacts; and generate the collaborative digital artifact using the one or more portions of the one or more digital artifacts.

In some embodiments, the at least one processing device is further configured to: determine that the stacked NFT is associated with one or more resources; determine, using a smart contract associated with the distributed ledger, one or more portions of the one or more resources for the one or more NFTs associated with the one or more digital artifacts based on at least the one or more weights; and automatically initiate a resource transfer with the one or more third party devices to transfer the one or more portions of the one or more resources.

In some embodiments, the one or more resources comprises at least a market value of the stacked NFT.

In some embodiments, the one or more portions of the one or more resources comprises at least royalties, access compensation, and/or ownership equity of the market value of the stacked NFT.

In some embodiments, the at least one processing device is further configured to: electronically receive information associated with one or more resource distribution repositories associated with one or more third party devices; and transfer the one or more portions of the one or more resources to the one or more resource distribution repositories associated with the one or more third party devices.

In some embodiments, the one or more digital artifacts comprises at least static digital media and/or dynamic digital media.

In another aspect, a computer program product for generating stacked non-fungible tokens on a collaborative technical platform is presented. The computer program product comprising a non-transitory computer-readable medium comprising code causing a first apparatus to: electronically receive, from a computing device of a user, a collaborative digital artifact, wherein the collaborative digital artifact comprises portions of one or more digital artifacts; retrieve one or more non-fungible tokens (NFTs) associated the one or more digital artifacts; generate a stacked NFT for the collaborative digital artifact based on at least the one or more NFTs associated with the one or more digital artifacts; and store the stacked NFT associated with the collaborative digital artifact on a distributed ledger.

In yet another aspect, a method for generating stacked non-fungible tokens on a collaborative technical platform is presented. The method comprising: electronically receiving, from a computing device of a user, a collaborative digital artifact, wherein the collaborative digital artifact comprises portions of one or more digital artifacts; retrieving one or more non-fungible tokens (NFTs) associated the one or more digital artifacts; generating a stacked NFT for the collaborative digital artifact based on at least the one or more NFTs associated with the one or more digital artifacts; and storing the stacked NFT associated with the collaborative digital artifact on a distributed ledger.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

As described herein, a “user” may be an individual associated with an entity. As such, in some embodiments, the user may be an individual having past relationships, current relationships or potential future relationships with an entity. In some embodiments, a “user” may be an employee (e.g., an associate, a project manager, an IT specialist, a manager, an administrator, an internal operations analyst, or the like) of the entity or enterprises affiliated with the entity, capable of operating the systems described herein. In some embodiments, a “user” may be any individual, entity or system who has a relationship with the entity, such as a customer or a prospective customer. In other embodiments, a user may be a system performing one or more tasks described herein.

As used herein, an “interaction” may refer to any communication between one or more users, one or more entities or institutions, and/or one or more devices, nodes, clusters, or systems within the system environment described herein. For example, an interaction may refer to a transfer of data between devices, an accessing of stored data by one or more nodes of a computing cluster, a transmission of a requested task, or the like.

As used herein, a “resource” may generally refer to objects, products, devices, goods, commodities, services, and the like, and/or the ability and opportunity to access and use the same. Some example implementations herein contemplate a market value of a property held by a user, including property that is stored and/or maintained by a third-party entity. For purposes of this invention, a resource is typically stored in a resource repository—a storage location where one or more resources are organized, stored and retrieved electronically using a computing device.

As used herein, a “resource transfer,” “resource distribution,” or “resource allocation” may refer to any transaction, activities or communication between one or more entities, or between the user and the one or more entities. A resource transfer may refer to any distribution of resources such as, but not limited to, a payment, processing of funds, purchase of goods or services, a return of goods or services, a payment transaction, a credit transaction, or other interactions involving a user's resource or account. In the context of an entity such as a financial institution, a resource transfer may refer to one or more of: a sale of goods and/or services, a user accessing their e-wallet, or any other interaction involving the user and/or the user's device that invokes or is detectable by the financial institution. In some embodiments, the user may authorize a resource transfer using at least a payment instrument (credit cards, debit cards, checks, digital wallets, currency, loyalty points), and/or payment credentials (account numbers, payment instrument identifiers). Unless specifically limited by the context, a “resource transfer” a “transaction”, “transaction event” or “point of transaction event” may refer to any activity between a user, a merchant, an entity, or any combination thereof. In some embodiments, a resource transfer or transaction may refer to financial transactions involving direct or indirect movement of funds through traditional paper transaction processing systems (i.e. paper check processing) or through electronic transaction processing systems.

FIG.1presents an exemplary block diagram of the system environment for generating stacked non-fungible tokens on a collaborative technical platform100, in accordance with an embodiment of the invention.FIG.1provides a unique system that includes specialized servers and system communicably linked across a distributive network of nodes required to perform the functions of the process flows described herein in accordance with embodiments of the present invention.

As illustrated, the system environment100includes a network110, a system130, and a user input system140. In some embodiments, the system130, and the user input system140may be used to implement the processes described herein, in accordance with an embodiment of the present invention. In this regard, the system130and/or the user input system140may include one or more applications stored thereon that are configured to interact with one another to implement any one or more portions of the various user interfaces and/or process flow described herein.

In accordance with embodiments of the invention, the system130is intended to represent various forms of digital computers, such as laptops, desktops, video recorders, audio/video player, radio, workstations, personal digital assistants, servers, wearable devices, Internet-of-things devices, augmented reality (AR) devices, virtual reality (VR) devices, extended reality (XR) devices automated teller machine devices, electronic kiosk devices, blade servers, mainframes, or any combination of the aforementioned. In accordance with embodiments of the invention, the user input system140is intended to represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smartphones, and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed in this document.

In accordance with some embodiments, the system130may include a processor102, memory104, a storage device106, a high-speed interface108connecting to memory104, and a low-speed interface112connecting to low speed bus114and storage device106. Each of the components102,104,106,108,111, and112are interconnected using various buses, and may be mounted on a common motherboard or in other manners as appropriate. The processor102can process instructions for execution within the system130, including instructions stored in the memory104or on the storage device106to display graphical information for a GUI on an external input/output device, such as display116coupled to a high-speed interface108. In other implementations, multiple processors and/or multiple buses may be used, as appropriate, along with multiple memories and types of memory. Also, multiple systems, same or similar to system130may be connected, with each system providing portions of the necessary operations (e.g., as a server bank, a group of blade servers, or a multi-processor system). In some embodiments, the system130may be a server managed by the business. The system130may be located at the facility associated with the business or remotely from the facility associated with the business.

The memory104stores information within the system130. In one implementation, the memory104is a volatile memory unit or units, such as volatile random access memory (RAM) having a cache area for the temporary storage of information. In another implementation, the memory104is a non-volatile memory unit or units. The memory104may also be another form of computer-readable medium, such as a magnetic or optical disk, which may be embedded and/or may be removable. The non-volatile memory may additionally or alternatively include an EEPROM, flash memory, and/or the like. The memory104may store any one or more of pieces of information and data used by the system in which it resides to implement the functions of that system. In this regard, the system may dynamically utilize the volatile memory over the non-volatile memory by storing multiple pieces of information in the volatile memory, thereby reducing the load on the system and increasing the processing speed.

In some embodiments, the system130may be configured to access, via the network110, a number of other computing devices (not shown) in addition to the user input system140. In this regard, the system130may be configured to access one or more storage devices and/or one or more memory devices associated with each of the other computing devices. In this way, the system130may implement dynamic allocation and de-allocation of local memory resources among multiple computing devices in a parallel or distributed system. Given a group of computing devices and a collection of interconnected local memory devices, the fragmentation of memory resources is rendered irrelevant by configuring the system130to dynamically allocate memory based on availability of memory either locally, or in any of the other computing devices accessible via the network. In effect, it appears as though the memory is being allocated from a central pool of memory, even though the space is distributed throughout the system. This method of dynamically allocating memory provides increased flexibility when the data size changes during the lifetime of an application and allows memory reuse for better utilization of the memory resources when the data sizes are large.

The system130may be implemented in a number of different forms, as shown inFIG.1. For example, it may be implemented as a standard server, or multiple times in a group of such servers. Additionally, the system130may also be implemented as part of a rack server system or a personal computer such as a laptop computer. Alternatively, components from system130may be combined with one or more other same or similar systems and an entire system130may be made up of multiple computing devices communicating with each other.

FIG.1also illustrates a user input system140, in accordance with an embodiment of the invention. The user input system140includes a processor152, memory154, an input/output device such as a display156, a communication interface158, and a transceiver160, among other components. The user input system140may also be provided with a storage device, such as a microdrive or other device, to provide additional storage. Each of the components152,154,158, and160, are interconnected using various buses, and several of the components may be mounted on a common motherboard or in other manners as appropriate.

The processor152is configured to execute instructions within the user input system140, including instructions stored in the memory154. The processor may be implemented as a chipset of chips that include separate and multiple analog and digital processors. The processor may be configured to provide, for example, for coordination of the other components of the user input system140, such as control of user interfaces, applications run by user input system140, and wireless communication by user input system140.

The memory154stores information within the user input system140. The memory154can be implemented as one or more of a computer-readable medium or media, a volatile memory unit or units, or a non-volatile memory unit or units. Expansion memory may also be provided and connected to user input system140through an expansion interface (not shown), which may include, for example, a SIMM (Single In Line Memory Module) card interface. Such expansion memory may provide extra storage space for user input system140or may also store applications or other information therein. In some embodiments, expansion memory may include instructions to carry out or supplement the processes described above and may include secure information also. For example, expansion memory may be provided as a security module for user input system140and may be programmed with instructions that permit secure use of user input system140. In addition, secure applications may be provided via the SIMM cards, along with additional information, such as placing identifying information on the SIMM card in a non-hackable manner. In some embodiments, the user may use the applications to execute processes described with respect to the process flows described herein. Specifically, the application executes the process flows described herein.

In some embodiments, the user may use the user input system140to transmit and/or receive information or commands to and from the system130via the network110. Any communication between the system130and the user input system140(or any other computing devices) may be subject to an authentication protocol allowing the system130to maintain security by permitting only authenticated users (or processes) to access the protected resources of the system130, which may include servers, databases, applications, and/or any of the components described herein. To this end, the system130may require the user (or process) to provide authentication credentials to determine whether the user (or process) is eligible to access the protected resources. Once the authentication credentials are validated and the user (or process) is authenticated, the system130may provide the user (or process) with permissioned access to the protected resources. Similarly, the user input system140(or any other computing devices) may provide the system130with permissioned to access the protected resources of the user input system130(or any other computing devices), which may include a GPS device, an image capturing component (e.g., camera), a microphone, a speaker, and/or any of the components described herein.

The user input system140may communicate with the system130(and one or more other devices) wirelessly through communication interface158, which may include digital signal processing circuitry where necessary. Communication interface158may provide for communications under various modes or protocols, such as GSM voice calls, SMS, EMS, or MMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others. Such communication may occur, for example, through radio-frequency transceiver160. In addition, short-range communication may occur, such as using a Bluetooth, Wi-Fi, or other such transceiver (not shown). In addition, GPS (Global Positioning System) receiver module170may provide additional navigation—and location-related wireless data to user input system140, which may be used as appropriate by applications running thereon, and in some embodiments, one or more applications operating on the system130.

The user input system140may also communicate audibly using audio codec162, which may receive spoken information from a user and convert it to usable digital information. Audio codec162may likewise generate audible sound for a user, such as through a speaker, e.g., in a handset of user input system140. Such sound may include sound from voice telephone calls, may include recorded sound (e.g., voice messages, music files, etc.) and may also include sound generated by one or more applications operating on the user input system140, and in some embodiments, one or more applications operating on the system130.

The systems and techniques described here can be implemented in a technical environment that includes a back end component (e.g., as a data server), that includes a middleware component (e.g., an application server), that includes a front end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components.

As shown inFIG.1, the components of the system130and the user input system140are interconnected using the network110. The network110, which may be include one or more separate networks, be a form of digital communication network such as a telecommunication network, a local area network (“LAN”), a wide area network (“WAN”), a global area network (“GAN”), the Internet, or any combination of the foregoing. It will also be understood that the network110may be secure and/or unsecure and may also include wireless and/or wired and/or optical interconnection technology.

In accordance with an embodiments of the invention, the components of the system environment100, such as the system130and the user input system140may have a client-server relationship, where the user input system130makes a service request to the system130, the system130accepts the service request, processes the service request, and returns the requested information to the user input system140, and vice versa. This relationship of client and server typically arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

It will be understood that the embodiment of the system environment100illustrated inFIG.1is exemplary and that other embodiments may vary. As another example, in some embodiments, the system environment may include more, fewer, or different components. As another example, in some embodiments, some or all of the portions of the system environment100may be combined into a single portion. Likewise, in some embodiments, some or all of the portions of the system130may be separated into two or more distinct portions.

An artist may want the ability to integrate their works with the works of other artists. For instance, one artist may have composed a melody or song, and another artist may want to collaborate by using the melody or song in a video production. The present invention allows for different artists to be able to contribute to a stacked NFT. The stacked NFT comprises sub-components, where each of the artists owns a portion or component of the digital work. Through smart contracts, this invention allows the ability to split the value of the stacked NFT in various ways and provide a system for disbursement of royalties, access compensation, ownership equity of market value, or the like. In addition, the present invention further includes a digital artifact collaboration portal where users can collaborate.

FIG.2illustrates a process flow for generating stacked non-fungible tokens on a collaborative technical platform200, in accordance with an embodiment of the invention. As shown in block202, the process flow includes electronically receiving, from a computing device of a user, a collaborative digital artifact, wherein the collaborative digital artifact comprises portions of one or more digital artifacts. In some embodiments, the digital artifacts may refer to any content that is stored digitally. This may include static digital artifacts such as photos, images, files containing text, spreadsheets, or dynamic digital artifacts such as videos, music. Examples of digital artifacts provided herein is exemplary and those of skill in the art will recognize a digital artifact can be any content, in any format, that is stored digitally and provides value to the entity (or to the user or consumer). A collaborative digital artifact may refer to any digital content that is constructed by combination portions of various digital artifacts in some form or another. For example, a movie may be considered a collaborative digital artifact if that movie is made using an existing video, layered with existing music in the background, represented by existing digital art.

Next, as shown in block204, the process flow includes retrieving one or more non-fungible tokens (NFTs) associated the one or more digital artifacts. An NFT is a unit of data used as a unique digital identifier stored on a digital ledger that certifies ownership and authenticity of a digital artifact. NFTs cannot be copied, substituted, or subdivided. They are typically stored using distributed ledger technology. As such, NFTs are stored in a distributed ledger—a database that is consensually shared and synchronized across multiple sites, institutions, or geographies, accessible by multiple people. Distributed ledgers use independent computers (referred to as nodes) to record, share and synchronize transactions in their respective electronic ledgers (instead of keeping data centralized as in a traditional ledger).

In some embodiments, NFTs are created when a distributed ledger (e.g., blockchain) string records of cryptographic hash, a set of characters that verifies a set of data to be unique, onto previous records therefore creating a chain of identifiable data artifacts. This cryptographic transaction process ensures the authentication of each digital file by providing a digital signature that is used to track NFT ownership. In some embodiments, NFTs are stored in “smart contracts,” which are automatically executable code that run on top of the distributed ledger on which the NFT is recorded.

Next, as shown in block206, the process flow includes generating a stacked NFT for the collaborative digital artifact based on at least the one or more NFTs associated with the one or more digital artifacts. As each digital artifact is associated with an NFT, a collaborative digital artifact that uses portions of existing digital artifacts needs its own NFT to certify authenticity and ownership. Accordingly, in some embodiments, the system may be configured to retrieve one or more portions of the one or more digital artifacts comprising the collaborative digital artifact. In response, the system may be configured to determine one or more weights for the one or more digital artifacts based on at least the one or more portions. In response, the system may be configured to generate the stacked NFT as a weighted combination (e.g., weighted average) of the NFTs associated with the one or more digital artifacts based on at least the one or more weights. Generating the stacked NFT using a weighted combination of NFTs of the digital artifacts used allows for equitable assignment of rights and ownership to the collaborative digital artifact.

Next, as shown in block208, the process flow includes storing the stacked NFT associated with the collaborative digital artifact on a distributed ledger. In some embodiments, the smart contracts associated with the distributed ledger may be used to attribute ownership and certify authenticity for the collaborative digital artifact using the stacked NFT.

FIG.3illustrates a process flow for generating a collaborative digital artifact using a digital artifact collaborative platform (DACP), in accordance with an embodiment of the invention. As shown in block302, the process flow includes providing a digital artifact collaboration platform (DACP) for installation on the computing device of the user.

Next, as shown in block304, the process flow includes electronically receiving, via the DACP, one or more digital artifacts from one or more third party devices. In response to receiving the digital artifacts, the system may be configured to ensure that each digital artifact is associated with an NFT. Once received, these digital artifacts are stored in a proprietary database associated with the DACP. The user may then access the proprietary database to retrieve the digital artifacts when creating the collaborative digital artifact using the DACP.

Next, as shown in block306, the process flow includes retrieving, using the DACP, the one or more portions from the one or more digital artifacts. Typically, when creating a collaborative piece, the entirety of the digital artifact may always not be used. A user may use snippets or portions of a digital artifact and combine that portion with portions of other digital artifacts to design and create a collaborative digital artifact. In some embodiments, the user may combine these portions with original contributions to create the collaborative digital artifact.

Next, as shown in block308, the process flow includes generating the collaborative digital artifact using the one or more portions of the one or more digital artifacts. In response to generating the collaborative digital artifact, the system may be configured to automatically generate the stacked NFT, as described herein. In some embodiments, the system may be configured to determine that the stacked NFT may be associated with one or more resources indicating a market value of the collaborative digital artifact and/or its associated stacked NFT. In response, the system may be configured to determine, using the smart contract associated with the distributed ledger, one or more portions of the one or more resources for the one or more NFTs associated with the one or more digital artifacts based on at least the one or more weights. In some embodiments, the one or more portions of the one or more resources may include at least royalties, access compensation, and/or ownership equity of the market value of the stacked NFT. In response, the system may be configured to automatically initiate a resource transfer with the one or more third party devices to transfer the one or more portions of the one or more resources. In some embodiments, the system may be configured to electronically receive information associated with one or more resource distribution repositories associated with one or more third party devices. In response, the system may be configured to transfer the one or more portions of the one or more resources to the one or more resource distribution repositories associated with the one or more third party devices.