btcs

commit 7c6f29cb9d8c873016184f9062e064648779e558
parent 0edb2400c9be655222691f3abc6325fd2594e77c
Author: William Casarin <jb55@jb55.com>
Date:   Tue, 24 Oct 2017 10:55:25 -0700

doc: todo

Diffstat:
A
doc/TODO.org
 | 
20
++++++++++++++++++++

1 file changed, 20 insertions(+), 0 deletions(-)
diff --git a/doc/TODO.org b/doc/TODO.org
@@ -0,0 +1,20 @@
+
+* Suggestions
+
+`arubi` from #bitcoin-dev
+
+    10:44 <arubi> jb55, awesome. for my serializer, I also defined a few "make
+    your life easy" templates, like plain numbers are treated as scriptnum (need
+    to be valid), the character @ means minimal push, so something like @<hex
+    pubkey> is converted to 0x21 0x<pubkey> (and longer pushes if needed), a
+    0x<hex> is just treated like literal serialized part of the script.. you're
+    probably already on it, but just my pov :)
+    
+* Evaluator
+
+Some things to consider
+
+- [ ] May need context for things like CSV
+- [ ] Should we represent context as the program environment?
+- [ ] Pure environment and perhaps live testnet environment?
+- [ ] How to do this?