Cross-chain Payments Integration

[gnomadic]

Job to be Done When launching challenges, Sponsors want the ability to fund the reward pool with non-protocol (Polygon) chain tokens, so they can reward analysts in cross-chain tokens such as NEAR, OSMO etc. and drive growth and adoption of various ecosystems.

Requirements

• Cross-chain payments - Fireblocks supported and Custom: https://docs.google.com/spreadsheets/d/10MpeLprURABMgmlqLGCf8O9eMCGJa9ad50udscLeWdE/edit#gid=1982506656
• Cross-chain payments - IOU Center
• iouToken backing token reserves validation - Don’t issue tokens we don’t have in the treasury
• Cross-chain payout addresses - https://docs.google.com/spreadsheets/d/10MpeLprURABMgmlqLGCf8O9eMCGJa9ad50udscLeWdE/edit#gid=1695826304

Notes

• See design specs linked below
• iouToken Metadata: https://docs.google.com/document/d/1IIRgTIEH31BpfUlLSSXGgfSXe-47BTfKw6Wn_h6nq-4/edit

Dependent on

• Protocol dev: https://github.com/orgs/FlipsideCrypto/projects/9/views/1?pane=issue&itemId=20222968
• Can find the repository for IOUs along with tests for each functioning piece https://github.com/FlipsideCrypto/iou
• all abis can be found here: https://github.com/FlipsideCrypto/iou/tree/master/abis
• To note here, if you use IOU.sol then it will include the interface for the IOU metadata needed as well as the ERC20 balance interface in one so that you don't have to do those things separately: https://github.com/FlipsideCrypto/iou/blob/master/abis/IOU.json
• Treasury dev: https://github.com/FlipsideCrypto/treasury/pull/212#

Designs

• Dev ready: https://www.figma.com/file/66Myyf1MVmY8UKv7BrVUa5/MDAO-App-Designs?node-id=2430%3A50812&t=0atwLL0zvpVP7v6v-0

[elisemarika]

@sebruiz fyi I updated the requirements (description) with links to allowlists to clarify exact pTokens and payout addresses needed for each token/chain

[nftchance]

Status Update:

Had a meeting with the Payments team detailing the final needs of protocol:payments system, and we are almost home free. In the final phase of:

• confirming signature shape
• payment team getting deployed tokens through factory
• deploy examples for payment team to use as seed data in testing

The current timeline is to finalize payment and protocol needs (noted above) in the next days and begin integration preparation between omkar and seb early next week!

[omkarb]

I'll grab some time with Seb early next week, but posting here for viz as well.

We have three endpoints:

1. To request validation to mint a specific endpoint treasury-listeners-pine.clusters-stg.flipside.kitchen/ioutoken/request-mint
2. To request metadata about a specific asset treasury-listeners-pine.clusters-stg.flipside.kitchen/ioutoken/metadata/Ethereum/ETH
3. To request metadata for all assets: treasury-listeners-pine.clusters-stg.flipside.kitchen/ioutoken/metadata

These are documented in the Postman collection under Treasury/IOU tokens as well.

[anthonyjoeseph]

👆🏻 Just a note to use the mdao [staging] environment in Postman!

[elisemarika]

@sebruiz let's make sure the iouCenter is also up to date for the latest since we had to add a couple new fields cc @drakedanner

• prod: https://metricsdao.xyz/app/ioucenter
• Figma: https://www.figma.com/file/66Myyf1MVmY8UKv7BrVUa5/MDAO-App-Designs?node-id=2430-50812&t=3i0evD8Rbr4YH0B1-0

[elisemarika]

5/3/23 next steps @sebruiz @termaatFlipside

• add chains incremently to wallet management page, with validation of entered address per chain, with input from GJ and AAron << will start with one Fireblocks supported chain
• scope out iouCenter, scope out scripts as a workaround for iouCenter if we have to go fast -
• claims as experiational need to be prominately displayed in the UX, using enforcement Expiration data.
• Fixing Data connectivity issue
• UX rough edges