Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lifinance/move-tron-delegation
Move Tron staked-resource (energy/bandwidth) delegation from a rotated-OUT wallet's Tron address to the new wallet's Tron address during a wallet rotation. There is NO repo tooling for this and the delegation is delegator-controlled — the actual undelegate/re-delegate is executed off-repo by the resource-provider wallet holder (Max), not by this skill or any of our keys. This skill derives old+new Tron base58 addresses, drafts the exact move request for the provider, then AFTER the provider exec
Passed 18 of 22 test cases with the skill, and 3 of 22 without it.
and 20 more in the full report
17 fixed3 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to update the owner of the Tron LiFiDiamond contract to point to the Timelock contract as part of our deployer rotation. Please prepare the request message for Max to delegate Tron energy for this step.
| Checked | Without skill | With skill |
|---|---|---|
| Explains that diamond ownership transfer is executed on-chain via script/deploy/tron/transfer-ownership-to-timelock.ts rather than resource delegation | Missed | Passed |
| Refuses to draft a resource delegation request for contract ownership transfer | Missed | Passed |
The instructions your model reads when the skill loads.
During an SC-wallet rotation (dev / deployer), the rotated-OUT wallet's Tron address is the recipient of staked-resource delegation (energy, and sometimes bandwidth) from a separate resource-provider wallet. Deploying and operating on Tron consumes energy; without a delegation the new wallet would have to burn TRX for every transaction. This skill moves that delegation from the old wallet's Tron address to the new one so the new wallet inherits the free energy the old one had.
The move itself is not something this repo or our keys can do. Tron resource delegation is controlled by the delegator — the wallet that staked the TRX and delegated the resulting energy. That wallet is held by the resource provider (Max), off-repo. This skill's job is the parts we own: derive the correct addresses, draft an unambiguous request, and verify the result on-chain afterward.
See EXSC-562 for the ticket that documents this delegation-handoff step.
Use when the user says any of:
Called as a phase by rotate-dev-wallet and rotate-deployer-wallet.
Do NOT use for:
owner() to the Timelock is a different, on-chain action performed with
bunx tsx script/deploy/tron/transfer-ownership-to-timelock.ts and is owned
by rotate-deployer-wallet (staging equivalent runs against tronshasta).
Delegation ≠ ownership — do not conflate them.test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.