# Proposal for adding pairs in Money On Chain Decentralized Oracles (OMOC) **URL:** \ **Category:** MOC Improvement Proposals\ **Created:** [August 1, 2024, 8:21pm UTC](https://forum.moneyonchain.com/t/proposal-for-adding-pairs-in-money-on-chain-decentralized-oracles-omoc/393 "2024-08-01T20:21:19Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![rick\_c-137](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.moneyonchain.com/rick_c-137/32/173_2.png) [@rick\_c-137](https://forum.moneyonchain.com/u/rick_c-137)\ **Post date:** [August 1, 2024, 8:21pm UTC](https://forum.moneyonchain.com/t/proposal-for-adding-pairs-in-money-on-chain-decentralized-oracles-omoc/393/1 "2024-08-01T20:21:19Z")
## Introduction The proposal contemplates adding the `USD/COP`, `USD/ARS`, and `RIF/USD` pairs to the [decentralized oracle protocol](https://moneyonchain.com/blog/omocs-are-feeding-the-stablecoin-protocol/), giving the option to protocols that need to use these pairs. ## Proposal details This proposal has as its initial objective the incorporation of `USD/COP`, `USD/ARS` pairs to the _Money on Chain Decentralized Oracle Protocol (OMOC)_. These pairs will provide an oracle solution to protocols that require them such as [Flipmoney](https://flipmoney.io/), a new protocol running over the Rootstock network, which chose _Money On Chain Decentralized Oracles_ to report prices, opening new opportunities for MOC Holders. It is important to note that, if the proposal is approved, the decentralized Oracles for Flipmoney will be the same Money On Chain oracles that will publish more prices. This means that the MOC node operators themselves will publish the price of the pairs needed by Flipmoney, with the latter paying back to the Oracles Node operators. ## Benefits for the MOC Holders Community 1. **Ecosystem expansion** : The addition of new peers attracts projects that need these prices, increasing the adoption of the OMOC protocol. MOC tokens will be required to pay back oracles, which increases their demand. 2. **New revenue opportunities** : Node operators will be able to subscribe to these new pairs and provide pricing data, earning additional revenue through incentives deposited by projects, which will also be received in MOC tokens. 3. **Zero cost for the protocol and optional for OMOC Node Operators** : The addition of these pairs does not generate additional costs for the decentralized oracle protocol nor for the Money on Chain protocol, representing an efficient and cost-effective solution to expand the functionality of the protocol. For OMOC Node Operators, it is optional to subscribe to the new price pairs. ## Incentives Projects that choose to adopt and support these pairs will be able to deposit the MOC token as an incentive in the contract corresponding to each pair, every month. ## Node Operators Operators may choose to subscribe to these new pairs and contribute to the price feed, receiving revenues provided by the protocols. ## Adding Procedure To add these pairs, new currency pair contracts must be deployed and make a change to the protocol registry. This requires community approval of the proposal through the governance process and a voting process. ## Implementation details - Proposed Pairs: USD/COP, USD/ARS. - Additional Pairs: RIF/USD. The RIF/USD pair will be enabled in the implementation so that the Rif On Chain protocol can opt to use decentralized oracles in the future. ## Technical procedure to aggregate the pairs > ⚠ Warning: some technical/coding knowledge is necessary to fully understand this document. In order to add these pairs, the new coinpair contracts must be deployed. The proxy contracts of the new coinpair end up pointing to the implementation that is already shared with the current productive coinpair, ergo the logic does not change and the contracts do not require a new audit. Then a change in the protocol registry is necessary to add these pairs. For this it will be necessary to run a contract change that must go through the voting process. ### The contracts of the new coin pairs would be: | Name | Pair | Type | Address¹ | | --- | --- | --- | --- | | `CoinPairPrice` | `RIF/USD` | Proxy | [`0xaFb1B8…B727A4`](https://explorer.rootstock.io/address/0xaFb1B8C320ACc776c1279bcDB24Ab8F84aB727A4?__ctab=Code) | | `CoinPairPrice` | `RIF/USD` | Implementation | [`0x486324…A6e963`](https://explorer.rootstock.io/address/0x4863244D2B5F2c79d74b5426959d78c3E7A6e963?__ctab=Code) | | `CoinPairPriceFree` | `RIF/USD` | Proxy | [`0x800B58…b2b076`](https://explorer.rootstock.io/address/0x800B589EFBC926C01cDa5BDf7cf12d5dB7b2b076?__ctab=Code) | | `CoinPairPriceFree` | `RIF/USD` | Implementation | [`0xE1C220…02DAE2`](https://explorer.rootstock.io/address/0xE1C2205dC6429512E88859114392540cC802DAE2?__ctab=Code) | | `CoinPairPrice` | `USD/ARS` | Proxy | [`0x44E100…F04393`](https://explorer.rootstock.io/address/0x44E100CC6B4b89EfFF71e0c88048166732F04393?__ctab=Code) | | `CoinPairPrice` | `USD/ARS` | Implementation | [`0x486324…A6e963`](https://explorer.rootstock.io/address/0x4863244D2B5F2c79d74b5426959d78c3E7A6e963?__ctab=Code) | | `CoinPairPriceFree` | `USD/ARS` | Proxy | [`0x214222…d091BD`](https://explorer.rootstock.io/address/0x2142228f2d907DDd443BB5F47a81dA611fd091BD?__ctab=Code) | | `CoinPairPriceFree` | `USD/ARS` | Implementation | [`0xE1C220…02DAE2`](https://explorer.rootstock.io/address/0xE1C2205dC6429512E88859114392540cC802DAE2?__ctab=Code) | | `CoinPairPrice` | `USD/COP` | Proxy | [`0xdD711A…8f166b`](https://explorer.rootstock.io/address/0xdD711A0EB1CbdF7F5287C5CA67E0E9d0288f166b?__ctab=Code) | | `CoinPairPrice` | `USD/COP` | Implementation | [`0x486324…A6e963`](https://explorer.rootstock.io/address/0x4863244D2B5F2c79d74b5426959d78c3E7A6e963?__ctab=Code) | | `CoinPairPriceFree` | `USD/COP` | Proxy | [`0xD3872f…96786e`](https://explorer.rootstock.io/address/0xD3872fEE8B5F3070C67A138Ef6aC710B7196786e?__ctab=Code) | | `CoinPairPriceFree` | `USD/COP` | Implementation | [`0xE1C220…02DAE2`](https://explorer.rootstock.io/address/0xE1C2205dC6429512E88859114392540cC802DAE2?__ctab=Code) | ¹ The contract address links point to the verified codes in the RSK explorer. ### The changer contract to vote would be: | Name | Address¹ | | --- | --- | | `OracleManagerPairChangeListWL` | [`0x6a2519…006bFf`](https://explorer.rootstock.io/address/0x6a251930787fdD06B7BA9e7dd9d4dF8dcB006bFf?__ctab=Code) | ¹ The contract address links point to the verified codes in the RSK explorer. ---
**Author:** ![Manu](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.moneyonchain.com/manu/32/36_2.png) [@Manu](https://forum.moneyonchain.com/u/Manu)\ **Post date:** [August 2, 2024, 3:37pm UTC](https://forum.moneyonchain.com/t/proposal-for-adding-pairs-in-money-on-chain-decentralized-oracles-omoc/393/2 "2024-08-02T15:37:57Z")
Muy buena propuesta! ---
**Author:** ![jbokser](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.moneyonchain.com/jbokser/32/228_2.png) [@jbokser](https://forum.moneyonchain.com/u/jbokser)\ **Post date:** [August 5, 2024, 12:46pm UTC](https://forum.moneyonchain.com/t/proposal-for-adding-pairs-in-money-on-chain-decentralized-oracles-omoc/393/3 "2024-08-05T12:46:19Z")
📣 **Call to MOC holders** : [This proposal](https://forum.moneyonchain.com/t/proposal-for-adding-pairs-in-money-on-chain-decentralized-oracles-omoc/393) is being voted on. [How to vote Tutorial](https://moneyonchain.com/blog/tutorial-how-to-vote-in-money-on-chain-governance/). 📣 **Llamado a los MOC holders** : [Esta propuesta](https://forum.moneyonchain.com/t/proposal-for-adding-pairs-in-money-on-chain-decentralized-oracles-omoc/393) se está votando. [Tutorial de cómo votar](https://moneyonchain.com/es/blog/tutorial-votar-gobernanza-money-on-chain/). ---
**Author:** ![jbokser](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.moneyonchain.com/jbokser/32/228_2.png) [@jbokser](https://forum.moneyonchain.com/u/jbokser)\ **Post date:** [August 13, 2024, 1:46pm UTC](https://forum.moneyonchain.com/t/proposal-for-adding-pairs-in-money-on-chain-decentralized-oracles-omoc/393/4 "2024-08-13T13:46:44Z")
📣 The voting process is over: - 27.73% of the MOC tokens total supply participated in the vote. - 100% of the participants voted in favor. - No one voted against the proposal. - The change was successfully implemented