Developers
DevelopersGuides
  • Introducing Bond
    • Introduction
    • Why we build Bond?
    • Roles In Bond Ecosystem
    • Decentralised Relations/Social Graph
    • Architecture
    • Bond Reward Model
      • Leech Principle
      • Barrel Principle
  • Main Concepts
    • Bond Profile
      • Identity
      • Relationships
      • Content
      • Creator Economy
    • Connection
      • Connection NFTs
    • Bond Social Graph
    • Centralities
      • In/Out Degree Centrality
      • Betweenness Centrality
      • Closeness Centrality
      • PageRank Centrality
    • Reward Models
    • Reward Contracts
    • Off-chain Oracles
    • Gasless Mode
    • Cross Chain Messaging and Pay Gas with Bond Token
  • Bond API
    • Introduction
    • API Urls
    • Getting started with GraphQL
    • Authentication
      • Login
      • Refresh JWT
    • Profile
      • Create Profile
      • SetProfileMetadata
    • Connect
      • Connect a profile
      • Disconnect
  • Smart Contracts
    • BondHub
    • MerkelDistributor
    • TokenDeployer
    • SingleStakePoolDeployer
    • LzTokenDeployer
    • LzSingleStakePoolDeployer
  • Bond SDK
    • Bond JS SDK
      • Authenticate
      • Create Profile
      • Connect
  • Bond Nodes
    • Hardware Requirements
    • Set up and Deploy
    • Node Config (TOML)
    • Secrets Config (TOML)
    • Role-Based Access Control (RBAC)
  • References
    • Deployed Contracts
    • Github
Powered by GitBook
On this page
  • Parameters
  • API Details
  1. Bond API
  2. Profile

Create Profile

PreviousProfileNextSetProfileMetadata

Last updated 1 year ago

With our API's support for gasless mode, users can seamlessly establish their profile, ensuring smooth interaction within the platform. Here, we outline the parameters that need to be provided or are optional for creating a profile and provide insights on how each parameter contributes to the profile's representation on the platform.

Parameters

  1. Handles (Required): The handle defines your unique bond handle name on the platform. It acts as a username or identifier, allowing other users to search, follow, or interact with your profile.

  2. Profile Picture URI (Optional): The profilePictureUri is a link pointing to an image stored in any cloud storage or online platform. If not provided, the platform will default to a standard image.

  3. Follow NFT URI (Optional): The followNFTURI represents the metadata of the NFT that your followers will mint when they choose to follow you. It's dynamic by default, meaning if not specified, the NFT image will showcase the latest publication from your profile. While bond.network does not enforce any specific metadata standards, it's highly recommended to follow the OpenSea metadata specifications for better compatibility with secondary marketplaces.

    Reference:

  4. Follow Module: Defining the follow module optimises user engagement on the platform. With our designed schema, setting this up becomes straightforward.

API Details

mutation CreateProfile($request: CreateProfileRequest!) {
  createProfile(request: $request) {
    ... on AppRelayerResult {
      txHash
      profileId
    }
    ... on AppRelayError {
      error
    }
  }
}
input CreateProfileRequest {

  handle: CreateHandle!

  # The profile picture uri
  profilePictureUri: Url

  # The follow module
  followModule: FollowModuleParams

  # The follow NFT URI is the NFT metadata your followers will mint when they follow you. This can be updated at all times. If you do not pass in anything it will create a super cool changing NFT which will show the last publication of your profile as the NFT which looks awesome! This means people do not have to worry about writing this logic but still have the ability to customise it for their followers
  followNFTURI: Url
}

input FollowModuleParams {
  # The follower fee follower module
  feeFollowModule: FeeFollowModuleParams

  # The empty follow module
  emptyFollowModule: Boolean
}
OpenSea Metadata Standards