System and method for scalably tracking media playback using blockchain

1. A system for tracking play of media files via a blockchain based platform, the system comprising:

a media request tracking server comprising:

a processor; and

memory, the memory storing instructions to cause the processor to execute a method, the method comprising:

receiving transaction data corresponding to play request from a platform stream, the platform stream corresponding to a platform streaming server that is separate from the media request tracking server, the transaction data corresponding to a request from an end user to the platform streaming server to play a media file at an end user device, wherein if the request is granted, the platform streaming server transmits the media file directly to the end user;

verifying the transaction data;

signing the verified transaction data using a cryptographic signature; and

validating the blockchain transaction, wherein validating the transaction data includes 1) having a first validation node of three validation nodes use their private key to sign the transaction data to prove that they have seen and validated the transaction data, 2) passing the signed request to a second validation node of the three validation nodes in order for the second validation node to use their private key and sign the transaction data, and 3) having a third validation node of the three validation nodes commit the transaction data, along with the signatures of the first and second validation nodes, to a blockchain, wherein the play request is not considered a valid play request to be added to a play count until there is a verifying signature associated to the play request from at least two validation nodes.

2. The system of claim 1 , wherein the transaction data includes a cryptographic signature corresponding to the end user.

3. The system of claim 1 , wherein determining whether the transaction data corresponds to a valid blockchain transaction includes verifying that the transaction data includes two cryptographic signatures from authorized or registered validation nodes.

4. The system of claim 1 , wherein verifying the transaction data includes verifying: 1) whether the format of the transaction data follows a protocol established by the platform, and 2) whether the transaction data includes a cryptographic signature of the end user that can be verified with a public key corresponding to the end user.

5. The system of claim 1 , wherein valid blockchain transactions are separately stored to a database such that third parties can access the data through a custom platform application programming interface (API).

6. The system of claim 1 , wherein valid blockchain transactions are periodically merklized, thereby producing merkle roots.

7. The system of claim 6 , wherein the merkle roots are committed to an external third-party blockchain as a supplemental point of security.

8. A system for tracking play of media files via a blockchain based platform, the system comprising:

a media request tracking server comprising:

a processor; and

memory, the memory storing instructions to cause the processor to execute a method, the method comprising:

receiving transaction data corresponding to play request from a platform stream, the platform stream corresponding to a platform streaming server that is separate from the media request tracking server, the transaction data corresponding to a request from an end user to a first validation node to play a media file at an end user device, wherein if the request is granted, the platform streaming server transmits the media file directly to the end user;

verifying the transaction data;

signing the verified transaction data using a cryptographic signature; and validating the blockchain transaction, wherein validating the transaction data includes 1) having a first validation node of three validation nodes use their private key to sign the transaction data to prove that they have seen and validated the transaction data, 2) passing the signed request to a second validation node of the three validation nodes in order for the second validation node to use their private key and sign the transaction data, and 3) having a third validation node of the three validation nodes commit the transaction data, along with the signatures of the first and second validation nodes, to a blockchain, wherein the play request is not considered a valid play request to be added to a play count until there is a verifying signature associated to the play request from at least two validation nodes.

9. The system of claim 8 , wherein the transaction data includes a cryptographic signature corresponding to the end user.

10. The system of claim 8 , wherein the transaction data is passed to the platform stream from the first validation node.

11. The system of claim 8 , wherein verifying the transaction data includes verifying: 1) whether the format of the transaction data follows a protocol established by the platform, and 2) whether the transaction data includes a cryptographic signature of the end user that can be verified with a public key corresponding to the end user.

12. The system of claim 8 , wherein valid blockchain transactions are separately stored to a database such that third parties can access the data through a custom platform application programming interface (API).

13. The system of claim 8 , wherein valid blockchain transactions are periodically merklized, thereby producing merkle roots.

14. The system of claim 13 , wherein the merkle roots are committed to an external third-party blockchain as a supplemental point of security.

15. A method for tracking play of media files via a blockchain based platform, the method comprising:

receiving, at a media request tracking server, transaction data corresponding to play request from a platform stream, the platform stream corresponding to a platform streaming server that is separate from the media request tracking server, the transaction data corresponding to a request from an end user to the platform streaming server to play a media file at an end user device, wherein if the request is granted, the platform streaming server transmits the media file directly to the end user;

verifying the transaction data;

signing the verified transaction data using a cryptographic signature; and

validating the blockchain transaction, wherein validating the transaction data includes 1) having a first validation node of three validation nodes use their private key to sign the transaction data to prove that they have seen and validated the transaction data, 2) passing the signed request to a second validation node of the three validation nodes in order for the second validation node to use their private key and sign the transaction data, and 3) having a third validation node of the three validation nodes commit the transaction data, along with the signatures of the first and second validation nodes, to a blockchain, wherein the play request is not considered a valid play request to be added to a play count until there is a verifying signature associated to the play request from at least two validation nodes.

16. The method of claim 15 , wherein the transaction data includes a cryptographic signature corresponding to the end user.

17. The method of claim 15 , wherein determining whether the transaction data corresponds to a valid blockchain transaction includes verifying that the transaction data includes two cryptographic signatures from authorized or registered validation nodes.

18. The method of claim 15 , wherein verifying the transaction data includes verifying: 1) whether the format of the transaction data follows a protocol established by the platform, and 2) whether the transaction data includes a cryptographic signature of the end user that can be verified with a public key corresponding to the end user.

19. The method of claim 15 , wherein valid blockchain transactions are separately stored to a database such that third parties can access the data through a custom platform application programming interface (API).

20. The method of claim 15 , wherein valid blockchain transactions are periodically merklized, thereby producing merkle roots.