# Introduction ## Welcome to SPYDRA Tokenize Your Real-World Assets with Our Blockchain Platform. Spydra Empowers enterprises and asset owners to tokenise real world assets for real world impact. Embrace Transparency, Security, and Compliance ## Getting Started **Got 3 minutes?** Check out a video overview of our product: {% embed url="" %} ### Guides; Learn the fundamentals of Spydra to get a deeper understanding of our main features: {% content-ref url="/pages/EsisdCuKG5qRniE4QZt6" %} [Blockchain fundamentals](/getting-started/blockchain-fundamentals) {% endcontent-ref %} {% content-ref url="/pages/x0hbFNs7rxvrZuu617bY" %} [Why Spydra?](/getting-started/why-spydra) {% endcontent-ref %} *** ### Kickstart Your Blockchain Journey with Spydra #### Private Network Follow our handy guides to kickstart your blockchain journey with Spydra and configure it for your enterprise use-case. {% content-ref url="/pages/RFlgdlbGud5yH5wdQaLk" %} [Getting started with a Private Network](/getting-started/getting-started-with-a-private-network) {% endcontent-ref %} {% content-ref url="/pages/16MLRQ0BJjvmPKnvVkd9" %} [Create an Organization](/how-to/private-network/organizations/create-an-organization) {% endcontent-ref %} {% content-ref url="/pages/RYnEXt12olzvpzyPB5jF" %} [Create a Network](/how-to/private-network/networks/create-a-network) {% endcontent-ref %} {% content-ref url="/pages/GcZA8Db1rvfGKCZB3nqZ" %} [Explore Apps](/how-to/private-network/apps/explore-apps) {% endcontent-ref %} {% content-ref url="/pages/9XM3I6BcWDVO1GBf8gMZ" %} [Deploy App](/how-to/private-network/apps/deploy-app) {% endcontent-ref %} {% content-ref url="/pages/UUDlvXHydtVkBmT5djpK" %} [API Reference](/developers/api-reference) {% endcontent-ref %} #### Public Chain Follow our comprehensive guides to tokenize your real-world assets on the Spydra platform. Our comprehensive documents guide you through every step, from setting up the initial token store to successfully tokenizing your real-world assets. Learn to navigate the platform effectively and use our guide to define tokenomics for your tokens. # Why Spydra? Spydra's mission is to revolutionize businesses by empowering them with the benefits of Asset Tokenization. Spydra enables organizations to * Create your own Private Enterprise Blockchain Network with multiple participant organizations. * Deploy a Pre-configured Asset Tokenization App that is low-code and highly configurable. * Upload your custom Chaincodes/Smart contracts. * Integrate your existing tech stack with your Blockchain networks and Applications using easy-to-use Rest APIs {% hint style="success" %} Spydra offers $400 free credits for the first two organizations you create. These credits can be utilized for platform usage. {% endhint %} ### -------------------------------------------------------------------------------- ### Overview Spydra is the ultimate Asset tokenization platform for businesses that can be deployed without writing a single line of code. Spydra offers an easy-to-use interface, simplified blockchain network deployment, low code decentralized application builder, and pre-configured blockchain solutions. With Spydra, you can set up your organization for blockchain, add users to your organizations, create blockchain networks with the cloud provider of your choice, join other blockchain networks, explore pre-configured chaincode solutions, deploy decentralized applications, access blockchain APIs, setup callbacks and listen to blockchain events, use decentralized storage solutions such as IPFS. ### Decentralization as a Service Spydra provides decentralized solutions to your centralized problems. With a single API call, your Centralized Business operations can transition to a Decentralized infrastructure. SPYDRA is an enabler for businesses and enterprises on their journey from Web 2.0 to Web 3.0 ### API Driven Infrastructure Our robust suite of high-availability APIs and Developer Tools provide quick, reliable access to the Hyperledger Fabric, Ethereum, and IPFS networks so you can focus on building and scaling next-generation software. ### Simplified User Interface One of the major hurdles in the web3 space is the lack of an intuitive user interface. At Spydra, we have addressed this issue with a simple and easy-to-use interface - optimizing the onboarding experience, incorporating familiarity and reducing complexities of workflows, abstracting complex functionalities, and focusing only on the essential components. We believe this is a key factor in adoption because SPYDRA aims to serve all users, from developers to non-technical users. ### Flexible Cloud Deployments Spydra offers flexible cloud deployment options for your blockchain network. We currently support AWS and Microsoft Azure; we will soon be adding support to more cloud service providers like Google Cloud etc. ### Protocols Supported Spydra currently supports Hyperledger Fabric Framework as part of our Enterprise Blockchain offering. Soon, we will be supporting Public Blockchain protocols such as Ethereum. ### Pre-configured solutions Spydra offers a pre-configured chaincode solution - Asset Management. You can deploy Asset Tokenization that suits your business requirements and customize them per your use case. For example, Asset Management solutions for supply chain-related use cases and Token Factory solutions for tokenization use cases such as Loyalty tokens (fungible) and Paintings (NFTs). Our team can also help you with the customization of chaincodes and custom deployment of networks through dedicated support. ### Low Code Platform As a platform, Spydra is keen to serve clients and customers across sectors such as Supply chain, Banking, Fintech, etc. We understand the diverse requirements of these industries and sectors and the variety of use cases they are looking to deploy. Hence, we designed SPYDRA as a low code platform enabling the one-click deployment of Blockchain Networks and plug and play model for implementing industrial use cases as decentralized applications. ### How Spydra works? Under the hood, Spydra is powered by the latest technologies and tools in the tech space. To enable the transition of enterprises from web 2.0 to web 3.0, we have done a lot of research, and our team of experts has come up with the best tech stack possible. Our Platform architecture is highly scalable to handle complex workloads and highly available to ensure zero downtime. We have also taken utmost care to ensure we do not compromise on security while providing full scalability and high availability. As a platform, we guarantee data isolation and provide flexible tenancy options - shared or dedicated. At a high level, SPYDRA uses a microservices architecture with Kubernetes orchestration for enterprises and public blockchain network deployments. # Blockchain fundamentals # Why Blockchain? Blockchain is a distributed ledger technology that allows multiple parties simultaneous access to a single, tamper-proof version of the same data. It is a secure, transparent, and decentralized system that is changing how businesses operate. Enterprises can use blockchain technology because it offers several advantages over traditional systems. Firstly, it allows for secure and transparent transactions, as mentioned before. This can help prevent fraud and increase trust between parties. Additionally, blockchain technology can simplify storing and sharing data, eliminating the need for intermediaries like banks and other financial institutions. This can result in lower transaction costs and faster processing times. One of the biggest advantages of blockchain is that it provides immutability. This means that once a transaction is recorded on the blockchain, it cannot be altered or deleted. This feature is particularly valuable in industries where data integrity is critical, such as finance, healthcare, and supply chain management. In addition to immutability, blockchain provides transparency, as all parties can view the same data in real time. This enhances trust between parties and reduces the need for intermediaries. Enterprises can benefit from blockchain in many ways. For example, it can streamline supply chain management by providing real-time visibility into the movement of goods, reducing the risk of fraud, and improving efficiency. It can also simplify the process of verifying identities, reducing the risk of fraud and improving security. # Private Blockchain Private Blockchain for Enterprises Blockchain technology has become increasingly popular in recent years. It is widely known for its decentralized nature and ability to provide a secure and transparent transaction platform. However, public blockchains like Ethereum and Bitcoin are not ideal for businesses as they lack control over who can access their sensitive data. This is where private blockchains come in. ## What is a Private Blockchain? A private blockchain is a permissioned blockchain where only selected participants are allowed to join the network. All participants are verified, and each participant has their own copy of the ledger. This means that only authorized users can access the data, and the data cannot be altered without the consensus of the network. ### How Does It Help Enterprises? Private blockchains offer several benefits to enterprises, including: #### Security and Privacy Private blockchains provide an added layer of security as only authorized users can access the data. This helps to prevent data breaches and cyber-attacks. Additionally, private blockchains offer privacy, as sensitive data can be kept hidden from unauthorized users. #### Efficiency Private blockchains can improve efficiency by reducing the need for intermediaries in transactions. Smart contracts can be used to automate processes, which can reduce costs and improve speed. #### Customization Enterprises can customize private blockchains to meet their specific needs. This means businesses can tailor their blockchain to fit their operations, making it more efficient and effective. #### Scalability Private blockchains can handle a large number of transactions per second, making them suitable for enterprise-level operations. This means that businesses can scale their blockchain as their operations grow. ### Why Enterprises Should Use It? Private blockchains offer several advantages over public blockchains, making them an ideal choice for enterprises. They provide a secure, efficient, and customizable platform for transactions. Additionally, private blockchains offer privacy, essential for businesses dealing with sensitive data. Overall, private blockchains are an excellent choice for enterprises looking to leverage blockchain technology to improve their operations. By using private blockchains, businesses can improve efficiency, reduce costs, and enhance security. Examples of Private Blockchain Use Cases Several industries have already adopted private blockchains to improve their operations. Here are some examples of private blockchain use cases: #### Finance Private blockchains are being used in the finance industry to facilitate transactions between banks and other financial institutions. These private blockchains help to reduce the cost and time required for cross-border transactions. #### Healthcare The healthcare industry is using private blockchains to store and secure patient data. Private blockchains provide a secure platform for storing sensitive patient information and can help to prevent data breaches. #### Supply Chain Management Private blockchains are being used in the supply chain management industry to improve transparency and reduce fraud. Using private blockchains, businesses can track the movement of goods from the manufacturer to the end consumer. #### Real Estate The real estate industry is using private blockchains to streamline the buying and selling of properties. Private blockchains provide a secure platform for storing property information and can help reduce the time and cost involved in buying and selling. ### Conclusion In conclusion, private blockchains are an excellent choice for enterprises looking to leverage blockchain technology to improve their operations. They provide a secure, efficient, and customizable platform for transactions, while also offering privacy and scalability. With many industries already adopting private blockchains, it is clear that this technology has significant potential for businesses of all sizes. # Public Chain ## Public Blockchains: An Overview Public blockchains, unlike private blockchains, are open to anyone who wishes to participate. They function on a decentralized network and allow transparent and immutable transactions. Major cryptocurrencies like Bitcoin and Ethereum operate on public blockchains, highlighting their robustness and reliability. #### Key Features 1. **Decentralization**: Public blockchains operate without a central authority, ensuring no single entity has control. 2. **Transparency**: All transactions are visible to anyone on the network, promoting trust and accountability. 3. **Immutability**: Once data is recorded on a public blockchain, it cannot be altered, ensuring data integrity. #### Advantages * **Security**: With a large number of nodes validating transactions, public blockchains are highly secure against attacks. * **Trustless System**: Participants do not need to trust each other or a central authority, as the blockchain itself provides the trust mechanism. ### Use Cases Public blockchains are ideal for applications like real-world asset tokenization, where transparency, security, and trustless interaction are crucial. ### Why Asset Owners Should Use Real World Asset Tokenization #### Benefits for Asset Owners 1. **Increased Liquidity**: Tokenization allows fractional ownership, enabling liquidity for traditionally illiquid assets like real estate and art. 2. **Cost Efficiency**: Reduces the need for intermediaries and lowers transaction costs. 3. **Greater Accessibility**: Broader investor base by enabling small investors to buy fractions of high-value assets. 4. **Enhanced Security**: Blockchain technology provides a secure and transparent method for asset tracking and ownership verification. #### Use Case by Category 1. **Real Estate**: Tokenizing property allows owners to sell shares of the property, providing funds while retaining partial ownership. 2. **Art and Collectibles**: Artists and collectors can tokenize expensive artwork, making it accessible to more investors. 3. **Precious Metals**: Gold, silver, and other precious metals can be tokenized to facilitate easier trading and ownership transfers. 4. **Commodities**: Agricultural and industrial commodities can be tokenized to streamline supply chain management and trading. and many more real world asset use-cases ### Conclusion Public blockchains are poised to become integral to the digital economy due to their transparency, immutability, and decentralized nature. As both technology and adoption advance, their significance in a wide array of applications is likely to grow. # Getting started with a Private Network This will guide you in setting up your Spydra account, Creating organizations, and deploying apps onto private blockchain networks. ### Steps to get started with Spydra 1. Create a Spydra account 2. Create an organization 3. Create a Network 4. Deploy app ## 1. Create a Spydra account **Using your details** * Navigate to * Enter the required details * Enter the verification code that will be sent to your email * Post email verification, and you'll be successfully Signed up. **Using Google Signup** * Navigate to * Use Sign up with Google. * Verify your email by logging into your account. * After verification, you'll be signed up and redirected to Spydra's platform. [Create an Account](/how-to/private-network/account/create-an-account) ## 2. Create an organization * Navigate to the Organization listing page here [https://console.spydra.app/organizations](https://console.spydra.app/) and click on 'Create Organization'. * Enter Organization Name, Country, Primary Contact Email address, Industry, Employee Size, and Use Case, then click on **Create Organization.** * Your organization will be created. [Create an Organization](/how-to/private-network/organizations/create-an-organization) ## 3. Creating a Network * You can create a network or an organization admin only when you create a network. * Navigate to the Network listing page from [https://console.spydra.app/networks](https://console.spydra.app/) and click Create Network. * Enter the required details and click on Create. * Your network will be created. [Create a Network](/how-to/private-network/networks/create-a-network) # Getting started with a Token Store on Public Chain Introducing the ultimate solution for real world asset tokenization and investment management on the Spydra platform. Spydra empowers you to create your own token store and list real-world assets to raise funds. With our platform, you can tokenize a wide range of asset categories, including real estate, collectibles, art, luxury goods, and even carbon credits, quickly and efficiently. Designed to unlock liquidity and attract new investors, Leverage Spydra to provide a best-in-class investment experience to your customers. Our platform allows you to: 1. **Create Your Token Store:** Establish a personalized digital marketplace where you can showcase and trade your tokenized assets. 2. **Tokenize Real-World Assets:** Transform tangible assets into digital tokens and list them on your store, making them accessible to a broader audience. 3. **Manage Token Lifecycle:** Utilize powerful management tools for compliance, transaction monitoring, and investor relations to ensure smooth operations.
Experience the future of asset investment with Spydra and transform how you engage with investors, unlocking new opportunities in the digital asset space. # Token store A personalized digital marketplace that serves as your central hub for managing tokenized assets. This comprehensive platform enables users to create, customize, and showcase their digital tokens while providing powerful tools for trading, monitoring, and community engagement. The Token Store acts as both a display window and management console for your digital asset portfolio, making it easier to reach and interact with potential investors. # Customise token store front Transform your digital presence using Spydra's advanced customization templates. Create a professional and distinctive storefront that perfectly represents your brand identity by personalizing every aspect - from color schemes and typography to layout designs and interactive elements. The intuitive interface allows you to craft a unique user experience that resonates with your target audience while maintaining professional standards. # List a real world asset and issue tokens Transform tangible assets into digital investments through our sophisticated tokenization process. This feature allows you to digitize and fractionalize real-world assets with precision, creating detailed asset profiles that include comprehensive information, valuation details, and investment terms. The platform facilitates the creation of tokens that represent fractional ownership or investment rights, making previously illiquid assets more accessible to a broader investor base. # Manage token lifecycle Take complete control of your tokenized assets through our comprehensive lifecycle management system. This powerful suite of tools enables you to oversee every aspect of your digital assets, including transaction monitoring, investor relationship management, sales tracking, automated payout distributions, and regulatory compliance documentation. The platform streamlines complex operations while maintaining transparency and security throughout the entire token lifecycle. # Intro to Hyperledger Fabric ## Hyperledger Fabric: An Overview Hyperledger Fabric is a blockchain framework that provides a modular architecture for developing blockchain-based solutions. It was developed by the Linux Foundation's Hyperledger project, which is a global collaboration of enterprises, developers, and academics working on advancing blockchain technology. Hyperledger Fabric provides a high degree of flexibility and scalability, making it ideal for enterprises looking to implement blockchain solutions that meet their specific business needs. The framework allows for the creation of private blockchain networks that can be customized with various consensus algorithms, smart contracts, and identity management solutions. One of the key benefits of Hyperledger Fabric is its focus on privacy and confidentiality. The framework allows for the creation of private channels within a network that can be used to restrict access to sensitive data. This makes it ideal for use cases such as supply chain management, where multiple parties need to share data without compromising confidentiality. Another advantage of Hyperledger Fabric is its ability to support both permissioned and permissionless blockchain networks. This means that enterprises can choose to implement a private blockchain network with a known set of participants or a public blockchain network that is open to anyone. In addition, Hyperledger Fabric provides a range of tools and resources to help enterprises develop, test, and deploy blockchain-based solutions. This includes a comprehensive documentation library, sample applications, and development tools such as Hyperledger Composer, which simplifies the process of creating and deploying smart contracts. Overall, Hyperledger Fabric is a powerful blockchain framework that provides enterprises with the flexibility, scalability, and privacy they need to develop and deploy blockchain-based solutions that meet their specific business needs. # Private Network Our vision is to revolutionize businesses by empowering them with the benefits of enterprise blockchain technology. To enable this vision, we built a platform for businesses to deploy their use cases onto the blockchain with ease. To understand how it works, let's understand the modules within Spydra and how they interact. ## Modules - Anatomy of Spydra It is important to understand the modules to see the full potential of Spydra. * **Users**: Any individual who signed up on the Spydra Platform. * **Organization**: Refers to a member or participant that has been granted access to the network and can transact with other members using the blockchain technology. These organizations can be businesses, institutions, government agencies, or any other entity that has a stake in the network.\ \ In an enterprise blockchain network, each organization has its own node or set of nodes that store a copy of the blockchain ledger. Each node maintains a copy of the ledger and verifies the validity of transactions within the network. This distributed ledger system allows for greater transparency, accountability, and security in transactions between organizations. * **Network**: A private blockchain network is designed for use by multiple businesses or organizations that are involved in a business process. It offers increased efficiency, cost savings, and improved security by using blockchain technology to facilitate secure and transparent transactions between different organizations or departments. It uses smart contracts to automate processes, and each member has their own node that stores a copy of the blockchain ledger. * **Application**: Applications are smart contracts that are self-executing computer programs that automatically execute the terms of a contract when predetermined conditions are met. Smart contracts can be used to automate processes, such as payment processing, supply chain management, and asset tracking, among others. They eliminate the need for intermediaries and can help reduce costs, increase efficiency, and improve security. Smart contracts/Apps are also referred to as Chaincode in a Hyperledger Fabric Blockchain network.\ \ Smart contracts are stored on a blockchain network, where they are transparent, immutable, and tamper-proof. Once a smart contract is deployed on a blockchain network, it cannot be altered, and its execution is guaranteed by the network's consensus mechanism. This makes smart contracts highly secure and reliable and reduces the risk of fraud and errors.
## How it works? {% hint style="info" %} Most of your interaction with Spydra happens on the Console, i.e., , where you'll create Organizations, Networks, and Apps/ Chaincodes or even deploy a custom chaincode/custom app. {% endhint %} Spydra connects your existing application ecosystem with your Blockchain Networks so that you can send and get information from Blockchain networks. The overall Spydra platform consists of a Control plane and a Data plane. The control plane is what users access through the website and is responsible for managing the blockchain platform, including tasks such as creating/modifying the networks and organizations, configuring applications, monitoring and logging etc. The Data plane, on the other hand, is where the actual blockchain nodes are deployed. All the customer data including ledger data, offchain database, keys and certificates etc. are stored in the Data plane. The Spydra platform is designed in such a manner that customers have a choice of deploying the Data plane on the Spydra Cloud or a cloud environment that they control. This provides complete control to customers to own and manage data in a way that is most suitable to them. ## Architecture overview
# Organizations An Organization is a logical entity, which can be as large as a multi-national corporation or as small as an individual, which participates as a member in a blockchain network. Each organization can have users added with different access rights based on the activities and operations they could do on the Spydra Platform. You will require organizations to create a blockchain network and deploy chaincode applications.
* You can create an unlimited number of Organizations. * You can join other organizations through invitations * You can invite other users as members to your organization with defined access rights * You can manage user memberships for your organization * You need an Organization to * Create a Blockchain Network * Deploy Chaincode applications on your Hyperledger Fabric Network * You can interact with deployed Chaincode applications through your organization's network * You can monitor your organization's activities through Organization's dashboard * You can utilize the Credits associated with your organization (***Note:*** Credit applies only to the first three organizations for an account) Get started by [creating an Organization](/how-to/private-network/organizations/create-an-organization) # Users and Organizations ## Users * When you Sign up on Spydra with an email address or Google account, you become a user. * By default, a user is not part of any organization. Only when an organization is created or when you accept an organization invitation you'll be associated with an organization. ## Organizations * Organizations are businesses, institutions, government agencies, or any other entity that is a participant in a blockchain network. * Users from Spydra's Console create organizations. So an organization is always associated with a user. * Users can be invited to collaborate with others in an Organization. * Multiple users can be part of an organization with different access rights. * **Your usage is billed at the Organization level.** # Organisation Hosting - Spydra Hosted and BYOC Spydra provides hosted cloud services on both Azure and AWS. However, Spydra provides users a flexibility to utilize their own existing cloud infrastructure to deploy and manage a network. BYOC (Bring Your Own Cloud) allows organizations to use their existing cloud infrastructure to deploy and manage the blockchain network on Spydra Platform. This approach provides flexibility, cost savings, and the ability to meet specific compliance and security requirements. Currently, Spydra supports the integration of user accounts from both **Azure** and **AWS**. This feature allows users to efficiently manage and monitor Spydra's blockchain network through these popular cloud service providers. # Organization Statuses These are set of Organization Statuses | **Name** | **Definition** | **Notes** | | ----------- | ---------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | ACTIVE | Orgs is active and will have access to all the modules and features. | | | INACTIVE |

> Orgs will not be part of any networks and will not be billed.
> Org cannot be invited by others.

| When an organization requests Spydra to make the account Inactive. | | FROZEN | When APIs are disabled for the organisation. Orgs will not be able to connect any APIs. | When the Payment is overdue for more than 7 days, the org will be moved to this state. | | DEACTIVATED | When the organisation is removed from all the networks due to unpaid bills. Orgs will have to set up all the Networks again. | When the payment is overdue for 15 days. | # Organization Roles & Permissions You can set access rights for different users based on how they collaborate with the Organization. These roles can be set when you invite users to your organization or from the membership page. ## Organization member roles
RoleDescriptionOrg Permissions
Org AdminCan manage Organization details, users, billing, and nodes that belong to the Organization in any network that the org is a part of.

Org Admins can also create new Networks and their org will automatically become part of it.

Org admins also get Network Admin, Network Contributor, or Chaincode Admin roles in networks that their Org is a part of. The exact role that they get in a network depends on what permission was assigned to the organization when it was added to a network.
  • Create, Update & Delete Org
  • Create, Update & Delete Org members
  • View and Pay Billing
  • Create and view Network
  • Create, Update & Delete Nodes
  • View Network Member
  • View Channel
  • View Chaincode
Org MemberCan manage organization properties and nodes that belong to the org in any of the networks that the org is a part of.

Org Members do not get any additional roles in any participant networks automatically except view access.
  • View Orgs, Update & Delete Orgs
  • View Org members
  • View billing details
  • Create, View, Update & Delete Node
  • View Networks
  • View Network Members
  • View Channels, View Chaincode
Org ReaderRead access to all Org properties and Networks.
  • View Org
  • View users
  • View Billing
  • View Node
  • View Networks
  • View Members
  • View Channels
  • View Chaincode
{% hint style="info" %} If an Organization participates in a Network, only **Org Admin** will inherit Network Permissions (Network Admin, Contributor, and Reader) set for the Organization. O**rg Member** and **Org Reader** will only have view access for any participant Networks. {% endhint %} Also view [Network Roles & Permissions](/products-overview/private-network/networks/network-roles-and-permissions) # Organization Dashboard Spydra offers a unified view of all activities happening within the organization through a dedicated dashboard for each organization. You can access the organization dashboard within the respective organization. For more details about Organization Dashboard - Check [Organization Dashboard](/how-to/private-network/organizations/organization-dashboard)How-tos. # Organization Entities ### What are Entities Every organization is registered as a member within the blockchain ledger. While invoking any method in the blockchain using REST API or GraphQL API, an Api key is used to authenticate which identifies the organization that is making the call. Sometimes, you would want to invoke a method on behalf of a user, department, sub-organization, vendor or any other entity that belongs to the parent organization. For e.g. a loyalty management organization might have multiple users on behalf of whom transactions have to be conducted or a healthcare organization might be providing services to different pharmacies and prescriptions are managed on behalf of these pharmacies. In such cases, the API calls can be made **on behalf** of an **Entity**. An Entity is identified by a **key:value** pair. For e.g. "userId:1234", "pharmacy:ph876" or "vendorId:345v" are all valid Entities. Basically, you have the flexibility to specify the Entity key (like userId, pharmacy, vendorId) etc. and the actual value. ### How do I use entities Entities can be used in two different ways: * **Assigning assets to entities**: In any API call, where assets can be assigned to organizations, you can assign them to Entities instead. For e.g to assign the ownership of an asset to an organization using the [Ownership transfer](/developers/api-reference/asset-tokenization/rest-api#asset-owners) API, the new owner organization will be specified as below: ```json {​ "assetType": "Property",​ "id": "Prop1",​ "owners": [​ {​ "orgId": "63c912fd5902d6c20ac43c89",​​ }​ ]​ ​} ``` To assign the same asset to an entity within the organization, you would do the following. Just add the entity that is part of the organization. ```json {​ "assetType": "Property",​ "id": "Prop1",​ "owners": [​ {​ "orgId": "63c912fd5902d6c20ac43c89",​ "userId": "1234"​ }​ ]​ ​} ``` * **API calls on behalf of an Entity**: In any API call, if you add the additional query string parameter "actAs=Entity", the call to the blockchain will be made on behalf of that Entity. This means that any permission evaluations will be done in the context of the specified Entity. For e.g. when you add the query parameter "actAs=userId:1234" while calling the [GetAsset](/developers/api-reference/asset-tokenization/rest-api#asset) API, it will only return results if the userId 1234 is an owner of the asset or has read permissions on it. Essentially, the call will be made in the context of userId 1234. ### How does it work in Hyperledger Fabric? The Entity based authentication and authorization uses the [Attribute based access control](https://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#attribute-based-access-control) concept in Hyperledger Fabric. The Spydra platform uses the Entity key and value specified in the actAs query parameter to create a certificate that uniquely identifies that Entity by adding the key/value pair as an additional attribute in the certificate. The blockchain calls are made by signing the requests by using this certificate. This additional attribute can then be extracted from the certificate and used in the App/Chaincode (pre-configured or custom) to make access control decisions. # Networks A Network is a group of nodes (or servers) that work together to establish consensus on a shared ledger or database. A blockchain network comprises multiple nodes that are connected and communicate with each other through a peer-to-peer network to validate and verify transactions on the network. These nodes can be owned and operated by different Organizations which are part of the Network, which allows them to collaborate on a shared application without needing to fully trust each other. Learn how to [Create a Network](/how-to/private-network/networks/create-a-network) # Network Statuses Networks have different statuses based on the stage at which they are in.
Network StatusDescription
CreatedWhen a network is created
LiveWhen a Blockchain network is initialized
ModifyWhen anything is being upgraded on a Network
DeletingWhen a Network is being deleted
InprogessWhen any details are being updated or any operations are running
Deleted Networks are deleted forever and cannot be retrieved. # Network Roles & Permissions You can set different access rights for the Organization members participating in a Network. This can be set when you are inviting an Organisation to your Network or from the Network membership page. {% hint style="info" %} Please note on Networks: * Only the participant **Organization's Admins** will inherit Network roles (**Network Admin, Network Contributor, or Chaincode Admin roles)**. * **Org Members and Org Reader** do not get additional permission for any participant Networks. They will only have **read access on Networks.** {% endhint %}
RoleDescriptionOrg Permissions
Network AdminCan manage all aspects of an existing network like network properties, channels, chaincodes, and members
  • Create, View, Update & Delete Network
  • Create, View, Update & Delete Participant Members
  • Create, View, Update & Delete Channels
  • Create, Deploy, View, and Update Apps/Chaincode
Network ContributorCan manage all aspects of the network except inviting or removing network member organizations
  • Create, View, Update & Delete Networks
  • View Participant Members
  • Create, View, Update & Delete Channels
  • Create, Deploy, View, and Update Apps/Chaincode
Network ReaderCan only view network information
  • View Network, View Members, View channels, View Apps/Chaincode
Also view, [Update Permissions for Network Members](/how-to/private-network/networks/view-and-edit-network-details/update-permissions-for-network-members) [Organization Roles & Permissions](/products-overview/private-network/organizations/organization-roles-and-permissions) # Network Configurations Every Network Configuration comes with a different configuration in terms of the number of Nodes and computational power. The following table outlines available resource limitations based on the provisioned node's size and will help you understand what constitutes a Network Configuration. | **Small** | **Medium** | **Large** | | ----------------------- | ----------------------- | ----------------------- | | 1 Peer + 1 orderer node | 2 Peer + 1 orderer node | 4 Peer + 3 orderer node | | 0.5 CPU | 1 CPU | 2 CPU | | 1 GB RAM | 2 GB RAM | 4 GB RAM | | 20 req/sec | 100 req/sec | 1000 req/sec | \*The number of nodes mentioned above is the default number of nodes for each network size. It is recommended to have a total of at least 3 orderer nodes in the entire network for production deployments. \*\*The req/sec mentioned above are indicative numbers and the actual performance of a network depends on various factors like the number of organizations, channels, endorsement policies, the performance of chaincode, etc. Learn more about Nodes: [Nodes: Peer, Orderer & CA](/products-overview/private-network/networks/nodes-peer-orderer-and-ca) {% hint style="info" %} Spydra allows users to add a custom number of nodes while creating Network, joining a Network, or later on from the Node page. It is recommended to have an odd number of Orderer nodes for consensus.
[Why is it recommended to have an Odd number of Orderer nodes on a Network?](/support/why-is-it-recommended-to-have-an-odd-number-of-orderer-nodes-on-a-network) {% endhint %} {% hint style="info" %} Only organizations that have a Network Admin role will be able to add Orderer Nodes. This can be used to limit which organizations should be able to participate in the network consensus. {% endhint %} {% hint style="info" %} Changing the Network Configuration will also affect your Organization's pricing. Please learn more about the pricing here. \ \ [Pricing](/billing-and-pricing/pricing) {% endhint %} ## How to Choose Network Configurations? You can choose a Node Configuration based on your requirement and the limitations of the Network Configurations. If you are still unsure about how to go about it, we recommend you choose the Network Configuration based on the below illustration. * Proof of Concepts / Testing - **Small Networks** * Startups / SMBs / Small-Medium scale projects - **Medium Networks** * Enterprises / Large Scale projects - **Large Networks** For more information and guidance for choosing specific orderer and peer size and number, refer to [Nodes: Peer, Orderer & CA](/products-overview/private-network/networks/nodes-peer-orderer-and-ca). # Mandatory Card Addition Adding a card is a mandatory requirement for the following actions: 1. Auto-pay for billing: If you want to enable auto-pay for billing, you will need to add a card to your account. This will ensure that the payments are made automatically and on time, without any manual intervention required. 2. Access to higher configurations: If you require access to higher configurations and resources, you will need to add a card to your account. This is because these higher configurations come at an additional cost, which is charged to the card on file. ### Configurations that require adding a Card These are the following configurations or flows that require you to Add a card for your organizations as these come at additional cost. * Dedicated Networks * Medium and Large Network Configurations * Adding custom Nodes You will be prompted to add a card if you are trying to add these configurations.
{% hint style="info" %} If payment details are added to the account, it can have up to 10 active networks. This means that you can create and manage multiple networks simultaneously within the account. If you wish create more networks, please [contact support](https://www.spydra.app/support) {% endhint %} {% hint style="info" %} However, if payment details are not added, the account is limited to only one network. This means that you can create and use only a single network within the account. {% endhint %} {% content-ref url="/pages/AYPgz2f6L8uih25bNWc9" %} [Adding a Card & Autopay](/billing-and-pricing/adding-a-card-and-autopay) {% endcontent-ref %} # Nodes: Peer, Orderer & CA Nodes play a crucial role in maintaining the integrity and security of the blockchain network. They work together to ensure that transactions are processed accurately and that the blockchain remains tamper-resistant. There are 3 types of Nodes in a Hyperledger Fabric network: Orderer, Peer and Certificate Authority Nodes ### Orderer Nodes The orderer nodes are responsible for maintaining the order and consistency of transactions on the blockchain. They ensure that all transactions are recorded in the correct order and that there are no conflicts between them. Spydra supports the [Raft](https://hyperledger-fabric.readthedocs.io/en/latest/orderer/ordering_service.html#raft) protocol which is the de-facto implementation of ordering service for Fabric v2.x networks. **Guidance on choosing orderer node size and number**: Every pre-configured network size provided by Spdra has a default size and number for the orderer nodes. You can change the number of orderer nodes while creating or joining a network. * All organizations need not deploy orderer nodes. Organizations that want to be part of the blockchain network consensus process should deploy orderer nodes. * The total number of orderers in the network should be an odd number as this is recommended for the Raft protocol. * Raft provides Crash Fault Tolerance (CFT). Having more number of nodes improve resiliency as more nodes can be lost and the ordering service can still be functional. A five node cluster, for example, can tolerate two down nodes, while a seven node cluster can tolerate three down nodes. * However, more nodes mean a larger communication overhead, which could eventually slow the network. Raft clusters of more than a few dozen nodes begin to see noticeable performance degradation. * Adding more number of nodes does not help with improving performance as orderer nodes are not load balanced. Choosing a higher size for the node does improve performance. * Clusters of three, five, seven, or nine orderer nodes in a network are the most popular. * For additional information on choosing orderer nodes, refer [here](https://hyperledger-fabric.readthedocs.io/en/latest/deployorderer/ordererplan.html#cluster-considerations). ### Peer Nodes The peer nodes are responsible for executing transactions, maintaining the ledger, and participating in the consensus process. They communicate with other peer nodes to validate transactions and reach a consensus on the state of the ledger. **Guidance on choosing peer node size and number**: Every pre-configured network size provided by Spdra has a default size and number for the peer nodes. You can change the number of peer nodes while creating or joining a network. * The size and number of the peer nodes have a direct bearing on the performance of the network. * Peer nodes are load balanced. So, increasing the size and number of nodes generally improves performance. * For additional guidance on choosing peer nodes, refer [here](https://hyperledger-fabric.readthedocs.io/en/latest/deploypeer/peerplan.html#sizing-your-peer-resources). ### CA Nodes The Hyperledger Fabric Certificate Authority (CA) node is responsible for managing the digital certificates and identities of network participants. It uses a Public Key Infrastructure (PKI) system to issue and manage digital certificates that are used to authenticate and authorize network participants. Spydra provides a CA node for each organization by default and nothing additional needs to be done to enable this. The certificates and related keys are securely stored in a dedicated Hashicorp vault that is provisioned for each organization. # Network Hosting Type ### Shared Networks * Infrastructure and virtual network resources will be shared with other Blockchain Networks for **Cost Optimization** * Data isolation: Blockchain networks and the network’s data & compute resources are logically isolated from other Blockchain networks even though the resources are shared * A separate set of nodes for every organization is still provided and the network data is stored in a separate storage explicitly created for that network ### Dedicated Networks * Physical isolation is provided at the underlying infrastructure and virtual network level. * The Blockchain nodes and data are physically separated into dedicated clusters created for that particular network, and the data traffic is routed through isolated virtual networks # Network Dashboard Network Dashboard helps you manage and monitor your Fabric Network by showing the Network Summary details like the Number of Channels, Nodes, Organizations, and Apps. This also includes showing the API transaction history and Activity log.
Learn More [Network Dashboard](/how-to/private-network/networks/network-dashboard) # Network Operations ### Why certain actions are restricted when an operation is running?
When an operation runs in a Network that utilizes infrastructure (such as containers or virtual machines), certain actions may not work due to the locked or unavailable resources. For example, if an operation is running in a container, other actions that require access to the container's resources may not be able to execute until the operation is complete. This could include modifying the container's configuration or accessing data stored within the container. {% hint style="info" %} If the operation is taking much longer than expected time, please reach out to our Support via messenger or email us at with the Network ID.\ \ You can find the **Network ID** on the Network Overview page.\ \ *Sometimes, the Operation can take more time depending on the resources, overall network load, and other factors. If it takes exceptionally longer than expected reach out to Support.* {% endhint %} ### List of operations When one of the operations is running, the user will be restricted from doing another operation. * Network creation and updation * Joining an Organization * Role and Node update * Listeners - Creation, Update, Delete * Edit and Deployment of App (Chaincode) # Nodes Nodes are the individual servers that make up the network. Each node runs an instance of the App you are running, which allows it to participate in the network and perform various tasks, such as validating transactions and maintaining the shared ledger. Adding a node helps improve the network's scalability by increasing transaction processing capacity and enhances fault tolerance by providing redundancy and resilience to the network. \ Also, a Node is a logical function in the sense that multiple nodes of different types can run on the same physical server. With Spydra, you can run Peer nodes and Orderer nodes to participate in the network. Peers are the fundamental elements of a Hyperledger fabric network since they host ledgers and Smart contracts/Chaincodes. Orderer (also known as an “ordering node”) is responsible for transaction ordering, which along with other orderer nodes forms an ordering service. In addition to their ordering role, orderers also maintain the list of organizations that are allowed to create channels and enforce basic access control for channels. To learn more about Node types, please read [Nodes: Peer, Orderer & CA](/products-overview/private-network/networks/nodes-peer-orderer-and-ca) {% content-ref url="/pages/D26kvhImryJAwRIODi3L" %} [Create Node](/how-to/private-network/nodes/create-node) {% endcontent-ref %} # Channels Channel on Spydra is a private “subnet” of communication between two or more specific network members. Each channel is defined by member organizations, shared ledgers, chaincode applications, ordering services, and anchor peers. Private or confidential transactions can be carried out within the channel among members. With Spydra, your deployed Network comes with a default channel, and all organizations part of the network will automatically be part of the default channel. Additionally, Spydra also provides you the option to add new channels to the network with custom memberships. {% content-ref url="/pages/GYwTGEXeVcEhnx2BblrC" %} [Creating a Channel](/how-to/private-network/channels/creating-a-channel) {% endcontent-ref %} # Apps Apps are computer programs that are stored on the blockchain as smart contracts. They are designed to implement specific business use cases and can be deployed on various networks. These applications are a secure and transparent way to execute transactions and processes. By utilizing blockchain technology, businesses can ensure the reliability and immutability of their data while maintaining a high level of privacy and security. Additionally, these apps can operate autonomously, interact with your existing tech stach with REST APIs and operate based on predefined rules, reducing the need for intermediaries and increasing efficiency. Overall, the use of blockchain apps can revolutionize the way businesses operate and interact with each other. **There are 2 types of apps** 1. [Pre-Configured Apps](/products-overview/private-network/apps/pre-configured-apps) 2. [Custom Apps](/products-overview/private-network/apps/custom-apps) # Pre-Configured Apps Pre-configured Apps/ Chaincodes are pre-written smart contracts that are already installed and available on the blockchain network for use. The pre-configured Apps/Chaincodes are designed to perform a specific set of functions and tasks and help solve a business case. This makes it easier for Spydra users to create blockchain-based use cases without having to write the code for the smart contract from scratch. In addition, pre-configured Apps/Chaincodes can also be customized to meet the specific requirements of a particular use case. Spydra can create properties with low or no code interface or integrate them with other systems or applications. Overall, pre-configured Apps/Chaincodes are a useful tool for users who want to create blockchain-based applications quickly and efficiently. By using Spydra's pre-written smart contracts, users can focus on other important problems without having to worry about the underlying blockchain technology. ## Spydra's Pre-configured apps {% content-ref url="/pages/JbwQr1k1g5vtfzPxWtmb" %} [Asset Tokenization](/products-overview/private-network/asset-tokenization) {% endcontent-ref %} # Custom Apps Custom Apps/Chaincodes are programmable code that define the business logic and rules governing the interactions and transactions within a blockchain network. They are written in programming languages such as Go, JavaScript, or Java, and are deployed onto the network. Custom chaincodes enable participants in the network to define and execute complex transactions, update the shared ledger, and enforce business rules specific to their domain or use case. They provide the flexibility to tailor the behavior of the blockchain network to suit the specific requirements of the application being developed or deployed on the Network. The chaincode is used to perform actions like creating, updating, or deleting data on the blockchain. It is recommended to carefully design and test chaincode to ensure that it functions correctly and meets the needs of the network. ## Spydra's Custom Apps Spydra allows users to deploy their own Custom chaincode/App to meet their Business requirements. Learn more about deploying Custom Chaincode {% content-ref url="/pages/1wtoh1kKvvsKxGf5vRq3" %} [Deploy Custom Chaincode](/how-to/private-network/custom-apps/deploy-custom-chaincode) {% endcontent-ref %} # Asset Tokenization ## Asset Tokenization: An Overview Asset Tokenization refers to the process of converting physical assets into digital tokens that can be easily tracked and traded on a blockchain network. In recent years, asset tokenization on the blockchain has gained significant popularity in industries such as supply chain, mining, and pharmaceuticals due to its benefits, including transparency, security, data immutability, fractional ownership of assets, etc, and reduction of fraud and corruption. ## Spydra's Asset Tokenization Spydra’s Asset Tokenization is a configurable pre-built low-code app that enables customization based on your Business use case and deploys your Business logic on Blockchain Network in a few clicks without worrying about creating and maintaining any smart contracts. One of the key elements of our platform is the ability to control permissions for all participating organizations on every asset and event. This allows for greater flexibility and control over who can access, edit, and view specific assets. With Asset Tokenization's REST APIs, it is easy to integrate Asset Tokenisation without changing your existing stack and popular ERPs like SAP, Navision, and Oracle ERP.
Asset tokenization will enable Businesses to create, update, track & trace Assets and Events in different industry use cases like Supply chain, Logistics, and Medicine. {% content-ref url="/pages/Y32rjEO6dnJusUVGDK7v" %} [Deploy Asset Tokenization App](/how-to/private-network/pre-configured-apps/deploy-asset-tokenization-app) {% endcontent-ref %}
# Use cases ## Asset Tokenization use cases #### Supply chain management Asset tokenization provides a decentralized ledger system that enables stakeholders to track the movement of goods and assets across the supply chain. It also ensures data transparency, security, and immutability, reducing the risk of fraud or corruption. #### Mining industry Asset tokenization enables miners to tokenize their mineral reserves, allowing investors to purchase fractional ownership of the reserves. This helps miners raise capital, while investors can benefit from the asset value appreciation. #### Pharmaceutical industry, Asset tokenization can help to reduce the risk of counterfeit drugs by creating a tamper-proof supply chain. Each drug can be assigned a unique token, and its movement can be tracked throughout the supply chain, ensuring that it is not tampered with or counterfeited. {% content-ref url="/pages/Y32rjEO6dnJusUVGDK7v" %} [Deploy Asset Tokenization App](/how-to/private-network/pre-configured-apps/deploy-asset-tokenization-app) {% endcontent-ref %} # Asset types An asset type refers to the category, type, or class of an asset that is being represented on the blockchain. An Asset can be anything of value that can be traded, such as real estate, stocks, bonds, commodities, art, intellectual property, and more. To tokenize an asset on the blockchain, it is necessary to define its asset type and specify all the relevant properties as required. Each asset type may have multiple instances, which can be distinguished by their unique characteristics. For instance, if the asset type is "car," there can be several cars with their respective properties, such as KA00201 (Red, BMW, 2020), DL00201 (White, Audi. 2021), and US00201 (Red, BMW. 2022). You can add as many properties for an Asset when you are creating an Asset without even defining them. Spydra stores all the properties with the asset which can be queried later on.
{% content-ref url="/pages/Y32rjEO6dnJusUVGDK7v" %} [Deploy Asset Tokenization App](/how-to/private-network/pre-configured-apps/deploy-asset-tokenization-app) {% endcontent-ref %} # References A reference is a relationship established between two Asset types, where one Asset refers to the primary key of another Asset. References are used to ensure data integrity and consistency. They enable you to maintain the relationships between Asset types and prevent the creation of abanded records.
For example, if you have two Asset types, "Sneaker" and "Sole" which represent Sneakers and Sole the sneakers have. The "Sneaker" asset can reference the "Sole" which is present in the sneaker and also have its own history individually.
{% content-ref url="/pages/Y32rjEO6dnJusUVGDK7v" %} [Deploy Asset Tokenization App](/how-to/private-network/pre-configured-apps/deploy-asset-tokenization-app) {% endcontent-ref %} # Asset Owners Assets represent a Digital copy of a Physical good. Learn more about Assets and Asset types here:\ [Asset types](/products-overview/private-network/asset-tokenization/asset-types) ### Asset Owners Simply kept, Assets are owned by a single individual or entity/Organization depending on the stage or step of the Asset. \ For example, in a supply chain context, an Asset might represent a Product, and ownership of a specific product might change from Manufacturer to logistics partner as the product is out for shipment of goods as they move from one location to another. In the end, the ownership can be moved to the buyer or end user.
Depending on the use case, the owner can be with the Organization or a User part of the Organisation.
```jsx { "assetType": "vehicle", "data": [ { "vehicleid": "car007", "type": "vehicle", "vehicleNo": "XXXX-YYYY", "Manufacturer":"BMW", "Model":"x1" }, "owners": [. // OWNERS OF THE ASSET { "orgId":"org_id" "userid": "user_id" } ] ``` # Permissions Permissions refer to the rights and privileges granted to different participants or organizations on the network. These permissions define what actions can be performed on the assets that are present on the blockchain network. **These actions can include creating, updating, viewing, and deleting assets.** For example, let's consider an asset type "Product". In this case, permissions can be set for each organization involved in the network, defining what actions they can perform on the product asset. The manufacturer can be given permission to create the product asset, while the logistic partner can be given permission to update and view the asset. However, the manufacturer may not have permission to update the asset. By setting permissions, access to sensitive or confidential data can be restricted, ensuring that only authorized organizations or participants can perform certain actions. This can help to prevent unauthorized modifications or deletions of data, ensuring integrity and security. Additionally, permission settings can be updated or modified as needed to accommodate changes in the network or to meet new business requirements.
{% content-ref url="/pages/Y32rjEO6dnJusUVGDK7v" %} [Deploy Asset Tokenization App](/how-to/private-network/pre-configured-apps/deploy-asset-tokenization-app) {% endcontent-ref %} # Tokens & Vault ### Spydra's Token Engine Spydra's Token Engine is a powerful component of the Spydra platform that enables the creation and issuance of tokens. It provides a seamless and efficient way to tokenize various assets, including currencies, securities, real estate, and more. With the Token Engine, users can define the specific characteristics and properties of their tokens, such as supply, divisibility, and transferability. This allows for the customization of tokens to meet specific business requirements and regulatory compliance. The Token Engine utilizes smart contract technology on blockchain networks to securely create and manage tokens. It ensures transparency, immutability, and traceability of token transactions, providing a trusted and decentralized environment for token issuance. Spydra's platform enables customer's to create both fungible and non-fungible tokens. #### Fungible Tokens Fungible tokens are a type of digital asset that can be exchanged on a one-to-one basis. Each token is identical and interchangeable with other tokens of the same type. Fungible tokens are commonly used for representing currencies or commodities, where each unit has the same value as any other unit. They are stored and managed on blockchain platforms and enable seamless transactions between participants. #### Non-Fungible Tokens (NFTs) Non-Fungible Tokens (NFTs) are a unique type of digital asset that represent ownership or proof of authenticity of a specific item or piece of content. Unlike fungible tokens, each NFT is distinct and cannot be exchanged on a one-to-one basis. NFTs are often used to represent digital collectibles, artwork, virtual real estate, or in-game items. Each NFT has its own unique value and cannot be replaced by another token. Spydra follows ERC-1155. ERC-1155 is a token standard on the Ethereum blockchain that allows for the creation of both fungible and non-fungible tokens. It provides a more efficient and flexible way to manage multiple token types within a single smart contract. Read about [REST API](/developers/api-reference/asset-tokenization/rest-api#tokens) to understand better. *** ### Fractionalizing Assets using Vaults Spydra uses vaults to facilitate the fractionalization of assets. Fractionalizing assets refers to the process of dividing a single asset into multiple smaller shares, allowing for broader ownership and investment opportunities. By tokenizing the asset and representing it as fungible tokens, the vault allows users to purchase and own fractional shares of the asset. Custodian is a crucial concept of vault. Custodian refers to a trusted entity or organization that holds and safeguards assets on behalf of others. Custodians play a crucial role in ensuring the security and integrity of digital assets. Read about [REST API](/developers/api-reference/asset-tokenization/rest-api#vault) to understand better. # Listeners 'Listeners' is a service that allows businesses to receive real-time notifications when specific events occur on Networks and Deployed Applications. These notifications can include transactions, smart contract events, and more. By using Listeners, businesses can streamline their workflow and quickly respond to critical events as they occur. ### Spydra allows two types of Listeners 1. [Network Listeners](/products-overview/private-network/listeners/network-listeners) 2. [App Listeners](/products-overview/private-network/listeners/app-listeners) # Network Listeners Network Listeners allow you to get notified when certain events happen on a Network. ## Network Events ### **Block Event** All the details about the block when a block is created on the ledger. The event data is a JSON structure containing the following fields: * **channelName**: Name of the channel that generated the event * **eventType**: BlockEvent * **eventData**: The entire block and its data that is written on the ledger. To understand the Block data structure, please refer [here](https://hyperledger-fabric.readthedocs.io/en/latest/ledger/ledger.html#blocks). ### **Transaction Commit Event** Every time a transaction is committed to the blockchain, the transaction data will be sent. The event data is a JSON structure containing the following fields: * **channelName**: Name of the channel that generated the event * **eventType**: TransactionEvent * **eventData**: The entire transaction and its data that is written on the ledger. To understand the transaction data structure, please refer [here](https://hyperledger-fabric.readthedocs.io/en/latest/ledger/ledger.html#transactions). # App Listeners App Listeners allows you to get notified when certain events happen in an App. The current list of supported events are: ### List of App Listener events #### **Asset** * Asset Type Created - When an Asset type is created * Asset Type Updated- When an Asset type is updated * Asset Type Deleted- When an Asset type is deleted * Asset Created- When an Asset is created * Asset Updated- When an Asset is updated * Asset Owners Updated- When Asset owners are updated * Asset Deleted- When Asset is deleted * Approval Request Created- When an ownership approval request is created * Approval Request Updated- When an ownership approval request is updated * Request Approved- When a request is approved * Request Rejected- When a request is rejected * Request Cancelled- When a request is cancelled #### Workflow This event should be enabled if the 'Raise Event' action is set up in a workflow. Once enabled, you will be notified every time the workflow goes through a raise event block. Refer workflow action -[Actions](/how-to/private-network/workflow/actions#raise-event) *** The event data is a JSON structure containing the following fields: * **channelName**: Name of the channel that generated the event * **chaincodeName**: Name of the chaincode that generated the event * **eventType**: The event type above that identifies the specific event * **eventData**: The actual event data returned from the ledger E.g. Event :: Create Asset ```json { "channelName": "default", "chaincodeName": "supplychain", "eventType": "CreateAsset", "eventData": { "chaincode_id": "supplychain", "tx_id": "d0c1358c29c294b7ed999dc20150e286b85232a882ce101580b3edbd4a327371", "event_name": "CreateAsset", "payload": { "message": "Created asset id - car1.", "data": { "id": "car1", "assetType": "Car", "data": { "Id": "car1", "color": "red", "engine": { "id": 9001, "isDefective": true, "lotId": 123, "model": "petrol" }, "make": "ford", "status": "recalled", "year": 2020 }, "owners": [ { "orgMSP": "641821e82c44573cb52c7d97" } ], "createdAt": "2023-05-13T02:20:46.881413278+05:30", "updatedAt": "2023-05-16T21:27:46.015214724+05:30", "createdBy": { "orgMSP": "Org1MSP" }, "updatedBy": { "orgMSP": "Org1MSP" } } } } } ``` # Token Listeners Token Listeners allows you to get notified when certain events happen in an App. The current list of supported events are: #### **Tokens** * InitializeToken: triggered when a token type is initialized/ created. * UpdateToken: triggered when a token is updated. * UpdatePermissions: triggered when permissions for a token are updated. * Mint: Event triggered when new token(s) are minted. * Burn: Event triggered when token(s) are burned or destroyed. * SetApproval: triggered when an approval is set for a token. #### **ERC1155** * TransferSingle: triggered when a token is transferred from one address to another. * TransferBatch: triggered when a tokens are transferred in a batch. * ApprovalForAll: triggered when a user is approved to manage all tokens that belong to a user. **Vault** * InitializeVault: triggered when a vault is initialized. * UpdateVault: triggered when a vault is updated. * Deposit: triggered when assets are deposited into a vault. * Withdraw: triggered when assets are withdrawn from a vault. # Workflow Builder A workflow refers to a series of steps or actions that are executed in a specific order to complete a task or achieve a particular goal. Spydra's workflow feature is designed to create a powerful Smart contract to automate work and manual tasks. The element of workflow include: * **Triggers**- Events or conditions that initiate the execution of a workflow on changes to a particular asset, token or a scheduled trigger. * **Workflow Conditions-** Criteria used to determine branching or execution paths within a workflow based on boolean evaluations of variables or inputs. * **Actions**- Specify the action to be automated for records that meet the set criteria. Example: In the below example, the workflow is triggered when an asset called bills is initiated and it updates the insurance asset also as claimed in the same transaction
See how to define a [Workflow](/how-to/private-network/workflow) # Oracles Smart contracts cannot make http requests directly due to the decentralized nature of blockchains. If http requests are made via chaincode, the data may differ per request. This issue is resolved by using an oracle to ensure that the data returned is consistent across all nodes for each transaction. Some advantages of using an oracle for smart contracts include: * Ensuring consistency of data across all nodes in the network * Allowing the smart contract to interact with off-chain data sources * Providing greater flexibility in the types of data that can be used in smart contracts * Enabling the smart contract to respond to real-world events in a timely manner Some of the use-cases include: 1. **Supply Chain Management:** Oracles can fetch real-time data about the location, condition, or authenticity of goods in transit from external sensors or tracking systems. This can be useful for verifying compliance with shipping terms or environmental conditions. 2. **Financial Products & Derivatives:** Smart contracts can use oracles to obtain real-world financial data, like stock prices or foreign exchange rates, to execute functions such as settling a contract upon reaching a particular stock price. 3. **Insurance Claims:** In the event of natural disasters like floods or hurricanes, oracles can pull data from weather agencies to automatically trigger insurance payouts for smart contract-based insurance policies. 4. **Real Estate:** Oracles can fetch data about property prices, tax rates, or rental income, allowing for the creation of decentralized property marketplaces or rental agreements. 5. **Agriculture:** Smart contracts can use oracles to get data from weather stations, which could decide, for instance, the payout amount for crop insurance if there’s a drought or heavy rainfall. 6. **Decentralized Identity Verification:** Oracles can fetch and verify identity-related data from trusted external sources, facilitating decentralized identity verification processes. 7. **Electricity Trading:** In decentralized energy grids, oracles can fetch real-time data on electricity production (e.g., from solar panels) and consumption, enabling automated, peer-to-peer energy trading. 8. **Internet of Things (IoT):** Oracles can relay data from IoT devices to the blockchain. For instance, data from a smart lock can confirm receipt of a delivery, triggering payment in a blockchain-based supply chain solution. Learn how to create and use and oracles - [Oracles](/how-to/private-network/oracles) # GraphQL ### **What is Graph Query Language?** GraphQL is a query language for APIs for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, makes it easier to evolve APIs over time, and enables powerful developer tools. For an overview of GraphQL, please refer to .
## Spydra's GraphQL Spydra’s QraphQL allows you to query Blockchain databases easily and efficiently. With its ability to support complex queries, you can access data in a streamlined manner. Not only can you execute simple queries based on any field of an object on the ledger, but also nested and paginated queries, as well as more complex ones. By leveraging the power of Spydra's Graph Query, you can simplify your blockchain data interactions and streamline your workflow. You can only query data using GraphQL and we do not support modifying ledger data using mutations with GraphQL at this time. For a list of supported queries please refer [here](/developers/api-reference/asset-tokenization/graphql). # Block Explorer Block explorer is a tool used to view and navigate through the contents of a blockchain. Block explorer provides valuable insights into the transactions, addresses, and overall state of the blockchain network. Use Spydra's block explorer feature to: 1. View Transactions: Explore and search for specific transactions by its hash. You can examine transaction details and owner details. 2. View Blocks: Explore and search for specific block by a block's number. You can examine number of transaction in the block and other details. 3. Monitor Network Stats: Keep track of network statistics, including the total number of transactions, the block height, and the overall health and performance of the blockchain network. To explore block explorer- * Open any active network details. * Click 'Block Explorer' option on the left menu * You will see a tabular data with following column information * Transaction ID * Block number- if a block has 10 transactions, 10 rows with the same block number will be displayed. * Transaction type- * CONFIG Transaction:\ Represents a transaction used to make changes to the network's protocol or rules. These can include various settings like block size, transaction fees, consensus rules, or other network-specific configurations. * CONFIG\_UPDATE Transaction:\ Represents a transaction which is typically initiated by a network participant, such as validator or administrator, who wish to propose modifications to the network's configuration settings. * ENDORSER\_TRANSACTION:\ Represents a transaction that has been endorsed by the required endorsers, indicating that the transaction has gone through the endorsement process and is ready for further processing, validation, and inclusion in a block * Organisation- which added the transaction * Application name * Age of the block * Search for a transaction using a transaction ID or search for a block using block number
* Click 'Details' to view detailed JSON of each transaction
# IPFS IPFS (InterPlanetary File System) is a distributed peer-to-peer protocol and network designed to create a decentralized and permanent method for storing and sharing files on the internet. It aims to replace the traditional centralized client-server model with a distributed and peer-to-peer approach. Spyra's IPFS comes with the following benefits: 1. Private Network to ensure data privacy- Store and share files only with participants of the network. 2. Easy deployment- Integrate with our REST APIs and never worry about scalability, security or performance. \ [IPFS](/developers/api-reference/ipfs) 3. Cluster Management- While IPFS is designed to work in a peer-to-peer fashion, cluster management introduces additional capabilities and features to optimize the usage of IPFS in scenarios where a group of nodes needs to work together efficiently.\ [Nodes: Peer, Orderer & CA](/products-overview/private-network/networks/nodes-peer-orderer-and-ca) {% hint style="info" %} Only organisations with an IPFS node can upload and store files. {% endhint %} # Fabric Debug Plugin ## Hyperledger Fabric Debugger for Visual Studio Code Hyperledger Fabric Debugger Plugin is an Open Source Extension for Visual Studio Code that makes it easy for developers to build and debug Chaincode right from within the IDE. Typically, developing Chaincode for Fabric requires developers to set up a Fabric environment, deploy the developed Chaincode to it and then debug it by printing log messages to the console. In addition, installing a new version of Chaincode in a Fabric network is not as simple as uploading the new code. Developers have to execute the chaincode lifecycle commands for every modification to upgrade the Chaincode. This makes it very difficult to develop code in an iterative manner. By using the Hyperledger Fabric Debug Plugin, a developer does not need to set up a Hyperledger Fabric network to deploy and test Chaincode. The plugin will automatically set up a local Fabric environment and manage the process of installing the Chaincode. {% hint style="info" %} Installing Fabric Debugger: You can install debugger for VS Code from the Microsoft Visual Studio Code's Marketplace.\ \ [Install Debugger](https://marketplace.visualstudio.com/items?itemName=Spydra.hyperledger-fabric-debugger) {% endhint %} # Public Chain Spydra is a comprehensive platform that empowers users to tokenize real-world assets and create personalized digital marketplaces. At its core, the platform features a Token Store - a centralized hub where users can create, customize, and showcase their digital tokens while accessing powerful tools for trading, monitoring, and community engagement. **Key Platform Capabilities:** * **Token Store Management:** Create and manage your digital marketplace with complete control over asset presentation and investor interactions. * **Investor Compliance:** Set up robust compliance frameworks by defining investor properties, including regional restrictions and KYC requirements. * **Token Sale Management:** Monitor and control token sales with real-time transaction tracking and the flexibility to initiate new sales with customizable parameters. * **Investor Management:** Keep track of your investor base, monitor investment levels, verify KYC status, and track token-related activities. **Technical Foundation:** The platform utilizes the ERC-3643 protocol, providing a standardized framework that ensures interoperability, security, and efficient management of Real World Assets (RWAs). **Core Benefits:** * Raise funds through tokenization * Access new investor demographics * Enhanced asset liquidity Through Spydra's platform, users can deliver a superior investment experience while efficiently managing their tokenized assets in compliance with regulatory requirements. # Token Store The Token Store serves as the centerpiece of Spydra's platform, providing a dynamic and customizable space for users to create, showcase, and manage their tokenized assets. Acting as a personalized digital marketplace, the Token Store enables seamless interaction with potential investors by offering tools for branding, trading, and engagement. With intuitive customization options, users can design storefronts that align with their brand identity and effectively highlight their assets. # Tokenize Real World Assets Spydra simplifies the complex process of asset tokenization, allowing users to digitize and fractionalize tangible assets such as real estate, art, collectibles, and more. By providing a detailed framework for asset documentation, valuation, and investment terms, the platform ensures transparency and trust. With tokenization, users can unlock liquidity, broaden their investor base, and make traditionally illiquid assets accessible to a global audience. # Tokenomics: Token & Token Sale Spydra's platform provides robust tools for defining tokenomics, ensuring that each token sale is tailored to the issuer’s goals. Users can configure key token attributes like supply, pricing, and trading rules while maintaining compliance with regional and regulatory requirements. The token sale management system allows for the creation of multiple sales with adjustable parameters such as soft caps, timelines, and investor restrictions, enabling flexibility and strategic fundraising. # Trade & Payout Efficiently manage token transactions and payouts with Spydra's comprehensive trade and payout tools. The platform tracks minting, buying, and burning transactions, offering real-time insights into token activity. Issuers can manage returns by initiating equity or debt payouts with a streamlined process, ensuring timely distributions to investors. With automated tracking and clear reporting, Spydra simplifies ongoing management of tokenized assets, strengthening investor trust and operational transparency. These features collectively make Spydra a powerful and versatile platform for tokenizing assets, managing token sales, and engaging with the digital investment ecosystem efficiently and securely. # Private Network # Account This section will help you understand setting up your account and all things related to your account. # Create an Account You can create an Account with Spydra with just a few clicks using your Google account or by entering the details and verifying your email. ## Sign up with Gmail * Navigate to * Click on **Signup with Google** * Login to your Google account or select the account if you are already logged in. * Once you verify the Gmail account, your signup process will be complete, and you will be redirected to Spydra Console. ## Signing up your Email and Password * Navigate to * Enter the required details like Name, Email, and Password. * Then click on **Create Account** to verify your email address * You will receive a verification email on the email address entered * Verify the email by clicking the verification link that you received on the email address * Once your email is verified, your signup process will be complete. * Please refresh the tab where you were Signing up. ### Next steps * Once your account is created, you can create or join an organization with an invite. Then create a network to deploy your app onto that network. You can also invite other organizations to join you on the network. # Edit Profile details You can edit profile details like Name, Phone number, Company, and Country from the Profile detail page. {% hint style="info" %} If you want to update your email address or password, please refer to the [Update email & Password](/how-to/private-network/account/update-email-and-password) {% endhint %} ### Edit Profile details * Login to your Sypdra account and click on the user Profile icon at the right top * Select User profile ![Screenshot](https://images.tango.us/workflows/6ce748aa-59ca-49c5-b47f-4e44ddfee337/steps/55650acb-04f6-4486-ba21-0c4162f607da/6bbaf358-0666-41ab-98ba-f8280a2811e3.png) * Make the required changes to the profile details. ![Screenshot](https://images.tango.us/workflows/6ce748aa-59ca-49c5-b47f-4e44ddfee337/steps/145b207f-c047-4b56-992d-e56566ba45b2/9a52327c-8970-40cf-83d5-0490616373fa.png) * And Save done.
{% content-ref url="/pages/UdaEc69gPQk2pQ28SFUU" %} [Update email & Password](/how-to/private-network/account/update-email-and-password) {% endcontent-ref %} # Update email & Password This article will guide you if you want to update your email address or account password. ## Update Email * Login to your Spydra account and navigate the profile section by clicking on the profile icon on the top right.
* Click on Update Email to change the Email address associated with the account. ![Screenshot](https://images.tango.us/workflows/bdf273fd-d2d2-41a1-8465-a06fb954459a/steps/5f7dc5fa-a9bd-4569-9182-ba3fc4f79fb5/942e1ac2-c6e2-4457-9144-d4f14291d8b0.png) * Enter the current password to Authenticate your account. ![Screenshot](https://images.tango.us/workflows/bdf273fd-d2d2-41a1-8465-a06fb954459a/steps/876d04bc-34a9-4483-89ce-6f65ba379e9b/b5caaeb1-ac1c-4a37-bcf3-28a95c437cf1.png) * After successful authentication, update the New email. ![Screenshot](https://images.tango.us/workflows/bdf273fd-d2d2-41a1-8465-a06fb954459a/steps/a8034535-1864-4cbe-91ba-2e3d9329256c/cc44a2f7-6b5c-46a7-a4c0-11de21e5ea1c.png) * The email will be updated. Click on Send a Verification link to verify your new email. ![Screenshot](https://images.tango.us/workflows/bdf273fd-d2d2-41a1-8465-a06fb954459a/steps/2f75a478-66e9-40d6-a10c-311bc87650c2/a1a13095-234b-46e9-8733-0c78717f119a.png) * The email will be tagged as Verified post successful email verification. ![Screenshot](https://images.tango.us/workflows/bdf273fd-d2d2-41a1-8465-a06fb954459a/steps/01d7c7e2-2f26-4a6a-917b-0e6810253e2b/22dfe2af-abb8-417f-8a77-3d38a8705d6e.png) ## Change Password * To change the existing password, navigate to the Security section in your Profile and select Account Settings.
* Click on Update password ![Screenshot](https://images.tango.us/workflows/fbd62c6a-7f96-45ee-952f-c1e001931309/steps/122be25e-6c98-46f2-8a31-abef49ffd009/eb67d511-7daf-4f6a-8351-bf224b147a4a.png) * Autheticate yourself by entering your current password. ![Screenshot](https://images.tango.us/workflows/fbd62c6a-7f96-45ee-952f-c1e001931309/steps/7a6e25fa-5e7e-4038-b770-86e0ed0b10e2/8a6600cd-b188-4e5b-a7f6-cd29b61b6e5d.png) * Enter new password and confirm it ![Screenshot](https://images.tango.us/workflows/fbd62c6a-7f96-45ee-952f-c1e001931309/steps/c106512e-259b-4c0b-828e-727ee233c68d/d5020d5e-8106-4fca-98b5-885ae418b2d9.png) * Click on Update password. ![Screenshot](https://images.tango.us/workflows/fbd62c6a-7f96-45ee-952f-c1e001931309/steps/ae24aa0a-8fcf-4994-8b29-5bc06c3cbff3/59203db5-b50d-404b-ac3f-e564087bb72a.png) ### Other resources: [Google OAuth Signup - Update Email & Password](/how-to/private-network/account/google-oauth-signup-update-email-and-password) # Forgot password ## Forgot Password * If you have forgotten your password and need a reset, click on **Forgot Password** on the Login page. ![Screenshot](https://images.tango.us/workflows/67975256-8e35-480e-84a0-2acbfec6ab00/steps/cc8cd4da-6565-49cd-9c8f-b3f0968b8769/09a2592f-3bd5-4ad9-83b9-c332afb5e028.png) * Enter the email and click on Send the email. ![Screenshot](https://images.tango.us/workflows/67975256-8e35-480e-84a0-2acbfec6ab00/steps/8af73394-bb2a-4883-8ce5-8f15c5dc887a/d07c1c95-4a3b-4ca3-aca1-68e23e5691f5.png) * Open the link you receive and enter a new password. ![Screenshot](https://images.tango.us/workflows/67975256-8e35-480e-84a0-2acbfec6ab00/steps/1e585ddf-ba91-4d38-82e3-4c317331af61/f265b6f8-73ce-48a3-809d-74aa9a50a476.png) * Save the password and your password will be updated. ![Screenshot](https://images.tango.us/workflows/67975256-8e35-480e-84a0-2acbfec6ab00/steps/3cfb743e-24cc-40e2-95de-951cd68dd859/b85808a3-ca82-49ec-92a1-0b6f8f7f6fb1.png) \* You will be prompted to log in again with the new password and then taken to the Spydra console. * You will receive an email to set a new password. * Open that link and enter a new password. ![Screenshot](https://images.tango.us/workflows/67975256-8e35-480e-84a0-2acbfec6ab00/steps/1e585ddf-ba91-4d38-82e3-4c317331af61/f265b6f8-73ce-48a3-809d-74aa9a50a476.png) * Post that, the password will be updated successfully. ![Screenshot](https://images.tango.us/workflows/67975256-8e35-480e-84a0-2acbfec6ab00/steps/3cfb743e-24cc-40e2-95de-951cd68dd859/b85808a3-ca82-49ec-92a1-0b6f8f7f6fb1.png) # Google OAuth Signup - Update Email & Password If you signed up using Google OAuth, we do not have the option to update your email or password. Please reach out to if you have any such requests. # Deactivating or deleting your account? We do not have the option to delete or deactivate an account from the console. Please reach out to for any such requests. If you are an org admin, we'll be unable to delete your account as your account is associated with an organization. Deletion of Organizations is currently not allowed because Organization is the core part of Spydra accounts. **Please transfer your ownership of the Organization admin to one of the team members to process your request.** # Organizations {% hint style="info" %} Organizations form the basic unit in the SPYDRA platform. Once you signup for an account with SPYDRA, the first step is to create[ Create an organization](/how-to/private-network/organizations/create-an-organization) or be a member of an existing organization. {% endhint %} An Organization is a logical entity, which can be as large as a multi-national corporation or as small as an individual. Each organization can have users added as members with different access rights. They are required to perform all other activities and operations on the Spydra Platform. You will require organizations to create a blockchain network and deploy chaincode applications. In the Spydra console, under the organization's section, you can view the list of all organizations that you created or are part of.
* You can create an unlimited number of Organizations * You can join other organizations through invitations * You can invite other users as members to your organization with defined access rights * You can manage user memberships for your organization * You can create a Hyperledger Fabric Blockchain Network using your Organization * You can deploy Chaincode applications on your Hyperledger Fabric Network through your organization * You can interact with deployed Chaincode applications through your organization's network * You can setup Billing Address and multiple payment methods for your organization * You can monitor your organization's activities through Organization's dashboard * You can utilize the Credits associated with your organization (***Note:*** Credit applies only to the first three organizations for an account) Get started by [creating an Organization](/how-to/private-network/organizations/create-an-organization) # Create an Organization {% hint style="info" %} Creating an Organization is a key step in the Spydra Platform as Organization acts as a core component.\ \ Spydra **offers $400 free credits for the first 2 organizations** you create to help you explore the platform. {% endhint %} 1. Navigate to the Organization section in the Spydra platform from the top nav bar; you can view the list of Organizations if you have already created one or joined other organizations. 2. Click on **Create Organization**
* Enter Organization Name
* Add the Billing country * Click on Create Organization * Congratulations! Your Organization has been created.
You can now see the Created Organization under the Organization's list. ### Next steps * Once an organization is created, you can invite your team as organization members and create a network to deploy your app onto that network. You can also invite other organizations to join you on the network. {% content-ref url="/pages/1IomauJ4i6CrWMM8T5ug" %} [Invite members to an organisation](/how-to/private-network/organizations/invite-members-to-an-organisation) {% endcontent-ref %} {% content-ref url="/pages/RYnEXt12olzvpzyPB5jF" %} [Create a Network](/how-to/private-network/networks/create-a-network) {% endcontent-ref %} # Create & Manage BYOC Hosting By default, Spydra provides hosted cloud services on both Azure and AWS. However, Spydra provides users a flexibility to utilize their own existing cloud infrastructure to deploy and manage a network. BYOC (Bring Your Own Cloud) allows organizations to use their existing cloud infrastructure to deploy and manage the blockchain network on Spydra Platform. This approach provides flexibility, cost savings, and the ability to meet specific compliance and security requirements. Currently, Spydra supports the integration of user accounts from both **Azure** and **AWS**. This feature allows users to efficiently manage and monitor Spydra's blockchain network through these popular cloud service providers. ### Adding your own Cloud Hosting (BYOC): Once an organization is created, go to the organization dashboard and click on the "Hosting" tab. This tab displays all cloud hosting services added by the organization, with Spydra Managed Azure and Spydra Managed AWS visible by default. To add a new cloud hosting service, click "Create Hosting."
#### Add AWS Cloud Hosting: To create a new AWS cloud hosting, follow these steps: 1. **Add a cloud source name** for easy reference later (e.g., "Supply Chain AWS Cloud"). 2. **Select 'AWS'** in the Cloud provider dropdown. 3. **Enter Secret Key** 4. **Enter Access Key** Once these details are filled in, the user can proceed to create a new hosting. If the provided access key and secret key are correct, the new hosting will be added to the organization. #### Add Azure Cloud Hosting: To create a new Azure cloud hosting, follow these steps: 1. **Add a cloud source name** for easy reference later (e.g., "Supply Chain Azure Cloud"). 2. **Select 'Azure'** in the Cloud provider dropdown. 3. **Application ID** 4. **Tenant ID** 5. **Application Secret** *** {% hint style="success" %} Organizations using BYOC hosting can only create a dedicated network. Only organizations with dedicated hosting can join a network hosted by BYOC. {% endhint %} *** #### Leverage your own cloud hosting (BYOC) to, {% content-ref url="/pages/RYnEXt12olzvpzyPB5jF" %} [Create a Network](/how-to/private-network/networks/create-a-network) {% endcontent-ref %} {% content-ref url="/pages/Ij4VKxzMyp9ls5U4R7Mv" %} [Joining a Network](/how-to/private-network/networks/joining-a-network) {% endcontent-ref %} # Invite members to an organisation {% hint style="info" %} Administrators of organizations can invite their team members to join their organizations and collaborate. {% endhint %} ## Inviting a user to join the organization * Navigate to the organization list and select an organization. ![Click on Apple Inc](https://images.tango.us/workflows/4db38004-eeb9-4fc5-a705-535ef157d3bd/steps/0d118e9a-9955-4588-9a82-0ed4e7fb47a3/de104ed3-6913-4c83-a1c0-b701f9dd3a3c.png) * You can click on 'Invite Members' from the organization's membership section**.** ![Click on Membership](https://images.tango.us/workflows/4db38004-eeb9-4fc5-a705-535ef157d3bd/steps/2f92efc0-7d7b-4613-8a05-0e4160ed03ff/22db12bf-dab5-434a-a1ff-a5db7b8047fb.png) ![Click on Invite Member](https://images.tango.us/workflows/4db38004-eeb9-4fc5-a705-535ef157d3bd/steps/bfd93399-5bb3-4761-981c-46f16ab3f4af/5be1d3ba-1ecd-4a18-b13f-8d01568b60a6.png) In the pop-up, you can enter the email address and specify the organization access by selecting the role. You can learn more about Organization Roles here - [Organization Roles & Permissions](/products-overview/private-network/organizations/organization-roles-and-permissions) ![Click on Org Admin](https://images.tango.us/workflows/4db38004-eeb9-4fc5-a705-535ef157d3bd/steps/b027769f-e562-4492-87c4-7ca9304f06a4/06043596-4e3e-473a-87b2-16d092107aa1.png) ![Click on Send Invite](https://images.tango.us/workflows/4db38004-eeb9-4fc5-a705-535ef157d3bd/steps/92aba5c6-97d9-4a91-b4af-6b537bbe065e/9f00263b-30f7-4439-abee-0cb9c03e7b98.png) Once you click on **Invite**, the user will receive the invite in their email, and they can accept your invitation and join your organization. ![Click on alert](https://images.tango.us/workflows/4db38004-eeb9-4fc5-a705-535ef157d3bd/steps/cb966fb9-2311-4843-8462-4aa010a3dded/b5bd749e-920a-476d-a078-2c5ff8c276a4.png) Organization Administrators can also view the list of invitations sent on the Org Members page. The list of pending invites is displayed, and org admins can choose to **Resend the invite** or **Cancel the Invite**. # Edit Organization details {% hint style="info" %} Organization admins can edit Organization details, manage membership, manage Organization membership invitations, and manage billing & payments for your Organizations. {% endhint %} ### View / Edit Organization details. Once you have created an Organization, you can view the Organization details in the **Overview** section of the Organization. * Organization Administrators can edit Organization information such as Organization name, primary email address, billing information, and payment methods.
### # Manage Org members ## Removing Organisation members If you want to remove any members from your organization, * Navigate to the organization listing page on the platform [https://console.spydra.app/organizations](https://dev-web-user.spydra.app/organizations) * Select the organization to go to the organization detail page ![Click on Membership](https://images.tango.us/workflows/d588260b-fea1-44a3-b831-cd47c93ca40a/steps/f6214253-24ba-43d0-91a1-2babbf549f26/787cf1aa-117b-4ec5-801a-5674d92e33c4.png) * Click on the Membership ![Click on Actions](https://images.tango.us/workflows/d588260b-fea1-44a3-b831-cd47c93ca40a/steps/e07d45a6-e669-4207-883d-f210e8078f2f/fdfed853-86a0-4cb7-916c-ee72ab9d4105.png) * Select the users and click on 'Remove membership.' * Post confirmation, the member will be removed from the organization. ![Click on Remove Membership](https://images.tango.us/workflows/d588260b-fea1-44a3-b831-cd47c93ca40a/steps/2a1d5ce2-a9cb-4ca9-9060-73fbbd781b37/d2bc6280-cfe3-4a68-a89a-e89c977ba131.png) 7
{% hint style="info" %} Please note only Organisation admins can remove members from an organization. Instead of removing members from an organization, you can restrict members' access by updating the role. * [Manage organization member roles](/how-to/private-network/organizations/update-organization-member-roles) {% endhint %} ## # Leave an Organization ## Leave an Organization * Navigate to the organization listing page on the platform [https://console.spydra.app/organizations](https://dev-web-user.spydra.app/organizations) * Select the organization to go to the organization detail page * Click on Leave the organization in the organization overview section * After confirmation, you'll be removed from the organization.
{% hint style="info" %} If you are the Admin of the organization will not have the option to leave the organization. Transfer your admin rights to another organization member if you want to leave the organization. Please note in this case, you'll lose all the following admin rights, and the new Admin will gain these rights. * All the rights on the networks the organization is part of. * Becomes the network admin for the networks created by your organization. * Full access to the billing section for your organization {% endhint %} # Update Organization member roles {% hint style="info" %} Only Organization Administrators can edit Organization membership roles.\ \ If you are the only Organization Admin, you will not be allowed to leave the Organisation or change your role. {% endhint %} ## Update Organization Memberships Role * Navigate to the organization from the Organization list * Select Membership ![Click on Membership](https://images.tango.us/workflows/d588260b-fea1-44a3-b831-cd47c93ca40a/steps/f6214253-24ba-43d0-91a1-2babbf549f26/787cf1aa-117b-4ec5-801a-5674d92e33c4.png) * Org Admins can edit the membership role by clicking on Actions and clicking on Update role * Select the appropriate for the members and save, * The user's role will be updated.
# Pay Organisation Invoice ## Billing details * Navigate to the Organisation from the organization listing page. * Click on Billing and select Billing Details. ![Click on Billing Details](https://images.tango.us/workflows/82d081bd-a215-4eb2-8c7b-790d6874c76e/steps/debad73d-5501-4087-9104-e36efb6245c9/d6224992-866c-48ed-a5c0-766417857874.png) * You'll see an option to pay the due if there's any overdue bill * If you have any credits available, you can choose to use them. * Click on PAY ![Click on Pay](https://images.tango.us/workflows/82d081bd-a215-4eb2-8c7b-790d6874c76e/steps/a69ce0d3-0f6e-4e19-b954-2e3fd9a469ad/7520c5c7-91b7-42b4-8a8b-bec28077a0ad.png) * Enter your card details, and confirm the payment. ![Click on Email](https://images.tango.us/workflows/82d081bd-a215-4eb2-8c7b-790d6874c76e/steps/819a129c-48e5-4027-8fdc-b94ea7d08347/a2adeb9a-6ab5-4151-95e9-479b4edf7212.png) * Post successful payment, you will be redirected to the Invoice History page where you can see the invoice details.
# Update Billing Address The billing Address is the address that will be shown on your invoices. Billing details are taken when an Organization is created; if you want to update this, Org admins can update the Billing address from Organisation's Billing details page. ## Update billing address * Navigate to the Organization where the Billing Address needs to be updated. * Select Billing details in the sidebar
* Scroll down to see the Billing address and click on Edit. * Enter your updated Address and save.
# View Invoices ## Invoices History * If you want to see all the invoices of your account, Navigate to the Organisation from the organization listing page * Select billing history in the Billing section * You can find all the Invoices paid previously there
# Organization Dashboard Spydra offers a unified view of all activities happening within the organization through a dedicated dashboard for each organization. You can access the organization dashboard within the respective organization.
The Organization dashboard will show an overview of important and critical information about the Organization * summary of the Organization details such as org name, org country, org active status, membership count, and network membership count. * Sections for billing and membership with graphical representations. # Delete an Organisation {% hint style="info" %} Deletion of Organizations is currently not allowed as Organizations are the core part of Spydra accounts.\ \ Please contact support\@spydra if you have queries about this action. {% endhint %} # Networks {% hint style="info" %} A blockchain network is a technical infrastructure that allows applications to access ledger and smart contract services. {% endhint %} Blockchain networks can be mainly classified as public, private, consortium, or hybrid depending on network access, data permissions, participant types, degree of decentralization, protocol/framework, and other factors as well. In Hyperledger, a Fabric permissioned blockchain network is a technical infrastructure that provides ledger services to application consumers and administrators. Fabric Network comprises unique organizations (or members) that interact with each other. Each Fabric Network has multiple components such as - Ledgers, Chaincode, Peer Nodes, Ordering Services, Channels, and Certificate Authority. Spydra allows its users to create and manage Hyperledger fabric networks and deploy pre-configured chaincode applications on the network. In the Spydra console, under the networks section, you can view the list of all networks that you created or your organization is part of.
# Create a Network {% hint style="info" %} Creating a network is essential in the Spydra platform to deploy Apps/Chaincode, and the prerequisite for creating a network is to [create an organization](/how-to/private-network/organizations/create-an-organization). {% endhint %} * Navigate to the Network section in the Spydra console, you can view the list of Networks if you have already created one or if your organization is already part of other Networks. * Click on **Create Network**
* You will enter the network creation wizard, and the first step is to enter network details - organization, network name and network description. * You'll be prompted to create an organization if you haven't created an organization earlier. Once you create an organization, you'll be redirected to the Network creation wizard. * You have to update the configuration details in the next step of the network creation wizard. Here, you can choose the cloud service provider, deployment cloud region, number of nodes (peers, orderers, etc.), hosting type (shared/dedicated), and whether media storage is required or not (IPFS requirement for network)
1. **Cloud Provider:** You can choose between cloud providers like AWS and Azure to host your data. You have the option to use Spydra's hosted cloud provider or bring your existing cloud (BYOC) infrastructure to set up the network.\ [Create & Manage BYOC Hosting](/how-to/private-network/organizations/create-and-manage-byoc-hosting) 2. **Cloud Region:** This is where you want your data to be hosted on the server. 3. **Network Configuration:** We offer 3 node sizes, Small, Medium, and Large, with different computational power. [Learn more](/products-overview/private-network/networks/network-configurations) 1. Number of Peer nodes 2. Number of orderer nodes. *It is recommended practice to have an odd number of Orderer Nodes on a Network.* [Learn more](/support/why-is-it-recommended-to-have-an-odd-number-of-orderer-nodes-on-a-network) 4. **Hosting type:** Choose between shared and dedicated types. By sharing the network, other organizations can also be hosted on the same network, reducing the pricing for each node. If you go ahead with a dedicated network, no organizations will be sharing that network. 5. To see how these selections affect your billing, please look at [Pricing](/billing-and-pricing/pricing)
Type of nodes / SizeSmallMediumLarge
Peer nodesWith 0.5 CPU, 1 GB RAM, 20 GB StorageWith 1 CPU, 2 GB RAM, 50 GB StorageWith 2 CPU, 4 GB RAM, 150 GB Storage
Orderer nodesWith 0.5 CPU, 1 GB RAM, 20 GB StorageWith 1 CPU, 1 GB RAM, 50 GB StorageWith 1 CPU, 2 GB RAM, 150 GB Storage
1. Once you select the responses from the dropdowns, click **Next** 2. You can review the entered details on the Confirm details and click on **Confirm & Create**. If any changes are required, you can navigate to the previous section to update the changes and proceed again to deploy. 3. Congratulations! Your Network has been created. 4. You can now see the Created Network under the Networks list. *** #### Advance Settings: **Key Vault** By default, Spydra sets up a key vault using HashiCorp Vault for every organisation part of the network. All the node related keys, certificates and credentials are stored in the vault. Users can connect an external key vault to store secrets and certificates necessary for the Spydra platform for your organisation. Managed services like Azure Key Vault or AWS Secrets Manager can be used. Other popular vaults will be available soon. Learn how to connect your key [Advance Settings: Key Vault Store](/how-to/private-network/networks/advance-settings-key-vault-store) {% hint style="info" %} On the platform, users are allowed to create one network using the free credits provided. Should you wish to create an additional network, you will need to add a valid payment method to the organisation [Adding a Card & Autopay](/billing-and-pricing/adding-a-card-and-autopay) {% endhint %} # Advance Settings: Key Vault Store Connecting your own key vault enhances security by providing centralized, encrypted storage for sensitive data. It simplifies compliance with regulatory requirements through robust access control and audit capabilities. Spydra offers a Hashicorp Vault for each organization to store node-related keys, credentials, and certificates. Users can access "Advanced Settings" in the hosting tab when creating a network. Users can connect managed key vault services like Azure Key Vault or AWS Key Manager to store keys and certificates during network setup.
However, user's will not be able to switch back to Spydra's default Hashicorp vault once your key vault is connected. #### Connecting Azure Key Vault * Uncheck the 'Default' Spydra managed Hashicorp vault option. * Choose Azure Key Vault as your 'External Vault Source'. When selecting the source, if you've previously connected an Azure Key Vault, it will appear as an option. Otherwise, you'll need to connect a new Azure Key Vault To proceed and connect your Azure Key Vault, ensure the vault details are correct: 1. **Vault Name**: Use a descriptive name for easy identification. Example- Blockchain Azure keys. 2. **Application ID** 3. **Tenant ID** 4. **Application Secret** 5. **Key Vault URL** {% hint style="success" %} Find details in your Azure Key Vault account by referring to [Azure's documentation](https://learn.microsoft.com/en-us/azure/key-vault/secrets/quick-create-net?tabs=azure-cli#setup). {% endhint %} #### Connecting AWS Key Manager * Uncheck the 'Default' Spydra managed Hashicorp vault option. * Choose AWS Key Manager as your 'External Vault Source'. When selecting the source, if you've previously connected an AWS Key Manager, it will appear as an option. Otherwise, you'll need to connect a new AWS Key Manager. To proceed and connect your AWS Key Manager, ensure the vault details are correct: 1. **Vault Name**: Use a descriptive name for easy identification. Example- Blockchain Azure keys. 2. **AWS Access Key** 3. **AWS secret key** 4. **Region** {% hint style="success" %} Find details in your AWS Key Manager account by referring to [AWS Key Manager's documentation.](https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_resource-policies.html) {% endhint %} # View and edit Network details {% hint style="info" %} Network Administrators can edit network membership information, update access, invite organizations, remove existing members in a network, manage API keys, manage callbacks, and deploy chaincode applications on the network. {% endhint %} ### View / Edit Network Details Once you have created a network, you can view the details in the **Overview** section. * Navigate to the network listing page [https://console.spydra.app/networks](https://dev-web-user.spydra.app/networks) * Click on the network you would like to edit * In the Overview section, you can view Network information such as network name, parent organization, org membership count, home region, network status, node count, channel count, and the deployed app count. * Network admins can edit information such as network names and transfer the network's ownership by changing the parent organization. * If the parent organization is changed, the admin of the parent organization will be the new Network admin.
### # Update Permissions for Network Members A Network can have any number of organizations added as members with defined access rights. Network admins can manage membership for the network. The network membership list can be viewed under the membership section of the network. * Network admins can navigate to the network detail page and select membership. * Then the role for the membership can be updated by clicking actions and selecting Update roles. * Then, one out of three roles defined for network org members can be selected. * Network Administrator * Network Contributor * Chaincode Admin Network Admins can set and change permissions for membership organizations using these defined roles. This access will determine the data access and operations each member organization can perform within the network.
### # Update Network Configuration Every Network Configuration comes with a different configuration in terms of the number of Nodes, speed, and computational power. Learn more about Network Configurations from the below article. {% content-ref url="/pages/OmBQMOn5BgXESDECrgvI" %} [Network Configurations](/products-overview/private-network/networks/network-configurations) {% endcontent-ref %} ### Updating Network Configuration To change the Configuration of the Network, * Navigate to the Networks page * Click on Members in the side menu * For the Organization you want to update configuration, click on Actions and select Update Configuration
* Select the new configuration for the Network and Submit
{% hint style="info" %} If you are upgrading your Network to Medium or Large, you need to add a payment method for your Organization to utilize this configuration. [Mandatory Card Addition](/products-overview/private-network/networks/mandatory-card-addition) {% endhint %} # Update Key Vault Users can upgrade their key vault from Spydra's default Hashicorp Vault to managed services like Azure Key Vault or AWS Key Manager for securely storing node credentials, certificates, and keys. However, user's will not be able to switch back to Spydra's default Hashicorp vault once your key vault is updated. To connect your managed vault service, follow these steps: 1. Navigate to the `Organisations` tab on the network details page. 2. Click on an organisation to view its network-org details. 3. Select the `Update vault` option. 4. Choose to connect to either your managed Azure Key Vault or AWS Key Manager. 5. Click on "Update key Vault' option.
#### To connect Azure Key Vault: * Choose Azure Key Vault as your 'External Vault Source'. When selecting the source, if you've previously connected an Azure Key Vault, it will appear as an option. Otherwise, you'll need to connect a new Azure Key Vault To proceed and connect your Azure Key Vault, ensure the vault details are correct: 1. **Vault Name**: Use a descriptive name for easy identification. Example- Blockchain Azure keys. 2. **Application ID** 3. **Tenant ID** 4. **Application Secret** 5. **Key Vault URL** {% hint style="success" %} Find details in your Azure Key Vault account by referring to [Azure's documentation](https://learn.microsoft.com/en-us/azure/key-vault/secrets/quick-create-net?tabs=azure-cli#setup). {% endhint %} #### To connect AWS Key Manager: * Choose AWS Key Manager as your 'External Vault Source'. When selecting the source, if you've previously connected an AWS Key Manager, it will appear as an option. Otherwise, you'll need to connect a new AWS Key Manager To proceed and connect your AWS Key Manager, ensure the vault details are correct: 1. **Vault Name**: Use a descriptive name for easy identification. Example- Blockchain Azure keys. 2. **Vault Name**: Use a descriptive name for easy identification. Example- Blockchain Azure keys. 3. **AWS Access Key** 4. **AWS secret key** 5. **Region** {% hint style="success" %} Find details in your AWS Key Manager account by referring to [AWS Key Manager's documentation.](https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_resource-policies.html) {% endhint %} # Manage API Keys Network admins can manage the API keys for the network by registering or deleting them. You can view the list of API keys under the respective network if already registered.
You can click on **Create API key** to generate and register new API keys for participant organizations, as a network admin. You can specify the organization, API key name, and expiry date and generate the API key. Once registered, the API key can be deleted only by the network admin.
# Delete a network Only Network admins can delete a network from the Network overview page. Before deleting a network, please ensure that all deployed resources, including any deployed applications, are removed before deleting the network. Please note network deletion is an irreversible operation, and you will lose all the data related to the network once deleted. * Navigate to the network listing page * Click on the network you would like to delete * In the Overview section, you can see an option to delete the Network. * Once the network is deleted, you'll lose all the information related to the Network.
# Inviting an organisation to a Network You can invite an organisation onto a network, but to do that, you need to create a network or be an Admin. The below article will guide you in creating a network. {% content-ref url="/pages/RYnEXt12olzvpzyPB5jF" %} [Create a Network](/how-to/private-network/networks/create-a-network) {% endcontent-ref %} ## Inviting an organization to join the network * Once a network is created, navigate to the network dashboard from the Network listing page. * You can click on Invite Members from the Network page's 'Organisations' section**.** * Enter the email address of the organization's primary contact to be invited, and specify the network access by selecting the role. * Once you click **Invite**, the organization's primary contact will receive the invite in their email.
## Invited organizations * Network Administrators can also view the list of invitations sent out by toggling the **Invitation Sent/Received** under the Manage Invitations section. * The list of pending invites is displayed, and network admins can choose to **Resend the invite** or **Cancel the Invite**. #### Unable to invite an organisation? On the Spydra platform, users are permitted to add up to two organizations to a network utilizing the provided free credits. However, to add a third organization (or more), a saved payment method is required. Please ensure that the organization you're inviting has a saved payment card. [Adding a Card & Autopay](/billing-and-pricing/adding-a-card-and-autopay) Alternatively, you have the option to opt-in to pay for the invited organization, provided you have a saved payment card. [Opt-in Billing](/billing-and-pricing/billing/opt-in-billing) # Joining a Network Organizations can invite you to join their network. You can accept the invitation and be part of that network or choose to decline it. ## Accepting Organization's invite * Once you have received an invitation to join the organization, open the invite link and Sign up on Spdyra if you do not have an account. * You will be prompted with the invitation, or you can view the invite in notifications. * You can view the organization's details and choose to accept the invite or decline. * Once you accept the invite, you will need to enter a few details for your organization for that network. * **Cloud Provider:** Choose providers like AWS and Azure to host your data. You can either choose Spydra hosted or you can bring your existing cloud infrastructure (BYOC) to join the network. \ [Create & Manage BYOC Hosting](/how-to/private-network/organizations/create-and-manage-byoc-hosting) * **Cloud Region:** This is where you want your data to be hosted on the server. * **Node size:** We offer 3 node sizes, Small, Medium, and Large, which come with different computational power. * **Number of Peer nodes** * **Number of orderer nodes** \[We recommend using odd-ordered nodes] * **Hosting type:** Choose between shared and dedicated types. By sharing the network, other organizations can also be hosted on the same network, reducing the pricing for each node. If you go ahead with a dedicated network, no organizations will be sharing that network. Node sizes define the computational power that comes with each node. Refer to the following table:
Type of nodes / SizeSmallMediumLarge
Peer nodesWith 0.5 CPU, 1 GB RAM, 20 GB StorageWith 1 CPU, 2 GB RAM, 50 GB StorageWith 2 CPU, 4 GB RAM, 150 GB Storage
Orderer nodesWith 0.5 CPU, 1 GB RAM, 20 GB StorageWith 1 CPU, 1 GB RAM, 50 GB StorageWith 1 CPU, 2 GB RAM, 150 GB Storage
* **Number of Peer nodes** * **Number of Orderer nodes** * **Advanced Setting - Key Vault** By default, Spydra sets up a key vault using HashiCorp Vault for every organisation part of the network. All the node related keys, certificates and credentials are stored in the vault. Users can connect an external key vault to store secrets and certificates necessary for the Spydra platform for your organisation. Managed services like Azure Key Vault or AWS Secrets Manager can be used. Other popular vaults will be available soon. * Users can connect managed key vault services like Azure Key Vault or AWS Key Manager to store keys and certificates while joining a network. * To connect you own key-vault: Uncheck the 'Default' Spydra managed Hashicorp vault option in the hosting tab. * For instructions on connecting to Azure Key Vault, please refer [Advance Settings: Key Vault Store](/how-to/private-network/networks/advance-settings-key-vault-store#connecting-azure-key-vault) * For instructions on connecting to AWS Key Manager Key Vault, please refer [Advance Settings: Key Vault Store](/how-to/private-network/networks/advance-settings-key-vault-store#connecting-aws-key-manager)
* Once you submit these details, you'll be part of that network. You can view the network under the Network list.
#### Please note: * Only the Network admin can set and update the role for an organization. * You can update the node size from the network page if you want to change the node size. Updation of the number of nodes is not available now. #### Unable to join a network? On the Spydra platform, free credits enable you to add up to two organizations to a network. From the third organization onward, you'll need a payment method added to the organisation, to join a network. Please add a card to your organization to join the network- [Adding a Card & Autopay](/billing-and-pricing/adding-a-card-and-autopay) If you encounter any other issues, please contact your network administrator or [reach out to us](https://www.spydra.app/contact-us) # Network Dashboard Spydra offers a unified view of all activities happening within the network through a dedicated dashboard for each network. You can access the network dashboard within the respective network.
The Network dashboard will show the summary of network information such as participant organization count, deployed chaincode count, node count (peers/orderers) and channel information. There are also detailed sections for Node active status, participant org details, deployed applications, and network activity log. # Apps Apps/Chaincodes/Smart contracts are computer programs stored on the blockchain, which encode business logic and can be automatically executed when predetermined conditions are met. Chaincode is a terminology used in Hyperledger Fabric. It refers to a single or group of smart contracts packaged and deployed into the blockchain network. Apps / Chaincodes can be implemented in several programming languages. Spydra offers pre-configured chaincode solutions such as Asset Management and Token Factory, which can be easily deployed as applications on the Hyperledger Fabric Networks. The chaincode solutions are designed to be implemented for any business use case, such as asset tracking, tokenization, etc. The chaincode application deployment process is simple and intuitive, so non-technical users can also easily implement them. In the Spydra console, you can view the list of deployed applications for each network under the networks section.
# Explore Apps In the Spydra console, you can click on **Explore Apps** under the **Apps** section, and view the list of available Apps solutions that have been pre-configured by the Spydra team for deployment on networks. Currently, Spydra offers a pre-configured App type which is Asset Tokenization for deployment on Hyperledger Fabric networks.
You can click on **View details** and see the details of each app type, and click on **Deploy App** if in case you want to deploy the same. # Deploy App A Hyperledger Fabric Network is a prerequisite for deploying the applications. If you do not have a network already, you will be prompted to create a network and redirected to the deploy application. To deploy a pre-configured App type on a Hyperledger fabric network, there are two different methods: #### First Method 1. Navigate to **Deployed Apps** under the Network section, and click on **Deploy App** 2. You will be prompted with the pre-configured chaincode list, from which you can choose the App type that you want to deploy and click on **Proceed** 3. You will be directed to the Deploy App wizard, where the first step is to confirm Network details - App name and organization. Here the Network, channel, and App type details are pre-populated. 4. You can click on Next and you will be taken to the Deploy App wizard step 2, which will be specific to each App type.
#### Second Method 1. Navigate to the Explore Apps under the Apps section, and choose the chaincode to be deployed 2. You will be prompted to select the network details 3. You will be directed to the Deploy App wizard, where the first step is to confirm Network details - App name and organization. Here the Network, channel, and App type details are pre-populated. 4. You can click on Next and you will be taken to the Deploy App wizard step 2, which will be specific to each App type.
# Manage Apps {% hint style="info" %} Network Administrators and Chaincode Administrators can edit App details, App settings and manage Application APIs {% endhint %} ### View / Edit App Details Once you have deployed an application on the network, you can view the App details in the **Overview** section of the deployed Application under the respective Network. You can view information such as the App name, chaincode solution, deployed network, organization, and channel details. Network admins and Chaincode Admins can edit only the Application name of the deployed App under the **Overview** section. ### Deleting an App Network admins and Chaincode admins can delete an application if required. Please note app deletion is an irreversible operation and you will lose all the data related to the app once deleted. ### View / Edit App Settings For each deployed App, network admins and chaincode admins will have access to view the current App settings as well as edit them if required. You can click on **Settings** under the deployed App to view the App settings, where you can see the deployed App details which were configured during App deployment.
Network admins and Chaincode Admins can click on Edit Settings, to edit the App configuration. Once you click on the Edit Settings, you will be taken through the App deployment wizard where you can add, edit or remove details as required. For example, in the case of Asset Management, you can edit Asset definitions, Event definitions, References, and defined Permissions. Similarly, for Token Factory deployment, you can edit Fungible and Non-Fungible token definitions. {% hint style="info" %} If any permission is given for an asset to an organization then only the owner org will be able to view, update, etc. {% endhint %} ### Manage Application APIs Spydra provides a rich set of APIs at the Application level since we're an API-driven platform. Each deployed Application has its own set of API endpoints that can be accessed by clicking on the **APIs** under the deployed App section. APIs differ between each deployed application, and the APIs can be accessed via a Swagger Interface on the Spydra Console. To access the APIs, API keys are required which are defined by Network admins at the network level for participant organizations. Please refer to the [API Reference](/developers/api-reference) section for further info on APIs.
# Application Dashboard Spydra offers a unified view of all activities happening within the deployed application through a dedicated dashboard. You can access the application dashboard within the respective deployed application in networks. The application dashboard will have a basic summary of deployed application details and the dashboard will also contain information specific to the chaincode solution. #### Asset Tokenization Dashboard This dashboard will show a summary of the asset details such as the defined assets count, defined events count, references count and permissions count. It will also show the asset/event distribution, dependency graph of assets/events, basic details of assets/events, and the latest events.
# Channels Channel on Spydra is a private “subnet” of communication between two or more specific network members. Each channel is defined by member organizations, shared ledgers, chaincode applications, ordering services, and anchor peers. Private or confidential transactions can be carried out within the channel among members. With Spydra, your deployed Network comes with a default channel, and all organizations part of the network will automatically be part of the default channel. Additionally, Spydra also provides you the option to add new channels to the network with custom memberships. Learn more about channels here [Channels](/products-overview/private-network/channels) ### List of Channels The list of channels can be viewed under the Channel section of the respective network. You can view the default channel and all the custom channels here. Channel details such as channel name, admin organization, membership count, node count, and channel active status are listed for each channel. * Navigate to the Network and click on Channels in the side menu * You will be able to see all the channels on that Network * Select a Channel to see details of that Channel
# Creating a Channel ### Adding a Channel Spydra offers the option to add custom channels to the deployed Hyperledger fabric network. * Navigate to the Network where you would like to create or add New channels * In the side menu, select Channels and click on "Add Channel" * Enter details such as the Channel name, description and select the member organizations for that channel. {% hint style="info" %} To create a channel, there should be at least one organization with an Orderer that is part of a channel {% endhint %}
* Once you input the details and click on the "Save" option, your custom channel will be added to the network, andwww you can install chaincodes/Apps on that channel. # Create a Consensus Policy The consensus policy allows for customizable consensus rules, where chaincode deployment can be endorsed by a subset of channel members instead of requiring agreement from the entire network. This flexibility enhances performance and scalability, making Spydra platform suitable for various use cases. ### Chaincode Consensus Chaincode consensus policy dictates when chaincode-related activities like deployment and upgrades can occur within a channel. #### Default Consensus Policy In the default consensus policy, all organizations in the channel receive approval requests for chaincode activities such as deployment and upgrade. Consensus is reached when the majority of organizations approve the request. Once the majority is met, the chain code deployment will continue till its deployed in the channel.
#### Define Consensus Policy Users have the flexibility to customize the default chaincode consensus policy. Select which organizations will receive approval requests and define the conditions under which consensus is achieved. To define consensus policy:
* Select organisations which can endorse * Any organisation can be have the endorsement rights, be it admin, contributor or reader. * Select when the consensus is met * All the selected organisations should endorse * Majority of the selected organisations should endorse * At least one of the selected organisation should endorse the request #### Accepting Consensus Request Organizations can also view the summary and status of other endorsement requests. This functionality enables organizations to monitor the progress and approvals of various requests efficiently. If an organization is an endorsing entity, they will specifically see an option to approve a consensus request. This option will be available on several platforms, including their dashboard, the channel dashboard, and the app dashboard associated with the request. These features collectively streamline the approval process, making it more transparent and easier to manage across multiple channels and networks. #### Meeting Consensus: If consensus is met, the operation will proceed to the next steps, such as deploying the chaincode. At this point, the endorsement requests from other organizations will expire, unless all organizations were required to endorse for consensus. Each time a consensus request is approved, the consensus policy is checked to ensure # Update Channel ### View or Update Channels * Channel details can be viewed under the "Overview" section of the respective channel. * You can view the channel name, admin organization, channel members, node count, and channel active status. Admins can also edit the channel name and add/remove channel member organizations.
### Update Consensus Policy # Channel Members Channel members are the participants who have been granted access to a specific channel within the network. Channel members can be added from the Channel Members page, or while creating a Channel. A channel member can also be removed from the Channel by the Channel Admin which will revoke all access to the channel. Please note just because an Organization is part of the Network doesn't mean that Organization is part of all the channels. One can only get access to a channel when permission is set explicitly.
{% hint style="info" %} An organization with the ONLY active orderer cannot be removed from the channel as there should be at least one Orderer present in the channel. {% endhint %} --- [Next Page](/llms-full.txt/1)