Ubiquity Compound Safe Wallet dapp

[Hodlatoor]

Is it too much off the reservation to envision a Ubiquity Dapp wallet that is issued to each Bounty Hunter (BH) where the BHhas an interface that shows:

1. Bounties Bounty history like which bounties were claimed, are pending, unclaimed
2. uAD ecocystem development Offers different incentives to convert to uAD and stake/farm
3. Financial tools from partners like compound, Yearn, Curve, Lido, Frax etc
4. Bridging tool from gnosis to mainnet (cowswap integration or in-house for a convenience fee?)
5. Card transaction history
6. Topping off / withdrawing functionality to be used alongside a digital credit card
7. Sending funds, recurring future transactions to others (fees for us)
8. CV/resume creation and editing for Ubiquibot DevPool integration for income generation submission (data mining and optimization)

[0x4007]

Bounties Bounty history like which bounties were claimed, are pending, unclaimed

In progress, based on our work with the audit tool.

uAD ecocystem development Offers different incentives to convert to uAD and stake/farm

This could be pretty straightforward to put together the UI. But we need to focus on the protocol level integrations first, which I think we're pretty far off from. So this will take some time.

Financial tools from partners like compound, Yearn, Curve, Lido, Frax etc

These are just links to their websites. It's not difficult to do but also I don't see how it's directly relevant, unless we build "zaps" which allow us to take a small convenience fee for users to be able to move their funds into these protocols in one click.

Bridging tool from gnosis to mainnet (cowswap integration or in-house for a convenience fee?)

I wonder if we can get by with a link to the official bridge.

Card transaction history

Seems necessary. First we need cards before we can build this of course.

Topping off / withdrawing functionality to be used alongside a digital credit card

Seems necessary.

Sending funds, recurring future transactions to others (fees for us)

Could be fine, these are all far off in the future

CV/resume creation and editing for Ubiquibot DevPool integration for income generation submission (data mining and optimization)

Not applicable for many reasons, but a big one is that projects hire bounty hunters based on the problems they came in and solved already, not because we know anything about who they are.

I only focus on their ability to communicate, how detail oriented they are, and their code quality. I don't ask for their name, or what country they are from etc. because that doesn't change anything about their effectiveness.

[Hodlatoor]

Bounties Bounty history like which bounties were claimed, are pending, unclaimed

In progress, based on our work with the audit tool.

uAD ecocystem development Offers different incentives to convert to uAD and stake/farm

This could be pretty straightforward to put together the UI. But we need to focus on the protocol level integrations first, which I think we're pretty far off from. So this will take some time.

Financial tools from partners like compound, Yearn, Curve, Lido, Frax etc

These are just links to their websites. It's not difficult to do but also I don't see how it's directly relevant, unless we build "zaps" which allow us to take a small convenience fee for users to be able to move their funds into these protocols in one click.

Bridging tool from gnosis to mainnet (cowswap integration or in-house for a convenience fee?)

I wonder if we can get by with a link to the official bridge.

Card transaction history

Seems necessary. First we need cards before we can build this of course.

Topping off / withdrawing functionality to be used alongside a digital credit card

Seems necessary.

Sending funds, recurring future transactions to others (fees for us)

Could be fine, these are all far off in the future

CV/resume creation and editing for Ubiquibot DevPool integration for income generation submission (data mining and optimization)

Not applicable for many reasons, but a big one is that projects hire bounty hunters based on the problems they came in and solved already, not because we know anything about who they are.

I only focus on their ability to communicate, how detail oriented they are, and their code quality. I don't ask for their name, or what country they are from etc. because that doesn't change anything about their effectiveness.

Good feedback! Would be great to see this. It's visual and easy for 3rd parties to understand as a service and product. As for name/ location of developers, they have PFPs and pseudonyms. In my mind, we can capture those and the real idea is to harvest and analyze their effective skillset to create a skillset database, the more we know about their abilities, the better we can funnel work optimally right? Think of it like a semi-anonymous recruiting database based on experience.

[0x4007]

harvest and analyze their effective skillset to create a skillset database, the more we know about their abilities, the better we can funnel work optimally right? Think of it like a semi-anonymous recruiting database based on experience.

DevPool roadmap will see solved issues for each user to determine these skills. It's extremely difficult to fraud merit when the work and entire conversation is public on GitHub. CVs are counter productive for data integrity because lying is too easy.

[Hodlatoor]

valid for small entities. counterpoint: when a larger company has an HR dept and a hiring process with multiple responsible parties, they will still want a resume or CV.

On Fri, Aug 18, 2023, 5:14 AM アレクサンダー.eth @.***> wrote:

harvest and analyze their effective skillset to create a skillset database, the more we know about their abilities, the better we can funnel work optimally right? Think of it like a semi-anonymous recruiting database based on experience.

DevPool roadmap will see solved issues for each user to determine these skills. It's extremely difficult to fraud merit when the work and entire conversation is public on GitHub. CVs are counter productive for data integrity because lying is too easy.

— Reply to this email directly, view it on GitHub https://github.com/ubiquity/research/issues/43#issuecomment-1683046096, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5CGQTCHQMFDRWHGJDSJQNTXV2JT3ANCNFSM6AAAAAA2LB35KA . You are receiving this because you authored the thread.Message ID: @.***>