<h1><strong>Overview</strong></h1>
<p>The <a href="https://github.com/paulmillr/micro-sr25519">micro-sr25519 package</a> developed by Paul Miller as an extension to @noble/curves to support the Polkadot ecosystem is now ready for the auditing phase. For this phase, Paul suggested to go with a new firm other than the Cure53 as most of his work is audited by Cure53. So we (Edgetributor SubDAO) explored multiple auditing firms for the last couple of weeks and selected 3 firms for the final evaluation. We then reviewed the scopes and offerings of those 3 firms based on the backgrounds of the auditing researchers they offered, their experience, stack familiarity and total number of researchers proposed in the scope, Polkadot ecosystem familiarity, low level JS/TS experience and cryptographic curves familiarity. Oak Security firm is the one which turned out to be superior compared to the other offerings in this specific case. (If anyone wants to know more about other firms or their offerings, feel free to reach us out on twitter.)</p>
<p>Previously approved development proposal: <a href="https://polkadot.polkassembly.io/referenda/1165">https://polkadot.polkassembly.io/referenda/1165</a></p>
<p>&nbsp;</p>
<h1><strong>Audit TL;DR:</strong></h1>
<ul>
<li>Type: Premium Security Audit</li>
<li>Cost per week for Audit: 44000 USD</li>
<li>Cost per week for Fuzzing: 10000 USD</li>
<li>Scope length: 0.6 week for audit, 0.8 week for fuzzing</li>
<li>Total cost: 34400 USD</li>
<li>No. of researchers involved: 5</li>
<li>Requested payment mode: USDC on Ethereum</li>
</ul>
<p>Detailed audit proposal:&nbsp;<a href="https://drive.google.com/file/d/1rdOtoEtgHXrJxX3lPu1khv8deEOcwKz3/view?usp=sharing">https://drive.google.com/file/d/1rdOtoEtgHXrJxX3lPu1khv8deEOcwKz3/view?usp=sharing</a></p>
<p>&nbsp;</p>
<h1><strong>About Paul Miller</strong></h1>
<p><a href="https://github.com/paulmillr">Paul</a> is the founding developer behind <strong>@noble packages</strong> which are used by different web3 ecosystems. He is well known for his contributions via <a href="https://github.com/paulmillr/noble-curves">@noble/curves</a> and <a href="https://github.com/paulmillr/noble-hashes">@noble/hashes</a> packages which are directly/indirectly being used by the majority of the modern web3 protocols/toolings/platforms which includes even the forum you&rsquo;re currently reading this proposal on!</p>
<p>&nbsp;</p>
<h1><strong>About Oak Security</strong></h1>
<p><a href="https://www.oaksecurity.io/">Oak Security GmbH</a> provides security services in the web3 space, such as threat modeling, penetration testing, security audits, and fuzz testing while following a multidisciplinary approach in their services.<br />Based in Munich but operating worldwide, they currently use a pool of 52 highly qualified security engineers and researchers. They operate under two brands: The Solidified brand focuses on EVM-based blockchains, while Oak Security caters to a wider blockchain ecosystem, with departments focusing on the security of Rust and Go source code, low-level protocol security, and infrastructure security, which goes beyond the realm of traditional smart contract security.</p>
<p>&nbsp;</p>
<h1><strong>Importance</strong></h1>
<p>Although many of the Polkadot ecosystem tools/products already started adopting the micro-sr25519 package, Paul Miller himself advocated to get the package audited before using it in any production deployments. Currently there is an open <a href="https://github.com/polkadot-js/common/pull/1971">pull request to switch from @polkadot/wasm-crypto to micro-sr25519 package in PolkadotJS suite</a> for ecosystem-wide security and performance benefits.</p>
<p>&nbsp;</p>
<h1><strong>Edgetributor SubDAO&rsquo;s role</strong></h1>
<p>What started as a quest to have the development of a missing component required for our project, have come a long way to benefit the whole Polkadot ecosystem. Edgetributor SubDAO as the curator of this proposal will be representing Oak Security in OpenGov and in other operational duties. Edgetributor SubDAO will be responsible for the custody of the USDC (in a multisig) which needs to be disbursed to the Oak Security in two mentioned phases. Oak Security also requires a legal entity to sign the contract and for the same purpose Edgetributor SubDAO will utilise the legal entity of Edgeware DAO Association (Swiss Association) to save the costs and time required to involve PCF.<br />The entire amount corresponding to this proposal (except the refundable bridging buffer) will be going to the auditing entity Oak Security. In this whole process, Edgetributor SubDAO or Edgeware DAO or any Edgeware contributors are not getting financially benefited by any means. We are interested in exploring the BD bounty for our time and efforts contributed so far, especially for the screening of the auditing firms, comparative analysis of their offerings and follow-ups.</p>
<p>&nbsp;</p>
<h1><strong>Budget and Timeline</strong></h1>
<p><strong>Budget distribution:</strong></p>
<ul>
<li>Requested amount: 34400 USDC</li>
<li>Refundable bridging buffer: 100 USDC (to Swap USDC AssetHub to USDC Warmhole on Hydration and then bridge further to Oak Security&rsquo;s address on Ethereum.)</li>
</ul>
<p><strong>Notable terms:</strong></p>
<ul>
<li>50% (17200 USDC) will be disbursed at the start of the audit.</li>
<li>The other 50% (17200 USDC) will be disbursed on receipt of the initial audit report.</li>
<li>The Remaining amount from the refundable bridging buffer will be sent back to the treasury.</li>
</ul>
<p><strong>Total:</strong> 34500 USDC</p>
<p><strong>Multisig:</strong> 14XNJmoUzkvmh9cYoqG4axBRR4BWzWRbnFP79oiZgKu7V9bz</p>

**Overview**
============

The [micro-sr25519 package](https://github.com/paulmillr/micro-sr25519) developed by Paul Miller as an extension to @noble/curves to support the Polkadot ecosystem is now ready for the auditing phase. For this phase, Paul suggested to go with a new firm other than the Cure53 as most of his work is audited by Cure53. So we (Edgetributor SubDAO) explored multiple auditing firms for the last couple of weeks and selected 3 firms for the final evaluation. We then reviewed the scopes and offerings of those 3 firms based on the backgrounds of the auditing researchers they offered, their experience, stack familiarity and total number of researchers proposed in the scope, Polkadot ecosystem familiarity, low level JS/TS experience and cryptographic curves familiarity. Oak Security firm is the one which turned out to be superior compared to the other offerings in this specific case. (If anyone wants to know more about other firms or their offerings, feel free to reach us out on twitter.)

Previously approved development proposal: [https://polkadot.polkassembly.io/referenda/1165](https://polkadot.polkassembly.io/referenda/1165)

**Audit TL;DR:**
================

*   Type: Premium Security Audit
*   Cost per week for Audit: 44000 USD
*   Cost per week for Fuzzing: 10000 USD
*   Scope length: 0.6 week for audit, 0.8 week for fuzzing
*   Total cost: 34400 USD
*   No. of researchers involved: 5
*   Requested payment mode: USDC on Ethereum

Detailed audit proposal: [https://drive.google.com/file/d/1rdOtoEtgHXrJxX3lPu1khv8deEOcwKz3/view?usp=sharing](https://drive.google.com/file/d/1rdOtoEtgHXrJxX3lPu1khv8deEOcwKz3/view?usp=sharing)

**About Paul Miller**
=====================

[Paul](https://github.com/paulmillr) is the founding developer behind **@noble packages** which are used by different web3 ecosystems. He is well known for his contributions via [@noble/curves](https://github.com/paulmillr/noble-curves) and [@noble/hashes](https://github.com/paulmillr/noble-hashes) packages which are directly/indirectly being used by the majority of the modern web3 protocols/toolings/platforms which includes even the forum you’re currently reading this proposal on!

**About Oak Security**
======================

[Oak Security GmbH](https://www.oaksecurity.io/) provides security services in the web3 space, such as threat modeling, penetration testing, security audits, and fuzz testing while following a multidisciplinary approach in their services.  
Based in Munich but operating worldwide, they currently use a pool of 52 highly qualified security engineers and researchers. They operate under two brands: The Solidified brand focuses on EVM-based blockchains, while Oak Security caters to a wider blockchain ecosystem, with departments focusing on the security of Rust and Go source code, low-level protocol security, and infrastructure security, which goes beyond the realm of traditional smart contract security.

**Importance**
==============

Although many of the Polkadot ecosystem tools/products already started adopting the micro-sr25519 package, Paul Miller himself advocated to get the package audited before using it in any production deployments. Currently there is an open [pull request to switch from @polkadot/wasm-crypto to micro-sr25519 package in PolkadotJS suite](https://github.com/polkadot-js/common/pull/1971) for ecosystem-wide security and performance benefits.

**Edgetributor SubDAO’s role**
==============================

What started as a quest to have the development of a missing component required for our project, have come a long way to benefit the whole Polkadot ecosystem. Edgetributor SubDAO as the curator of this proposal will be representing Oak Security in OpenGov and in other operational duties. Edgetributor SubDAO will be responsible for the custody of the USDC (in a multisig) which needs to be disbursed to the Oak Security in two mentioned phases. Oak Security also requires a legal entity to sign the contract and for the same purpose Edgetributor SubDAO will utilise the legal entity of Edgeware DAO Association (Swiss Association) to save the costs and time required to involve PCF.  
The entire amount corresponding to this proposal (except the refundable bridging buffer) will be going to the auditing entity Oak Security. In this whole process, Edgetributor SubDAO or Edgeware DAO or any Edgeware contributors are not getting financially benefited by any means. We are interested in exploring the BD bounty for our time and efforts contributed so far, especially for the screening of the auditing firms, comparative analysis of their offerings and follow-ups.

**Budget and Timeline**
=======================

**Budget distribution:**

*   Requested amount: 34400 USDC
*   Refundable bridging buffer: 100 USDC (to Swap USDC AssetHub to USDC Warmhole on Hydration and then bridge further to Oak Security’s address on Ethereum.)

**Notable terms:**

*   50% (17200 USDC) will be disbursed at the start of the audit.
*   The other 50% (17200 USDC) will be disbursed on receipt of the initial audit report.
*   The Remaining amount from the refundable bridging buffer will be sent back to the treasury.

**Total:** 34500 USDC

**Multisig:** 14XNJmoUzkvmh9cYoqG4axBRR4BWzWRbnFP79oiZgKu7V9bz

Audit sponsorship of micro-sr25519 package by Paul Miller (2/2)

Treasury

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

- **Problem Statement:** Selecting a reliable auditing firm for the micro-sr25519 package in the Polkadot ecosystem.
- **Significance:** Ensuring the security and performance benefits of the micro-sr25519 package before widespread adoption in the Polkadot ecosystem.
- **Proposed Solution:** Engaging Oak Security for a Premium Security Audit costing 34400 USD with 5 researchers involved.
- **Expected Outcomes:** Enhanced security and performance of the micro-sr25519 package for the Polkadot ecosystem.

#1520 {Vote Nay, opting PAL bounty} Audit sponsorship of micro-sr25519 package by Paul Miller (2/2)

No Active Proposals