Unikernel-z: A unikernel for the Network of Momentum

[romeo]

I’m no expert, but my understanding is even just replicating any basic zApp or tool built on NoM on the unikernal would provide a few key benefits:
*Speed (launching in a custom image that only holds what is required)
*Enhanced security (running in an isolated layer)
*Size (should allow zApps to have a smaller footprint)

I also hope individual contracts could eventually be run within NoM unikernals which would allow the contract operator to upgrade the contract without needing to make modifications to the base network

Also there’s a cool project called Mewz (GitHub - mewz-project/mewz: A unikernel designed specifically for running Wasm applications and compatible with WASI) which is a good example of unikernal use

[EovE7Kj]

@0x3639

@EovE7Kj do you agree with these potential use cases?

These are all feasible zApp implementations, and this is good to circle back on this discussion. Now that the phase 1 delivery is complete, I am starting to brainstorm a potential zApp(s) for phase 3.

[EovE7Kj]

@aliencoder

I’m researching how we can integrate a gas metering system inside the unikernel controlled by an embedded contract.

I’m still looking into this as well, let me know what you find. This is the most critical component of the zApp development.

[0x3639]

@EovE7Kj

I am starting to brainstorm a potential zApp(s) for phase 3.

Personally I think a Uniswap type DEX is a logical first step. We can fork the uniswap front end and showcase what is possible on NoM. Everyone wants to trade tokens.

Another idea could be implementation of this: https://medium.com/@zenon.network/the-new-nft-standard-when-cryptography-meets-steganography-9e356007dcaa

@sol did some high level work on this topic and did some POC work in his repo. I think others have looked into this too.

[0x3639]

@EovE7Kj

I am starting to brainstorm a potential zApp(s) for phase 3.

I’m thinking about this more. New idea. Why not focus on something that is novel and unique to NoM that could attract devs to the project.

What can we highlight?

1. Unikernel architecture
2. Adaptive Smart Contracts (link above)

What is a “simple” idea that is useful, demonstrates the unikernel architecture and showcases adaptive smart contracts? I understand what an Adaptive Smart Contract is, but I’m not entirely sure what about our architecture that makes them possible. Maybe @EovE7Kj if we understood that, we can brainstorm more ideas.

[EovE7Kj]

@0x3639

I understand what an Adaptive Smart Contract is, but I’m not entirely sure what about our architecture that makes them possible

Currently, we don’t have the architecture to make adaptive smart contracts. @aliencoder’s work on supernova chain is opening doors to EVM support, and the potential for embedded contracts within unikernel-z is what I am focusing on here.

[edgepillar]

@EovE7Kj

@0x3639

I understand what an Adaptive Smart Contract is, but I’m not entirely sure what about our architecture that makes them possible

Currently, we don’t have the architecture to make adaptive smart contracts. @aliencoder’s work on supernova chain is opening doors to EVM support, and the potential for embedded contracts within unikernel-z is what I am focusing on here.

Is it possible to explain this simply by illustrating it with a use case example?

[EovE7Kj]

@edgepillar

Is it possible to explain this simply by illustrating it with a use case example?

Any decentralzied application you can think of can be offloaded to unikernel as opposed to running in EVM. An oracle network, a social network, a CDN, or even an NFT arcade are all feasible.

Some great web3 examples have been built on cartesi, you can check out their rollup lab

Rollup Lab - Projects Powered by Cartesi

[EovE7Kj]

@aliencoder

Is it hard to create a custom module that is loaded by the unikernel? Can you tell a bit about the lifecycle of an unikernel? Thanks!

I have conceptualized this as a sort of “Zenon unikernel dev kits”, the way we have the SDKs.

The idea is: you write your zApp in your language of choice - Go, JS, C, whatever - you run a binary ELF to compile it to a qcow2 unikernel image. At compile time, it will identify all the necessary components, libs, packages, and build the unikernel around it, implementing the computation mechanisms (gas metering, contract execution)

[0x3639]

what if we did something like “r/place”

https://www.reddit.com/r/place/comments/twft1q/full_screenshot_of_rplace_2022/#lightbox

[aliencoder]

@EovE7Kj

This is the most critical component of the zApp development.

I agree. I’m still researching at the moment. But we have options.

[EovE7Kj]

@sultanofstaking

You submitted a phase 1 for payment in AZ correct? Is that different than the Phase 1 you describe above?

Phase 1 delivery is complete. I am still working on the performance analysis for the unikernel; I will await Phase 1 to reach quorum until I submit it for Phase 2

[0x3639]

More dApp ideas:

• Satoshi Dice
• Prime Dice - Looks like there might be some geo restrictions.
• DEX (back to original idea)
• Decentralized Voting System - Delegators or pillars create a poll that is voted on. Votes require a signed message (absent a Web3 wallet). The vote is then associated with a pillar and weighted based on amount of ZNN delegated. The goal is to determine a delegator weighted response by Pillar to a pole. Wait… not sure this requires a smart contract. Sounds like math only. Let me think about a variation that is more useful.

[NeoShredder]

A feeless Dex would do wonders. Still date there are no feeless Dex, afaik

[TheDev1776]

A streaming payments infra like Sablier or Superfluid could really help demonstrate the feeless differentiator of NoM

[EovE7Kj]

One vote until phase1 quorum!

I am nearly done writing up the znnd performance analyses. Compared to a baremetal ubuntu server and unikernel-znnd docker image, it is several orders of magnitude greater for boot time and time to first momentum.

I will post the phase2 shortly after phase1 reaches quorum.

Still brainstorming zApp development and a standardized unikernel framework for it.

[romeo]

It’s approved now

[0x3639]

@EovE7Kj

I will post the phase2 shortly after phase1 reaches quorum.

Was just reading Phase 2 deliveries, and noted this deliverable " Successful integration of smart contract support".

What does this entail?

[EovE7Kj]

@0x3639

Was just reading Phase 2 deliveries, and noted this deliverable " Successful integration of smart contract support".

This was in my original (misguided) proposal, during which I did not realize I could spread the proposal across multiple AZ…

@EovE7Kj

That project will likely fork into multiple AZ proposals, once POC has been delivered and a functional Testnet is online. For now my initial funding proposal can be disregarded, as it may be more realistic to dynamically assess funding requirements and allocations.

…

@EovE7Kj

Given the amount of time and work the project phases will require, I think the best option is to separate each phase into its own AZ project. Given that I have already submitted the proposal to the accelerator for 5k/50k, the metrics for the first phase can be broken down:

• 2k/20k: znnd running in unikernel (~3-4 weeks)
• 1k/10k: Demonstrable improvement in resource efficiency and performance (~1 week)
• 2k/20k: Successful testnet deployment (~4-8 weeks)

So the current phase2 is analysis of performance improvements, and phase3 will be a ‘testnet’ version of an embedded zApp smart contract on unikernel.

The next AZ will be functional zApp development, and will likely span several projects and have crossover with other devs

[0x3639]

Cool. Makes sense. Thanks for explaining that again.