migrations: re-apply migration 14 as 23.

Due to a git branch cherry-pick mishap, the migration number 14 wasn't
included in a released version and therefore wasn't applied on some
systems. Because the tables in that migration file were only being used
with a recently released version (v0.4.0/v0.4.1), this wasn't noticed
for a long time.
We fix this by re-applying the same migration as number 23, slightly
modified so that it's a no-op if the tables and entries already exist on
a system.

Author: guggero

tapdb/migrations.go

@@ -22,7 +22,7 @@ const (
 	// daemon.
 	//
 	// NOTE: This MUST be updated when a new migration is added.
-	LatestMigrationVersion = 22
+	LatestMigrationVersion = 23
 )
 
 // MigrationTarget is a functional option that can be passed to applyMigrations

tapdb/sqlc/migrations/000023_multiverse_tree_re_apply.down.sql

@@ -0,0 +1,3 @@
+DROP INDEX IF EXISTS multiverse_leaves_unique;
+DROP TABLE IF EXISTS multiverse_leaves;
+DROP TABLE IF EXISTS multiverse_roots;

tapdb/sqlc/migrations/000023_multiverse_tree_re_apply.up.sql

@@ -0,0 +1,94 @@
+-- This is a slightly modified duplicate of migration 14, which due to a git
+-- branch cherry-pick mistake wasn't included in a released version.
+-- If this is running on a version that already has the tables, then this is a
+-- no-op.
+
+CREATE TABLE IF NOT EXISTS multiverse_roots (
+    id BIGINT PRIMARY KEY,
+
+    -- For the namespace root, we set the foreign key constraint evaluation to
+    -- be deferred until after the database transaction ends. Otherwise, if the
+    -- root of the SMT is deleted temporarily before inserting a new root, then
+    -- this constraint is violated as there's no longer a root that this
+    -- universe tree can point to.
+    namespace_root VARCHAR UNIQUE NOT NULL REFERENCES mssmt_roots(namespace) DEFERRABLE INITIALLY DEFERRED,
+
+    -- This field is an enum representing the proof type stored in the given
+    -- universe.
+    proof_type TEXT NOT NULL CHECK(proof_type IN ('issuance', 'transfer'))
+);
+
+CREATE TABLE IF NOT EXISTS multiverse_leaves (
+    id BIGINT PRIMARY KEY,
+
+    multiverse_root_id BIGINT NOT NULL REFERENCES multiverse_roots(id),
+
+    asset_id BLOB CHECK(length(asset_id) = 32),
+
+    -- We use the 32 byte schnorr key here as this is what's used to derive the
+    -- top-level Taproot Asset commitment key.
+    group_key BLOB CHECK(LENGTH(group_key) = 32),
+    
+    leaf_node_key BLOB NOT NULL,
+
+    leaf_node_namespace VARCHAR NOT NULL,
+
+    -- Both the asset ID and group key cannot be null at the same time.
+    CHECK (
+        (asset_id IS NOT NULL AND group_key IS NULL) OR
+        (asset_id IS NULL AND group_key IS NOT NULL)
+    )
+);
+
+CREATE UNIQUE INDEX IF NOT EXISTS multiverse_leaves_unique ON multiverse_leaves (
+    leaf_node_key, leaf_node_namespace
+);
+
+-- If there already is a multiverse root entry in the mssmt_roots for the
+-- issuance or transfer multiverses, add them to the multiverse_roots table as
+-- well. Both statements are no-ops if the root doesn't exist yet.
+INSERT INTO multiverse_roots (namespace_root, proof_type)
+SELECT 'multiverse-issuance', 'issuance'
+WHERE EXISTS (
+    SELECT 1 FROM mssmt_roots WHERE namespace = 'multiverse-issuance'
+) ON CONFLICT DO NOTHING;
+
+INSERT INTO multiverse_roots (namespace_root, proof_type)
+SELECT 'multiverse-transfer', 'transfer'
+WHERE EXISTS (
+    SELECT 1 FROM mssmt_roots WHERE namespace = 'multiverse-transfer'
+) ON CONFLICT DO NOTHING;
+
+-- And now we create the multiverse_leaves entries for the multiverse roots.
+-- This is a no-op if the multiverse root doesn't exist yet.
+INSERT INTO multiverse_leaves (
+    multiverse_root_id, asset_id, group_key, leaf_node_key, leaf_node_namespace
+) SELECT
+      (SELECT id from multiverse_roots mr where mr.namespace_root = 'multiverse-issuance'),
+      CASE WHEN ur.group_key IS NULL THEN ur.asset_id ELSE NULL END,
+      ur.group_key,
+      -- UNHEX() only exists in SQLite and it doesn't take a second argument
+      -- (the 'hex' part). But it also doesn't complain about it, so we can
+      -- leave it in for the Postgres version which is replaced in-memory to
+      -- DECODE() which needs the 'hex' argument.
+      UNHEX(REPLACE(ur.namespace_root, 'issuance-', ''), 'hex'),
+      ur.namespace_root
+FROM universe_roots ur
+WHERE ur.namespace_root LIKE 'issuance-%'
+ON CONFLICT DO NOTHING;
+
+INSERT INTO multiverse_leaves (
+    multiverse_root_id, asset_id, group_key, leaf_node_key, leaf_node_namespace
+) SELECT
+      (SELECT id from multiverse_roots mr where mr.namespace_root = 'multiverse-transfer'),
+      CASE WHEN ur.group_key IS NULL THEN ur.asset_id ELSE NULL END,
+      ur.group_key,
+      -- UNHEX() only exists in SQLite and it doesn't take a second argument
+      -- (the 'hex' part). But it also doesn't complain about it, so we can
+      -- leave it in for the Postgres version which is replaced in-memory to
+      -- DECODE() which needs the 'hex' argument.
+      UNHEX(REPLACE(ur.namespace_root, 'transfer-', ''), 'hex'),
+      ur.namespace_root
+FROM universe_roots ur
+WHERE ur.namespace_root LIKE 'transfer-%'
+ON CONFLICT DO NOTHING;