rebase onto master

rebase onto master

In D16821#382053, @bytesofman wrote:

really does get us into some interesting complexity needing to check the existing orderbook before making an order.

Improve comments to direct people to the new function

Add Agora.selectParams to abstract away the selection of enforcedLockTime.

But I think what we should do it also add an object that safely creates good lock times (and storing previous one internally), and then people just forward this value from that object. Would also allow for future extensions.

In D16821#381670, @bytesofman wrote:

So i this case -- we are using locktime because it's an existing field that is available in script. But we are not really setting a locktime -- we are setting a sort of nonce, that should be a unique ID.

use ===

tabs

fix lints

rebase and fix join

One nit

Otherwise looks good to me!

@bot check-iguana

improve tests, rebase

one small nit

rebase onto D16753.

rebase on D16745.

address review + based memes

otherwise lgtm

fix !

remove GetNextOp, rename some functions to map more closely to what they do

rebase onto D16754.

rebase onto D16753.

rebase onto D16745.

rebase onto D16743

rebase on master

exposing CastToBool is not needed

add tests, refactor a bit

let's add some tests

add missing headers

This has a weird double-scroll behavior. Isn't just simpler to just put all the stuff in cashtab and let the browser handle the scrolling?