Chain Syncs

This section makes reference to various API calls. Click here for the full technical documentation related to those requests.

What is a chain sync?

Chain Syncs come in multiple varieties, but in all cases, they involve taking a data set, whether it be the metadata associated with a song, or that song's audio fingerprint, and sending them to various blockchain to promote immutability.

Generally, chain syncs go from our local network to a private BESU network, and then from the private BESU network to the Ethereum mainnet network.

How do I initiate a chain sync for my song's data?

The process of getting a song from outside of WrapDapp's application all the way to the Ethereum Mainnet is a complex one, but generally speaking, the steps required are:

Create a user in the platform (creates a wallet) using the POST/user endpoint.
Add a song into the user's wallet using the POST/user/{userId}/song endpoint.
Finally, use the POST/song/{songId}/metadata endpoint to create a snapshot of the song's metadata at this point in time.

Where does chain sync data live?

If you've followed the steps in the "How do I initiate a chain sync for my song's data?" question above, this means that you've sent a hashed representation of your song's data to our internal BESU blockchain network (you can think of BESU as our "staging area" before we send hashed data onto the Ethereum mainnet.).

However the data doesn't only live there: routinely, our internal systems will create "roll up" chain syncs, which send the combined hashes of recently hashed songs directly to the Ethereum Mainnet.

How often is chain sync data sent to mainnet?

The frequency varies depending on a variety of factors, but we aim to do roll up chain syncs once daily.

How do I see a history of what data was synced and when?

You can use the GET/sync endpoint to search and filter through all of our historical data regarding chain syncs.