evan.network Developer Documentation

standalone Hello World

The goal of this tutorial is to interact with different functionalities of the evan.network blockchain, by the help of DBCP or the evan.network blockchain-core. A simple HTML file is being produced, which is able to use all functionalities without any runtime environment. With the help of this small example, you can develop applications on the evan.network blockchain that run completely independently.

After creating the ÐApp functionalities, you can use a ‘greeter contract’ sample to create a contract instance. The DBCP description attached to the ‘greeter contract’ will use your ƉApp as display possiblity.

standalone tutorial preview

1. Get Tutorial Application

2. Tutorial applications

Within the ƉApps folder, you will find frontend ‘Hello World’ applications for DBCP and blockchain-core (in short bcc). These projects have the minimal setup for interacting with the evan.network framework. The DBCP / bcc libraries are bundled using Browserify and published to the IPFS. So the application can attain the dependencies directly from IPFS.

In this simple scenario, both examples look almost the same. This is because the bcc is an extension of the DBCP, including various encryption mechanisms and structures, such as the mailbox or the address book, which are not used for a ‘Hello World’ example.

In the bcc example, the runtime is less encapsulated and can therefore be better adapted, but needs a few more configuration parameters.

2.1 local development

For testing, you need to open the “dapps/hello-world-bcc/src/index.html” / “dapps/hello-world-dbcp/src/index.html” file within you local browser.

If you want to test the application using a small web server, you can run the following command within your root Lerna project:

npm run serve

The web server will be started at port 3000 and each dapps/\*\*/src folder is mapped for file serving. So you can open the following URLs to view the application:

  • http://localhost:3000/hello-world-bcc/index.html
  • http://localhost:3000/hello-world-dbcp/index.html

2.2 index.html

The index.html is the point of entry for the application that requires the necessary files to start the DBCP / bcc. You can simply insert the origin of the library using a script tag. In addtion, the Web3 and IPFS library needs to be loaded. This sample shows how to load the DBCP using IPFS.

<!-- Loading DBCP -->
<script src="http://ipfs.evan.network/ipfs/QmPCNLE794BCwsriAg9gYjCha3EPZHDxefB5GNwugoUgfh"></script>

<!-- Loading Web3 -->
<script src="http://ipfs.evan.network/ipfs/QmXVX173ygohnfg8rxzhynrNFHLTLKUqcBEKAFrEZGA9JN"></script>

<!-- Loading ipfs-api -->
<script src="http://ipfs.evan.network/ipfs/QmczFSf23jB7RhT5ptnkycCf57hTGdfUE1Pa2qbZe4pmEN"></script>

2.3 index.js DBCP

After all depdencies have been loaded, you can start your application right away within the index.js file. Use the createRuntime function to generate a new DBCP Runtime. Using this Runtime, you can access all the functionalities that are exposed by DBCP / bcc.

async function createRuntime() {
  const runtimeConfig = {
    accountMap: {
    ipfs: { host: 'ipfs.evan.network', port: '443', protocol: 'https' },
    web3Provider: 'wss://testcore.evan.network/ws',

  // initialize dependencies
  const web3 = new Web3();
  web3.setProvider(new web3.providers.WebsocketProvider(runtimeConfig.web3Provider));
  const dfs = new dbcp.Ipfs({ remoteNode: new IpfsApi(runtimeConfig.ipfs), });

  // create runtime
  const runtime = await dbcp.createDefaultRuntime(web3, dfs, { accountMap: runtimeConfig.accountMap, });

  return runtime;

When we run our application without any contract ID, we load a test description from the dashboard.evan ENS address to show that it is also working without any contracts. After deploying the ‘Hello World’ sample into a contract, you can access several functions of the contract. The getContractId function shows that the contract ID, which should have been loaded, can be parsed out of the window location. When you have deployed the application, append the following parameters to the applications URL: ‘?contractid=0xB070f2e1FcbE4d01987E30a9DF9F6e22E69EA105’.

 * Get the contract id from an url parameter or from last url hash value for iframe routing.
 * @param {string} url url that should be checked, default is window.location.href
function getContractId(url) {
  // try to load contract id over url parameter
  const match = (url || window.location.href).match('[?&]contractid=([^&]+)');
  let contractId;

  if (match) {
    contractId = match[1];
  } else {
    // try to get contract id from url hash (#/.../0x00)
    contractId = (url || window.location.href).split('/').pop();

  if (contractId.indexOf('0x') === 0) {
    return contractId;

 * Start Hello World sample.
async function runHelloWorld() {
  window.runtime = runtime = await createRuntime();

  // get contract id from current url or from parent
  let contractId = getContractId();
  if (!contractId && window.parent) {
    contractId = getContractId(window.parent.location.href);
  if (!contractId || contractId.indexOf('0x') !== 0) {
    contractId = '';

    document.getElementById('test-description').innerHTML = 'not set';
  } else {
    // load opened contract
    const contract = await runtime.description.loadContract(contractId);
    // load sample contract data
    document.getElementById('contract-id').innerHTML = contractId;
    document.getElementById('owner').innerHTML = await contract.methods.owner().call();
    document.getElementById('contract-methods').innerHTML = Object.keys(contract.methods).join(', ');
    document.getElementById('sample1').innerHTML = await contract.methods.greet().call();
    document.getElementById('sample2').innerHTML = await runtime.executor.executeContractCall(contract, 'greet');
  // load contract description
  let description = await runtime.description.getDescription(
    contractId || 'dashboard.evan',

  document.getElementById('test-description').value = JSON.stringify(

2.4 index.js BCC

In comparison, the createDefaultRuntime of the DBCP is replaced with the following code. By using this code, you will be enabled to adjust the whole configuration and use the modular components as you like to. This means that the frontend is able to put the individual components together as required. The result looks almost like the runtime of the DBCP, but with much more features.

// BCC core configuration
const config = {
  // web3Provider: 'ws://',
  web3Provider: 'ws://localhost:8546',
  nameResolver: {
    ensAddress: '0x937bbC1d3874961CA38726E9cD07317ba81eD2e1',
    ensResolver: '0xDC18774FA2E472D26aB91deCC4CDd20D9E82047e',
    labels: {
      businessCenterRoot: 'testbc.evan',
      ensRoot: 'evan',
      factory: 'factory',
      admin: 'admin',
      eventhub: 'eventhub',
      profile: 'profile',
      mailbox: 'mailbox'
    domains: {
      root: ['ensRoot'],
      factory: ['factory', 'businessCenterRoot'],
      adminFactory: ['admin', 'factory', 'ensRoot'],
      businessCenter: ['businessCenterRoot'],
      eventhub: ['eventhub', 'ensRoot'],
      profile: ['profile', 'ensRoot'],
      profileFactory: ['profile', 'factory', 'ensRoot'],
      mailbox: ['mailbox', 'ensRoot'],
  smartAgents: {
    onboarding: {
      accountId: '0x063fB42cCe4CA5448D69b4418cb89E663E71A139',
  alwaysAutoGasLimit: 1.1,

// runtime configuration
const runtimeConfig = {
  accountMap: {
  ipfs: { host: 'ipfs.evan.network', port: '443', protocol: 'https' },
  web3Provider: 'wss://testcore.evan.network/ws',

 * Smart contracts solc representation.
Solc = function (SmartContracts) {
  this.SmartContracts = SmartContracts;

Solc.prototype.getContracts = function() {
  const shortenedContracts = {};

  Object.keys(this.SmartContracts).forEach((key) => {
    const contractKey = (key.indexOf(':') !== -1) ? key.split(':')[1] : key
    shortenedContracts[contractKey] = this.SmartContracts[key]

  return shortenedContracts;

 * Create DBCP runtime.
async function createRuntime() {
  // initialize dependencies
  const web3 = new Web3();
  web3.setProvider(new web3.providers.WebsocketProvider(runtimeConfig.web3Provider));

  // load SmartContracts from ipfs externally
  const SmartContracts = await SystemJS.import('https://ipfs.evan.network/ipfs/QmdB15Kqy4Gwe1aSSS6grj5ftSaFbUktqVdB1G4wkBYP1G/compiled.js');
  const keyProvider = new bcc.KeyProvider(runtimeConfig.accountMap);
  keyProvider.origin = keyProvider;

  // initialize the bcc core runtime
  await bcc.createAndSet({
    accountId: Object.keys(runtimeConfig.accountMap)[0],
    coreOptions: {
      web3: web3,
      solc: new Solc(SmartContracts),
      dfsRemoteNode: bcc.IpfsRemoteConstructor(runtimeConfig.ipfs),
      config: config,
    keyProvider: keyProvider,
    CoreBundle: bcc,

  return bcc.CoreRuntime;

3 Deploy it to the Real World

3.1 Deploy ƉApp within an Contract

Each application can be deployed together with a contract. This allows the contract to contain the information as it should be displayed. A little sample how to create and sample contracts with your ‘Hello World’ ƉApp can be found within the dapps-tutorial-angular/scripts/create-contract.js file. Run the following commands (each ‘Hello World’-DBCP can be replaced with hello-world-bcc):

  1. Start IPFS client
  2. Publish your files to the IPFS
    ipfs add -r dapps/hello-world-dbcp/src

    dapps-tutorial - directory

  3. Insert the deployed folder hash (e.g. ‘QmfZLwBPUT1n3DoJqpqnLCTcUKABLgUsgfE4KetkXdq8XK’) to the correct origin to dbcp.json file. dapps-tutorial - directory

  4. Deploy it to the contract
    npm run deploy-to-contract hello-world-dbcp

You will get a console output similar to the following. Behind the log parameter created contract, you will find the newly created contract ID.

dapps-tutorial - directory

3.2 Deploy ƉApp to ENS

Have a look ƉApp deployment.

3.3 View it in the Real World

After you deployed the application within a contract or by using an ENS address, the ƉApp is available from everywhere, globally. To test this, you can use the evan.network dashboard. Open the following URL https://dashboard.evan.network/index.html and navigate to the favorites ƉApp tab. Before you can access your favorites, it is necessary to create an evan.network identity. If you haven’t created an identity before, have a look here.

Add the favorite using the following steps:

  1. Open Dashboard: dapps-tutorial - directory

  2. Add the favorite: dapps-tutorial - directory

  3. Open the DApp: dapps-tutorial - directory

  4. Result:

By having a look into the browser network tab you will see that your data is loaded from the IPFS server:

dapps-tutorial - directory