This Dapp allows you to browse the list of services from the SingularityNET Registry and call them. The beta dapp is under active development and will see several changes in the upcoming weeks
- Navigate to the SingularityNET beta dapp
- Sign up / Login to the DApp account
- Every service has a free trial, so you can invoke the service without any payment
- If free trial has expired, you need to use your AGIX tokens to make the call using Metamask (this is on the mainnet)
- Authorize and Transfer tokens to the Multi party escrow in the Accounts page
- Follow the service execution steps on the service details page
- The result from the operation is displayed in the result tab
- Install Node.js and npm
npm install
to get dependenciesnpm run start
to serve the application locally and watch source files for modifications
Currently the UI needed by a service to capture inputs and render the output must be provided by the service developer as a PR. It must be provided in the form of a React component. This approach will change in the future as we support a generic mechanism to declaratively describe a service's API. See this for more details
git clone git@github.com:singnet/snet-dapp.git
cd snet-dapp
npm install
cp .env.sandbox .env
-
Update
.env
file to reflect the actual values for each environment variable.-
REACT_APP_SANDBOX_SERVICE_ENDPOINT
The endpoint of the service running locally.
snetd
defaults tohttp://localhost:8088
. -
REACT_APP_SANDBOX_ORG_ID
&REACT_APP_SANDBOX_SERVICE_ID
The
org_id
to which the service belongs and theservice_id
of the service. The values set for these variables will be used for registering the custom ui. -
REACT_APP_WEB3_PROVIDER
The infura endpoint to be used for the Web3 connection.
-
-
Start the AI service locally along with the snet daemon. Make sure the blockchain is disabled in the daemon configuration.
-
Building the custom ui
-
Generate
js
stubs from.proto
filesFor the custom ui to talk to the services on SingularityNET platform via the DApp, we are using gRPC-web by improbable-eng. Apart from the steps mentioned at the official documentation to generate
js stubs
from.proto
definitions, you also need to provide thenamespace_prefix
flag to the generator. Here is an example which illustrates the usageprotoc \ --plugin=protoc-gen-ts=./node_modules/.bin/protoc-gen-ts \ --js_out=import_style=commonjs,binary,namespace_prefix=<uniq_name_space>:. \ --ts_out=service=true:. \ example_service.proto
<uniq_name_space> should be a combination of
package_name
+org_id
+service_id
. For the following proto file withorg_id=snet
andservice_id=example-service
the namespace_prefix would beexample_service_snet_example_service
.
PS: All the-
should be replaced by_
. -
You need build the custom UI following the steps
Create a new directory named after the
org-id
to which this service belongs insidesrc/assets/thirdPartyServices
. It could be possible that the directory already exists, in which case you can use it instead of creating a new one.Create a new directory named after the
service-id
under the newly created directory in the above stepe.g. for a service with org-id: snet and service-id: example-service you will have to do the following assuming you are at the root of the
snet-dapp
cd src/assets/thirdPartyServices mkdir snet cd snet mkdir example_service cd example_service
Put the all the resources used by the custom ui under this directory including the
js stubs
.
-
-
Register the custom ui
Add an entry for the new service in
src/assets/thirdPartyServices/index.js
if it does not already exist. Add the following line towards the end of the file. Make sure to replaceorgId
,serviceId
andCustomUIComponent
accordingly.thirdPartyCustomUIComponents.addCustomUIComponent(orgId, serviceId, CustomUIComponent);
-
Assuming that the snet daemon is running on port
8088
, running the bellow commands should bring up the DApp in sandbox mode for local development.npm run sandbox