parity-bitcoin VS trust-dns

Compare parity-bitcoin vs trust-dns and see what are their differences.


A Rust based DNS client, server, and resolver [Moved to:] (by bluejekyll)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern API for authentication & user identity.
  • Onboard AI - ChatGPT with full context of any GitHub repo.
parity-bitcoin trust-dns
3 14
723 3,254
0.3% -
0.0 7.1
8 months ago 4 months ago
Rust Rust
GNU General Public License v3.0 only GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.


Posts with mentions or reviews of parity-bitcoin. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-06-28.


Posts with mentions or reviews of trust-dns. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-09.
  • You might want async in your project
    2 projects | | 9 Sep 2023
    IO is not a part of the async runtime contract (I don't know if this is good or bad), and Tokio & futures famously have different `Async{Read,Write}` traits. I once had to do this [0] to adapt between them.

    This means that any crate that uses IO will be bound to a limited number of Runtimes. Everything being Tokio-only is pretty bad (though Tokio itself is great), but here we are...


  • What would you rewrite in Rust?
    44 projects | /r/rust | 11 Feb 2023
    You might be interested in Trust DNS - "A Rust based DNS client, server, and Resolver, built to be safe and secure from the ground up."
  • Announcing `async-dns`
    4 projects | /r/rust | 22 Sep 2022
    It looks like you need to reach for a separate crate for that:
    4 projects | /r/rust | 22 Sep 2022
    This is not true; you can use the async resolver with other executors:
  • Innernet: Open source Rust based Tailscale alternative by Tonari
    6 projects | | 29 Mar 2021
    You could run a local DNS server using something like . Or, you could install an NSS module to resolve names via the innernet client.
  • single-producer single-consumer concurrent queue
    5 projects | /r/rust | 29 Mar 2021
    My point is that "implementation that doesn't use unsafe" is not necessarily always slower than "implementation that does use unsafe". Often people assume that this is the case, and it isn't. tinyvec currently beats smallvec in more than a few benchmarks. Not all, but some. And this sometimes visible to users. The point is that if you want speed, you don't necessarily need to give up any safety at all. Most differences in performance are due to the amount of effort or expertise that has been spent on the codebase, not the amount of unsafe in it.

What are some alternatives?

When comparing parity-bitcoin and trust-dns you can also consider the following projects:

woodpecker - Drill is an HTTP load testing application written in Rust

citybound - A work-in-progress, open-source, multi-player city simulation game.

Parallel - Static site generator written in Rust

rsedis - Redis re-implemented in Rust.

tauri - Build smaller, faster, and more secure desktop applications with a web frontend.

iota - A terminal-based text editor written in Rust

tokei - Count your code, quickly.

Servo - Servo, the embeddable, independent, memory-safe, modular, parallel web rendering engine

tv-renamer - Mirror of