XcavateDeveloperLoandApp

Project Name: Xcavate
Team Name: Xcavate
Payment Address: 5E28NSFGwYB9C39bYdRAQ79UKRsM6shxkJr3LG4hehycwfJc

Project Overview
Due to a combination of increased population and changing housing needs, there is global housing crisis. According to the UN, the global population is set to reach over 11.2 billion by the year 2100, therefore 2 billion new homes are required in the next 80 years. 20% of all housing is built by small to medium sized real estate developers but access to finance through traditonal banks and other financial institutions is complex, time consuming and expensive.
Xcavate is looking to solve this issue by developing a completely decentralised lending and NFT protocol to help fund the building of real world real estate assets, as well as transact and manage fractions of each property as a route to a global real estate investor market. Our goal is to create a community of real estate developers, investors and blockchain developers so more houses can be built and invested in to help reach the growing demand.

Overview
Xcavate will be a first-of-its-kind real-world land & property NFT platform that collateralizes real world parcels of land to finance real estate development.
Xcavate facilitates digitizing land and/or property title deeds through minting and bundling of NFTs, which are then linked to verifiable digital identities (DIDs) approved by government entities.
Xcavate is an ecosystem that allows real-world property developers access to finance parcels of physical land with planning permission for development. Once the land is at the final development stage, the developer will create NFTs for the individual properties to be sold/managed by a peer-to-peer marketplace (property owners, investors, trusts etc.).
The system will significantly reduce the time from real estate planning permission to build start. By simplifying the finance application process and speeding up the release of funds to the developer. Xcavate not only provides real-world property developers with a way to build quicker but, as a result, enables a more significant number of much-needed houses to be delivered to market. It also provides liquidity to static real-world assets at every stage of the property development process in a fair and risk-averse way. It will enable the real estate to be onboarded cleanly and efficiently, opening up opportunities throughout the broader Dotsama ecosystem.

Project Details
We will initially build a POC of the real estate developer loan process to prove the concept. Building a simple polkadot.js wallet that allows verification of identity and creation of DIDS (through the KILT protocol). Once land ownership and build value has been identified (using Oracles) then the LAND NFT can be minted and placed in a multi-sig wallet along with the full loan amount (from the community loan pool). Each build tranche of money will be delivered to the real estate developer wallet, once real estate build evidence has been established and verified.

Xcavate will adapt and build multiple Pallets to execute the functionalities. We will use the KILT SDK as well as the substrate framework and primary language Rust to create the pallets on the Polkadot ecosystem.
Token Pallet
Decentralized Identity Document pallet
User Management pallet
Loan Management pallet
Transaction management pallet
Staking pallet
Verification pallet
This Architecture diagram shows the visual representation that maps out the physical implementation for components in the Polkadot ecosystem and how the scalability of the platform works. The diagram represents Microservices we are using to execute the functionality. API gateway will split the API calls to the respective microservices. We are using an s3 bucket to store the media files. We are using pallets to execute the functions on the Polkadot ecosystem.

Token:
XCAV - Platforms Native Token to launch a para chain and participate in a crowd loan/slot auction. XCAV tokens are used to stake within the platform. We will create these tokens with the Transfer, Mint, Burn, Approve, and Allowance functions.
Liquidity Pool:
Xcavate creates a liquidity pool to store staked tokens, staked tokens will be queued and utilized for each loan application. XCAV tokens are swapped as GBPT through XCM and deposited on the Central Loan pool.
Central Loan Pool:
Xcavate Creates a central loan pool to manage Loan amounts and Loan repayment. The central lending pool will act as the heart of the platform to map all the transactions.
Technology Stack
React.js |
Node.js |
Express.js |
Rust |
Substrate Framework |
Polkadot |
Third-Party
Kilt – SDK |
Chainlink |
AWS |
Ecosystem Fit
After many months of research, we initially met on a zoom with Ingo from Kilt, discussing our idea and talking through how the Kilt chain can be incorporated into the Xcavate system. A few weeks later, we contacted Acala and met with Robinson, who was very helpful and enthusiastic about us being involved in the ecosystem and our potential partnership. We also reached Centrifuge and spent many weeks looking through their docs with the initial idea of creating a dApp on their chain, but as there were some striking differences in how their chain operated, it was apparent that was not going to be the best fit for our project. Going forward, however, once the real estate has been built, there will be opportunities for us to introduce Centrifuge.
We feel this is a great way to bring land & Property assets into the digital ecosystem to interact with the following potential partners:
Kilt (Identity & wallet)
This is a crucial part of the initial process to verify; Real Estate Director, Company & Title Deed and create DID’s, which will be held in a polkadot.js wallet and used throughout the process.
Chainlink (Oracle)
To accurately value and risk rate land and the completed real estate, we need to build Oracles that enable off-chain APIs to feed data into an algorithm which delivers the personalized loan APR. In the first phase, we will build a Chainlink Oracle that relies on https://propertydata.co.uk/ for its data.
Statemint / Acala
There are many stages of financing that will involve aUSD / USDT / GDPT… from the initial funding pool, a liquidity pool, as well as the need to exchange the locked loan value for each project in GBP stable coins (as our initial market is based in the UK).
CRUST
Our POC will use AWS to prove the concept, however going forward we will look to host our dApp and all the land and property related documents on the Crust network.
Team :busts_in_silhouette:
Team members
Richard Houldsworth – CTO |
Alex Ward – COO |
Akash Takyar - Management Sponsor |
Deepak Shokeen - Chief Engineer |
Kapil Saxena - Design Head |
Contact
Richard Houldsworth – +44 7798 666 710 |
Alex Ward – +44 7779 885964 |
xcavate.io |
Legal Structure
H & W Investments Limited |
17 College Road, Cheshunt EN8 9LS, United Kingdom |
Team's experience
Richard Houldsworth – 10 years in web 2.0 dev space – serial Entrepreneur
Alex Ward – 25 years in the global property market – serial Entrepreneur
Akash Takyar - Akash has a master’s in computer application with a deep understanding of IoT and Blockchain. Akash is a world-renowned expert, blockchain influencer, and technical architect.
Deepak Shokeen - With over 20 years of experience engineering and developing apps. He has a deep understanding of building Cloud, IoT, and Blockchain applications.
Kapil Saxena - Kapil is a design professional with 15+ years of experience in User Experience & User Interface design. Currently, he is leading
the design team at LeewayHertz designing UX and UI for Blockchain Applications, handheld devices, Artificial Intelligence Solutions, and IoT Products.
Team Code Repos
https://github.com/xcavate2022
https://github.com/LeewayHertz
https://github.com/orgs/XDCFoundation/repositories
https://github.com/XDCFoundation/XDC3Android
https://github.com/XDCFoundation/xdc-testnetwork-leo
Team LinkedIn Profiles
https://www.linkedin.com/in/richard-houldsworth/
https://www.linkedin.com/in/alex-ward-2350a036/
https://www.linkedin.com/company/leewayhertz-technologies/
Development Status :open_book:
We have been heavily involved in learning all things associated with the Polkadot & Kusama Ecosystem. This has been coupled with the idea of bringing land and property from its current state into the web3 ecosystem. We have been meeting with top-level industry leads, government officials and developers.
Robin Ejsmond-Frey and NIco Morgan from Parity have been a tremendous help by supporting us with information about the W3F grant application process and recommendations to attend Hackathons and the Polkadot Decoded Event London. As well as as number of forums to help our substrate development knowledge.
We have been taking time to play with Substrate to form initial local nodes. We feel we are now ready to build the initial POC for this project in the Rococco test environmenment.
Development Roadmap :nut_and_bolt:
Overview

Total Estimated Duration: 2 months
Full-Time Equivalent (FTE):  4
Total Costs: 4732 DOT

Milestone 1 — Initial POC of lending protocol

Estimated Duration: 2 months
FTE:  4
Costs: 4732 DOT

In the first milestone, the features for the PoC will be implemented and tested by limited users.

Number
Deliverables
Specification

0a.
License
Apache 2.0

0b.
Documentation
The documentation will be provided to show the whole achitecture of the Apron Network.

0c.
Testing and Testing Guide
The testing guide will be provided to test each component.

1
Xcavate Node Repo
We will create a customized chain node with Substrate 2.0 Framework.

2
Xcavate Loan App Repo
The contracts will be implemented with Ink!, and it will handle all the API services related functions such as 1) Land planning permission, ownership & DIDs 2) Creation and management of multisig wallet 3) Minting and transfer of LAND NFTs 4) Define the APR of loan 5) Monitor and execute real estate build stage checks 5) Deliver tranches of loan amounts to wallets 6) Manage the loan repayment and NFT transfer.

3.
Decentralized Developer Loan dApp / Front End Repo
It's a webpage working with Xcavate Network, it's implemented based on polkadot.js as planned.

4.
Docker
We will provide a dockerfile to demonstrate the full functionality of our chain

5.
Tutorial
We will write an tutorial about how to use Apron Network.

6.
Article
We will write an article published on media channels.

7.
DAO
An Xcavate DAO will be created to handle the governance of the Decentralized lending protocol.

Future Plans
Once we have built the initial POC, then we will build the POC of the real estate NFT marketplace. Then on to the MVP and GTM. We have already started the white paper as well as developed a pitch deck to demonstrate the potential of the system to; investors, partners and eventually XCAV coin holders. We have started a social media campaign in order to build a community now and through the dApp build & testing stages.
Additional Information :heavy_plus_sign:
We have applied to be a speaker at the 2023 Polkadot Decoded event. We would talk through how Xcavate supported by the Polkadot community and network, can help to build much needed housing to a global population.

Thanks for the feedback :)

Project Name: Xcavate
Team Name: Xcavate
Payment Address: 5E28NSFGwYB9C39bYdRAQ79UKRsM6shxkJr3LG4hehycwfJc

Project Overview
Due to a combination of increased population and changing housing needs, there is global housing crisis. According to the UN, the global population is set to reach over 11.2 billion by the year 2100, therefore 2 billion new homes are required in the next 80 years. 20% of all housing is built by small to medium sized real estate developers but access to finance through traditonal banks and other financial institutions is complex, time consuming and expensive.
Xcavate is looking to solve this issue by developing a completely decentralised lending and NFT protocol governed by a DAO to help fund the building of real world real estate assets, as well as transact and manage fractions of each property as a route to a global real estate investor market. Our goal is to create a Decentralised Autonomous Organisation (DAO), which has a core Fellowship of real estate developers, investors and blockchain developers accountable to its wider community, so more houses can be built and invested in to help reach the growing demand.
Overview
Xcavate will be a first-of-its-kind real-world land & property NFT platform that collateralizes real world parcels of land to finance real estate development.
Xcavate facilitates digitizing land and/or property title deeds through minting and bundling of NFTs, which are then linked to verifiable digital identities (DIDs) approved by government entities.
Xcavate is an ecosystem that allows real-world property developers access to finance parcels of physical land with planning permission for development. Once the land is at the final development stage, the developer will create NFTs for the individual properties to be sold/managed by a peer-to-peer marketplace (property owners, investors, trusts etc.).
The system will significantly reduce the time from real estate planning permission to build start. By simplifying the finance application process and speeding up the release of funds to the developer. Xcavate not only provides real-world property developers with a way to build quicker but, as a result, enables a more significant number of much-needed houses to be delivered to market. It also provides liquidity to static real-world assets at every stage of the property development process in a fair and risk-averse way. It will enable the real estate to be onboarded cleanly and efficiently, opening up opportunities throughout the broader Dotsama ecosystem.
Project Details
We will initially build a POC of the real estate developer loan process to prove the concept. Building a simple polkadot.js wallet that allows verification of identity and creation of DIDS (through the KILT protocol). Once land ownership and build value has been identified (using Oracles) then the LAND NFT can be minted and placed in a multi-sig wallet along with the full loan amount (from the community loan pool). Each build tranche of money will be delivered to the real estate developer wallet, once real estate build evidence has been established and verified.

Xcavate will adapt and build multiple Pallets to execute the functionalities. We will use the KILT SDK as well as the substrate framework and primary language Rust to create the pallets on the Polkadot ecosystem.
Token Pallet
Decentralized Identity Document pallet
User Management pallet
Loan Management pallet
Transaction management pallet
Staking pallet
Verification pallet
This Architecture diagram shows the visual representation that maps out the physical implementation for components in the Polkadot ecosystem and how the scalability of the platform works. The diagram represents Microservices we are using to execute the functionality. API gateway will split the API calls to the respective microservices. We are using an s3 bucket to store the media files. We are using pallets to execute the functions on the Polkadot ecosystem.

Token:
XCAV - Platforms Native Token to launch a para chain and participate in a crowd loan/slot auction. XCAV tokens are used to stake within the platform. We will create these tokens with the Transfer, Mint, Burn, Approve, and Allowance functions.
Liquidity Pool:
Xcavate creates a liquidity pool to store staked tokens, staked tokens will be queued and utilized for each loan application. XCAV tokens are swapped as GBPT through XCM and deposited on the Central Loan pool.
Central Loan Pool:
Xcavate Creates a central loan pool to manage Loan amounts and Loan repayment. The central lending pool will act as the heart of the platform to map all the transactions.
Technology Stack

React.js
Node.js
Express.js
Rust
Substrate Framework
Polkadot

Third-Party

Kilt – SDK
Chainlink
AWS

Ecosystem Fit
After many months of research, we initially met on a zoom with Ingo from Kilt, discussing our idea and talking through how the Kilt chain can be incorporated into the Xcavate system. A few weeks later, we contacted Acala and met with Robinson, who was very helpful and enthusiastic about us being involved in the ecosystem and our potential partnership. We also reached Centrifuge and spent many weeks looking through their docs with the initial idea of creating a dApp on their chain, but as there were some striking differences in how their chain operated, it was apparent that was not going to be the best fit for our project. Going forward, however, once the real estate has been built, there will be opportunities for us to introduce Centrifuge.
We feel this is a great way to bring land & Property assets into the digital ecosystem to interact with the following potential partners:
Kilt (Identity & wallet)
This is a crucial part of the initial process to verify; Real Estate Director, Company & Title Deed and create DID’s, which will be held in a polkadot.js wallet and used throughout the process.
Chainlink (Oracle)
To accurately value and risk rate land and the completed real estate, we need to build Oracles that enable off-chain APIs to feed data into an algorithm which delivers the personalized loan APR. In the first phase, we will build a Chainlink Oracle that relies on https://propertydata.co.uk/ for its data.
Statemint / Acala
There are many stages of financing that will involve aUSD / USDT / GDPT… from the initial funding pool, a liquidity pool, as well as the need to exchange the locked loan value for each project in GBP stable coins (as our initial market is based in the UK).
CRUST
Our POC will use AWS to prove the concept, however going forward we will look to host our dApp and all the land and property related documents on the Crust network.
Team :busts_in_silhouette:
Team members

Richard Houldsworth – CTO
Alex Ward – COO
Akash Takyar - Management Sponsor
Deepak Shokeen - Chief Engineer
Kapil Saxena - Design Head

Contact

Richard Houldsworth – +44 7798 666 710
Alex Ward – +44 7779 885964
xcavate.io

Legal Structure

H & W Investments Limited
17 College Road, Cheshunt EN8 9LS, United Kingdom

Team's experience
Richard Houldsworth – 10 years in web 2.0 dev space – serial Entrepreneur
Alex Ward – 25 years in the global property market – serial Entrepreneur
Akash Takyar - Akash has a master’s in computer application with a deep understanding of IoT and Blockchain. Akash is a world-renowned expert, blockchain influencer, and technical architect.
Deepak Shokeen - With over 20 years of experience engineering and developing apps. He has a deep understanding of building Cloud, IoT, and Blockchain applications.
Kapil Saxena - Kapil is a design professional with 15+ years of experience in User Experience & User Interface design. Currently, he is leading
the design team at LeewayHertz designing UX and UI for Blockchain Applications, handheld devices, Artificial Intelligence Solutions, and IoT Products.
Team Code Repos
https://github.com/xcavate2022
https://github.com/LeewayHertz
https://github.com/orgs/XDCFoundation/repositories
https://github.com/XDCFoundation/XDC3Android
https://github.com/XDCFoundation/xdc-testnetwork-leo
Team LinkedIn Profiles
https://www.linkedin.com/in/richard-houldsworth/
https://www.linkedin.com/in/alex-ward-2350a036/
https://www.linkedin.com/company/leewayhertz-technologies/
Development Status :open_book:
We have been heavily involved in learning all things associated with the Polkadot & Kusama Ecosystem. This has been coupled with the idea of bringing land and property from its current state into the web3 ecosystem. We have been meeting with top-level industry leads, government officials and developers.
Robin Ejsmond-Frey and NIco Morgan from Parity have been a tremendous help by supporting us with information about the W3F grant application process and recommendations to attend Hackathons and the Polkadot Decoded Event London. As well as as number of forums to help our substrate development knowledge.
We have been taking time to play with Substrate to form initial local nodes. We feel we are now ready to build the initial POC for this project in the Rococco test environmenment.
Development Roadmap :nut_and_bolt:
Overview

Total Estimated Duration: 2 months
Full-Time Equivalent (FTE):  4
Total Costs: $30000

Milestone 1 — Initial POC of lending protocol

Estimated Duration: 2 months
FTE:  4
Costs: $30000

In the first milestone, the features for the PoC will be implemented and tested by limited users. The unique structure of a central loan pool, which enables an easy on / off ramp for community loan stakers, could be useful in various other Dotsama chain environments.

Number
Deliverables
Specification

0a.
License
Apache 2.0

0b.
Documentation
The documentation will be provided to show the whole achitecture of the Apron Network.

0c.
Testing and Testing Guide
The testing guide will be provided to test each component.

1
Xcavate Node Repo
We will create a customized chain node with Substrate 2.0 Framework.

2
Xcavate Loan App Repo
The contracts will be implemented with Ink!, and it will handle all the on chain services related functions such as 1) Assess loan application criteria 2) Creation and management of multisig wallet 3) Minting and transfer of LAND NFTs 4) Defining and executing the loan APR structure 5) Monitor and execute real estate build stage checks 5) Deliver tranches of loan amounts to wallets 6) Manage the loan repayment and NFT transfer.

3.
Loan management pallet
* Manage loan application ** Land details' ** Registration * Manage loan interest percentage ** Based on land and experience * Approve/Reject request

4.
Staking pallet
* User can stake native token * Calculate APR * Distribute payouts

5.
Verification pallet
* Verification of user identity * Manage users identity * Manage loan request

6.
DAO
The PoC will have a basic DAO structure that will be created using the OpenGov pallet to ensure rewards can be given to the real estate build stage checkers (As we progress in to the MVP stage this will be expanded to form a full governance structure).

7.
Decentralized Developer Loan dApp / Front End Repo
It's a webpage working with Xcavate Network, it's implemented based on polkadot.js as planned.

8.
Docker
We will provide a dockerfile to demonstrate the full functionality of our chain

9.
Tutorial
We will write an tutorial about how to use Apron Network.

10.
Article
We will write an article published on media channels.

Future Plans
Once we have built the initial POC, then we will build the POC of the real estate NFT marketplace. Then on to the MVP and GTM. We have already started the white paper as well as developed a pitch deck to demonstrate the potential of the system to; investors, partners and eventually XCAV coin holders. We have started a social media campaign in order to build a community now and through the dApp build & testing stages.
Additional Information :heavy_plus_sign:
We have applied to be a speaker at the 2023 Polkadot Decoded event. We would talk through how Xcavate supported by the Polkadot community and network, can help to build much needed housing to a global population.

Many thanks for your comments Sebastian… I believe I have addressed the issues. I look forward to your feedback
Best Regards,
Richard
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 6 Apr 2023, at 08:59, Sebastian Müller @.***> wrote:
@semuelle requested changes on this pull request.
Thanks for the application, @xcavate2022 https://github.com/xcavate2022. A couple of issues:
DOT is not a payment option
Why do you mention Apron Network in your deliverables?
Who or what is responsible for getting the external data into the pallets/contracts? The flow of data is not clear from the architecture diagram.
Can you be more explicit about the technical novelty of your deliverables? For example, what does it mean for the smart contracts to "handle all the API services"? How is the DAO implemented? You don't mention governance until the end.
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#pullrequestreview-1374274854, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7HPUUG4RW3X4ABLGULW7ZZV7ANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

Hi W3F Grant Team, There have been some developments this week that would change the application slightly... before I commit to the changes can I check the details with you first? I have set up a team at the https://web3athon2023.hackerearth.com/ our project is to build the Xcavate Real Estate NFT Marketplace... I have talked about the bigger plan and the W3F Grant to build the Real Estate Developer Loan dApp / node / pallets and a number of the team are keen to join us. I can share the Hackathon repo as part of our application if you feel it will help us? I look forward to hearing from you. All the best Richard

Project Name: Xcavate
Team Name: Xcavate
Payment Address: 5E28NSFGwYB9C39bYdRAQ79UKRsM6shxkJr3LG4hehycwfJc

Project Overview
Due to a combination of increased population and changing housing needs, there is global housing crisis. According to the UN, the global population is set to reach over 11.2 billion by the year 2100, therefore 2 billion new homes are required in the next 80 years. 20% of all housing is built by small to medium sized real estate developers but access to finance through traditional banks and other financial institutions is complex, time consuming and expensive.
Xcavate is looking to solve this issue by developing a completely decentralised lending and NFT protocol governed by a DAO to help fund the building of real world real estate assets, as well as transact and manage fractions of each property as a route to a global real estate investor market. Our goal is to create a Decentralised Autonomous Organisation (DAO), which has a core Fellowship of real estate developers, investors and blockchain developers accountable to its wider community, so more houses can be built and invested in to help reach the growing demand.
Overview
Xcavate will be a first-of-its-kind real-world land & property NFT platform that collateralises real world parcels of land to finance real estate development.
Xcavate facilitates digitising land and/or property title deeds through minting and bundling of NFTs, which are then linked to verifiable digital identities (DIDs) approved by government entities.
Xcavate is an ecosystem that allows real-world property developers access to finance parcels of physical land with planning permission for development. Once the land is at the final development stage, the developer will create NFTs for the individual properties to be sold/managed by a peer-to-peer marketplace (property owners, investors, trusts etc.).
The system will significantly reduce the time from real estate planning permission to build start. By simplifying the finance application process and speeding up the release of funds to the developer. Xcavate not only provides real-world property developers with a way to build quicker but, as a result, enables a more significant number of much-needed houses to be delivered to market. It also provides liquidity to static real-world assets at every stage of the property development process in a fair and risk-averse way. It will enable the real estate to be onboarded cleanly and efficiently, opening up opportunities throughout the broader Dotsama ecosystem.
Project Details
We will initially build a POC of the real estate developer loan process to prove the concept. Building a simple polkadot.js wallet that allows verification of identity and creation of DIDS (through the KILT protocol). Once land ownership and build value has been identified (using Oracles) then the LAND NFT can be minted and placed in a multi-sig wallet along with the full loan amount (from the community loan pool). Each build tranche of money will be delivered to the real estate developer wallet, once real estate build evidence has been established and verified.

Xcavate will adapt and build multiple Pallets to execute the functionalities. We will use the KILT SDK as well as the substrate framework and primary language Rust to create the pallets on the Polkadot ecosystem.
Token Pallet
Decentralised Identity Document pallet
User Management pallet
Loan Management pallet
Transaction management pallet
Staking pallet
Verification pallet
This Architecture diagram shows the visual representation that maps out the physical implementation for components in the Polkadot ecosystem and how the scalability of the platform works. The diagram represents Microservices we are using to execute the functionality. API gateway will split the API calls to the respective microservices. We are using an s3 bucket to store the media files. We are using pallets to execute the functions on the Polkadot ecosystem.

Token:
XCAV - Platforms Native Token to launch a para chain and participate in a crowd loan/slot auction. XCAV tokens are used to stake within the platform. We will create these tokens with the Transfer, Mint, Burn, Approve, and Allowance functions.
Liquidity Pool:
Xcavate creates a liquidity pool to store staked tokens, staked tokens will be queued and utilized for each loan application. XCAV tokens are swapped as GBPT through XCM and deposited on the Central Loan pool.
Central Loan Pool:
Xcavate Creates a central loan pool to manage Loan amounts and Loan repayment. The central lending pool will act as the heart of the platform to map all the transactions.
Technology Stack

React.js
Node.js
Express.js
Rust
Substrate Framework
Polkadot

Third-Party

Kilt – SDK
Chainlink
AWS

Ecosystem Fit
After many months of research, we initially met on a zoom with Ingo from Kilt, discussing our idea and talking through how the Kilt chain can be incorporated into the Xcavate system. A few weeks later, we contacted Acala and met with Robinson, who was very helpful and enthusiastic about us being involved in the ecosystem and our potential partnership. We also reached Centrifuge and spent many weeks looking through their docs with the initial idea of creating a dApp on their chain, but as there were some striking differences in how their chain operated, it was apparent that was not going to be the best fit for our project. Going forward, however, once the real estate has been built, there will be opportunities for us to introduce Centrifuge.
We feel this is a great way to bring land & Property assets into the digital ecosystem to interact with the following potential partners:
Kilt (Identity & wallet)
This is a crucial part of the initial process to verify; Real Estate Director, Company & Title Deed and create DID’s, which will be held in a polkadot.js wallet and used throughout the process.
Chainlink (Oracle)
To accurately value and risk rate land and the completed real estate, we need to build Oracles that enable off-chain APIs to feed data into an algorithm which delivers the personalized loan APR. In the first phase, we will build a Chainlink Oracle that relies on https://propertydata.co.uk/ for its data.
Statemint / Acala
There are many stages of financing that will involve aUSD / USDT / GDPT… from the initial funding pool, a liquidity pool, as well as the need to exchange the locked loan value for each project in GBP stable coins (as our initial market is based in the UK).
CRUST
Our POC will use AWS to prove the concept, however going forward we will look to host our dApp and all the land and property related documents on the Crust network.
Team :busts_in_silhouette:
Team members

Richard Houldsworth – CTO
Alex Ward – COO
Kaioh - Substrate Developer
Ganish Oli - Substrate Developer
Neeraj Choubisa - Full Stack Developer

Contact

Richard Houldsworth – +44 7798 666 710
Alex Ward – +44 7779 885964
xcavate.io

Legal Structure

H & W Investments Limited
17 College Road, Cheshunt EN8 9LS, United Kingdom

Team's experience
Richard Houldsworth – 10 years in web 2.0 dev space – serial Entrepreneur
Alex Ward – 25 years in the global property market – serial Entrepreneur
Ganish Oli - ink! smart contract developer and substrate blockchain developer.
Kaioh - ink! smart contract developer and substrate blockchain developer.
Neeraj Choubisa - A Passionate Full Stack Blockchain Ethereum Based Web Developer, Third-Year student at Indian Institute of Information Technology, Dharwad
Team Code Repos
https://github.com/xcavateblockchain
https://github.com/xcavate2022
https://github.com/gflow33
https://github.com/ganesh1233456
https://github.com/Kali-Decoder
Team LinkedIn Profiles
https://www.linkedin.com/in/richard-houldsworth/
https://www.linkedin.com/in/alex-ward-2350a036/
https://www.linkedin.com/in/ganesh-oli-9285a4163/
https://www.linkedin.com/in/neeraj-choubisa-a4952b202/
Development Status :open_book:
We have been heavily involved in learning all things associated with the Polkadot & Kusama Ecosystem. This has been coupled with the idea of bringing land and property from its current state into the web3 ecosystem. We have been meeting with top-level industry leads, government officials and developers.
Robin Ejsmond-Frey and Nico Morgan from Parity have been a tremendous help by supporting us with information about the W3F grant application process and recommendations to attend Hackathons and the Polkadot Decoded Event London. As well as as number of forums to help our substrate development knowledge.
We have been taking time to play with Substrate to form initial local nodes. We feel we are now ready to build the initial POC for this project in the Rococco test environmenment.
Development Roadmap :nut_and_bolt:
Overview

Total Estimated Duration: 2 months
Full-Time Equivalent (FTE):  4
Total Costs: $30000

Milestone 1 — Initial POC of lending protocol

Estimated Duration: 2 months
FTE:  4
Costs: $30000

We will build on the excellent work we have achieved developing the Real Estate NFT marketplace for the hackerearth.com hackerthon.
In the first milestone, the features for the PoC will be implemented and tested by limited users. We will build a pallet that has a unique structure of a central community loan pool that acts as a risk reducer to allow individual loan stakers to lock and unlock native XCAV coins quickly and easily, rather than being committed to the full term of a particular loan. This will provide an attractive low risk investment opportunity and increase community confidence in the network while eliminating any delay in providing the funds to the real estate development project, once all the necessary checks have been completed. This loan pool structure could be applied to many different chains in future projects.

Number
Deliverables
Specification

0a.
License
Apache 2.0

0b.
Documentation
The documentation will be provided to show the whole architecture of the Xcavate Network.

0c.
Testing and Testing Guide
The testing guide will be provided to test each component.

1
Xcavate Node Repo
We will create a customized chain node with Substrate 2.0 Framework.

2
Xcavate Loan App Repo
All smart contracts will be written in Ink! to handle all the on chain runtime events related pallet functions such as; 1) Assess loan application criteria 2) Creation and management of multisig wallet 3) Minting and transfer of LAND NFTs 4) Defining and executing the loan APR structure 5) Monitor and execute real estate build stage checks 5) Deliver tranches of loan amounts to wallets 6) Manage the loan repayment and NFT transfer.

3.
Loan management pallet
* Manage loan application ** Land details' ** Registration * Manage loan interest percentage ** Based on land and experience * Approve/Reject request

4.
Staking pallet
* User can stake native token * Calculate APR * Distribute payouts

5.
Verification pallet
* Verification of user identity * Manage users identity * Manage loan request

6.
DAO
The PoC will have a basic DAO structure that will be created using the OpenGov pallet to ensure rewards can be given to the real estate build stage checkers (As we progress in to the MVP stage this will be expanded to form a full governance structure).

7.
Decentralized Developer Loan dApp / Front End Repo
It's a webpage working with Xcavate Network, it's implemented based on polkadot.js as planned.

8.
Docker
We will provide a dockerfile to demonstrate the full functionality of our chain

9.
Tutorial
We will write a tutorial about how to use Xcavate Network.

10.
Article
We will write an article published on media channels.

Future Plans
We are talking to Subwallet about integrating the KILT protocol DIDs in to their wallet for a smoother and simpler user experience. Once we have built the initial POC then on to the MVP and GTM. We have already started the white paper as well as developed a pitch deck to demonstrate the potential of the system to; investors, partners and eventually XCAV coin holders. We have started a social media campaign in order to build a community now and through the dApp build & testing stages.
Additional Information :heavy_plus_sign:
We will be attending the 2023 Polkadot Decoded event. We are keen to network and expand our partnerships across the Dotsama Ecosystem, while helping to build much needed real estate investment opportunities to a global population.

Hi Sebastian,
Many thanks for your questions. Please see answers below:

Our road map starts with the UK so yes the initial talks we have had are with the UK government, however the next geographic locations in our roadmap are all countries with similar legal structures and land / property development regulations (Australia, Canada, USA, Ireland, South Africa, Hong Kong & Singapore), there are some local variations which will be built in although those should not affect the core logic. As we establish our protocol then the Xcavate community will decide which geographic locations they wish us to add to the roadmap.

The Land NFT will be a digital representation of the real world asset… a first charge will be made on the land as part of the loan approval process, so it can be sold to another developer should a loan default happen.

All interactive users of any dApp built on top of the Xcavate protocol / will need to have created a personal DID (& company DID) and gone through KYC / AML checks.

General KYC will be made similar to the real world (attested by a trusted party)… for the Land and Property ownership and planning approval then a number of external checks are made with the relevant government (these are public credentials that can be easily verified with an Oracle).

Please let me know if you have any further questions.
Best Regards,
Richard
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 16 May 2023, at 22:55, Sebastian Müller @.***> wrote:
@semuelle commented on this pull request.
Thanks for the updates, @xcavate2022 https://github.com/xcavate2022. I still have a few questions.
You talk about government officials and entities involved. Does this refer to the UK only? Which entities approve DIDs? In what format?
Do you expect the land NFTs to have any legal bearing?
Related: how do you ensure compliance with KYC/AML regulations?
What do you mean by "smart contracts will be written in Ink! to handle all the on chain runtime events related pallet functions"? What are the "runtime events related pallet functions" and what do the smart contracts do with them?
How does the verification pallet work? I assume there will be some manual review/transaction required.
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#pullrequestreview-1429492454, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7CTOBOFH3EHJTDHTNLXGPZTRANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

Sorry I think I missed answering this question.
What do you mean by "smart contracts will be written in Ink! to handle all the on chain runtime events related pallet functions"? What are the "runtime events related pallet functions" and what do the smart contracts do with them?
While the core logic will be written in substrate as pallets… the execution of this logic will depend on a number of parameters which will happen in a deterministic way controlled by smart contracts written in Ink!
Hope that helps explain that specific question
Best Regards,
Richard
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 17 May 2023, at 08:32, richard @.***> wrote:
Hi Sebastian,
Many thanks for your questions. Please see answers below:

Our road map starts with the UK so yes the initial talks we have had are with the UK government, however the next geographic locations in our roadmap are all countries with similar legal structures and land / property development regulations (Australia, Canada, USA, Ireland, South Africa, Hong Kong & Singapore), there are some local variations which will be built in although those should not affect the core logic. As we establish our protocol then the Xcavate community will decide which geographic locations they wish us to add to the roadmap.

The Land NFT will be a digital representation of the real world asset… a first charge will be made on the land as part of the loan approval process, so it can be sold to another developer should a loan default happen.

All interactive users of any dApp built on top of the Xcavate protocol / will need to have created a personal DID (& company DID) and gone through KYC / AML checks.

General KYC will be made similar to the real world (attested by a trusted party)… for the Land and Property ownership and planning approval then a number of external checks are made with the relevant government (these are public credentials that can be easily verified with an Oracle).

Please let me know if you have any further questions.
Best Regards,
Richard
Richard J Houldsworth
m 07798 666 710
www.xcavate.io http://www.xcavate.io/
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 16 May 2023, at 22:55, Sebastian Müller @.*** @.***>> wrote:
@semuelle commented on this pull request.
Thanks for the updates, @xcavate2022 https://github.com/xcavate2022. I still have a few questions.
You talk about government officials and entities involved. Does this refer to the UK only? Which entities approve DIDs? In what format?
Do you expect the land NFTs to have any legal bearing?
Related: how do you ensure compliance with KYC/AML regulations?
What do you mean by "smart contracts will be written in Ink! to handle all the on chain runtime events related pallet functions"? What are the "runtime events related pallet functions" and what do the smart contracts do with them?
How does the verification pallet work? I assume there will be some manual review/transaction required.
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#pullrequestreview-1429492454, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7CTOBOFH3EHJTDHTNLXGPZTRANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

Thanks for the changes @xcavate2022 a couple of additional comments:

I'm still not seeing what payment method you chose. Can you indicate the currency you wish to be paid in next to your provided address?
The "Docker" and "Article" deliverables should be part of the mandatory deliverables 0a. - 0d. can you switch these around so they match our template?

Thanks!

Many thanks for feedback - all updated :)
R
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 17 May 2023, at 23:02, Keegan | W3F @.***> wrote:
Thanks for the changes @xcavate2022 https://github.com/xcavate2022 a couple of additional comments:
I'm still not seeing what payment method you chose. Can you indicate the currency you wish to be paid in next to your provided address?
The "Docker" and "Article" deliverables should be part of the mandatory deliverables 0a. - 0d. can you switch these around so they match our template https://github.com/w3f/Grants-Program/blob/master/applications/application-template.md?
Thanks!
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#issuecomment-1552146314, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7AGFTP3ZX2LFYKU4GDXGVDHRANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

Thanks @xcavate2022

So if I understand correctly, real estate developers would have to join a DAO to use the product? I think this might be a significant barrier to entry. Or is the DAO just for those who want to participate in governance?
What service will you use for the KYC/AML checks?
It sounds like an interesting PoC but I also have doubts about how it would work legally. Have you met with any lawyers or real estate developers to discuss the feasibility and legalities behind land NFTs?
Can you use an existing multi-sig wallet instead of creating your own?

Hi Keegan,
Many thanks for your questions. Please see my answers below:

No it would not be the case that they need to join the DAO (that would just be for governance of the network… software upgrades, signing off treasury spends etc...)… users of the dApp just create DIDs which have verified credentials.
Every real estate developer who needs to take out a development loan to build property, would need to create a personal (if more than one owner of the land is identified then all the owners need verified personal DIDs), company (generally a company would own the land so it would be all the directors that need to sign with their DIDs they accept the terms of the loan) & land DID with credentials that have been verified. The personal DID would be basic KYC information; name & address plus a copy of a passport and utility bill… the company DID would include the company registration number (so the company directors could be checked)… The land DID would include the title deed code (checked with land registry) and the planning permission number (which can be checked with the local authority). I’ve been speaking with the KILT protocol team and we could use Deloitte to carry out KYC & AML.
This process works legally in the real world so all our platform is doing is making it digital and more efficient - my co-founder has been in the international real estate industry for 25 years, we have a large network of real estate developers all of whom have said this is a great idea and would help them build developments easier and quicker. Yes we do have a legal team and we have already run through the legal aspects of the transactions.
Yes we would utilise the multisig FRAME pallet and control it with a smart contract

I hope this sufficiently answers your questions.
Best Regards,
Richard
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 18 May 2023, at 17:59, Keegan | W3F @.***> wrote:
Thanks @xcavate2022 https://github.com/xcavate2022
So if I understand correctly, real estate developers would have to join a DAO to use the product? I think this might be a significant barrier to entry. Or is the DAO just for those who want to participate in governance?
What service will you use for the KYC/AML checks?
It sounds like an interesting PoC but I also have doubts about how it would work legally. Have you met with any lawyers or real estate developers to discuss the feasibility and legalities behind land NFTs?
Can you use an existing https://wiki.polkadot.network/docs/build-open-source multi-sig wallet instead of creating your own?
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#issuecomment-1553346050, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7DOFBWTM5M3UVSV32LXGZINZANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

The Land NFT will be a digital representation of the real world asset… a first charge will be made on the land as part of the loan approval process, so it can be sold to another developer should a loan default happen.

I don't understand what this means, but my main concern was: do the NFTs replace any of the existing legal paperwork? Do they have any legal bearing outside Xcavate?

General KYC will be made similar to the real world (attested by a trusted party)… for the Land and Property ownership and planning approval then a number of external checks are made with the relevant government (these are public credentials that can be easily verified with an Oracle).

Who makes these checks? I don't understand the flow of information between Xcavate, the KYC provider and the credential issuer. I assume these would be matched manually by you?

Hi Sebastian,Just to clarify we will be fully decentralised… therefore the legal standing will be that a “land owner” has taken out a loan (as an individual or a company) with the land NFT as a representation (legal deed ownership) of an asset against the loan (the digital world mirrors the real world)… if a default (failure to repay the loan) occurs, then the real world land asset (represented by the NFT) can be sold to repay the loan (there maybe a small shortfall, which would be be absorbed by the community - based on the number of defaults this will not be a significant number). A legal loan agreement will have been digitally signed by the owner(s) as part of the loan agreement.To address your second point:We will be partnering with the Kilt protocol which will provide decentralised DIDs (each personal digital identity is verified by a professional person - who knows the individual - & has viewed the personal credentials)… however the ownership of the land asset will have additional asset ownership checks (Oracles can easily confirm who owns a particular piece of land based on a check on the land title deed registry). Checks would be based upon the legal jurisdiction the land is in.I appreciate that this can be viewed as quite a complex process to those not in the industry… but I assure you we understand how this works in the real world and will ensure that the digital world simply duplicates what is required in the real world to reduce the risk to the investor while providing a service to the property developer.All the bestRichardSent from my iPhoneOn 25 May 2023, at 20:51, Sebastian Müller @.***> wrote:
The Land NFT will be a digital representation of the real world asset… a first charge will be made on the land as part of the loan approval process, so it can be sold to another developer should a loan default happen.
I don't understand what this means, but my main concern was: do the NFTs replace any of the existing legal paperwork? Do they have any legal bearing outside Xcavate?
General KYC will be made similar to the real world (attested by a trusted party)… for the Land and Property ownership and planning approval then a number of external checks are made with the relevant government (these are public credentials that can be easily verified with an Oracle).
Who makes these checks? I don't understand the flow of information between Xcavate, the KYC provider and the credential issuer. I assume these would be matched manually by you?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Hi Sebastian,Just to clarify we will be fully decentralised… therefore the legal standing will be that a land owner has taken out a loan (as an individual or a company) with the land NFT as a representation (legal deed ownership) of an asset against the loan (the digital world mirrors the real world)… if a default (failure to repay the loan) occurs, then the real world land asset (represented by the NFT) can be sold to repay the loan (there maybe a small shortfall, which would be be absorbed by the community - based on the number of defaults this will not be a significant number). A legal loan agreement will have been digitally signed by the owner(s) as part of the loan agreement.To address your second point:We will be partnering with the Kilt protocol which will provide decentralised DIDs (each personal digital identity is verified by a professional person - who knows the individual - & has viewed the personal credentials)… however the ownership of the land asset will have additional asset ownership checks (Oracles can easily confirm who owns a particular piece of land based on a check on the land title deed registry). Checks would be based upon the legal jurisdiction the land is in.I appreciate that this can be viewed as quite a complex process to those not in the industry… but I assure you we understand how this works in the real world and will ensure that the digital world simply duplicates what is required in the real world to reduce the risk to the investor while providing a service to the property developer.All the bestRichardSent from my iPhoneOn 25 May 2023, at 20:51, Sebastian Müller @.***> wrote:
The Land NFT will be a digital representation of the real world asset… a first charge will be made on the land as part of the loan approval process, so it can be sold to another developer should a loan default happen.
I don't understand what this means, but my main concern was: do the NFTs replace any of the existing legal paperwork? Do they have any legal bearing outside Xcavate?
General KYC will be made similar to the real world (attested by a trusted party)… for the Land and Property ownership and planning approval then a number of external checks are made with the relevant government (these are public credentials that can be easily verified with an Oracle).
Who makes these checks? I don't understand the flow of information between Xcavate, the KYC provider and the credential issuer. I assume these would be matched manually by you?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Just to be 100% clear… no the NFT does not replace the real world legal paperwork… they are just a way of identifying and verifying ownership of the land asset and helping to set out the terms of the loan.
On the KYC let me give you an example:
Bob the builder owns a plot of land… he has planning permission to build 9 apartments. The value of the land is £1,000,000 the cost of the build is £1,000,000 the GDV (or finished build value is £3,000,000. Bob wants to use Xcavate to access the build finance. He accesses the dApp… connects / creates his sporran wallet… creates a personal DID (name, address, email, tel & two forms of ID - passport & utility bill)… which is verified by someone they know (but not a family member or spouse) who has been verified as a professional (lawyer, company director, dentist etc…) with heir own DID. If the land is owned by a company (an oracle checks with land registry) then Bob the builder needs to create a company DID (which is verified by an oracle checking companies house) and all the directors of the company will have to create DIDs and digitally sign a loan agreement… if the loan application meets the predetermined loan to asset value then it is approved by a smart contract. The land asset is then minted as an NFT (a real world lawyer places a charge on the land). A loan pool is also created and both the NFT and the funds are held in a multi sig wallet… funds are delivered in tranches based on the build schedule and as the build progresses a qualified surveyor (in the real world & on the dApp) verifies the build stage so the next tranche can be delivered to the builders wallet.
If the loan is repaid then the NFT is destroyed (and the charge on the land is removed)… if the loan is not repaid the the land NFT (and so the real world asset) is sold to another developer to complete the build.
Hope this clarifies the data / information flow
Best Regards,
Richard.

Not sure if this is necessary but this is some of the work we’ve done on the real estate NFT marketplace (which would be used to repay the real estate developer loan - once the properties have been built)… hopefully seeing the process flows will help to understand more about our project overall.
https://miro.com/app/board/uXjVMRZ1ZuA=/ https://miro.com/app/board/uXjVMRZ1ZuA=/
I’ve also been given a place at the Polkadot Founders Track (June 10th to June 31st)
Best Regards,
Richard
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 26 May 2023, at 06:52, Richard - Xcavate @.***> wrote:
Just to be 100% clear… no the NFT does not replace the real world legal paperwork… they are just a way of identifying and verifying ownership of the land asset and helping to set out the terms of the loan.
On the KYC let me give you an example:
Bob the builder owns a plot of land… he has planning permission to build 9 apartments. The value of the land is £1,000,000 the cost of the build is £1,000,000 the GDV (or finished build value is £3,000,000. Bob wants to use Xcavate to access the build finance. He accesses the dApp… connects / creates his sporran wallet… creates a personal DID (name, address, email, tel & two forms of ID - passport & utility bill)… which is verified by someone they know (but not a family member or spouse) who has been verified as a professional (lawyer, company director, dentist etc…) with heir own DID. If the land is owned by a company (an oracle checks with land registry) then Bob the builder needs to create a company DID (which is verified by an oracle checking companies house) and all the directors of the company will have to create DIDs and digitally sign a loan agreement… if the loan application meets the predetermined loan to asset value then it is approved by a smart contract. The land asset is then minted as an NFT (a real world lawyer places a charge on the land). A loan pool is also created and both the NFT and the funds are held in a multi sig wallet… funds are delivered in tranches based on the build schedule and as the build progresses a qualified surveyor (in the real world & on the dApp) verifies the build stage so the next tranche can be delivered to the builders wallet.
If the loan is repaid then the NFT is destroyed (and the charge on the land is removed)… if the loan is not repaid the the land NFT (and so the real world asset) is sold to another developer to complete the build.
Hope this clarifies the data / information flow
Best Regards,
Richard.

Thanks @xcavate2022 for your time and effort with this application. I will also not approve the application at this time due to the concerns discussed above, as well as the fact that I'm not sure how these pallets benefit the overall Polkadot & Kusama ecosystem. However please take a look at our open RFPs to see examples of some of the things we are looking for.

Hi David,
I’ve spoken to the team (its now a core of six) and for the next 4-6 weeks we are concentrating on the build of the Xcavate real estate NFT marketplace (and the basic Xcavate node network core logic), which will have ink! contracts to execute a number of the dApp specific logic functions.
If I submit a new W3F grant application just for the ink! contracts… should only require a grant of $10000 USD… do you think that might have a better chance of success?
All the best
Richard
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 31 May 2023, at 07:36, David Hawig @.***> wrote:
@Noc2 requested changes on this pull request.
Thanks for the application. I personally would be willing to support at least the ink! related development. I think we need more projects that leverage ink! smart contracts. Could you focus on these with your application? Additionally, it's currently not clear to me how the staking pallet or the verification pallet are different from existing solutions. If you simply reuse other pallets here, I would suggest to remove them. Furthermore, it would be nice if you could improve the formatting, e.g.
"Token Pallet Decentralised Identity Document pallet User Management pallet Loan Management pallet Transaction management pallet Staking pallet Verification pallet"
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#pullrequestreview-1452308053, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7CIISHLDCD2Q4FBWLLXI3RIXANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

Amazing… yes I’ll certainly do that asap
Thank you
R
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 8 Jun 2023, at 14:58, Keegan | W3F @.***> wrote:
Thanks for the update @xcavate2022 https://github.com/xcavate2022, reducing the price to 10k would fall under a level 1 grant and therefore only need two approvals. So based on this fact alone I think there would be a better chance of success. But also, since we haven't worked with your team before, this would give us a chance to see some of your work and allow you to build a rapport with us. If we like the work, this usually also helps in getting bigger/more expensive follow-up grants approved in the future.
Personally, I'd be willing to support a level 1 grant for the ink! contracts, so that's one approval already. Also, you don't necessarily need to submit a new application. You can just refactor this one if you'd like, and change the level on the PR accordingly.
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#issuecomment-1582626805, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7CARWDN3PVV6QYSTRDXKHK63ANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

I’ve revised the application if you can review and comment I’d really appreciate it.
All the best
Richard
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 8 Jun 2023, at 14:58, Keegan | W3F @.***> wrote:
Thanks for the update @xcavate2022 https://github.com/xcavate2022, reducing the price to 10k would fall under a level 1 grant and therefore only need two approvals. So based on this fact alone I think there would be a better chance of success. But also, since we haven't worked with your team before, this would give us a chance to see some of your work and allow you to build a rapport with us. If we like the work, this usually also helps in getting bigger/more expensive follow-up grants approved in the future.
Personally, I'd be willing to support a level 1 grant for the ink! contracts, so that's one approval already. Also, you don't necessarily need to submit a new application. You can just refactor this one if you'd like, and change the level on the PR accordingly.
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#issuecomment-1582626805, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7CARWDN3PVV6QYSTRDXKHK63ANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

Many thanks for the feedback - I think I have done what you have asked… please check & advise any further changes
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 12 Jun 2023, at 16:56, Keegan | W3F @.***> wrote:
@keeganquigley requested changes on this pull request.
Thanks for the changes @xcavate2022 https://github.com/xcavate2022 and for reducing the scope of your PoC. A couple small things:
Can you specify the payment currency next to the address? I see you have a substrate address, but do you wish to be paid in USDT via Statemint/Statemine? If so, can you specify whether you prefer the payment on Polkadot or Kusama?
Right now your initial PR displays your application. Can you integrate the pull request template https://github.com/w3f/Grants-Program/blob/master/.github/pull_request_template.md at the top, in order to mark it as a level 1? You can also get rid of the application and delivery parts if you'd like, since these will be merged into the applications folder when it is accepted. Here is an example https://github.com/w3f/Grants-Program/pull/1791 of what the PR should look like. Thanks!
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#pullrequestreview-1475264726, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7C2RYSXLVBWY27XBE3XK4323ANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

:))  so sorry about the confusion… its been a long weekend
many thanks for all your help… I’ve just updated the application
R
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 12 Jun 2023, at 17:46, Keegan | W3F @.***> wrote:
@keeganquigley requested changes on this pull request.
Thanks @xcavate2022 https://github.com/xcavate2022 the payment currency looks good now. However, the rest of the PR template should actually be changed in the PR description itself, instead of in the application. I'm realizing now that I may have made that more confusing, because I was asking for changes in two places. My apologies!
I went ahead and updated the PR for you. If that looks good, please remove the checklist from the application (but leave in the updated payment method). I hope that makes sense. Thanks!
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#pullrequestreview-1475369115, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7B25SKUIUEOTAGNM3LXK5BXXANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

Sorry we have had a slight delay due to technical issues with integrating the Kilt Sporran wallet / developing the marketplace MVP… we should be starting the W3F grant focused Xcavate Lending Protocol in the next week, so milestone completed in the next 7/8 weeks from now.
Best Regards,
Richard
Richard J Houldsworth
m 07798 666 710
www.xcavate.io

Hi All,
I hope you are well?
We have been extremely busy building our MVP and while there are a couple of things that are not quite complete like the loan staking pallet (due to complexity and time) we feel we have completed enough of the milestone to have this signed off (maybe creating a new milestone to build further on this project). Will you need to see a fully functioning frontend MVP to sign this off? or will you just review the code in our repo?
I look forward to your advice
Best Regards,
Richard
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 12 Jun 2023, at 19:56, github-actions[bot] @.***> wrote:
Congratulations and welcome to the Web3 Foundation Grants Program! Please refer to our Milestone Delivery repository https://github.com/w3f/Grant-Milestone-Delivery/ for instructions on how to submit milestones and invoices, our FAQ https://github.com/w3f/Grants-Program/blob/master/docs/faq.md for frequently asked questions and the support section of our README https://github.com/w3f/Grants-Program/blob/master/README.md#support for more ways to find answers to your questions.
Before you start, take a moment to read through our announcement guidelines https://github.com/w3f/Grants-Program/blob/master/docs/Support Docs/announcement-guidelines.md for all communications related to the grant or make them known to the right person in your organisation. In particular, please don't announce the grant publicly before at least the first milestone of your project has been approved. At that point or shortly before, you can get in touch with us at @.*** @.***> and we'll be happy to collaborate on an announcement about the work you’re doing.
Lastly, please remember to let us know in case you run into any delays or deviate from the deliverables in your application. You can either leave a comment here or directly request to amend your application via PR. We wish you luck with your project! 🚀
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#issuecomment-1587897541, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7AFSVJACPUBLTHBLLDXK5Q6LANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

Hi @xcavate2022 thanks for the update!
To answer your question, the evaluator will want to see that the core software works as expected according to the milestone table(s). Usually the easiest way is typically to provide a Dockerfile or Docker Compose to spin up any nodes, unit tests and/or integration tests, e2e tests, etc. and a testing guide with a demo/tutorial of any working software. Essentially, the delivery should be broken down into the same deliverables in the original application.
After taking a look at your application, I see that your front-end focus was rather small, with one deliverable noting that there will be a "working webpage". So I think in your case a static web page app would suffice.
That being said, it's entirely possible for us to use and test your contracts and pallets using only Polkadot.js and not a custom front-end. Therefore I think that leaves you two options:

You still have two months left before the milestone is due. Since you are ahead of schedule, you could take these two months to build the front-end before submitting the delivery.
If you'd rather do it in a follow-up grant, you can submit an amendment to the original application to remove deliverable 7 and drop the price a bit. This would most likely get approved quickly, and then you could submit the milestone as is and apply for a follow-up grant.

I hope that helps! Let me know if you have further questions.

Many thanks Keegan… I don’t think we need to wait…. we have sufficient milestone evidence… I just think we need to create the Docker file. I’ll ask my team to do that now
Much appreciated
R
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 22 Aug 2023, at 15:28, Keegan | W3F @.***> wrote:
Hi @xcavate2022 https://github.com/xcavate2022 thanks for the update!
To answer your question, the evaluator will want to see that the core software works as expected according to the milestone table(s). Usually the easiest way is typically to provide a Dockerfile or Docker Compose to spin up any nodes, unit tests and/or integration tests, e2e tests, etc. and a testing guide with a demo/tutorial of any working software. Essentially, the delivery should be broken down into the same deliverables in the original application.
After taking a look at your application, I see that your front-end focus was rather small, with one deliverable noting that there will be a "working webpage". So I think in your case a static web page app would suffice.
That being said, it's entirely possible for us to use and test your contracts and pallets using only Polkadot.js and not a custom front-end. Therefore I think that leaves you two options:
You still have two months left before the milestone is due. Since you are ahead of schedule, you could take these two months to build the front-end before submitting the delivery.
If you'd rather do it in a follow-up grant, you can submit an amendment https://github.com/w3f/Grants-Program#changes-to-a-grant-after-approval to the original application https://github.com/w3f/Grants-Program/blob/master/applications/Xcavate.md to remove deliverable 7 and drop the price a bit. This would most likely get approved quickly, and then you could submit the milestone as is and apply for a follow-up grant.
I hope that helps! Let me know if you have further questions.
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#issuecomment-1688298665, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7GAD2AJZQ2G6QSHGLTXWS6XPANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

Hi Guys,
Hope you are well?
I wonder if you can clarify something… We are trying to create a Docker image of the Xcavate Substrate Node but because there have been a number of SP Core updates (among others) its throwing out lots of errors… The node works perfectly well when running just using VS code, so is it possible for your team to assess the submission without the Docker File please?
Best Regards,
Richard
Richard J Houldsworth
m 07798 666 710
www.xcavate.io
CONFIDENTIALITY: This email and its attachments are confidential to the intended recipient only. They may not be used by, disclosed to or copied in any way to anyone other than the intended recipient. If this email is received in error, please contact @.***
Disclaimer STRICTLY CONFIDENTIAL The contents of this email and any attachments are confidential and intended solely for the organisation or individual to whom it is addressed. If you are not the intended recipient, you must not copy, print, forward, distribute or disseminate the information, or take any action in reliance of it. If you have received this message in error, do not open any attachment but please notify the sender above and delete this email from your system.

On 22 Aug 2023, at 15:28, Keegan | W3F @.***> wrote:
Hi @xcavate2022 https://github.com/xcavate2022 thanks for the update!
To answer your question, the evaluator will want to see that the core software works as expected according to the milestone table(s). Usually the easiest way is typically to provide a Dockerfile or Docker Compose to spin up any nodes, unit tests and/or integration tests, e2e tests, etc. and a testing guide with a demo/tutorial of any working software. Essentially, the delivery should be broken down into the same deliverables in the original application.
After taking a look at your application, I see that your front-end focus was rather small, with one deliverable noting that there will be a "working webpage". So I think in your case a static web page app would suffice.
That being said, it's entirely possible for us to use and test your contracts and pallets using only Polkadot.js and not a custom front-end. Therefore I think that leaves you two options:
You still have two months left before the milestone is due. Since you are ahead of schedule, you could take these two months to build the front-end before submitting the delivery.
If you'd rather do it in a follow-up grant, you can submit an amendment https://github.com/w3f/Grants-Program#changes-to-a-grant-after-approval to the original application https://github.com/w3f/Grants-Program/blob/master/applications/Xcavate.md to remove deliverable 7 and drop the price a bit. This would most likely get approved quickly, and then you could submit the milestone as is and apply for a follow-up grant.
I hope that helps! Let me know if you have further questions.
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1649#issuecomment-1688298665, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2OSX7GAD2AJZQ2G6QSHGLTXWS6XPANCNFSM6AAAAAAWRWY4KA.
You are receiving this because you were mentioned.

Hi @xcavate2022,
the Dockerfile is supposed to make testing easier for us. Depending on your architecture, this could also be done using a Makefile, any other kind of script or automation, or even thorough testing documentation. Without knowing the details, I cannot tell for sure, but I suggest you submit the milestone and provide whatever testing environment you can.

Many thanks Sebastian thanks really helpful… we will include as much as we can to make testing as easy as possible for you.On 1 Sep 2023, at 20:42, Sebastian Müller @.***> wrote:
Hi @xcavate2022,
the Dockerfile is supposed to make testing easier for us. Depending on your architecture, this could also be done using a Makefile, any other kind of script or automation, or even thorough testing documentation. Without knowing the details, I cannot tell for sure, but I suggest you submit the milestone and provide whatever testing environment you can.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Extract geographic coverage via NLP

Identifying the geographical coverage of the models and data behind the project could be very interesting to detect areas without coverage. This could also be for help to find projects for a specific geographical area they are interested in.

Agree, this would be valuable information. You mentioned NLP, do you have an idea where to get this info from? Any reliable/consistent source?

I never worked with NLP but did some investigations in the past:
This framework could be useful for many application to extract more data from the projects:
https://github.com/RaRe-Technologies/gensim
On the website repo we also have an issue that is talking about this problem:
https://github.com/protontypes/open-sustainable-technology/issues/110
In my view, a first step to get started with NLP would be to create missing topic labels for the projects. For this, one could use the README of the already created projects and their topic as training data. For about 50% of the projects, the topics are missing and could be added to the database in this way.
This would be a clear improvement of the database, would enable much better searches and would also be very interesting in the analysis.

I think there are several approaches we can consider here. {gensim} uses a pretty simple bag-of-words approach for topic modelling (unsupervised ML) and this method can be effective but very sensitive to corpora content and text-cleaning preprocessing steps, as well as our wild guess of how many topics there may be in the first place. Alternatively, we can see if there's a systematic way we could scrape this information directly from the project's GitHub repo's website and/or (big one!) train a simple supervised algorithm to classify the repo based on the content of README. LOTS OF FUN 💯

I think there are several approaches we can consider here. {gensim} uses a pretty simple bag-of-words approach for topic modelling (unsupervised ML) and this method can be effective but very sensitive to corpora content and text-cleaning preprocessing steps, as well as our wild guess of how many topics there may be in the first place. Alternatively, we can see if there's a systematic way we could scrape this information directly from the project's GitHub repo's website and/or (big one!) train a simple supervised algorithm to classify the repo based on the content of README. LOTS OF FUN 100

That should be feasible. I never worked with such frameworks just the classical CNNs for image processing so far.
The simplest information we could extract from the READMEs is the linked DOIs URLs. This data could be of importance for classification and labeling. After randomly selecting a few projects from the list almost all of them have DOI URLs to papers related to them. Adding this to the existing data mining script should not be a problem but It could increase the runtime by increasing the number of API calls needed per project.

Had some success last night with the DOI extraction. More details in the separated issue https://github.com/protontypes/AwesomeCure/issues/14.
The new list is compiling a now CSV file at the moment. It looks like we are getting DOI links for about a quarter of the projects, but we are still missing some.
Let us see if there are open source tools that give us more contextual information based on the DOIs.


Misleading docstring for component.setDimension()

Misleading docstring on setDimension method caused some minor confusion.
Testing the method indicates the cold flag sets the dimension of the component at cold temperature to val.
It does not set the dimension of the component at cold temperature such that the thermally expanded hot dimension matches val
https://github.com/terrapower/armi/blob/b1658e4a733751213c452b22661830e5ce2f9d9a/armi/reactor/components/component.py#L794-L796

So not so much misleading as wrong?

So, the only use of the cold flag on Component.setDimension() is this one line:
https://github.com/terrapower/armi/blob/b1658e4a733751213c452b22661830e5ce2f9d9a/armi/reactor/components/component.py#L809
So, the docstring doesn't sound too far off.
What do you think it should say?

The docstring for the cold flag should just say If True sets the component cold dimension to the specified value.
Currently, the flag description implies that c.setDimension("op", 30.0, cold=True) will set the cold dimension to a thermally contracted value such that the hot dimension is 30.0 which is completely different behavior from what it actually does. It sets the component cold dimension to be 30.0 which is correct behavior imo. So no changes requested in the method, just the docstring.

@jasonbmeng PR opened over here.


Create the pipeline.

Select Easy-to-use prebuilt modules.
IS NOT VISIBLE

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0c40f439-613c-e09d-9d5a-8c6001c47417
Version Independent ID: 185d3a30-b35b-cc5f-f374-f2881a1fccf6
Content: Tutorial: Predict automobile price with the designer - Azure Machine Learning
Content Source: articles/machine-learning/tutorial-designer-automobile-price-train-score.md
Service: machine-learning
Sub-service: core
GitHub Login: @PeterCLu
Microsoft Alias: peterlu

@baltmann Thanks for brining this to our notice. The option to select "Easy-to-use prebuilt modules" is available once you click on the "Designer" tab on the left. Please find the screen shot below.

@PeterCLu Could you please update the screen shot in the document to display the option "Easy-to-use prebuilt modules" ?

Hi Rohit,
Here’s my page.
Do I have to “upgrade this workspace to Enterprise edition ….”?
Bill
<EMAIL_ADDRESS>From: RohitMungi-MSFT<EMAIL_ADDRESS>Sent: Tuesday, 14 January 2020 16:23
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: baltmann<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Create the pipeline. (#46100)
@baltmannhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbaltmann&data=02|01||5bed555c34cf4b9b79f808d798b1d568|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637145761858106863&sdata=V94Wj7YT4YC0HfKRCfliDrWLxNGwBRoXP%2B4jvh9q1rc%3D&reserved=0 Thanks for brining this to our notice. The option to select "Easy-to-use prebuilt modules" is available once you click on the "Designer" tab on the left. Please find the screen shot below.
[image]https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F46958063%2F72316328-cfb8cb00-36bb-11ea-88b1-31570d45434c.png&data=02|01||5bed555c34cf4b9b79f808d798b1d568|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637145761858116868&sdata=4gKA%2BAd4bRICsfOYajdpDW32uuDRvjpFhr7mRKtLwWQ%3D&reserved=0
@PeterCLuhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPeterCLu&data=02|01||5bed555c34cf4b9b79f808d798b1d568|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637145761858116868&sdata=gFRbLllMQu7Sn6SOPJVBDB0uybszOXvxOJ8iWSoXq0A%3D&reserved=0 Could you please update the screen shot in the document to display the option "Easy-to-use prebuilt modules" ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F46100%3Femail_source%3Dnotifications%26email_token%3DAAPC7ANQP4XNJGKGZIRI453Q5VD3TA5CNFSM4KGMPB2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI3KOCA%23issuecomment-574007048&data=02|01||5bed555c34cf4b9b79f808d798b1d568|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637145761858126878&sdata=mbJlO7DDt10RjwpTAsm5J2h8bk6hnbu%2BhdnuFMt2Sr8%3D&reserved=0, or unsubscribehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAPC7AOUO26CIUPPAQCKOPDQ5VD3TANCNFSM4KGMPB2A&data=02|01||5bed555c34cf4b9b79f808d798b1d568|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637145761858126878&sdata=K%2BOt%2F%2BeGpmxjSdEb%2BQIcE56g2DT82RX630W3cgy91GY%3D&reserved=0.

@baltmann To use the designer an upgrade is required to the Enterprise edition.

@RohitMungi-MSFT , I can update the screenshot to avoid similar issues in the future.
@baltmann, please let us know if we have resolved your issue. If we haven't heard back from a few days, we will proceed to close this issue. Thank you.


Adding .editorconfig file

Adding an .editorconfig file promotes development environment neutrality, while enforcing a consistent spacing style that doesn't require manual configuration by each developer. Fixes #158

I think we should stick with language standards as far as tab widths go.  Scala calls for 2 in its standards doc, but Python, Java, Javascript  and Groovy all go with 4.  Not sure about some of the others you've listed.  I think Python even goes so far as to call out spaces instead of tabs, which probably causes some people out there a lot of sleepless nights.

Completely agree. My preference would be the language-standard: 2 spaces instead of tabs for JS/JSON and Scala, 4 spaces instead of tabs for Python/Java with no actual tabs used anywhere. But I was basing this on the actual tiles code, where I found actual tabs used in almost every file I looked at.

I think all of the code was initially done with tabs, so we'll just roll with it.  If you could update the widths as mentioned above, I'll merge.


Finished back-end implementation of the new @fold representation.

Also fixes an unfortunate bug with @filter directives -- if more than two were present at the same location, some of the filters would get dropped.
I added lots of test cases for the bug and for the new functionality.
The final remaining thing is updating the documentation to state that filtering and type coercions are now allowed within @fold scopes.

Coverage increased (+0.09%) to 94.07% when pulling d5a04965e13ff09089a5773ab1dafdea04c78015 on filtering_in_fold_final into a3267426af47b05ffa735eac28ca0b93717991af on filtering_in_fold_scopes.

Coverage decreased (-0.2%) to 93.786% when pulling 08c5a7963b7eca75e046cbc0c4950c130e033e99 on filtering_in_fold_final into a3267426af47b05ffa735eac28ca0b93717991af on filtering_in_fold_scopes.