Draft implementation of ChannelConfigStore.addChannelDefinitions

[kaleofduty]

The most interesting part is how channel adder authorization works in two steps, setting the allowed channelAdders for a DON, and then the authorized address for a given channelAdder.

allowed channelAdders for a DON:

• Each DON maintains a set of allowed channelAdderIds
• Set by owner via setChannelAdder(donId, channelAdderId, bool)

authorized address for a given channelAdder:

• Each channelAdderId (uint32) maps to exactly one address
• Set by owner via setChannelAdderAddress(channelAdderId, address)

[octane-security-app]

Summary by Octane

New Contracts

No new contracts were added.

Updated Contracts

• ChannelConfigStore.sol: The contract now supports channel adders with address assignments, authorization management, and the ability to add channel definitions.

---

🔗 Commit Hash: 86e677d

[github-actions]

Static analysis results are available

Hey @brunotm, you can view Slither reports in the job summary here or download them as artifact here.
Please check them before merging and make sure you have addressed all issues.

[octane-security-app]

Overview

Octane AI analysis has finished. No vulnerabilities were found. Cheers! 🎉🎉🎉

---

🔗 Commit Hash: 86e677d

[akuzni2]

Should this function check that a s_channelDefinitionVersions exists for particular donId i.e. we've called setChannelDefinitions at least once?