Usual Tech Docs
Usual WebsiteGeneral DocsContract DeploymentsAuditsAccess dApp
  • 🚀GM GM
    • Usual Tech Hub
  • 🔭Overview
    • Usual Protocol Primer
    • Features
      • Mint & Redeem Engine
      • USD0
      • USD0++
      • USUAL
      • USUAL*
      • USUALx (USUAL staking)
      • USUAL distribution
      • USUAL Airdrop
      • Usual USD0++ Investment Vault
    • Architecture
      • Role Management
      • USUAL Distribution Model
  • ⛓️Smart Contracts
    • Protocol Contracts
      • DaoCollateral
      • Swapper Engine
      • USUAL staking
      • USUAL* Vested Allocation Staking
      • USUAL Distribution
        • Distribution Module
        • Yield Module
      • Airdrop Module
    • Token Contracts
      • USD0
      • USD0++
      • USUAL
      • USUAL*
      • USUALx
      • Usual USD0++ Investment Vault
        • VaultRouter
    • Utility Contracts
      • ClassicalOracle
      • Abstract Oracle
      • Chainlink Oracles
      • Pyth Oracles
      • RedStone Oracles
    • Real World Assets
      • USYC (by Hashnote)
      • M (by M0)
        • UsualM
      • USDtb
    • Contract Deployments
  • 🛡️Security & Audits
    • Security Practices
    • Testing Framework
    • Monitoring Framework
    • Audits
    • Bug Bounty
  • 🧩Integrations
    • Integrate USD0++
      • Reward redistribution by integration partner
      • Claim Address Redirect
      • Daily Distribution powered by Brevis (coming soon)
  • 📚Resources
    • Community & Support
    • References
  • 📖Support
    • FAQ
    • Glossary
  • ⚖️Legal
    • Terms of Services
    • Legal Notice
    • Privacy Policy
Powered by GitBook
On this page
  • Overview
  • How to request a Claim Address Redirect
  • Detailed Flow

Was this helpful?

  1. Integrations
  2. Integrate USD0++

Claim Address Redirect

PreviousReward redistribution by integration partnerNextDaily Distribution powered by Brevis (coming soon)

Last updated 2 months ago

Was this helpful?

Overview

If an USD0++ integration partners can't by themselves mint and claim the USUAL rewards that accumulate on their smart contract, then this "Claim Address Redirect" integration feature enables them to access the USUAL and redistribute it to their Users as lined out .

How to request a Claim Address Redirect

In in order to request a "Claim Address Redirect" a current or potential integration partner simply has to follow the flow as outlined in the graphic below:

Detailed Flow

In order to be eligible for a claim address redirect the USUAL accumulating on the address needs to fulfil the following prerequisites:

  • $100 worth of USUAL/month

  • $1000 worth of USUAL in total

  1. Contact the USUAL DAO via the established communication channel.

    1. If no channel is available yet, set one up (if you work in Crypto you know how 😏)

  2. Communicate the contract address on which the USUAL accumulates as well as the address that should "Claim" it.

  3. In order to add your claim address we require "sufficient" proof that you are the deployer or the project team behind the contract address that should be redirected.

    1. Sufficient proof could be:

      1. Social proof

      2. Governance proof (e.g. DAO vote)

      3. Signed message from original deployer

      4. Proof of redistribution

  4. After the "Claim Redirect Address" has been added, a pre-defined challenge period (5 days) will start, in which the USUAL DAO admin or the original claim address owner can cancel the addition of the claim address.

As USUAL DAO we strive to diligently enact the "Claim Address Redirect" process. However, it's up to the integrators to provide correct addresses, sufficient proof and reward their users properly. As an enduser please take up any reward disputes and challenges with the respective integrator.

For the best "Claim" experience after the successful redirect we recommend that address is set up in a (MultiSig) wallet (such as ), which can interact with our dApp or Etherscan.

Once the proof has been established, the Claim Redirect will be added to the .

As soon as the challenge period has concluded the added "Claim address" can claim the USUAL via the Usual dApp's (or ).

As long as an integration is not fully integrated with the reward system (i.e. enduser can claim USUAL via ) it is up to the USD0++ integrator to reward its endusers.

🧩
Safe
DistributionModule
Earn page
Etherscan
Earn page
here
Claim Address Redirect Flow