Currently(before subspaces is live on mainnet), the following behavior is observed.
echo 'andrew@tabconf. 3600 CLASS2 TXT "I went to TABConf 2025"' | space-cli signzone andrew@tabconf
⚠️ Name Error: Malformed name
There needs to be a likewise feature for signing zone files as a subspace handle(identity).
The private key(secret) used to create the certificate request(in nacho.io, submitted to subs) for the handle needs to be provided in order to sign the zone file.
Likely provided as a required option when the spacename is provided as a subspace(andrew@tabconf) instead of a top-level space(@TABConf).
Currently(before subspaces is live on mainnet), the following behavior is observed.
echo 'andrew@tabconf. 3600 CLASS2 TXT "I went to TABConf 2025"' | space-cli signzone andrew@tabconf
⚠️ Name Error: Malformed name
There needs to be a likewise feature for signing zone files as a subspace handle(identity).
The private key(secret) used to create the certificate request(in nacho.io, submitted to subs) for the handle needs to be provided in order to sign the zone file.
Likely provided as a required option when the spacename is provided as a subspace(andrew@tabconf) instead of a top-level space(@TABConf).