Decode Morpho Multicall in type safe way with sol! macros

.cla-signed-users

@@ -4,8 +4,12 @@ andrestielau
 prasanna-anchorage
 hassan-anchor
 francisco-olea-anchor
+guido-peirano-anchor
+diego-rivas-anchor
 # Turnkey
 r-n-o
 # Distributed Lab
 KyrylR
-
+#bots
+#makes the PR
+github-actions[bot]

CONTRIBUTING.md

@@ -0,0 +1,36 @@
+# Contributing
+
+Thank you for your interest in contributing to this project! This document outlines the contribution workflow and guidelines.
+
+## Governance
+
+For details about authority, core team structure, and decision-making, please refer to [GOVERNANCE.md](GOVERNANCE.md).
+
+## How to Contribute
+
+### For Community/Public Contributors
+1. **Fork** the repository
+2. **Create a feature branch** from `main`
+3. **Make your changes** following the code style and practices used in the project
+4. **Sign the Contributor License Agreement (CLA) if this is your first contribution. The CLA check will prompt you with instructions if needed.**
+5. **Submit a Pull Request** with a clear description of your changes
+6. **Wait for Core Team review** - A Core Team member will review and approve your PR before it can be merged
+
+### For Core Team Members
+1. Core Team members can review, approve, and merge PRs from community contributors and other Core Team members
+2. Follow the same PR workflow but with merge authority
+
+## PR Guidelines
+- **Clear description:** Explain what problem your PR solves and how it solves it
+- **Test coverage:** Include tests for new functionality
+- **Code style:** Follow existing code conventions in the repository
+- **One concern per PR:** Keep PRs focused on a single feature or bug fix
+
+## Code Standards
+- Format your code using [rustfmt](https://github.com/rust-lang/rustfmt) by running `make -C src fmt` before submitting
+- Address all linter warnings by running `make -C src lint` and fixing issues
+- Run `make -C src test` to ensure all tests pass before submitting
+- No breaking changes without discussion
+
+## Questions or Issues?
+If you have questions about the contribution process, please reach out to the Core Team through the repository's issue tracker.

GOVERNANCE.md

@@ -0,0 +1,18 @@
+# Governance
+
+## Authority and The Core Team
+
+### Authority
+**Anchorage Digital** retains all rights, title, and interest in the repository. Final decision-making authority rests with the Anchorage Digital internal engineering leadership.
+
+### The Core Team
+The "Core Team" is the only group authorized to merge code, approve pull requests, and manage releases. This team is composed of:
+
+1. **Anchorage Digital Employees:** Internal engineering staff.
+2. **Authorized Partners:** designated representatives from partner organizations (e.g., Turnkey).
+3. **Contractors:** Engineering contractors vetted and authorized by Anchorage Digital.
+
+### Contribution Workflow
+* **Core Team Members:** May review and approve PRs. We currently require at least one Anchorage employee to review and Approve PRs.
+* **Community/Public:** May submit PRs, but they must be approved by a Core Team member. We currently require at least one Anchorage employee to review and Approve PRs. For protocol owners in chains/dapps that we consider in maintenance mode, we want to require 1 Anchorage Employee and 1 Protocol Owner to approve the PR.
+* Note: Being a Partner or Contractor does not grant automatic administrative rights over the repository settings, only code maintenance rights.

SECURITY.md

@@ -0,0 +1,44 @@
+# Security Policy
+
+We take the security of this project seriously. We appreciate your help in disclosing vulnerabilities responsibly and ethically.
+
+## Supported Versions
+
+Only the latest versions of this project are currently supported with security updates. 
+## Reporting a Vulnerability
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+If you have discovered a security vulnerability, we ask that you report it privately to the maintainers.
+
+### Method 1: GitHub Private Reporting (Preferred)
+You can privately report a vulnerability directly on GitHub:
+1. Go to the **Security** tab of this repository.
+2. Click on **Advisories**.
+3. Click **"Report a vulnerability"**.
+
+### Method 2: Email
+If you cannot use the GitHub reporting tool, please email the maintainers at **[security@anchorage.com]**.
+
+## Reporting Guidelines
+
+To help us triage and patch the issue as quickly as possible, please include:
+* A description of the vulnerability.
+* Steps to reproduce the issue (a proof-of-concept code or script is ideal).
+* Any relevant logs or error messages.
+* The version of the software you are running.
+
+## Our Response Policy
+
+After you report a vulnerability, here is what you can expect:
+1.  **Acknowledgement:** We will acknowledge receipt of your report within **[72 hours]**.
+2.  **Assessment:** We will confirm the vulnerability and determine its severity.
+3.  **Fix:** We will work on a patch. We may ask you to verify the fix.
+4.  **Release:** We will release a security update and a public security advisory.
+
+We ask that you maintain confidentiality during this process and do not disclose the vulnerability publicly until a patch has been released.
+
+## Bounty Program
+**[Choose one of the following options and delete the other]**
+
+* **Option A:** We currently **do not** offer a paid bug bounty program.