Some background first
You may have noticed in recent months the extensive Beet wallet developments on Github and the related 3rd party apps like the NFT issuance tool, NFT viewer, Airdrop tool and the new market UI project being posted here on Hive.
In the past the Bitshares committee helped fund the development of the wallet, now we're reaching out to the EOS community to bring greater EOS integration into the Beet wallet stack, and to do so we need to raise development funds.
To aid in EOS relations, 
Check out the Beet Pomelo Grant page and consider a small donation to improve our quadratic development funding, every little bit helps!
Once the EOS related developments are funded and implemented, greater Hive integration will be on the horizon, so even if you're not involved in the EOS community consider helping out.
What is Pomelo?
Pomelo's mission
Their mission is to empower anyone to fund and build the open web. They do that by giving creators and builders the opportunity to fund their projects through four seasons of Pomelo per year. The quadratic funding mechanism allows the community to have full involvement in determining the allocation of funds.
To hear from those who have benefitted from Pomelo, check out their testimonial videos.
What are Pomelo Grants?
Pomelo Grants is an open-source crowdfunding platform that enables anyone to contribute directly to projects seeking funding. Projects that provide a public good for the EOS community will have contributions matched from a pool of funds.
These grants use quadratic funding to allocate more matching funds to the projects that receive more contributions from more unique donors.
Pomelo aims to help developers, businesses, and individuals build a reputation in the ecosystem, season after season. Grant owners are encouraged to promote their grants and build their communities, using the opportunity to get noticed by larger funding bodies.
For more, see the article, What Is Pomelo?
What is quadratic funding?
Pomelo has two components, a crowdfunding round and a large matching pool of funds. During the crowdfund, grant owners seek donations from the community, and the community supports the projects they care about. The matching pool is distributed to grants using quadratic funding.
Quadratic funding (QF) is an optimal method of funding public goods in a democratic society. Inspired by Gitcoin, Pomelo employs QF as a funding mechanism for digital public goods.
The QF mechanism means that the number of contributions and the total amount contributed to the project influence the total amount allocated from the matching pool. The greater the number of community members that support a project, the more funds the project will receive from the matching pool. Even lower value contributions can result in a high matched amount.
Beet's Pomelo pitch
The following text is from the Beet Wallet Pomelo page:
Meet Beet, a stand-alone key/identity manager and signing app originally built for Bitcoin and BitShares. Our goal is to develop this working proof of concept into a new, free and open-source web application for the EOS ecosystem.
The problem Beet solves: Key management and trust on the EOS Blockchain
Every action on a blockchain requires a cryptographic signature of the required private keys for this action. When using third party tools (especially closed source ones), the question about trust quickly arises. Particularly, are they going to steal my private keys?
Beet aims to solve these trust concerns and streamline private key management for the everyday user. For example, Beet allows separate account management and full user control of what data is exposed to third parties.
Beet has additional features when compared to Metamask, since it runs as a desktop application and can take operation inputs as a JSON. This method saves developers time and adds flexibility across devices.
A more direct approach would be for the web app to communicate directly with Beet for signing and broadcasting transactions. This gives Beet an “Anchor-like” experience. This method eliminates the JSON step and lowers the chance of user error.
Here's what we aim to offer the EOS Ecosystem through Beet:
Provide a free and open-source code base for the EOS community
Integrate and secure EOS/TLOS keys into the Beet wallet.
Refine the wallet User Experience (UX) for EOSHere's a proof of concept for Beet Wallet on BitShares. (And here are some additional developments demonstrated)
We aim to bring this working concept of Beet thus far into a stand-alone, free and open-source EOS Native wallet.
Who are we?
We are members of the BitShares Group, an independent organization acting in the best interests of the BitShares Blockchain. Beet has been an effort by many contributors that are a part of this organization.
Why do we need another wallet supporting EOS?
Infrastructure and diversity is critical for decentralized network security. Anchor and Wombat are excellent wallet utilities, and adding another capable wallet further strengthens the ecosystem.
Ultimately, with Beet, EOS users and dApp developers would have an independent "swiss army knife" app to interact with the EOS blockchain.
Feel free to peruse our Github for additional information on what has been built so far. We also have a Beet Telegram group of developers and builders and are happy to discuss any questions or concerns.
Thanks for your support!
In conclusion
I'm looking forwards to continuing Beet wallet developments; if you're interested in helping open source development then please do consider contributing to the dev fundraiser this season.
Cheers :)