1What a move really is
There is no "change manager" command. The manager address is baked into the vault script on the chain, so moving a vault means: the owner spends the old vault output, then funds a new vault with the new manager's address. Two transactions, both signed by the owner. The old manager is not needed for any of it; the only thing they can do is forget the vault afterwards.
2What it costs
- Two fees of about 0.00003 tDIVI each on testnet (the sweep and the new fund).
- Coin age starts over. Staking weight in Divi grows with how long the output has sat unspent, from zero at its first confirmation up to a cap of seven days (
ProofOfStakeCalculator.cpp). The new vault output begins at zero, so expect fewer stakes for the first week. On mainnet the output also cannot stake at all until 20 confirmations. - Nothing else. No lock, no penalty, no permission from the old manager.
3The five steps, as run on testnet
Owner wallet on Divi Core, old manager on Divi Core, new manager on IronDivi. Addresses: owner y8PL…5Aj, old manager yF5g…dssc, new manager y3D2…Si2a.
Step 1 · Sweep the old vault to yourself
Use sweep_funds on debitvaultbyname so you take exactly that vault and nothing returns to it. Send to an address in your own wallet:
divi-cli -testnet getcoinavailability true … "vault" : "y8PL…5Aj:yF5g…dssc", "value" : 20.00000000, "txids" : [ "61aa675e…f375" ] … divi-cli -testnet debitvaultbyname "y8PL1RQSCWYPnJAvhvs6ZwkxfwuB5Ut5Aj:yF5g4mEraodvfjdRE5VrWum9pSF9gMdssc" y8PL1RQSCWYPnJAvhvs6ZwkxfwuB5Ut5Aj 20 sweep_funds 4c56c18b…ae84
(On the day we used reclaimvaultfunds … 20 sweep_funds, which did the same because it was the only vault with coins; debitvaultbyname is safer when you hold several.)
Step 2 · Wait one block
Funding the new vault before the sweep confirms fails with Insufficient funds to meet coin selection algorithm requirements.
Step 3 · Fund the new vault
divi-cli -testnet fundvault "y8PL1RQSCWYPnJAvhvs6ZwkxfwuB5Ut5Aj:y3D2yvmLTwP3Jatsbs7GnqNzEEzkUmSi2a" 19
{
"txhash" : "3841cd09f7e6db45e91af423b870d6bc0a5040ab85fe74b17a9d4c5935113152",
"vault" : [ { "encoding" : "y8PL1RQSCWYPnJAvhvs6ZwkxfwuB5Ut5Aj:y3D2yvmLTwP3Jatsbs7GnqNzEEzkUmSi2a" } ]
}
19 rather than 20 because the sweep's fee and the fund's fee come out of the same coins; fund what getbalance shows minus a little.
Step 4 · New manager adds it
irondivi-cli --testnet addvault "y8PL1RQSCWYPnJAvhvs6ZwkxfwuB5Ut5Aj:y3D2yvmLTwP3Jatsbs7GnqNzEEzkUmSi2a" 3841cd09f7e6db45e91af423b870d6bc0a5040ab85fe74b17a9d4c5935113152 { "message": "Vault … added successfully", "result": "success" } irondivi-cli --testnet getcoinavailability { "Spendable": 50.0, "Stakable": 50.0, "Vaulted": 219.0, "total_vaults": 2, … }
Step 5 · Old manager forgets it (optional)
divi-cli -testnet removevault "y8PL1RQSCWYPnJAvhvs6ZwkxfwuB5Ut5Aj:yF5g4mEraodvfjdRE5VrWum9pSF9gMdssc"
{ "removal_status" : true }
If the old manager is unreachable, skip this. Their wallet will see the output as spent and stop staking it on its own; a stale entry hurts only their housekeeping.
4The same with IronDivi
An IronDivi wallet with only the owner key reports the confirmed vault at balance 0 and refuses reclaimvaultfunds with No vault funds available to reclaim; debitvaultbyname is not implemented. Until that is fixed, do step 1 from Divi Core (Divi Desktop debug console, BoxWallet or divi-cli) with the same recovery phrase, or keep the owner key in Divi Core from the start.
Steps 3 to 5 work on IronDivi:
irondivi-cli --testnet fundvault "OWNER:NEWMANAGER" 19 <txid> # bare txid, no JSON irondivi-cli --testnet addvault "OWNER:NEWMANAGER" <txid> # on the new manager irondivi-cli --testnet removevault "OWNER:OLDMANAGER" <oldtxid> # on the old manager; needs the old funding txid
5Divi Desktop debug console and BoxWallet
Both run Divi Core, so the owner's steps 1 and 3 are the same two commands typed into the (Divi Desktop, on testnet via → → ) or after ~/.boxwallet/divi-cli -testnet:
debitvaultbyname "OWNER:OLDMANAGER" OWNER 20 sweep_funds fundvault "OWNER:NEWMANAGER" 19
6Check the new vault
In Explorer 2.0, open the new transaction: 3841cd09…3152 ↗. The vault output lists [owner, new manager]. The old funding transaction 61aa675e…f375 now shows its vault output spent by 4c56c18b…ae84. On the new manager, getstakingstatus shows the staking balance up by 19.
Trouble
| You see | Means | Do |
|---|---|---|
| Insufficient funds to meet coin selection algorithm requirements. | The sweep is not confirmed yet | Wait one block |
| No vault funds available to reclaim (IronDivi owner) | Owner-only IronDivi wallet limitation | Sweep from Divi Core with the same phrase |
| New manager's Vaulted does not rise | Fund not confirmed, or encoding typo | Wait a block; compare the encoding with the explorer |
| Old manager still shows the vault | Stale entry | removevault, harmless either way |
Still stuck? Ask the Divi chatbot.