-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 polkakeeper.md #200
Conversation
There was a problem hiding this 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. In general this sounds interesting. However, it might be a little bit early for this kind of application in our ecosystem or do you have already specific “jobs” in mind. Did you already play around with ink!, substrate or rust and have some code which you could share?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor questions from me:
@Noc2 Yes, we believe that for each blockchain in the Defi space, there needs to be proper infrastructure in place as growth of the eco-system develops. Hence we are building up important lego pieces for Vault and Liquidation functionality that can be called to manage the risk within projects. Our developers have the foundational level understanding of substrate and rust and are deep diving in research to develop this project. We have updated our PR to reflect specifically the Vault and Liquidation functionality. |
There was a problem hiding this 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. Makes sense. Regarding the Technical Milestones, could you restructure these? We generally focus on the development of open source software, which can potentially be reused by others in the ecosystem. So, we wouldn’t support the integration into the parachain or testing as part of the roco integration. Instead we would rather have the concrete open source deliveries as part of the delivery table, e.g. runtime module, ui etc. plus the specification of these (e.g. functions, programing language, etc.).
@Noc2 : We have updated our PR and restructured the Technical Milestones to make it more concrete with clear open source deliveries of reusable components in each milestone. Included also a Technical Stack Specification for clarity. |
There was a problem hiding this 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, but now your milestones no longer have a payment associated with them. So does your complete project consist of a single milestone? Also milestone one says only “the pallets” without specifying which pallets.
@Noc2 We have updated our PR to reflect the individual Milestone payments attached to each Milestone. There are a total of 3 milestones stated for this project. The Pallets refer to the Vault, Liquidator and LiquidatorAdaptor Pallets as described. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the late reply and thanks for the update. I have a two additional comments/questions:
- Could you also integrate the license into the deliveries 2 and 3?
- What is the difference between milestone 1, 2 and 3? It’s currently very difficult for us to evaluate the deliveries. For example what features will the finished ui support, which aren’t already implemented as part of milestone 2. The same is true for the pallets. Could you be more specific about the functionality of the different delivieries?
- Also it would be nice to have a good unit test coverage for milestone 3.
Added UI User stories, and more detail on the milestones
|
Thanks again for the quick response and update. @coostendorp still needs to sign the CLA, once this is done, please ping me and I will share it with the rest of the team. |
Hey @Noc2 , thanks for the quick reply. @coostendorp has signed the CLA too. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I will share it with the rest of the team.
Thanks @Noc2 |
Hey @semuelle , PR has been updated since. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per the code comments, I would be reluctant to fund M1, which would result only in placeholders that don't contribute much, in my opinion.
applications/polkakeeper.md
Outdated
| Deliverable | Description | | ||
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------- | | ||
| License | All code will be open-sourced under the MIT license and shared in github or gitlab. We welcome contribution and reuse. | | ||
| Source code| Vault, Liquidator and LiquidatorAdaptor pallets all implemented with basic (<30%) unit test coverage.| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you outline the difference in functionality between Milestone 2 and 3, apart from unit test coverage? Will the solution be feature-complete by the end of M2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mmagician besides the unit test coverage, the other key difference between milestone 2 and 3 is that milestone 2 would be feature complete for internal use but would not yet be connected to a real chain for general use whereas milestone 3 would be connected to a real chain and ready for general public use.
applications/polkakeeper.md
Outdated
|
||
### Technical Milestones | ||
|
||
#### Milestone 1: Preparation (0.10 BTC) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see any concrete benefit of M1 as a standalone delivery, since the code that you propose to develop (pallet outlines & substrate node template) is readily available from official substrate repos & unless I am missing something, the only thing to be done here is replacing placeholders with the names of your pallets.
Furthermore, design specifications are expected to be part of the grant application and as such, are not explicitly funded.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mmagician we have collapsed milestone 1 & milestone 2 together and adjusted the milestone payout. There are now only 2 milestones with milestone 1 being feature-complete for internal use (working internal POC not connected to a real chain) and milestone 2 being ready for general use (fully functional and compatible with real chain) by the public.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, thanks for the updates and good luck with the development!
Congratulations! As part of the Open Grants Program, we want to help winning teams acknowledge their grants publicly while observing the foundation’s guidelines. To that end, we’ve created a badge for grant-winning teams. Here is a link to the download and guidelines. |
Thank you @Noc2 @RouvenP @mmagician ! Our team is excited to be able to contribute :) |
* 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>
* 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>
Hi @Noc2 @mmagician @RouvenP, we've been working on our pallets but having some trouble compiling due to substrate bug. We've had help from 2 support engineers but have still not been able to get things working. Would you be able to guide us technically or point us in the correct direction? Here's the link to detail out the error and issue. https://docs.google.com/document/d/1e6GuwP7fvgJK1VYaZ_gJ4DtPfXuMd8lmAI7RRvEV4h8/edit?usp=sharing Appreciate any help! |
Hi @RAMPDEFITEAM. Unfortuately we don't usually provide technical support in the context of the grants program (see README). Besides, I'm afraid if two Parity engineers haven't been able to help, chances are neither will we. You'll have better chances of getting an answer on one of the resources listed here, in particular the Substrate Technical Element chat or Stack Overflow. I hope you can resolve the issue soon, but do let us know if you're out of options and we'll see what we can do. |
Hi Aleixo,
Thanks for your reply.
Would try those and if it doesn't work will reach out again.
Cheers!
RAMP DEFI TEAM
…On Fri, 28 May 2021 at 18:55, Aleixo Sánchez ***@***.***> wrote:
Hi @RAMPDEFITEAM <https://github.com/RAMPDEFITEAM>. Unfortuately we don't
usually provide technical support in the context of the grants program (see
README <https://github.com/w3f/Open-Grants-Program#support>). Besides,
I'm afraid if two Parity engineers haven't been able to help, chances are
neither will we. You'll have better chances of getting an answer on one of
the resources listed here <https://substrate.dev/en/community>, in
particular the Substrate Technical Element chat or Stack Overflow.
I hope you can resolve the issue soon, but do let us know if you're out of
options and we'll see what we can do.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#200 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQ2JKTZ255WMUCADCV3WDB3TP5ZBTANCNFSM4WCG4DUA>
.
|
@RAMPDEFITEAM I hope you managed to get past those issues. Unless you're planning to deliver milestone 1 in the near future, could you please submit an amendment to your application to update the duration or include an ETA? |
Quick heads-up that since we haven't heard from you in a while and there's no significant activity on your public repositories, we would terminate the grant in the coming days. If you're still interested in delivering 1 in the foreseeable future, please briefly let us know. |
Grant Application Checklist