GITBOOK-386: change request with no subject merged in GitBook

lightning-network-tools/taproot-assets/first-steps.md

@@ -165,14 +165,12 @@ Or on mainnet:
 
 `tapcli universe federation add --universe_host universe.lightning.finance`
 
-Your node will periodically sync with the universes you have added to your federation, but you can also always manually sync with any universe using:
+Your node will sync with the universes you have added to your federation whenever you create a new taproot asset address with an unknown asset ID, or when specifically instructed to. This requires an asset ID or a group key.
 
-`tapcli universe sync --universe_host <universe_ip:port>`
+`tapcli universe sync --universe_host <universe_ip:port> --asset_id <asset id>`
 
 Upon successful sync, information about existing assets should be retrieved, alongside their issuance proofs.
 
-Newly minted assets are automatically synced to all universes in your local federation.
-
 ## Generating Taproot Assets addresses <a href="#docs-internal-guid-2d861222-7fff-ef76-60b9-65367a4fd1b7" id="docs-internal-guid-2d861222-7fff-ef76-60b9-65367a4fd1b7"></a>
 
 As soon as your minted assets have one confirmation on the blockchain, you are able to send them. To send assets, you will need the recipient’s Taproot Assets address. This Taproot Assets address is specific to an asset and amount, so to generate an address, the recipient needs to know an asset’s `asset_id`, as well as be synced to the issuer’s universe. Taproot Assets address reuse should be avoided.

lightning-network-tools/taproot-assets/get-tapd.md

@@ -31,6 +31,8 @@ Optionally, create a Taproot Assets configuration file under `~/.tapd/tapd.conf`
 
 Within the `tapd.conf` file you can permanently set your variables, such as directory, macaroon or other paths and how to connect to your LND.
 
+As there is currently no migration path between the SQLite and Postgres backends, the backend needs to be configured when `tapd` is first initialized.
+
 ## Running tapd: <a href="#docs-internal-guid-ebf73e49-7fff-b5ed-44ff-b9b0953c6082" id="docs-internal-guid-ebf73e49-7fff-b5ed-44ff-b9b0953c6082"></a>
 
 Run Taproot Assets with the command `tapd`. Specify how Taproot Assets can reach LND and what bitcoin network to run Taproot Assets with by passing it additional flags.

lightning-network-tools/taproot-assets/universes.md

@@ -22,5 +22,16 @@ You can add and remove universes from your local federation with `tapcli univers
 
 The contents of the default universe are also available via a public API:
 
-[https://universe.lightning.finance/v1/taproot-assets/universe/roots](https://universe.lightning.finance/v1/taproot-assets/universe/roots)
+{% embed url="https://universe.lightning.finance/v1/taproot-assets/universe/roots" %}
 
+## Syncing to a universe
+
+By default, your `tapd` will sync to universes for which have configured in your local federation, and only for assets which you either hold or have created a taproot address for. You may also manually sync specific asset IDs or group keys.
+
+`tapcli universe sync --universe_host <universe_ip:port> --group_key <group key>`
+
+To configure your `tapd` to regularly sync to other asset IDs or group keys, you may use the universe federation configuration. The `config global` options will apply to all assets, while the `config local` options will only apply to specific assets.
+
+`tapcli universe federation config global --proof_type issuance --allow_insert true`
+
+`tapcli universe federation config local --proof_type transfer --allow_insert true --group_key <group key>`