From 5b72eb15cd43e80ac327278fa833761e8aa0afdd Mon Sep 17 00:00:00 2001 From: Marco Granelli Date: Tue, 24 Dec 2024 16:44:34 +0100 Subject: [PATCH] Adds instructions for offline wrapper signature --- packages/docs/pages/users/fees.mdx | 31 +++++++++++++++++++++++++++++- 1 file changed, 30 insertions(+), 1 deletion(-) diff --git a/packages/docs/pages/users/fees.mdx b/packages/docs/pages/users/fees.mdx index 266e9869..fdaca2fe 100644 --- a/packages/docs/pages/users/fees.mdx +++ b/packages/docs/pages/users/fees.mdx @@ -231,7 +231,7 @@ namadac utils sign-offline \ --output-folder-path tx-dump-dir ``` -You can now pass on the serialized transaction (\*.tx file) and signature (\*.sig) to whoever is going to wrap it. +You can now pass on the serialized transaction (`\*.tx` file) and signature (`\offline_signature_*.sig`) to whoever is going to wrap it. They can then wrap this tx and submit it to the chain with e.g.: @@ -241,3 +241,32 @@ namadac tx \ --signatures signature.sig \ --gas-payer gas-payer-key ``` + +They can also produce the wrapper signature offline if this is required. In this case, instead of the previous command, they should first wrap and dump the tx as follows: + +```shell copy +namadac tx \ + --tx-path transaction.tx \ + --signatures signature.sig \ + --gas-payer gas-payer-key \ + --dump-wrapper-tx \ + --output-folder-path tx-dump-dir +``` + +This will generate a separate serialized transaction (`\*.tx` file). They can then produce the wrapper signature offline: + +```shell copy +namadac utils sign-offline \ + --data-path tx-dump-dir/*.tx \ + --secret-key gas-payer-key \ + --output-folder-path tx-dump-dir +``` + +Which generates a serialized wrapper signature (`\offline_wrapper_signature_*.sig`). Finally they can submit the transaction with: + +```shell copy +namadac tx \ + --tx-path wrapper_transaction.tx \ + --gas-signature wrapper_signature.sig +``` +