Update TODOs in README

diff --git a/README.md b/README.md
index 877ccc3bcf6150d506d3146144eda78711159b54..24a76c2276dab03433a68f3d689c634d167c425f 100644 (file)
--- a/README.md
+++ b/README.md
@@ -27,17 +27,13 @@ Assorted random TODOs:
    a timer. By default we should provide an implementation of this which uses
    some newfangled rusty promise-y library, but should generally ensure a
    client can simply integrate this into whatever existing timer interface
-   they use.
-
- * Networking...having a simple bytes-in-bytes-out interface which does message
-   handling and calls our encryption layer is probably the right approach. We
-   should then also probably use the same promise-y library we use for timers
-   to do socket selection and reading/writing.
+   they use. (This is partially complete, but the events stuff needs to also
+   exist in Channel, which has a few inline TODOs to set up timers).
 
  * Figure out how to expose when-to-connect and who-to-connect-to.
 
  * Implement when-to-connect and who-to-connect-to based on route/node rumoring
-   and channelmanager state.
+   and channelmanager state (and some concept of available value in wallet).
 
  * Some kind of serialization format for on-disk storage of things like
    channels, channelmonitors, routing db, etc.
@@ -50,8 +46,6 @@ Assorted random TODOs:
 
  * All the random TODOs and unimplemented!()s across the codebase.
 
- * BOLT 11 (invoice/address creation/generation) implementation
-
  * Type-ify our somewhat random usage of Uint256/[u8; 32]. Use Sha256dHash
    where appropriate, create our own types for everything else.