TAU
bittorrent-dht
TAU | bittorrent-dht | |
---|---|---|
7 | 3 | |
11 | 1,199 | |
- | 0.4% | |
0.0 | 5.8 | |
over 1 year ago | 23 days ago | |
JavaScript | ||
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
TAU
-
TAU: open and free source code
Please if you consider deploying your fully owned free ads coin to your community to make ads income, visit here to download TAU server-less app and check details.
- Freely airdrop your Ads coins to expand community, and sell coins to marketeers for Ads display.
-
IP2 and development status
We really love our public key to public key communication model. It solves internet devices universal connectivity issues and guarantee a communication channel even firewall and NAT wants to block it. So here we standardize it to IP2 protocol.
-
TAU App will natively enable 1300 community blockchains and airdropping 80% of the coins to community leaders. Check which city you live!
We have identified 1300 regions with 1 million population. The unique power of TAU tech is to run thousands of blockchains in parallel. This is the time to use it. For these 1300 regions include most of metros in the world, we will build one blockchain for each region. Once some user's location matches, the p2p trade blockchain will show up in the app. These blockchains are all registered on TAU main chain by TAU Dev. At the same time, we will airdrop 80% of the 1300 chains to community leaders in those region.
-
Killer App thinking for libTAU
I went to Knights of Nordic event recently. During many technical conversations, I feel one place that libTAU might have very fast adoption in Z generation. Music coins Each music, song or album, has native fans and supporters, most of them are younger and more familiar with digital technology. As an artist, pushing music fans to spend transaction fee on eth, sol, bnb or ada to play NFT is a costly action. Forming a blockchain community with native coins will be a free option for the artist. Free is an enormous power in both saving money and faster user experiences. I might need to talk to a few more music people to understand this better. Blockchain is a long life thing for community, the owner ship of a song might belong to a blockchain community rather than a company or artist themselves.
bittorrent-dht
- Theseus DHT Protocol
-
Static torrent website with peer-to-peer queries over BitTorrent on 2M records
I'm not talking about the consensus protocol of the blockchain itself, but of the p2p algorithms underlying it, e.g. using Kademlia for service discovery and message routing. I'm asking why a distributed system would choose something like Consul (which uses Raft, and requires a coordinator node) instead of running a decentralized protocol like Kademlia (which has no coordinator nodes) within their distributed single-tenant environment.
I did a bit more research last night, and discovered that Bitfinex actually does something like this internally (anyone know if this is up to date?) [0] — they built a service discovery mesh by storing arbitrary data on a DHT implementing BEP44 (using webtorrent/bittorrent-dht [1]).
This seems pretty cool to me, and IMO any modern distributed system should consider running decentralized protocols to benefit from their robustness properties. Deploying a node to a decentralized protocol requires no coordination or orchestration, aside from it simply joining the network. Scaling a service is as simple as joining a node to the network and announcing its availability of an implementation of that service.
At first glance, this looks like a competitive advantage, because it decouples the operational and maintenance costs of the network from the size of the network.
So I'm wondering if there is a consistent tradeoff in exchange for this robustness — are decentralized applications more complex to implement but simpler to operate? Is latency of decentralized protocols (e.g. average number of hops to lookup item in a DHT) untenably higher than that of distributed protocols (e.g. one hop once to get instructions from coordinator, then one hop to lookup item in distributed KV)? Does a central coordinator eliminate some kind of principle agent problem, resulting in e.g. a more balanced usage of the hashing keyspace?
Decentralization emerged because distributed solutions fail in untrusted environments — but this doesn't mean that decentralized solutions fail in trusted environments. So why not consider more decentralized protocols to scale internal systems?
[0] https://github.com/bitfinexcom/grenache
[1] https://github.com/webtorrent/bittorrent-dht
-
Decentralized in-browser torrent site
Yes the database is fixed. I would like to make it updateable using web2web or mutable torrents (BEP44) which the WebTorrent DHT supports.
What are some alternatives?
sentient - Simple sentiment analysis using the AFINN-111 word list
webtorrent - ⚡️ Streaming torrent client for the web
ipfs-pubsub-room - IPFS Pubsub room
bittorrent-tracker - 🌊 Simple, robust, BitTorrent tracker (client & server) implementation
torrent-paradise - Decentralized DHT search site for IPFS
webtorrent - ⚡️ Streaming torrent client for the web [Moved to: https://github.com/webtorrent/webtorrent]
webtorrent-desktop - ❤️ Streaming torrent app for Mac, Windows, and Linux
rats-search - BitTorrent P2P multi-platform search engine for Desktop and Web servers with integrated torrent client.
libtorrent4j - libtorrent for java, a swig Java interface for libtorrent
ipfs - Peer-to-peer hypermedia protocol
magnet-uri - Parse a magnet URI and return an object of keys/values
autodl-rutorrent - ruTorrent plugin for autodl-community fork of autodl-irssi