Polkassembly discussion post can be found at [this link](https://polkadot.polkassembly.io/post/1802).

BOTLabs GmbH, the initial developer of KILT Protocol, is requesting funds from the Polkadot Treasury for work on the Decentralized Identity Provider (DIP), which has been ongoing for a few months now.
The KILT Decentralized Identity Provider (DIP) brings an [OpenID](https://openid.net/)-like authentication flow into Web3 by providing the building blocks to establish an open cross-chain identity ecosystem using a combination of on-chain and off-chain mechanisms, initially based on XCM v3. The DIP is a protocol whose initial design has been carried out by BOTLabs, the initial developer of KILT, and which results in infrastructure work (i.e., pallets and crates) that other projects can integrate into their runtimes. The protocol allows any chain to become an identity provider, with other parachains able to choose the identity providers they want to cooperate with, opening up a free market for identity rather than a monopoly. KILT will be the first mover, but it is opening up space for other identity projects to enter the ecosystem and use DIP, beyond contributing to the overall DIP vision.


 The full proposal with the history of changes can be found here (read-only access): [https://docs.google.com/document/d/1-04dherCsMCDqVfwnGF8ZzCI1cOfSjbaBe4Jv4ilcjY](https://docs.google.com/document/d/1-04dherCsMCDqVfwnGF8ZzCI1cOfSjbaBe4Jv4ilcjY).
# How to verify the document integrity
The current version of the proposal document has been digitally signed with one of the DIDs that BOTLabs GmbH controls. To verify the signature:
1.	Download the PDF version of the Google Document linked above.
2.	Download the DID signature of the file from IPFS, with CID QmfDECBY1c7BCTR2A6QVfQPnrjQ6V4jdw2EmnWjYhs2on1 (e.g., [ipfs.io](https://ipfs.io/ipfs/QmfDECBY1c7BCTR2A6QVfQPnrjQ6V4jdw2EmnWjYhs2on1)). Save the file with *dip-proposal.didsign*.
3.	Visit didsign.io, and upload both the PDF file and the downloaded signature. The signature should verify correctly and link to the KILT tx in which the timestamp was generated.
4.	To verify the back-link from the DID to the account to which the funds must be sent if the Proposal is accepted, copy the account in the Proposal (15oXzySe6tjF2MumHfUodH8pFQWjy2hraRmXUJXXMKKY6p3F for quick reference) and paste it in [w3n.id](https://w3n.id/). The account must be linked to the same web3name that signed the proposal document, i.e., [w3n:botlabs_dip](https://w3n.id/botlabs_dip).
# Further Discussions
Please post any questions/concerns/feedback in one of the following ways:

* In the comments section below
* In the Polkadot Direction Element channel
* Using one of the contacts included at the end of the proposal document


BOTLabs GmbH, the initial developer of KILT Protocol, is requesting funds from the Polkadot Treasury for work on the Decentralized Identity Provider (DIP), which has been ongoing for a few months now.
In short, the DIP is a protocol based on XCM that allows KILT identities to be bridged to any destination that XCM is able to reach, i.e., fellow parachains, the Polkadot Relay Chain, or other consensus systems.
The protocol implementation is already in the development phase, after the original idea was presented and refined with fellow projects.
More documentation about the system design and architecture will follow, but the main development work can be tracked on the KILT GitHub space, currently mainly as part of [this Pull Request](https://github.com/KILTprotocol/kilt-node/pull/494).
The full proposal can be found here (comment access): [https://docs.google.com/document/d/1apqOcH5a5fV7pri_MVm9O5ExuHuOWs2Z4IbX-skWu5E](https://docs.google.com/document/d/1apqOcH5a5fV7pri_MVm9O5ExuHuOWs2Z4IbX-skWu5E).
## How to verify the document integrity
The current version of the proposal document has been digitally signed with one of the DIDs that BOTLabs GmbH controls.
To verify the signature:
1. Download the PDF version of the Google Document linked above.
2. Download the DID signature of the file from IPFS, with CID *QmRcYyPcCKGDQno2m5qBSZq7dftoZKuwraF9C9M96rXR36* (e.g., [ipfs.io](https://ipfs.io/ipfs/QmRcYyPcCKGDQno2m5qBSZq7dftoZKuwraF9C9M96rXR36)).
3. Visit [didsign.io](https://didsign.io), and upload both the PDF file and the downloaded signature. The signature should verify correctly and link to the KILT tx in which the timestamp was generated.
4. To verify the back-link from the DID to the account to which the funds must be sent if the Proposal is accepted, copy the account in the Proposal (*15oXzySe6tjF2MumHfUodH8pFQWjy2hraRmXUJXXMKKY6p3F* for quick reference) and paste it in [w3n.id](https://w3n.id). The account must be linked to the same web3name that signed the proposal document.
## Further Discussions
Please post any questions/concerns/feedback in one of the following ways:
* In the comments section below
* In the Polkadot Direction Element channel
* Using one of the contacts included at the end of the proposal document

KILT Decentralized Identity Provider (DIP) - Polkadot Treasury Proposal

Treasury

Propose and approve a spend of treasury funds.

- `origin`: Must be `SpendOrigin` with the `Success` value being at least `amount`.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The destination account for the transfer.

NOTE: For record-keeping purposes, the proposer is deemed to be equivalent to the
beneficiary.


 - BOTLabs is requesting funds for work on the Decentralized Identity Provider (DIP) 
 - The DIP is a OpenID-like authentication flow into Web3 
 - The proposal with history of changes be found at  https://docs.google.com/document/d/1-04dherCsMCDqVfwnGF8ZzCI1cOfSjbaBe4Jv4ilcjY 
 - Signature can be verified at didsign.io
 - Questions or feedback can be left in the comments, Polkadot Direction Element channel, or one of the contacts in the proposal document.

#5 KILT Decentralized Identity Provider (DIP) - Polkadot Medium Spender Proposal

No Active Proposals