ubiquity / research

3 stars 2 forks source link

Communicate progress with Gnosis and define next steps #53

Closed sergfeldman closed 6 months ago

sergfeldman commented 1 year ago

Gnosis podcast

The previous episodes are here https://open.spotify.com/show/3FghHWrqWr66faGcUeCwtE

Alex can be interviewed for the Gnosis podcast as we use Gnosis Chain to pay freelancers. I strongly recommend that Alex lead the conversation for this podcast because

This is a good opportunity to

Gnosis Pay

Summary of the discussions with the Gnosis Pay team.

sergfeldman commented 1 year ago

The decisions 1) Continue our research and monitor the Gnosis Pay progress. 2) Ask Jon to speak on Gnosis Builders podcast.

sergfeldman commented 1 year ago

@pavlovcik @Hodlatoor please, review

Proposal of content for the Gnosis podcast

I propose to keep simple info regarding technical aspects and features: 1) DevPool is a bounty marketplace natively built on top of GitHub. 2) All payouts are performed on the Gnosis Chain. 3) DevPool automates routine activity and saves time both for projects and freelancers. If you are interested, please contact us [here should be our contacts].

The most important: it is needed to express all our requests for collaboration with Gnosis ecosystem.

1) DevPool - we can launch Gnosis and Safe bounties to our marketplace without additional fees. We can launch any other partner project to our bounties marketplace as well, fees will be discussed with each project. For the priority partner projects, we can customize DevPool for each partner needs, so that they have their own bounties shop on GitHub.

2) Ubiquity has a proposal for the Safe grant. [Here should be Jon's idea :) ]

3) We want to issue Ubiquity Card based on the Gnosis Pay and Gnosis Card.

4) Ubiquity wishes to establish a strategic partnership with Gnosis so open to other collaboration options as well.

Hodlatoor commented 1 year ago

@sergfeldman what was the feedback to : "Then I offered our DevPool help to develop Gnosis Pay itself."?

still thinking about what the most effective offer to them would be...

sergfeldman commented 1 year ago

@sergfeldman what was the feedback to : "Then I offered our DevPool help to develop Gnosis Pay itself."?

still thinking about what the most effective offer to them would be...

@Hodlatoor The guys from Gnosis Pay have not reacted to this proposal. I will ping them in some time.

But Gnosis Pay is just one part of Gnosis.

Hodlatoor commented 1 year ago

@pavlovcik @sergfeldman I think the value proposition to them is a wider audience for their products which we piggyback into our product offering like each person on DevPool gets a gnosis safe built in. using gnosis chain for payment, any other value propositions to them?

I think looking to UbiquiStreams, yield and staking products should also be on the table.

sergfeldman commented 1 year ago

I think looking to UbiquiStreams, yield and staking products should also be on the table.

@Hodlatoor Per my understanding, everything related to payments is highly relevant to their strategy. Yield products can be relevant to Safe.

This is a question to Alex could we offer such products or not.

@sergfeldman agreed.
@pavlovcik - thoughts?

0x4007 commented 1 year ago

Directly relevant Gnosis products:

  1. Safe for partners to custody the funds that the UbiquiBot pays to their community.
  2. CowSwap for enhancing the cash out experience.

Possibly relevant:

  1. Pay. We want to make a card and fiat banking for our users. But if Pay ends up being perfect then we don't need to reinvent it. Again we should wait to actually use their offering before changing our strategy.
Hodlatoor commented 1 year ago

great! :)

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

Directly relevant Gnosis products:

  1. Safe for partners to custody the funds that the UbiquiBot pays to their community.
  2. CowSwap for enhancing the cash out experience.

Possibly relevant:

  1. Pay. We want to make a card and fiat banking system for our users. But if Pay ends up being perfect then we don't need to reinvent it. Again we should wait to actually use their offering before changing our strategy.

— Reply to this email directly, view it on GitHub https://github.com/ubiquity/research/issues/53#issuecomment-1683058101, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5CGQTDYTG2AVX5P7COG3CLXV2LGVANCNFSM6AAAAAA3BBZD6I . You are receiving this because you were mentioned.Message ID: @.***>

ubiquibot[bot] commented 6 months ago
# Issue was not closed as completed. Skipping.