Contract Meta (SEP-46)

[leighmcculloch]

I've opened a pull request containing a SEP that retroactively captures the existing contract meta capabilities that exist in the Rust soroban-sdk and the stellar-cli:

• SEP-46: Contract Meta #1655

The soroban-sdk and stellar-cli already implement a way that any contract can be attached with meta. The ecosystem is already using this, and other proposals are forming (thanks @orbitlens!) that are using the meta. It would be helpful to document the behavior of the contract meta so that it does not remain as tribal / hidden knowledge, and so that as other contract SDKs are built there is a clear outline of how they can be compatible and seamless as to providing meta.

This meta is already in use by other proposals in flight, such as the following proposal:

• Contract Source Validation SEP #1573

It's not ideal write this SEP retroactively, and this SEP should have been written early as part of and during the soroban development, but here we are, and I think it is valueable to capture this.

(Note that a similar SEP needs writing for contract spec definition as well for the same reasons, and it's on my todo list.)

[leighmcculloch]

This discussion topic has been open for one month. The proposal captures a pre-existing implementation used by all contracts via the Rust Soroban SDK. No one appears to object to documenting it as such. There is one supporting 🚀 — nice choice of emoji — by @orbitlens on the comment above.

I've updated the PR to use SEP-46 as the SEP number.

@tomerweller Could I get a final review and ✅ if you agree with this assessment?

PR:

• SEP-46: Contract Meta #1655

[tomerweller]

It's not ideal write this SEP retroactively

I don't agree with that sentiment. I think that retroactively standardizing something in use makes a perfect sense. Approved and merged.