Computing technologies for musical performances

1. A method, using a server in communications with a sponsor client, a performance venue client, an audience member client, a DJ client, a music artist client and a blockchain node, for incentivizing musical performances by a DJ application running on the DJ client at a performance venue and promoting a sponsor product via an augmented reality content at the performance venue with a beacon associated with the performance venue client or with a geolocation chip of the audience member client, wherein the beacon is positioned internally or externally at the performance venue and the performance venue client interacts with the audience member client via beacon alerts using the beacon, the method further comprises:

storing, by the server, a sponsor user profile of the sponsor client, a server user profile of the server, a performance venue profile of the performance venue client and a music artist profile of the music artist client, wherein the sponsor user profile (a) comprises a first crypto-asset wallet address, and a digital utility token, and (b) is associated with a sponsor product, and wherein the server user profile comprises a second crypto-asset wallet address;

associating, by the server, the digital utility token associated with the first crypto-asset wallet address of the sponsor user profile with the sponsor product by receiving a first request from the sponsor client;

communicating, by the server, data associated with the sponsor product to the performance venue client;

sending, by the server, information associated with the augmented reality content of the sponsor product to the audience member client within the performance venue;

performing, by the server, a first assignment associated with the digital utility token from the first crypto-asset wallet address of the sponsor user profile to the second crypto-asset wallet address of the server user profile in response to the communicating the data associated with the sponsor product to the performance venue client and the sending the information associated with the augmented reality content of the sponsor product to the audience member client;

sending, by the server, a second request to the blockchain node to record the first assignment associated with the digital utility token from the first crypto-asset wallet address of the sponsor user profile to the second crypto-asset wallet address of the server user profile;

receiving, by the server, an audio content from the DJ application of the DJ client, wherein the audio content from the DJ application is the music being played by the DJ client within the performance venue;

based on the received audio content, accessing, by the server, a database, wherein the database stores a plurality of music piece identifiers and a plurality of crypto-asset wallet addresses, wherein each of the music piece identifiers corresponds to one of the crypto-asset wallet addresses;

comparing, by the server, the received audio content with the music piece identifiers based on the server accessing the database;

determining, by the server, a match between the received audio content and at least one of the music piece identifiers based on the comparison;

based on the determined match, identifying, by the server, at least one of the crypto-asset wallet addresses corresponding to the at least one of the music piece identifiers and the music artist profile associated with the at least one of the music piece identifiers;

performing, by the server, a second assignment associated with a value of the digital utility token from the second crypto asset wallet address of the server user profile to a third crypto-asset wallet address, wherein the third crypto-asset wallet address is the identified at least one of the crypto asset wallet addresses;

sending, by the server, a third request to the blockchain node to record the second assignment of the value of the digital utility token from the second crypto-asset wallet address to the third crypto-asset wallet address; and

notifying, by the server, the music artist client of the second assignment based on the identified music artist profile.

2. The method of claim 1 , wherein the audio content includes an acoustic fingerprint, wherein the comparing comprises comparing the acoustic fingerprint with the music piece identifiers.

3. The method of claim 1 , wherein the receiving the audio content further comprises:

generating, by the server, an acoustic fingerprint based on the received audio content; and

wherein the comparing comprises comparing the generated acoustic fingerprint with the music piece identifiers.

4. The method of claim 1 , wherein the music piece identifiers include a plurality of acoustic fingerprints, wherein the comparing comprises comparing the received audio content with the acoustic fingerprints.

5. The method of claim 1 , wherein the database is an in-memory database.

6. The method of claim 1 , wherein the blockchain node is an Ethereum based node.

7. The method of claim 1 , wherein the DJ client is the music artist client.

8. The method of claim 1 , wherein the DJ client is not the music artist client.

9. The method of claim 1 , wherein the blockchain node is remote from the DJ client and the music artist client.

10. The method of claim 1 , wherein at least two of the music piece identifiers correspond to at least one of the crypto-asset wallet addresses.

11. The method of claim 1 , wherein at least one of the music piece identifiers corresponds to at least two of the crypto-asset wallet addresses.

12. The method of claim 1 , wherein the database stores a record, wherein the record comprises the at least one of the music piece identifiers and the at least one of the crypto-asset wallet addresses.

13. The method of claim 1 , wherein the database stores a first record and a second record, wherein the first record comprises the at least one of the music identifiers; and the second record comprises the at least one of the crypt-asset wallet addresses, and

wherein the comparing further comprises:

storing, by the server, a third record in the database, wherein the third record comprises an association of the first record and the second record.