bittorrent-dht
ens
bittorrent-dht | ens | |
---|---|---|
3 | 293 | |
1,199 | 1,140 | |
0.3% | - | |
5.8 | 0.0 | |
22 days ago | 7 months ago | |
JavaScript | JavaScript | |
MIT License | BSD 2-clause "Simplified" 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.
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.
ens
- Show HN: Prototype for ETH Signing for endorsing Wikipedia updates
-
Don't trust, verify: Indexing ENS Domains with Subsquid
While creating these tutorials, I choose Ethereum Name Service as an example, because it's a famous project, and quite frankly, also because I take these changes to study some subjects I am interested in (sue me! 😛).
- Domain registrar Gandi gets bought out, screws existing customers
-
Domain Names as Handles in Bluesky
> I hope this idea catches on
This already exists with Ethereum Name Service (ENS) https://ens.domains and Sign-in With Ethereum.
-
Binance to Suspend US Dollar Bank Transfers
ENS is my go to example for something novel and useful that Ethereum enables. Instantly propagating private key based DNS.
https://ens.domains
-
Nostr.how – A Complete Guide to Nostr
One of the first applications of blockchains was DNS. (Namecoin) ENS is a modern form. (https://ens.domains)
I would say there's still some degree of centrality for ENS, but it is more decentralized than DNS.
-
Ethereum Name Service ($ENS) is Airdropping Tokens worth up to 5000$ for the first 1000 People To Claim it.
This is a scam. The real url is ens.domains, not ens.com.
- How do I register my address to a short, meaningful name? I have seen a lot with word and .eth - thanks!
- Its been a whole cycle now.
- $850 USD to renew your own .dev domain which is owned by Google, insane
What are some alternatives?
webtorrent - ⚡️ Streaming torrent client for the web
ipfs - Peer-to-peer hypermedia protocol
ipfs-pubsub-room - IPFS Pubsub room
namecoin.org - Namecoin.org website in Jekyll -- send PR's to beta branch, then merge into master and gh-pages
bittorrent-tracker - 🌊 Simple, robust, BitTorrent tracker (client & server) implementation
flow-nft - The non-fungible token standard on the Flow blockchain
torrent-paradise - Decentralized DHT search site for IPFS
rainbow - 🌈‒ the Ethereum wallet that lives in your pocket
webtorrent - ⚡️ Streaming torrent client for the web [Moved to: https://github.com/webtorrent/webtorrent]
ens-app - Legacy ENS manager app
webtorrent-desktop - ❤️ Streaming torrent app for Mac, Windows, and Linux
arweave - The Arweave server and App Developer Toolkit.