Oh wow; up until now I’ve only seen spacechain demos that didn’t actually implement the spacechain part. Is the spacechain data archived somewhere?
Not using a NUMS point probably makes sense for an experiment – lets you use a key path spend to hardfork the spacechain when updating the code, while potentially retaining history. Of course, that assumes you’re using a somewhat secure key; looks like you used G so the funds could be stolen at any point (edit: or more importantly, the spacechain could be stopped dead) by anyone who can figure out what signature the latest scriptPubKey contains.
(I was expecting a non-well-known pubkey and a published list of signatures, which would have been secure-ish and also allowed permissionless mining)
If I’m reading the code right, you limited the spacechain to only doing 50 blocks (Publish.scala, bmm.precompute(0, 50)), which looks like it about matches the number of txs listed above, which presumably means the only script path spend you can do now is the final tx, paying to a 0sat “fim” OP_RETURN and reclaiming the funds (or using them for fees, or using them to launch a brand new spacechain)?