Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create vera_defi.md #281

Merged
merged 12 commits into from
Apr 1, 2021
Merged

Create vera_defi.md #281

merged 12 commits into from
Apr 1, 2021

Conversation

arbach
Copy link
Contributor

@arbach arbach commented Feb 25, 2021

Initial grant application

Grant Application Checklist

  • The application-template.md has been copied, renamed ( "project_name.md") and updated.
  • A BTC or Ethereum (DAI) address for the payment of the milestones is provided inside the application.
  • The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
  • The total funding amount of the project is below USD $30k for initial grant applications and $100k for follow-up grants.
  • The initial PR contains only one commit (squash if needed before submitting your PR).
  • The grant will only be announced once we've successfully delivered the first milestone.

Initial grant application
@CLAassistant
Copy link

CLAassistant commented Feb 25, 2021

CLA assistant check
All committers have signed the CLA.

@Noc2 Noc2 self-assigned this Feb 25, 2021
Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the application. The links to your POC aren’t working for me: https://github.com/veraprotocol/defi or http://18.219.122.155/?rpc=ws%3A%2F%2F18.219.122.155%3A9944#/explorer Also, where can I find more information about the AssetManager module and it’s functionality?

@Noc2 Noc2 added the changes requested The team needs to clarify a few things first. label Feb 25, 2021
@arbach
Copy link
Contributor Author

arbach commented Feb 26, 2021

Repo was turned private by mistake. I also brought the nodes and app up. Sorry about that.

AssetManager is Ink smart contract, there is description about it on the READ.ME in the repo.

We are working on adding more documentation.

Thank you.

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for sharing. It’s nice to see that you already started to work on the AssetManager. Which additional features do you plan to integrate as part of the grant? Could you add more technical details to the application itself (e.g. lending manager etc.). What programming languages are you planning to use for the UI and what functionality will you implement in the UI? Do you already have an initial draft of the design?

@arbach
Copy link
Contributor Author

arbach commented Mar 1, 2021

We are working on more technical specification for the milestone, including the UI and contracts. Will update application soon.
UI will be in react as you can see in the tech stack already included in the application.
In the application we included clickable wireframe. The actual design will be part of the grant, as we want to make sure it's top quality work. Design and UX are essential for the long term success of this project.
Thanks for the feedback!

@Noc2
Copy link
Collaborator

Noc2 commented Mar 1, 2021

Thanks. Feel free to ping me once you’ve updated the application.

@arbach
Copy link
Contributor Author

arbach commented Mar 8, 2021

David, please check we have added more details to our application. Thank You!

@arbach arbach requested a review from Noc2 March 15, 2021 01:48
Copy link
Contributor Author

@arbach arbach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

David, if you please review at your convince.

@Noc2
Copy link
Collaborator

Noc2 commented Mar 15, 2021

@denislam also needs to sign the CLA.

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the updated application. Could you also update the table with the Deliverables and Specification? For example you defined NFT Lending and I’m not sure it’s actually part of the deliverables. Also what do you mean with “Continue the development of our NFT.”?

arbach and others added 2 commits March 17, 2021 11:27
NFT Token development clarification
@arbach arbach requested a review from Noc2 March 17, 2021 19:59
@arbach
Copy link
Contributor Author

arbach commented Mar 17, 2021

David, Thank you for the review.

Yes, NFT lending is part of this, sorry about the confusion. I have updated the table. There are details on the NFT itself in under the milestone details.

Denis signed the CLA.

Would love to hear any feedback you have, negative before positive.

Thanks

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update and sorry for the late reply. I have two more questions: Could you also integrate more information regarding the User Interface? For example programming languages, support for the polkadot.js extension, etc. and I noticed that the attribution in your code seems to be missing: https://github.com/veraprotocol/defi and https://github.com/paritytech/ink/tree/master/examples Could you clarify this?

@arbach
Copy link
Contributor Author

arbach commented Mar 23, 2021

David,

We have discussed and added the license to our code.

As for the UI, it will built with React mostly coded with TypeScript, and we will rely on Polkadot.js to sign transaction, that is already included in our wireframe.

@arbach arbach requested a review from Noc2 March 23, 2021 04:12
Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the quick response. But the repo still doesn’t contain any license file, nor any reference to the code, which originally was developed by parity. At least as far as I can see it.

@arbach
Copy link
Contributor Author

arbach commented Mar 25, 2021

Sorry about that. We have added missing attribution to all relative files.

We are eager to work with you, let me please if there is anything else we can do to make sure our project is accepted in the program.

If you think we need to add more technical details, or elaborate on the business further we are more than happy to do it.

Thanks.

@arbach arbach requested a review from Noc2 March 25, 2021 00:22
@Noc2
Copy link
Collaborator

Noc2 commented Mar 25, 2021

Thanks for adding the additional attribution and details. To be honest, I’m personally at the moment not convinced by your application but I will share it already with the rest of the team. Also are you aware of the Element/Telegram chat group for all things NFT on Kusama and Polkadot. Also something you should be aware is that: A group of devs, PMs and designers, along with artists and NFT creators are working on a NFT strategy for Kusama network (already ongoing: https://kusama.polkassembly.io/post/303).

@Noc2 Noc2 added ready for review The project is ready to be reviewed by the committee members. and removed changes requested The team needs to clarify a few things first. labels Mar 25, 2021
@mmagician
Copy link
Contributor

research and implement attributes and functionalities to link Token to real assets, such as hash or signature of scan of Art, and other proprietary techniques.

This is just adding a metadata to the token, nothing new here.


Add support for perpetual royalties to original creator

This is covered by ERC-2665, so I'm not sure what further research you need to do in this front (and adapting ink!'s erc721 to support this feature should be trivial).


We also don't provide support for the UX design phase as part of grants, as we believe this should form part of the team's investment and market research, and normally should be provided as part of the application. In your case, it's a benefit that you already provided wireframes, thanks for that.


With the above two points in mind, your list of core deliverables is halved. I think the idea you have might have some potential and I would be happy to support your project for a smaller amount. Let me know if this makes sense!

@semuelle
Copy link
Member

On top of what @mmagician mentioned, given that the aspect of linking real-world assets to NFTs isn't part of this application, it isn't a good selling point in the context of a grant. I would be keen to support a more generalised smart contract lending library, though.

@arbach
Copy link
Contributor Author

arbach commented Mar 26, 2021

Thanks for adding the additional attribution and details. To be honest, I’m personally at the moment not convinced by your application but I will share it already with the rest of the team. Also are you aware of the Element/Telegram chat group for all things NFT on Kusama and Polkadot. Also something you should be aware is that: A group of devs, PMs and designers, along with artists and NFT creators are working on a NFT strategy for Kusama network (already ongoing: https://kusama.polkassembly.io/post/303).

David, thanks for the great valuable feedback, this is exactly what we are looking for. We already joined both these group and will start discussion the best fit for our solution in the ecosystem based on their feedback and need. Our primary goal is to bring our industry connections, and technical knowledge to the Polkadot ecosystem to learn, contribute, and be part of the success of the wider ecosystem. We will keep you posted as our business evolve as we engage further with the community.

@arbach
Copy link
Contributor Author

arbach commented Mar 26, 2021

research and implement attributes and functionalities to link Token to real assets, such as hash or signature of scan of Art, and other proprietary techniques.

This is just adding a metadata to the token, nothing new here.

Add support for perpetual royalties to original creator

This is covered by ERC-2665, so I'm not sure what further research you need to do in this front (and adapting ink!'s erc721 to support this feature should be trivial).

We also don't provide support for the UX design phase as part of grants, as we believe this should form part of the team's investment and market research, and normally should be provided as part of the application. In your case, it's a benefit that you already provided wireframes, thanks for that.

With the above two points in mind, your list of core deliverables is halved. I think the idea you have might have some potential and I would be happy to support your project for a smaller amount. Let me know if this makes sense!

Marcin, we appreciate the valuable feedback.

For the attributes, our long term intention is to bring more industry standard to the on chain data to incorporate things like ISO 25178 to have better traceability of physical assets and their digital representation.

Yes, indeed ERC-2665 already provide strong foundation, however we are hoping to provide more comprehensive royalty structures, research and try to address IP issues related to NFT. We don't have exact scope of how much of this research outcome can be incoporated in current grant milestone. Completely understand if you think this doesn't add value to the ecosystem.

Thanks for the clarification on the UI/UX. Our team is heavily invested in this, and will cover that aspect of the expense.

Having said that, our primary objective is the engagement with the community to make sure what we are building has value for everyone. We highly appreciated your generous support and happy to take a smaller amount you suggest for this project.

@arbach
Copy link
Contributor Author

arbach commented Mar 26, 2021

On top of what @mmagician mentioned, given that the aspect of linking real-world assets to NFTs isn't part of this application, it isn't a good selling point in the context of a grant. I would be keen to support a more generalised smart contract lending library, though.

Sebastian, thank you for the valuable feedback! we talk about physical assets to give context for our overall vision as recommended by the grant guideline, sorry if we took this too far in this application. At it's heart this is a lending smart contract. and will be available for use by other under open source license. We are open to put more effort to make our smarts in a well documented library to be used by other as well.

Let me please know if you have further suggestion to help us gain your support for our project.

Thank you.

@mmagician
Copy link
Contributor

@arbach We are generally happy to support a research phase, although in general I would see it as a separate grant. In this case, however, I'm not sure what the outcomes/deliverables of such a research phase would contribute, so without seeing a concrete proposal it's hard to judge.
Nevertheless, my personal suggestion would be to decouple NFT specifications from the rest. For this grant I suggest to focus on the AssetManager & the ExchangeManager, given that we've already got plenty of similar NFT grants. @semuelle @Noc2 do you think that would make sense?

@semuelle
Copy link
Member

the AssetManager & the ExchangeManager

@mmagician Isn't the ExchangeManager rather common? Agreed on the AssetManager, though.

@arbach
Copy link
Contributor Author

arbach commented Mar 30, 2021

Let us please know if there are any other clarification from our side you need. or anything else we can do to make sure we start this partnership. Thanks

@mmagician
Copy link
Contributor

@arbach

For this grant I suggest to focus on the AssetManager

If you're ok with it, you can go ahead and change the scope of the application to reflect that. You should be able to integrate with existing NFT implementations, rather than building another one anew.

Update scope to focus on AssetManager. Use existing NFT implementation instead of building our own.
@arbach
Copy link
Contributor Author

arbach commented Mar 30, 2021

If you're ok with it, you can go ahead and change the scope of the application to reflect that. You should be able to integrate with existing NFT implementations, rather than building another one anew.

@mmagician

I have updated our Grant application accordingly.

@mmagician
Copy link
Contributor

Thanks for your flexibility.
As I pointed out before:

With the above two points in mind, your list of core deliverables is halved.

I believe you still should adjust the price accordingly.

Update cost
@arbach
Copy link
Contributor Author

arbach commented Mar 31, 2021

@mmagician Sorry I missed that. fixed.

Copy link
Contributor

@alxs alxs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy to go ahead with this.

Copy link
Contributor

@mmagician mmagician left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alright, let's give it a try

@Noc2 Noc2 merged commit ce5e2d4 into w3f:master Apr 1, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2021

Congratulations! As part of the Open Grants Program, we want to help winning teams acknowledge their grants publicly. To that end, we’ve created a badge for projects that successfully delivered their first milestone. Please observe the foundation’s guidelines when making any announcements; in particular, don’t announce the grant publicly before you've completed at least the first milestone of the project.

At that point, we will be happy to collaborate on an announcement about the work you’re doing. Please get in touch with us at grantspr@web3.foundation in case you're interested (at least two weeks notice is preferred).

@arbach
Copy link
Contributor Author

arbach commented Apr 1, 2021

@mmagician @Noc2 @alxs @semuelle , web3 team

We , the Vera team, are grateful for the trust you put in us, and we are thrilled for your approval for our project, and looking forward to complete this work and move forward with you!

chrisli30 added a commit to AvaProtocol/W3F-Grants-Fork that referenced this pull request Apr 19, 2021
* resource viewer

* changed milestone 3

* quadratic-funding (w3f#227)

* quadratic-funding

* add license, unit test and a standalone minimalistic frontend to spec

* add SEOR code-less smart contract platform application (w3f#205)

* add SEOR code-less smart contract platform application

* update deliverable & add future plans

* add multi-chain support in Milestone 2 & 3's deliverable

* formart the subtitles of 'Project Details' segment

* Polkastarter Grant Application (w3f#204)

* Make Polkastarter Grant Application

* Added screenshots

* Added testing guides

Co-authored-by: Tiago Martins <tiagom87@gmail.com>

* Added curve market maker (w3f#225)

* Added Zondax maintenance+recovery extensions+support (w3f#234)

* Create polkakeeper.md (w3f#200)

* Create polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

Added UI User stories, and more detail on the milestones

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

* Update polkakeeper.md

Co-authored-by: Caspar Oostendorp <caspar@oostvoort.com>

* Readmefixing (w3f#241)

* upgrade readme

* fix icons

* smaller icons

* correct icons

* Update README.md

Updated Evaluators

* Update welcome.yml (w3f#242)

* Update welcome.yml

Update Welcome message

* Update welcome.yml

updated

* Create proposal of stone index on substrate

* Updated the BTC payment address

* draft of pallet design

* Added more details of public functions

* Added back the mandatory deliverables

* Added desc for public exposed methods

* Adjusted the budget

* Revised the deliverables

1. Merge the token module into indexed basket management module
2. Made it more clear for DEX integration
3. Update the sequence of deliverables

* Create AlgoCash.md

* Update AlgoCash.md

* Update AlgoCash.md

* Update AlgoCash.md

* Update AlgoCash.md

* Update AlgoCash.md

Update the approach of further 500,000 share token distribution

* Update AlgoCash.md

Add contract specification

* Update AlgoCash.md

* Update README.md (w3f#250)

As discussed on Element, David, I've added Edgeware Grants and Bounties under the other grant programs header.

* Update welcome.yml

fix html </b>

* Create php-scale-lib.md

* Payment change

* Upgradeability

* Add missing milestone title

* Reduce scope by removing milestone 2

Milestone 2 was deemed too uncertain to be part of the initial grant.
Depending on the results of the first milestone, we will consider
submitting another proposal with more concrete steps.

* Update pull_request_template.md

* Denominating in usd (w3f#253)

* Update application-template.md

denominating in USD

* Update README.md

* Create starry_network.md

* Rename starry_network.md to Starry_Network.md

* Update Starry_Network.md

* update Ecosystem Fit

* update overview

* update architecture

* remove ecosystem fit and add additional Information

* update overview

* Update Starry_Network.md

* add nft dao architecture image and reduce price

* Added user story about NFT DAO, update demo link

* reduce from 12000 DAI to 10000 DAI

* Update pull_request_template.md (w3f#261)

* Update kylin_network.md (w3f#259)

Update the original contract based on grant evaluation comments. [Here](w3f/Grant-Milestone-Delivery#98)

Co-authored-by: wannam2049 <71331352+wannam2049@users.noreply.github.com>

* Unified TOC and language with general grants (w3f#264)

* Update sensio_network.md

Second milestone of senseo will no longer be delivered

* Remove forum link (w3f#269)

* NewOmega Application (w3f#243)

* Add newomega application

newomega: Fix alignment

newomega: More details

newomega: Improve formatting

* newomega: Include github link to solidity contracts in deliverables

* newomega: Update deliverables to reflect file rename

* newomega: Update deliverableremove third milestone, tweak price

* newomega: more precision in milestone 2 definition

* dotmog application

* Create bright_treasury.md

* Update currency to DAI, add DoD

* Update README.md

Updated Committee

* Update .gitignore (w3f#279)

Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com>

* Delete .DS_Store

* StandardProtocol application (w3f#244)

* Add Standard Protocol Application

* Update Standard_Protocol.md

* Update Standard_Protocol.md

* Update Standard_Protocol.md

* Update Standard_Protocol.md

* Update Standard_Protocol.md

* Update Standard_Protocol.md

* Update Standard_Protocol.md

* Update Standard_Protocol.md

* Update Standard_Protocol.md

* Create application-template.md (w3f#276)

* Create application-template.md

- Some clarifications and highlighting based on past issues,
- mention licensing,
- more emojis ✊,
- ask for 
  - short and long term plans,
  - community & contributors,
  - status of project before grant,
  - previous grant applications,
  - work done.

* Apply suggestions from code review

Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com>

* Update applications/application-template.md

Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com>

Co-authored-by: David Hawig <davidhawig@gmail.com>
Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com>

* Ask for follow-up grant info (w3f#280)

* Update README.md

* fix headings (w3f#285)

* SkyePass application (w3f#212)

* add application for skyepass

* update porposal

* update: identity solution spec

* updates on milestone desc

* update milestone descp

* update milestones

* update total cost

* update milestone spec

* delete status col

* Polkadot UI Web Identicon + Angular Identicon (w3f#252)

* Submission of the project grant template

* Adding repositories for Angular and Web Identicon projects

* Deliverable + future plans update

* Grant Amount Update

* Create ZeroPool.md (w3f#208)

* add ZeroPool.md

* remove the last milestone

* fix typo

* Update ZeroPool.md

* Quadratic Funding Module and Dapp Application (w3f#268)

* Quadratic Funding Module and Dapp Application (#2)

* Added quardratic funding proposal

* Finalized quadratic funding open grant proposal

* Added web app wireframe link and description to project details

* 1. Added finalize function to M1 delivery
2. Adjusted BTC amount to make sure the total funding is within limit

* 1. Move user study out of M2 to future plans due to tightness
2. Fix the paragraph spacing of last commit

* 1. Added UI examples to team's experience section
2. Update the cost denomination to DAI instead of BTC

* 1. Changed BTC address to ERC20 DAI address
2. Added Sybil resistance to future plans

* Added identity module interaction requirement to M1 delivery

* Added project and proposal concepts to UML chart

* Webb Mixer (w3f#216)

* Create MIXER.md

* Update MIXER.md

* Update MIXER.md

* Update MIXER.md

* Update MIXER.md

* Update MIXER.md

* Update README.md (w3f#288)

* Update README.md

* Update application-template.md (w3f#289)

- target audience
- limitations
- `the project` -> `your project`

* Action to automatically label by approvals remaining (w3f#291)

* Github action to label based on approvals (missing)

* Revert "Github action to label based on approvals (missing)"

This reverts commit f6a6b70.

* Github action to label based on approvals

* Create Gluon_decentralized_hardware_crypto_wallet_services.md (w3f#182)

* Create Gluon_decentralized_hardware_crypto_wallet_services.md

* Merge branch 'master' of https://github.com/tearust/Open-Grants-Program

* update btc to dot

* add light node to communicate with DOT. adjust cost based on BTC price change

* update based on discussion. using schnorr and social recovery pellet

* update milestones

* add prerequisites to Schnorr threshold sign

* update using Schnorrkel algorithm

* update to USD

* Update google_sheet_update.yml

* EverlastingCash Web3 Grant Application (w3f#277)

* Create EverlastingCash.md

ELC - An algorithmic stablecoin with reserves

* Update EverlastingCash.md

* Update EverlastingCash.md

* Update EverlastingCash.md

* Update EverlastingCash.md

* Update Linkedin

Co-authored-by: steven <39795608+steven858@users.noreply.github.com>

* approval labeler rewrite (w3f#292)

* Github action to label based on approvals (missing)

* Revert "Github action to label based on approvals (missing)"

This reverts commit f6a6b70.

* Github action to label based on approvals

* approval labeler rewrite

* substrate identity directory (w3f#255)

* substrate identity directory

* substrate identity directory

* added 0a to 0d deliveries to milestone 1

* price changed

Co-authored-by: dark64 <darem966@gmail.com>

* A comma (w3f#298)

* Update README as in General Grants repo (w3f#303)

* Update README as in General Grants repo

* Update README.md

Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com>

Co-authored-by: David Hawig <davidhawig@gmail.com>

* Update README.md

Fixing links

* Update README.md

fix rfp link

* Update README.md

fix milestone-deliverables-guidelines link

* Update README.md

Update tech stack/accepted links

* Fix broken links (w3f#307)

* Update MAP-Bridge.md

Termination, see [comment](w3f/Grant-Milestone-Delivery#89 (comment))

* Update MAP-Bridge.md

Added payment address again, just in case

* Update clover_network.md (w3f#310)

* Update shadows-network.md (w3f#309)

* Update README.md

* Update README.md

* Update README.md

* Open Grants Program application for project Delmonicos (w3f#283)

* Update delmonicos.md
+ Application update after questions from Noc2

* Update to address demand from gautamdhameja

* Changed repo url

Repo moved to the newly created Delmonicos organisation

* Update polkadex.md

* Add Treasureland Grant (w3f#218)

* Create Treasureland.md

* Update Treasureland.md

* Update Treasureland.md

* Update Treasureland.md

* Update Treasureland.md

* Update Treasureland.md

* Update Treasureland.md

* Update Treasureland.md

* Update Treasureland.md

* ChainJS Grant application (w3f#228)

* Create chainjs.md

Adding template for grant proposal

* Update chainjs.md

Adding ChainJS for Polkadot draft proposal

* Update chainjs.md

Corrected title

* Update chainjs.md

formatting

* Update chainjs.md

added ecosystem fit section

* Update chainjs.md

* Update chainjs.md

Removed instructions

* Update chainjs.md

removed instructions

* Update chainjs.md

Added more narrative to future plans

* Update chainjs.md

* Update chainjs.md

Added Kusama support into the grant application, and added more description of the difference between ChainJS and Polkadot.js

* Update chainjs.md

Updated pricing

* Update chainjs.md

Lowering price

* PolkaJ Android Support proposal (w3f#301)

* PolkaJ Android Support proposal

* Update BTC to DAI

* Adjust price based on feedback

* Remove undelivered milestone (w3f#318)

* xtoken - XCM Implementation for Fungible Assets (w3f#316)

* xtoken

* update description

* update

* update payment denomination, and milestone 1 deliverables

* file name change, milestone cost updated

Co-authored-by: Bryan Chen <xlchen1291@gmail.com>

* stable-asset.md (w3f#286)

* stable-asset.md

* Update stable-asset.md

* Update stable-asset.md

* Update stable-asset.md

Co-authored-by: Shengda Ding <dingshengda@gmail.com>

* move the application file into its proper folder (w3f#320)

* discount based on hackathon participation (w3f#325)

* Update EVANESCO Legal Structure (w3f#326)

* pallet-maci (Minimal Anti Collusion Infrastructure) (w3f#232)

* Create pallet_maci.md

* Update pallet_maci.md

* Update pallet_maci.md

* Update pallet_maci.md

* discount Apron Network for ParityAsia hackathon award (w3f#323)

* changed the bitcoin address (w3f#330)

* discount deeper network due to hackathon participation (w3f#324)

* Create XPredictMarket.md (w3f#313)

* update the gsheet workflow

* re-estimate the price of milestone (w3f#331)

* Update Apron_Network.md

Remove SDK from milestone and reduce the price

* Update Apron_Network.md

Reduce the price

* Bit.Country Milestone 2 (w3f#305)

* Create bit_country_m2.md

initial draft for m2.

* Update bit_country_m2.md

Finalised the tasks in the milestone.

* Update bit_country_m2.md

minor milestone text update

* Update bit_country_m2.md

update team member

* Update bit_country_m2.md

update image.

* Update bit_country_m2.md

Change the amount to be USD as required.

* Update bit_country_m2.md

Add bootstrap tasks for launching testnet.

* Update grant application. (#1)

Restructure and update wording to improve clarity of deliverables.
Add summary and considerations sections.

* Tech stack and changing NFT native to support NFT

Tech stack and changing NFT native to support NFT

* update Duration

update Duration

* fix typo

Co-authored-by: Shannon Christie <20452861+shannon-christie@users.noreply.github.com>

* removed "Adopt storage", reduced costs (w3f#339)

* Create vera_defi.md (w3f#281)

* Create vera_defi.md

Initial grant application

* Update grant application

* Replace https with http to fix images link.

* Add more details to the milestone

* Update vera_defi.md

Update bio

* Update vera_defi.md

* Clarification on NFT Lending

* Update vera_defi.md

NFT Token development clarification

* Update vera_defi.md

Fix style

* Update vera_defi.md

Fix style

* Update vera_defi.md

Update scope to focus on AssetManager. Use existing NFT implementation instead of building our own.

* Update vera_defi.md

Update cost

Co-authored-by: arbach <dev@dev.com>
Co-authored-by: Denis <denislam@users.noreply.github.com>

* Create Parallel.md (w3f#329)

* Auto-merge action (w3f#349)

* NFT Collectibles Wallet (w3f#341)

* NFT Collectibles Wallet

* updating project scope and adjusting cost

* updating estimated duration

* reordering milestone numbers

Co-authored-by: Michael Huntington <2466745+MikeHuntington@users.noreply.github.com>

* Clean & fix actions (w3f#359)

* Delete label_approval_count.yml

* Update auto_merge.yml (w3f#360)

* remove m2 (w3f#355)

* Update README.md

* cosmetic fixes

* Subspace (w3f#357)

* first draft

* second draft

* minor edits

* finial revisions

* Rename subspace.md to spartan_poc_consensus_module.md

* adjust license and cost

* adjust license and cost

* no parallel funding from multiple sources

* Update dorahacks-quadratic-funding.md

* Update README + other minor changes (w3f#367)

* Add more info to README

* Track team provenance + minor updates to template

* Update PR template

* Update dorahacks-quadratic-funding.md (w3f#370)

We completed frontend integration with HackerLink. However due to tight schedules we didn't create a demo page based on the substrate-frontend-template (task #2 of Milestone-2). Another reason why we didn't create the simple page is that HackerLink has a complete infrastructure for user registration, project upload / display, etc. The HackerLink code base is not open source. We would like to provide a complete demo of how quadratic funding grant is functioning on a parachain or potentially on Polkadot / Kusama relaychains in the future. Therefore we would like to still submit a milestone. Given that our frontend is not open source and we are only providing a demonstration site that uses our milestone-1 code to provide a service for quadratic funding grant, we are reducing the price to 0 accordingly.

* Delete application-template-cn.md (w3f#372)

Co-authored-by: borispovod <boris@wings.ai>
Co-authored-by: Jiannan Zhang <jn.zhang610@gmail.com>
Co-authored-by: AKACoder <30492526+AKACoder@users.noreply.github.com>
Co-authored-by: Polkastarter <72085336+polkastarter@users.noreply.github.com>
Co-authored-by: Tiago Martins <tiagom87@gmail.com>
Co-authored-by: mikolajsobolewski <51751942+mikolajsobolewski@users.noreply.github.com>
Co-authored-by: Juan Leni <juan.leni@zondax.ch>
Co-authored-by: RAMPDEFITEAM <70554959+RAMPDEFITEAM@users.noreply.github.com>
Co-authored-by: Caspar Oostendorp <caspar@oostvoort.com>
Co-authored-by: semuelle <sebastian@web3.foundation>
Co-authored-by: David Hawig <davidhawig@gmail.com>
Co-authored-by: calvinzhou-rockx <55546839+calvinzhou-rockx@users.noreply.github.com>
Co-authored-by: Dohkooo <77781754+Dohkooo@users.noreply.github.com>
Co-authored-by: Junte <59536049+Madtodist@users.noreply.github.com>
Co-authored-by: gmajor <63032554+gmajor-encrypt@users.noreply.github.com>
Co-authored-by: Hugo Peixoto <hugo.peixoto@gmail.com>
Co-authored-by: Fuling <mon.samuel@qq.com>
Co-authored-by: Aleixo Sánchez <aleixosk@gmail.com>
Co-authored-by: kylin <70003847+kylin-dev@users.noreply.github.com>
Co-authored-by: wannam2049 <71331352+wannam2049@users.noreply.github.com>
Co-authored-by: celrisen <78207373+celrisen@users.noreply.github.com>
Co-authored-by: darkfriend77 <darkfriend77@users.noreply.github.com>
Co-authored-by: Agnieszka Olszewska <agnieszka.olszewska@brightinventions.pl>
Co-authored-by: Kasia Łukasiewicz <katarzyna.bulska@gmail.com>
Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com>
Co-authored-by: Hyungsuk Kang <hskang9@gmail.com>
Co-authored-by: Song Zhou <zs@ziorix.com>
Co-authored-by: Mor GUEYE <74042620+morgueye4@users.noreply.github.com>
Co-authored-by: Igor Gulamov <igor.gulamov@gmail.com>
Co-authored-by: Drew Stone <drewstone329@gmail.com>
Co-authored-by: Kevin Zhang <kevin.zhang.canada@gmail.com>
Co-authored-by: steve <39795608+steve1588@users.noreply.github.com>
Co-authored-by: steven <39795608+steven858@users.noreply.github.com>
Co-authored-by: Ana Milić-Štrkalj <48686305+anamst@users.noreply.github.com>
Co-authored-by: dark64 <darem966@gmail.com>
Co-authored-by: Lumena <78696551+lumena-tech@users.noreply.github.com>
Co-authored-by: dego-team <69787970+dego-team@users.noreply.github.com>
Co-authored-by: Marc Blinder <marc@api.market>
Co-authored-by: Nathan Schwermann <schwiz@gmail.com>
Co-authored-by: Bette <42193328+bette7@users.noreply.github.com>
Co-authored-by: Bryan Chen <xlchen1291@gmail.com>
Co-authored-by: Frank Yin <ukby.1234@gmail.com>
Co-authored-by: Shengda Ding <dingshengda@gmail.com>
Co-authored-by: Marcin <marcin@web3.foundation>
Co-authored-by: eva-networks <evanesco.networks@hotmail.com>
Co-authored-by: Filip Pajic <42151917+pajicf@users.noreply.github.com>
Co-authored-by: Sota Watanabe <w.souta.s.life@gmail.com>
Co-authored-by: XPredictMarket <80562134+XPredictMarket@users.noreply.github.com>
Co-authored-by: Toney <74755044+Apron2050@users.noreply.github.com>
Co-authored-by: Ray Lu <ray@codemeit.com>
Co-authored-by: Shannon Christie <20452861+shannon-christie@users.noreply.github.com>
Co-authored-by: arbach <aarbache@gmail.com>
Co-authored-by: arbach <dev@dev.com>
Co-authored-by: Denis <denislam@users.noreply.github.com>
Co-authored-by: yubo-ruan <40745291+yubo-ruan@users.noreply.github.com>
Co-authored-by: Michael (GP) <79423936+GamePowerDev@users.noreply.github.com>
Co-authored-by: Michael Huntington <2466745+MikeHuntington@users.noreply.github.com>
Co-authored-by: J Wagstaff <7297707+rg3l3dr@users.noreply.github.com>
chrisli30 pushed a commit to AvaProtocol/W3F-Grants-Fork that referenced this pull request Apr 19, 2021
* Create vera_defi.md

Initial grant application

* Update grant application

* Replace https with http to fix images link.

* Add more details to the milestone

* Update vera_defi.md

Update bio

* Update vera_defi.md

* Clarification on NFT Lending

* Update vera_defi.md

NFT Token development clarification

* Update vera_defi.md

Fix style

* Update vera_defi.md

Fix style

* Update vera_defi.md

Update scope to focus on AssetManager. Use existing NFT implementation instead of building our own.

* Update vera_defi.md

Update cost

Co-authored-by: arbach <dev@dev.com>
Co-authored-by: Denis <denislam@users.noreply.github.com>
@arbach
Copy link
Contributor Author

arbach commented Jun 23, 2021

Hello web3 team,

Wanted to keep you posted that our work on this was done a while back, we did not have time wrap up the delivery for it yet.

here is the beta app. http://beta.vera.financial/
and recorded demo https://drive.google.com/file/d/16sUVt-wvYdWAUsfupGVtnzWDOvYAbio6/view
and here is the source code https://github.com/veraprotocol/ambrosia

Working on putting together all documents required for the delivery, and submitting as per instruction.

Sorry we are late on this, we had multiple good partnerships that we had to do tech work for that delay this specific project.

Looking forward to continuing the collaboration.

@semuelle
Copy link
Member

Thanks for the update, @arbach. Looking forward to your delivery.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready for review The project is ready to be reviewed by the committee members.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants