Skip to content

Commit b750860

Browse files
authored
Merge pull request #94 from ValuedMammal/doc/include-str
docs: automatically include README text in lib.rs
2 parents 965582b + 788c778 commit b750860

File tree

1 file changed

+1
-15
lines changed

1 file changed

+1
-15
lines changed

src/lib.rs

+1-15
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,4 @@
1-
//! BDK-Kyoto is an extension of [Kyoto](https://github.com/rustaceanrob/kyoto), a client-side implementation of BIP157/BIP158.
2-
//! These proposals define a way for users to fetch transactions privately, using _compact block
3-
//! filters_. You may want to read the specification [here](https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki).
4-
//!
5-
//! Kyoto runs as a psuedo-node, sending messages over the Bitcoin peer-to-peer layer, finding new
6-
//! peers to connect to, and managing a light-weight database of Bitcoin block headers. As such,
7-
//! developing a wallet application using this crate is distinct from a typical client/server
8-
//! relationship. Esplora and Electrum offer _proactive_ APIs, in that the servers will respond to
9-
//! events as they are requested. In the case of running a node as a background process, the
10-
//! developer experience is far more _reactive_, in that the node may emit any number of events, and
11-
//! the application may respond to them.
12-
//!
13-
//! BDK-Kyoto curates these events into structures that are easily handled by BDK APIs, making
14-
//! integration of compact block filters easily understood. Developers are free to use [`bdk_wallet`], or only primatives found in [`bdk_core`](https://docs.rs/bdk_core/latest/bdk_core/) and [`bdk_chain`].
15-
//!
1+
#![doc = include_str!("../README.md")]
162
//! ## Examples
173
//!
184
//! If you have an existing project that leverages `bdk_wallet`, building the compact block filter

0 commit comments

Comments
 (0)