torrent file which contains the necessary metadata needed to start. This can be avoided by using the &xs parameter in the magnetURI or by specifying torrent.xs and then calling torrent._getMetadataFromServer() after being added to the client, which allows you to specify a HTTP(s) path to the. In both situations a peer must exist with the metadata, so there must be a seeding peer. With a magnetURI you can specify trackers using &tr, in combination with using the DHT these trackers would be used to find peers and again use ut_metadata to get the metadata from the peers. With just an infoHashes a typical BitTorrent client would query the Mainline DHT for peers then use ut_metadata to get the metadata from a peer, assuming a peer exists with the metadata. Mentioned by Feross above, you do not need a WRTC seed, but what you need is a way of getting the metadata of the torrent.
