Skip to content
Crypto.world

The Ledger

Sky details DssExecLib v0.1.0 upgrade; integration remains pending

A Sky Forum technical scope details DssExecLib v0.1.0, a library upgrade that moves to Solidity 0.8.16 and changes helpers used in governance spells. The library is deployed, but its integration into spells-mainnet and a related USDS authorization are still pending.

Sky details DssExecLib v0.1.0 upgrade; integration remains pending

A deployed library, awaiting integration

A technical scope posted to Sky’s forum on Nov. 17 details DssExecLib v0.1.0, a library upgrade that changes the code linked by future Sky Protocol Core Spells. Dewiz prepared the document, which says the library is deployed and audited, while the change to the spells-mainnet link remains pending.

DssExecLib provides common operations used in Core Spells, including debt-ceiling changes, rate updates, collateral onboarding and Chainlog management. The scope describes v0.1.0 as a minor-version update intended to align the library with Sky’s current contracts and practices; it says the existing v0.0.9 predates the Solidity 0.8 compiler, the Chief Migration, the SKY launch and other protocol changes.

Changes for spell authors

The update raises the compiler from Solidity 0.6.x to 0.8.16, changes function names and removes helpers associated with retired contracts. The document lists new helpers for USDS and SKY address lookups, savings-rate operations, Chainlog key removal and Star spell execution, among other additions.

It also introduces a three-argument sendPaymentFromSurplusBuffer function, whose first argument specifies the Join adapter used for a payment. That lets spells select the DAI or USDS payment route. The scope says the USDS path requires a one-time Vat authorization for USDS_JOIN before it can be used; without it, the payment path reverts.

Spell authors will need to update existing calls and review changes that may not trigger compiler errors, including the behavior of mkr(). The scope says that in v0.1.0, mkr() resolves the MKR token, whereas the earlier version resolved MCD_GOV, which it identifies as pointing to SKY. It also notes that checkWhitelistedOSM now checks whether an oracle is already whitelisted instead of arranging that whitelisting, which must be done with the oracle provider before the spell is cast.

Checks and limitations

Five existing helpers gain stricter input checks, including a requirement that a liquidation limit cannot be set below an ilk’s minimum vault debt. The scope also warns spell authors to preserve call order when changing liquidation limits and minimum vault amounts for the same ilk, because an intermediate setting that violates the check will revert.

The document identifies ChainSecurity and Cantina reports covering commit 555d1c1; it says Cantina found no issues and ChainSecurity reported no open findings, with one low and three informational findings resolved during its engagement. It says the audit scope excluded spells built with the library and the selection of parameters passed to its functions.

The scope lists known issues and cautions, including that tryExecuteStarSpell can fail while the Core spell succeeds. It also says AutoLine setter calls need a separate exec call for the ilk to apply the configuration.

Integration steps remain open

The scope says the v0.1.0 library was deployed on Sept. 14 at address 0x99933a7b2982Ea2ad3d7e9027Cd034197aA562C2. It reports bytecode checks matched the audited commit and says the library itself has no storage, owner or roles.

Its integration PR, spells-mainnet #579, was still open for review when the scope was posted on Nov. 17; merge was planned at the start of a Core Spell cycle. The one-time Vat authorization of USDS_JOIN is planned for the first Core Spell that links the updated library, after the integration PR is merged.

Sources

  1. Original source Sky Forum forum.skyeco.com

Related stories

Explore

More articles