Task Example 0: Hello World!
Info
This example illustrates following Golem features & aspects:
- Mid-level components usage
Prerequisites
The only assumption made in this article is that you have some familiarity with basic Golem application concepts. Here's a good starting point to learn about these:
Golem Application Fundamentals
Here are the prerequisites in case you'd like to follow along and/or experiment with the code presented in this article:
- you have a local
yagnanode set up (instructions can be found here: Requestor development: a quick primer - you have the Golem JS API set up on your machine (instructions here: Run first task on Golem)
Requestor agent code
Let's jump straight to the example:
import {
Package,
Accounts,
Allocation,
Demand,
DemandEvent,
DemandEventType,
Proposal,
Agreement,
Activity,
Result,
Deploy,
Run,
Script,
Start,
ConsoleLogger
} from "yajsapi";
async function main() {
const logger = new ConsoleLogger();
const vmPackage = await Package.create({imageHash: "9a3b5d67b0b27746283cb5f287c13eab1beaa12d92a9f536b747c7ae"});
const accounts = await (await Accounts.create({yagnaOptions: {apiKey: 'YOUR_YAGNA_APP_KEY'}})).list();
const account = accounts.find((account) => account?.platform === 'erc20-rinkeby-tglm');
if (!account) throw new Error("There is no available account");
const allocation = await Allocation.create({account, logger});
const demand = await Demand.create(vmPackage, [allocation], {logger});
const offer: Proposal = await new Promise((res) =>
demand.addEventListener(DemandEventType, async (event) => {
const proposalEvent = event
as
DemandEvent;
if (proposalEvent.proposal.isInitial()) await proposalEvent.proposal.respond(account.platform);
else if (proposalEvent.proposal.isDraft()) res(proposalEvent.proposal);
})
);
const agreement = await Agreement.create(offer.id, {logger});
await agreement.confirm();
const activity = await Activity.create(agreement.id, {logger});
const script = await Script.create([new Deploy(), new Start(), new Run("/bin/sh", ["-c", "echo 'Hello Golem'"])]);
const exeScript = script.getExeScriptRequest();
const streamResult = await activity.execute(exeScript);
const results: Result[] = [];
for await (const result of streamResult) results.push(result);
console.log(results[2].stdout);
await activity.stop();
await agreement.terminate();
await allocation.release();
await demand.unsubscribe();
}
main().catch((e) => {
console.error(e);
process.exit(1);
});
How does it work?
The main() function
The interface of each module has mostly asynchronous methods, so we have to embed all the code inside the async function main.
Logger
Each module has specific options. The constructor parameter that occurs in each of the modules is the logger object. It is responsible for showing messages during the lifetime of a given module. The logger object must implement the Logger Logger interface. In this example, we will use a ready-made ConsoleLogger implementation that prints all messages in the console.
Package
The first component is Package. When creating a Package, we must determine which image we want to use. Currently, only VM images can be used, though with future implementations packages for wasm and other images will become feasible.
To create package we need defined PackageOptions:
const vmPackage = await Package.create({ imageHash: "9a3b5d67b0b27746283cb5f287c13eab1beaa12d92a9f536b747c7ae" });
Account
We need to know the account entity provided by yagna deamon. For list available account we can use:
and then find an account that has the appropriate payment platform:
For the purposes of this example, we choose an account that has the ability to make payments on the erc20-rinkeby-tglm platform.
Allocation
Now we need to create allocation for chosen account by:
An Allocation is a designated sum of money reserved for the purpose of making some particular payments. Allocations are currently purely virtual objects. An Allocation is connected to a payment account (wallet) specified by address and payment platform field.
Demand
To create and publish Demand on the market, you need to create it for previously created package and allocation.
To customize the Demand object, you can pass the corresponding DemandOptions.
Demand object can be considered an "open" or public Demand, as it is not directed at a specific Provider, but rather is sent to the market so that the matching mechanism implementation can associate relevant Offers. Note: it is an "atomic" operation, ie. as soon as Demand is created, the subscription is published on the market.
Demand is a special entity type because it inherits from the EventTarget class. Therefore, after creating it, you can add listeners to it, which will listen to offers from the market on an event of a specific type: DemandEvent, to do this, add a listener with:
const offer: Proposal = await new Promise((res) =>
demand.addEventListener(DemandEventType, async (event) => {
const proposalEvent = event as DemandEvent;
if (proposalEvent.proposal.isInitial()) await proposalEvent.proposal.respond(account.platform);
else if (proposalEvent.proposal.isDraft()) res(proposalEvent.proposal);
})
);
Each occurrence of the event checks whether it is the initial proposal from the provider (Proposal) or the next version - Draft (Offer).
If it is a proposal, we must respond to it using the .respond(account.platform) method and pass our payment platform as parameter.
In the case when it is a Draft, we can proceed to further process the offer.
Agreement
Now we can create initial Agreement with provider by:
This initiates the Agreement handshake phase. Created Agreement is in Proposal state. We can pass additional options ActivityOptions.
If the agreement is successfully created, we can confirm it by:
After that we have ability to create activity on provider side and run scripts.
Activity
Activity is an object representing the runtime environment on the provider in accordance with the Package specification.
As part of a given activity, it is possible to execute exe script commands and capture their results.
The first thing we need to do is create a script that consists of commands.
Depending on the type of runtime, the sent script should be in accordance with its specification.
In order to execute any Run command in VM Runtime, first we need to get our activity state to Ready. To do this, we need to send a script containing the Deploy and Start commands first,
then we can add any Run command.
const script = await Script.create([
new Deploy(),
new Start(),
new Run("/bin/sh", ["-c", "echo 'Hello World'"]),
]);
We can always check the status of our activity by:
After creating the script, we can execute it on our activity:
const exeScript = script.getExeScriptRequest();
const streamResult = await activity.execute(exeScript);
As a result of executing the script, we receive a Readable object, which will asynchronously return the results of execution of individual commands. We can capture these results in two ways:
- synchronously - using the
for awaitconstruct: - or asynchronously - by event handlers:
Now in results we have an array of Result objects indexed by command number in the script starting from 0.
To display the result of the Run command, do the following:
Final tasks
After completing all tasks, you must end the activity and terminate the contract, release allocations and unsubscribe the demand. To do this, you must:
await activity.stop();
await agreement.terminate();
await allocation.release();
await demand.unsubscribe();
All done!
That's all there is to the example!
To run it on your local machine make sure you have a yagna node running and set up as a requestor (take a look here in case of any doubts: Requestor development: a quick primer). You can then issue the following command:
This assumes you're in the directory which contains the hello.ts file. You'll also need to provide your node's actual app key. If everything went fine you should see a log similar to the one below:
2023-01-31T15:03:30.103Z [debug] Allocation 88ced4c2-ee07-4ca0-a4b7-e5a6d8e0345d has been created using payment platform erc20-rinkeby-tglm
2023-01-31T15:03:30.588Z [info] Demand published on the market
2023-01-31T15:03:40.673Z [info] Agreement cddbb6ca895c2e4a05a71f37ebdad5fdaf0ec8a667343ebac264000da7b15c26 created
2023-01-31T15:03:40.932Z [debug] Agreement cddbb6ca895c2e4a05a71f37ebdad5fdaf0ec8a667343ebac264000da7b15c26 approved
2023-01-31T15:03:41.815Z [debug] Activity bc28956ae3c64ea39a8b6408a6a05c00 created
2023-01-31T15:03:41.905Z [debug] Script sent. Batch ID: 11e019868f854c8d9ee154ace90fe74c
Hello World
2023-01-31T15:03:46.111Z [debug] Activity bc28956ae3c64ea39a8b6408a6a05c00 destroyed
2023-01-31T15:03:46.209Z [debug] Agreement cddbb6ca895c2e4a05a71f37ebdad5fdaf0ec8a667343ebac264000da7b15c26 terminated
2023-01-31T15:03:46.218Z [debug] Allocation 88ced4c2-ee07-4ca0-a4b7-e5a6d8e0345d has been released.
2023-01-31T15:03:46.222Z [debug] Demand 583383e485da4ffc8d9d2690d1659905-2b72ccb054d6810a843811c97ac92fb4bdb124523b7f3d979469a878d293faa6 unsubscribed
Warning
In the current version, the payment acceptance mechanism has not yet been implemented.