Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Torrent Server for Metadata #6

Closed
RekhaTcs opened this issue Aug 24, 2016 · 1 comment
Closed

Torrent Server for Metadata #6

RekhaTcs opened this issue Aug 24, 2016 · 1 comment
Labels

Comments

@RekhaTcs
Copy link

RekhaTcs commented Aug 24, 2016

I saw an API called addMetadata , which is expecting a token from torrent server.
Can anyone help me in answering the following questions?

  1. What is the token that they are referring to?
  2. And in one of the colored coins documentation , I came across that Bittorrent protocol is used to store and share data.
    so my question is whether colored coins is restricted to Bittorent.
@oleiba
Copy link
Contributor

oleiba commented Aug 25, 2016

Our Torrent server is currently a closed source and only allows private requests.
As such, it requires a JWT (JSON web token) encoded with a secret configured in both servers environment variables.
It uses https://github.com/Colored-Coins/Metadata-Handler as a Bittorrent client, to seed and download metadata torrents.
Regarding your second question - I am not sure I understand what you're asking, but anyway:
Yes, Colored-Coins protocol relies on the Bittorrent network, from the thought of being able to store assets metadata without size limits, and staying within the architecture of peer-to-peer.
The connection between a colored-coins transaction and its corresponding meta-data is achieved with the encoding of the torrent info-hash (20 bytes SHA1).

@oleiba oleiba closed this as completed Aug 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants