fmt: run go fmt

Since v1.19.0 `go fmt` also formats comments. This commit is only to
ensure that `go fmt ./...` does not modify any of our commited files.
This commit is contained in:
positiveblue 2023-01-04 13:59:01 -08:00
parent 033991dbad
commit a66a63e895
No known key found for this signature in database
GPG key ID: 4FFF2510928804DC
3 changed files with 33 additions and 30 deletions

View file

@ -15,25 +15,26 @@ import (
)
// batch-snapshot-bucket
// |
// |-- batch-snapshot-pending-key: <batch snapshot>
// |
// |-- batch-snapshot-seq-bucket
// | |
// | |-- <sequence num>
// | | |
// | | |-- batch-snapshot-batch: <batch snapshot>
// | |
// | |-- <sequence num>
// | | |
// | ... ...
// |
// |-- batch-snapshot-batchid-index-bucket
// |
// |-- <batch id>: <sequence-num>
// |-- <batch id>: <sequence-num>
// |
// ...
//
// |
// |-- batch-snapshot-pending-key: <batch snapshot>
// |
// |-- batch-snapshot-seq-bucket
// | |
// | |-- <sequence num>
// | | |
// | | |-- batch-snapshot-batch: <batch snapshot>
// | |
// | |-- <sequence num>
// | | |
// | ... ...
// |
// |-- batch-snapshot-batchid-index-bucket
// |
// |-- <batch id>: <sequence-num>
// |-- <batch id>: <sequence-num>
// |
// ...
var (
// batchSnapshotBucketKey is the top level bucket where we'll find
// snapshot information about all batches we have participated in.

View file

@ -275,10 +275,11 @@ func (r *RecoveryHelper) LocateAnyOutput(expiry uint32,
// AccountScript returns the output script of an account on-chain.
//
// For version 0 (p2wsh) this returns the hash of the following script:
// <trader_key> OP_CHECKSIGVERIFY
// <auctioneer_key> OP_CHECKSIG OP_IFDUP OP_NOTIF
// <account_expiry> OP_CHECKLOCKTIMEVERIFY
// OP_ENDIF
//
// <trader_key> OP_CHECKSIGVERIFY
// <auctioneer_key> OP_CHECKSIG OP_IFDUP OP_NOTIF
// <account_expiry> OP_CHECKLOCKTIMEVERIFY
// OP_ENDIF
//
// For version 1 (p2tr) this returns the taproot key of a MuSig2 combined key
// of the auctioneer's and trader's public keys as the internal key, tweaked

View file

@ -25,13 +25,14 @@ import (
// SidecarAcceptor is a type that is exclusively responsible for managing the
// recipient's tasks of executing a sidecar channel. The two tasks are:
// 1. Verify a sidecar ticket and the offer contained within then add the
// recipient node information to the ticket so it can be returned to the
// sidecar provider. This is step 2/4 of the entire sidecar execution
// protocol.
// 2. Interact with the auction server and connect out to an asker's node in the
// right moment then accept the incoming channel. This is step 4/4 of the
// entire sidecar execution protocol.
// 1. Verify a sidecar ticket and the offer contained within then add the
// recipient node information to the ticket so it can be returned to the
// sidecar provider. This is step 2/4 of the entire sidecar execution
// protocol.
// 2. Interact with the auction server and connect out to an asker's node in the
// right moment then accept the incoming channel. This is step 4/4 of the
// entire sidecar execution protocol.
//
// The code for these two tasks are kept separate from the default funding
// manager to make it easier to extract a standalone sidecar acceptor client
// later on. It also makes it easier to see what code would need to be re-