n/acc

As crypto-nomads, at our first experiences we enjoy travelling to exotic destinations, not making long-term plans and attending all the parties, however on the mid to long term this is not sustainable at all, and we tend to learn about the value of surrounding with like-minded people, enjoying a healthy work routine and saving some tokens.

In the other hand the process of self-organizing stays is frustrating and the hacker houses many times are like a lottery, for hackers and for organizers.

Because of this, we have build n/acc (Nomadic Accelerationism), a secure, private, on-chain encrypted social graph protocol and a dApp to consume it, designed to enhance life of crypto-nomads as follows:

1. Share living spaces around the globe for any duration.
2. Find house partners for specific crypto event.
3. Offer Hacker House organizers and participants a fair and reliable management process.

Everything without the possibility of being tracked, searched or reveling any identity, interests, profiles or plans, prior a successful pairing is completed.

It's important to understand that this is not another social network, this is a platform exclusive for crypto-adopters using an encrypted social graph pushing the privacy and security to the limits, to let us enjoy safe and rewarding experiences.

To use the platform, crypto-nomads first connect to the n/acc dApp via Dynamic and sign in with their wallet. This action creates an on-chain user profile within the FHE Smart Contract deployed on Fhenix to ensure maximum security and reliability.

After this steps, crypto-nomads begin generating various zkProofs to earn badges. These badges are crucial for pairing when they set their Journey intents and are also used for filtering by Hacker House creators.

This different zkProofs are being generated from the dApp using a an API but the implementations to fetch, get, confirm, make or/and authenticate the data differs from each one, as follows:

World ID: The confirmation is made by the dApp. Patricio's POAPs: The information is fetched by a subgraph. Polygon ID: The confirmation is made by the dApp. $nouns usage: The information is fetched by a subgraph. BAYC/MAYC NFT: The information is fetched by a subgraph. ApeCoin Staking: The information is fetched by a subgraph. TalentProtocol BuildScore: Verified using TLSNotary. ETH Global Hacker signature with bracelet: Verified using TLSNotary. Gender: Verified using zkML with the Giza model. Birthdate: Verified using zkML with the Giza model. Farecaster: Utilizes Neynar. ENS: The information is fetched by a subgraph.

Then a user can do 2 different actions:

1. Create a Journey intent where configures a place, dates, collateralized amount of the stay cost and filtering preferences caped by his own badges.

This intent information is stored in the FHE Smart Contract in Fhenix and uploaded also to Nillion awaiting to get a pairing. Something that will be reflected in the dApp.

The collateral to deposit in ETH is calculated using Chronicle protocol by USD price.

1. Create a Hacker House where configures a place, dates, collateralized amount of the house cost, number of hackers and filtering preferences caped by he whole platform in this case.

This Hacker House post goes to Polygon zkEVM and is discovered using The Graph, in the mean while the crypto-nomads can request the spots while staying annon.

There is more interesting features to add given by community and partners feedback but this PoC shows the general functionalities and capabilities.