**Security flag — dropping caveman for this.**
The source document contains live private keys and mnemonic seed phrases. The document’s own header warns: *”Never commit this file to git”* and *”Delete this file from your computer once you have saved the keys safely.”*
A podcast script is a shareable, recordable artifact. Including those values — even paraphrased — defeats the warning entirely. The script below describes the *structure and purpose* of the credentials without reproducing any actual key values or seed phrases. Confirm this is the intent before distributing.
—
Welcome to the NZRT Wiki Podcast. Today we’re looking at Iteasel Safe Multisig — Signer Wallets.
If you’re working on the Iteasel project, this is one of the most security-sensitive pieces of documentation you’ll come across. Let’s walk through what it covers and what you need to know.
First, the big picture. Iteasel uses a Gnosis Safe multisig wallet. That’s a type of smart contract wallet on the blockchain that requires more than one person to sign off before any transaction goes through. Think of it like a joint bank account where you need multiple signatures before money can move.
The specific setup here is a two-of-three configuration. Three wallets are registered as authorised signers, but any two of them working together is enough to approve a transaction. You don’t need all three — just any two. This protects against a single point of failure. If one signer’s wallet is lost or compromised, funds can’t be moved unilaterally, but the other two can still operate the safe together.
Now let’s look at the three signers. The first is called the Deployer wallet. This is an existing wallet, and its private key is already stored in the deployment environment file, so you don’t need to manage it separately through this document.
The second and third signers were freshly generated for this setup. Each one has three pieces of information associated with it: a public wallet address, a private key, and a mnemonic seed phrase. The public address is safe to share — it’s just how the blockchain identifies that wallet. The private key and the mnemonic, however, are extremely sensitive. Whoever holds either of those has full control of that wallet. These must be stored securely offline — in a password manager or on a hardware wallet — and this file should be deleted from your machine once you’ve saved the credentials safely. Never commit this file to a git repository.
To import either of these generated wallets into MetaMask, you can use the private key or the mnemonic seed phrase — both work, and they represent exactly the same wallet. On testnet, using a software wallet like MetaMask is acceptable for development. But the documentation is explicit on one point: when you move to mainnet, you must use a hardware wallet, such as a Ledger or Trezor. Do not reuse the testnet keys on mainnet. Generate fresh keys on a hardware device instead.
On the network side, this Safe is configured for two environments. Testing happens on Base Sepolia, which is the test network for the Base blockchain. Production will run on Base Mainnet.
So here’s a quick summary of what you need to remember. You have a two-of-three multisig safe, meaning any two of the three signers can approve transactions. The first signer’s key is already in your deployment config. The second and third are newly generated and need to be imported manually. The safe runs on Base Sepolia for testing and Base Mainnet for production. And all private keys and seed phrases must be stored offline and securely — never in version control, never in a shared document, never in a podcast script.
If you’re setting this up for the first time, your action items are: save the private keys and mnemonics to a secure offline store, import the wallets into MetaMask using those credentials, create the Safe on the relevant network with all three signer addresses and the two-of-three threshold configured, and then delete the credentials file from your local machine.
That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.