Initial site

Author: valentinewallace

.gitignore

@@ -0,0 +1,20 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

README.md

@@ -1,3 +1,33 @@
-# lightningdevkit.org
-The dev website
+# Website
 
+This website is built using [Docusaurus 2](https://v2.docusaurus.io/), a modern static website generator.
+
+## Installation
+
+```console
+yarn install
+```
+
+## Local Development
+
+```console
+yarn start
+```
+
+This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server.
+
+## Build
+
+```console
+yarn build
+```
+
+This command generates static content into the `build` directory and can be served using any static contents hosting service.
+
+## Deployment
+
+```console
+GIT_USER=<Your GitHub username> USE_SSH=true yarn deploy
+```
+
+If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

babel.config.js

@@ -0,0 +1,3 @@
+module.exports = {
+  presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
+};

blog/2019-05-28-hola.md

@@ -0,0 +1,11 @@
+---
+slug: hola
+title: Hola
+author: Gao Wei
+author_title: Docusaurus Core Team
+author_url: https://github.com/wgao19
+author_image_url: https://avatars1.githubusercontent.com/u/2055384?v=4
+tags: [hola, docusaurus]
+---
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet

blog/2019-05-29-hello-world.md

@@ -0,0 +1,17 @@
+---
+slug: hello-world
+title: Hello
+author: Endilie Yacop Sucipto
+author_title: Maintainer of Docusaurus
+author_url: https://github.com/endiliey
+author_image_url: https://avatars1.githubusercontent.com/u/17883920?s=460&v=4
+tags: [hello, docusaurus]
+---
+
+Welcome to this blog. This blog is created with [**Docusaurus 2 alpha**](https://v2.docusaurus.io/).
+
+<!--truncate-->
+
+This is a test post.
+
+A whole bunch of other information.

blog/2019-05-30-welcome.md

@@ -0,0 +1,13 @@
+---
+slug: welcome
+title: Welcome
+author: Yangshun Tay
+author_title: Front End Engineer @ Facebook
+author_url: https://github.com/yangshun
+author_image_url: https://avatars0.githubusercontent.com/u/1315101?s=400&v=4
+tags: [facebook, hello, docusaurus]
+---
+
+Blog features are powered by the blog plugin. Simply add files to the `blog` directory. It supports tags as well!
+
+Delete the whole directory if you don't want the blog features. As simple as that!

docs/build_node.md

@@ -0,0 +1,90 @@
+---
+id: build_node
+title: Building a Node
+---
+
+## Introduction
+In this guide, we'll be building a lightning node using LDK.
+
+The completed sample node built in this guide is available at [TODO(val) insert link]. *Not intended for use in production.* This node is built using the Java bindings. See [TODO(val)] for all LDK language bindings options.
+
+Whether your project is an existing bitcoin-only wallet or a lightning wallet, the core process for
+integrating LDK is the same.
+
+The process breaks down to 3 overarching steps:
+1. Initializing LDK's channel, peer, chain monitoring, and (optionally) routing objects. 
+   * These objects will be parameterized by various other objects that can be from either your custom logic or one of LDK's supplied modules.
+<!-- 2. Starting loops to (a) poll for new peers and (b) tell LDK's channel and peer objects each time a minute passes, so they can properly maintain their state. -->
+2. Starting loops to (a) poll for new peers and (b) periodically nudge the channel and peer objects so they can properly maintain their state.
+   * Specific instructions for existing lightning wallets is found in the Lightning Wallet Integration Guide.
+3. Connect and disconnect blocks to LDK as they come in.
+
+## Requirements
+0. Some basic lightning knowledge like e.g. what a channel is, what force-closing means.
+1. A regtest bitcoind node (see [TODO(val) link to polar] for an easy way to spin this up)
+2. Java (this was tested using Java 11)
+<!-- 3. LDK's Java bindings jar [TODO link] in your class path -->
+TODO revise requirements
+
+## Part 0: Setup
+Import the bindings to your Java file and define a `main()`:
+```java
+import org.ldk.impl.bindings;
+
+public static void main(String[] args) {
+
+}
+```
+
+## Part 1: Managing Channels
+We'll start by initializing probably the most core struct to Rust-Lightning (see FAQs[TODO add link] for the difference between Rust-Lightning and LDK): the channel manager. 
+
+First, we'll initialize the objects that the channel manager is parameterized by.
+// fee estimator, chain_watch, tx broadcaster, logger, keys interface,
+
+## Part 1: Chain Monitoring
+Every lightning implementation needs a way to watch for relevant transactions appearing on-chain.
+
+### Setup
+But first, some housekeeping. 
+
+1. Within `main`, initialize a logger. A logger can be anything that satisfies the `LoggerInterface` interface [TODO add link]. In this case, we'll just print to the console.
+
+```java
+public static void main(String[] args) { 
+    // LoggerInterface is a functional interface, so we can implement it with a lambda
+    final logger = Logger.new_impl((String log) -> System.out.println(log));
+}
+```
+
+2. Add an on-chain fee estimator, which is anything that satisfies the `FeeEstimatorInterface` interface [TODO add link]. We need this because LDK's chain monitoring logic is responsible for broadcasting force-close transactions.
+
+```java
+    ..
+    final fee_estimator = FeeEstimator.new_impl((
+```
+
+3. Add a transaction broadcaster, which is anything that satisfies the `TransactionBroadcasterInterface` interface. We need this to broadcast the force-closing transaction if need be.
+```java
+    ..
+    final tx_broadcaster = 
+```
+
+
+4. Add a data persister, which is anything that satisfies the `PersisterInterface` interface. We need this because our chain monitoring system also needs to ensure that crucial channel data is pesisted to disk and/or backups.
+```java
+    ..
+    final persister = 
+```
+
+We're now ready to initialize our chain monitor.
+
+```java
+    ..
+    final chain_monitor = ChainMonitor.constructor_new(null, tx_broadcaster, logger, fee_estimator, persister);
+```
+
+Next, we'll add the feature of telling this object whenever we receive a connected or disconnected block.
+
+
+## 

docs/custom_blockdata.md

@@ -0,0 +1,6 @@
+---
+id: custom_blockdata
+title: Customizing Blockchain Data
+---
+
+TODO

docs/custom_key_mgmt.md

@@ -0,0 +1,6 @@
+---
+id: custom_key_mgmt
+title: Customizing Key Management
+---
+
+TODO

docs/custom_persist.md

@@ -0,0 +1,6 @@
+---
+id: custom_persist
+title: Customizing Data Persistence
+---
+
+TODO

docs/doc1.md

@@ -0,0 +1,28 @@
+---
+id: doc1
+title: Overview
+slug: /
+---
+
+Hi
+
+Ideas:
+Integrating LDK
+    Bitcoin-Only Wallet
+    Lightning Wallet
+
+LDK from Scratch: Walkthrough
+
+Customizing LDK
+    Persistence
+    Networking
+    Block Source
+    Key Management
+
+Language Bindings
+    Java/Kotlin
+    Swift
+
+References
+    Rust API Docs
+    Sample Node