{"title": "Venn Protocol", "logoImg": "bafkreiany3wmbab665qtooxzcphdu2peqnx734fy74tjb53yqhdisf6t24", "website": "https://venn-protocol.vercel.app/", "bannerImg": "bafkreidmxpyu5btqnbzhgz7gnzjzyxbxjrd4tvkowehwnsq3tgvjjr6goy", "createdAt": 1713318421913, "userGithub": "bfranceschin", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..bi4PjWZEcyvaiYRmnxtJI_RKGWM1sYV0NTpsDxEgCDZ0cMX35-8immf6BTIC_OyNZW2tyCYORc_Gqlc85FKoDA", "type": "Ed25519Signature2018", "created": "2024-04-17T01:46:21.211Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-04-17T01:46:21.210Z", "expirationDate": "2024-07-16T01:46:21.210Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x48966e1D5D711dF56140489F92736aC05d2035ca", "hash": "v0.0.0:dvVmqjE1FoxPw6xBAL9o/UXC6utvRKFtIm7VDtpkMfI=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#australopitech#50725001"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..5j_uEn6Z7gZpuMCuU79No6OWeX4q_21-57FSUpLsooVaTVyNGE3yDrXC_asNMj4Pr8LACtACaiUoZhbZD62XBQ", "type": "Ed25519Signature2018", "created": "2024-04-17T01:42:45.673Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-04-17T01:42:45.673Z", "expirationDate": "2024-07-16T01:42:45.673Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x48966e1D5D711dF56140489F92736aC05d2035ca", "hash": "v0.0.0:iU/zzEdhonH8X5OuS9LlNclh0REVJp7NobczqcVqVIw=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#vennprotocol"}}}, "description": "NFT Rentals through Account Abstraction. No collateral and no integration required.\n\n## What is Venn?\u2753\n  \nVenn is a Protocol/Dapp that leverages Smart Accounts through ERC-4337 to empower users to engage in NFT rentals in a completely SAFE and TRUSTLESS manner, WITHOUT the need of COLLATERAL or THIRD PARTY INTEGRATION. Most major NFT platforms are COMPATIBLE FROM THE GET GO!\n  \n## Why Venn?\u00a0\ud83d\ude4b\n  \nPrevious NFT rental solutions involved some very undesirable features that ended up halting the growth of this market. Among these are:\n  \n\u00a0\n  \n\ud83d\udeab\u00a0__Need of Collateral__: this feature has two big negative implications. 1st users paying to acquire NFT rentals need to put out capital in excess of the rent value. This makes tx's way less attractive economically, since these users would need to have capital sitting idle in an escrow. 2nd, the NFT owner runs the risk of not getting his asset back. This risk will be priced in rent values and internalized by all tx's, even the ones in which the risk is minimal, making the market really inefficient.\n  \n\u00a0\n  \n\ud83d\udeab\u00a0__Need of Integrations__: even solutions that enable uncollateralized rentals, do so in ways that require 3rd party integration, e.g., proposing new NFT patterns, using an escrow-replica scheme, using NFT-wrappers, etc. This means that in order to enjoy some nice functionality attached to the NFT, the user paying to acquire the rental would have to wait for NFT platforms to integrate their Dapps to this particular solution. That is a HUGE barrier to growth since NFT platforms first need to get sold on the idea, then make the required changes on their end and then educate their customers. That all takes time and resources. Of course that platforms may never entertain the idea at all. The users are the ones who lose.\n  \n  \n\n\ud83d\udeab\u00a0__Highly complex solutions__: another characteristic that halts the growth of said platforms is the complexity of the solution being proposed. In order to feel safe in transacting highly valuable assets, users should be able to understand, at least at a high level how the solution they are using works. If this is not a requirement it is a HUGE PLUS when it comes to user onboarding.\n  \n\u00a0 \n  \nVenn SOLVES ALL THESE PROBLEMS, among others, providing a SAFE and extremely SIMPLE solution, that does NOT require COLLATERAL nor 3RD PARTY INTEGRATION! Most major NFT platforms are compatible by default.\u00a0 \n  \n\u00a0 \n  \nWe do so by using a new scheme related to the new hot topic in web3 development: Account Abstraction. This scheme was proposed in EIP-4337 and was adopted by many infrastructure providers last year, boosting the development of new solutions using the concept of Smart Accounts, including yours truly. \n  \n## Grants\u00a0\ud83c\udf96\ufe0f\n  \n- 5 ETH from Base through [BASE House]([https://offchain.prop.house/base](https://offchain.prop.house/base)) Community Fund. \n\u00a0 \u00a0 \n## Demo and roadmap\u00a0\u25b6\ufe0f\ud83d\uddd3\ufe0f \n  \nWe have a [Demo]([https://venn-protocol.vercel.app/](https://venn-protocol.vercel.app/)) working in Ethereum Sepolia. Anyone can test it. We intend to continue development to hit some important milestones and eventually produce an end user product. Some future improvements include: \n  \n\u00a0 \n  \n\ud83d\udd1c\u00a0Mobile friendly UI\n\n\ud83d\udd1c\u00a0ERC-1155 compatibility\u00a0 \n  \n\ud83d\udd1c\u00a0Subscription based payments \n\n\ud83d\udd1c\u00a0Rentee renewal options \n  \n\ud83d\udd1c\u00a0ERC-20 payment options \n  \n\ud83d\udd1c\u00a0Scaling API through sub-graphs \n \n  \n## External links\u00a0\ud83d\udd17 \n  \n\ud83d\udcfd\ufe0f\u00a0[Demo]([https://venn-protocol.vercel.app/](https://venn-protocol.vercel.app/)) \u00a0\u00a0\ud83d\udcd6\u00a0[About]([https://pbfranceschin.gitbook.io/venn](https://pbfranceschin.gitbook.io/venn)) \u00a0\u00a0\u2753\u00a0[Guides]([https://pbfranceschin.gitbook.io/venn/overview/guides](https://pbfranceschin.gitbook.io/venn/overview/guides)) \u00a0\u00a0\ud83d\udc68\u200d\ud83c\udfeb\u00a0[Deck]([https://drive.google.com/file/d/1-L40R7qWpt1J7Z2VkNQQ3BSPh3cGZO68/view?usp=sharing](https://drive.google.com/file/d/1-L40R7qWpt1J7Z2VkNQQ3BSPh3cGZO68/view?usp=sharing)) \u00a0 </> [Code]([https://github.com/australopitech/venn-protocol](https://github.com/australopitech/venn-protocol)) \u00a0\u00a0\ud83d\udc35\u00a0[Team Page]([https://australopitech.xyz/](https://australopitech.xyz/))", "logoImgData": {}, "bannerImgData": {}, "projectGithub": "australopitech", "projectTwitter": "vennprotocol"}
Venn Protocol
NFT Rentals through Account Abstraction. No collateral and no integration required.

## What is Venn?❓
  
Venn is a Protocol/Dapp that leverages Smart Accounts through ERC-4337 to empower users to engage in NFT rentals in a completely SAFE and TRUSTLESS manner, WITHOUT the need of COLLATERAL or THIRD PARTY INTEGRATION. Most major NFT platforms are COMPATIBLE FROM THE GET GO!
  
## Why Venn? 🙋
  
Previous NFT rental solutions involved some very undesirable features that ended up halting the growth of this market. Among these are:
  
 
  
🚫 __Need of Collateral__: this feature has two big negative implications. 1st users paying to acquire NFT rentals need to put out capital in excess of the rent value. This makes tx's way less attractive economically, since these users would need to have capital sitting idle in an escrow. 2nd, the NFT owner runs the risk of not getting his asset back. This risk will be priced in rent values and internalized by all tx's, even the ones in which the risk is minimal, making the market really inefficient.
  
 
  
🚫 __Need of Integrations__: even solutions that enable uncollateralized rentals, do so in ways that require 3rd party integration, e.g., proposing new NFT patterns, using an escrow-replica scheme, using NFT-wrappers, etc. This means that in order to enjoy some nice functionality attached to the NFT, the user paying to acquire the rental would have to wait for NFT platforms to integrate their Dapps to this particular solution. That is a HUGE barrier to growth since NFT platforms first need to get sold on the idea, then make the required changes on their end and then educate their customers. That all takes time and resources. Of course that platforms may never entertain the idea at all. The users are the ones who lose.
  
  

🚫 __Highly complex solutions__: another characteristic that halts the growth of said platforms is the complexity of the solution being proposed. In order to feel safe in transacting highly valuable assets, users should be able to understand, at least at a high level how the solution they are using works. If this is not a requirement it is a HUGE PLUS when it comes to user onboarding.
  
  
  
Venn SOLVES ALL THESE PROBLEMS, among others, providing a SAFE and extremely SIMPLE solution, that does NOT require COLLATERAL nor 3RD PARTY INTEGRATION! Most major NFT platforms are compatible by default.  
  
  
  
We do so by using a new scheme related to the new hot topic in web3 development: Account Abstraction. This scheme was proposed in EIP-4337 and was adopted by many infrastructure providers last year, boosting the development of new solutions using the concept of Smart Accounts, including yours truly. 
  
## Grants 🎖️
  
- 5 ETH from Base through [BASE House]([https://offchain.prop.house/base](https://offchain.prop.house/base)) Community Fund. 
    
## Demo and roadmap ▶️🗓️ 
  
We have a [Demo]([https://venn-protocol.vercel.app/](https://venn-protocol.vercel.app/)) working in Ethereum Sepolia. Anyone can test it. We intend to continue development to hit some important milestones and eventually produce an end user product. Some future improvements include: 
  
  
  
🔜 Mobile friendly UI

🔜 ERC-1155 compatibility  
  
🔜 Subscription based payments 

🔜 Rentee renewal options 
  
🔜 ERC-20 payment options 
  
🔜 Scaling API through sub-graphs 
 
  
## External links 🔗 
  
📽️ [Demo]([https://venn-protocol.vercel.app/](https://venn-protocol.vercel.app/))   📖 [About]([https://pbfranceschin.gitbook.io/venn](https://pbfranceschin.gitbook.io/venn))   ❓ [Guides]([https://pbfranceschin.gitbook.io/venn/overview/guides](https://pbfranceschin.gitbook.io/venn/overview/guides))   👨‍🏫 [Deck]([https://drive.google.com/file/d/1-L40R7qWpt1J7Z2VkNQQ3BSPh3cGZO68/view?usp=sharing](https://drive.google.com/file/d/1-L40R7qWpt1J7Z2VkNQQ3BSPh3cGZO68/view?usp=sharing))   </> [Code]([https://github.com/australopitech/venn-protocol](https://github.com/australopitech/venn-protocol))   🐵 [Team Page]([https://australopitech.xyz/](https://australopitech.xyz/))
Venn Protocol