Why are you participating for Based LatAm?

OpenVino was born in wine country, Mendoza, Argentina.

Though our product is designed for the world's 70,000 wineries, the existing wine supply chain, and wine drinkers globally, our first producers are in LatAm. We are bringing web3 solutions to wine producers, brick-and-mortar businesses that have existed since humans began fermenting grapes 10,000 years ago.

Our developers are based in Argentina, and we are active in the community. We are Aleph citizens, developers and core contributors to the Creciminto movement, and our primary focus is on bringing real-world asset tokenization to a traditional business community.

We have presented OpenVino as a reference for RWA tokenization, along with new models of transparency and traceability, not only in web3 conferences in the region, but to universities, goverment agencies, trade and agricultural organizations, and businesses througout Argentina, Mexico, Peru, Brazil, Chile, and Uruguay.
https://openvino.atlassian.net/wiki/spaces/OPENVINO/overview?mode=global

We partner with Latam projects. For example, we are building our unique transparency model, called "BioDigital Certification" with Kleros.

What challenges are you focusing on?

OpenVino is a Web3 platform that provides Tokenization, Transparency, and Traceability services for the wine industry. A highly atomized industry, 70,000+ wine producers operate worldwide, representing $400B in annual revenue. OpenVino solves existing real-world problems that affect wine producers, the wine supply-chain, and consumers.

But we must insure that our solution is simple and inexpensive for our non crypto-native customers.

Though we began with our initial deployment on Ethereum mainnet in 2018, we believe migrating our solution to Base can be instrumental in three ways:

• Reducing complexity (by using account abstraction and smart contract wallets)
• Reducing cost for consumers (low gas fees and gasless transactions)
• Easy integration with the fiat on-ramp for global customers.

We believe firmly in decentralization - and for us an Ethereum L2 based on the OP stack is ideal.

Though we are currently connecting our dApps to "centralized" endpoints, like Infura, our vision with OpenVino is bring a utilitarian use-case for blockchain nodes distributed at OpenVinoDAO wineries with our Netrabrick solution:
https://openvino.atlassian.net/wiki/spaces/OPENVINO/pages/187793741/Netrabrick
With the Netrabrick, we envision a low-cost, administered appliance that provides blockchain endpoints, IPFS, web2 decentralization, IoT connectivity, and localized AI image processing for wineries. For this, we are building a dappnode package for Base.

For a complete and concise description of OpenVino, please have a look at the OpenVino "Purple Paper".
https://openvino.atlassian.net/l/cp/DhpyA1tC

And we have many videos and short animations on https://youtube.com/@OpenVino

How does your submission address this challenge?

With this project, we have built several components to address the challenges of improving user experience and reducing costs, by incorporating account abstraction, smart wallets, social login, for our consumers on our dApp: https://base.openvino.exchange
Next, we created tools for deploying new wine tokens and migration from Ethereum mainnet to Base. These tools are part of a larger initiative to create provisioning tools for wineries to deploy new wine-backed crypto assets.
And we built Viniswap (base.viniswap.openvino.org) - our adaptation of Uniswap to accommadate revenue distribution, both to token liquidity providers and to OpenVinoDAO as a primary revenue stream, so that we can provide free services to the wine world.

Challenges we ran into

We had many challenges...and we are exhausted!
Many of our initial challenges were simply related to migrating openvino.exchange from depracated applications - moving from Create React app to Vite and Angular to Vite, not to mention that we deployed a fresh server for this new environment.

We found that the SDKv5 that we are using for account abstraction is poorly documented, resolving these issues through trial and error.

We were unable to implement paymaster for gasless transactions. This may be because of the payment mechanism (credit card) but we are using the openzeppelin relayer on nft.openvino.org which we can adopt for this in-lieu of paymaster for payment in crypto, if there is no work around.

Finally, EOA wallets don't accept batch transactions, but by using smart wallets with account abstration we were able to create a more fluid user experience.

Additional Features

We have a base dApp (https://openvino.exchange) - which we have now put into "maintenance mode" until we deploy this new environment. But as mentioned earlier, we had to migrate everything to a new codebase (even the OS!) so that we could add the features for this challenge. Certainly, this overall rewrite was something we had planned to do anyway, so our eagerness to migrate to base has been a great push for us.

So, new things that we were able to integrate, include:

• Viniswap - our brand new DEX, enabling wineries to manage liquidity pools, and swap fee distribution to OpenVinoDAO.
• Account abstraction for smart wallets, enabling a payment gateway for customers with only fiat, simpler batch transactions, social login, and integration with EOA wallets beyond metamask.
• Provisioning and migration tools for creating new wine token pairs. This is essential, as we are now launching 9 new wineries on OpenVino!
  https://github.com/openvino/minter-and-forwarder.git