💚
vSelf Project Documentation
vSelf functionality
vSelf functionality
  • NEAR onboarding
    • Create account
    • Supported wallets
    • Smooth onboarding
  • NFT collection toolkit
    • Overview
    • Set up NFT collection
    • Claim NFT rewards
    • Mobile application
    • Analytics
    • Provenance traction
    • Collection settings
    • VSELF API for collections
    • Payment
  • User profile toolkit
    • Overview
    • NEAR NFT-based profile
    • Multi-chain support
    • Sub-identities support
  • Community management toolkit
    • Overview
    • Community types
    • Community structure
    • Community roles & rights & reputation
    • Community functionality
    • Private community
    • zkp proof-of-membership SDK
  • Verifiable credentials toolkit
    • Overview
    • Roles definition
    • Credential types & concepts
    • Toolkit functionality
    • Credential-based wallet & studio
Powered by GitBook
On this page
  1. User profile toolkit

NEAR NFT-based profile

Status: ready to use

PreviousOverviewNextMulti-chain support

Last updated 2 years ago

Current stage (ready)

The current version of the vSelf toolkit for user profiles supports one personal identity per user and only NEAR network. In this case, the user ID matches her NEAR ID.

The user can add the following information to her profile:

  • Name & biography

  • Avatar picture

  • Portfolio links

  • NEAR NFTs

Note: The NEAR contract address should be provided to add NFTs. All the NFTs minted from this contract & owned by the current user will be added to her profile.

The web form to provide user data is available .

All the listed information is saved and stored for the authorized user ID. We store all the user data expect the big source files, an avatar, in on-chain storage . The source files are downloaded & stored in using powergate. The link to the avatar image is stored in Social DB too.

All this information about the user is available to everyone on the user's public page. The address of this public page contains the user NEAR ID. Therefore, the data is retrieved to the dynamic page according to the current user ID.

Social graph navigation (in development)

The next step is to add these navigation elements: search of the user's public page by NEAR ID and subscription to a Social DB user. All the subscriptions will be saved and shown on the user's public page.

Loading NFTs optimization (in development)

Using NEAR Explorer to import profile data might be confusing, especially if we address Web2 users. For this reason, we are improving the process of NFT import. In the process we propose, there is no need to provide a NEAR contact address. All the NFTs will be loaded automatically according to the user's NEAR ID. We use to set up a NEAR subgraph to accomplish this goal. It is used to index all NFTs owned by the user. The user will be able to choose which NFTs from her list she wants to share on the public page. Chosen NFTs will be added to the user profile.

here
Social DB
IPFS
NFT.storage
The Graph Protocol