Welcome to Zeeve’s documentation!¶
What is Zeeve?¶
Blockchain adoption is slow due to various complexities that are involved in ideating, deploying, maintaining and extending a solution built over it. IT sector is not well equipped to take on these challenges in the same manner that it has been handling deployments so far, putting big workforce onto their projects. Zeeve is a Blockchain management platform which acts as one’s own Devops and Cloud team. It targets to provide ease to developers & enterprises by targetting 100% automation for their Blockchain solutions, indirectly solving challenges in adoption of Blockchain.
It is backed by a group of Blockchain and IOT experts, which have expertise over various protocols and understand the needs of the industry, the protocol and developers. Initially created to automate some of our personal projects, we saw the need for it externally.
Some basic needs for blockchain solutions are:-
Multi-cloud network deployments. A product should be able to function over any cloud that your client requires it run on without any extra configurations.
Heterogeneous Cloud networks. A Blockchain network might have some nodes running on one Cloud, while some nodes on another. This is important for the next big point which is,
Ability to create consortiums easily. Building consortium is the toughest challenge for the industry. Zeeve targets technical side of this challenge and intends for users to extend their consortium to others through simple UI based interactions.
Making your deployments production grade. Blockchain industry is full of complex protocols. A single left out variable of which may cause some pretty huge consequences. Zeeve helps standardize your deployments, making them ready to use in production.
Monitor/Scale/Optimize your deployments. Scaling your network in count of nodes and monitor and look out for any red flags is vital to any distributed network, but its also something hard to come by as every protocol is unique in their own manner.
Reach your customers easily through marketplace. Zeeve allows users to list their product in marketplace which could , if fully configured can be bought and started in a matter of minutes.
This document will help user to understand different operations onto zeeve and understand its functioning. Welcome!
description: Get the latest documentation and technical details for Zeeve’s innovative platform. Explore our API, integrations, and tools for building scalable, reliable applications on the Zeeve platform.¶
Overview¶
Zeeve is a Blockchain as a Service (BaaS) offering that allows customers to leverage cloud-based solutions to build, host and use their own Blockchain apps, Smart Contracts and functions on the blockchain while the cloud-based service provider manages all the necessary tasks and activities to keep the infrastructure agile and operational. It is an interesting development in the blockchain ecosystem that is indirectly aiding the blockchain adoption across businesses. It is based on, and works similar to, the concept of Software As A Service (SaaS) model.
Dashboard¶
This is the dashboard page of Zeeve where you can see your Networks, Nodes, deployed product details, Node Disk Usage, Node Statistics, and all activity logs
Networks¶
Networks page basically give the details of Network Name, Number of active nodes, Number of inactive nodes, Selected Blockchain Network, Running Products Name, Network Created Date, Health of Network, Action(Statistics, Restart, Stop and Delete) .
Nodes¶
Nodes Page contains the information like Node ID, Network Name, Health, Network’s Region, Network Created Date, Online(Green colour for online and Red colour for Offline) and Action(Statistics, Restart, Stop and Delete).
Stats(Statistics)¶
This action page contains information of Node Performance Details like Network, Region, Created Date, Node ID, IP Address, Node Status, CPU Usage, RAM Usage, Storage, Recent RAM Usage, Disk Usage, Inodes, Network Usage and Load. Basically we can monitor our network in this action.
Restart¶
By using this action we can re-start the Node.
Stop¶
By using this action we can stop the Node.
Delete¶
By using this action we can delete the Node.
Products¶
The products page contains the information about selected blockchain’s product. These products are fully based on Blockchain. There are two types of products we can see here one is free product and another one is paid product.
Free Products¶
Free product is nothing but it’s open source project i.e. is supported by blockchain network e.g. Sawtooth Supply Chain, Sawtooth Tuna Fish. We have no need to pay for it.
Paid Producs¶
There are various paid products offering by blockchain network based on our choice we can choose it and add to our network. Sawtooth offering paid produts like MBC (Menu Based Choice) Conjoint, Lighthouse Studio etc.
API Services¶
Device Data¶
Tasks(Activity Log)¶
We can see all activity logs and related information of tasks here like network creation, product addition, node addition, etc.
Notification¶
In this section we can see all notifications and invitations(refer to or receive from other people to add network).
Night Mode¶
We can change page orientation by using this theme we can select night mode or day light mode, working as vice-versa.
Night Mode¶
Day Light Mode¶
Zeeve Assistant¶
For more information you can communicate with our Zeeve Assistant.
description: Learn how to create a new account on Zeeve’s platform. Our step-by-step guide walks you through the process of setting up a secure and reliable account for accessing our API and tools.¶
Account Creation¶
This section speaks about how to create an account on Zeeve after which user can authorize external accounts/platforms on Zeeve.
Zeeve supports multiple options for creating an account. You can choose to create account with you Google account or Github account. Also you can use your email to create an account and use the same for signing in.
Signing up with google account¶
Click on with Google
You will be redirected to google account page. Fill the email address, password and click Next
After successful sign in with Google, you will be landed to Zeeve’s dashboard.
Signing up with github account¶
Click on with Google
You will be redirected to github account page. Fill the username/email address, password and click Sign in
After successful sign in with GitHub, you will be landed to Zeeve’s dashboard.
Signing up with email account¶
Click on Sign-Up and fill all the required details. Your email-id will act as your username for login.
This will give you a account verification email, clicking which will redirect you to zeeve where you can do successful login.
After successful login, you will be landed to Zeeve’s dashboard.
description: Explore the best practices and technical details for managing authorization in Zeeve’s cloud-based platform. Learn how to secure your data and control access to resources with our API and tools.¶
Cloud Authorizations¶
Zeeve allows you to authorize multiple cloud accounts of yours so as to create networks in the cloud of your choice. You may choose to deploy some nodes of network on one cloud and extend some nodes of the same on another. This cross cloud deployment maybe a major requirement for your usecase or clients especially for creating/expanding consortiums.
Zeeve supports a list of cloud for you to choose from. You can authorize multiple clouds and choose between them at the time of creating networks or nodes. Following is the list of currently supported clouds:-
AWS
Digital Ocean
Google Cloud
Tencent Cloud
INTERESTING FACT: Zeeve doesn’t use blockchain services of any of the supported cloud platforms, and hence is not restricted for the level of features it can provide for a protocol on any cloud.
AWS Authorization¶
Configuration on AWS Portal¶
Before you authorize your AWS account with Zeeve, you’ll need following provide IAM permissions to deploy a network:
Login into the AWS console, go to IAM service by clicking Security Credential on the upper right corner.
Select the User for which needs to be authorized on the Zeeve platform.
Click on Add Permissions button, and Create Inline Policy.
Copy the ACCOUNTID from the upper-right corner (we will need this Account ID in Further Steps).
Click on the JSON button, and add the below mentioned policy, (Please do replace ACCOUNTID with your AWS Account ID)
Write the Policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"logs:CreateLogStream",
"logs:TagLogGroup",
"logs:DeleteLogGroup",
"logs:TagResource",
"logs:PutRetentionPolicy",
"logs:CreateLogGroup",
"logs:DeleteDestination",
"logs:TagResource",
"logs:ListTagsLogGroup"
],
"Resource": [
"arn:aws:logs:*:ACCOUNTID:destination:*",
"arn:aws:logs:*:ACCOUNTID:log-group:*"
]
},
{
"Effect": "Allow",
"Action": [
"logs:DescribeLogGroups",
"logs:DescribeDestinations"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"iam:GetPolicyVersion",
"iam:GetPolicy",
"iam:GetUserPolicy",
"iam:ListAttachedUserPolicies",
"iam:ListUserPolicies",
"iam:GetUser"
],
"Resource": [
"*"
]
}
]
}
Name this policy as Zeeve-IAM-Policy, and click Save.
Grant AWS Managed EC2 Permissions:AmazonEC2FullAccess. a. Click on Add Permissions -> Add Permissions
b. Click on Attach Policies Directly and Search for AmazonEC2FullAccess.
c. Select the permission and Click on Next.
d. On the Review Page, Review the Policy and Click on Add Permissions.
(Only Permissive Protocol) Grant below permissions for Permissive protocols.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"elasticfilesystem:CreateFileSystem",
"eks:ListClusters",
"eks:DescribeAddonVersions",
"eks:RegisterCluster",
"eks:CreateCluster"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"elasticfilesystem:DescribeMountTargets",
"elasticfilesystem:DeleteAccessPoint",
"elasticfilesystem:CreateMountTarget",
"elasticfilesystem:DescribeLifecycleConfiguration",
"elasticfilesystem:DescribeFileSystems",
"elasticfilesystem:DeleteMountTarget",
"elasticfilesystem:CreateAccessPoint",
"elasticfilesystem:DeleteFileSystem",
"elasticfilesystem:DescribeMountTargetSecurityGroups",
"elasticfilesystem:TagResource"
],
"Resource": [
"arn:aws:elasticfilesystem:*:ACCOUNTID:file-system/*",
"arn:aws:elasticfilesystem:*:ACCOUNTID:access-point/*"
]
},
{
"Effect": "Allow",
"Action": "eks:*",
"Resource": [
"arn:aws:eks:*:ACCOUNTID:cluster/*",
"arn:aws:eks:*:ACCOUNTID:nodegroup/*/*/*",
"arn:aws:eks:*:ACCOUNTID:fargateprofile/*/*/*",
"arn:aws:eks:*:ACCOUNTID:addon/*/*/*",
"arn:aws:eks:*:ACCOUNTID:identityproviderconfig/*/*/*/*"
]
},
{
"Effect": "Allow",
"Action": [
"secretsmanager:CreateSecret",
"secretsmanager:UpdateSecret",
"secretsmanager:DescribeSecret",
"secretsmanager:GetSecretValue",
"secretsmanager:PutSecretValue",
"secretsmanager:ReplicateSecretToRegions",
"secretsmanager:TagResource"
],
"Resource": [
"*"
]
},
{
"Effect": "Allow",
"Action": [
"iam:GetRole",
"iam:UpdateAssumeRolePolicy",
"iam:GetPolicyVersion",
"iam:GetPolicy",
"iam:DeletePolicy",
"iam:CreateRole",
"iam:DeleteRole",
"iam:AttachRolePolicy",
"iam:CreateOpenIDConnectProvider",
"iam:CreatePolicy",
"iam:ListInstanceProfilesForRole",
"iam:PassRole",
"iam:DetachRolePolicy",
"iam:ListPolicyVersions",
"iam:ListAttachedRolePolicies",
"iam:ListRolePolicies",
"iam:GetOpenIDConnectProvider",
"iam:DeleteOpenIDConnectProvider"
],
"Resource": [
"arn:aws:iam::ACCOUNTID:policy/*",
"arn:aws:iam::ACCOUNTID:oidc-provider/*",
"arn:aws:iam::ACCOUNTID:role/*"
]
}
]
}
Follow steps 5-7, and Name this Policy as Zeeve-Permissive-Protocol-Policy.
(Only Corda Enterprise) Grant below permissions for Corda Enterprise.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"route53:GetHostedZone",
"route53:CreateHostedZone",
"iam:CreateInstanceProfile",
"iam:DeleteInstanceProfile",
"iam:GetInstanceProfile",
"iam:TagRole",
"route53:GetChange",
"route53:ChangeResourceRecordSets",
"iam:RemoveRoleFromInstanceProfile",
"iam:PutRolePolicy",
"route53:ListTagsForResource",
"iam:AddRoleToInstanceProfile",
"route53:ListTagsForResources",
"iam:DeleteRolePolicy",
"route53:ListResourceRecordSets",
"route53:AssociateVPCWithHostedZone"
],
"Resource": [
"arn:aws:route53:::hostedzone/*",
"arn:aws:route53:::healthcheck/*",
"arn:aws:route53:::change/*",
"arn:aws:iam::ACCOUNTID:role/*",
"arn:aws:iam::ACCOUNTID:instance-profile/*",
]
},
{
"Effect": "Allow",
"Action": [
"kms:PutKeyPolicy",
"kms:DescribeKey",
"kms:CreateGrant",
"kms:EnableKeyRotation",
"kms:Decrypt",
"kms:GetKeyRotationStatus",
"kms:GenerateDataKey",
"route53:DeleteHostedZone",
"kms:GenerateDataKeyPair",
"kms:CreateGrant",
"kms:ScheduleKeyDeletion",
"kms:GetKeyPolicy",
"kms:ListResourceTags",
"kms:TagResource"
],
"Resource": [
"arn:aws:kms:*:ACCOUNTID:key/*"
]
},
{
"Effect": "Allow",
"Action": [
"ecr:DeleteRepository",
"ecr:PutImage",
"ecr:DeleteRepository",
"ecr:TagResource",
"ecr:ListTagsForResource",
"ecr:UploadLayerPart",
"ecr:CompleteLayerUpload",
"ecr:DescribeRepositories",
"ecr:InitiateLayerUpload",
"ecr:BatchCheckLayerAvailability"
],
"Resource": "arn:aws:ecr:*:ACCOUNTID:repository/*",
},
{
"Action": "ec2:*",
"Effect": "Allow",
"Resource": "*"
},
{
"Action": "ec2:*",
"Effect": "Allow",
"Resource": "*"
},
{
"Effect": "Allow",
"Action": "elasticloadbalancing:*",
"Resource": "*"
},
{
"Effect": "Allow",
"Action": "cloudwatch:*",
"Resource": "*"
},
{
"Effect": "Allow",
"Action": "autoscaling:*",
"Resource": "*"
},
{
"Effect": "Allow",
"Action": "eks:*",
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"rds:AddTagsToResource",
"rds:DescribeDBSubnetGroups",
"ecr:CreateRepository",
"rds:DescribeGlobalClusters",
"route53:ListHostedZones",
"ecr:GetAuthorizationToken",
"rds:CreateDBSubnetGroup",
"rds:DeleteDBSubnetGroup",
"rds:ListTagsForResource",
"rds:CreateDBCluster",
"rds:CreateDBInstance",
"rds:DescribeDBInstances",
"kms:CreateKey",
"rds:DeleteDBCluster",
"rds:DescribeDBClusters",
"rds:DeleteDBInstance"
],
"Resource": "*"
}
]
}
Follow steps 5-7, and Name this Policy as Zeeve-Corda-Enterprise-Policy.
Configuration on Zeeve Portal¶
To authorize your AWS account on Zeeve:-
Hover on profile
Click on My Account
Click on My Cloud.
Click on AWS and then click on Add AWS Cloud.
You will need AWS Access Key and AWS Access Secret Key, to authenticate your AWS account with Zeeve.
Digital Ocean Authorization¶
To authorize your Digital Ocean account on Zeeve you’ll need to ensure certain things:-
User must have an account with enough permissions to create -
Project
Droplets
Kubernetes service.
Specific Scope in DO Account:
Read
Write
After which on Zeeve do following steps:-
Hover on profile
Click on My Account
Click on your cloud authentication for Digital Ocean account, click on Authorize digital Ocean.
Click on DigitalOcean and then click on Add Digital Ocean Cloud.
Authorize DigitalOcean will redirect you to login page, you can add your DigitalOcean credentials and then click on Add Cloud.
After that click on the team which you want to give access and click on Authorize Application.
GCP Cloud Authorization¶
To authorize your GCP account on Zeeve you’ll need to ensure certain things:-
Configuration on GCP Portal¶
Enable Below APIs from Google Cloud Platform:
Compute Engine API
Kubernetes Engine API
Steps to enable APIs on GCP Platform
Go to Google Cloud console: https://console.cloud.google.com/
Select the project, in which you need to enable APIs.
Click on APIs and services from the navigation bar and click Enabled APIs and services
Click on + Enable API and Services
Search Compute Engine API in search bar.
Click on Compute Engine API -> Enable/Manage Option
Follow 5-6 step for enabling Kubernetes Engine API.
User must have an account with enough permissions to create -
Specific Permissions in GCP Account:
‘compute.globalOperations.get’
‘compute.machineTypes.get’
‘compute.networks.create’
‘compute.networks.delete’
‘compute.networks.get’
‘compute.networks.updatePolicy’
‘compute.projects.get’
‘compute.regionOperations.get’
‘compute.regions.get’
‘compute.routers.create’
‘compute.routers.delete’
‘compute.routers.get’
‘compute.routers.update’
‘compute.routes.create’
‘compute.routes.delete’
‘compute.routes.get’
‘compute.subnetworks.create’
‘compute.subnetworks.delete’
‘compute.subnetworks.get’
‘compute.zones.list’
‘resourcemanager.projects.get’
‘compute.disks.create’
‘compute.instances.create’
‘compute.instances.get’
‘compute.instances.setMetadata’
‘iam.serviceAccounts.create’
‘iam.serviceAccounts.delete’
‘iam.serviceAccounts.get’
‘iam.serviceAccountKeys.create’
‘iam.serviceAccountKeys.delete’
‘iam.serviceAccountKeys.get’
‘iam.serviceAccounts.actAs’,
‘container.clusters.create’
‘container.clusters.delete’
‘container.clusters.get’
‘container.clusters.getCredentials’
‘container.clusters.update’
‘container.operations.get’
‘container.clusters.list’
‘container.deployments.delete’
‘container.deployments.get’
‘container.namespaces.list’
‘container.namespaces.get’
‘container.services.get’,
‘compute.disks.createSnapshot’
‘compute.snapshots.get’
‘compute.snapshots.create’
‘compute.snapshots.useReadOnly’
‘compute.snapshots.delete’
‘compute.zones.get’
‘storage.objects.create’
‘storage.objects.delete’
‘storage.objects.get’
‘storage.objects.list’
‘iam.serviceAccounts.signBlob’
Configuration on Zeeve Portal¶
Hover on profile
Click on My Account
Click on My Cloud.
Click on GCP and then click on Add GCP Cloud.
Authorize GCP will redirect you to login page, you can add your GCP credentials and then click on Add Cloud.
Login to your Google Cloud account using Google IDP.
Allow Zeeve to access your GCP Account.
You can view your creds in Zeeve Console.
Tencent Cloud Authorization¶
Before you authorize Tencent Cloud on Zeeve, you will need to add Zeeve’s IDP into your Cloud account.
Creating an OIDC IdP¶
On the left sidebar in the CAM console, select Identity Providers > Role-Based SSO.
On the Role-Based SSO page, click Create IdP.
On the page you enter, select OIDC as the IdP type and enter the following IdP information.
IdP Name:zeeve_oauth
IdP URL:https://login.microsoftonline.com/9188040d-6c67-4c5b-b112-36a304b66dad/v2.0
Client ID:505b1146-13fe-4df6-927a-ca57321786fd
Public Key for Signature: For this you can click on this link (https://login.microsoftonline.com/common/discovery/v2.0/keys) then copy all the content and paste it in the column.Click Next to enter the information review page.
Confirm the information you entered and click Complete to save it.
Creating a role for the IdP¶
On the left sidebar in the CAM console, click Roles.
On the role management page, click Create Role.
Select IdPs as the role entity.
On the page you enter, select OIDC as the IdP type.
Select an IdP you created i.e zeeve_oauth.
Set conditions for the role:
oidc:aud:505b1146-13fe-4df6-927a-ca57321786fd
oidc:sub: Delete this.
Click Next.
On the page you enter, associate the QCloudResourceFullAccess and the QCloudFinanceFullAccess policy with the role and click Next.
On the review page, enter the role name and role description (optional) and click Complete to save the above configurations.
Authorizing Cloud account¶
Hover on profile
Click on My Account
Click on My Cloud.
Click on Tencent and then click on Add Tencent Cloud.
Add the ProviderId and RoleARN that you have created in the previous steps.
Login through any of your microsoft personal account, work account or you can add an account.
This will lead you to a consent screen where you will need to Accept the Terms & Conditions to allow Zeeve to use your credentials.
description: Discover how to manage subscriptions on Zeeve’s platform. Learn how to create, update and cancel subscriptions, as well as how to manage the billing, payments and usage of the resources in our platform.¶
Manage your subscriptions¶
This section talks about how one can purcahse a subscription of a service. It will also guide how one can view manage their subscriptions.
Purchase Subscriptions¶
This section is going to guide you how to purchase a subscription of your choice.
API Endpoint¶
Click on the API Endpoint under Buy Services from the left pane and you will be redirected to the purchase page.
Click on the Supported Protocols button on top right and you will be able to see the protocols and their network types that Zeeve offers for creating API endpoints.
Choose the plan of your choice and click on the Subscribe button under the plan of choice. A pop up window will open which will show the plan which you are subscribing. Click on Continue button to proceed with your purchase.
You will be redirected to the payment page to complete your purchase. Fill the card details and click Subscribe.
After successful payment you will be redirected to success page which ensures successful purchase of your subscription.
NOTE: Developer Plan is a free plan and can only be purchased once.
Staking Nodes¶
Click on the Staking Nodes under Buy Services from the left pane and you will be able to see the list of protocols that Zeeve offers for staking.
Click on the protocol card that you want to subscribe. You will be then redirected to the purchase page.
Select the cloud option from Bring Your Own Cloud or Zeeve Managed Cloud and the number of nodes you want to purchase. Based on your selection the total amount for the subscription will be shown. Click on Subscribe button to continue. A pop up window will open, click on Continue to proceed with your purchase.
You will be redirected to the payment page to complete your purchase. Fill the card details and click Subscribe.
NOTE Prices on this page totally depends on the protocol and your selection of different options in previous step.
After successful payment you will be redirected to success page which ensures successful purchase of your subscription.
Full Nodes¶
Click on Marketplace on the left side navigation bar.
You will be landed to zeeve’s market place page. Select the protocol card of you choice to purchase subscription of the protocol.
You will be redirected to purchase page of the protocol, which looks similar to the below image.
NOTE This page can be different for different protocls. Node types can vary from protocol to protocol
Select the number of nodes you want to purchase. You can also view the amount based on your selection of different options and number of nodes. After your selection, click on subscribe button. A pop up window will open similar to the below image. Click on continue.
You will get redirect to the payment page to complete your purchase of subscription. Fill all the required details and click subscribe.
NOTE Prices on this page totally depends on protocol and your selection of different options in previous step.
After successful payment you will be redirected to payment success page which ensures successful purchase of your subscription.
View Subscriptions¶
This section is going to guide you how you can view the subscriptions you purchased.
To view the subscriptions you have purchased follow the steps given below -
Hover on profile
Click on Edit Profile
Click on subscription on the right most side.
In the subscription section you will be able to view the list of subscriptions, you currently have.
In this section you can have a look to detailed information of your subscriptions.
Monthly cost: This tells you about the amount of each of the subscriptions.
Next Billing Cycle: It provides the next renewal date of a subscription.
Total subscribed: This talks about the quantity of each of the item you have purchased with the subscription.
Available: This tells you about available quantity of each of the item associated with the subscription. This number will increase or decrease according to the consumption of the item as you delete a network/node or create a network/adding a node respectively.
This will help you to keep track of the consumption of each of the items, so that you can update your subscription as your needs.
Edit Subscriptions¶
This section talks about how to edit the subscriptions you purchased. You can choose to add more items to your subscription or you can also choose to decrease the quantity of the already purchased items.
Increase items¶
You can increase items of your subscriptions in two ways. Either you can choose to add new items to the subscriotion or you can choose to increase the quantity of alredy purchased items with the subscription.
To add a new item click on the subscribe more button on the right most side of the subscription. Which will redirect you to the purcahse page of the selected product.
To increase the quantify of alredy purchased item follow the steps mentioned below:-
Go to subscriptions section.
Click on the update button on the right most side of the subscription.
A pop up window will be opened similar to the image provided below.
Increase the quantity of the item of your choice by clicking the green button associated to it and click on update button. A continue button will apper on the pop up window.
Clicking on the button will redirect you to the payment page, where you can view the items you have just added. Click on the subscribe button to complete the process of updation of your subscription.
After successful payment of the item you can view your updated subscription in subscriptions section.
Decrease items¶
Go to subscriptions section.
Click on the update button on the right most side of the subscription.
A pop up window will be opened similar to the image provided below.
Decrease the quantity of the item of your choice by clicking the red button associated to it and click on update button.
Clicking on the button will update your subscription. A continue button will apper on the pop up window.
After successful updation you can view your updated subscription in subscriptions section.
*INFO: One can decrease the quantity of an item as much as available quantity of that item.*
Delete Subscriptions¶
This section talks about how to delte the subscriptions you don’t need.
Before deleting a subsection, make sure that any of the items of the subscription is not consumed. Basically, make sure that the purchased quantity and available quantity is same for each of the item associated with the subscription. Otherwise you will not be able to delete a subscription.
Go to subscriptions section.
Click on the update button on the right most side of the subscription.
A pop up window will be opened similar to the image provided below.
Decrease the quantity of each of the item to 0 by clicking the red button associated to it and click on update button. This will delete your selected subscription.
description: Find out how to access and use the API endpoints on Zeeve’s platform. Our API documentation provides technical details on authentication, making requests and handling responses for interacting with our platform.¶
API Endpoints¶
This page has detailed steps on how to
-
Change name
Update security
Create an endpoint¶
NOTE: Purchase a subscription plan before proceeding.
This section will provide you detailed steps for creating an API endpoint.
Visit the API Endpoints page by clicking on API Endpoints under Manage Services from the left side pane.
Click on Add Endpoint card or the button on top right corner. You will be able to see all the subscriptions you bought for the API endpoints.
NOTE: These cards can be different based on your purchased subscriptions.
NOTE: The card will not be visible if the API Units or the Endpoint quota for that subscription has been exhausted.
Click on the card to choose the subscription in which you want add the endpoint. This will redirect you to the endpoint setup page.
Endpoint Info
This step configures the basic and blockchain protocol settings for the endpoint.
Endpoint Name: The name of your endpoint.
Workspace: The workspace in which the endpoint will be added.
Protocol: The blockchain protocol for which the endpoint is created.
Network Type: The network type of the selected blockchain protocol.
Proceed further by clicking on the Next Step button after providing all the details.
Security Configuration
NOTE: Adding security to the endpoint is optional.
This step configures the security settings for the endpoint. An option to add a JWT in your API call to make your endpoint more secure.
Require JWT: Enable this checkbox if you want to add a JWT security option.
Public Key Name: The name associated to the public key.
Public Key: The public key of a assymetric key-pair. Only keys generated using RSA and ECDSA algorithms are allowed.
On clicking the Submit button a pop-up window will open which ensures the successful creation of your endpoint.
On clicking the Continue button you will be redirected to the page where you can see the endpoint you created.
Modify Endpoint¶
This section will guide you on how you can modify an endpoint’s
Name
Security
Visit the endpoint detail page of your endpoint (Manage Services > API Endpoints > Your Endpoint).
Click on the Edit icon in the top right corner.
Change Endpoint Name
After clicking the Edit icon the endpoint name field will become editable. Update the name as required.
Then click the Save button beside the input field to save the name.
A pop-up will confirm the successful updation of the endpoint name.
Modify Endpoint Security
After clicking the Edit icon the security section will become editable.
Toggle the security toggle as per the requirement to turn on or off the JWT security option.
Then click the Save button below to save the update in security.
A pop-up will confirm the successful updation of the endpoint security.
Delete Endpoint¶
Visit the endpoint detail page of your endpoint (Manage Services > API Endpoints > Your Endpoint).
Click on the Delete icon in the top right corner.
A confirmation window will open, click on the Yes button to delete the endpoint.
description: Learn how to build your first network on Zeeve’s platform. Our step-by-step guide provides detailed instructions and resources for setting up and configuring your network infrastructure.¶
How to create my first Network?¶
Zeeve makes the process of blockchain network deployment from a long time consuming one to just a matter of few clicks whilst taking care of the most important bits.
With a handful of steps using Zeeve, it has become so easy to create your own blockchain network. These networks can also be altered as per the need of the required deployment with the help of given protocol specific parameters that helps you align with your desired network performance.
So wondering upon how to begin? Just follow these easy steps:-
Create workspace¶
Click on Workspace on the left side navigation bar.
You will be landed to a page similar to below image.
Click on New workspace. A pop up window will appear.
Give it a name of your choice(in our case we are going to name it Ethereum) and add a short description. Click create. You can see your newly created workspace added to the workspace tab.
Create Network¶
Click on Workspace on the left side navigation bar.
You will be landed to Zeeve’s network listing page where you will get the list of all of the networks you created. Click on Add Network.
You will be landed to the Network Configuration page which looks similar to the below image.
Here you will get to see different cards with different network configuration of diffrent protocols. These cards can be different according to your purchased subscriptions.
Choose the configuration of your choice for creating a network, and click on a card accordingly.
To see protocol specific configuration parameters please refer to the detailed deployment spec using the following links.
description: Get started with Hyperledger Fabric on Zeeve’s platform. Our documentation provides an introduction to the key concepts, tools and techniques for building decentralized applications using Hyperledger Fabric and the Zeeve platform.
meta:
name: robots content: noindex
Hyperledger Fabric Dedicated Node Setup¶
Hyperledger Fabric has one of the most exhaustive sets of available configuration parameters.
This page would help you a lot to achieve a highly customized fabric network.
Create a network¶
Fabric network creation is spread across 4 sections. Please read further to know about each of them.
On the Network Configuration page you will have different cards with different network configurations for Fabric, which looks similar to the image provided below.
NOTE: These cards can be different for your case. Card configurations totally depend on your purchased subscription.
Choose the configuration you want. Click on the card and follow the steps accordingly.
In the first step choose the Fabric version and Consensus type. After that click on Next Step button.
A fabric network is made up of a group of organizations wherein an organization is a mere stakeholder(participant) of the network, this group is called a consortium. You can add an organization by pressing the Add organization button and after that add a name for this organization.
Each organization participate in the network via a few fabric specific pillars namely orderer, peer and certificate authority.
CA: CA(Certificate Authority) can be configured just by providing the admin user name and password.
Orderer: Zeeve supports all the three types of ordering service, which are provided by HL Fabric namely Solo (Single Orderer Network), Kafka and Raft. Making it one of the best tools for deploying fabric-based production networks.
So based upon the requirement, select the type of ordering service and just add the number of orderers using the Add Orderer button under the orderer tab of the organization section.This is the step to configure the channel details.
Batch Timeout is the amount of time to wait after receiving the first transaction, in order to receive more transactions before cutting a block. In case we decrease this value then we get lower latency but decreasing too much will result in a decrease in throughput, as the block will not fill to its maximum capacity.
As indicated in the above screenshot
{ "timeout": "2s" }Maximum Message Count indicates the maximum number of transactions in a block. Also, if we look into
Absolute Maximum Bytes: It indicates the maximum size of a block that can be built in the channel.
In respect of Absolute Maximum Bytes, there is another parameter viz.,
Preferred maximum Bytes which is nothing but the minimum size of a block.
This is the last step in creating a network. select the region for the network by clicking on Select Region, select the AWS account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type, and then click on the Create button.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
View Network¶
Click on Networks on the left side navigation bar.
You will be landed on a page similar to the below image. You can view all of your networks listed on this page.
NOTE This page can be different in your case.
Select the Fabric network you want. After clicking on the network card you can view the nodes attached to the selected network. Network Nodes are listed with details - node’s unique ID and cloud provider, an organization it is part of, node’s role(peer, ca, orderer), and node’s deployment region.
Pipelines are listed with details - pipeline unique ID, the status of the pipeline(completed, in progress, failed), Total Jobs that it holds, and Action (to open up jobs inside it).
Add peer¶
A peer can be added to the organization by only following the two steps mentioned below. You just need to choose the type of peer service for each peer you want to go with, it can be either level Db or CouchDB based, and specify whether you want to have a persistent volume for the same.
Select the network to which you want to add a node, and click on the network card Ref.. You will get to see similar to the below image.
Click on Actions button and select Add Peer.
You will get to see a web page similar to the image provided below. Fill the details and click create button.
Add organization¶
Select the network to which you want to add a node, and click on the network card Ref.. You will get to see similar to the below image.
Click on Actions button and select Add Peer.
You will get to see a web page similar to the image provided below. Fill the details and click create button.
Zeeve CLI¶
This section talks about how to use the Zeeve CLI and how to perform fabric chain code operations.
Create CLI Access¶
Navigate to settings and then click on “API Credentials” to see a list of CLI/API credentials.
Click “Create key”.
Provide a name, and select one or more networks to associate with the key.
Add appropriate permissions for the operations that the keys are being created.
Click “Create key” and then copy/save generated keys.
Chaincode Pipelines¶
Login with Zeeve CLI using the earlier created keys and add these URLs as well -
zeeve login -i < access-key > -s < secret-key > -ae https://app.zeeve.io/auth/cli/login -fe https://app.zeeve.io/fabric-backend/
Zeeve CLI supports fabric chaincode operations - package, install, deploy, approve and commit.
Package: builds chaincode image, creates ECR and pushes into ECR, and creates chaincode connection package to be installed onto peers. Zeeve chaincode pipelines can deploy chaincode as a service (For more details). Following are the inputs required to run package operation
Chaincode zip file is a compressed file of chaincode with the name chaincode.tar.gz
zeeve fabric chaincode package -f /path/to/chaincode.tar.gz -n 44b28e1f-7296-42a4-8904-e04341edfb27 -c marbles2 -v 1.0 -o org1 <br></br>
Install: runs chaincode install operation on given peer URLs.
The install operation can be run on a set of peers in a given org with the peer-URLs option.
zeeve fabric chaincode install -n 44b28e1f-7296-42a4-8904-e04341edfb27 -c marbles2 -v 1.0 -o org1 -p peer1.org1.example.fabric.zeeve.net, peer2.org1.example.fabric.zeeve.net
Deploy: starts chaincode pod/service in Kubernetes cluster.
- zeeve fabric chaincode deploy -n 44b28e1f-7296-42a4-8904-e04341edfb27 -c marbles3 -v 1.0 -o org1 -p peer1.org1.example.fabric.zeeve.net ,peer2.org1.example.fabric.zeeve.net
Approve: runs ‘peer chaincode approve’ on a set of given peers in an org in the channel provided.
zeeve fabric chaincode approve -n 44b28e1f-7296-42a4-8904-e04341edfb27 -cc marbles3 -v 1.0 -o org1 -p peer1.org1.example.fabric.zeeve.net, peer2.org1.example.fabric.zeeve.net -ch mychannel -s 1
Commit: runs ‘peer chaincode commit’ and also inits the chaincode with Init method on the given set of peers and organizations in the provided channel.
zeeve fabric chaincode commit -n 44b28e1f-7296-42a4-8904-e04341edfb27 -cc marbles3 -v 1.0 -o org1,org2 -p peer1.org1.example.fabric.zeeve.net,peer2.org1.example.fabric.zeeve.net -ch mychannel -s 1
Multitenant Networks¶
Zeeve also supports the creation of Mulitenant networks in Hyperledger Fabric. This means that two or more users may be part of a network and may perform network operations collectively.
Inviting A User¶
Select the network to which you want to add a node, and click on the network card.
Click on the Manage Invites tab and click on Invite New Partner.
Enter the Email Address of the user to invite.
Select the system channel checkbox if you want the invited user’s organization to have orderers or be a part of the consortium.
Fill in the maximum number of orderers for the new user.
Select the consortium checkbox to add the user to consortium. Also fill in the system channel policy for the new organization.
Select the application channel checkbox to make the new organization a part of atleast one pre-existing application channel.
Click on the dropdown and select the channel you want to new organization to be a part of. You can select more than one channels but alteast one application channel is required.
Fill in the channel policy for the application channel.
Repeat this for all application channels.
When all the details are filled, click on the “Submit” button. This will send an invite to the user.
Accepting The Invite¶
Go to the settings page
Click on the Network Invite tab.
Click on the View Details button for the invite.
Verify the details and click on approve.
Fill in the details of the new organization.
Click on submit to deploy the new organization.
Certificate Renewal¶
Zeeve supports the ability to renew your fabric certificates at a click of a button. Hyperledger fabric network certificates expire in 365 days. This means that certificates need to be renewed atleast once a year.
Renewing Certificates¶
Click on Renew Certs button on actions tab.
You can see the details of the certificate renewal with expiry date.
Select the organizations for which you need to renew the certificates and click on Renew button.
description: Explore the capabilities of Ethereum on Zeeve’s platform. Our documentation provides an introduction to the key concepts, tools and techniques for building decentralized applications using Ethereum and the Zeeve platform.
meta:
name: robots content: noindex
Ethereum Dedicated Node Setup¶
This section will guide you about different actions you can perform for Ethereum.
Dedicated nodes¶
Create a network¶
This section will provide you with detailed steps for creating a network of Ethereum.
NOTE Please make sure to follow the steps mentioned earlier before proceeding.
On the Network Configuration page you will have different cards with different network configurations for Ethereum, which looks similar to the image provided below.
NOTE: These cards can be different for your case. Card configurations depend on your purchased subscription.
You can Choose Managed-AWS (Zeeve’s managed hosting) for the infrastructure of your node or you can use your cloud account (AWS/DO) for the hosting of your node.
Choose the configuration you want. Click on the card and follow the steps accordingly.
Network Info: Clicking on the card you will be landed on a page similar to the below image. In this section, we have to provide network-related information for ex- Network Name, Network type, etc.
Name of Network: To uniquely identify your network, this field requires a unique name for it. Unique over here is in terms of the account in which you are creating your network. In case you have created some network earlier, and now you are trying to create with the same name, then the Zeeve platform won’t allow you to create it.
Deployment Type: This defines the deployment type
Type Of Network
MainNet: This will deploy your network on the network mainnet. This is suggested for deploying production-grade Ethereum dapps.
Ropsten: This is a testnet you can use for your non-production needs like testing or demonstrations.
Rinkeby: This is yet another testnet that can be used for non-production needs like testing or demonstrations, however unlike ropsten it just supports geth.
Workspace:
After providing all the details correctly go to the next step by clicking on the Next Step button.
Node Configuration: In this section, you have to fill in the details of the nodes you want to add to your network.
Username & Password: Choose the username and password of your choice. These will be used as RPC API credentials.
Email: Fill email of yours.
Node Name To identify your nodes, this field will be used.
Rpc Server: RPC, which stands for “Remote Procedure Call,” is a group of protocols and interfaces that let us talk to the blockchain system. Through the RPC interface, we can ask for information about the blockchain (such as block number, blocks, node connection, etc.) and send a request for a transaction. > * HTTP: Uses individual HTTP requests and responses for each call, similar to a RESTful API. > * ws: WebSocket uses a persistent connection that allows the server to push data to the client.
JSON RPC APIs: JSON RPC API is a bridge that allows dApps to connect to nodes.
After providing the details click on Next step to go to the last step.
Cloud Configuration: This is the step for the configuration of the cloud for your nodes. This step can be different based on your selection of Network configuration cards.
Managed - AWS¶
In the case of Managed - AWS, you don’t have to bother about anything, just select the region for the network by clicking on Select Region.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
BYOC - AWS¶
In the case of BYOC - AWS, select the region for the network by clicking on Select Region, select the AWS account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
BYOC - DO¶
In the case of BYOC - DO, select the region for the network by clicking on Select Region, select the Digital Ocean account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
Click on the Create button. A pop-up window will appear similar to the below image, which ensures the successful creation of your network.
Click on continue and you will be redirected to a page similar to the below image where you can see the nodes listed you’ve just added to the network.
Add node to a network¶
This section will guide you on how you can add a node to a network.
Select the network to which you want to add a node, and click on the network card Ref.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Add Node option. You will get to see a web page similar to that provided below.
Fill in the details for the new node and click on the Next button. In this step, the cloud configuration and region will be prefilled according to the configuration of the network. Click on the Create button and it’s done!
Delete node in a network¶
Select the network, you want to perform the deleted node to, and click on the network card Ref.. You will get to see similar to the below image.
Click on the delete icon present alongside the node. A pop-up window will open for the confirmation, click on the yes button to confirm.
Delete a network¶
Select the network you want to delete, and click on the network cardRef.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Delete Network option. A confirmation window will open, click on the Yes button, attached to it.
NOTE It can take a few minutes to delete a network.
description: Discover the power of Corda on Zeeve’s platform. Our documentation provides an introduction to the key concepts, tools and techniques for building decentralized applications using Corda and the Zeeve platform.
meta:
name: robots content: noindex
Corda¶
Create CLI Access
Navigate to settings and then click on “API Credentials” to see a list of CLI/API credentials.
Click “Create key”.
Provide a name, and select one or more networks to associate with the key.
Add appropriate permissions for the operations that the keys are being created for.
Click “Create key” and then copy/save generated keys.
Login with Zeeve CLI
Login with Zeeve CLI using the earlier created keys and add these urls as well -
zeeve login -i < access-key > -s < secret-key > -ae https://app.zeeve.io/auth/cli/login -ce https://app.zeeve.io/fabric-backend/chaincode/
Deploy
Use the following command to deploy Corda
zeeve corda corda-deploy -f < cordapp tar file> -n < networkID >
description: Learn about Avalanche on Zeeve’s platform. Our documentation provides an introduction to the key concepts, tools and techniques for building decentralized applications using Avalanche and the Zeeve platform.
meta:
name: robots content: noindex
Avalanche Dedicated Node Setup¶
This section will guide you about the different features offered by Zeeve for Avalanche.
Dedicated nodes¶
Create a network¶
This section will provide you with detailed steps for creating a network of Avalanche.
NOTE Please make sure to follow the steps before proceeding.
On the Network Configuration page you will have different cards with different network configurations for Avalanche, which looks similar to the image provided below.
NOTE: These cards can be different in your case. Card configurations depend on your purchased subscription.
You can Choose Managed-AWS (Zeeve’s managed hosting) for the infrastructure of your node or you can use your cloud account (AWS/DO) for the hosting of your node.
Choose the configuration you want. Click on the card and follow the steps accordingly.
Network Info Clicking on the card you will be landed on a page similar to the below image. In this section, we have to provide network-related information for ex- Network Name, Network type, etc.
Name of Network: To uniquely identify your network, this field requires a unique name for it. Unique over here is in terms of the account in which you are creating your network. In case you have created some network earlier, and now you are trying to create with the same name, then the Zeeve platform won’t allow you to create it.
Deployment Type: Deployment type
Type Of Network
MainNet: This will deploy your network on the network mainnet. This is suggested for deploying production-grade avalanche dapps.
TestNet: This will deploy your network on the network testnet. you can use this for your non-production needs like testing or demonstrations.
Workspace: This represents the workspace in which the network will be added after the successful creation.
After providing all the details correctly go to the next step by clicking on the Next Step button.
Node Configuration
In this section, you have to fill in the details of the nodes you want to add to your network.
Username & Password: Choose the username and password of your choice. These will be used as RPC API credentials.
Email: Fill email of yours.
Node Name: To identify your nodes, this field will be used.
Rpc Server: RPC, which stands for “Remote Procedure Call,” is a group of protocols and interfaces that let us talk to the blockchain system. Through the RPC interface, we can ask for information about the blockchain (such as block number, blocks, node connection, etc.) and send a request for a transaction. > * HTTP: Uses individual HTTP requests and responses for each call, similar to a RESTful API. > * ws: WebSocket uses a persistent connection that allows the server to push data to the client.
JSON RPC APIs: JSON RPC API is a bridge that allows dApps to connect to nodes.
After providing the details click on Next step to go to the last step.
Cloud Configuration
This is the step for the configuration of the cloud for your nodes. This step can be different based on your selection of Network configuration cards
Managed - AWS¶
In the case of Managed - AWS, you don’t have to bother about anything, just select the region for the network by clicking on Select Region.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
BYOC - AWS¶
In the case of BYOC - AWS, select the region for the network by clicking on Select Region, select the AWS account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
BYOC - DO¶
In the case of BYOC - DO, select the region for the network by clicking on Select Region, select the Digital Ocean account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the Digital Ocean cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
Click on the Create button. A pop-up window will appear similar to the below image, which ensures the successful creation of your network.
Click on continue and you will be redirected to a page similar to the below image where you can see the nodes listed you’ve just added to the network.
Add node to a network¶
This section will guide you on how you can add a node to a network.
Select the network to which you want to add a node, and click on the network card Ref.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Add Node option. You will get to see a web page similar to that provided below.
Fill in the details for the new node and click on the Next button. In this step, the cloud configuration and region will be prefilled according to the configuration of the network. Click on the Create button and it’s done!
Delete node in a network¶
Select the network, in which you want to perform the delete node action, and click on the network card Ref.. You will get to see similar to the below image.
Click on the delete icon present alongside the node. A pop-up window will open for the confirmation, click on the yes button to confirm.
Delete a network¶
Select the network you want to delete, and click on the network cardRef.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Delete Network option. A confirmation window will open, click on the Yes button, attached to it.
NOTE It can take a few minutes to delete a network.
RPC API endpoints¶
This section talks about different actions you can perform in Avalanche RPC API endpoints.
Create endpoint¶
This section provides a step-by-step guide for creating avalanche RPC API endpoints.
Click on Endpoints on the left side navigation bar and then click on Add Endpoints.
You will be landed on a page similar to the below image.
NOTE It can take be different in your case. These configuration cards depend on your subscription.
Select the configuration and click on the card you want. You will be landed on a page similar to the image provided below. Fill in the required details and click next.
In this step you can check the Require JWT and provide JWT public key details and click on Submit.
Edit endpoint¶
Delete endpoint¶
description: Integrate Binance with Zeeve’s platform using our API and tools. Our documentation provides technical details on authentication, making requests and handling responses for interacting with Binance and the Zeeve platform.
meta:
name: robots content: noindex
Binance Dedicated Node Setup¶
This section will guide you about the different features offered by Zeeve for Binance.
Dedicated nodes¶
Create a network¶
This section will provide you with detailed steps for creating a network of Binance.
NOTE Please make sure to follow the steps mentioned earlier before proceeding.
On the Network Configuration page you will have different cards with different network configurations for Binance, which looks similar to the image provided below.
NOTE: These cards can be different for your case. Card configurations depend on your purchased subscription.
You can Choose Managed-AWS (Zeeve’s managed hosting) for the infrastructure of your node or you can use your cloud account (AWS/DO) for the hosting of your node.
Choose the configuration you want. Click on the card and follow the steps accordingly.
Network Info: Clicking on the card you will be landed on a page similar to the below image. In this section, we have to provide network-related information for ex- Network Name, Network type, etc.
Name of Network: To uniquely identify your network, this field requires a unique name for it. Unique over here is in terms of the account in which you are creating your network. In case you have created some network earlier, and now you are trying to create with the same name, then the Zeeve platform won’t allow you to create it.
Deployment Type: Deployment type
Type Of Network
MainNet: This will deploy your network on the network mainnet. This is suggested for deploying production-grade Binance dapps.
TestNet: This will deploy your network on the network testnet. you can use this for your non-production needs like testing or demonstrations.
Workspace: This represents the workspace in which the network will be added after successful creation.
After providing all the details correctly go to the next step by clicking on the Next Step button.
Node Configuration: In this section, you have to fill in the details of the nodes you want to add to your network.
Username & Password: Choose the username and password of your choice. These will be used as RPC API credentials.
Email: Fill email of yours.
Node Name: To identify your nodes, this field will be used.
Rpc Server: RPC, which stands for “Remote Procedure Call,” is a group of protocols and interfaces that let us talk to the blockchain system. Through the RPC interface, we can ask for information about the blockchain (such as block number, blocks, node connection, etc.) and send a request for a transaction. > * HTTP: Uses individual HTTP requests and responses for each call, similar to a RESTful API. > * ws: WebSocket uses a persistent connection that allows the server to push data to the client.
JSON RPC APIs: JSON RPC API is a bridge that allows dApps to connect to nodes.
After providing the details click on Next step to go to the last step.
Cloud Configuration: This is the step for the configuration of the cloud for your nodes. This step can be different based on your selection of Network configuration cards
Managed - AWS¶
In the case of Managed - AWS, you don’t have to bother about anything, just select the region for the network by clicking on Select Region.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
BYOC - AWS¶
In the case of BYOC - AWS, select the region for the network by clicking on Select Region, select the AWS account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
BYOC - DO¶
In the case of BYOC - DO, select the region for the network by clicking on Select Region, select the Digital Ocean account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
Click on the Create button. A pop-up window will appear similar to the below image, which ensures the successful creation of your network.
Click on continue and you will be redirected to a page similar to the below image where you can see the nodes listed you’ve just added to the network.
Add node to a network¶
This section will guide you on how you can add a node to a network.
Select the network to which you want to add a node, and click on the network card Ref.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Add Node option. You will get to see a web page similar to that provided below.
Fill in the details for the new node and click on the Next button. In this step, the cloud configuration and region will be prefilled according to the configuration of the network. Click on the Create button and it’s done!
Delete node in a network¶
Select the network, in which you want to perform the delete node action, and click on the network card Ref.. You will get to see similar to the below image.
Click on the delete icon present alongside the node. A pop-up window will open for the confirmation, click on the yes button to confirm.
Delete a network¶
Select the network you want to delete, and click on the network cardRef.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Delete Network option. A confirmation window will open, click on the Yes button, attached to it.
NOTE It can take a few minutes to delete a network.
Api endpoints¶
description: Integrate Coreum with Zeeve’s platform using our API and tools. Our documentation provides technical details on authentication, making requests and handling responses for interacting with Coreum and the Zeeve platform.¶
Coreum Node Setup¶
This section will guide you about the different features offered by Zeeve for Coreum.
Dedicated nodes¶
Create a network¶
This section will provide you with detailed steps for creating a network of Coreum.
NOTE Please make sure to follow the steps mentioned earlier before proceeding.
On the Network Configuration page you will have different cards with different network configurations for Coreum, which looks similar to the image provided below.
NOTE: These cards can be different for your case. Card configurations depend on your purchased subscription.
You can Choose Zeeve-Managed-Cloud (Zeeve’s managed hosting) for the infrastructure of your node or you can use your cloud account (AWS/DO) for the hosting of your node.
Choose the configuration you want. Click on the card and follow the steps accordingly.
Network Info: Clicking on the card you will be landed on a page similar to the below image. In this section, we have to provide network-related information for ex- Network Name, Network type, etc.
Name of Network: To uniquely identify your network, this field requires a unique name for it. Unique over here is in terms of the account in which you are creating your network. In case you have created some network earlier, and now you are trying to create with the same name, then the Zeeve platform won’t allow you to create it.
Deployment Type: Deployment type
Type Of Network
TestNet: This will deploy your network on the network testnet. you can use this for your non-production needs like testing or demonstrations.
Workspace: This represents the workspace in which the network will be added after successful creation.
After providing all the details correctly go to the next step by clicking on the Next Step button.
Node Configuration: In this section, you have to fill in the details of the nodes you want to add to your network.
Username & Password: Choose the username and password of your choice. These will be used as RPC API credentials.
Node Name: To identify your nodes, this field will be used.
MonikerId: A unique ID is required.
Rpc Server: RPC, which stands for “Remote Procedure Call,” is a group of protocols and interfaces that let us talk to the blockchain system. Through the RPC interface, we can ask for information about the blockchain (such as block number, blocks, node connection, etc.) and send a request for a transaction. > * HTTP: Uses individual HTTP requests and responses for each call, similar to a RESTful API. > * ws: WebSocket uses a persistent connection that allows the server to push data to the client.
After providing the details click on Next step to go to the last step.
Cloud Configuration: This is the step for the configuration of the cloud for your nodes. This step can be different based on your selection of Network configuration cards
Zeeve Managed¶
In the case of Zeeve Managed, you don’t have to bother about anything, just select the region for the network by clicking on Select Region.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted.
BYOC - AWS¶
In the case of BYOC - AWS, select the region for the network by clicking on Select Region, select the AWS account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
BYOC - DO¶
In the case of BYOC - DO, select the region for the network by clicking on Select Region, select the Digital Ocean account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of DigitalOcean, each of its regions has multiple, isolated locations known as Availability Zones. Digitial Ocean provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across it’s Regions unless you do so specifically. Ref.
Cloud Account: It represents the DO cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
Click on the Create button. A pop-up window will appear similar to the below image, which ensures the successful creation of your network.
Click on continue and you will be redirected to a page similar to the below image where you can see the nodes listed you’ve just added to the network.
Add node to a network¶
This section will guide you on how you can add a node to a network.
Select the network to which you want to add a node, and click on the network card Ref.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Add Node option. You will get to see a web page similar to that provided below.
Fill in the details for the new node and click on the Next button. In this step, the cloud configuration and region will be prefilled according to the configuration of the network. Click on the Create button and it’s done!
Delete node in a network¶
Select the network, in which you want to perform the delete node action, and click on the network card Ref.. You will get to see similar to the below image.
Click on the delete icon present alongside the node. A pop-up window will open for the confirmation, click on the yes button to confirm.
Delete a network¶
Select the network you want to delete, and click on the network cardRef.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Delete Network option. A confirmation window will open, click on the Yes button, attached to it.
NOTE It can take a few minutes to delete a network.
Staking nodes¶
NOTE Purchase a subscription before proceeding.
Create a network¶
This section will provide you detailed steps for creating a network of Coreum.
On the Network Configuration page you will be able to see different configuration cards for Coreum, which looks similar to the image provided below.
NOTE: These cards can be different for your case. Card configurations depend on your purchased subscription.
You can Choose Zeeve-Managed-Cloud (Zeeve’s managed hosting) for the infrastructure of your node or you can use your cloud account (AWS/DO) for the hosting of your node.
Choose the configuration you want. Click on the card and follow the steps accordingly.
Network Info: Clicking on the card you will be landed on a page similar to the below image. In this section, we have to provide network-related information for ex- Network Name, Network type, etc.
Name of Network: To uniquely identify your network, this field requires a unique name for it. Unique over here is in terms of the account in which you are creating your network. In case you have created some network earlier, and now you are trying to create with the same name, then the Zeeve platform won’t allow you to create it.
Deployment Type: Deployment type
Type Of Network
TestNet: This will deploy your network on the network testnet. you can use this for your non-production needs like testing or demonstrations.
Workspace: This represents the workspace in which the network will be added after successful creation.
After providing all the details correctly go to the next step by clicking on the Next Step button.
Node Configuration: In this section, you have to fill in the details of the nodes you want to add to your network.
Node Name: To identify your nodes, this field will be used.
Node MonikerId: A custom human readable name for this node.
Account MonikerId: Account id.
Validator Name: The name which is visible on the Coreum Explorer.
Mnemonic Key: bip39 mnemonic passphrase of your wallet.
Key Ring: A passprase to access your private key.
Email: Email will be used as a secret identity.
Delegation Amount: Amount which you want to delegate/stake.
Minimum Delegation Amount: The minimum delegation amount and must be grater or equal min_self_delegation.
Commission Rate: The initial commission rate percentage.
Commission Max. Rate: The maximum commission rate percentage.
Commission Max. Change Rate: The maximum commission change rate percentage (per day).
Website: Website you want to be reflected in the.
Validator Identity: The optional identity signature (ex. UPort or Keybase).
State Sync: By enabling state sync your node will download data related to the head or near the head of the chain and verify the data. This leads to drastically shorter times for joining a network Read more.
Username & Password: Choose the username and password of your choice. These will be used as RPC API credentials.
Rpc Server: RPC, which stands for “Remote Procedure Call,” is a group of protocols and interfaces that let us talk to the blockchain system. Through the RPC interface, we can ask for information about the blockchain (such as block number, blocks, node connection, etc.) and send a request for a transaction. > * HTTP: Uses individual HTTP requests and responses for each call, similar to a RESTful API. > * ws: WebSocket uses a persistent connection that allows the server to push data to the client.
After providing the details click on Next step to go to the last step.
Cloud Configuration: This is the step for the configuration of the cloud for your nodes. This step can be different based on your selection of Network configuration cards
Zeeve Managed¶
In the case of Zeeve Managed, you don’t have to bother about anything, just select the region for the network by clicking on Select Region.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted.
BYOC - AWS¶
In the case of BYOC - AWS, select the region for the network by clicking on Select Region, select the AWS account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
BYOC - DO¶
In the case of BYOC - DO, select the region for the network by clicking on Select Region, select the Digital Ocean account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of DigitalOcean, each of its regions has multiple, isolated locations known as Availability Zones. Digitial Ocean provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across it’s Regions unless you do so specifically. Ref.
Cloud Account: It represents the DO cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
Click on the Create button. A pop-up window will appear similar to the below image, which ensures the successful creation of your network.
Click on continue and you will be redirected to a page similar to the below image where you can see the nodes listed you’ve just added to the network.
Update Validator Details¶
Find the Edit button on top right of the screen and click on it to edit and update the prefered validator detail. You will get to see similar to the below image.
Step 01 :
Validator Name
Commission Rate
Email
Validator Identity
Step 02 :
Keyring is require in order to update the validator details.
Ubound tokens¶
Click on the Actions button on the top right, and select the Unbound Token option.
Enter the amount you want to unbound and the keyring, then click on Unbound button.
Withdraw rewards¶
Click on the Actions button on the top right, and select the Withdraw reward option.
Enter the keyring then click on Withdraw button.
Set rewards to a different wallet¶
Click on the Actions button on the top right, and select the Set rewards to a different wallet option.
Enter the wallet address and keyring then click on Set button.
Delete a network¶
Select the network you want to delete, and click on the network card. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Delete Network option. A confirmation window will open, click on the Yes button, attached to it.
NOTE It can take a few minutes to delete a network.
description: Use Dcomm with Zeeve’s platform through our API and tools. Our documentation provides technical details on authentication, making requests and handling responses for interacting with Dcomm and the Zeeve platform.
meta:
name: robots content: noindex
Dcomm Staking Node Setup¶
NOTE Purchase a subscription before proceeding.
Create a network¶
This section will provide you detailed steps for creating a network of Dcomm.
On the Network Configuration page you will be able to see different configuration cards for Dcomm, which looks similar to the image provided below.
*NOTE: These configuration cards can be different based on your purchased subscriptions.*
You can Choose Zeeve Managed Cloud or you can use your cloud account (AWS/DO) for the infrastructure of your node.
Choose the card with the configuration you want. Clicking on the card you will be redirected to the network setup page.
Network Info
Network Name: A name to identify your network.
Deployment Type: Deployment type
Network Type
Melbourne Testnet: This will deploy your network on the network testnet. you can use this for your non-production needs like testing or demonstrations.
Workspace: This represents the workspace in which the network will be added after the successful creation.
Proceed further by clicking on the Next Step button after providing all the details.
Cloud Configuration
This step configures the cloud settings for your node. This step can vary based on your selection of Network configuration card
Zeeve Managed Cloud¶
In the case of Managed - Cloud, select the region for the network under Select Region and provide a name to your node.
Node Name: A name to identify your node, this field requires a unique name. Unique means that it should be unique in a network to which you are adding a node.
Region: It indicates the region of the cloud service. These regions are the geographic locations where your network instances are going to be hosted.
For better understanding of which region is best for you please refer the following
New York City, The US: NYC1, NYC3
San Francisco, The US: SFO2
Toronto, Canada: TOR1
London, United Kingdom: LON1
Frankfurt, Germany: FRA1
Amsterdam, the Netherlands: AMS3
Bangalore, India: BLR1
Bring Your Own Cloud¶
In the case of BYOC (AWS or Digital Ocean), select the region for the network by clicking on Select Region, select the Cloud account you want to use by clicking on Select Cloud Account, choose the instance type as your requirement by clicking on Select Instance Type and provide a name to your node.
Node Name: A name to identify your node, this field requires a unique name. Unique means that it should be unique in a network to which you are adding a node.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted.
Cloud Account: It represents the cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
On clicking the Create button a pop-up window will open which ensures the successful creation of your network.
On clicking the Continue button you will be redirected to the page where you can see the network you created.
Add additional node to a network¶
This section will guide you on how you can add an additional node to a network. As you have already created a network, follow these steps to add more nodes to the network.
Visit the network detail page. Click on the Actions button on the top right, and select the Add Node option.
You will be redirected to the node setup page. Fill the name for the new node, network type and deployment type will be prefilled based on the network configuration. Click on the Next button to continue.
Select the instance type for the node, cloud account and region will be prefilled based on the network configuration. Click on the Create button and the node will be added.
NOTE For Zeeve Managed Cloud, the option for selecting the instance type will not be available as it will be selected by Zeeve.
Delete node in a network¶
Select the network, in which you want to perform the delete node action, and click on the network card Ref.. You will get to see a page similar to the below image.
Click on the delete icon present alongside the node. A pop-up window will open for the confirmation, click on the Yes button to confirm.
Delete a network¶
Visit the network detail pageRef.. Click on the Actions button on the top right, and select the Delete Network option.
A confirmation window will open, click on the Yes button to delete the network.
NOTE It will take a few minutes to delete a network.
Supported API methods¶
Just like any other protocol, Dcomm supports JSON RPC API call, which can be called to retrive the the information. Dcomm supports both HTTP as well as WS(WebSocket) JSON RPC methods.
HTTP¶
ACT-Chain URL -
https://node_url/ext/bc/ACT/rpc.AST-Chain URL -
https://node_url/ext/bc/AST.ATH-Chain URL -
https://node_url/ext/bc/ATH.
Example¶
import axios from "axios";
const data = JSON.stringify({
"jsonrpc": "2.0",
"id": 1,
"method": "eth_blockNumber",
"params": []
});
const config = {
method: 'post',
url: 'https://node_url/ext/bc/ACT/rpc',
headers: {
'Content-Type': 'application/json'
},
data : data
};
axios(config)
.then(function (response) {
console.log(JSON.stringify(response.data));
})
.catch(function (error) {
console.log(error);
});
Available HTTP methods¶
⚙️ dvm.buildGenesis
Given a JSON representation of this Virtual Machine’s genesis state, create the byte representation of that state.
Example: Nodejs
⚙️ dvm.getAddressTxs
Returns all transactions that change the balance of the given address. A transaction is said to change an address's balance if either is true: A UTXO that the transaction consumes was at least partially owned by the address. A UTXO that the transaction produces is at least partially owned by the address. Note: Indexing (index-transactions) must be enabled in the ACT-chain config.
Example: Nodejs
⚙️ dvm.getAllBalances
Get the balances of all assets controlled by a given address.
Example: Nodejs
⚙️ dvm.getAssetDescription
Get information about an asset.
Example: Nodejs
⚙️ dvm.getBalance
Get the balance of an asset controlled by a given address.
Example: Nodejs
⚙️ dvm.getTx
Returns the specified transaction.
Example: Nodejs
⚙️ dvm.getTxStatus
Get the status of a transaction sent to the network.
Example: Nodejs
⚙️ dvm.getUTXOs
Get the UTXOs that reference a given address.
Example: Nodejs
⚙️ health.health
Get health check on this node.
Example: Nodejs
⚙️ eth_baseFee
Get the base fee for the next block.
Example: Nodejs
⚙️ eth_blockNumber
Getting the most recent block number.
Example: Nodejs
⚙️ eth_call
Call a contract.
Example: Nodejs
⚙️ eth_chainId
Not well documented in JSON-RPC references. See instead EIP694.
Example: Nodejs
⚙️ eth_getAssetBalance
Getting an account’s non-DCM balance.
Example: Nodejs
⚙️ eth_getBalance
Getting an account’s balance.
Example: Nodejs
⚙️ eth_maxPriorityFeePerGas
Getting an account’s balance.
Example: Nodejs
⚙️ eth_getTransactionCount
Getting an account’s nonce.
Example: Nodejs
⚙️ eth_sendRawTransaction
Send a raw transaction.
Example: Nodejs
⚙️ eth_getBlockByHash
Getting a block by hash.
Example: Nodejs
⚙️ eth_getBlockByNumber
Getting a block by number.
Example: Nodejs
⚙️ eth_getTransactionByHash
Getting a transaction by hash.
Example: Nodejs
⚙️ eth_getTransactionReceipt
Getting a transaction receipt.
Example: Nodejs
⚙️ dcm.getAtomicTx
Returns the specified transaction.
Example: Nodejs
⚙️ dcm.getAtomicTxStatus
Get the status of a transaction sent to the network.
Example: Nodejs
⚙️ dcm.getUTXOs
Get the UTXOs that reference a given address.
Example: Nodejs
⚙️ net_version
Getting the network ID.
Example: Nodejs
⚙️ web3_clientVersion
Getting the current client version.
Example: Nodejs
⚙️ web3_sha3
Calculate a cryptographic hash.
Example: Nodejs
⚙️ index.getLastAccepted (AST Transactions)
Get the most recently accepted container.
Example: Nodejs
⚙️ index.getContainerByIndex (AST Transactions)
Get container by index. The first container accepted is at index 0, the second is at index 1, etc.
Example: Nodejs
⚙️ index.getContainerByID (AST Transactions)
Get container by ID.
Example: Nodejs
⚙️ index.getContainerRange (AST Transactions)
Returns containers with indices in [startIndex, startIndex+1, ... , startIndex + numToFetch - 1]. numToFetch must be in [0,1024].
Example: Nodejs
⚙️ index.getIndex (AST Transactions)
Get a container's index.
Example: Nodejs
⚙️ index.isAccepted (AST Transactions)
Returns true if the container is in this index.
Example: Nodejs
⚙️ index.getLastAccepted (AST Vertices)
Get the most recently accepted container.
Example: Nodejs
⚙️ index.getContainerByIndex (AST Vertices)
Get container by index. The first container accepted is at index 0, the second is at index 1, etc.
Example: Nodejs
⚙️ index.getContainerByID (AST Vertices)
Get container by ID.
Example: Nodejs
⚙️ index.getContainerRange (AST Vertices)
Returns containers with indices in [startIndex, startIndex+1, ... , startIndex + numToFetch - 1]. numToFetch must be in [0,1024].
Example: Nodejs
⚙️ index.getIndex (AST Vertices)
Get a container's index.
Example: Nodejs
⚙️ index.isAccepted (AST Vertices)
Returns true if the container is in this index.
Example: Nodejs
⚙️ index.getLastAccepted (ATH Blocks)
Get the most recently accepted container.
Example: Nodejs
⚙️ index.getContainerByIndex (ATH Blocks)
Get container by index. The first container accepted is at index 0, the second is at index 1, etc.
Example: Nodejs
⚙️ index.getContainerByID (ATH Blocks)
Get container by ID.
Example: Nodejs
⚙️ index.getContainerRange (ATH Blocks)
Returns containers with indices in [startIndex, startIndex+1, ... , startIndex + numToFetch - 1]. numToFetch must be in [0,1024].
Example: Nodejs
⚙️ index.getIndex (ACT Blocks)
Get a container's index.
Example: Nodejs
⚙️ index.isAccepted (ACT Blocks)
Returns true if the container is in this index.
Example: Nodejs
⚙️ index.getLastAccepted (ACT Blocks)
Get the most recently accepted container.
Example: Nodejs
⚙️ index.getContainerByIndex (ACT Blocks)
Get container by index. The first container accepted is at index 0, the second is at index 1, etc.
Example: Nodejs
⚙️ index.getContainerByID (ACT Blocks)
Get container by ID.
Example: Nodejs
⚙️ index.getContainerRange (ACT Blocks)
Returns containers with indices in [startIndex, startIndex+1, ... , startIndex + numToFetch - 1]. numToFetch must be in [0,1024].
Example: Nodejs
⚙️ index.getIndex (ATH Blocks)
Get a container's index.
Example: Nodejs
⚙️ index.isAccepted (ATH Blocks)
Returns true if the container is in this index.
Example: Nodejs
⚙️ info.getBlockchainID
Given a blockchain’s alias, get its ID.
Example: Nodejs
⚙️ info.getNetworkID
Get the ID of the network this node is participating in.
Example: Nodejs
⚙️ info.getNetworkName
Get the name of the network this node is participating in.
Example: Nodejs
⚙️ info.getNodeID
Get the id of the node is participating in.
Example: Nodejs
⚙️ info.getNodeIP
Get the IP of this node.
Example: Nodejs
⚙️ info.getNodeVersion
Get the version of this node.
Example: Nodejs
⚙️ info.isBootstrapped
Check whether a given chain is done bootstrapping.
Example: Nodejs
⚙️ info.getTxFee
Get the transaction fee of the network.
Example: Nodejs
⚙️ info.getVMs
Get the virtual machines installed on this node.
Example: Nodejs
⚙️ info.uptime
Returns the network's observed uptime of this node.
Example: Nodejs
⚙️ info.peers
Get description of peer connections.
Example: Nodejs
⚙️ authority.getBalance
Get the balance of an asset controlled by a given address.
Example: Nodejs
⚙️ authority.getBlockchains
Get all the blockchains that exist (excluding the ATH-Chain).
Example: Nodejs
⚙️ authority.getBlockchainStatus
Get the status of a blockchain.
Example: Nodejs
⚙️ authority.getCurrentSupply
Returns an upper bound on the number of DCM that exist. This is an upper bound because it does not account for burnt tokens, including transaction fees.
Example: Nodejs
⚙️ authority.getTotalStake
Get the total amount of nDCM staked on the Primary Network.
Example: Nodejs
⚙️ authority.getCurrentValidators
List the current validators of the given Subnet.
Example: Nodejs
⚙️ authority.getMaxStakeAmount
List the current validators of the given Subnet.
Example: Nodejs
⚙️ authority.getHeight
Returns the height of the last accepted block.
Example: Nodejs
⚙️ authority.getMinStake
Returns the minimum stake amount.
Example: Nodejs
⚙️ authority.getRewardUTXOs
Returns the UTXOs that were rewarded after the provided transaction's staking or delegation period ended.
Example: Nodejs
⚙️ authority.getStake
Returns the staked amount for an array of addresses.
Example: Nodejs
⚙️ authority.getTxStatus
Returns the status of a authority chain transaction.
Example: Nodejs
⚙️ authority.getPendingValidators
List the validators in the pending validator set of the specified Subnet. Each validator is not currently validating the Subnet but will in the future.
Example: Nodejs
⚙️ authority.getStakingAssetID
Retrieve an assetID for a subnet’s staking asset. Currently this always returns the Primary Network’s staking assetID.
Example: Nodejs
⚙️ authority.getSubnets
Get all the Subnets that exist.
Example: Nodejs
⚙️ authority.getTx
Returns the specified transaction.
Example: Nodejs
⚙️ authority.getTimestamp
Returns the specified transaction.
Example: Nodejs
⚙️ authority.getUTXOs
Get the UTXOs that reference a given address.
Example: Nodejs
⚙️ authority.getValidatorsAt
Get the validators and their weights of a subnet or the Primary Network at a given ATH-Chain height.
Example: Nodejs
⚙️ authority.sampleValidators
Sample validators from the specified Subnet.
Example: Nodejs
⚙️ authority.validatedBy
Get the Subnet that validates a given blockchain.
Example: Nodejs
⚙️ authority.validates
Get the IDs of the blockchains a Subnet validates.
Example: Nodejs
WebSocket¶
ACT-Chain URL -
wss://node_url/ext/bc/ACT/ws.
*NOTE: As of now only Action Chain supports WS RPC methods.
Example¶
import WebSocket from 'ws';
const ws = new WebSocket('wss://node_url/ext/bc/ACT/ws');
ws.on('open', function open() {
console.log('connected');
// NOTE : use delay to avoid missing messages from server
setTimeout(() => {
const msg = {"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1};
ws.send(JSON.stringify(msg));
}, 1000);
});
ws.on('message', function message(data) {
console.log('received: %s', data);
});
Available WebSocket Methods¶
⚙️ eth_baseFee
Get the base fee for the next block.
⚙️ eth_blockNumber
Getting the most recent block number.
⚙️ eth_call
Call a contract.
⚙️ eth_chainId
Not well documented in JSON-RPC references. See instead EIP694.
⚙️ eth_getAssetBalance
Getting an account’s non-DCM balance.
⚙️ eth_getBalance
Getting an account’s balance.
⚙️ eth_maxPriorityFeePerGas
Getting an account’s balance.
⚙️ eth_getTransactionCount
Getting an account’s nonce.
⚙️ eth_sendRawTransaction
Send a raw transaction.
⚙️ eth_getBlockByHash
Getting a block by hash.
⚙️ eth_getBlockByNumber
Getting a block by number.
⚙️ eth_getTransactionByHash
Getting a transaction by hash.
⚙️ eth_getTransactionReceipt
Getting a transaction receipt.
⚙️ dcm.getAtomicTx
Returns the specified transaction.
⚙️ dcm.getAtomicTxStatus
Get the status of a transaction sent to the network.
⚙️ dcm.getUTXOs
Get the UTXOs that reference a given address.
⚙️ net_version
Getting the network ID.
⚙️ web3_clientVersion
Getting the current client version.
⚙️ web3_sha3
Calculate a cryptographic hash.
description: Use EWC with Zeeve’s platform through our API and tools. Our documentation provides technical details on authentication, making requests and handling responses for interacting with EWC and the Zeeve platform.¶
EWC Validator Node Setup¶
NOTE Purchase a subscription before proceeding.
Create a network¶
This section will provide you detailed steps for creating a network of EWC.
On the Network Configuration page you will be able to see different configuration cards for EWC, which looks similar to the image provided below.
*NOTE: These configuration cards can be different based on your purchased subscriptions.*
You can Choose Zeeve Managed Cloud or you can use your cloud account (AWS/DO/GCP/Tencent Cloud) for the infrastructure of your node.
Choose the card with the configuration you want. Clicking on the card you will be redirected to the network setup page.
Network Info
Network Name: A name to identify your network.
Deployment Type: Deployment type
Network Type
Energy Web: This will deploy your network on the network mainnet. This is suggested for deploying production-grade EWC dapps.
Volta: This will deploy your network on the network testnet. you can use this for your non-production needs like testing or demonstrations.
Workspace: This represents the workspace in which the network will be added after the successful creation.
Proceed further by clicking on the Next Step button after providing all the details.
Cloud Configuration
This step configures the cloud settings for your node. This step can vary based on your selection of Network configuration card
Zeeve Managed Cloud¶
In the case of Managed - Cloud, select the region for the network under Select Region and provide a name to your node.
Company/Node Name: This is the name given to the validator node.
Region: It indicates the region of the cloud service. These regions are the geographic locations where your network instances are going to be hosted.
Bring Your Own Cloud¶
In the case of BYOC (AWS/Digital Ocean/GCP/Tencent Cloud), select the region for the network by clicking on Select Region, select the Cloud account you want to use by clicking on Select Cloud Account, choose the instance type as your requirement by clicking on Select Instance Type and provide a name to your node.
Company/Node Name: This is the name given to the validator node.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted.
Cloud Account: It represents the cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
On clicking the Create button a pop-up window will open which ensures the successful creation of your network.
On clicking the Continue button you will be redirected to the page where you can see the network you created.
NOTE To become an EWF (Volta/EWC) validator, please proceed with the multi-sig process.
Withdrawal and Address Change¶
Amount Withdraw¶
In the case you want to withdraw amount, click on the withdraw button in the Node Address Details panel.
On clicking the Withdraw button a pop-up window will open.
Address: Enter the address where you want to withdraw the amount.
Amount: Enter the amount you want to withdraw. The amount should be more than 0.0015.
On clicking the Submit button to make the transaction. The amount withrawal will take few minutes to complete the transaction.
Address Change¶
In the case you want to change Address, click on the Change Payout Address button in the Payout Address Details panel.
On clicking the Change Payout Address button a pop-up window will open.
Address: Enter the new payout address.
On clicking the Submit button the Payout Address will be changed.
Download Installation Summary¶
To Download Installation Summary. Go to the detail page and click on the Download installation summary button.
On clicking the Download installation summary button, a PDF will be downloaded with the EWF Node Install information.
Node Name.
Validator Address.
Enode.
IP Address.
This information will be displayed in a format similar to the below image
NOTE Download option will be available when a node is In the Active stage.
View Transaction¶
To view all the transaction. Click on the Actions button on the top right, and select the View Transaction option.
On clicking the View Transaction button a pop-up window will open.
View On Explorer¶
To view all Address details on the EWC Explorer. Click on the Actions button on the top right, and select the View On Explorer option.
On clicking the View On Explorer button a new tab will open.
Analytics¶
To view network analytics and monitoring details, click on the View Analytics in the Infrastructure Details panel.
On clicking the View Analytics hyperlink, four button will be displayed.
System metrics
Blockchain metrics
Logs
Alerts
Alerts Section¶
You will see Alerts sections at the bottom of the page. Here you can see the list of Alerts related to you EWC network.
Delete a network¶
Visit the network detail page. Click on the Actions button on the top right, and select the Delete Network option.
A confirmation window will open, click on the Yes button to delete the network.
NOTE It will take a few minutes to delete a network.
description: Build decentralized applications using Fantom and Zeeve’s platform. Our documentation provides technical details on authentication, making requests and handling responses for interacting with Fantom and the Zeeve platform.
meta:
name: robots content: noindex
Fantom Dedicated Node Setup¶
This section will guide you about different actions you can perform for Fantom
Dedicated nodes¶
Create a network¶
This section will provide you with detailed steps for creating a network of Fantom.
NOTE Please make sure to follow the steps mentioned earlier before proceeding.
On the Network Configuration page you will have different cards with different network configurations for Fantom, which looks similar to the image provided below.
NOTE: These cards can be different for your case. Card configurations depend on your purchased subscription.
You can Choose Managed-AWS (Zeeve’s managed hosting) for the infrastructure of your node or you can use your cloud account (AWS/DO) for the hosting of your node.
Choose the configuration you want. Click on the card and follow the steps accordingly.
Network Info Clicking on the card you will be landed on a page similar to the below image. In this section, we have to provide network-related information for ex- Network Name, Network type, etc.
Name of Network: To uniquely identify your network, this field requires a unique name for it. Unique over here is in terms of the account in which you are creating your network. In case you have created some network earlier, and now you are trying to create with the same name, then the Zeeve platform won’t allow you to create it.
Deployment Type: This defines the deployment type.
Type Of Network
MainNet: This will deploy your network on the network mainnet. This is suggested for deploying production-grade Fantom dapps.
Testnet: This is a testnet you can use for your non-production needs like testing or demonstrations.
Workspace:
After providing all the details correctly go to the next step by clicking on the Next Step button.
Node Configuration
In this section, you have to fill in the details of the nodes you want to add to your network.
Username & Password: Choose the username and password of your choice. These will be used as RPC API credentials.
Email: Fill email of yours.
Node Name In order to identify your nodes, this field will be used.
Rpc Server: RPC, which stands for “Remote Procedure Call,” is a group of protocols and interfaces that let us talk to the blockchain system. Through the RPC interface, we can ask for information about the blockchain (such as block number, blocks, node connection, etc.) and send a request for a transaction. > * HTTP: Uses individual HTTP requests and responses for each call, similar to a RESTful API. > * ws: WebSocket uses a persistent connection that allows the server to push data to the client.
JSON RPC APIs: JSON RPC API is a bridge that allows dApps to connect to nodes.
After providing the details click on Next step to go to the last step.
Cloud Configuration
This is the step for the configuration of the cloud for your nodes. This step can be different based on your selection of Network configuration cards
Managed - AWS¶
In the case of Managed - AWS, you don’t have to bother about anything, just select the region for the network by clicking on Select Region.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
BYOC - AWS¶
In the case of BYOC - AWS, select the region for the network by clicking on Select Region, select the AWS account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
BYOC - DO¶
In the case of BYOC - DO, select the region for the network by clicking on Select Region, select the Digital Ocean account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
Click on the Create button. A pop-up window will appear similar to the below image, which ensures the successful creation of your network.
Click on continue and you will be redirected to a page similar to the below image where you can see the nodes listed you’ve just added to the network.
Add node to a network¶
This section will guide you on how you can add a node to a network.
Select the network to which you want to add a node, and click on the network card Ref.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Add Node option. You will get to see a web page similar to that provided below.
Fill in the details for the new node and click on the Next button. In this step, the cloud configuration and region will be prefilled according to the configuration of the network. Click on the Create button and it’s done!
Delete node in a network¶
Select the network, in which you want to perform delete a node, and click on the network card Ref.. You will get to see similar to the below image.
Click on the delete icon present alongside the node. A pop-up window will open for the confirmation, click on the yes button to confirm.
Delete a network¶
Select the network you want to delete, and click on the network cardRef.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Delete Network option. A confirmation window will open, click on the Yes button, attached to it.
NOTE It can take a few minutes to delete a network.
description: Integrate Polygon with Zeeve’s platform using our API and tools. Our documentation provides technical details on authentication, making requests and handling responses for interacting with Polygon and the Zeeve platform.
meta:
name: robots content: noindex
Polygon Dedicated Node Setup¶
This section will guide you about different actions you can perform for Polygon
Dedicated nodes¶
Create a network¶
This section will provide you with detailed steps for creating a network of Polygon.
NOTE Please make sure to follow the steps mentioned earlier before proceeding.
On the Network Configuration page you will have different cards with different network configurations for Polygon, which looks similar to the image provided below.
NOTE: These cards can be different for your case. Card configurations totally depend on your purchased subscription.
You can Choose Managed-AWS (Zeeve’s managed hosting) for the infrastructure of your node or you can use your own cloud account (AWS/DO) for hosting your node.
Choose the configuration you want. Click on the card and follow the steps accordingly.
Network Info Clicking on the card you will be landed on a page similar to the below image. In this section, we have to provide network-related information for ex- Network Name, Network type, etc.
Name of Network: In order to uniquely identify your network, this field requires a unique name for it. Unique over here is in terms of the account in which you are creating your network. In case you have created some network earlier, and now you are trying to create with the same name, then the Zeeve platform won’t allow you to create it.
Deployment Type: Deployment type
Type Of Network
MainNet: This will deploy your network on the network mainnet. This is suggested for deploying production-grade Polygon dapps.
TestNet: This will deploy your network on the network testnet. you can use this for your non-production needs like testing or demonstrations.
Workspace: This represents the workspace in which the network will be added after successful creation.
After providing all the details correctly go to the next step by clicking on the Next Step button.
Node Configuration
In this section, you have to fill in the details of the nodes you want to add to your network.
Username & Password: Choose the username and password of your choice. These will be used as RPC API credentials.
Email: Fill email of yours.
Node Name: In order to identify your nodes, this field will be used.
Rpc Server: RPC, which stands for “Remote Procedure Call,” is a group of protocols and interfaces that let us talk to the blockchain system. Through the RPC interface, we can ask for information about the blockchain (such as block number, blocks, node connection, etc.) and send a request for a transaction. > * HTTP: Uses individual HTTP requests and responses for each call, similar to a RESTful API. > * ws: WebSocket uses a persistent connection that allows the server to push data to the client.
JSON RPC APIs: JSON RPC API is a bridge that allows dApps to connect to nodes.
After providing the details click on Next step to go to the last step.
Cloud Configuration
This is the step for the configuration of the cloud for your nodes. This step can be different based on your selection of Network configuration cards
Managed - AWS¶
In the case of Managed - AWS, you don’t have to bother about anything, just select the region for the network by clicking on Select Region.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
BYOC - AWS¶
In the case of BYOC - AWS, select the region for the network by clicking on Select Region, select the AWS account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
BYOC - DO¶
In the case of BYOC - DO, select the region for the network by clicking on Select Region, select the Digital Ocean account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple, isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
Click on the Create button. A pop-up window will appear similar to the below image, which ensures the successful creation of your network.
Click on continue and you will be redirected to a page similar to the below image where you can see the nodes listed you’ve just added to the network.
Add node to a network¶
This section will guide you on how you can add a node to a network.
Select the network to which you want to add a node, and click on the network card Ref.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Add Node option. You will get to see a web page similar to that provided below.
Fill in the details for the new node and click on the Next button. In this step, the cloud configuration and region will be prefilled according to the configuration of the network. Click on the Create button and it’s done!
Delete node in a network¶
Select the network, you want to perform the deleted node to, and click on the network card Ref.. You will get to see similar to the below image.
Click on the delete icon present alongside the node. A pop-up window will open for the confirmation, click on the yes button to confirm.
Delete a network¶
Select the network you want to delete, and click on the network cardRef.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Delete Network option. A confirmation window will open, click on the Yes button, attached to it.
NOTE It can take a few minutes to delete a network.
meta:
name: robots content: noindex
Tron Dedicated Node Setup¶
This section will guide you about different actions you can perform for Tron.
Dedicated nodes¶
Create a network¶
This section will provide detailed steps for creating a network of Tron.
NOTE Please make sure to follow the steps mentioned earlier before proceeding.
On the Network Configuration page, you will have different cards with different network configurations for Tron, which looks similar to the image provided below.
NOTE: These cards can be different for your case. Card configurations totally depend on your purchased subscription.
You can choose Managed (Zeeve’s managed hosting) for the infrastructure of your node, or you can use your own cloud account (AWS/DO/GCP/Tencent) for hosting your node.
Choose the configuration you want. Click on the card and follow the steps accordingly.
Network Info
Clicking on the card, you will be landed on a page similar to the below image. In this section, we have to provide network-related information, ex- Network Name, Network type, etc.
Name of Network: In order to uniquely identify your network, this field requires a unique name for it. Unique over here is in terms of the account in which you are creating your network. In case you have created some network earlier, and now you are trying to create one with the same name, then the Zeeve platform won’t allow you to create it.
Deployment Type: Deployment type
Type Of Network
MainNet: This will deploy your network on the network mainnet. This is suggested for deploying production-grade Tron dapps.
TestNet: This will deploy your network on the network testnet. you can use this for your non-production needs like testing or demonstrations.
Workspace: This represents the workspace in which the network will be added after successful creation.
After providing all the details correctly, go to the next step by clicking on the Next Step button.
Node Configuration
In this section, you have to fill in the details of the nodes you want to add to your network.
Username & Password: Choose the username and password of your choice. These will be used as RPC API credentials.
Node Name: In order to identify your nodes, this field will be used.
RPC Server: RPC, which stands for “Remote Procedure Call,” is a group of protocols and interfaces that let us talk to the blockchain system. Through the RPC interface, we can ask for information about the blockchain (such as block number, blocks, node connection, etc.) and send a request for a transaction. > * HTTP: Uses individual HTTP requests and responses for each call, similar to a RESTful API. > * ws: WebSocket uses a persistent connection that allows the server to push data to the client.
JSON RPC APIs: JSON RPC API is a bridge that allows dApps to connect to nodes.
After providing the details, click on Next step to go to the last step.
Cloud Configuration
This is the step for the configuration of the cloud for your nodes. This step can be different based on your selection of Network configuration cards
Managed¶
In the case of Managed, you don’t have to bother about anything; just select the region for the network by clicking on Select Region.
Region: In managed, you just need to select the region depending on your case and major area of operations to reduce the latency as much as possible. Ref.
BYOC - AWS¶
In the case of BYOC - AWS, select the region for the network by clicking on Select Region, select the AWS account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: It indicates the region of cloud service. These regions are the geographic locations where your network instances are going to be hosted. In the case of AWS, each of its regions has multiple isolated locations known as Availability Zones. Amazon RDS provides you the ability to place resources, such as instances and data, in multiple locations. Resources aren’t replicated across AWS Regions unless you do so specifically. Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
BYOC - GCP¶
In the case of BYOC - GCP, select the region for the network by clicking on Select Region, select the GCP account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: GCP Compute Engine resources are hosted in multiple locations worldwide. These locations are composed of regions and zones. A region is a specific geographical location where you can host your resources. Regions have three or more zones. For example, the us-west1 region denotes a region on the west coast of the United States that has three zones: us-west1-a, us-west1-b, and us-west1-c. Putting resources in different regions provides an even higher degree of failure independence. This lets you design robust systems with resources spread across different failure domains. Ref.
Cloud Account: It represents the GCP cloud account that is going to be used for network creation.
Type of Instance: Here, you’ll get options for different virtual machines (VM). You can select the suitable VM type in Google Cloud Platform (GCP) depending on various factors, including your workload requirements, performance needs, and budget constraints. Ref.
BYOC - TENCENT¶
In the case of BYOC - TENCENT, select the region for the network by clicking on Select Region, select the TENCENT account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: A region is the physical location of an IDC. In Tencent Cloud, regions are fully isolated from each other, ensuring cross-region stability and fault tolerance. We recommend that you choose the region closest to your end users to minimize access latency and improve access speed. Ref.
Cloud Account: It represents the TENCENT cloud account that is going to be used for network creation.
Type of Instance: Here, each instance type provides different computing, memory, and storage features. You can choose the instance type that suits your application scale. Tencent Cloud provides a range of instance families with varying combinations of CPU, memory, storage, heterogeneous hardware, and network bandwidth. This gives you flexibility in selecting the appropriate mix of resources for your applications. Ref.
BYOC - DO¶
In the case of BYOC - DO, select the region for the network by clicking on Select Region, select the Digital Ocean account you want to use by clicking on Select Cloud Account, also choose the instance type as your requirement by clicking on Select Instance Type.
Region: A region is a physical location in the world where DigitalOcean has a data center. You can always see the available regions to choose from when creating a new app, Ref.
Cloud Account: It represents the AWS cloud account that is going to be used for network creation.
Type of Instance: It defines the combination of CPU cores and memory. Choose the configuration which could handle loads of your network. This parameter is useful for scaling up the network. The type of Instances may vary from cloud to cloud.
Click on the Create button. A pop-up window will appear similar to the below image, which ensures the successful creation of your network.
Click on continue, and you will be redirected to a page similar to the below image, where you can see the nodes listed you’ve just added to the network.
Add node to a network¶
This section will guide you on how you can add a node to a network.
Select the network to which you want to add a node, and click on the network card Ref.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Add Node option. You will get to see a web page similar to that provided below.
Fill in the details for the new node and click on the Next button. In this step, the cloud configuration and region will be prefilled according to the configuration of the network. Click on the Create button, and it’s done!
Delete node in a network¶
Select the network you want to perform the deleted node to, and click on the network card Ref.. You will get to see similar to the below image.
Click on the delete icon present alongside the node. A pop-up window will open for the confirmation; click on the yes button to confirm.
Delete a network¶
Select the network you want to delete, and click on the network cardRef.. You will get to see similar to the below image.
Click on the Actions button on the top right, and select the Delete Network option. A confirmation window will open; click on the Yes button attached to it.
NOTE It can take a few minutes to delete a network.
description: Build decentralized applications using Credits and Zeeve’s platform. Our documentation provides technical details on authentication, making requests and handling responses for interacting with Credits and the Zeeve platform.¶
Credits Deployment Specifications¶
Currently Credits Networks can be created using some default settings only.
Currently the Zeeve team is working to roll out more features to give you more power in your hands. Keep a watch at the releases or join our active developer community on telegram at https://t.me/ZeevePlatform.
description: Learn how to configure your products on Zeeve’s platform. Our documentation provides detailed instructions and resources for setting up and customizing your products to meet your specific needs¶
Product Configurations¶
Zeeve allows the user to configure their projects onto the platform, which comes with in-built CI-CD pipelines and let Zeeve do the heavy lifting to make a network compatible for your product. This is ensured with some practices developer shall do in order to make the deployments one click based(mentioned later). There are some benefits to configure your product through Zeeve:
Allow automated deployments without having to configure any web servers or domain endpoints.
Form CI-CD pipelines. Authorizing your git account and configuring you git repository to a product.
List your product onto marketplace to reach customers. You can either keep your products private or you can list them or marketplace as fully configured one click deployment products or as just an idea.
Following section defines how to set-up your product on the platform:
Configuring a Product¶
Configuring a product allows you to do one click deployments for your product in any cloud. It is based on configuring your git repo to a product and making sure certain configuration files are utilized in a standard manner such that Zeeve can automate it to 100%.
To configure a product fully as click based deployment make sure you have seen the development practices for the relevant blockchain protocol.
Steps:-¶
Go to
Marketplace -> My products -> Add product.Provide title and Add team members to your product.
Select the blockchain protocol your product is built upon.
Add a small description and logo (if any) to your product.
Provide supporting documents( could be presentation, white paper or architecture document) for the people to understand the idea behind the product.
You can choose to keep a product private to you once you have configured it, or you can choose to list it in marketplace.
Select the type:- Product or Idea.
Publishing as an idea A product can be listed as an idea or as full deployable solution. Listing it as an idea allows the user to present it to marketplace before even the product is ready or has been implemented. Listing it as idea doesn’t require any git authorizations or development practices to worry about.
To publish as an idea, simply select option Publish my idea.
Configuring as a Product A product can be configured such that it is available to the public as a free or as a paid product. Once authrized the party can themselves deploy the product anytime they want. To configure as a product you would need to
Zeeve will make use of the default git branch for setting up the CI-CD piepline for the project.
To configure as a product, select configure product option. It will ask for github authorization and ask you to select one of the projects. Make sure you have followed development practices if you want to make your product deployable in matter of clicks.
Once configured, you can deploy a network and choose to deploy this product on it.
If you want to enter any running events on platform, you can select yes and select event type and problem statements.
description: Explore best practices for developing on Zeeve’s platform. Our documentation provides guidelines and recommendations for building scalable, reliable applications and maintaining high levels of quality and security.¶
Development Practices¶
Every protocol has its own way of development and deployment which might vary a lot from other protocol’s development practices. This make automation for your apps even tougher. Zeeve intends to allow developer to do their dvelopment as they do, and still allow Zeeve’s automation to do the rest. This section speaks of how to develop you applications and make the deploy-ready for Zeeve for which developer shall keep certain practices in mind.
Hyperledger Fabric’s Application Development Practices¶
Refer to Sample Project
Certain practices can help the developer create applications which are one click deployable on Zeeve. They are:-
For packaging your product to be automated by Zeeve, you will need to dockerize your project’s services by creating
Dockerfilesfor them.FROM node:8.9.0 WORKDIR /balance-transfer COPY . . ENV PORT=4000 RUN npm install CMD node app
Make use of
network-config.yaml(connections profiles) andorg.yaml(if required) for all blockchain related configurations. At the time of deployment for a network, Zeeve creates these files and allows the developer to download them along with the other artifacts. You can consider this file to develop your applications. All other application configs should be part of the Docker image itself.Create a
.envfile containing an array of domain prefixes corrosponding to Ingress resource definitions. The syntax should be of the form:("<domain_prefix_1>:<ingress_resource_name_1>" "<domain_prefix_2>:<ingress_resource_name_2> ...")EXT_EXPOSED_SERVICES=("balancetranfer:balance-transfer-ingress")
Create a
docker-compose-build.yamlfile for creating images of all services that your application requires. This will help Zeeve create relevant images, push them to the container-registry and later use them.Each service definition whose container image would be created needs to have an
imagekeyword, the associated value needs to same as that of image name (Deployment.contianers.spec.containers.image) in k8_application.yaml.template.
version: "2.0" services: balance-transfer: build: context: . dockerfile: Dockerfile image: balance-transfer:latest container_name: balance-transfer-default ports: - '4000:4000' command: | bash -c "PORT=4000 node app" restart: always
Create a yaml file
k8_application.yaml.templateand keep it at your project’s root folder. The file needs to keep the following points in account:-The image name for containers needs to adhere to the guideline outlined in the step above.
Define an
imagePullSecretsnamed container-registry-cred. Creation and updation of this secret is handled by Zeeve, but the definition is developers responsibility.For mounting relevant crypto data and channel artifacts in a deployment, Zeeve will create secrets and mount them on
/crypto-datapath. The deployment/s on which this mounting takes place is identified by special character string@@replace_my_crypto_artifacts@@.Host for each Ingress resource will be an amalgamation of information specified in .env file and domain assigned to your Kubernetes cluster.
Take special care to mount relevant persistent volumes as pods will be recreated whenever there is an application update.
apiVersion: v1 kind: Service metadata: name: balance-transfer-svc spec: type: ClusterIP ports: - port: 4000 targetPort: 4000 protocol: TCP selector: name: balance-transfer-dep --- apiVersion: apps/v1 kind: Deployment metadata: name: balance-transfer-dep spec: replicas: 1 selector: matchLabels: name: balance-transfer template: metadata: labels: name: balance-transfer spec: volumes: #- name: balance-transfer-data # persistentVolumeClaim: # claimName: balance-transfer-data-pvc @@replace_my_crypto_artifacts@@ imagePullSecrets: - name: container-registry-cred containers: - name: balance-transfer image: balance-transfer:12 imagePullPolicy: Always ports: - containerPort: 4000 protocol: TCP #livenessProbe: # httpGet: # path: / # port: 4000 command: - bash - -c - | echo "installing GO" cd /usr/local curl -O https://dl.google.com/go/go1.10.3.linux-amd64.tar.gz tar -xvf go1.10.3.linux-amd64.tar.gz echo "export PATH=$PATH:/usr/local/go/bin" >> /root/.bashrc source /root/.bashrc echo "configuring application" mkdir /application cd /application cp -r /balance-transfer/* ./ cp -Lr /crypto-data/* ./artifacts/ #npm install node app volumeMounts: #- mountPath: /application # name: balance-transfer-data @@replace_my_crypto_artifacts@@ --- kind: PersistentVolumeClaim apiVersion: v1 metadata: name: balance-transfer-data-pvc spec: accessModes: - "ReadWriteOnce" resources: requests: storage: "5Gi" --- apiVersion: extensions/v1beta1 kind: Ingress metadata: name: balance-transfer-ingress annotations: kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/backend-protocol: "http" spec: rules: - host: http: paths: - backend: serviceName: balance-transfer-svc servicePort: 4000
While uploading the project attach some supporting documents to explain the organisation names and other details that shall be put while creating networks for the product. These documents will help users to create and deploy networks and products on their own.
description: Learn about the different blockchain protocols available on Zeeve’s platform. Our documentation provides an overview of the key features, benefits and use cases for Hyperledger Fabric, Ethereum, Corda, and other leading blockchain technologies.
meta:
name: robots content: noindex
Major Blockchain Protocols¶
This page of this documentation is here just to provide you with a gist of various major protocols and help you give a rough idea around them. So you can choose the one which suits your usecase well.
HyperLedger Fabric¶
Hyperledger Fabric is an open source enterprise-grade permissioned distributed ledger technology (DLT) platform, designed for use in enterprise contexts, that delivers some key differentiating capabilities over other popular distributed ledger or blockchain platforms. Ref.
Ethereum¶
Ethereum is an open-source, blockchain based distributed computing platform which involves smart contract (business logic coded script) functionality. Ether is a currency used for transactions between accounts and also used to compensate participating mining nodes for computations performed. Ref.
Corda¶
Corda is an open source blockchain project, designed for businesses. Only Corda allows you to build interoperable blockchain networks that transact in strict privacy. Corda’s smart contract technology allows businesses to transact directly, with value. Ref.
Avalanche¶
Avalanche is an open, programmable smart contracts platform with low cost and Solidity compatible dApps. It is the fastest platform as measured by time-to-finality.
Axia¶
Axia is an open, programmable smart contracts platform with low cost and Solidity compatible dApps. It is the fastest platform as measured by time-to-finality.
Binance¶
Binance is an EVM-compatible customized blockchain protocol forked out of Geth and uses consensus of Proof of Staked Authority (PoSA).
Polygon¶
Polygon is a protocol and a framework for building and connecting Ethereum-compatible blockchain networks.
Fantom¶
Fantom is a fast, scalable, and secure layer-1 platform built on an aBFT consensus protocol.
Tron¶
Tron is a protocol and a framework for building and connecting Tron-compatible blockchain networks.
description: Find resources and references for using Zeeve’s platform. Our documentation includes technical guides, API documentation, and other useful materials for developers building applications on the Zeeve platform.¶
References¶
In order to understand various terminologies used in the knowledge base and different releases of Zeeve, they have been provided under below sections.
description: Discover Zeeve’s distributed file system for storing and managing large amounts of data. Our documentation provides an introduction to the key features and benefits of the Zeeve distributed file system, as well as technical details on how to use it with our platform.
meta:
name: robots content: noindex
Zeeve Distributed File System¶
Overview¶
ZDFS is your secure and decentralised storage for your digital assets whether it be NFTs or other digital assets. It has been built by developers for developers and feature the most secure, easy to use and easy to integrate decentralised storage service. Now you don’t need to hustle around IPFS complexities because ZDFS offers you the complete control over your contents using interactive ZDFS GUI. ZDFS allows you to upload your file, folder and content using an IPFS hash of 25GB in size. ZDFS ensures your content is always online in the IPFS network without worrying about unusual downtime and IPFS node management. ZDFS supports IPFS CLI out of the box and also provides Public HTTP APIs to integrate with your application and perform various actions on your content.
There is a series of steps you need to follow in order to access ZDFS service.
Purchase Subscription¶
ZDFS offers you different subscription plans and you can optimize cost as per your requirement using the plan calculator. You need to purchase the endpoints of a particular plan to enjoy seamless services of ZDFS. You can purchase ‘N’ number of endpoints of a particular plan on a monthly basis.
NOTE: We are referring 1 ENDPOINT as 1 Access Key.
There are two plan types offered by ZDFS currently:
Basic Plan¶
This plan is meant for experimenting purpose where you can enjoy the following features:
1 GB Storage.
5 GB Bandwidth.
API Based Access.
Console Management.
Pinning Service.
Community Support.
Standard Plan¶
This plan is meant for small-scale purpose where you can enjoy the following features:
100 GB Storage.
500 GB Bandwidth.
API Based Access.
Console Management.
Pinning Service.
24x7 Hours Professional Support.
INFO: ZDFS also offers ENTERPRISE PLAN, you can contact us at support@zeeve.io to get the quotation.
Go to
ZDFS -> Purchase Subscription.
Select the plan by clicking on it.
You can enter the ‘N’ number of endpoints you want to purchase.
Click on the
Subscribebutton to finally crosscheck your purchase details.
Click on the
Redirect for Paymentbutton to get redirected to the payment gateway.
You can make the payment by entering your card details and applying Coupon Code if you have any.
Create Access¶
You need to generate an access token in order to use ZDFS APIs. You need to have AccessKey & AccessSecret or AccessToken for the same.
Go to
Settings/My Accounts -> API Credentials.
Click on the Create Key button. You will get the pop up form to take some information as described in the next step.
Provide Key Name as per your choice.
Select
ZDFSas Service Type.Select Permissions as per your requirement. Actions are having direct relation with API methods present in the API Document.
Click on the Create Key button in order to generate it.
Please write down
AccessKey,AccessSecretandAccessTokenat a safe place.Close the pop by clicking on the Cancel button.
You can see all your generated access keys within the same section.
Usage¶
You can utilize ZDFS services in ample ways as per your use case. There are 3 ways in which you can use ZDFS as follows:
IPFS CLI¶
Command-line users benefit from ipfs pin remote commands, which simplify remote pinning operations. The built-in pinning service API client executes all the necessary remote calls under the hood.
Configure ZDFS in IPFS CLI¶
You need to have an access token with Pinned Service APIs permissions.
Open a terminal and execute the following command:
ipfs pin remote service add zdfs https://app.zeeve.io/zdfs-api/api/psa ACCESS_TOKEN
For more information please refer to API documentation.
HTTP APIs¶
ZDFS offers you public APIs to integrate in your application. An access token is required to be sent with each request in the HTTP authorization header. Learn More
There are two types of HTTP APIs:
1. Pinning Service API (PSA)¶
Pinning Service API is meant for the purpose of performing operation on remote IPFS node of ZDFS. Pinning Service API spec is standardized specification for the developers and pinning service providers. Pinning Service API reduces the learning curve because of standardization. Learn More.
2. Data APIs¶
ZDFS goes beyond in order to make the remote operation and integration of content with your application more effective. That’s why your control on your content is not limited to just a few pinning methods but there are multiple other ways in which you fully access your content and make a seamless pipeline with your application. Learn More
ZDFS GUI¶
ZDFS provides you with a good and interactive console to manage your content on a click of a button. You can visualise your content and play around. Perform all the operations graphically which are possible through Data APIs. You can even check file CID and availability on the IPFS Public Network without being uploaded on it.
You can perform multiple file based operations using ZDFS console manager in the following optimized ways.
File Upload¶
You can upload your content using file, folder or by file CID upto individual file size 25GB.
Go to
ZDFS -> Files.Click on Upload button.
Choose from the provided upload method.
Select a file and click on Upload File button to complete the process.
File List¶
You can organize your file or folder at the same place so that you can perform different operations individually.
Go to
ZDFS -> Files.
Now, you can perform the following operations by clicking on the More (three vertical dot) button.
File Detail¶
You can check the details of your file in a more readable manner.
Go to
ZDFS -> Files -> More -> Details.
Click on Detail button to view file detail.
File Edit¶
You can change the file or folder name along with the meta data.
Go to
ZDFS -> Files -> More -> Edit.
Click on Edit button to edit the file detail.
File Delete¶
You can delete any content such that it will get automatically unpinned while removing its entry in ZDFS.
Go to
ZDFS -> Files -> More -> Delete.
Now you will see the confirmation dialogue box to reinsure delete.
File Export¶
You can download your content by simply following the steps.
Go to
ZDFS -> Files -> More -> Export.
Click on Export button to start downloading.
File Unpin¶
You can unpin the already pinned file or folder.
Go to
ZDFS -> Files -> More -> Unpin.
Click on Unpin button to make the file unpin.
File Pin¶
You can pin the unpinned file or folder.
Go to
ZDFS -> Files -> More -> Pin.
Click on Pin button to make the file pin.
File Preview¶
You can see your file directly on the IPFS gateway.
Go to
ZDFS -> Files -> More -> Preview.
Click on Preview button to see your file.
File CID Verifier¶
ZDFS offers you to check the IPFS file CID IPFS hash of version 0 and 1 hashing schema. And also provides you to check its availability on IPFS Public Gateway. ZDFS ensures that you can check file CID IPFS hash of a particular content without being uploaded to the IPFS Public Gateway.
Go to
ZDFS -> File CID Verifier.
Drag file or click inside the dotted area.
Now you will be able to see file CID hash and its availability for both the cases.
Click on Clear button to check for another file.
NOTE: File might get available late on IPFS Public Network after upload because it takes some time to propagate on IPFS Public Network
description: Get support for using Zeeve’s platform. Our documentation provides resources for troubleshooting and resolving common issues, as well as information on how to contact our support team for further assistance. robots: noindex¶
Zeeve Support¶
Stuck anywhere? Need help about anything? Want some kind of clarification? Want to pour in your suggestions? Want to raise feature requests? We are easily reachable and are all ears, eyes and mind for you on the following channels :
Chat Client : You can connect with us via our chat client. This client can be found at the bottom right corner across the Zeeve platform. Talk to us, by just hitting that green button you find there.
Telegram : You can also join our active developer community on telegram.
Glossary¶
Access Key¶
Access Key ID helps in accessing and controlling the cloud account and services like EC2, S3, SimpleDB, CloudFront, SQS, EMR, RDS, etc. In case of AWS its length is 20 alphanumeric characters long like ABCDGHJK1234CBDG123C . It can be shared with others as well.
Bitcoin¶
Bitcoin is an open source public blockchain in which anyone can participate. Currency exchange in this is termed as Bitcoin, which is having value in stock exchange as well. It is a peer-to-peer technology to operate with no central authority or banks; managing transactions and the issuing of bitcoins is carried out collectively by the network. Ref.
Blockchain¶
Blockchain is considered as a chain of blocks. Blocks are nothing but collection of data. Blockchain is an immutable time-stamped series of data that is maintained within a distributed network of peer nodes. These nodes each maintain a copy of the ledger by applying transactions that have been validated by a consensus protocol, grouped into blocks that include a hash that bind each block to the preceding block.
Certificate Authority¶
Certificate Authority accorss this documentation refers to HyperLedger Fabric’s key component. This component is responsible for issuing identification material like certificates and keys for an organization.
Cloud¶
Distributed Ledger Technology (DLT)¶
Distributed Ledger is a backbone of Blockchain. Literal meaning of Ledger says that a book contains different records, which in turn is distributed in nature. DLT is a digital system which is recording the transactions and their details in distributed manner. Distributed ledger don’t have any central data store.
Inode¶
Instance Type¶
In cloud instance is considered as a node termed as EC2 (Elastic Compute Cloud). Instance type is a term given which varies based upon the hardware configuration of instance created. In Zeeve we have various instance type both in AWS as well as in Azure. For more information click for AWS Instance Type and Azure Instance Type.
IOT¶
Internet of Things
Kafka¶
Kafka is a message handling system which uses Publish-Subscribe model. Consumers subscribe to the topic to receive new messages, that are published by a Producer. Topics are nothing but messages, so when they become huge in number, then they are split into partitions, and Kafka guarantees that all messages inside a partition are sequentially ordered. Hyperledger Fabric ordering service nodes (OSNs) use the Kafka cluster and provide an ordering service to your blockchain network. Kafka is permissioned voting based consensus type, here leader does the ordering, only in-sync can be voted as leader.
Node¶
Node is an instance of a network. It basically a connection point which is helping in receiving, creating, storing and sending data.
Network¶
Network is a collection of nodes/instances. In Zeeve, when you create a network over the cloud then it asks you for providing the number of nodes and other configuration details. Once all the installation and configuration gets over, it results in [[How_to_create_my_first_network|creating]] your Blockchain network.
Orderer¶
Orderers are considered as the special nodes, which are helping each peer nodes to have consistent ledger by enabling the interaction of peer nodes and applications participating in the network.
Secret Key¶
Secret key is used along with Access key in order to access and control the cloud account and services like EC2, S3, SimpleDB, CloudFront, SQS, EMR, RDS, etc. In case of AWS its length is 40 alphanumeric-slash-plus characters long like ******KOsJW/******/c*********+***wy . It can’t be shared with others.
Smart Contract¶
Smart Contract is a piece of code that contains the business logic. It’s execution is done in a secured environment. This is the part of the blockchain that ensures validity of data going into it.
Zookeeper¶
Zookeeper is a distributed key-value store, most commonly used to store metadata and handle the mechanics of clustering. It allows clients of the service (the Kafka brokers) to subscribe and have changes sent to them once they happen. This is how brokers know when to switch partition leaders. Zookeeper is also extremely fault-tolerant as it ought to be, since Kafka heavily depends on it.
Releases¶
Zeeve 1.5.0 IBM Cloud Release¶
Now use your favourite Cloud to Deploy your favourite Blockchain. This update includes IBM cloud support, which allows you to deploy the choice of Blockchain deployments in a few clicks.
Key Highlights of this release, Now deploy on IBM cloud:
Hyperledger Fabric
Hyperledger Sawtooth
R3 Corda
Ethereum
Credits
What’s up next
Support for private networks deployment for Corda.
One click CorDapps deployment using Marketplace
Google Cloud support.
Did someone say bugs? We have restocked the bug repellent to allow seamless experience.
Night mode is shinier then it was.
Zeeve 1.4.0 R3 Corda Release¶
We continuously upgrade Zeeve with smaller updates having bigger impacts. This release will be the addition of one of the leading Consortium protocol to the platform. Zeeve will now allow you to deploy Corda Production, Pre-Production and Test net on demand.
Key Highlights of this release:
Corda as a protocol choice to deploy
Option for selecting your public zone:-
R3 production zone
R3 pre-production zone
R3 test-net
Selecting version for your corda nodes/notaries.
Specifying detailed configurations for your corda nodes and notaries.
Also allowing options for doing initial registration or to upload your keystore/SSLstore files with custom passwords and other CSR details.
Currently supports deployment on AWS, Azure, Digital Ocean, IBM Cloud and Google cloud.
What’s up next
Support for private networks deployment for Corda.
One click CorDapps deployment using Marketplace
Google Cloud support.
IBM Cloud (BlueMix) support.
Did someone say bugs? We now have made Zeeve stable more than ever. And these as well:
Project creation bug fixed for Digital Ocean.
Day/Night visual mode is persistent now.
Zeeve Digital Ocean Follow-up Release¶
We are committed to continuously update Zeeve and provide you all the Blockchain essentials required to power up your Blockchain Business needs. In the latest Follow-up Release, Zeeve now allows you to Deploy and Manage Hyperledger Fabric Networks on DigitalOcean Cloud using Kubernetes.
What Support for Fabric allows you to do on DO:
• Create & scale Fabric networks on Digital Ocean Cloud • Create & download cryptographic artifacts • Channel configurations • Choice of consensus - RAFT, Solo & Kafka • Organization wise Orderers • Choice between LevelDb and CouchDb for peer • Configure CAs with admin’s user-name and password • Persistent volume option for every service • Option to create and join application channels • Option to add more nodes to existing networks
Did someone say bugs? We now have made Zeeve stable more than ever.
Check now @ https://www.zeeve.io
Zeeve 1.3.0 Major Release¶
Another upgrade to upgrade your Blockchain experience. Zeeve 1.3.0 has been released and is available for use. We now support DigitalOcean, this allows you to deploy your Blockchain networks in your own DigitalOcean cloud infrastructure and its just a few clicks away.
Key Highlights of this release:
Deploy Ethereum, Sawtooth and Credits networks on DigitalOcean.
Fabric Networks are more configurable now with
Support for RAFT consensus
Organization wise Orderers
Choice between LevelDb and CouchDb for peer.
Configure CAs with admin’s username and password.
Persistent volume option for every service.
Option to create and join application channel added.
Option to add more nodes to the network.
What’s up next
R3 Corda network deployments
Zeeve managed deployments
Fabric support on DigitalOcean
Did someone say bugs? We now have made Zeeve stable more than ever. And these as well:
Error notifications are more detailed
You can see cloud VPC limit errors in Zeeve
Check now @ https://www.zeeve.io
Zeeve 1.2.0 Major Release¶
Credits Public Blockchain deployment is now Supported
If you are a developer then you must be familiar with Credits already as an open-source, fully decentralized blockchain software protocol. Now it is simpler then ever to do Credits. If you are a developer working on credits or a business running a production grade solution, you can now sip a coffee, deploy, monitor and manage your Credits deployment on cloud with ease.
Credits is now integrated with worlds leading Blockchain as a Service platform Zeeve (https://zeeve.io). Zeeve will power up your credits development and production environments. With a few clicks, it will enable you to deploy credits on your own cloud infrastructure.
1 2 3 Credits with Zeeve:
Choose among your choice of cloud providers, i.e. AWS and Azure
Sign up with Zeeve and authorize your cloud account through your profile
Launch a Credits MainNet Node through create a network option
Monitor resources, start/stop or delete on demand
Continue to create more nodes in different cloud data centers
Whats coming up for Credits
TestNet support to be available soon
Support for hosted infrastructure for seamless and managed deployments
Wallet support for Credits
Smart Contract deployments
We hear you! You can submit feedback/features to us to improve
We have also squashed a few bugs and fixed some annoying issues. Please feel free to test the beta, we are open to suggestions, issues and feature requests.
Check now @ https://www.zeeve.io
Zeeve 1.1.1 Minor Release¶
IoT as a Service is the latest offering.
Zeeve 1.1.1 has been released and is available for use. Platform already had the support to deploy Hyperledger Sawtooth, Fabric and Ethereum. Now we have added support for IoT Services to it too.
Key highlights of 1.1.1
Create data publish/consume APIs
Create and Manage API service keys for IoT data access
Fabric stability and improvements
Now you can delete/start/stop/restart fabric nodes.
Azure cloud support is now enabled for Sawtooth and Ethereum.
Fabric Network now allows users to download the blockchain artifacts.
Live logs are now available while you watch your Tasks.
And there is more
More enhancements to Dark Mode
Several performance improvements
We have also squashed a few bugs and fixed some annoying issues. Please feel free to test the beta, we are open to suggestions, issues and feature requests.
Check now @ https://www.zeeve.io
Zeeve 1.1.0 Released¶
Zeeve 1.1.0 has been released and is live.
The Major change you can enjoy is addition of Hyperledger Fabric, while it already supported Hyperledger Sawtooth and Ethereum.
Fabric release allows
Creation of cryptographic artifacts
Supports Channel configurations
Kubernetes based cloud service on your own AWS account
Deploy production grade multi-ordered network Choice of consensus
Solo orderer
Kafka based ordering
And there is more
Dark mode is made even better
Activity and logs are more detailed
Dashboard now auto updates
Several performance improvements
We have also squashed a few bugs and fixed some annoying issues. Please feel free to test the beta, we are open to suggestions, issues and feature requests.
Check now @ https://www.zeeve.io