Immutable Component Config (SRC-107)

[ericnordelo]

Discussion:

https://community.starknet.io/t/immutable-component-config/114434

Abstract

This standard proposes a mechanism to allow setting components’ configurable constants in the implementing contracts
without needing to save them in storage. Component providers can leverage this standard to make them configurable while
keeping the constants hardcoded in the bytecode, removing the extra storage reads required if storage were to be used for
this matter.

SNIP number

I followed the PR number pattern to assign 107.

[github-actions]

There hasn't been any activity on this pull request recently, and in order to prioritize active work, it has been marked as stale.
This PR will be closed and locked in 7 days if no further activity occurs.
Thank you for your contributions!

[ericnordelo]

@amanusk If I recall correctly you are also a maintainer of this repo now? tagging you for review in case that is correct. cc @ArielElp

[leo-starkware]

Hey @ericnordelo can you add the mandatory section "Rationale" (IMO you could simply rename the section "Motivation" which is optional) and "Security considerations"?
Also tagging @ArielElp in case there are comments to address before merging to main

[ericnordelo]

Hey @leo-starkware, sorry for the delay. Updates applied!

[leo-starkware]

Can you change the file name to "snip-23", as well as in line 2 "snip: 23". After that let's merge

[ericnordelo]

What is the rationale behind the 23? It is not easier to track SNIPs by the PR number (like EIPs) so they can be safely referenced when they are drafts? We are also already referencing this in the library as SRC-107.