Learn how to run a universe and connect to other universes.
Running a universe is as simple as running
tapdand amending your configuration file. To run a universe, set your instance to listen on the RPC port (10029) and ensure this port is open on your machine. Being publicly reachable is not a requirement for a universe, however. Your universe may only serve resources on a private network, or be otherwise restricted.
rpclisten=0.0.0.0:10029 allow-public-uni-proof-courier=true allow-public-stats=true universe.public-access=true
By default, your
tapdwill connect to the default universe, for instance
testnet.universe.lightning.finance:10029for testnet, or
The contents of the default universe are also available via a public API:
By default, your tapd instance will connect to a default universe. You can manually add additional universes to sync to and from, called a federation. You can see this federation with
tapcli universe federation list.
If you would like to add a universe to this federation, you can do this on with
tapcli universe federation add --universe_host <universe_ip:port>
Similarly, you can remove universes from this federation with
tapcli universe federation del --universe_host <universe_ip>:port
By default, your
tapdwill sync to universes 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
tapdto regularly sync to other asset IDs or group keys, you may use the universe federation configuration. The
config globaloptions will apply to all assets, while the
config localoptions 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>