Provisioning Tool: Requirements

Owned by Mike Tango Bravo
Last updated: Jun 29, 2022
2 min read

This section describes the requirements for a "multi-tentant" winery/token provisioning platform.

Provisioning should consider:

  • Reglutator (i.e. INV in Argentina)

  • Smart-contract provisioning

    • Crowdsale
      Token information provided by the winery should be parsed into new crowdsale contracts, based on the original OpenVino crowdsale contracts.

    • Uniswap
      Token information provided by the winery should be parsed into new Uniswap DEX contracts, based on the original OpenVino crowdsale contracts.

  • OpenVino.Exchange info
    Information to be provided by the winery for token deployment by a form.

    • Token info

    • Winery info

      • Name (i.e. “Costaflores”)

      • Identifier (i.e: “costaflores”) for the winery URL: (https://openvino.exchange/costaflores )

      • Winery web URL: http://costaflores.com

      • Small image for the winery selector page: openvino.exchange

      • Primary color in hex (#FFFFFF)

      • API connectors for

        • Sensor data

        • Work data

        • Image 360

        • Accounting data

      • Wallet address for smart-contract funding

      • Wallet address for crowdsale receipts

      • Wallet address for redeems

    • Wine information

      • Identifier (i.e: “MTB18”)

      • Name (i.e: “Mike Tango Bravo 2018”)

      • Vintage (2018)

      • Generic bottle image (PNG, 1024px high, transparent background)

      • Token Logo (SVG)

      • Crowdsale start date

      • Crowdsale end date

      • Redeem start date

      • Redeem end date

      • Percentages of estimated costs

        • Grape cultivation

        • Wine production

        • Packaging

        • Logistics

        • Marketing